bd daemon sync: 2026-01-11 21:05:40

This commit is contained in:
beads/refinery
2026-01-11 21:05:40 -08:00
committed by Steve Yegge
parent 992049948f
commit 6dec528e1f

View File

@@ -2043,6 +2043,7 @@
{"id":"bd-uyq10","title":"Digest: mol-refinery-patrol","description":"Patrol: queue empty, main synced to 355ce734","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-11T18:45:37.150101-08:00","updated_at":"2026-01-11T18:45:37.150101-08:00","closed_at":"2026-01-11T18:45:37.149985-08:00","close_reason":"Squashed from 11 wisps","dependencies":[{"issue_id":"bd-uyq10","depends_on_id":"bd-wisp-i97","type":"parent-child","created_at":"2026-01-11T18:45:37.151093-08:00","created_by":"beads/refinery"}]}
{"id":"bd-uyrt4","title":"Session ended: gt-beads-crew-emma","status":"closed","priority":2,"issue_type":"event","created_at":"2026-01-09T12:38:29.302861-08:00","created_by":"beads/crew/emma","updated_at":"2026-01-09T12:38:29.336056-08:00","closed_at":"2026-01-09T12:38:29.336056-08:00","close_reason":"auto-closed session event"}
{"id":"bd-uz8r","title":"Phase 2.3: TOON deletion tracking","description":"Implement deletion tracking in TOON format.\n\n## Overview\nPhase 2.2 switched storage to TOON format. Phase 2.3 adds deletion tracking in TOON format for propagating deletions across clones.\n\n## Required Work\n\n### 2.3.1 Deletion Tracking (TOON Format)\n- [ ] Implement deletions.toon file (tracking deleted issue records)\n- [ ] Add DeleteTracker struct to record deleted issue IDs and metadata\n- [ ] Update bdt delete command to record in deletions.toon\n- [ ] Design deletion record format (ID, timestamp, reason, hash)\n- [ ] Implement auto-prune of old deletion records (configurable TTL)\n\n### 2.3.2 Sync Propagation\n- [ ] Load deletions.toon during import\n- [ ] Remove deleted issues from local database when imported from remote\n- [ ] Handle edge cases (delete same issue in multiple clones)\n- [ ] Deletion ordering and conflict resolution\n\n### 2.3.3 Testing\n- [ ] Unit tests for deletion tracking\n- [ ] Integration tests for deletion propagation\n- [ ] Multi-clone deletion scenarios\n- [ ] TTL expiration tests\n\n## Success Criteria\n- deletions.toon stores deletion records in TOON format\n- Deletions propagate across clones via git sync\n- Old records auto-prune after TTL\n- All 70+ tests still passing\n- bdt delete command works seamlessly","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-19T14:37:23.722066816-07:00","updated_at":"2025-12-21T14:42:27.491932-08:00","closed_at":"2025-12-21T14:42:27.491932-08:00","dependencies":[{"issue_id":"bd-uz8r","depends_on_id":"bd-iic1","type":"discovered-from","created_at":"2025-12-19T14:37:23.726825771-07:00","created_by":"daemon"}]}
{"id":"bd-v0lkx","title":"Session ended: gt-beads-refinery","status":"closed","priority":2,"issue_type":"event","owner":"steve.yegge@gmail.com","created_at":"2026-01-11T21:05:39.667104-08:00","created_by":"beads/refinery","updated_at":"2026-01-11T21:05:39.7386-08:00","closed_at":"2026-01-11T21:05:39.7386-08:00","close_reason":"auto-closed session cost wisp","ephemeral":true}
{"id":"bd-v0x","title":"Auto-detect issue prefix from existing JSONL in 'bd init'","description":"When running `bd init` in a fresh clone with existing JSONL, it should auto-detect the issue prefix from the JSONL file instead of requiring `--prefix`.\n\nCurrently you must specify `--prefix ef` manually. But the JSONL file already contains issues like `ef-1it`, `ef-1jp` etc., so the prefix is known.\n\n**Ideal UX**:\n```\n$ bd init\nDetected issue prefix 'ef' from existing JSONL (38 issues).\n✓ Database initialized...\n```\n\nThis would make fresh clone hydration a single command: `bd init` with no flags.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-11-27T20:21:21.049215-08:00","updated_at":"2025-12-02T17:11:19.751009583-05:00","closed_at":"2025-11-28T21:57:11.164293-08:00"}
{"id":"bd-v29","title":"Deletions pruning doesn't include results in JSON output","description":"## Problem\n\nWhen `bd compact --json` runs with deletions pruning, the prune results are silently discarded:\n\n```go\n// Only report if there were deletions to prune\nif result.PrunedCount \u003e 0 {\n if jsonOutput {\n // JSON output will be included in the main response\n return // \u003c-- BUG: results are NOT included anywhere\n }\n ...\n}\n```\n\n## Location\n`cmd/bd/compact.go:925-929`\n\n## Impact\n- JSON consumers don't know deletions were pruned\n- No way to audit pruning via automation\n\n## Fix\nReturn prune results and include in JSON output structure:\n\n```json\n{\n \"success\": true,\n \"compacted\": {...},\n \"deletions_pruned\": {\n \"count\": 5,\n \"retention_days\": 7\n }\n}\n```","status":"closed","priority":2,"issue_type":"bug","created_at":"2025-11-25T12:48:59.730979-08:00","updated_at":"2025-11-25T15:11:54.363653-08:00","closed_at":"2025-11-25T15:11:54.363653-08:00"}
{"id":"bd-v2mr","title":"Add RequiredSections() method to IssueType","description":"Add method to internal/types that returns recommended sections per issue type (bug, task, feature, epic). This is the foundation for validation.","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-01T11:19:06.129337-08:00","created_by":"beads/crew/grip","updated_at":"2026-01-01T11:28:00.829607-08:00","closed_at":"2026-01-01T11:28:00.829607-08:00","close_reason":"Implemented RequiredSections() method on IssueType with tests","dependencies":[{"issue_id":"bd-v2mr","depends_on_id":"bd-ou35","type":"parent-child","created_at":"2026-01-01T11:19:22.697598-08:00","created_by":"beads/crew/grip"}]}