johno/beads
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bd sync: 2025-12-29 21:13:11

Browse Source
This commit is contained in:
Steve Yegge
2025-12-29 21:13:11 -08:00
parent 6b12efbb2b
commit 5f5a341624
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.beads/issues.jsonl
View File

@@ -471,7 +471,7 @@
{"id":"bd-lo4","title":"Test pinned issue","status":"tombstone","priority":2,"issue_type":"task","created_at":"2025-12-18T21:44:49.031385-08:00","updated_at":"2025-12-18T21:47:25.055109-08:00","deleted_at":"2025-12-18T21:47:25.055109-08:00","deleted_by":"daemon","delete_reason":"delete","original_type":"task"}
{"id":"bd-lrj8","title":"Technical debt: Scattered TODOs should be tracked as issues","description":"Multiple TODO comments exist in the codebase that should be tracked as proper issues:\n\n1. cmd/bd/migrate_hash_ids.go:24 - 'Consider integrating into bd doctor migration detection'\n2. cmd/bd/migrate_tombstones.go:72 - Same\n3. cmd/bd/migrate_sync.go:16 - Same\n4. cmd/bd/migrate_issues.go:15 - Same\n5. cmd/bd/create.go:164 - 'Switch to target repo for multi-repo support'\n6. cmd/bd/create.go:208 - 'Add RPC method to get config in daemon mode'\n7. cmd/bd/daemon_logger.go:131 - 'Remove this once all callers are updated'\n8. cmd/bd/mol_stale.go:67 - 'Add RPC endpoint for stale check'\n9. cmd/bd/sync_test.go:444 - 'Refactor to use direct import logic'\n10. cmd/bd/jira.go:633 - 'In a full implementation, fetch Jira issue and compare timestamps'\n11. internal/formula/types.go:170,174,179,186,210 - Multiple 'Not yet implemented' TODOs\n12. internal/importer/importer_test.go:1010 - 'Test hangs due to database deadlock'\n\nConsider:\n1. Running 'grep -r TODO' periodically to find new ones\n2. Adding a lint rule to discourage inline TODOs\n3. Converting each to a bd issue with proper tracking\n\nLocation: Various files across codebase","status":"closed","priority":4,"issue_type":"chore","created_at":"2025-12-28T15:32:57.125279-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-28T16:34:10.911155-08:00","closed_at":"2025-12-28T16:34:10.911155-08:00","dependencies":[{"issue_id":"bd-lrj8","depends_on_id":"bd-784c","type":"parent-child","created_at":"2025-12-28T15:38:04.33312-08:00","created_by":"daemon"}]}
{"id":"bd-lsv4","title":"GH#444: Fix inconsistent status naming in_progress vs in-progress","description":"Documentation uses in-progress (hyphen) but code expects in_progress (underscore). Update all docs to use canonical in_progress. See GitHub issue #444.","status":"tombstone","priority":2,"issue_type":"bug","created_at":"2025-12-16T01:03:14.349425-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"}
{"id":"bd-luso","title":"Add agent identity to commit metadata for forensics","description":"## Problem\n\nWhen agents (polecats, crew workers) make commits on behalf of a human, the commit only shows:\n- **Author**: Human (e.g., Steve Yegge)\n- **Co-Authored-By**: Claude Opus 4.5 (generic)\n\nMissing from the audit trail:\n- Which agent instance performed the work\n- Whether it was a polecat (transient) or crew (persistent)\n- What rig/workspace it ran in\n\nExample from a recent release commit:\n```\nAuthor: Steve Yegge \u003csteve.yegge@gmail.com\u003e\nCo-Authored-By: Claude Opus 4.5 \u003cnoreply@anthropic.com\u003e\n```\n\nNo way to trace this back to the specific agent session that executed the release molecule.\n\n## Proposal\n\nAdd git trailers to commits made by Gas Town agents:\n\n```\nExecuted-By: beads/polecat/Nux-1766978911613\nRig: beads\nRole: polecat\n```\n\nOr for crew workers:\n```\nExecuted-By: beads/crew/emma\nRig: beads\nRole: crew\n```\n\n## Benefits\n\n1. **Forensics**: If a release goes wrong, trace back to the exact agent session\n2. **Audit**: Query commits by agent type (`git log --grep=\"Role: polecat\"`)\n3. **Debugging**: Correlate commits with handoff mail and session logs\n4. **Accountability**: Distinguish human-direct vs agent-mediated commits\n\n## Implementation\n\nCould be implemented via:\n- Claude Code hooks (UserPromptSubmit or pre-commit)\n- `gt` commit helper that injects trailers\n- CLAUDE.md instructions for agents to include trailers\n\n## Open Questions\n\n- Should molecule ID be included if work was part of a molecule?\n- Should session ID or other correlation data be included?\n- Privacy considerations for commit metadata?","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-29T13:33:53.591916-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-29T21:09:01.603544-08:00","closed_at":"2025-12-29T21:09:01.603544-08:00","close_reason":"Implemented gt commit command in gastown (commit 4b75b15)"}
{"id":"bd-luso","title":"Add agent identity to commit metadata for forensics","description":"## Problem\n\nWhen agents (polecats, crew workers) make commits on behalf of a human, the commit only shows:\n- **Author**: Human (e.g., Steve Yegge)\n- **Co-Authored-By**: Claude Opus 4.5 (generic)\n\nMissing from the audit trail:\n- Which agent instance performed the work\n- Whether it was a polecat (transient) or crew (persistent)\n- What rig/workspace it ran in\n\nExample from a recent release commit:\n```\nAuthor: Steve Yegge \u003csteve.yegge@gmail.com\u003e\nCo-Authored-By: Claude Opus 4.5 \u003cnoreply@anthropic.com\u003e\n```\n\nNo way to trace this back to the specific agent session that executed the release molecule.\n\n## Proposal\n\nAdd git trailers to commits made by Gas Town agents:\n\n```\nExecuted-By: beads/polecat/Nux-1766978911613\nRig: beads\nRole: polecat\n```\n\nOr for crew workers:\n```\nExecuted-By: beads/crew/emma\nRig: beads\nRole: crew\n```\n\n## Benefits\n\n1. **Forensics**: If a release goes wrong, trace back to the exact agent session\n2. **Audit**: Query commits by agent type (`git log --grep=\"Role: polecat\"`)\n3. **Debugging**: Correlate commits with handoff mail and session logs\n4. **Accountability**: Distinguish human-direct vs agent-mediated commits\n\n## Implementation\n\nCould be implemented via:\n- Claude Code hooks (UserPromptSubmit or pre-commit)\n- `gt` commit helper that injects trailers\n- CLAUDE.md instructions for agents to include trailers\n\n## Open Questions\n\n- Should molecule ID be included if work was part of a molecule?\n- Should session ID or other correlation data be included?\n- Privacy considerations for commit metadata?","status":"open","priority":2,"issue_type":"feature","created_at":"2025-12-29T13:33:53.591916-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-29T21:13:11.101579-08:00"}
{"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":"open","priority":2,"issue_type":"task","created_at":"2025-12-14T14:25:17.414916-08:00","updated_at":"2025-12-14T14:25:17.414916-08:00","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"}]}