diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl
index 52ebdb72..f4551ba8 100644
--- a/.beads/issues.jsonl
+++ b/.beads/issues.jsonl
@@ -1,4 +1,4 @@
-{"id":"bd-00u3","title":"Deprecate bd mol run after gt absorbs its semantics","description":"bd mol run is a convenience combo (pour + update + pin) that feels like orchestration but lives in the data layer. This blurs the bd/gt architectural boundary.\n\n## Current State\n- bd mol run = bd pour + bd update --status=in_progress + bd pin --for me\n- gt spawn depends on bd mol run (shells out to it)\n\n## Proposed Change\nOnce gt spawn inlines the pour+assign+pin logic:\n1. Deprecate bd mol run with a warning pointing to gt spawn\n2. Eventually remove bd mol run entirely\n\n## Why\n- bd should be pure data operations (pour, update, pin, close)\n- gt should own orchestration (spawn, sling, hook, handoff)\n- Standalone bd users can run the three commands separately or script them\n\n## Blocked By\ngastown issue gt-r7jj2 (Move mol run semantics from bd into gt spawn)","status":"open","priority":2,"issue_type":"task","created_at":"2025-12-25T00:59:03.667211-08:00","updated_at":"2025-12-25T00:59:20.490179-08:00"}
+{"id":"bd-00u3","title":"Deprecate bd mol run after gt absorbs its semantics","description":"bd mol run is a convenience combo (pour + update + pin) that feels like orchestration but lives in the data layer. This blurs the bd/gt architectural boundary.\n\n## Current State\n- bd mol run = bd pour + bd update --status=in_progress + bd pin --for me\n- gt spawn depends on bd mol run (shells out to it)\n\n## Proposed Change\nOnce gt spawn inlines the pour+assign+pin logic:\n1. Deprecate bd mol run with a warning pointing to gt spawn\n2. Eventually remove bd mol run entirely\n\n## Why\n- bd should be pure data operations (pour, update, pin, close)\n- gt should own orchestration (spawn, sling, hook, handoff)\n- Standalone bd users can run the three commands separately or script them\n\n## Blocked By\ngastown issue gt-r7jj2 (Move mol run semantics from bd into gt spawn)","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-25T00:59:03.667211-08:00","updated_at":"2025-12-25T01:04:51.755145-08:00","closed_at":"2025-12-25T01:04:51.755145-08:00","close_reason":"Removed bd mol run - gt will implement the orchestration combo"}
 {"id":"bd-05a8","title":"Split large cmd/bd files: doctor.go (2948 lines), sync.go (2121 lines)","description":"Code health review found several oversized files:\n\n1. doctor.go - 2948 lines, 48 functions mixed together\n   - Should split into doctor/checks/*.go for individual diagnostics\n   - applyFixes() and previewFixes() are nearly identical\n\n2. sync.go - 2121 lines\n   - ZFC (Zero Flush Check) logic embedded inline (lines 213-247)\n   - Multiple mode handlers should be extracted\n\n3. init.go - 1732 lines\n4. compact.go - 1097 lines\n5. show.go - 1069 lines\n\nRecommendation: Extract into focused sub-packages or split into logical files.","status":"closed","priority":2,"issue_type":"task","assignee":"beads/lima","created_at":"2025-12-16T18:17:18.169927-08:00","updated_at":"2025-12-23T23:58:24.591999-08:00","closed_at":"2025-12-23T23:58:24.591999-08:00","close_reason":"Already completed - doctor.go and sync.go refactored in previous sessions"}
 {"id":"bd-06px","title":"bd sync --from-main fails: unknown flag --no-git-history","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-17T14:32:02.998106-08:00","updated_at":"2025-12-17T23:13:40.531756-08:00","closed_at":"2025-12-17T17:21:48.506039-08:00"}
 {"id":"bd-077e","title":"Add close_reason field to CLI schema and documentation","description":"PR #551 persists close_reason, but the CLI documentation may not mention this field as part of the issue schema.\n\n## Current State\n- close_reason is now persisted in database\n- `bd show --json` will return close_reason in JSON output\n- Documentation may not reflect this new field\n\n## What's Missing\n- CLI reference documentation for close_reason field\n- Schema documentation showing close_reason is a top-level issue field\n- Example output showing close_reason in bd show --json\n- bd close command documentation should mention close_reason parameter is optional\n\n## Suggested Action\n1. Update README.md or CLI reference docs to list close_reason as an issue field\n2. Add example to bd close documentation\n3. Update any type definitions or schema specs\n4. Consider adding close_reason to verbose list output (bd list --verbose)","status":"open","priority":3,"issue_type":"task","created_at":"2025-12-14T14:25:28.448654-08:00","updated_at":"2025-12-14T14:25:28.448654-08:00","dependencies":[{"issue_id":"bd-077e","depends_on_id":"bd-z86n","type":"discovered-from","created_at":"2025-12-14T14:25:28.449968-08:00","created_by":"stevey","metadata":"{}"}]}