bd daemon sync: 2026-01-11 21:58:30

.beads/issues.jsonl

@@ -2074,6 +2074,7 @@
 {"id":"bd-v9kd2","title":"Session ended: gt-beads-witness","status":"closed","priority":2,"issue_type":"event","created_at":"2026-01-08T18:22:02.116594-08:00","created_by":"beads/witness","updated_at":"2026-01-08T18:22:02.153947-08:00","closed_at":"2026-01-08T18:22:02.153947-08:00","close_reason":"auto-closed session event"}
 {"id":"bd-vavh","title":"Fix row iterator resource leak in recursive dependency queries","description":"Critical resource leak in findAllDependentsRecursive() where rows.Close() is called AFTER early return on error, never executing.\n\nLocation: internal/storage/sqlite/sqlite.go:1131-1136\n\nProblem: \n- rows.Close() placed after return statement\n- On scan error, iterator never closed\n- Can exhaust SQLite connections under moderate load\n\nFix: Move defer rows.Close() to execute on all code paths\n\nImpact: Connection exhaustion during dependency traversal","status":"closed","priority":0,"issue_type":"bug","created_at":"2025-11-16T14:50:55.881698-08:00","updated_at":"2025-11-16T15:03:55.009607-08:00","closed_at":"2025-11-16T15:03:55.009607-08:00"}
 {"id":"bd-vcec","title":"postinstall fails on Windows: zip locked by Defender (GH#889)","description":"npm install fails on Windows because the zip file is locked when Expand-Archive runs. Fixed by adding retry loop with exponential backoff.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-04T12:26:43.264589-08:00","created_by":"beads/crew/grip","updated_at":"2026-01-04T12:27:15.417741-08:00","closed_at":"2026-01-04T12:27:15.417741-08:00","close_reason":"Fixed in 1a87d96d - added retry loop with exponential backoff"}
+{"id":"bd-vcfy3","title":"Session ended: gt-beads-refinery","status":"closed","priority":2,"issue_type":"event","owner":"steve.yegge@gmail.com","created_at":"2026-01-11T21:58:29.862877-08:00","created_by":"beads/refinery","updated_at":"2026-01-11T21:58:29.928397-08:00","closed_at":"2026-01-11T21:58:29.928397-08:00","close_reason":"auto-closed session cost wisp","ephemeral":true}
 {"id":"bd-vcg5","title":"Daemon crash recovery: panic handler + socket cleanup","description":"Improve daemon cleanup on unexpected exit:\n1. Add top-level recover() in runDaemonLoop to capture panics\n2. Write daemon-error file with stack trace on panic\n3. Prefer return over os.Exit where possible (so defers run)\n4. In stopDaemon forced-kill path, also remove stale socket if present\n\nThis ensures better diagnostics and cleaner state after crashes.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-07T16:42:12.733219-08:00","updated_at":"2025-11-07T22:07:17.347728-08:00","closed_at":"2025-11-07T21:17:15.94117-08:00","dependencies":[{"issue_id":"bd-vcg5","depends_on_id":"bd-ndyz","type":"discovered-from","created_at":"2025-11-07T16:42:12.733889-08:00","created_by":"daemon"}]}
 {"id":"bd-vckm","title":"Improve sync branch divergence recovery UX","description":"When the sync branch diverges significantly from remote (e.g., 89 local vs 36 remote commits), bd sync fails with a confusing rebase conflict error.\n\n**Current behavior:**\n```\nError committing to sync branch: failed to push from worktree: push failed and recovery rebase also failed\nerror: could not apply 8712f35... bd sync: 2025-12-13 07:30:04\nCONFLICT (content): Merge conflict in .beads/issues.jsonl\n```\n\nUser is left in a broken state with no clear recovery path.\n\n**Expected behavior:**\n1. Detect significant divergence before attempting sync\n2. Offer options: 'Sync branch diverged. Choose: (1) Reset to remote (2) Force push local (3) Manual merge'\n3. Provide clear recovery commands if automatic recovery fails\n\n**Context:** This happened after multiple clones synced different states. The workaround was manually resetting the sync branch worktree to remote.","status":"closed","priority":3,"issue_type":"feature","created_at":"2025-12-15T17:29:01.803478-08:00","updated_at":"2025-12-16T01:06:31.174908-08:00","closed_at":"2025-12-16T01:04:45.251662-08:00"}
 {"id":"bd-vd8e","title":"Detect uncommitted JSONL changes before sync operations","description":"Part of GH#885 fix: pre-flight safety check.\n\nAdd detection at sync start:\n1. Check if .beads/issues.jsonl has uncommitted changes in git\n2. If so, this indicates a previous sync failed after export but before commit\n3. Force a fresh export cycle to reconcile state\n\nImplementation:\n- Add gitHasUnstagedBeadsChanges() helper\n- Call in sync pre-flight checks (sync.go ~line 159)\n- If detected, warn user and force re-export\n\nThis catches the failure mode early before it compounds.","status":"closed","priority":1,"issue_type":"task","assignee":"beads/crew/fang","created_at":"2026-01-04T13:53:24.808788-08:00","created_by":"beads/crew/emma","updated_at":"2026-01-04T15:10:56.883507-08:00","closed_at":"2026-01-04T15:10:56.883507-08:00","close_reason":"Implemented: gitHasUncommittedBeadsChanges() helper + pre-flight check in sync.go","dependencies":[{"issue_id":"bd-vd8e","depends_on_id":"bd-pnx2","type":"parent-child","created_at":"2026-01-04T13:53:55.823237-08:00","created_by":"beads/crew/emma"}]}