2 Commits

Author	SHA1	Message	Date
Steve Yegge	1edf3c6c88	Fix bd-9v7l: bd status now uses git history for recent activity ... - Changed from database timestamps (7 days) to git log analysis (24 hours) - Git log is fast (~24ms) and reflects actual JSONL changes - Shows commits, total changes, created/closed/reopened/updated counts - Updated tests to verify git-based activity tracking - Removed misleading database-based getRecentActivity function Amp-Thread-ID: https://ampcode.com/threads/T-dc29c5ad-ff33-401a-9546-4d5ca1d8421b Co-authored-by: Amp <amp@ampcode.com>	2025-11-06 18:49:07 -08:00
Steve Yegge	fd93a29ab5	Add 'bd status' command for issue database overview (bd-28db) ... Implement a new `bd status` command that provides a quick snapshot of the issue database state, similar to how `git status` shows working tree state. Features: - Summary counts by state (open, in-progress, blocked, closed) - Ready to work count - Recent activity stats (last 7 days): created, closed, updated issues - Support for --assigned flag to filter by current user - JSON output format with --json flag - Comprehensive test coverage Usage examples: bd status # Show summary bd status --json # JSON output bd status --assigned # Filter to assigned issues bd status --no-daemon # Direct mode with recent activity Note: Recent activity currently only works in direct mode (--no-daemon). Daemon mode support marked with TODO for future enhancement. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-11-02 17:57:59 -08:00