diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl
index c7be5bb1..1b0e7872 100644
--- a/.beads/issues.jsonl
+++ b/.beads/issues.jsonl
@@ -1803,7 +1803,7 @@
 {"id":"bd-z4f5","title":"--parent flag reports success but doesn't persist to JSONL","description":"The --parent flag for bd update reports success but the change doesn't persist.\n\nReported by: Mayor\nLocation: show.go:810-814 handles the logic\n\nSymptoms:\n- bd update \u003cid\u003e --parent=\u003cnew-parent\u003e returns success\n- But the parent change is not written to JSONL\n- Subsequent bd show reveals parent unchanged\n\nThis shipped in v0.39.1 as part of bd-cj2e (--parent flag for reparenting).\n\nInvestigation: Check the update path from show.go through to JSONL export. The RPC/daemon layer may be dropping the parent field, or the storage layer isn't persisting it.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-27T23:10:22.428136-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-27T23:27:45.716572-08:00","closed_at":"2025-12-27T23:27:45.716572-08:00"}
 {"id":"bd-z528","title":"Prevent test pollution in production database","description":"The bd-vxdr cleanup revealed test issues were created during manual testing in the production workspace (Nov 2-4, template feature development).\n\n**Root cause:** Manual testing with `./bd create \"Test issue\"` pollutes the production .beads database.\n\n**Prevention strategies:**\n1. Use TEST_DB environment variable for manual testing\n2. Add warning when creating issues with \"Test\" prefix\n3. Improve developer docs about testing workflow\n4. Consider adding `bd test-mode` command for isolated testing","notes":"**Implementation completed:**\n\n1. ✅ Added warning when creating issues with \"Test\" prefix in production database\n   - Shows yellow warning with ⚠ symbol\n   - Suggests using BEADS_DB for isolated testing\n   - Warning appears in create.go after title validation\n\n2. ✅ Documented BEADS_DB testing workflow in AGENTS.md\n   - Added \"Testing Workflow\" section in Development Guidelines\n   - Includes manual testing examples with BEADS_DB\n   - Includes automated testing examples with t.TempDir()\n   - Clear warning about not polluting production database\n\n3. ⚠️ Decided against bd test-mode command\n   - BEADS_DB already provides simple, flexible isolation\n   - Additional command would add complexity without much benefit\n   - Current approach follows Unix philosophy (env vars for config)\n\n**Files modified:**\n- cmd/bd/create.go - Added Test prefix warning\n- AGENTS.md - Added Testing Workflow section\n\n**Testing:**\n- Verified warning appears when creating \"Test\" prefix issues\n- Verified BEADS_DB isolation works correctly\n- Built successfully with `go build`","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-07T16:07:28.255289-08:00","updated_at":"2025-11-07T23:18:08.386514-08:00","closed_at":"2025-11-07T22:43:28.669908-08:00"}
 {"id":"bd-z6kw","title":"Refinery gh:run gate auto-discovery","description":"Refinery auto-populates await_id for gh:run gates from recent workflow runs.\n\n## Problem\nGate created by cook has await_type=gh:run but no await_id.\nNeed to discover the run ID from the push that triggered CI.\n\n## Solution\nDuring Refinery patrol:\n1. Find open gh:run gates without await_id\n2. Query: gh run list --workflow=\u003cgate.workflow\u003e --limit=5\n3. Match run to gate (by branch, commit, or time proximity)\n4. Update gate: bd update \u003cgate-id\u003e --await-id=\u003crun-id\u003e\n5. Now bd gate check --type=gh can poll that specific run\n\n## Implementation\n- Add discover-await-ids step to mol-refinery-patrol\n- Use gh CLI to query recent runs\n- Match heuristics: same branch, recent commit, within 5 mins\n- Update gate with discovered run ID\n\n## Acceptance Criteria\n- [ ] Refinery discovers run IDs for gh:run gates\n- [ ] Gates updated with correct await_id\n- [ ] Subsequent polls use run ID\n- [ ] Handles multiple pending gates","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-02T13:27:42.35667-08:00","created_by":"mayor","updated_at":"2026-01-04T15:22:07.771701-08:00","closed_at":"2026-01-02T16:12:24.656236-08:00","close_reason":"Implemented bd gate discover command for auto-discovery of gh:run gate await_ids","dependencies":[{"issue_id":"bd-z6kw","depends_on_id":"bd-d1n1","type":"parent-child","created_at":"2026-01-02T13:28:18.621422-08:00","created_by":"mayor"},{"issue_id":"bd-z6kw","depends_on_id":"bd-4k3c","type":"blocks","created_at":"2026-01-02T13:28:18.688305-08:00","created_by":"mayor"}]}
-{"id":"bd-z7w5p","title":"Review PR #16215: Fix broken links in plugin docs","description":"Review and verify PR #16215 (anthropics/claude-code)\n\nPR: https://github.com/anthropics/claude-code/pull/16215\nAuthor: jeremylongshore\n\nFixes broken CONTRIBUTING and LICENSE links.\n- gh pr view 16215 --repo anthropics/claude-code\n- gh pr diff 16215 --repo anthropics/claude-code\n- If good: gh pr merge 16215 --repo anthropics/claude-code --squash","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-08T14:20:05.178308-08:00","created_by":"beads/crew/emma","updated_at":"2026-01-08T14:20:05.178308-08:00"}
+{"id":"bd-z7w5p","title":"Review PR #16215: Fix broken links in plugin docs","description":"dispatched_by: beads/crew/emma\n\nReview and verify PR #16215 (anthropics/claude-code)\n\nPR: https://github.com/anthropics/claude-code/pull/16215\nAuthor: jeremylongshore\n\nFixes broken CONTRIBUTING and LICENSE links.\n- gh pr view 16215 --repo anthropics/claude-code\n- gh pr diff 16215 --repo anthropics/claude-code\n- If good: gh pr merge 16215 --repo anthropics/claude-code --squash","status":"hooked","priority":2,"issue_type":"task","assignee":"beads/crew/fang","created_at":"2026-01-08T14:20:05.178308-08:00","created_by":"beads/crew/emma","updated_at":"2026-01-08T14:22:09.411632-08:00"}
 {"id":"bd-z830","title":"Test child task","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-27T23:26:58.246573-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-27T23:27:40.451603-08:00","closed_at":"2025-12-27T23:27:40.451603-08:00","dependencies":[{"issue_id":"bd-z830","depends_on_id":"bd-fbl9","type":"parent-child","created_at":"2025-12-27T23:27:02.984294-08:00","created_by":"daemon"}]}
 {"id":"bd-z86n","title":"Code Review: PR #551 - Persist close_reason to issues table","description":"Code review of PR #551 which fixes close_reason persistence bug.\n\n## Summary\nThe PR correctly fixes a bug where close_reason was only stored in the events table, not in the issues.close_reason column. This caused `bd show --json` to return empty close_reason.\n\n## What Was Fixed\n- ✅ CloseIssue now updates both close_reason and closed_at\n- ✅ ReOpenIssue clears both close_reason and closed_at\n- ✅ Comprehensive tests added for both storage and CLI layers\n- ✅ Clear documentation in queries.go about dual storage strategy\n\n## Quality Assessment\n✅ Tests cover both storage layer and CLI JSON output\n✅ Handles reopen case (clearing close_reason)\n✅ Good comments explaining dual-storage design\n✅ No known issues\n\n## Potential Followups\nSee linked issues for suggestions.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-14T14:25:06.887069-08:00","updated_at":"2025-12-29T13:40:29.724656-08:00","closed_at":"2025-12-29T13:40:29.724656-08:00","close_reason":"Stale/spurious - test artifacts, merged PRs, or auto-close candidates"}
 {"id":"bd-z8a6","title":"bd delete --from-file should add deleted issues to deletions manifest","description":"When using bd delete --from-file to bulk delete issues, the deleted issue IDs are not being added to the deletions.jsonl manifest.\n\nThis causes those issues to be resurrected during bd sync when git history scanning finds them in old commits.\n\nExpected: All deleted issues should be added to deletions.jsonl so they wont be reimported from git history.\n\nWorkaround: Manually add deletion records to deletions.jsonl.","status":"tombstone","priority":1,"issue_type":"bug","created_at":"2025-12-16T01:48:14.099855-08:00","updated_at":"2025-12-17T16:11:17.070763-08:00","deleted_at":"2025-12-17T16:11:17.070763-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"bug"}