bd daemon sync: 2026-01-11 09:09:30

.beads/issues.jsonl

@@ -1587,6 +1587,7 @@
 {"id":"bd-nib2","title":"Add tests for bd create --dry-run flag","description":"dispatched_by: gastown/crew/max\n\nCommit 744d2a7d added --dry-run flag to bd create but lacks tests.\n\nTest cases needed:\n- Basic dry-run outputs preview without creating issue\n- Dry-run with --json outputs valid JSON (with empty ID)\n- Dry-run with --rig/--prefix shows target rig\n- Dry-run with --file returns error\n- Dry-run includes labels and deps in preview\n- Dry-run with --type=event includes event fields\n\nLocation: cmd/bd/create.go:181-254\nSuggested test file: cmd/bd/create_test.go","status":"closed","priority":2,"issue_type":"task","assignee":"beads/crew/giles","created_at":"2026-01-07T01:18:08.338705-08:00","created_by":"beads/crew/emma","updated_at":"2026-01-08T20:08:34.078988-08:00","closed_at":"2026-01-08T20:08:34.078988-08:00","close_reason":"Tests already added in commit 66ab0ccd. All 7 test cases pass: BasicDryRunPreview, DryRunWithJSONOutput, DryRunWithLabelsAndDeps, DryRunWithRigPrefix, DryRunWithFileReturnsError, DryRunWithEventType, DryRunWithExplicitID"}
 {"id":"bd-nim5","title":"Detect/prevent child→parent dependency anti-pattern","description":"## Problem\n\nWhen filing issues with dependencies, it's easy to fall into the \"temporal trap\":\n- Thinking \"Phase 1 comes before Phase 2\"\n- Writing `bd dep add phase1 phase2`\n- But that means \"phase1 depends on phase2\" (backwards!)\n\nA specific variant: children depending on their parent epic. This is ALWAYS wrong because:\n1. Parent-child relationship already captures the dependency (parent closes when children done)\n2. Child→parent dep creates a block: child can't start because parent is \"open\"\n3. Parent can't close because children aren't done\n4. Deadlock\n\n## Solution\n\n### 1. Prevent at creation (`bd dep add`)\n\nWhen user runs `bd dep add X Y`:\n- Check if X is a child of Y (X.id starts with Y.id + \".\")\n- If so, error: \"Cannot add dependency: X is already a child of Y. Children inherit dependency on parent completion via hierarchy.\"\n\n### 2. Detect in `bd doctor`\n\nAdd a check that finds all cases where:\n- Issue A depends on Issue B\n- A.id matches pattern B.id + \".*\" (A is child of B)\n\nReport as: \"Child→parent dependency detected (anti-pattern)\"\nOffer repair: \"Remove N backwards dependencies? [y/N]\"\n\n## Implementation\n\n- `dep_add.go`: Add parent-child check before adding dependency\n- `doctor.go`: Add backwards-dep detection to health checks\n","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-24T12:51:15.788796-08:00","updated_at":"2025-12-24T13:02:44.079093-08:00","closed_at":"2025-12-24T13:02:44.079093-08:00"}
 {"id":"bd-njrm","title":"Work on gt-8tmz.34: Expansion var overrides not implement...","description":"Work on gt-8tmz.34: Expansion var overrides not implemented. The ExpandRule.Vars field exists in internal/formula/types.go but is ignored during expansion in internal/formula/expand.go. Implement: 1) Pass rule.Vars to expandStep in ApplyExpansions, 2) Merge vars with formula defaults (rule.Vars wins), 3) Substitute vars in template placeholders, 4) Add test in expand_test.go. When done, commit and push to main.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-25T20:01:13.586558-08:00","updated_at":"2025-12-25T20:06:11.099142-08:00","closed_at":"2025-12-25T20:06:11.099142-08:00"}
+{"id":"bd-njs96","title":"Session ended: gt-beads-refinery","status":"closed","priority":2,"issue_type":"event","owner":"steve.yegge@gmail.com","created_at":"2026-01-11T09:09:29.792196-08:00","created_by":"beads/refinery","updated_at":"2026-01-11T09:09:29.852959-08:00","closed_at":"2026-01-11T09:09:29.852959-08:00","close_reason":"auto-closed session cost wisp","ephemeral":true}
 {"id":"bd-nkqx","title":"bd swarm validate command","description":"Add bd swarm validate to check epic structure for swarming.\n\n## Context\nBefore running a swarm, we need to validate the epic structure:\n- Are dependencies correct (not inverted)?\n- Are there orphaned issues?\n- Is the DAG well-formed?\n\nThe Ready Front model (not phases!) means dependencies define execution order.\nCommon mistake: 'Phase 1 before Phase 2' → inverted deps.\nCorrect thinking: 'Phase 2 needs Phase 1' → bd dep add phase2 phase1\n\n## Implementation\n1. New command: bd swarm validate \u003cepic-id\u003e\n2. Walk the dependency DAG from epic children\n3. Detect issues:\n   - Root issues with no dependents (orphans?)\n   - Leaf issues depending on nothing (missing deps?)\n   - Cycles (impossible)\n   - Disconnected subgraphs\n4. Report:\n   - Ready fronts (waves of parallel work)\n   - Estimated worker-sessions\n   - Max parallelism\n   - Warnings for potential issues\n\n## Reference\n~/gt/docs/swarm-architecture.md - 'The Ready Front Model' section\n\n## Acceptance\n- bd swarm validate \u003cepic\u003e runs\n- Reports ready fronts accurately\n- Warns about structural issues\n- Returns success/failure exit code","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-28T19:11:08.788203-08:00","created_by":"mayor","updated_at":"2025-12-28T19:34:57.218009-08:00","closed_at":"2025-12-28T19:34:57.218009-08:00"}
 {"id":"bd-nl2","title":"No logging/debugging for tombstone resurrection events","description":"Per the design document bd-zvg Open Question 1: Should resurrection log a warning? Recommendation was Yes. Currently, when an expired tombstone loses to a live issue (resurrection), there is no logging or debugging output. This makes it hard to understand why an issue reappeared. Recommendation: Add optional debug logging when resurrection occurs, e.g., Issue bd-abc resurrected (tombstone expired). Files: internal/merge/merge.go:359-366, 371-378, 400-405, 410-415","status":"closed","priority":4,"issue_type":"feature","created_at":"2025-12-05T16:36:52.27525-08:00","updated_at":"2025-12-30T18:12:30.964926-08:00","closed_at":"2025-12-30T15:57:06.707152-08:00","close_reason":"Implemented debug logging for tombstone resurrection events. Added debug parameter to Merge3WayWithTTL and all 4 resurrection code paths now log 'Issue \u003cid\u003e resurrected (tombstone expired)' when debug mode is enabled."}
 {"id":"bd-nl8z","title":"Documentation","description":"Complete documentation for Agent Mail integration to enable adoption.","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-11-07T22:42:37.969636-08:00","updated_at":"2025-11-08T03:09:48.253476-08:00","closed_at":"2025-11-08T02:34:57.887891-08:00","dependencies":[{"issue_id":"bd-nl8z","depends_on_id":"bd-wfmw","type":"blocks","created_at":"2025-11-07T22:42:37.970621-08:00","created_by":"daemon"}]}