diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl
index 6369b70b..719db6d9 100644
--- a/.beads/issues.jsonl
+++ b/.beads/issues.jsonl
@@ -548,7 +548,7 @@
 {"id":"bd-lw0x","title":"Fix bd sync race condition with daemon causing dirty working directory","description":"After bd sync completes with sync.branch mode, subsequent bd commands or daemon file watcher would see a hash mismatch and trigger auto-import, which then schedules re-export, dirtying the working directory.\n\n**Root cause:**\n1. bd sync exports JSONL with NEW content (hash H1)\n2. bd sync updates jsonl_content_hash = H1 in DB\n3. bd sync restores JSONL from HEAD (OLD content, hash H0)\n4. Now: file hash = H0, DB hash = H1 (MISMATCH)\n5. Daemon or next CLI command sees mismatch, imports from OLD JSONL\n6. Import triggers re-export → file is dirty\n\n**Fix:**\nAfter restoreBeadsDirFromBranch(), update jsonl_content_hash to match the restored file's hash. This ensures daemon and CLI see file hash = DB hash → no spurious import/export cycle.\n\nRelated: bd-c83r (multiple daemon prevention)","status":"tombstone","priority":2,"issue_type":"bug","created_at":"2025-12-13T06:42:17.130839-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-lxzx","title":"Add close_reason to JSONL export format documentation","description":"PR #551 now persists close_reason to the database, but there's a question about whether this field should be exported to JSONL format.\n\n## Current State\n- close_reason is stored in issues.close_reason column\n- close_reason is also stored in events table (audit trail)\n- The JSONL export format may or may not include close_reason\n\n## Questions\n1. Should close_reason be exported to JSONL format?\n2. If yes, where should it go (root level or nested in events)?\n3. Should there be any special handling to avoid duplication?\n4. How should close_reason be handled during JSONL import?\n\n## Why This Matters\n- JSONL is the git-friendly sync format\n- Other beads instances import from JSONL\n- close_reason is meaningful data that should be preserved across clones\n\n## Suggested Action\n- Check if close_reason is currently exported in JSONL\n- If not, add it to the export schema\n- Document the field in JSONL format spec\n- Add tests for round-trip (export -\u003e import -\u003e verify close_reason)","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-14T14:25:17.414916-08:00","updated_at":"2025-12-30T18:12:30.972954-08:00","closed_at":"2025-12-30T17:03:27.56903-08:00","close_reason":"Documented close_reason in JSONL schema and added round-trip test","dependencies":[{"issue_id":"bd-lxzx","depends_on_id":"bd-z86n","type":"discovered-from","created_at":"2025-12-14T14:25:17.416131-08:00","created_by":"stevey"}]}
 {"id":"bd-lz49","title":"Add gate fields: await_type, await_id, timeout, waiters","description":"Add gate-specific fields to the Issue type.\n\n## New Fields\n- await_type: string - Type of condition (gh:run, gh:pr, timer, human, mail)\n- await_id: string - Identifier for the condition\n- timeout: duration - Max time to wait before escalation\n- waiters: []string - Mail addresses to notify when gate clears\n\n## Implementation\n- Add fields to Issue struct in internal/types/types.go\n- Update SQLite schema for new columns\n- Add JSONL serialization/deserialization\n- Update import/export logic","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-23T11:44:32.720196-08:00","updated_at":"2025-12-23T12:00:03.837691-08:00","closed_at":"2025-12-23T12:00:03.837691-08:00","dependencies":[{"issue_id":"bd-lz49","depends_on_id":"bd-udsi","type":"parent-child","created_at":"2025-12-23T11:44:52.738823-08:00","created_by":"daemon"},{"issue_id":"bd-lz49","depends_on_id":"bd-2v0f","type":"blocks","created_at":"2025-12-23T11:44:56.269351-08:00","created_by":"daemon"}]}
-{"id":"bd-m03p","title":"Merge: quartz-mjw4bkpv","description":"branch: polecat/quartz-mjw4bkpv\ntarget: main\nsource_issue: quartz-mjw4bkpv\nrig: beads\nagent_bead: gt-beads-polecat-quartz","status":"open","priority":2,"issue_type":"merge-request","created_at":"2026-01-01T16:16:18.601679-08:00","created_by":"beads/polecats/quartz","updated_at":"2026-01-01T16:16:18.601679-08:00"}
+{"id":"bd-m03p","title":"Merge: quartz-mjw4bkpv","description":"branch: polecat/quartz-mjw4bkpv\ntarget: main\nsource_issue: quartz-mjw4bkpv\nrig: beads\nagent_bead: gt-beads-polecat-quartz","status":"closed","priority":2,"issue_type":"merge-request","created_at":"2026-01-01T16:16:18.601679-08:00","created_by":"beads/polecats/quartz","updated_at":"2026-01-01T19:27:21.729371-08:00","closed_at":"2026-01-01T19:27:21.729371-08:00","close_reason":"Stale MR - no branch pushed after 3+ hours"}
 {"id":"bd-m0tl","title":"bd create -f crashes with nil pointer dereference","description":"GitHub issue #674. The markdown import feature crashes at markdown.go:338 because global variables (store, ctx, actor) aren't initialized when createIssuesFromMarkdown is called. The function uses globals set by cobra command framework but is being called before they're ready. Need to either initialize globals at start of function or pass them as parameters.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-21T14:35:14.813012-08:00","updated_at":"2025-12-21T15:41:14.600953-08:00","closed_at":"2025-12-21T15:41:14.600953-08:00"}
 {"id":"bd-m164","title":"Add 0.33.2 to versionChanges in info.go","description":"Add new entry at the TOP of versionChanges array in cmd/bd/info.go:\n\n```go\n{\n    Version: \"0.33.2\",\n    Date:    \"2025-12-21\",\n    Changes: []string{\n        // Add notable changes here\n    },\n},\n```\n\nCopy changes from CHANGELOG.md [Unreleased] section.","status":"tombstone","priority":1,"issue_type":"task","created_at":"2025-12-21T16:10:13.761218-08:00","updated_at":"2025-12-21T17:29:31.791368-08:00","deleted_at":"2025-12-21T17:29:31.791368-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"task"}
 {"id":"bd-m6r3","title":"Refactor: Extract shared getEpicChildren helper for swarm commands","description":"## Context\n`getSwarmStatus` and `analyzeEpicForSwarm` in cmd/bd/swarm.go have nearly identical code for:\n- Getting epic dependents via GetDependents\n- Filtering to parent-child relationships\n- Building childIDSet map\n- Building dependency maps\n\n## Implementation\n1. Extract `getEpicChildren(ctx, store, epicID)` that returns:\n   - `[]*types.Issue` - child issues\n   - `map[string]bool` - child ID set\n   - `map[string][]string` - dependency map (within children)\n   - `error`\n\n2. Refactor both `analyzeEpicForSwarm` and `getSwarmStatus` to use it\n\n3. Consider defining a named interface for the store methods:\n   ```go\n   type SwarmStore interface {\n       GetIssue(context.Context, string) (*types.Issue, error)\n       GetDependents(context.Context, string) ([]*types.Issue, error)\n       GetDependencyRecords(context.Context, string) ([]*types.Dependency, error)\n   }\n   ```\n\n## Files\n- cmd/bd/swarm.go (lines 150-248, 616-682)\n\n## Acceptance\n- No duplicated code for fetching epic children\n- Both commands produce identical results as before","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-28T21:30:55.55377-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-28T21:43:50.759453-08:00","closed_at":"2025-12-28T21:43:50.759453-08:00"}