bd daemon sync: 2026-01-11 08:41:55

.beads/issues.jsonl

@@ -179,6 +179,7 @@
 {"id":"bd-2fs7","title":"Move pour/ephemeral under bd mol subcommand","description":"For consistency, bd pour and bd ephemeral should become bd mol pour and bd mol ephemeral:\n\nCurrent:\n  bd mol list                  # Available protos\n  bd mol show \u003cid\u003e             # Proto details\n  bd pour \u003cproto\u003e              # Create mol ← sticks out\n  bd ephemeral \u003cproto\u003e         # Create ephemeral ← sticks out  \n  bd mol bond \u003cproto\u003e \u003cparent\u003e # Attach to existing mol\n  bd mol squash \u003cid\u003e           # Condense to digest\n  bd mol burn \u003cid\u003e             # Discard\n\nProposed:\n  bd mol list\n  bd mol show \u003cid\u003e\n  bd mol pour \u003cproto\u003e          # Moved under mol\n  bd mol ephemeral \u003cproto\u003e     # Moved under mol\n  bd mol bond \u003cproto\u003e \u003cparent\u003e\n  bd mol squash \u003cid\u003e\n  bd mol burn \u003cid\u003e\n\nAll molecule operations should be under bd mol for discoverability and consistency.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-26T23:36:23.945902-08:00","created_by":"stevey","updated_at":"2025-12-26T23:41:01.096333-08:00","closed_at":"2025-12-26T23:41:01.096333-08:00"}
 {"id":"bd-2g79w","title":"Session ended: gt-beads-refinery","status":"closed","priority":2,"issue_type":"event","created_at":"2026-01-11T00:14:48.858858-08:00","created_by":"beads/refinery","updated_at":"2026-01-11T00:14:48.893797-08:00","closed_at":"2026-01-11T00:14:48.893797-08:00","close_reason":"auto-closed session cost wisp","ephemeral":true}
 {"id":"bd-2gkg","title":"Fix path casing mismatch on macOS causing sync failures (GH#880)","description":"bd sync fails with exit status 128 when daemon started from terminal with different path casing than git worktree registry. macOS case-insensitive filesystem causes mismatch. Fix: normalize paths using realpath or canonical lowercase when daemon starts.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-04T16:09:19.727279-08:00","created_by":"beads/crew/emma","updated_at":"2026-01-04T16:11:30.968102-08:00","closed_at":"2026-01-04T16:11:30.968102-08:00","close_reason":"Fixed: use utils.PathsEqual() for case-insensitive path comparison in worktree validation"}
+{"id":"bd-2hnb4","title":"Session ended: gt-beads-refinery","status":"closed","priority":2,"issue_type":"event","owner":"steve.yegge@gmail.com","created_at":"2026-01-11T08:41:55.248729-08:00","created_by":"beads/refinery","updated_at":"2026-01-11T08:41:55.319098-08:00","closed_at":"2026-01-11T08:41:55.319098-08:00","close_reason":"auto-closed session cost wisp","ephemeral":true}
 {"id":"bd-2ifg","title":"bd-hv01: Silent partial deletion failures cause DB inconsistency","description":"Problem: deletion_tracking.go:76-77 logs deletion errors as warnings but continues. If deletion fails midway (database locked, disk full), some issues delete but others don't. System thinks all deletions succeeded.\n\nImpact: Database diverges from JSONL, silent corruption, issues may resurrect on next sync.\n\nFix: Collect errors and fail the operation:\nvar deletionErrors []error\nfor _, id := range acceptedDeletions {\n    if err := d.DeleteIssue(ctx, id); err != nil {\n        deletionErrors = append(deletionErrors, fmt.Errorf(\"issue %s: %w\", id, err))\n    }\n}\nif len(deletionErrors) \u003e 0 {\n    return false, fmt.Errorf(\"deletion failures: %v\", deletionErrors)\n}\n\nFiles: cmd/bd/deletion_tracking.go:73-82","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-11-06T18:16:19.465137-08:00","updated_at":"2025-11-06T18:46:55.901973-08:00","closed_at":"2025-11-06T18:46:55.901973-08:00","dependencies":[{"issue_id":"bd-2ifg","depends_on_id":"bd-rbxi","type":"parent-child","created_at":"2025-11-06T18:19:14.833477-08:00","created_by":"daemon"}]}
 {"id":"bd-2k5f","title":"GH#510: Document sync-branch worktree behavior","description":"User confused about beads creating worktree on main branch. Need docs explaining sync-branch worktree mechanism. See: https://github.com/steveyegge/beads/issues/510","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-14T16:31:58.800071-08:00","updated_at":"2025-12-16T01:27:29.057639-08:00","closed_at":"2025-12-16T01:27:29.057639-08:00"}
 {"id":"bd-2kf8","title":"Document CompactedResult response format in CONTEXT_ENGINEERING.md","description":"The CompactedResult is a new response format that MCP clients need to understand, but it's not documented in CONTEXT_ENGINEERING.md.\n\n## What's Missing\n- Example CompactedResult JSON response\n- How to detect if a result is compacted\n- How to request full results (disable compaction or increase limit)\n- Guidance on handling both list[IssueMinimal] and CompactedResult return types\n- Migration guide for clients expecting list[Issue] from ready() and list()\n\n## Documentation Gaps\nCurrently CONTEXT_ENGINEERING.md explains the optimization strategy but doesn't show:\n1. Sample CompactedResult response\n2. Client-side code examples for handling compaction\n3. When compaction is triggered (\u003e20 results)\n4. How to get all results if needed\n\n## Suggested Additions\nAdd new section \\\"Handling Large Result Sets\\\" with:\n- CompactedResult schema documentation\n- Python client example for handling both response types\n- Guidance on re-issuing queries with better filters","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-14T14:24:45.216616-08:00","updated_at":"2025-12-14T14:37:15.205803-08:00","closed_at":"2025-12-14T14:37:15.205803-08:00","dependencies":[{"issue_id":"bd-2kf8","depends_on_id":"bd-otf4","type":"discovered-from","created_at":"2025-12-14T14:24:45.217962-08:00","created_by":"stevey"}]}