bd daemon sync: 2026-01-11 05:52:11

.beads/issues.jsonl

@@ -2093,6 +2093,7 @@
 {"id":"bd-xzrv","title":"Write Agent Mail integration guide","description":"Comprehensive guide for setting up and using Agent Mail with Beads.\n\nAcceptance Criteria:\n- Installation instructions\n- Configuration (environment variables)\n- Architecture diagram\n- Benefits and tradeoffs\n- When to use vs not use\n- Troubleshooting section\n- Migration from git-only mode\n\nFile: docs/AGENT_MAIL.md\n\nSections:\n- Quick start\n- How it works\n- Integration points\n- Graceful degradation\n- Multi-machine deployment\n- FAQ","status":"closed","priority":1,"issue_type":"task","created_at":"2025-11-07T22:42:51.231066-08:00","updated_at":"2025-11-08T00:40:38.798162-08:00","closed_at":"2025-11-08T00:40:38.798162-08:00","dependencies":[{"issue_id":"bd-xzrv","depends_on_id":"bd-fzbg","type":"blocks","created_at":"2025-11-07T22:42:51.232246-08:00","created_by":"daemon"}]}
 {"id":"bd-y0e4","title":"Code smell: Storage interface has 50+ methods - consider interface segregation","description":"The Storage interface in internal/storage/storage.go has 50+ methods covering:\n\n- Issue CRUD (CreateIssue, GetIssue, UpdateIssue, DeleteIssue, SearchIssues)\n- Dependencies (AddDependency, RemoveDependency, GetDependencies, GetDependents, etc.)\n- Labels (AddLabel, RemoveLabel, GetLabels, etc.)\n- Ready work (GetReadyWork, GetBlockedIssues, etc.)\n- Events/Comments\n- Statistics\n- Dirty tracking\n- Export hash tracking\n- ID generation\n- Config/Metadata\n- Transactions\n- Lifecycle\n\nWhile this is a valid design for a storage abstraction, consider the Interface Segregation Principle:\n\n1. Split into smaller interfaces: IssueStorage, DependencyStorage, LabelStorage, etc.\n2. Compose them: `type Storage interface { IssueStorage; DependencyStorage; ... }`\n3. This allows more focused testing and clearer API contracts\n\nLocation: internal/storage/storage.go:79-197","status":"closed","priority":4,"issue_type":"chore","created_at":"2025-12-28T15:32:54.005169-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-28T17:21:44.466226-08:00","closed_at":"2025-12-28T17:21:44.466226-08:00","dependencies":[{"issue_id":"bd-y0e4","depends_on_id":"bd-784c","type":"parent-child","created_at":"2025-12-28T15:38:04.296641-08:00","created_by":"daemon"}]}
 {"id":"bd-y0fj","title":"Issue lifecycle hooks (on-close, on-complete)","description":"Add hooks that fire on issue state transitions, enabling automation like closing linked GitHub issues.\n\n## Problem\n\nWe have `external_ref` to link beads issues to external systems (GitHub, Linear, Jira), but no mechanism to trigger actions when issues close. Currently:\n\n```\nbd-u2sc (external_ref: gh-692) closes → nothing happens\n```\n\n## Proposed Solution\n\n### Phase 1: Shell Hooks\n\nAdd `.beads-hooks/on-close.sh` (and similar lifecycle hooks):\n\n```bash\n# .beads-hooks/on-close.sh\n# Called by bd close with issue JSON on stdin\n#\\!/bin/bash\nissue=$(cat)\nexternal_ref=$(echo \"$issue\" | jq -r '.external_ref // empty')\nif [[ \"$external_ref\" == gh-* ]]; then\n    number=\"${external_ref#gh-}\"\n    gh issue close \"$number\" --repo steveyegge/beads \\\n      --comment \"Completed via beads epic $(echo $issue | jq -r .id)\"\nfi\n```\n\n### Lifecycle Events\n\n| Event | Trigger | Use Cases |\n|-------|---------|-----------|\n| `on-close` | Issue closed | Close external refs, notify, archive |\n| `on-complete` | Epic children all done | Roll-up completion, close parent refs |\n| `on-status-change` | Any status transition | Sync to external systems |\n\n### Phase 2: Molecule Completion Handlers\n\nMolecules could define completion actions:\n\n```yaml\nname: github-issue-tracker\non_complete:\n  - action: shell\n    command: gh issue close {{external_ref}} --repo {{repo}}\n  - action: mail\n    to: mayor/\n    subject: \"Epic {{id}} completed\"\n```\n\n### Phase 3: Gas Town Integration\n\nFor full Gas Town deployments:\n- Witness observes closures via beads events\n- Routes to integration agents via mail\n- Agents handle external system interactions\n\n## Implementation Notes\n\n- Hooks should be async (don't block bd close)\n- Pass full issue JSON to hook via stdin\n- Support hook timeout and failure handling\n- Consider `--no-hooks` flag for bulk operations\n\n## Related\n\n- `external_ref` field already exists (GH#142)\n- Cross-project deps: bd-h807, bd-d9mu\n- Git hooks: .beads-hooks/ pattern established\n\n## Use Cases\n\n1. **GitHub integration**: Close GH issues when beads epic completes\n2. **Linear sync**: Update Linear status when beads status changes  \n3. **Notifications**: Send mail/Slack when high-priority issues close\n4. **Audit**: Log all closures to external system","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-22T14:46:04.846657-08:00","updated_at":"2025-12-22T14:50:40.35447-08:00","closed_at":"2025-12-22T14:50:40.35447-08:00"}
+{"id":"bd-y1a3y","title":"Session ended: gt-beads-refinery","status":"closed","priority":2,"issue_type":"event","owner":"steve.yegge@gmail.com","created_at":"2026-01-11T05:52:10.952063-08:00","created_by":"beads/refinery","updated_at":"2026-01-11T05:52:11.014817-08:00","closed_at":"2026-01-11T05:52:11.014817-08:00","close_reason":"auto-closed session cost wisp","ephemeral":true}
 {"id":"bd-y2v","title":"Refactor duplicate JSONL-from-git parsing code","description":"Both readFirstIssueFromGit() in init.go and importFromGit() in autoimport.go have similar code patterns for:\n1. Running git show \u003cref\u003e:\u003cpath\u003e\n2. Scanning the output with bufio.Scanner\n3. Parsing JSON lines\n\nCould be refactored to share a helper like:\n- readJSONLFromGit(gitRef, path string) ([]byte, error)\n- Or a streaming version: streamJSONLFromGit(gitRef, path string) (io.Reader, error)\n\nFiles:\n- cmd/bd/autoimport.go:225-256 (importFromGit)\n- cmd/bd/init.go:1212-1243 (readFirstIssueFromGit)\n\nPriority is low since code duplication is minimal and both functions work correctly.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-05T14:51:18.41124-08:00","updated_at":"2025-12-23T22:37:15.770825-08:00","closed_at":"2025-12-23T22:37:15.770825-08:00"}
 {"id":"bd-y4804","title":"Session ended: gt-beads-crew-emma","status":"closed","priority":2,"issue_type":"event","created_at":"2026-01-09T21:27:08.729768-08:00","created_by":"beads/crew/emma","updated_at":"2026-01-09T21:27:08.76478-08:00","closed_at":"2026-01-09T21:27:08.76478-08:00","close_reason":"auto-closed session cost wisp","ephemeral":true}
 {"id":"bd-y4vz","title":"Work on beads-eub: Consolidated context tool for MCP serv...","description":"Work on beads-eub: Consolidated context tool for MCP server (GH#636). Merge set_context, where_am_i, init into single 'context' tool. When done, submit MR (not PR) to integration branch for Refinery.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-19T22:56:58.527144-08:00","updated_at":"2025-12-20T00:49:51.929597-08:00","closed_at":"2025-12-19T23:31:11.906952-08:00"}