johno/beads
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bd sync: 2025-12-28 22:36:53

Browse Source
This commit is contained in:
Steve Yegge
2025-12-28 22:36:53 -08:00
parent 8e746ed9ec
commit 4a6d942fad
1 changed files with 10 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
.beads/issues.jsonl
View File

@@ -288,6 +288,7 @@
{"id":"bd-d73u","title":"Re: Thread Test 2","description":"Great! Thread is working well.","status":"tombstone","priority":2,"issue_type":"message","created_at":"2025-12-16T18:21:46.655093-08:00","updated_at":"2025-12-17T16:11:17.070763-08:00","dependencies":[{"issue_id":"bd-d73u","depends_on_id":"bd-vpan","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-d9mu","title":"Cross-rig external dependency support","description":"Support dependencies on issues in other rigs/repos.\n\n## Use Case\n\nGas Town issues often depend on Beads issues (and vice versa). Currently we use labels like `external:beads/bd-xxx` as documentation, but:\n- `bd blocked` doesn't recognize external deps\n- `bd ready` doesn't filter them out\n- No way to query cross-rig status\n\n## Proposed UX\n\n### Adding external deps\n```bash\n# New syntax for bd dep add\nbd dep add gt-a07f external:beads:bd-kwjh\n\n# Or maybe cleaner\nbd dep add gt-a07f --external beads:bd-kwjh\n```\n\n### Showing blocked status\n```bash\nbd blocked\n# → gt-a07f blocked by external:beads:bd-kwjh (unverified)\n\n# With optional cross-rig query\nbd blocked --resolve-external\n# → gt-a07f blocked by external:beads:bd-kwjh (closed) ← unblocked!\n```\n\n### Storage\nCould use:\n- Special dependency type: `type: external`\n- Label convention: `external:rig:id`\n- New field: `external_deps: [\"beads:bd-kwjh\"]`\n\n## Implementation Notes\n\nCross-rig queries would need:\n- Known rig locations (config or discovery)\n- Read-only beads access to external rigs\n- Caching to avoid repeated queries\n\nFor MVP, just recognizing external deps and marking them as 'unverified' blockers would be valuable.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-22T02:27:23.892706-08:00","updated_at":"2025-12-22T22:32:49.261551-08:00","closed_at":"2025-12-22T22:32:49.261551-08:00","close_reason":"Superseded: Cross-rig external dependency support was fully implemented through child issues: bd-om4a (external: prefix syntax), bd-zmmy (bd ready resolution), bd-396j (bd blocked filtering), bd-66w1 (external_projects config), bd-vks2 (dep tree display), bd-mv6h (test coverage). External deps are auto-resolved when external_projects config is set. The --resolve-external flag is not needed."}
{"id":"bd-de6","title":"Fix FindBeadsDir to prioritize main repo .beads for worktrees","description":"The FindBeadsDir function should prioritize finding .beads in the main repository root when accessed from a worktree, rather than finding worktree-local .beads directories. This ensures proper sharing of the database across all worktrees.","status":"closed","priority":2,"issue_type":"bug","assignee":"beads/golf","created_at":"2025-12-07T16:48:36.883117467-07:00","updated_at":"2025-12-23T22:33:23.795459-08:00","closed_at":"2025-12-23T22:33:23.795459-08:00","close_reason":"Already implemented - FindBeadsDir prioritizes main repo .beads via IsWorktree() and GetMainRepoRoot(). All tests pass."}
{"id":"bd-desl","title":"Test hooked status","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-28T22:24:24.647682-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-28T22:30:38.057696-08:00","closed_at":"2025-12-28T22:30:38.057696-08:00","close_reason":"Test issue for hooked status - can be deleted"}
{"id":"bd-dhza","title":"Reduce global state in cmd/bd/main.go (25+ variables)","description":"Code health review found main.go has 25+ global variables (lines 57-112):\n\n- dbPath, actor, store, jsonOutput, daemonClient, noDaemon\n- rootCtx, rootCancel, autoFlushEnabled\n- isDirty (marked 'USED BY LEGACY CODE')\n- needsFullExport (marked 'USED BY LEGACY CODE')\n- flushTimer (marked 'DEPRECATED')\n- flushMutex, storeMutex, storeActive\n- flushFailureCount, lastFlushError, flushManager\n- skipFinalFlush, autoImportEnabled\n- versionUpgradeDetected, previousVersion, upgradeAcknowledged\n\nImpact:\n- Hard to test individual commands\n- Race conditions possible\n- State leakage between commands\n\nFix: Move toward dependency injection. Remove deprecated variables. Consider cmd/bd/internal package.","notes":"COMPLETED: Migration of legacy flush state to FlushManager. The main work (isDirty, needsFullExport, flushTimer) moved to local vars in FlushManager.run() lines 170-173. This fixes the race conditions. Remaining globals are: Cobra flag bindings (standard), runtime state (store, daemonClient - structural), store coordination (storeActive/storeMutex). Future: move error tracking to FlushManager, create cmd/bd/internal for encapsulation.","status":"closed","priority":3,"issue_type":"task","assignee":"beads/kilo","created_at":"2025-12-16T18:17:29.643293-08:00","updated_at":"2025-12-23T22:36:09.600594-08:00","closed_at":"2025-12-23T22:36:09.600594-08:00","close_reason":"Legacy flush globals (isDirty, needsFullExport, flushTimer) already migrated to FlushManager local vars. Race conditions fixed. Remaining globals are Cobra flags (standard) or structural (store, daemonClient). Future work filed separately if needed."}
{"id":"bd-djhk","title":"Test agent with fields","status":"closed","priority":2,"issue_type":"agent","created_at":"2025-12-27T23:44:08.97791-08:00","created_by":"mayor","updated_at":"2025-12-27T23:44:15.275899-08:00","closed_at":"2025-12-27T23:44:15.275899-08:00","close_reason":"Test bead"}
{"id":"bd-do8e","title":"Consolidate migrate-* commands under bd migrate","description":"## Task\nMove standalone migrate commands under `bd migrate` parent:\n- `bd migrate-hash-ids` → `bd migrate hash-ids`\n- `bd migrate-issues` → `bd migrate issues`\n- `bd migrate-sync` → `bd migrate sync`\n- `bd migrate-tombstones` → `bd migrate tombstones`\n\n## Implementation\n\n### 1. Update migrate.go\nAdd subcommands to migrateCmd:\n```go\nfunc init() {\n migrateCmd.AddCommand(migrateHashIDsCmd)\n migrateCmd.AddCommand(migrateIssuesCmd)\n migrateCmd.AddCommand(migrateSyncCmd)\n migrateCmd.AddCommand(migrateTombstonesCmd)\n}\n```\n\n### 2. Update each migrate_*.go file\n- Change `Use:` from `migrate-foo` to `foo`\n- Remove `rootCmd.AddCommand()` from init()\n\n### 3. Create hidden aliases for backwards compatibility\nIn main.go, add hidden top-level commands that forward to subcommands.\n\n### 4. Update docs\n- docs/DELETIONS.md - references `bd migrate-tombstones`\n- docs/CLI_REFERENCE.md - migration section\n\n## Files to modify\n- cmd/bd/migrate.go\n- cmd/bd/migrate_hash_ids.go \n- cmd/bd/migrate_issues.go\n- cmd/bd/migrate_sync.go\n- cmd/bd/migrate_tombstones.go\n- cmd/bd/main.go (aliases)\n","status":"closed","priority":2,"issue_type":"task","assignee":"quartz","created_at":"2025-12-27T15:10:41.618026-08:00","created_by":"mayor","updated_at":"2025-12-27T16:01:32.021299-08:00","closed_at":"2025-12-27T16:01:32.021299-08:00","close_reason":"Consolidated migrate-* commands under bd migrate parent with backwards-compat aliases","pinned":true}
@@ -503,7 +504,7 @@
{"id":"bd-n3v","title":"Error committing to sync branch: failed to create worktree","description":"\u003e bd sync --no-daemon\n→ Exporting pending changes to JSONL...\n→ Committing changes to sync branch 'beads-sync'...\nError committing to sync branch: failed to create worktree: failed to create worktree parent directory: mkdir /var/home/matt/dev/beads/fix-ci/.git: not a directory","notes":"**Problem Diagnosed**: The `bd sync` command was failing with \"mkdir /var/home/matt/dev/beads/fix-ci/.git: not a directory\" because it was being executed from the wrong directory.\n\n**Root Cause**: The command was run from `/var/home/matt/dev/beads` (where the `fix-ci` worktree exists) instead of the main repository directory `/var/home/matt/dev/beads/main`. Since `fix-ci` is a git worktree with a `.git` file (not directory), the worktree creation logic failed when trying to create `\u003ccurrent_dir\u003e/.git/beads-worktrees/\u003cbranch\u003e`.\n\n**Solution Verified**: Execute `bd sync` from the main repository directory:\n```bash\ncd main \u0026\u0026 bd sync --dry-run\n```\n","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-05T15:25:24.514998248-07:00","updated_at":"2025-12-24T00:25:13.040406-08:00","closed_at":"2025-12-24T00:25:13.040406-08:00","close_reason":"Fixed in PR #641 (commit 81aa3016). The getBeadsWorktreePath function now uses git rev-parse --git-common-dir to correctly find the shared git directory, ensuring beads worktrees are created in the correct location regardless of repository structure (regular repos, worktrees, bare repos)."}
{"id":"bd-n4td","title":"Add warning when staleness check errors","description":"## Problem\n\nWhen ensureDatabaseFresh() calls CheckStaleness() and it errors (corrupted metadata, permission issues, etc.), we silently proceed with potentially stale data.\n\n**Location:** cmd/bd/staleness.go:27-32\n\n**Scenarios:**\n- Corrupted metadata table\n- Database locked by another process \n- Permission issues reading JSONL file\n- Invalid last_import_time format in DB\n\n## Current Code\n\n```go\nisStale, err := autoimport.CheckStaleness(ctx, store, dbPath)\nif err \\!= nil {\n // If we can't determine staleness, allow operation to proceed\n // (better to show potentially stale data than block user)\n return nil\n}\n```\n\n## Fix\n\n```go\nisStale, err := autoimport.CheckStaleness(ctx, store, dbPath)\nif err \\!= nil {\n fmt.Fprintf(os.Stderr, \"Warning: Could not verify database freshness: %v\\n\", err)\n fmt.Fprintf(os.Stderr, \"Proceeding anyway. Data may be stale.\\n\\n\")\n return nil\n}\n```\n\n## Impact\nMedium - users should know when staleness check fails\n\n## Effort\nEasy - 5 minutes","status":"tombstone","priority":2,"issue_type":"bug","created_at":"2025-11-20T20:16:34.889997-05:00","updated_at":"2025-12-25T01:21:01.952723-08:00","dependencies":[{"issue_id":"bd-n4td","depends_on_id":"bd-2q6d","type":"blocks","created_at":"2025-11-20T20:18:20.154723-05:00","created_by":"stevey","metadata":"{}"}],"deleted_at":"2025-12-25T01:21:01.952723-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"bug"}
{"id":"bd-n5ug","title":"Merge: bd-au0.7","description":"branch: polecat/dementus\ntarget: main\nsource_issue: bd-au0.7\nrig: beads","status":"closed","priority":1,"issue_type":"merge-request","created_at":"2025-12-23T20:43:36.024341-08:00","updated_at":"2025-12-23T21:21:57.692158-08:00","closed_at":"2025-12-23T21:21:57.692158-08:00","close_reason":"stale - no code pushed"}
{"id":"bd-n6fm","title":"witness Handoff","status":"pinned","priority":2,"issue_type":"task","created_at":"2025-12-23T04:35:02.675024-08:00","updated_at":"2025-12-24T17:38:31.554705-08:00"}
{"id":"bd-n6fm","title":"witness Handoff","status":"hooked","priority":2,"issue_type":"task","created_at":"2025-12-23T04:35:02.675024-08:00","updated_at":"2025-12-24T17:38:31.554705-08:00"}
{"id":"bd-n777","title":"Timer beads for scheduled agent callbacks","description":"## Problem\n\nAgents frequently need to wait for external events (CI completion, PR reviews, artifact builds) but have no good mechanism:\n- `sleep N` blocks and is unreliable (often times out at 8+ minutes)\n- Polling wastes context and is easy to forget\n- No way to survive session restarts\n\n## Proposal: Timer Beads\n\nA new bead type or field that represents a scheduled callback:\n\n### Creating timers\n```bash\nbd timer create --in 30s --callback \"Check CI run 12345\" --issue bd-xyz\nbd timer create --at \"2025-12-20T08:00:00\" --callback \"Morning standup\"\nbd timer create --in 5m --on-expire \"tmux send-keys -t dave 'bd show bd-xyz'\"\n```\n\n### Timer storage\n- Store in beads (survives restarts)\n- Fields: `expires_at`, `callback_description`, `on_expire_command`, `linked_issue`\n- Status: pending, fired, cancelled\n\n### Deacon integration\nThe Deacon daemon monitors timer beads:\n1. Wakes on next timer expiry\n2. Executes `on_expire` command (e.g., tmux send-keys to interrupt agent)\n3. Marks timer as fired\n4. Optionally updates linked issue\n\n### Use cases\n- CI monitoring: \"ping me when build completes\"\n- PR reviews: \"check back in 1 hour\"\n- Scheduled tasks: \"remind me at EOD to sync\"\n- Blocking waits: agent registers callback instead of sleeping\n\n## Acceptance criteria\n- [ ] Timer bead type or field design\n- [ ] `bd timer create/list/cancel` commands\n- [ ] Deacon timer monitoring loop\n- [ ] tmux integration for agent interrupts\n- [ ] Survives daemon restarts","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-19T23:05:33.051861-08:00","updated_at":"2025-12-21T17:19:48.087482-08:00","closed_at":"2025-12-21T17:19:48.087482-08:00","close_reason":"Will not implement - Gas Town uses a different approach for timed events"}
{"id":"bd-n97g","title":"bump-version.sh should detect pre-staged release notes","description":"When running the release workflow, I staged CHANGELOG.md and info.go changes before running bump-version.sh. The script:\n\n1. Warned about uncommitted changes (correct)\n2. Required stash/pop to proceed\n3. After pop, the [Unreleased] header wasn't converted to version/date\n\nThe script could be smarter:\n- Detect if staged changes are to CHANGELOG.md/info.go (expected for releases)\n- Or provide a --allow-staged flag\n- Or at minimum, re-apply the [Unreleased] → [X.Y.Z] transformation after detecting manual edits\n\nWorkaround: manually edit [Unreleased] to [0.39.1] - 2025-12-27 after stash pop.","status":"closed","priority":3,"issue_type":"bug","created_at":"2025-12-27T22:51:23.239642-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-27T23:36:47.949197-08:00","closed_at":"2025-12-27T23:36:47.949197-08:00","close_reason":"Added --allow-staged flag to detect pre-staged CHANGELOG.md/info.go and include them in auto-commit"}
{"id":"bd-ncwo","title":"Ghost resurrection: remote status:closed wins during git merge","description":"During bd sync, the 3-way git merge sometimes keeps remote's status:closed instead of local's status:tombstone. This causes ghost issues to resurrect even when tombstones exist.\n\nRoot cause: Git 3-way merge doesn't understand tombstone semantics. If base had closed, local changed to tombstone, and remote has closed, git might keep remote's version.\n\nThe early tombstone check in importer.go only prevents CREATION when tombstones exist in DB. But if applyDeletionsFromMerge hard-deletes the tombstones before import runs (because they're not in the merged result), the check doesn't help.\n\nPotential fixes:\n1. Make tombstones 'win' in the beads merge driver (internal/merge/merge.go)\n2. Don't hard-delete tombstones in applyDeletionsFromMerge if they're in the DB\n3. Export tombstones to a separate file that's not subject to merge\n\nGhost issues: bd-cb64c226.*, bd-cbed9619.*","status":"tombstone","priority":1,"issue_type":"bug","created_at":"2025-12-16T22:01:03.56423-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":"bug"}
@@ -529,7 +530,7 @@
{"id":"bd-o9o","title":"Exclude pinned issues from bd ready","description":"Update bd ready to exclude pinned issues. Pinned issues are context markers, not work items, and should never appear in the ready-to-work list.","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-18T23:33:41.979073-08:00","updated_at":"2025-12-21T11:29:41.190567-08:00","closed_at":"2025-12-21T11:29:41.190567-08:00","close_reason":"Already implemented in SQLite (line 18). Added memory storage exclusion for completeness.","dependencies":[{"issue_id":"bd-o9o","depends_on_id":"bd-0vg","type":"blocks","created_at":"2025-12-18T23:33:56.392931-08:00","created_by":"daemon"},{"issue_id":"bd-o9o","depends_on_id":"bd-7h5","type":"blocks","created_at":"2025-12-18T23:34:07.612655-08:00","created_by":"daemon"}]}
{"id":"bd-obep","title":"Spawn-time bonding: --attach flag","description":"Add --attach flag to bd mol spawn for on-the-fly composition.\n\nCOMMAND: bd mol spawn proto-feature --attach proto-docs --attach proto-testing\n\nBEHAVIOR:\n- Spawn the primary proto as normal\n- For each --attach: spawn that proto and wire to primary\n- Attachments become children of primary's root epic\n- Dependencies wired based on bond type (default: sequential)\n\nFLAGS:\n- --attach PROTO: Attach a proto (can repeat)\n- --attach-type TYPE: sequential (default) or parallel for all attachments\n- --after ISSUE: Attachment point for attached protos\n\nVARIABLE HANDLING:\n- All attached protos share variable namespace\n- Warn on variable name conflicts\n- All --var flags apply to all protos","notes":"DESIGN NOTE: This is syntactic sugar. Equivalent to:\n bd mol spawn proto-A\n bd mol bond $new_epic_id proto-B\n \nKeeping as separate task because it's a common UX pattern worth optimizing.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-21T00:59:06.178092-08:00","updated_at":"2025-12-21T10:42:50.554816-08:00","closed_at":"2025-12-21T10:42:50.554816-08:00","close_reason":"Implemented --attach and --attach-type flags for bd mol spawn. Fixed pre-existing bug where bondProtoMol and bondMolMol tried to add duplicate dependencies (UNIQUE constraint). Sequential bonds now use blocks type, parallel/conditional use parent-child.","dependencies":[{"issue_id":"bd-obep","depends_on_id":"bd-o5xe","type":"parent-child","created_at":"2025-12-21T00:59:51.368491-08:00","created_by":"daemon"},{"issue_id":"bd-obep","depends_on_id":"bd-o91r","type":"blocks","created_at":"2025-12-21T00:59:51.733369-08:00","created_by":"daemon"}]}
{"id":"bd-of2p","title":"Improve version bump molecule with missing steps","description":"During v0.32.1 release, discovered missing steps in the release molecule:\n\n**Missing from molecule:**\n1. Rebuild ~/go/bin/bd (only did ~/.local/bin/bd)\n2. Install beads-mcp from local source: `uv tool install --reinstall ./integrations/beads-mcp`\n3. Restart daemons with `bd daemons killall`\n4. (Optional) Publish beads-mcp to PyPI\n\n**Current molecule steps (bd-6s61):**\n1. Update CHANGELOG.md\n2. Update info.go versionChanges \n3. Run bump-version.sh\n4. Run tests and linting\n5. Update local installation\n6. Commit and push release\n7. Wait for CI\n8. Verify release artifacts\n\n**Proposed additions:**\n- After \"Update local installation\": rebuild BOTH ~/.local/bin/bd AND ~/go/bin/bd\n- Add: \"Install beads-mcp from source\" step\n- Add: \"Restart daemons\" step\n- Add: \"Verify all versions match\" step that checks all artifacts\n\n**Also learned:**\n- Must run from mayor/rig to avoid git conflicts with bd sync (already documented in bump-version.sh)","notes":"CORRECTION: npm publishing IS automated and working!\n\n**Package naming:**\n- OLD: `beads` (npm) - deprecated, stuck at 0.2.1\n- CURRENT: `@beads/bd` (npm) - scoped package, auto-published by CI\n\n**How it works:**\n- CI uses OIDC trusted publishing (no token needed)\n- Workflow: .github/workflows/release.yml → publish-npm job\n- Permissions: `id-token: write` enables GitHub OIDC\n- To install: `npm install -g @beads/bd` (not `npm install beads`)\n\n**All publishing is automated on tag push:**\n1. GitHub Release - goreleaser ✓\n2. PyPI - publish-pypi job ✓\n3. Homebrew - update-homebrew job ✓\n4. npm (@beads/bd) - publish-npm job ✓\n\n**Remaining molecule improvements (local steps only):**\n- Rebuild BOTH ~/.local/bin/bd AND ~/go/bin/bd\n- Install beads-mcp from source: `uv tool install --reinstall ./integrations/beads-mcp`\n- Restart daemons: `bd daemons killall`\n- Run from mayor/rig to avoid git conflicts with bd sync\n- Final verification step to check all local versions match","status":"closed","priority":2,"issue_type":"task","assignee":"beads/dave","created_at":"2025-12-20T22:09:11.845787-08:00","updated_at":"2025-12-22T16:01:18.199132-08:00","closed_at":"2025-12-22T16:01:18.199132-08:00","close_reason":"Implemented: Added --install (dual location), --mcp-local, --restart-daemons, and --all flags to bump-version.sh. Updated RELEASING.md with new flag documentation."}
{"id":"bd-ohil","title":"refinery Handoff","status":"pinned","priority":2,"issue_type":"task","created_at":"2025-12-23T04:35:07.488226-08:00","updated_at":"2025-12-24T17:38:31.483362-08:00"}
{"id":"bd-ohil","title":"refinery Handoff","status":"hooked","priority":2,"issue_type":"task","created_at":"2025-12-23T04:35:07.488226-08:00","updated_at":"2025-12-24T17:38:31.483362-08:00"}
{"id":"bd-ola6","title":"Implement transaction retry logic for SQLITE_BUSY","description":"BEGIN IMMEDIATE fails immediately on SQLITE_BUSY instead of retrying with exponential backoff.\n\nLocation: internal/storage/sqlite/sqlite.go:223-225\n\nProblem:\n- Under concurrent write load, BEGIN IMMEDIATE can fail with SQLITE_BUSY\n- Current implementation fails immediately instead of retrying\n- Results in spurious failures under normal concurrent usage\n\nSolution: Implement exponential backoff retry:\n- Retry up to N times (e.g., 5)\n- Backoff: 10ms, 20ms, 40ms, 80ms, 160ms\n- Check for context cancellation between retries\n- Only retry on SQLITE_BUSY/database locked errors\n\nImpact: Spurious failures under concurrent write load\n\nEffort: 3 hours","status":"closed","priority":1,"issue_type":"feature","created_at":"2025-11-16T14:51:31.247147-08:00","updated_at":"2025-12-21T21:39:23.071036-08:00","closed_at":"2025-12-21T21:39:23.071036-08:00","close_reason":"Already implemented: beginImmediateWithRetry in util.go provides exponential backoff (5 retries, 10ms→160ms) for SQLITE_BUSY errors, used by RunInTransaction. Tests in util_test.go verify behavior."}
{"id":"bd-om4a","title":"Support external: prefix in blocked_by field","description":"Allow blocked_by to include external project references:\n\n```bash\nbd update gt-xyz --blocked-by=\"external:beads:mol-run-assignee\"\n```\n\nSyntax: `external:\u003cproject\u003e:\u003ccapability\u003e`\n- project: name from external_projects config\n- capability: matches provides:\u003ccapability\u003e label in target project\n\nStorage: Store as-is in blocked_by array. Resolution happens at query time.\n\nPart of cross-project dependency system.\nSee: gastown/docs/cross-project-deps.md","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-21T22:37:29.725196-08:00","updated_at":"2025-12-21T23:07:48.127045-08:00","closed_at":"2025-12-21T23:07:48.127045-08:00","close_reason":"Implemented: bd dep add accepts external:project:capability syntax, stores as-is, shows in blocked output, updates blocked cache"}
{"id":"bd-omrf","title":"Merge: oast-1766978911452","description":"branch: polecat/Toast-1766978911452\ntarget: main\nsource_issue: oast-1766978911452\nrig: beads","status":"open","priority":2,"issue_type":"merge-request","created_at":"2025-12-28T19:51:11.183702-08:00","created_by":"beads/polecats/Toast","updated_at":"2025-12-28T19:51:11.183702-08:00"}
@@ -624,11 +625,11 @@
{"id":"bd-rupw","title":"Run bump-version.sh 0.30.7","description":"Run ./scripts/bump-version.sh 0.30.7 to update version in all files","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-19T22:56:48.649647-08:00","updated_at":"2025-12-19T22:57:31.512956-08:00","closed_at":"2025-12-19T22:57:31.512956-08:00","dependencies":[{"issue_id":"bd-rupw","depends_on_id":"bd-8pyn","type":"parent-child","created_at":"2025-12-19T22:56:48.653475-08:00","created_by":"stevey"}]}
{"id":"bd-rx6o","title":"Test Child Task","status":"tombstone","priority":2,"issue_type":"task","created_at":"2025-12-27T22:15:23.27506-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-27T22:16:35.925357-08:00","deleted_at":"2025-12-27T22:16:35.925357-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"task"}
{"id":"bd-rze6","title":"Digest: Release v0.34.0 @ 2025-12-22 12:16","description":"Released v0.34.0: wisp commands, chemistry UX, cross-project deps","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-22T12:16:53.033119-08:00","updated_at":"2025-12-22T12:16:53.033119-08:00","closed_at":"2025-12-22T12:16:53.033025-08:00","close_reason":"Squashed from wisp bd-25c (20 issues)"}
{"id":"bd-s00m","title":"Add 'hooked' status for GUPP work assignment","description":"## Summary\n\nSeparate the semantics of `pinned` (identity records) from work-on-hook (GUPP assignment).\n\n**Current problem:** `pinned` is overloaded to mean both:\n1. Agent identity beads (gt-mayor, gt-crew-gastown-max) - should never block\n2. Work attached to an agent's hook - should block until closed\n\nThe blocking logic excludes `pinned` from blocking, which means work on hooks doesn't block its dependents.\n\n## Semantic Split\n\n| Status | Meaning | Blocks dependents? |\n|--------|---------|-------------------|\n| `pinned` | Domain table / identity record (agents, roles) | No |\n| `hooked` | Work on an agent's hook (GUPP invoked) | Yes |\n\n**Terminology:**\n- **Pin** (verb): Establish a permanent identity record\n- **Hook** (verb): Attach work to an agent's hook\n- **Sling** (verb): The act of hooking work to an agent\n\n## Lifecycles\n\n**Molecule** (the work):\n open -\u003e hooked -\u003e closed\n\n**Persistent agent** (Mayor, Witness, Crew):\n idle \u003c-\u003e working (cycles)\nAgent bead stays pinned. Operational state derived from hook slot occupancy.\n\n**Polecat** (ephemeral worker):\n spawned-with-work -\u003e working -\u003e despawning\nPolecats never idle - spawned for one molecule, nuked after.\n\nThe `hooked` status belongs to the **molecule**, not the agent. Agent identity beads remain `pinned` throughout their existence.\n\n## in_progress vs hooked\n\nBoth remain valid statuses with different semantics:\n- `in_progress` = Soft claim, cooperative (humans juggling multiple issues)\n- `hooked` = Hard claim, GUPP-driven (molecule on agent's hook)\n\nGas Town molecules use `hooked`. Humans/non-Gas Town workflows may use `in_progress`.\n\n## Success Criteria\n\n1. `hooked` is a valid status in beads schema\n2. Blocking logic treats `hooked` as blocking (like `in_progress`)\n3. gt sling sets status=hooked on the molecule (not pinned)\n4. Existing pinned work items migrated to hooked where appropriate\n5. Agent/role beads remain pinned and non-blocking","status":"open","priority":1,"issue_type":"epic","created_at":"2025-12-28T22:16:37.66048-08:00","created_by":"stevey","updated_at":"2025-12-28T22:19:56.640166-08:00"}
{"id":"bd-s00m.1","title":"Schema: Add 'hooked' as valid status","description":"Add 'hooked' to the valid status enum in the beads schema.\n\n## Files to Update\n\n1. `internal/types/types.go` - Add StatusHooked constant\n2. `internal/storage/sqlite/schema.go` - Add 'hooked' to CHECK constraint\n3. `internal/storage/sqlite/migrations/` - New migration to alter constraint\n\n## Status Values After Change\n\n- open\n- in_progress\n- blocked\n- deferred\n- hooked (NEW)\n- closed\n- pinned\n- tombstone\n\n## Validation\n\n- bd update \u003cid\u003e --status=hooked should work\n- bd list --status=hooked should filter correctly","status":"open","priority":1,"issue_type":"task","created_at":"2025-12-28T22:16:56.596014-08:00","created_by":"stevey","updated_at":"2025-12-28T22:16:56.596014-08:00","dependencies":[{"issue_id":"bd-s00m.1","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:16:56.596584-08:00","created_by":"daemon"}]}
{"id":"bd-s00m.2","title":"Blocking logic: Include 'hooked' in blocking statuses","description":"Update the blocked_cache.go SQL to treat 'hooked' as a blocking status.\n\n## Current Logic (line ~163)\n\n```sql\nblocker.status IN ('open', 'in_progress', 'blocked', 'deferred')\n```\n\n## Updated Logic\n\n```sql\nblocker.status IN ('open', 'in_progress', 'blocked', 'deferred', 'hooked')\n```\n\n## Files to Update\n\n- internal/storage/sqlite/blocked_cache.go\n\n## Test Cases\n\n1. Issue A (hooked) blocks Issue B → B should NOT appear in bd ready\n2. Issue A (pinned, type=agent) → B should appear in bd ready\n3. Issue A (hooked) closed → B should appear in bd ready","status":"open","priority":1,"issue_type":"task","created_at":"2025-12-28T22:16:56.809269-08:00","created_by":"stevey","updated_at":"2025-12-28T22:16:56.809269-08:00","dependencies":[{"issue_id":"bd-s00m.2","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:16:56.809716-08:00","created_by":"daemon"},{"issue_id":"bd-s00m.2","depends_on_id":"bd-s00m.1","type":"blocks","created_at":"2025-12-28T22:17:22.129513-08:00","created_by":"daemon"}]}
{"id":"bd-s00m.3","title":"UI: Style 'hooked' status in bd list output","description":"Add styling for 'hooked' status in bd list and bd show output.\n\n## Semantic\n\n'hooked' means actively being worked by an agent (GUPP). Should be visually prominent.\n\n## Suggested Styling\n\n- Color: Cyan or bright blue (active, in-flight)\n- Distinct from 'in_progress' (which is more passive/cooperative)\n\n## Files to Update\n\n- internal/ui/styles.go - Add case for 'hooked' status","status":"open","priority":1,"issue_type":"task","created_at":"2025-12-28T22:16:57.019828-08:00","created_by":"stevey","updated_at":"2025-12-28T22:16:57.019828-08:00","dependencies":[{"issue_id":"bd-s00m.3","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:16:57.020313-08:00","created_by":"daemon"},{"issue_id":"bd-s00m.3","depends_on_id":"bd-s00m.1","type":"blocks","created_at":"2025-12-28T22:17:22.148918-08:00","created_by":"daemon"}]}
{"id":"bd-s00m.4","title":"Migration: Convert pinned work items to hooked","description":"Migrate existing pinned beads that represent work-on-hook to use 'hooked' status.\n\n## Migration Logic\n\n```sql\nUPDATE issues \nSET status = 'hooked'\nWHERE status = 'pinned' \n AND issue_type NOT IN ('agent', 'role')\n```\n\n## What Stays Pinned\n\n- Agent identity beads (gt-mayor, gt-witness-gastown, etc.)\n- Role definition beads (gt-mayor-role, etc.)\n\n## What Becomes Hooked\n\n- Molecules on hooks (mol_type field set)\n- Regular issues/tasks that were pinned to hooks\n\n## Verification\n\nAfter migration:\n- bd list --status=pinned should only show agents/roles\n- bd list --status=hooked should show work on hooks","status":"open","priority":2,"issue_type":"task","created_at":"2025-12-28T22:17:13.872171-08:00","created_by":"stevey","updated_at":"2025-12-28T22:17:13.872171-08:00","dependencies":[{"issue_id":"bd-s00m.4","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:17:13.872786-08:00","created_by":"daemon"},{"issue_id":"bd-s00m.4","depends_on_id":"bd-s00m.1","type":"blocks","created_at":"2025-12-28T22:17:22.168228-08:00","created_by":"daemon"}]}
{"id":"bd-s00m","title":"Add 'hooked' status for GUPP work assignment","description":"## Summary\n\nSeparate the semantics of `pinned` (identity records) from work-on-hook (GUPP assignment).\n\n**Current problem:** `pinned` is overloaded to mean both:\n1. Agent identity beads (gt-mayor, gt-crew-gastown-max) - should never block\n2. Work attached to an agent's hook - should block until closed\n\nThe blocking logic excludes `pinned` from blocking, which means work on hooks doesn't block its dependents.\n\n## Semantic Split\n\n| Status | Meaning | Blocks dependents? |\n|--------|---------|-------------------|\n| `pinned` | Domain table / identity record (agents, roles) | No |\n| `hooked` | Work on an agent's hook (GUPP invoked) | Yes |\n\n**Terminology:**\n- **Pin** (verb): Establish a permanent identity record\n- **Hook** (verb): Attach work to an agent's hook\n- **Sling** (verb): The act of hooking work to an agent\n\n## Lifecycles\n\n**Molecule** (the work):\n open -\u003e hooked -\u003e closed\n\n**Persistent agent** (Mayor, Witness, Crew):\n idle \u003c-\u003e working (cycles)\nAgent bead stays pinned. Operational state derived from hook slot occupancy.\n\n**Polecat** (ephemeral worker):\n spawned-with-work -\u003e working -\u003e despawning\nPolecats never idle - spawned for one molecule, nuked after.\n\nThe `hooked` status belongs to the **molecule**, not the agent. Agent identity beads remain `pinned` throughout their existence.\n\n## in_progress vs hooked\n\nBoth remain valid statuses with different semantics:\n- `in_progress` = Soft claim, cooperative (humans juggling multiple issues)\n- `hooked` = Hard claim, GUPP-driven (molecule on agent's hook)\n\nGas Town molecules use `hooked`. Humans/non-Gas Town workflows may use `in_progress`.\n\n## Success Criteria\n\n1. `hooked` is a valid status in beads schema\n2. Blocking logic treats `hooked` as blocking (like `in_progress`)\n3. gt sling sets status=hooked on the molecule (not pinned)\n4. Existing pinned work items migrated to hooked where appropriate\n5. Agent/role beads remain pinned and non-blocking","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-12-28T22:16:37.66048-08:00","created_by":"stevey","updated_at":"2025-12-28T22:36:19.769137-08:00","closed_at":"2025-12-28T22:36:19.769137-08:00","close_reason":"All tasks complete: hooked status added to schema, blocking logic, UI, and migration created"}
{"id":"bd-s00m.1","title":"Schema: Add 'hooked' as valid status","description":"Add 'hooked' to the valid status enum in the beads schema.\n\n## Files to Update\n\n1. `internal/types/types.go` - Add StatusHooked constant\n2. `internal/storage/sqlite/schema.go` - Add 'hooked' to CHECK constraint\n3. `internal/storage/sqlite/migrations/` - New migration to alter constraint\n\n## Status Values After Change\n\n- open\n- in_progress\n- blocked\n- deferred\n- hooked (NEW)\n- closed\n- pinned\n- tombstone\n\n## Validation\n\n- bd update \u003cid\u003e --status=hooked should work\n- bd list --status=hooked should filter correctly","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-28T22:16:56.596014-08:00","created_by":"stevey","updated_at":"2025-12-28T22:30:39.09597-08:00","closed_at":"2025-12-28T22:30:39.09597-08:00","close_reason":"Added StatusHooked constant and IsValid() support","dependencies":[{"issue_id":"bd-s00m.1","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:16:56.596584-08:00","created_by":"daemon"}]}
{"id":"bd-s00m.2","title":"Blocking logic: Include 'hooked' in blocking statuses","description":"Update the blocked_cache.go SQL to treat 'hooked' as a blocking status.\n\n## Current Logic (line ~163)\n\n```sql\nblocker.status IN ('open', 'in_progress', 'blocked', 'deferred')\n```\n\n## Updated Logic\n\n```sql\nblocker.status IN ('open', 'in_progress', 'blocked', 'deferred', 'hooked')\n```\n\n## Files to Update\n\n- internal/storage/sqlite/blocked_cache.go\n\n## Test Cases\n\n1. Issue A (hooked) blocks Issue B → B should NOT appear in bd ready\n2. Issue A (pinned, type=agent) → B should appear in bd ready\n3. Issue A (hooked) closed → B should appear in bd ready","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-28T22:16:56.809269-08:00","created_by":"stevey","updated_at":"2025-12-28T22:32:27.742984-08:00","closed_at":"2025-12-28T22:32:27.742984-08:00","close_reason":"Added 'hooked' to all blocking status queries in sqlite, ready, events, compact, and memory storage","dependencies":[{"issue_id":"bd-s00m.2","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:16:56.809716-08:00","created_by":"daemon"},{"issue_id":"bd-s00m.2","depends_on_id":"bd-s00m.1","type":"blocks","created_at":"2025-12-28T22:17:22.129513-08:00","created_by":"daemon"}]}
{"id":"bd-s00m.3","title":"UI: Style 'hooked' status in bd list output","description":"Add styling for 'hooked' status in bd list and bd show output.\n\n## Semantic\n\n'hooked' means actively being worked by an agent (GUPP). Should be visually prominent.\n\n## Suggested Styling\n\n- Color: Cyan or bright blue (active, in-flight)\n- Distinct from 'in_progress' (which is more passive/cooperative)\n\n## Files to Update\n\n- internal/ui/styles.go - Add case for 'hooked' status","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-28T22:16:57.019828-08:00","created_by":"stevey","updated_at":"2025-12-28T22:34:31.132171-08:00","closed_at":"2025-12-28T22:34:31.132171-08:00","close_reason":"Added ColorStatusHooked (cyan) and StatusHookedStyle, updated RenderStatus()","dependencies":[{"issue_id":"bd-s00m.3","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:16:57.020313-08:00","created_by":"daemon"},{"issue_id":"bd-s00m.3","depends_on_id":"bd-s00m.1","type":"blocks","created_at":"2025-12-28T22:17:22.148918-08:00","created_by":"daemon"}]}
{"id":"bd-s00m.4","title":"Migration: Convert pinned work items to hooked","description":"Migrate existing pinned beads that represent work-on-hook to use 'hooked' status.\n\n## Migration Logic\n\n```sql\nUPDATE issues \nSET status = 'hooked'\nWHERE status = 'pinned' \n AND issue_type NOT IN ('agent', 'role')\n```\n\n## What Stays Pinned\n\n- Agent identity beads (gt-mayor, gt-witness-gastown, etc.)\n- Role definition beads (gt-mayor-role, etc.)\n\n## What Becomes Hooked\n\n- Molecules on hooks (mol_type field set)\n- Regular issues/tasks that were pinned to hooks\n\n## Verification\n\nAfter migration:\n- bd list --status=pinned should only show agents/roles\n- bd list --status=hooked should show work on hooks","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-28T22:17:13.872171-08:00","created_by":"stevey","updated_at":"2025-12-28T22:36:09.039612-08:00","closed_at":"2025-12-28T22:36:09.039612-08:00","close_reason":"Created migration 032_hooked_status_migration.go - converts non-agent/role pinned issues to hooked","dependencies":[{"issue_id":"bd-s00m.4","depends_on_id":"bd-s00m","type":"parent-child","created_at":"2025-12-28T22:17:13.872786-08:00","created_by":"daemon"},{"issue_id":"bd-s00m.4","depends_on_id":"bd-s00m.1","type":"blocks","created_at":"2025-12-28T22:17:22.168228-08:00","created_by":"daemon"}]}
{"id":"bd-s0qf","title":"GH#405: Fix prefix parsing with hyphens - multi-hyphen prefixes parsed incorrectly","description":"Fixed: ExtractIssuePrefix was falling back to first-hyphen for word-like suffixes, breaking multi-hyphen prefixes like 'hacker-news' and 'me-py-toolkit'.","status":"tombstone","priority":2,"issue_type":"bug","created_at":"2025-12-16T01:13:56.951359-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":"bug"}
{"id":"bd-s1pz","title":"Merge: bd-u2sc.4","description":"branch: polecat/Logger\ntarget: main\nsource_issue: bd-u2sc.4\nrig: beads","status":"closed","priority":3,"issue_type":"merge-request","created_at":"2025-12-23T13:45:52.412757-08:00","updated_at":"2025-12-23T19:12:08.356689-08:00","closed_at":"2025-12-23T19:12:08.356689-08:00","close_reason":"Stale merge-requests from orphaned polecat branches - refinery not processing"}
{"id":"bd-s2t","title":"wish: a 'continue' or similar cmd/flag which means alter last issue","description":"so many time I create an issue and then have another thought: 'oh, before I did X and it crashed there was ZZZ happening' or 'actually that is P4 not P2'. It would be nice if when `bd {cmd}` is used without a {title} or {id} it just adds or updates the most recently touched issue.","status":"open","priority":3,"issue_type":"task","created_at":"2025-12-08T06:46:37.529160416-07:00","updated_at":"2025-12-08T06:46:37.529160416-07:00"}
@@ -650,6 +651,7 @@
{"id":"bd-tcvh","title":"Test prefix beads","status":"tombstone","priority":2,"issue_type":"task","created_at":"2025-12-27T14:24:41.707092-08:00","created_by":"stevey","updated_at":"2025-12-27T14:24:50.421598-08:00","deleted_at":"2025-12-27T14:24:50.421598-08:00","deleted_by":"daemon","delete_reason":"delete","original_type":"task"}
{"id":"bd-tggf","title":"Code Health Review Dec 2025: Technical Debt Cleanup","description":"Epic grouping technical debt identified in the Dec 16, 2025 code health review.\n\n## Overall Health Grade: B (Solid foundation, needs cleanup)\n\n### P1 (High Priority):\n- bd-74w1: Consolidate duplicate path-finding utilities\n- [deleted:bd-b6xo]: Remove/fix ClearDirtyIssues() race condition\n- [deleted:bd-b3og]: Fix TestImportBugIntegration deadlock\n\n### P2 (Medium Priority):\n- bd-05a8: Split large files (doctor.go, sync.go)\n- bd-qioh: Standardize error handling patterns\n- bd-rgyd: Split queries.go (1586 lines)\n- bd-9g1z: Fix/remove TestFindJSONLPathDefault\n\n### P3 (Low Priority):\n- bd-ork0: Add comments to 30+ ignored errors\n- bd-4nqq: Remove dead test code in info_test.go\n- bd-dhza: Reduce global state in main.go\n\n## Key Areas:\n1. Code duplication in path utilities\n2. Large monolithic files (5 files \u003e1000 lines)\n3. Global state (25+ variables, 3 deprecated)\n4. Silent error suppression (30+ instances)\n5. Test gaps and dead test code\n6. Atomicity risks in batch operations","status":"open","priority":2,"issue_type":"epic","created_at":"2025-12-16T18:18:58.115507-08:00","updated_at":"2025-12-25T01:21:01.961139-08:00","dependencies":[{"issue_id":"bd-tggf","depends_on_id":"bd-74w1","type":"blocks","created_at":"2025-12-22T21:00:21.429274-08:00","created_by":"daemon"},{"issue_id":"bd-tggf","depends_on_id":"bd-05a8","type":"blocks","created_at":"2025-12-22T21:00:21.501589-08:00","created_by":"daemon"},{"issue_id":"bd-tggf","depends_on_id":"bd-9g1z","type":"blocks","created_at":"2025-12-22T21:00:21.571116-08:00","created_by":"daemon"},{"issue_id":"bd-tggf","depends_on_id":"bd-qioh","type":"blocks","created_at":"2025-12-22T21:00:21.640589-08:00","created_by":"daemon"},{"issue_id":"bd-tggf","depends_on_id":"bd-rgyd","type":"blocks","created_at":"2025-12-22T21:00:21.710912-08:00","created_by":"daemon"},{"issue_id":"bd-tggf","depends_on_id":"bd-4nqq","type":"blocks","created_at":"2025-12-22T21:00:21.781914-08:00","created_by":"daemon"},{"issue_id":"bd-tggf","depends_on_id":"bd-dhza","type":"blocks","created_at":"2025-12-22T21:00:21.852-08:00","created_by":"daemon"},{"issue_id":"bd-tggf","depends_on_id":"bd-ork0","type":"blocks","created_at":"2025-12-22T21:00:21.930168-08:00","created_by":"daemon"}]}
{"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","assignee":"beads/Compactor","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","close_reason":"Coverage improved from 17.3% to 81.8%, exceeding 70% target","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","close_reason":"Test issue for hooked styling"}
{"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","close_reason":"Installed bd 0.32.1","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-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-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"}
@@ -730,7 +732,7 @@
{"id":"bd-yuxq","title":"Code smell: 262 uses of interface{} reduce type safety","description":"Heavy use of interface{} across 92 files (262 occurrences) in:\n- RPC update arguments: updatesFromArgs() returns map[string]interface{}\n- JSON unmarshaling and formatting\n- Storage query helpers\n\n**Example in internal/rpc/server_issues_epics.go:45:**\n```go\nfunc updatesFromArgs(a UpdateArgs) map[string]interface{} {\n // Returns map with interface{} values - types must be asserted at use sites\n}\n```\n\n**Problem:**\n- Loss of type safety\n- Runtime type assertions required\n- Harder to catch errors at compile time\n\n**Acceptance Criteria:**\n- [ ] Define typed update structs for specific field groups\n- [ ] Use generics where possible (Go 1.18+)\n- [ ] Reduce interface{} count by at least 50%\n- [ ] Document expected types where interface{} remains necessary\n- [ ] Tests pass","status":"open","priority":3,"issue_type":"chore","created_at":"2025-12-28T19:00:01.896147-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-28T19:00:01.896147-08:00","dependencies":[{"issue_id":"bd-yuxq","depends_on_id":"bd-ox1o","type":"blocks","created_at":"2025-12-28T19:00:23.812412-08:00","created_by":"daemon"}]}
{"id":"bd-yx22","title":"Merge: bd-d28c","description":"branch: polecat/testcat\ntarget: main\nsource_issue: bd-d28c\nrig: beads","status":"closed","priority":1,"issue_type":"merge-request","created_at":"2025-12-23T21:33:15.490412-08:00","updated_at":"2025-12-23T21:36:38.584933-08:00","closed_at":"2025-12-23T21:36:38.584933-08:00","close_reason":"stale - code never pushed to remote"}
{"id":"bd-yy1h","title":"Witness Patrol","description":"Per-rig worker monitor patrol loop with progressive nudging.","status":"tombstone","priority":2,"issue_type":"molecule","created_at":"2025-12-26T13:08:21.271692-08:00","updated_at":"2025-12-27T00:10:54.178645-08:00","deleted_at":"2025-12-27T00:10:54.178645-08:00","deleted_by":"daemon","delete_reason":"delete","original_type":"molecule"}
{"id":"bd-z3rf","title":"dave Handoff","status":"pinned","priority":2,"issue_type":"task","created_at":"2025-12-23T04:33:42.874554-08:00","updated_at":"2025-12-26T13:08:21.874062-08:00"}
{"id":"bd-z3rf","title":"dave Handoff","status":"hooked","priority":2,"issue_type":"task","created_at":"2025-12-23T04:33:42.874554-08:00","updated_at":"2025-12-26T13:08:21.874062-08:00"}
{"id":"bd-z4f5","title":"--parent flag reports success but doesn't persist to JSONL","description":"The --parent flag for bd update reports success but the change doesn't persist.\n\nReported by: Mayor\nLocation: show.go:810-814 handles the logic\n\nSymptoms:\n- bd update \u003cid\u003e --parent=\u003cnew-parent\u003e returns success\n- But the parent change is not written to JSONL\n- Subsequent bd show reveals parent unchanged\n\nThis shipped in v0.39.1 as part of bd-cj2e (--parent flag for reparenting).\n\nInvestigation: Check the update path from show.go through to JSONL export. The RPC/daemon layer may be dropping the parent field, or the storage layer isn't persisting it.","status":"closed","priority":1,"issue_type":"bug","assignee":"dave","created_at":"2025-12-27T23:10:22.428136-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-27T23:27:45.716572-08:00","closed_at":"2025-12-27T23:27:45.716572-08:00","close_reason":"Cannot reproduce - --parent flag persists correctly to JSONL. Issue may have been transient during initial testing or daemon restart resolved it."}
{"id":"bd-z830","title":"Test child task","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-27T23:26:58.246573-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-27T23:27:40.451603-08:00","closed_at":"2025-12-27T23:27:40.451603-08:00","close_reason":"Test issues, cleanup","dependencies":[{"issue_id":"bd-z830","depends_on_id":"bd-fbl9","type":"parent-child","created_at":"2025-12-27T23:27:02.984294-08:00","created_by":"daemon"}]}
{"id":"bd-z86n","title":"Code Review: PR #551 - Persist close_reason to issues table","description":"Code review of PR #551 which fixes close_reason persistence bug.\n\n## Summary\nThe PR correctly fixes a bug where close_reason was only stored in the events table, not in the issues.close_reason column. This caused `bd show --json` to return empty close_reason.\n\n## What Was Fixed\n- ✅ CloseIssue now updates both close_reason and closed_at\n- ✅ ReOpenIssue clears both close_reason and closed_at\n- ✅ Comprehensive tests added for both storage and CLI layers\n- ✅ Clear documentation in queries.go about dual storage strategy\n\n## Quality Assessment\n✅ Tests cover both storage layer and CLI JSON output\n✅ Handles reopen case (clearing close_reason)\n✅ Good comments explaining dual-storage design\n✅ No known issues\n\n## Potential Followups\nSee linked issues for suggestions.","status":"open","priority":2,"issue_type":"task","created_at":"2025-12-14T14:25:06.887069-08:00","updated_at":"2025-12-14T14:25:06.887069-08:00"}