feat: add display guards for large molecules in bd mol current (bd-vln0)
For molecules with >100 steps, shows summary instead of full step list: - Counts children first using efficient GetMoleculeProgress query - Shows progress summary with pointer to bd mol progress - Add --limit flag to cap output (e.g., --limit 50) - Add --range flag for specific ranges (e.g., --range 1-50) Also closes epic bd-5nu1 (mega-molecule progress support). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
beads/crew/fang
committed by
Steve Yegge
Steve Yegge
parent
f3224278a8
commit
7c9b975436
@@ -128,7 +128,7 @@
|
||||
{"id":"bd-5exm","title":"Merge: bd-49kw","description":"branch: polecat/nux\ntarget: main\nsource_issue: bd-49kw\nrig: beads","status":"closed","priority":1,"issue_type":"merge-request","created_at":"2025-12-23T20:43:23.156375-08:00","updated_at":"2025-12-23T21:21:57.693169-08:00","closed_at":"2025-12-23T21:21:57.693169-08:00"}
|
||||
{"id":"bd-5hrq","title":"bd doctor: detect issues referenced in commits but still open","description":"Add a doctor check that finds 'orphaned' issues - ones referenced in git commit messages (e.g., 'fix bug (bd-xxx)') but still marked as open in beads.\n\n**Detection logic:**\n1. Get all open issue IDs from beads\n2. Parse git log for issue ID references matching pattern \\(prefix-[a-z0-9.]+\\)\n3. Report issues that appear in commits but are still open\n\n**Output:**\n⚠ Warning: N issues referenced in commits but still open\n bd-xxx: 'Issue title' (commit abc123)\n bd-yyy: 'Issue title' (commit def456)\n \n These may be implemented but not closed. Run 'bd show \u003cid\u003e' to check.\n\n**Implementation:**\n- Add check to doctor/checks.go\n- Use git log parsing (already have git utilities)\n- Match against configured issue_prefix","status":"closed","priority":1,"issue_type":"feature","created_at":"2025-12-21T21:48:08.473165-08:00","updated_at":"2025-12-21T21:55:37.795109-08:00","closed_at":"2025-12-21T21:55:37.795109-08:00"}
|
||||
{"id":"bd-5l59","title":"Code smell: Issue struct is a God Object (50+ fields)","description":"attached_args: Refactor Issue struct God Object\n\nThe Issue struct in internal/types/types.go has 50+ fields covering many different concerns:\n\n- Basic issue tracking (ID, Title, Description, Status, Priority)\n- Messaging/communication (Sender, Ephemeral, etc.)\n- Agent identity (HookBead, RoleBead, AgentState, RoleType, Rig)\n- Gate/async coordination (AwaitType, AwaitID, Timeout, Waiters)\n- Source tracing (SourceFormula, SourceLocation)\n- HOP validation/entities (Creator, Validations)\n- Compaction (CompactionLevel, CompactedAt, OriginalSize)\n- Tombstones (DeletedAt, DeletedBy, DeleteReason)\n\nConsider:\n1. Extracting field groups into embedded structs (e.g., AgentFields, GateFields)\n2. Using composition pattern to make the struct more modular\n3. At minimum, grouping related fields together with section comments\n\nLocation: internal/types/types.go:12-82","status":"closed","priority":3,"issue_type":"chore","created_at":"2025-12-28T15:31:34.021236-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-28T16:41:07.721864-08:00","closed_at":"2025-12-28T16:41:07.721864-08:00","dependencies":[{"issue_id":"bd-5l59","depends_on_id":"bd-784c","type":"parent-child","created_at":"2025-12-28T15:38:04.187103-08:00","created_by":"daemon"}]}
|
||||
{"id":"bd-5nu1","title":"Mega-molecule progress support for Hanoi demo","description":"Beads-side work for million-step molecule monitoring.\n\n## Context\nTowers of Hanoi with 20 disks = 1,048,575 steps.\nNeed efficient progress queries and display guards.\n\n## Requirements\n1. bd mol progress command (summary without listing all steps)\n2. Display guards in bd mol current (detect large molecules)\n3. Efficient child count queries (already indexed)","status":"open","priority":1,"issue_type":"epic","created_at":"2025-12-31T00:52:40.474932-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T00:52:40.474932-08:00"}
|
||||
{"id":"bd-5nu1","title":"Mega-molecule progress support for Hanoi demo","description":"Beads-side work for million-step molecule monitoring.\n\n## Context\nTowers of Hanoi with 20 disks = 1,048,575 steps.\nNeed efficient progress queries and display guards.\n\n## Requirements\n1. bd mol progress command (summary without listing all steps)\n2. Display guards in bd mol current (detect large molecules)\n3. Efficient child count queries (already indexed)","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-12-31T00:52:40.474932-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T13:08:29.656523-08:00","closed_at":"2025-12-31T13:08:29.656523-08:00","close_reason":"All children complete: mol progress command and display guards implemented"}
|
||||
{"id":"bd-5qim","title":"Optimize GetReadyWork performance - 752ms on 10K database (target: \u003c50ms)","notes":"# Performance Analysis (10K Issue Database)\n\nAnalyzed using CPU profiles from benchmark suite on Apple M2 Pro.\n\n## Operation Performance\n\n| Operation | Time | Allocations | Memory |\n|----------------------------------|---------|-------------|--------|\n| bd ready (GetReadyWork) | ~752ms | 167,466 | 16MB |\n| bd list (SearchIssues no filter) | ~11.6ms | 89,214 | 5.8MB |\n| bd list (SearchIssues filtered) | ~9.2ms | 62,365 | 3.5MB |\n| bd create (CreateIssue) | ~2.6ms | 146 | 8.6KB |\n| bd update (UpdateIssue) | ~0.32ms | 364 | 15KB |\n| bd close (UpdateIssue) | ~0.32ms | 364 | 15KB |\n\n**Target: \u003c50ms for all operations on 10K database**\n\n**Current issue: GetReadyWork is 15x over target (752ms vs 50ms)**\n\n## Root Cause\n\nGetReadyWork (internal/storage/sqlite/ready.go:90-128) uses recursive CTE to propagate blocking:\n- 65x slower than SearchIssues\n- Recalculates entire blocked issue tree on every call\n- Algorithm:\n 1. Find directly blocked issues via 'blocks' dependencies\n 2. Recursively propagate blockage to descendants (max depth: 50)\n 3. Exclude all blocked issues from results\n\n## CPU Profile Analysis\n\n- Database syscalls (pthread_cond_signal, syscall6): ~75%\n- SQLite engine overhead: inherent to recursive CTE\n- Application code (query construction): \u003c1%\n\n**Bottleneck is the recursive CTE query execution, not application code.**\n\n## Optimization Recommendations\n\n### High Impact (Likely to achieve \u003c50ms target)\n\n1. **Cache blocked issue calculation**\n - Add `blocked_issues` table updated on dependency changes\n - Trade write complexity for read speed (ready called \u003e\u003e dependency changes)\n - Eliminates recursive CTE on every read\n\n2. **Add/verify database indexes**\n ```sql\n CREATE INDEX IF NOT EXISTS idx_dependencies_blocked \n ON dependencies(issue_id, type, depends_on_id);\n CREATE INDEX IF NOT EXISTS idx_issues_status \n ON issues(status);\n ```\n\n### Medium Impact\n\n3. **Reduce allocations** (167K allocations for GetReadyWork)\n - Profile `scanIssues()` for object pooling opportunities\n - Reuse slice capacity for repeated calls\n\n### Low Impact (Not recommended)\n- Query optimization for CRUD operations (already \u003c3ms)\n- Connection pooling tuning (not showing in profiles)\n\n## Verification\n\nRun benchmarks to validate optimization:\n```bash\nmake bench-quick\ngo tool pprof -http=:8080 internal/storage/sqlite/bench-cpu-*.prof\n```\n\nProfile files automatically generated in `internal/storage/sqlite/`.","status":"tombstone","priority":0,"issue_type":"bug","created_at":"2025-11-14T09:02:46.507526-08:00","updated_at":"2025-12-25T01:21:01.952723-08:00","deleted_at":"2025-12-25T01:21:01.952723-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"bug"}
|
||||
{"id":"bd-5rj1","title":"Merge: bd-gqxd","description":"branch: polecat/furiosa\ntarget: main\nsource_issue: bd-gqxd\nrig: beads","status":"closed","priority":2,"issue_type":"merge-request","created_at":"2025-12-23T16:40:21.707706-08:00","updated_at":"2025-12-23T19:12:08.349245-08:00","closed_at":"2025-12-23T19:12:08.349245-08:00"}
|
||||
{"id":"bd-5s91","title":"CLI API Audit for OSS Launch","description":"Comprehensive CLI API audit before OSS launch.\n\n## Tasks\n1. Review gt command groupings - propose consolidation\n2. Review bd command groupings \n3. Document gt vs bd ownership boundaries\n4. Identify naming inconsistencies\n5. Document flag vs subcommand criteria\n\n## Context\n- Pre-OSS launch cleanup\n- Goal: clean, consistent, discoverable CLI surface","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-12-25T00:15:41.355013-08:00","updated_at":"2025-12-25T13:26:25.587476-08:00","closed_at":"2025-12-25T13:26:25.587476-08:00"}
|
||||
@@ -372,6 +372,7 @@
|
||||
{"id":"bd-exy3","title":"Ephemeral patrol molecules leaking into beads","description":"## Problem\n\nEphemeral patrol orchestration molecules (e.g., mol-deacon-patrol, wisp step issues) keep appearing in `bd ready` output in gastown beads.\n\nThese are ephemeral/wisp issues that should:\n1. Never be synced to the beads-sync branch\n2. Live only in .beads-wisp/ (ephemeral storage)\n3. Be squashed to digests, not persisted as regular beads\n\n## Examples found\n\n- gt-wisp-6ue: mol-deacon-patrol\n- gt-pacdm: mol-deacon-patrol \n- gt-wisp-mpm: Check own context limit\n- gt-wisp-lkc: Clean dead sessions\n\n## Investigation needed\n\n1. Where are these being created? (gt mol bond? manual bd create?)\n2. Why are they using the gt- prefix instead of staying ephemeral?\n3. Is the wisp storage (.beads-wisp/) being used correctly?\n4. Is bd sync accidentally picking up ephemeral issues?\n\n## Expected behavior\n\nPatrol molecules and their steps should be ephemeral and never appear in `bd ready` or `bd list`.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-27T17:04:16.51075-08:00","created_by":"gastown/crew/joe","updated_at":"2025-12-27T19:18:16.809273-08:00","closed_at":"2025-12-27T19:18:16.809273-08:00"}
|
||||
{"id":"bd-eylk","title":"Full event test","status":"tombstone","priority":2,"issue_type":"event","created_at":"2025-12-30T16:08:32.342126-08:00","created_by":"beads/polecats/obsidian","updated_at":"2025-12-30T16:08:59.772362-08:00","deleted_at":"2025-12-30T16:08:59.772362-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"event"}
|
||||
{"id":"bd-eyrh","title":"🤝 HANDOFF: Review remaining beads PRs","description":"## Current State\nJust merged PR #653 (doctor refactor) and added tests to restore coverage.\n\n## Remaining Open PRs to Review\nRun `gh pr list --repo steveyegge/beads` to see current list. As of handoff:\n\n1. #655 - feat: Linear Integration (jblwilliams)\n2. #651 - feat(audit): agent audit trail (dchichkov)\n3. #648 - Stop init creating redundant @AGENTS.md (maphew)\n4. #646 - fix(unix): handle Statfs field types (jordanhubbard)\n5. #645 - feat: /plan-to-beads Claude Code command (petebytes)\n6. #642, #641, #640 - sync branch fixes (cpdata)\n\n## Review Checklist\n- Check CI status with `gh pr checks \u003cnum\u003e --repo steveyegge/beads`\n- Verify no .beads/ data leaking (we have a hook now)\n- Review code quality\n- Merge good ones, request changes on problematic ones\n\n## Notes\n- User wants us to be proactive about merging good PRs\n- Can add tests ourselves if coverage drops","status":"tombstone","priority":2,"issue_type":"message","created_at":"2025-12-19T17:44:34.149837-08:00","updated_at":"2025-12-21T13:53:33.613805-08:00","deleted_at":"2025-12-21T13:53:33.613805-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"message"}
|
||||
{"id":"bd-eysh","title":"Test refile v2","description":"Testing improved refile","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-31T13:00:22.994648-08:00","created_by":"beads/crew/grip","updated_at":"2025-12-31T13:00:30.637161-08:00","closed_at":"2025-12-31T13:00:30.637161-08:00","close_reason":"Refiled to gt-w66v4"}
|
||||
{"id":"bd-eyto","title":"Time-dependent tests may be flaky near TTL boundary","description":"Several tombstone merge tests use time.Now() to create test data: time.Now().Add(-24 * time.Hour), time.Now().Add(-60 * 24 * time.Hour), etc. While these work reliably in practice (24h vs 30d TTL has large margin), they could theoretically be flaky if: 1) Tests run slowly, 2) System clock changes during test, 3) TTL constants change. Recommendation: Consider using a fixed reference time or time injection for deterministic tests. Lower priority since current margin is large. Files: internal/merge/merge_test.go:1337-1338, 1352-1353, 1548-1549, 1590-1591","status":"hooked","priority":3,"issue_type":"task","created_at":"2025-12-05T16:37:02.348143-08:00","updated_at":"2025-12-30T15:44:43.36321-08:00"}
|
||||
{"id":"bd-f0wm","title":"Swarm status doesn't update after task completions","description":"During swarm bd-784c, the swarm status remained at '9% (1/11 tasks merged)' even after 5 tasks were completed and closed.\n\n**Observed:**\n```\ngt swarm status bd-784c\nProgress: 9% (1/11 tasks merged)\n```\n\nBut bd list showed 4+ issues closed:\n- bd-j3dj, bd-kkka, bd-1tkd, bd-9btu all closed\n\n**Expected:**\nSwarm status should reflect actual completion count, either by:\n1. Polling issue status from beads\n2. Updating when polecats close issues\n3. Updating when commits are pushed to integration branch\n\n**Impact:**\nCoordinator (me) had to manually check bd list to know actual progress.","status":"closed","priority":2,"issue_type":"bug","created_at":"2025-12-28T16:17:49.27816-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-28T22:14:20.098792-08:00","closed_at":"2025-12-28T22:14:20.098792-08:00"}
|
||||
{"id":"bd-f2lb","title":"Update CHANGELOG.md with release notes","description":"Add meaningful release notes to CHANGELOG.md describing what changed in test-squash","status":"tombstone","priority":1,"issue_type":"task","created_at":"2025-12-21T13:52:33.066065-08:00","updated_at":"2025-12-21T13:53:49.858742-08:00","deleted_at":"2025-12-21T13:53:49.858742-08:00","deleted_by":"stevey","delete_reason":"manual delete","original_type":"task"}
|
||||
@@ -430,7 +431,7 @@
|
||||
{"id":"bd-hobo","title":"Distinct prefixes for protos, molecules, wisps","description":"Template/workflow entities should have visually distinct prefixes from regular issues.\n\n**Problem:**\n- Protos (bd-7bs4) look like regular issues - invites squashing\n- Molecules (poured instances) also use bd- prefix\n- Wisps are in separate DB but still use bd- when referenced\n\n**Proposed Prefixes:**\n- `proto-` for templates (e.g., proto-release, proto-review)\n- `mol-` for active molecules (poured from protos)\n- `wisp-` for ephemeral wisps (vapor phase)\n\n**Benefits:**\n- Instant visual recognition of entity type\n- Prevents accidental modification of templates\n- Clear lifecycle: proto → mol → wisp → digest\n\n**Implementation options:**\n1. Separate databases with different prefixes\n2. Issue type determines prefix generation\n3. Naming convention enforced by bd pour/wisp commands","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-24T16:45:24.940809-08:00","updated_at":"2025-12-25T02:04:52.459233-08:00","closed_at":"2025-12-25T02:04:52.459233-08:00","labels":["workflow"]}
|
||||
{"id":"bd-hp8g","title":"gt sling should look up formulas from .beads/formulas/ registry","description":"## Problem\n\ngt sling \u003cformula-name\u003e doesn't find formulas from the registry that bd formula list shows.\n\n## What I tried\n\n1. gt sling beads/crew/emma --formula beads-release --var version=0.42.0\n - Problem: --formula flag doesn't exist\n\n2. gt sling beads-release beads/crew/emma --var version=0.42.0\n - Error: open .../beads-release: no such file or directory\n - Problem: Looks for file in cwd, not formula registry\n\n## What worked\n\nbd mol wisp beads-release --var version=0.42.0 - correctly finds formula from .beads/formulas/\n\n## Expected\n\ngt sling should use the same formula lookup as bd mol wisp - checking .beads/formulas/*.formula.json\n\n## Documentation gap\n\nThe help shows examples like 'gt sling mol-release mayor/' suggesting formula slinging works, but it doesn't find registry formulas.","status":"closed","priority":2,"issue_type":"bug","assignee":"beads/polecats/jade","created_at":"2025-12-30T21:18:17.251292-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-30T22:06:27.153176-08:00","closed_at":"2025-12-30T22:06:27.153176-08:00","close_reason":"Fixed in both repos: bd cook now looks up formulas from registry, and gt sling uses bd mol wisp"}
|
||||
{"id":"bd-hr39","title":"bd cook: needs field not converted to step dependencies","description":"When cooking a formula with `needs` fields on steps, the dependencies are not created between sibling steps.\n\n## Expected\n\nFormula:\n```yaml\nsteps:\n - id: inbox-check\n title: Check inbox\n - id: trigger-spawns\n title: Nudge polecats\n needs: [inbox-check]\n```\n\nShould create:\n- mol-foo.inbox-check (no deps)\n- mol-foo.trigger-spawns → depends on → mol-foo.inbox-check\n\n## Actual\n\nBoth steps only depend on the parent proto:\n- mol-foo.inbox-check → depends on → mol-foo\n- mol-foo.trigger-spawns → depends on → mol-foo\n\nThe `needs` field is ignored.\n\n## Impact\n\nThis breaks the step execution order. Steps that should wait for predecessors will run in parallel or out of order.\n\n## Reproduction\n\n```bash\nbd cook mol-deacon-patrol.formula.yaml\nbd show mol-deacon-patrol.trigger-pending-spawns\n# Shows: Depends on mol-deacon-patrol (parent only)\n# Should show: Depends on mol-deacon-patrol.inbox-check\n```","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-24T13:49:59.023514-08:00","updated_at":"2025-12-24T13:59:09.929298-08:00","closed_at":"2025-12-24T13:59:09.929298-08:00"}
|
||||
{"id":"bd-htwx","title":"Stale daemon.lock files cause 5+ second delays","description":"## Problem\nWhen a bd daemon crashes or is killed without cleanup, it leaves a stale daemon.lock file. Subsequent bd commands try to connect to the dead daemon, causing 5+ second timeouts before falling back to direct mode.\n\nFound during gt status optimization (gt-zdtpw) - one stale wyvern daemon was causing 10+ second delays.\n\n## Evidence\n```\n# Lock files with stale PIDs:\n$ find ~/gt -name \"daemon.lock\" -exec cat {} \\;\n{\"pid\": 11045, ...} # Not running (from Dec 27)\n{\"pid\": 15986, ...} # Not running (from Dec 27)\n{\"pid\": 98055, ...} # Just restarted\n\n# But running daemons have different PIDs:\n$ ps aux | grep \"bd.*daemon\"\n11847, 11683, 11624 # None match the lock files!\n```\n\n## Proposed fixes\n\n### 1. Validate lock on startup (quick fix)\nBefore trusting daemon.lock, check if the PID is still running:\n```python\ndef is_daemon_alive(lock_path):\n lock = json.load(open(lock_path))\n try:\n os.kill(lock[\"pid\"], 0) # Signal 0 = check if alive\n return True\n except OSError:\n return False\n```\n\n### 2. Heartbeat mechanism (robust fix)\nDaemon writes periodic heartbeat to lock file or separate file.\nClients check heartbeat age before attempting IPC.\n\n### 3. Lock cleanup in daemon startup\nWhen starting a new daemon, always check for and clean stale locks.\n\n### 4. Graceful shutdown handling\nRegister signal handlers (SIGTERM, SIGINT) to clean up lock on exit.\n\n## Workaround\nFor now, gastown uses `--no-daemon` for all read operations to avoid this issue.","status":"open","priority":1,"issue_type":"bug","created_at":"2025-12-31T12:19:37.758373-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T12:19:37.758373-08:00"}
|
||||
{"id":"bd-htwx","title":"Stale daemon.lock files cause 5+ second delays","description":"## Problem\nWhen a bd daemon crashes or is killed without cleanup, it leaves a stale daemon.lock file. Subsequent bd commands try to connect to the dead daemon, causing 5+ second timeouts before falling back to direct mode.\n\nFound during gt status optimization (gt-zdtpw) - one stale wyvern daemon was causing 10+ second delays.\n\n## Evidence\n```\n# Lock files with stale PIDs:\n$ find ~/gt -name \"daemon.lock\" -exec cat {} \\;\n{\"pid\": 11045, ...} # Not running (from Dec 27)\n{\"pid\": 15986, ...} # Not running (from Dec 27)\n{\"pid\": 98055, ...} # Just restarted\n\n# But running daemons have different PIDs:\n$ ps aux | grep \"bd.*daemon\"\n11847, 11683, 11624 # None match the lock files!\n```\n\n## Proposed fixes\n\n### 1. Validate lock on startup (quick fix)\nBefore trusting daemon.lock, check if the PID is still running:\n```python\ndef is_daemon_alive(lock_path):\n lock = json.load(open(lock_path))\n try:\n os.kill(lock[\"pid\"], 0) # Signal 0 = check if alive\n return True\n except OSError:\n return False\n```\n\n### 2. Heartbeat mechanism (robust fix)\nDaemon writes periodic heartbeat to lock file or separate file.\nClients check heartbeat age before attempting IPC.\n\n### 3. Lock cleanup in daemon startup\nWhen starting a new daemon, always check for and clean stale locks.\n\n### 4. Graceful shutdown handling\nRegister signal handlers (SIGTERM, SIGINT) to clean up lock on exit.\n\n## Workaround\nFor now, gastown uses `--no-daemon` for all read operations to avoid this issue.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-31T12:19:37.758373-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T13:03:56.641703-08:00","closed_at":"2025-12-31T13:03:56.641703-08:00","close_reason":"Fixed - use flock-based check as authoritative source instead of PID file"}
|
||||
{"id":"bd-hulf","title":"Molecule execution state management","description":"Implement molecule execution state tracking.\n\n## State Location\n\n```\n.beads/molecules/\u003cmol-id\u003e.state.yaml\n```\n\n## State Schema\n\n```yaml\nid: mol-deacon-patrol\nformula: mol-deacon-patrol # Source formula\nbonded_at: ISO timestamp\nbonded_by: entity who created it\n\n# Execution state\nstatus: running | paused | completed | failed\ncurrent_step: step-id\nstarted_at: ISO timestamp\ncompleted_at: ISO timestamp (if done)\n\n# Loop tracking\nreset_count: 0\nlast_reset_at: null\n\n# Per-step state\nsteps:\n inbox-check:\n status: completed | in_progress | pending\n started_at: ...\n completed_at: ...\n spawn-work:\n status: pending\n self-inspect:\n status: pending\n\n# Variables (from formula instantiation)\nvariables:\n rig: gastown\n issue_id: gt-xxx\n```\n\n## Operations\n\n- CreateState(molID, formula, variables) - Initialize state\n- LoadState(molID) - Read current state \n- SaveState(molID, state) - Write state\n- AdvanceStep(molID) - Mark current complete, find next\n- ResetState(molID) - Reset all steps to pending\n\n## Files\n\n- internal/mol/state.go\n- internal/mol/types.go","status":"closed","priority":0,"issue_type":"task","created_at":"2025-12-24T15:53:43.381634-08:00","updated_at":"2025-12-24T16:53:11.807645-08:00","closed_at":"2025-12-24T16:53:11.807645-08:00"}
|
||||
{"id":"bd-hvng","title":"Merge: bd-w193","description":"branch: polecat/nux\ntarget: main\nsource_issue: bd-w193\nrig: beads","status":"closed","priority":2,"issue_type":"merge-request","created_at":"2025-12-19T23:23:47.496139-08:00","updated_at":"2025-12-20T23:17:26.996479-08:00","closed_at":"2025-12-20T23:17:26.996479-08:00"}
|
||||
{"id":"bd-hw3w","title":"Update info.go versionChanges","description":"Add entry to versionChanges in cmd/bd/info.go with agent-actionable changes for {{version}}","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-19T22:56:01.016558-08:00","updated_at":"2025-12-20T17:59:26.262511-08:00","closed_at":"2025-12-20T01:23:50.3879-08:00","dependencies":[{"issue_id":"bd-hw3w","depends_on_id":"bd-6s61","type":"parent-child","created_at":"2025-12-19T22:56:14.941855-08:00","created_by":"daemon"},{"issue_id":"bd-hw3w","depends_on_id":"bd-czss","type":"blocks","created_at":"2025-12-19T22:56:23.219257-08:00","created_by":"daemon"}]}
|
||||
@@ -783,6 +784,7 @@
|
||||
{"id":"bd-thgk","title":"Improve test coverage for internal/compact (18.2% → 70%)","description":"Improve test coverage for internal/compact package from 17% to 70%.\n\n## Current State\n- Coverage: 17.3%\n- Files: compactor.go, git.go, haiku.go\n- Tests: compactor_test.go (minimal tests)\n\n## Functions Needing Tests\n\n### compactor.go (core compaction)\n- [ ] New - needs config validation tests\n- [ ] CompactTier1 - needs single issue compaction tests\n- [ ] CompactTier1Batch - needs batch processing tests\n- [ ] compactSingleWithResult - internal, test via public API\n\n### git.go\n- [ ] GetCurrentCommitHash - needs git repo fixture tests\n\n### haiku.go (AI summarization) - MOCK REQUIRED\n- [ ] NewHaikuClient - needs API key validation tests\n- [ ] SummarizeTier1 - needs mock API response tests\n- [ ] callWithRetry - needs retry logic tests\n- [ ] isRetryable - needs error classification tests\n- [ ] renderTier1Prompt - needs template rendering tests\n\n## Implementation Guide\n\n1. **Mock the Anthropic API:**\n ```go\n // Create mock HTTP server\n server := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n json.NewEncoder(w).Encode(map[string]interface{}{\n \"content\": []map[string]string{{\"text\": \"Summarized content\"}},\n })\n }))\n defer server.Close()\n \n // Point client at mock\n client.baseURL = server.URL\n ```\n\n2. **Test scenarios:**\n - Successful compaction with AI summary\n - API failure with retry\n - Rate limit handling\n - Empty issue handling\n - Large issue truncation\n\n3. **Use test database:**\n ```go\n store, cleanup := testutil.NewTestStore(t)\n defer cleanup()\n ```\n\n## Success Criteria\n- Coverage ≥ 70%\n- AI calls properly mocked (no real API calls in tests)\n- Retry logic verified\n- Error paths covered\n\n## Run Tests\n```bash\ngo test -v -cover ./internal/compact\ngo test -race ./internal/compact\n```","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-13T20:42:58.455767-08:00","updated_at":"2025-12-23T13:41:10.80832-08:00","closed_at":"2025-12-23T13:41:10.80832-08:00","dependencies":[{"issue_id":"bd-thgk","depends_on_id":"bd-iz5t","type":"parent-child","created_at":"2025-12-23T12:44:07.287377-08:00","created_by":"daemon"}]}
|
||||
{"id":"bd-ti1m","title":"Test hooked styling","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-28T22:33:47.135871-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-28T22:34:26.00871-08:00","closed_at":"2025-12-28T22:34:26.00871-08:00"}
|
||||
{"id":"bd-tj00","title":"Update local installation","description":"go build -o ~/.local/bin/bd ./cmd/bd \u0026\u0026 codesign -s - ~/.local/bin/bd","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-20T21:53:20.616907-08:00","updated_at":"2025-12-20T21:55:42.756171-08:00","closed_at":"2025-12-20T21:55:42.756171-08:00","dependencies":[{"issue_id":"bd-tj00","depends_on_id":"bd-an4s","type":"parent-child","created_at":"2025-12-20T21:53:20.619834-08:00","created_by":"daemon"},{"issue_id":"bd-tj00","depends_on_id":"bd-9l0h","type":"blocks","created_at":"2025-12-20T21:53:29.817989-08:00","created_by":"daemon"}]}
|
||||
{"id":"bd-tksk","title":"Support session_id field on issue close/update mutations","description":"## Context\n\nPer Gas Town decision 009-session-events-architecture.md, work attribution for\nentity CV building requires capturing which Claude Code session performed work.\n\n## Implementation\n\nAdd session_id support to issue mutations:\n\n### Schema\nAdd optional field to issue close:\n- closed_by_session: string (Claude Code session UUID)\n\n### CLI\n```bash\nbd close gt-abc --session \"abc123-session-id\"\n# Or via env var:\nCLAUDE_SESSION_ID=abc123 bd close gt-abc\n```\n\n### Storage\nStore in issues.jsonl:\n```json\n{\"id\": \"gt-abc\", \"status\": \"closed\", \"closed_by_session\": \"abc123\", ...}\n```\n\n## Acceptance Criteria\n\n- [ ] bd close accepts --session flag or reads CLAUDE_SESSION_ID env\n- [ ] session_id stored in issue close record\n- [ ] bd show displays closed_by_session if present\n- [ ] Works for bd update --status=closed as well\n\n## Future\n\n- Query by session: bd list --closed-by-session=X\n- Entity chain: aggregate session activity for CV\n\n## Related\n\n- Gas Town docs/hop/decisions/009-session-events-architecture.md\n- gt-nvz8b: gt done captures session_id","status":"in_progress","priority":2,"issue_type":"feature","assignee":"beads/crew/dave","created_at":"2025-12-31T12:49:58.379182-08:00","created_by":"gastown/crew/joe","updated_at":"2025-12-31T12:58:46.657764-08:00"}
|
||||
{"id":"bd-tm2p","title":"Polecats get stuck on interactive shell prompts (cp/mv/rm -i)","description":"During swarm operations, polecats frequently get stuck waiting for interactive prompts from shell commands like:\n- cp prompting 'overwrite file? (y/n)'\n- mv prompting 'overwrite file? (y/n)' \n- rm prompting 'remove file?'\n\nThis happens because macOS aliases or shell configs may have -i flags set by default.\n\nRoot cause: Claude Code runs commands that trigger interactive confirmation prompts, but cannot respond to them, causing the agent to hang indefinitely.\n\nObserved in: Multiple polecats during GH issues swarm (Dec 2024)\n- Derrick, Roustabout, Prospector, Warboy all got stuck on y/n prompts\n\nSuggested fixes:\n1. AGENTS.md should instruct agents to always use -f flag with cp/mv/rm\n2. Polecat startup could set shell aliases to use non-interactive versions\n3. bd prime hook could include guidance about non-interactive commands\n4. Consider detecting stuck prompts and auto-recovering","status":"tombstone","priority":1,"issue_type":"bug","created_at":"2025-12-14T16:51:24.572271-08:00","updated_at":"2025-12-25T01:21:01.952723-08:00","deleted_at":"2025-12-25T01:21:01.952723-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"bug"}
|
||||
{"id":"bd-to1u","title":"Run bump-version.sh test-squash","description":"Run ./scripts/bump-version.sh test-squash to update version in all files","status":"tombstone","priority":1,"issue_type":"task","created_at":"2025-12-21T13:52:33.06696-08:00","updated_at":"2025-12-21T13:53:41.841677-08:00","deleted_at":"2025-12-21T13:53:41.841677-08:00","deleted_by":"stevey","delete_reason":"manual delete","original_type":"task"}
|
||||
{"id":"bd-toy3","title":"Test hook","status":"tombstone","priority":2,"issue_type":"task","created_at":"2025-12-16T18:33:39.717036-08:00","updated_at":"2025-12-17T16:11:17.070763-08:00","deleted_at":"2025-12-17T16:11:17.070763-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"task"}
|
||||
@@ -821,7 +823,7 @@
|
||||
{"id":"bd-vgi5","title":"Push version bump to GitHub","description":"git push origin main - triggers CI but no release yet.","status":"tombstone","priority":1,"issue_type":"task","created_at":"2025-12-18T22:43:05.363604-08:00","updated_at":"2025-12-24T16:25:30.019895-08:00","dependencies":[{"issue_id":"bd-vgi5","depends_on_id":"bd-qqc","type":"parent-child","created_at":"2025-12-18T22:43:16.87736-08:00","created_by":"daemon"},{"issue_id":"bd-vgi5","depends_on_id":"bd-3ggb","type":"blocks","created_at":"2025-12-18T22:43:21.078208-08:00","created_by":"daemon"}],"deleted_at":"2025-12-24T16:25:30.019895-08:00","deleted_by":"daemon","delete_reason":"delete","original_type":"task"}
|
||||
{"id":"bd-vjas","title":"Add --pretty flag to bd ready","description":"bd list has --pretty but bd ready doesn't. Should support same tree format with status/priority symbols for consistency.","status":"open","priority":3,"issue_type":"feature","created_at":"2025-12-31T11:54:59.911409-08:00","created_by":"mayor","updated_at":"2025-12-31T11:54:59.911409-08:00"}
|
||||
{"id":"bd-vks2","title":"bd dep tree doesn't display external dependencies","description":"GetDependencyTree (dependencies.go:464-624) uses a recursive CTE that JOINs with the issues table, which means external refs (external:project:capability) are invisible in the tree output.\n\nWhen an issue has an external blocking dependency, running 'bd dep tree \u003cid\u003e' won't show it.\n\nOptions:\n1. Query dependencies table separately for external refs and display them as leaf nodes\n2. Add a synthetic 'external' node type that shows the ref and resolution status\n3. Document that external deps aren't shown in tree view (use bd show for full deps)\n\nLower priority since bd show \u003cid\u003e displays all dependencies including external refs.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-21T23:45:27.121934-08:00","updated_at":"2025-12-22T22:30:19.083652-08:00","closed_at":"2025-12-22T22:30:19.083652-08:00","dependencies":[{"issue_id":"bd-vks2","depends_on_id":"bd-zmmy","type":"discovered-from","created_at":"2025-12-21T23:45:27.122511-08:00","created_by":"daemon"}]}
|
||||
{"id":"bd-vln0","title":"Add display guards for large molecules in bd mol current","description":"When molecule has \u003e100 steps, show summary instead of list.\n\nChanges:\n1. Count children first\n2. If count \u003e 100: show summary + pointer to bd mol progress\n3. Add --range flag for viewing specific step ranges\n4. Add --limit flag for capping output","status":"open","priority":2,"issue_type":"task","created_at":"2025-12-31T00:52:52.823925-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T00:52:52.823925-08:00","dependencies":[{"issue_id":"bd-vln0","depends_on_id":"bd-5nu1","type":"parent-child","created_at":"2025-12-31T00:54:00.833563-08:00","created_by":"gastown/crew/max"}]}
|
||||
{"id":"bd-vln0","title":"Add display guards for large molecules in bd mol current","description":"When molecule has \u003e100 steps, show summary instead of list.\n\nChanges:\n1. Count children first\n2. If count \u003e 100: show summary + pointer to bd mol progress\n3. Add --range flag for viewing specific step ranges\n4. Add --limit flag for capping output","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-31T00:52:52.823925-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T13:08:19.539445-08:00","closed_at":"2025-12-31T13:08:19.539445-08:00","close_reason":"Added display guards: threshold check, --limit and --range flags","dependencies":[{"issue_id":"bd-vln0","depends_on_id":"bd-5nu1","type":"parent-child","created_at":"2025-12-31T00:54:00.833563-08:00","created_by":"gastown/crew/max"}]}
|
||||
{"id":"bd-vpan","title":"Re: Thread Test 2","description":"Got your message. Testing reply feature.","status":"tombstone","priority":2,"issue_type":"message","created_at":"2025-12-16T18:21:29.144352-08:00","updated_at":"2025-12-17T16:11:17.070763-08:00","dependencies":[{"issue_id":"bd-vpan","depends_on_id":"bd-x36g","type":"replies-to","created_at":"2025-12-18T13:45:31.137191-08:00","created_by":"migration"}],"deleted_at":"2025-12-17T16:11:17.070763-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"message"}
|
||||
{"id":"bd-vqh9","title":"Code smell: init.go is 1928 lines - needs splitting","description":"cmd/bd/init.go is 1928 lines covering multiple init modes, contributor/team setup, hooks setup, and stealth mode.\n\n**Problem:**\n- File is too large to understand and maintain\n- Multiple responsibilities within single file\n- Harder to test individual components\n\n**Acceptance Criteria:**\n- [ ] Split into logical files (init_setup.go, init_hooks.go, init_stealth.go, etc.)\n- [ ] Each file under 500 lines\n- [ ] No functionality changes\n- [ ] Tests pass","status":"closed","priority":2,"issue_type":"chore","created_at":"2025-12-28T18:58:59.37092-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-28T19:01:18.403417-08:00","closed_at":"2025-12-28T19:01:18.403417-08:00","dependencies":[{"issue_id":"bd-vqh9","depends_on_id":"bd-ox1o","type":"blocks","created_at":"2025-12-28T19:00:23.586968-08:00","created_by":"daemon"}]}
|
||||
{"id":"bd-vqm0","title":"Swarm: Code Review: Swarm commands consolidation","description":"Swarm molecule orchestrating epic bd-2ubv.\n\nEpic: bd-2ubv\nCoordinator: ","status":"closed","priority":2,"issue_type":"molecule","created_at":"2025-12-28T22:06:58.82489-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-29T13:40:29.709541-08:00","closed_at":"2025-12-29T13:40:29.709541-08:00","close_reason":"Stale/spurious - test artifacts, merged PRs, or auto-close candidates","dependencies":[{"issue_id":"bd-vqm0","depends_on_id":"bd-2ubv","type":"relates-to","created_at":"2025-12-28T22:06:58.825608-08:00","created_by":"beads/crew/dave"}]}
|
||||
|
||||
@@ -6,6 +6,8 @@ import (
|
||||
"fmt"
|
||||
"os"
|
||||
"sort"
|
||||
"strconv"
|
||||
"strings"
|
||||
|
||||
"github.com/spf13/cobra"
|
||||
"github.com/steveyegge/beads/internal/rpc"
|
||||
@@ -15,6 +17,10 @@ import (
|
||||
"github.com/steveyegge/beads/internal/utils"
|
||||
)
|
||||
|
||||
// LargeMoleculeThreshold is the step count above which we show summary instead of full list.
|
||||
// This prevents overwhelming output and slow queries for mega-molecules.
|
||||
const LargeMoleculeThreshold = 100
|
||||
|
||||
// MoleculeProgress holds the progress information for a molecule
|
||||
type MoleculeProgress struct {
|
||||
MoleculeID string `json:"molecule_id"`
|
||||
@@ -47,11 +53,18 @@ The output shows all steps with status indicators:
|
||||
[current] - Step is in_progress (you are here)
|
||||
[ready] - Step is ready to start (unblocked)
|
||||
[blocked] - Step is blocked by dependencies
|
||||
[pending] - Step is waiting`,
|
||||
[pending] - Step is waiting
|
||||
|
||||
For large molecules (>100 steps), a summary is shown instead.
|
||||
Use --limit or --range to view specific steps:
|
||||
bd mol current <id> --limit 50 # Show first 50 steps
|
||||
bd mol current <id> --range 100-150 # Show steps 100-150`,
|
||||
Args: cobra.MaximumNArgs(1),
|
||||
Run: func(cmd *cobra.Command, args []string) {
|
||||
ctx := rootCtx
|
||||
forAgent, _ := cmd.Flags().GetString("for")
|
||||
limit, _ := cmd.Flags().GetInt("limit")
|
||||
rangeStr, _ := cmd.Flags().GetString("range")
|
||||
|
||||
// Determine who we're looking for
|
||||
agent := forAgent
|
||||
@@ -70,6 +83,20 @@ The output shows all steps with status indicators:
|
||||
os.Exit(1)
|
||||
}
|
||||
|
||||
// Parse range flag if provided
|
||||
var rangeStart, rangeEnd int
|
||||
if rangeStr != "" {
|
||||
var err error
|
||||
rangeStart, rangeEnd, err = parseRange(rangeStr)
|
||||
if err != nil {
|
||||
fmt.Fprintf(os.Stderr, "Error: invalid range '%s': %v\n", rangeStr, err)
|
||||
os.Exit(1)
|
||||
}
|
||||
}
|
||||
|
||||
// Determine if user explicitly requested steps
|
||||
explicitSteps := limit > 0 || rangeStr != ""
|
||||
|
||||
var molecules []*MoleculeProgress
|
||||
|
||||
if len(args) == 1 {
|
||||
@@ -80,11 +107,32 @@ The output shows all steps with status indicators:
|
||||
os.Exit(1)
|
||||
}
|
||||
|
||||
// Check child count first for large molecule detection
|
||||
stats, err := store.GetMoleculeProgress(ctx, moleculeID)
|
||||
if err != nil {
|
||||
fmt.Fprintf(os.Stderr, "Error loading molecule: %v\n", err)
|
||||
os.Exit(1)
|
||||
}
|
||||
|
||||
// If large molecule and no explicit flags, show summary
|
||||
if stats.Total > LargeMoleculeThreshold && !explicitSteps && !jsonOutput {
|
||||
printLargeMoleculeSummary(stats)
|
||||
return
|
||||
}
|
||||
|
||||
progress, err := getMoleculeProgress(ctx, store, moleculeID)
|
||||
if err != nil {
|
||||
fmt.Fprintf(os.Stderr, "Error loading molecule: %v\n", err)
|
||||
os.Exit(1)
|
||||
}
|
||||
|
||||
// Apply limit or range filtering
|
||||
if rangeStr != "" {
|
||||
progress.Steps = filterStepsByRange(progress.Steps, rangeStart, rangeEnd)
|
||||
} else if limit > 0 && len(progress.Steps) > limit {
|
||||
progress.Steps = progress.Steps[:limit]
|
||||
}
|
||||
|
||||
molecules = append(molecules, progress)
|
||||
} else {
|
||||
// Infer from in_progress issues
|
||||
@@ -480,7 +528,76 @@ func PrintContinueResult(result *ContinueResult) {
|
||||
}
|
||||
}
|
||||
|
||||
// parseRange parses a range string like "1-50" or "100-150" into start and end indices.
|
||||
// Returns 1-based indices (start=1 means first step).
|
||||
func parseRange(rangeStr string) (start, end int, err error) {
|
||||
parts := strings.Split(rangeStr, "-")
|
||||
if len(parts) != 2 {
|
||||
return 0, 0, fmt.Errorf("expected format 'start-end' (e.g., '1-50')")
|
||||
}
|
||||
start, err = strconv.Atoi(strings.TrimSpace(parts[0]))
|
||||
if err != nil {
|
||||
return 0, 0, fmt.Errorf("invalid start: %w", err)
|
||||
}
|
||||
end, err = strconv.Atoi(strings.TrimSpace(parts[1]))
|
||||
if err != nil {
|
||||
return 0, 0, fmt.Errorf("invalid end: %w", err)
|
||||
}
|
||||
if start < 1 {
|
||||
return 0, 0, fmt.Errorf("start must be >= 1")
|
||||
}
|
||||
if end < start {
|
||||
return 0, 0, fmt.Errorf("end must be >= start")
|
||||
}
|
||||
return start, end, nil
|
||||
}
|
||||
|
||||
// filterStepsByRange filters steps to a 1-based range [start, end].
|
||||
func filterStepsByRange(steps []*StepStatus, start, end int) []*StepStatus {
|
||||
// Convert to 0-based indices
|
||||
startIdx := start - 1
|
||||
endIdx := end
|
||||
|
||||
if startIdx >= len(steps) {
|
||||
return nil
|
||||
}
|
||||
if endIdx > len(steps) {
|
||||
endIdx = len(steps)
|
||||
}
|
||||
return steps[startIdx:endIdx]
|
||||
}
|
||||
|
||||
// printLargeMoleculeSummary prints a summary for molecules with many steps.
|
||||
func printLargeMoleculeSummary(stats *types.MoleculeProgressStats) {
|
||||
fmt.Printf("Molecule: %s\n", ui.RenderAccent(stats.MoleculeID))
|
||||
fmt.Printf(" %s\n", stats.MoleculeTitle)
|
||||
fmt.Println()
|
||||
|
||||
// Progress summary
|
||||
var percent float64
|
||||
if stats.Total > 0 {
|
||||
percent = float64(stats.Completed) * 100 / float64(stats.Total)
|
||||
}
|
||||
fmt.Printf("Progress: %d / %d steps (%.1f%%)\n", stats.Completed, stats.Total, percent)
|
||||
|
||||
if stats.CurrentStepID != "" {
|
||||
fmt.Printf("Current step: %s\n", stats.CurrentStepID)
|
||||
} else if stats.InProgress > 0 {
|
||||
fmt.Printf("In progress: %d step(s)\n", stats.InProgress)
|
||||
}
|
||||
|
||||
fmt.Println()
|
||||
fmt.Printf("%s This molecule has %d steps (threshold: %d).\n",
|
||||
ui.RenderWarn("Note:"), stats.Total, LargeMoleculeThreshold)
|
||||
fmt.Println("To view steps, use one of:")
|
||||
fmt.Printf(" bd mol current %s --limit 50 # First 50 steps\n", stats.MoleculeID)
|
||||
fmt.Printf(" bd mol current %s --range 1-50 # Steps 1-50\n", stats.MoleculeID)
|
||||
fmt.Printf(" bd mol progress %s # Efficient progress summary\n", stats.MoleculeID)
|
||||
}
|
||||
|
||||
func init() {
|
||||
molCurrentCmd.Flags().String("for", "", "Show molecules for a specific agent/assignee")
|
||||
molCurrentCmd.Flags().Int("limit", 0, "Maximum number of steps to display (0 = auto, use 'all' threshold)")
|
||||
molCurrentCmd.Flags().String("range", "", "Display specific step range (e.g., '1-50', '100-150')")
|
||||
molCmd.AddCommand(molCurrentCmd)
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user