bd daemon sync: 2026-01-11 20:41:20

.beads/issues.jsonl

@@ -1280,7 +1280,7 @@
 {"id":"bd-hv01","title":"Deletions not propagated across multi-workspace sync","description":"## Problem\n\nWhen working with multiple beads workspaces (clones) sharing the same git remote, deleted issues keep coming back.\n\n## Reproduction\n\n1. Clone A deletes issue `bd-xyz` via `bd delete bd-xyz --force`\n2. Clone A daemon syncs and pushes to GitHub\n3. Clone B still has `bd-xyz` in its database\n4. Clone B daemon exports and pushes its JSONL\n5. Clone A pulls and imports → `bd-xyz` comes back!\n\n## Root Cause\n\n**No deletion tracking mechanism.** The system has no way to distinguish between:\n- \"Issue doesn't exist in JSONL because it was deleted\" \n- \"Issue doesn't exist in JSONL because the export is stale\"\n\nImport treats missing issues as \"not in this export\" rather than \"explicitly deleted.\"\n\n## Solution Options\n\n1. **Tombstone records** - Keep deleted issues in JSONL with `\"status\":\"deleted\"` or `\"deleted_at\"` field\n2. **Deletion log** - Separate `.beads/deletions.jsonl` file tracking all deleted IDs\n3. **Three-way merge** - Import compares: DB state, old JSONL, new JSONL\n4. **Manual conflict resolution** - Detect resurrection and prompt user\n\n## Related\n\n- Similar to resurrection logic for orphaned children (bd-cc4f)\n- beads-merge tool handles this better with 3-way merge","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-11-05T18:34:24.094474-08:00","updated_at":"2025-11-06T18:19:16.233949-08:00","closed_at":"2025-11-06T17:52:24.860716-08:00","dependencies":[{"issue_id":"bd-hv01","depends_on_id":"bd-qqvw","type":"blocks","created_at":"2025-11-05T18:42:35.485002-08:00","created_by":"daemon"}]}
 {"id":"bd-hv0zl","title":"Session ended: gt-gastown-crew-george","status":"closed","priority":2,"issue_type":"event","created_at":"2026-01-07T23:35:29.446162-08:00","created_by":"beads/refinery","updated_at":"2026-01-09T21:15:40.684842-08:00","closed_at":"2026-01-09T21:15:40.684842-08:00","close_reason":"Stale session ended events"}
 {"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-hvwnb","title":"gt prime: detectSessionState duplicates checkSlungWork logic","description":"detectSessionState() (lines 1775-1799) duplicates the hooked bead detection logic from checkSlungWork() (lines 1035-1066). This could lead to drift if one is updated without the other.\n\nOptions:\n1. Extract shared helper function for hooked bead detection\n2. Have detectSessionState call into checkSlungWork (would need refactoring)\n3. Accept duplication with comment noting the relationship\n\nLocation: gastown/mayor/rig/internal/cmd/prime.go","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T00:45:57.553336-08:00","created_by":"mayor","updated_at":"2026-01-10T17:19:10.040103-08:00"}
+{"id":"bd-hvwnb","title":"gt prime: detectSessionState duplicates checkSlungWork logic","description":"detectSessionState() (lines 1775-1799) duplicates the hooked bead detection logic from checkSlungWork() (lines 1035-1066). This could lead to drift if one is updated without the other.\n\nOptions:\n1. Extract shared helper function for hooked bead detection\n2. Have detectSessionState call into checkSlungWork (would need refactoring)\n3. Accept duplication with comment noting the relationship\n\nLocation: gastown/mayor/rig/internal/cmd/prime.go","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-10T00:45:57.553336-08:00","created_by":"mayor","updated_at":"2026-01-11T20:41:19.75541-08:00","closed_at":"2026-01-11T20:41:19.75541-08:00","close_reason":"Won't fix - minor duplication between checkSlungWork and detectSessionState. Low drift risk since both in same package. Not worth the churn."}
 {"id":"bd-hw1g","title":"Merge: quartz-mjxey2w1","description":"branch: polecat/quartz-mjxey2w1\ntarget: main\nsource_issue: quartz-mjxey2w1\nrig: beads\nagent_bead: bd-beads-polecat-quartz","status":"closed","priority":2,"issue_type":"merge-request","created_at":"2026-01-02T14:00:55.648449-08:00","created_by":"beads/polecats/quartz","updated_at":"2026-01-02T17:14:49.305672-08:00","closed_at":"2026-01-02T17:14:49.305672-08:00","close_reason":"Orphaned MR - quartz stopped (design doc), branch never pushed"}
 {"id":"bd-hw3c","title":"Fix GH #227: bd edit broken pipe errors","description":"bd edit command gets \"broken pipe\" errors when using daemon mode because editing can take minutes and the daemon connection times out.\n\nSolution: Force bd edit to always use direct mode (--no-daemon) since it's human-only and interactive.\n\nFixed by checking cmd.Name() == \"edit\" in main.go PersistentPreRun and setting noDaemon = true.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-11-05T14:36:04.289431-08:00","updated_at":"2025-11-05T14:36:08.103964-08:00","closed_at":"2025-11-05T14:36:08.103964-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"}]}