bd sync: 2026-01-01 19:27:21
This commit is contained in:
committed by
Steve Yegge
parent
137d115849
commit
756622c219
@@ -267,6 +267,7 @@
|
||||
{"id":"bd-au0.7","title":"Audit and standardize JSON output across all commands","description":"Ensure consistent JSON format and error handling when --json flag is used.\n\n**Scope:**\n1. Verify all commands respect --json flag\n2. Standardize success response format\n3. Standardize error response format\n4. Document JSON schemas\n\n**Commands to audit:**\n- Core CRUD: create, update, delete, show, list, search ✓\n- Queries: ready, blocked, stale, count, stats, status\n- Deps: dep add/remove/tree/cycles\n- Labels: label commands\n- Comments: comments add/list/delete\n- Epics: epic status/close-eligible\n- Export/import: already support --json ✓\n\n**Testing:**\n- Success cases return valid JSON\n- Error cases return valid JSON (not plain text)\n- Consistent field naming (snake_case vs camelCase)\n- Array vs object wrapping consistency","notes":"## Audit Complete (2025-12-25)\n\n### Findings\n\n**✓ All commands support --json flag**\n- Query commands: ready, blocked, stale, count, stats, status\n- Dep commands: add, remove, tree, cycles \n- Label commands: add, remove, list, list-all\n- Comments: list, add\n- Epic: status, close-eligible\n\n**✓ Field naming is consistent**\n- All fields use snake_case: created_at, issue_type, dependency_count, etc.\n\n**✗ Error output is INCONSISTENT**\n- Only bd show uses FatalErrorRespectJSON (returns JSON errors)\n- All other commands use fmt.Fprintf(os.Stderr, ...) (returns plain text)\n\n### Files needing fixes\n\n| File | stderr writes | Commands |\n|------|---------------|----------|\n| show.go | 51 | update, close, edit |\n| dep.go | 41 | dep add/remove/tree/cycles |\n| label.go | 19 | label add/remove/list |\n| comments.go | ~10 | comments add/list |\n| epic.go | ~5 | epic status/close-eligible |\n\n### Follow-up\n\nCreated epic bd-28sq to track fixing all error handlers.","status":"closed","priority":1,"issue_type":"task","created_at":"2025-11-21T21:07:35.304424-05:00","updated_at":"2025-12-25T13:32:32.460786-08:00","closed_at":"2025-12-25T13:32:32.460786-08:00","dependencies":[{"issue_id":"bd-au0.7","depends_on_id":"bd-au0","type":"parent-child","created_at":"2025-11-21T21:07:35.305663-05:00","created_by":"daemon"}],"comments":[{"id":4,"issue_id":"bd-au0.7","author":"stevey","text":"Progress on JSON standardization:\n\n## Completed\n1. **Fixed `bd comments list` null output** - Now returns `[]` instead of `null` for empty comments\n2. **Added `FatalErrorRespectJSON` helper** in errors.go - Pattern for JSON-aware error output\n3. **Fixed flag shadowing** - Removed local `--json` flags from show/update/close that shadowed the global persistent flag\n4. **Updated show command** - Error handlers now use `FatalErrorRespectJSON` as reference implementation\n\n## Audit Results\n- Query commands (ready, blocked, stale, count, stats, status): ✓ All support --json correctly\n- Dep commands (tree, cycles): ✓ All support --json correctly \n- Label commands: ✓ Returns [] for empty\n- Comments: ✓ Fixed null→[]\n- Epic commands (status, close-eligible): ✓ All support --json correctly\n\n## Remaining Work\n- Other commands (list, create, etc.) still use `fmt.Fprintf(os.Stderr, ...)` for errors - could be updated to use `FatalErrorRespectJSON` for JSON error output\n- JSON schema documentation not yet created","created_at":"2025-12-24T07:53:38Z"}]}
|
||||
{"id":"bd-au0.8","title":"Improve clean vs cleanup command naming/documentation","description":"Clarify the difference between bd clean and bd cleanup to reduce user confusion.\n\n**Current state:**\n- bd clean: Remove temporary artifacts (.beads/bd.sock, logs, etc.)\n- bd cleanup: Delete old closed issues from database\n\n**Options:**\n1. Rename for clarity:\n - bd clean → bd clean-temp\n - bd cleanup → bd cleanup-issues\n \n2. Keep names but improve help text and documentation\n\n3. Add prominent warnings in help output\n\n**Preferred approach:** Option 2 (improve documentation)\n- Update short/long descriptions in commands\n- Add examples to help text\n- Update README.md\n- Add cross-references in help output\n\n**Files to modify:**\n- cmd/bd/clean.go\n- cmd/bd/cleanup.go\n- README.md or ADVANCED.md","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-21T21:07:49.960534-05:00","updated_at":"2025-12-23T23:48:00.594734-08:00","closed_at":"2025-12-23T23:48:00.594734-08:00","dependencies":[{"issue_id":"bd-au0.8","depends_on_id":"bd-au0","type":"parent-child","created_at":"2025-11-21T21:07:49.962743-05:00","created_by":"daemon"}]}
|
||||
{"id":"bd-au0.9","title":"Review and document rarely-used commands","description":"Document use cases or consider deprecation for infrequently-used commands.\n\n**Commands to review:**\n1. bd rename-prefix - How often is this used? Document use cases\n2. bd detect-pollution - Consider integrating into bd validate\n3. bd migrate-hash-ids - One-time migration, keep but document as legacy\n\n**For each command:**\n- Document typical use cases\n- Add examples to help text\n- Consider if it should be a subcommand instead\n- Add deprecation warning if appropriate\n\n**Not changing:**\n- duplicates ✓ (useful for data quality)\n- repair-deps ✓ (useful for fixing broken refs)\n- restore ✓ (critical for compacted issues)\n- compact ✓ (performance feature)\n\n**Deliverable:**\n- Updated help text\n- Documentation in ADVANCED.md\n- Deprecation plan if needed","status":"closed","priority":3,"issue_type":"task","created_at":"2025-11-21T21:08:05.588275-05:00","updated_at":"2025-12-23T23:50:04.180989-08:00","closed_at":"2025-12-23T23:50:04.180989-08:00","dependencies":[{"issue_id":"bd-au0.9","depends_on_id":"bd-au0","type":"parent-child","created_at":"2025-11-21T21:08:05.59003-05:00","created_by":"daemon"}]}
|
||||
{"id":"bd-avxi","title":"Merge: opal-mjwb5yov","description":"branch: polecat/opal-mjwb5yov\ntarget: main\nsource_issue: opal-mjwb5yov\nrig: beads\nagent_bead: gt-beads-polecat-opal","status":"closed","priority":2,"issue_type":"merge-request","created_at":"2026-01-01T19:25:41.421501-08:00","created_by":"beads/polecats/opal","updated_at":"2026-01-01T19:27:07.580453-08:00","closed_at":"2026-01-01T19:27:07.580453-08:00","close_reason":"No branch pushed - verification task with no code changes"}
|
||||
{"id":"bd-awmf","title":"Merge: bd-dtl8","description":"branch: polecat/dag\ntarget: main\nsource_issue: bd-dtl8\nrig: beads","status":"closed","priority":1,"issue_type":"merge-request","created_at":"2025-12-23T20:47:15.147476-08:00","updated_at":"2025-12-23T21:21:57.690692-08:00","closed_at":"2025-12-23T21:21:57.690692-08:00"}
|
||||
{"id":"bd-aydr","title":"Add bd reset command for clean slate restart","description":"Implement a `bd reset` command to reset beads to a clean starting state.\n\n## Context\nGitHub issue #479 - users sometimes get beads into an invalid state after updates, and there's no clean way to start fresh. The git backup/restore mechanism that protects against accidental deletion also makes it hard to intentionally reset.\n\n## Design\n\n### Command Interface\n```\nbd reset [--hard] [--force] [--backup] [--dry-run] [--no-init]\n```\n\n| Flag | Effect |\n|------|--------|\n| `--hard` | Also remove from git index and commit |\n| `--force` | Skip confirmation prompt |\n| `--backup` | Create `.beads-backup-{timestamp}/` first |\n| `--dry-run` | Preview what would happen |\n| `--no-init` | Don't re-initialize after clearing |\n\n### Reset Levels\n1. **Soft Reset (default)** - Kill daemons, clear .beads/, re-init. Git history unchanged.\n2. **Hard Reset (`--hard`)** - Also git rm and commit the removal, then commit fresh state.\n\n### Implementation Flow\n1. Validate .beads/ exists\n2. If not --force: show impact summary, prompt confirmation\n3. If --backup: copy .beads/ to .beads-backup-{timestamp}/\n4. Kill daemons\n5. If --hard: git rm + commit\n6. rm -rf .beads/*\n7. If not --no-init: bd init (and git add+commit if --hard)\n8. Print summary\n\n### Safety Mechanisms\n- Confirmation prompt (skip with --force)\n- Impact summary (issue/tombstone counts)\n- Backup option\n- Dry-run preview\n- Git dirty check warning\n\n### Code Structure\n- `cmd/bd/reset.go` - CLI command\n- `internal/reset/` - Core logic package","status":"tombstone","priority":2,"issue_type":"epic","created_at":"2025-12-13T08:44:01.38379+11: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":"epic"}
|
||||
{"id":"bd-aydr.1","title":"Implement core reset package (internal/reset)","description":"Create the core reset logic in internal/reset/ package.\n\n## Responsibilities\n- ResetOptions struct with all flag options\n- CountImpact() - count issues/tombstones that will be deleted\n- ValidateState() - check .beads/ exists, check git dirty state\n- ExecuteReset() - main reset logic (without CLI concerns)\n- Integrate with daemon killall\n\n## Interface Design\n```go\ntype ResetOptions struct {\n Hard bool // Include git operations (git rm, commit)\n Backup bool // Create backup before reset\n DryRun bool // Preview only, don't execute\n SkipInit bool // Don't re-initialize after reset\n}\n\ntype ResetResult struct {\n IssuesDeleted int\n TombstonesDeleted int\n BackupPath string // if backup was created\n DaemonsKilled int\n}\n\ntype ImpactSummary struct {\n IssueCount int\n OpenCount int\n ClosedCount int\n TombstoneCount int\n HasUncommitted bool // git dirty state\n}\n\nfunc Reset(opts ResetOptions) (*ResetResult, error)\nfunc CountImpact() (*ImpactSummary, error)\nfunc ValidateState() error\n```\n\n## IMPORTANT: CLI vs Core Separation\n- `Force` (skip confirmation) is NOT in ResetOptions - that's a CLI concern\n- Core always executes when called; CLI decides whether to prompt first\n- Keep CLI-agnostic: no prompts, no colored output, no user interaction\n- Return errors for CLI to handle with user-friendly messages\n- Unit testable in isolation\n\n## Dependencies\n- Uses daemon.KillAllDaemons() from internal/daemon/\n- Calls bd init logic after reset (unless SkipInit)","status":"tombstone","priority":2,"issue_type":"task","created_at":"2025-12-13T08:44:50.145364+11:00","updated_at":"2025-12-25T01:21:01.952723-08:00","dependencies":[{"issue_id":"bd-aydr.1","depends_on_id":"bd-aydr","type":"parent-child","created_at":"2025-12-13T08:44:50.145775+11:00","created_by":"daemon"}],"deleted_at":"2025-12-25T01:21:01.952723-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"task"}
|
||||
@@ -351,6 +352,7 @@
|
||||
{"id":"bd-dju6","title":"Commit and push release","description":"git add -A \u0026\u0026 git commit \u0026\u0026 git push to trigger CI","status":"tombstone","priority":1,"issue_type":"task","created_at":"2025-12-21T13:52:33.065863-08:00","updated_at":"2025-12-21T13:53:49.957804-08:00","deleted_at":"2025-12-21T13:53:49.957804-08:00","deleted_by":"stevey","delete_reason":"manual delete","original_type":"task"}
|
||||
{"id":"bd-do8e","title":"Consolidate migrate-* commands under bd migrate","description":"## Task\nMove standalone migrate commands under `bd migrate` parent:\n- `bd migrate-hash-ids` → `bd migrate hash-ids`\n- `bd migrate-issues` → `bd migrate issues`\n- `bd migrate-sync` → `bd migrate sync`\n- `bd migrate-tombstones` → `bd migrate tombstones`\n\n## Implementation\n\n### 1. Update migrate.go\nAdd subcommands to migrateCmd:\n```go\nfunc init() {\n migrateCmd.AddCommand(migrateHashIDsCmd)\n migrateCmd.AddCommand(migrateIssuesCmd)\n migrateCmd.AddCommand(migrateSyncCmd)\n migrateCmd.AddCommand(migrateTombstonesCmd)\n}\n```\n\n### 2. Update each migrate_*.go file\n- Change `Use:` from `migrate-foo` to `foo`\n- Remove `rootCmd.AddCommand()` from init()\n\n### 3. Create hidden aliases for backwards compatibility\nIn main.go, add hidden top-level commands that forward to subcommands.\n\n### 4. Update docs\n- docs/DELETIONS.md - references `bd migrate-tombstones`\n- docs/CLI_REFERENCE.md - migration section\n\n## Files to modify\n- cmd/bd/migrate.go\n- cmd/bd/migrate_hash_ids.go \n- cmd/bd/migrate_issues.go\n- cmd/bd/migrate_sync.go\n- cmd/bd/migrate_tombstones.go\n- cmd/bd/main.go (aliases)\n","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-27T15:10:41.618026-08:00","created_by":"mayor","updated_at":"2025-12-27T16:01:32.021299-08:00","closed_at":"2025-12-27T16:01:32.021299-08:00"}
|
||||
{"id":"bd-dp4w","title":"Test message","description":"This is a test message body","status":"tombstone","priority":2,"issue_type":"message","created_at":"2025-12-16T18:11:58.467876-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":"message"}
|
||||
{"id":"bd-dpbm","title":"Test no validate","description":"Quick capture","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-01T19:24:58.637574-08:00","created_by":"beads/polecats/opal","updated_at":"2026-01-01T19:25:09.044121-08:00","closed_at":"2026-01-01T19:25:09.044121-08:00","close_reason":"Test issue cleanup"}
|
||||
{"id":"bd-dq74","title":"bd repair: Handle .beads/redirect files","description":"The bd repair command hardcodes .beads/beads.db path but doesn't follow .beads/redirect files like other commands do. This means repair won't work on clones that use redirected beads directories.\n\nFix: Check for .beads/redirect file and follow it to find the actual database location.","status":"closed","priority":2,"issue_type":"bug","created_at":"2025-12-29T12:47:53.089729-08:00","created_by":"stevey","updated_at":"2025-12-29T12:59:05.121303-08:00","closed_at":"2025-12-29T12:59:05.121303-08:00","close_reason":"Fixed in commit d7a67ad6"}
|
||||
{"id":"bd-dqck","title":"Version Bump: test-squash","description":"Release checklist for version test-squash. This molecule ensures all release steps are completed properly.","status":"tombstone","priority":1,"issue_type":"epic","created_at":"2025-12-21T13:52:33.065408-08:00","updated_at":"2025-12-21T13:53:41.946036-08:00","deleted_at":"2025-12-21T13:53:41.946036-08:00","deleted_by":"stevey","delete_reason":"manual delete","original_type":"epic"}
|
||||
{"id":"bd-dqu8","title":"Restart running daemons","description":"Kill and restart any running bd daemons to pick up new version: pkill -f 'bd daemon' \u0026\u0026 bd daemon --start","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-20T00:32:26.559311-08:00","updated_at":"2025-12-20T00:32:59.123766-08:00","closed_at":"2025-12-20T00:32:59.123766-08:00","dependencies":[{"issue_id":"bd-dqu8","depends_on_id":"bd-6s61","type":"parent-child","created_at":"2025-12-20T00:32:39.36213-08:00","created_by":"daemon"},{"issue_id":"bd-dqu8","depends_on_id":"bd-fgw3","type":"blocks","created_at":"2025-12-20T00:32:39.427846-08:00","created_by":"daemon"}]}
|
||||
@@ -673,7 +675,7 @@
|
||||
{"id":"bd-otf4","title":"Code Review: PR #481 - Context Engineering Optimizations","description":"Comprehensive code review of the merged context engineering PR (PR #481) that reduces MCP context usage by 80-90%.\n\n## Summary\nThe PR successfully implements lazy tool schema loading and minimal issue models to reduce context window usage. Overall implementation is solid and well-tested.\n\n## Positive Findings\n✅ Well-designed models (IssueMinimal, CompactedResult)\n✅ Comprehensive test coverage (28 tests, all passing)\n✅ Clear documentation and comments\n✅ Backward compatibility preserved (show() still returns full Issue)\n✅ Sensible defaults (COMPACTION_THRESHOLD=20, PREVIEW_COUNT=5)\n✅ Tool catalog complete with all 15 tools documented\n\n## Issues Identified\nSee linked issues for specific followup tasks.\n\n## Context Engineering Architecture\n- discover_tools(): List tool names only (~500 bytes vs ~15KB)\n- get_tool_info(name): Get specific tool details on-demand\n- IssueMinimal: Lightweight model for list views (~80 bytes vs ~400 bytes)\n- CompactedResult: Auto-compacts results with \u003e20 issues\n- _to_minimal(): Conversion function (efficient, no N+1 issues)","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-14T14:24:13.523532-08:00","updated_at":"2025-12-29T13:40:29.726141-08:00","closed_at":"2025-12-29T13:40:29.726141-08:00","close_reason":"Stale/spurious - test artifacts, merged PRs, or auto-close candidates"}
|
||||
{"id":"bd-otli","title":"Wait for CI to pass","description":"Monitor GitHub Actions - all checks must pass before release artifacts are built","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-19T22:56:03.022281-08:00","updated_at":"2025-12-20T00:49:51.928591-08:00","closed_at":"2025-12-20T00:25:52.635223-08:00","dependencies":[{"issue_id":"bd-otli","depends_on_id":"bd-6s61","type":"parent-child","created_at":"2025-12-19T22:56:15.097564-08:00","created_by":"daemon"},{"issue_id":"bd-otli","depends_on_id":"bd-7tuu","type":"blocks","created_at":"2025-12-19T22:56:23.360436-08:00","created_by":"daemon"}]}
|
||||
{"id":"bd-otyh","title":"Agent bead prefix mismatch: gt- vs bd- for beads polecat agents","description":"When spawning polecats in beads rig, gt sling tries to create agent beads with gt-beads-polecat-* prefix, but beads requires bd- prefix. Warning: 'issue ID gt-beads-polecat-obsidian does not match configured prefix bd'. Agent beads should use the rig's configured prefix.","status":"closed","priority":3,"issue_type":"bug","created_at":"2025-12-30T00:13:42.570237-08:00","created_by":"mayor","updated_at":"2025-12-30T18:12:30.982503-08:00","closed_at":"2025-12-30T16:57:00.673794-08:00","close_reason":"Fixed in gastown commit 05b1f30. Agent beads now use the rig's configured prefix from routes.jsonl instead of hardcoding 'gt-'. Modified polecat/manager.go and prime.go to look up the correct prefix."}
|
||||
{"id":"bd-ou35","title":"Opt-in template validation for issues","description":"## Summary\n\nAdd optional validation that issues include required sections based on type, without making it mandatory by default.\n\n## Background\n\nGH#821 proposed mandatory template validation, but that's too draconian for quick capture workflows. Instead, provide opt-in validation through multiple mechanisms.\n\n## Design\n\n### 1. `bd lint` command\n\nCheck issues for missing recommended sections:\n\n```bash\nbd lint # Lint all open issues\nbd lint bd-xxx # Lint specific issue\nbd lint --fix # Interactive: prompt to add missing sections\n```\n\nOutput:\n```\nbd-abc [bug]: Missing \"## Steps to Reproduce\"\nbd-def [task]: Missing \"## Acceptance Criteria\"\n\n2 issues with warnings\n```\n\n### 2. `--validate` flag on `bd create`\n\nOpt-in strict mode at creation time:\n\n```bash\nbd create -t bug --validate -d \"...\" # Fails if missing required sections\nbd create -t bug -d \"...\" # Succeeds (current behavior)\n```\n\n### 3. Section requirements by type\n\n| Type | Recommended Sections |\n|------|---------------------|\n| Bug | Steps to Reproduce, Acceptance Criteria |\n| Task/Feature | Acceptance Criteria |\n| Epic | Success Criteria |\n| Chore/Message | None |\n\nNote: \"Workaround\" dropped from GH#821 - not always applicable.\n\n### 4. Config option (future)\n\n```json\n// .beads/config.json\n{\n \"validation\": {\n \"on_create\": \"warn\" | \"error\" | \"none\",\n \"on_sync\": \"warn\" | \"error\" | \"none\"\n }\n}\n```\n\n### 5. Hook integration (future)\n\nPre-sync hook could run `bd lint` and warn/block based on config.\n\n## Implementation Order\n\n1. Add `RequiredSections()` to IssueType (internal/types)\n2. Add `ValidateTemplate()` function (internal/validation)\n3. Implement `bd lint` command\n4. Add `--validate` flag to `bd create`\n5. (Future) Config file support\n6. (Future) Hook integration\n\n## Acceptance Criteria\n\n- [ ] `bd lint` reports missing sections without blocking\n- [ ] `bd lint \u003cid\u003e` works on single issue\n- [ ] `bd create --validate` enforces sections\n- [ ] `bd create` without flag works as today\n- [ ] Clear, actionable error messages\n\n## References\n\n- GH#821: Original proposal (will close referencing this epic)","status":"open","priority":3,"issue_type":"epic","created_at":"2026-01-01T11:18:04.828755-08:00","created_by":"beads/crew/grip","updated_at":"2026-01-01T11:18:04.828755-08:00"}
|
||||
{"id":"bd-ou35","title":"Opt-in template validation for issues","description":"## Summary\n\nAdd optional validation that issues include required sections based on type, without making it mandatory by default.\n\n## Background\n\nGH#821 proposed mandatory template validation, but that's too draconian for quick capture workflows. Instead, provide opt-in validation through multiple mechanisms.\n\n## Design\n\n### 1. `bd lint` command\n\nCheck issues for missing recommended sections:\n\n```bash\nbd lint # Lint all open issues\nbd lint bd-xxx # Lint specific issue\nbd lint --fix # Interactive: prompt to add missing sections\n```\n\nOutput:\n```\nbd-abc [bug]: Missing \"## Steps to Reproduce\"\nbd-def [task]: Missing \"## Acceptance Criteria\"\n\n2 issues with warnings\n```\n\n### 2. `--validate` flag on `bd create`\n\nOpt-in strict mode at creation time:\n\n```bash\nbd create -t bug --validate -d \"...\" # Fails if missing required sections\nbd create -t bug -d \"...\" # Succeeds (current behavior)\n```\n\n### 3. Section requirements by type\n\n| Type | Recommended Sections |\n|------|---------------------|\n| Bug | Steps to Reproduce, Acceptance Criteria |\n| Task/Feature | Acceptance Criteria |\n| Epic | Success Criteria |\n| Chore/Message | None |\n\nNote: \"Workaround\" dropped from GH#821 - not always applicable.\n\n### 4. Config option (future)\n\n```json\n// .beads/config.json\n{\n \"validation\": {\n \"on_create\": \"warn\" | \"error\" | \"none\",\n \"on_sync\": \"warn\" | \"error\" | \"none\"\n }\n}\n```\n\n### 5. Hook integration (future)\n\nPre-sync hook could run `bd lint` and warn/block based on config.\n\n## Implementation Order\n\n1. Add `RequiredSections()` to IssueType (internal/types)\n2. Add `ValidateTemplate()` function (internal/validation)\n3. Implement `bd lint` command\n4. Add `--validate` flag to `bd create`\n5. (Future) Config file support\n6. (Future) Hook integration\n\n## Acceptance Criteria\n\n- [ ] `bd lint` reports missing sections without blocking\n- [ ] `bd lint \u003cid\u003e` works on single issue\n- [ ] `bd create --validate` enforces sections\n- [ ] `bd create` without flag works as today\n- [ ] Clear, actionable error messages\n\n## References\n\n- GH#821: Original proposal (will close referencing this epic)","status":"closed","priority":3,"issue_type":"epic","assignee":"beads/polecats/opal","created_at":"2026-01-01T11:18:04.828755-08:00","created_by":"beads/crew/grip","updated_at":"2026-01-01T19:25:09.99215-08:00","closed_at":"2026-01-01T19:25:09.99215-08:00","close_reason":"All P3 acceptance criteria complete. P4 items (config, hooks) are future work."}
|
||||
{"id":"bd-ov1u","title":"Clean repo cruft: bd_new, @AGENTS.md, state.json","description":"Remove tracked cruft:\n- git rm bd_new (31MB old binary)\n- git rm @AGENTS.md (duplicate, was 'removed' but still tracked)\n- Add state.json to .gitignore, git rm --cached state.json\n- Consider moving history/EPHEMERAL_MOLECULES_DESIGN.md to docs/ or removing","status":"closed","priority":2,"issue_type":"chore","assignee":"beads/polecats/obsidian","created_at":"2026-01-01T11:09:49.833027-08:00","created_by":"mayor","updated_at":"2026-01-01T11:12:22.320022-08:00","closed_at":"2026-01-01T11:12:22.320022-08:00","close_reason":"Removed bd_new (31MB) and @AGENTS.md. state.json already gitignored, history/EPHEMERAL_MOLECULES_DESIGN.md did not exist."}
|
||||
{"id":"bd-ox1o","title":"Code Review Round 2: Beads Refactoring","description":"Second pass code review of Beads codebase. Found 10 HIGH/MEDIUM priority issues.\n\n**HIGH (P2):**\n- bd-6dnt: Duplicated IssueDetails struct (4 definitions)\n- bd-vqh9: init.go is 1928 lines\n- bd-it19: show.go is 1592 lines\n\n**MEDIUM (P3):**\n- bd-qobn: 20+ global variables in main.go\n- bd-0e02: Inconsistent error handling patterns\n- bd-g6m5: Mixed daemon/direct mode logic\n- bd-qe7j: Incomplete TODOs in formula/types.go\n- bd-4sxh: Issue struct ~100 fields\n- bd-yuxq: 262 uses of interface{}\n- bd-jbqx: Repeated validation patterns","status":"closed","priority":2,"issue_type":"epic","created_at":"2025-12-28T19:00:15.483532-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-29T13:40:29.721916-08:00","closed_at":"2025-12-29T13:40:29.721916-08:00","close_reason":"Stale/spurious - test artifacts, merged PRs, or auto-close candidates"}
|
||||
{"id":"bd-oxgi","title":"Add mol_type schema field to beads","description":"Add mol_type field to distinguish molecule types (swarm/patrol/work).\n\n## Context\nSwarms need to be distinguishable from regular work molecules. The mol_type field enables:\n- Filtering: bd list --type=swarm \n- Queries: Find all active swarm molecules\n- Coordinator logic: Different handling for different mol types\n\n## Implementation\n1. Add mol_type column to SQLite schema (nullable, default null = work)\n2. Add mol_type to JSONL format\n3. Update create command to accept --mol-type\n4. Update list/ready commands to filter by mol_type\n5. Values: 'swarm', 'patrol', 'work', null (null = work)\n\n## Reference\n~/gt/docs/swarm-architecture.md - 'Data Model' section\n\n## Acceptance\n- bd create --mol-type=swarm works\n- bd list --mol-type=swarm filters correctly\n- Existing molecules work unchanged (backward compatible)","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-28T19:11:07.616818-08:00","created_by":"mayor","updated_at":"2025-12-28T19:50:33.213538-08:00","closed_at":"2025-12-28T19:50:33.213538-08:00"}
|
||||
@@ -793,7 +795,7 @@
|
||||
{"id":"bd-t3en","title":"Merge: bd-d28c","description":"branch: polecat/capable\ntarget: main\nsource_issue: bd-d28c\nrig: beads","status":"closed","priority":1,"issue_type":"merge-request","created_at":"2025-12-23T20:43:16.997802-08:00","updated_at":"2025-12-23T21:21:57.694201-08:00","closed_at":"2025-12-23T21:21:57.694201-08:00"}
|
||||
{"id":"bd-t4sb","title":"Work on beads-d8h: Fix prefix mismatch false positive wit...","description":"Work on beads-d8h: Fix prefix mismatch false positive with multi-hyphen prefixes like 'asianops-audit-' (GH#422). When done, submit MR (not PR) to integration branch for Refinery.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-19T22:56:19.545069-08:00","updated_at":"2025-12-19T23:28:32.429127-08:00","closed_at":"2025-12-19T23:21:45.471711-08:00"}
|
||||
{"id":"bd-t4u1","title":"False positive detection by Kaspersky Antivirus (Trojan)","description":"Kaspersky Antivirus falsely detects beads (bd.exe v0.23.1) as a Trojan (PDM:Trojan.Win32.Generic) and removes it.\nEvent: Malicious object detected\nComponent: System Watcher\nObject name: bd.exe\n","status":"closed","priority":1,"issue_type":"task","created_at":"2025-11-20T18:56:12.498187-05:00","updated_at":"2025-12-23T23:47:23.182018-08:00","closed_at":"2025-12-23T23:47:23.182018-08:00"}
|
||||
{"id":"bd-t7jq","title":"Add validation config support","description":"Future: Add .beads/config.json support for validation settings (on_create, on_sync: warn|error|none).","status":"open","priority":4,"issue_type":"task","created_at":"2026-01-01T11:19:09.96198-08:00","created_by":"beads/crew/grip","updated_at":"2026-01-01T11:19:09.96198-08:00","dependencies":[{"issue_id":"bd-t7jq","depends_on_id":"bd-ou35","type":"parent-child","created_at":"2026-01-01T11:19:22.7728-08:00","created_by":"beads/crew/grip"},{"issue_id":"bd-t7jq","depends_on_id":"bd-gn5r","type":"blocks","created_at":"2026-01-01T11:19:23.985574-08:00","created_by":"beads/crew/grip"}]}
|
||||
{"id":"bd-t7jq","title":"Add validation config support","description":"Future: Add .beads/config.json support for validation settings (on_create, on_sync: warn|error|none).","status":"hooked","priority":4,"issue_type":"task","assignee":"beads/polecats/topaz","created_at":"2026-01-01T11:19:09.96198-08:00","created_by":"beads/crew/grip","updated_at":"2026-01-01T19:22:58.008828-08:00","dependencies":[{"issue_id":"bd-t7jq","depends_on_id":"bd-ou35","type":"parent-child","created_at":"2026-01-01T11:19:22.7728-08:00","created_by":"beads/crew/grip"},{"issue_id":"bd-t7jq","depends_on_id":"bd-gn5r","type":"blocks","created_at":"2026-01-01T11:19:23.985574-08:00","created_by":"beads/crew/grip"}]}
|
||||
{"id":"bd-ta4r","title":"Wisp operations should auto-bypass daemon","description":"During the v0.39.1 release, every wisp operation required --no-daemon flag:\n\nbd --no-daemon mol wisp create beads-release --var version=0.39.1\nbd --no-daemon close bd-eph-xxx\nbd --no-daemon mol burn bd-eph-bv2\n\nSince wisps are ephemeral (Ephemeral=true) and never exported to JSONL, they are inherently local-only. The daemon cannot help with them anyway.\n\nProposal: When operating on bd-eph-* issues or wisp subcommands, auto-detect and bypass the daemon. This would:\n- Reduce friction in wisp workflows\n- Prevent accidental daemon use that would fail anyway\n- Make the ephemeral nature more obvious","status":"closed","priority":3,"issue_type":"feature","created_at":"2025-12-27T22:51:24.409066-08:00","created_by":"beads/crew/emma","updated_at":"2025-12-28T02:10:30.123755-08:00","closed_at":"2025-12-28T02:10:30.123755-08:00"}
|
||||
{"id":"bd-tbz3","title":"bd init UX Improvements","description":"bd init leaves users with incomplete setup, requiring manual bd doctor --fix. Issues found: (1) git hooks not installed if user declines prompt, (2) no auto-migration when CLI is upgraded, (3) stale merge driver configs from old versions. Fix by making bd init more robust with better defaults and auto-migration.","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-11-21T23:16:00.333543-08:00","updated_at":"2025-12-23T04:20:51.88847-08:00","closed_at":"2025-12-23T04:20:51.88847-08:00"}
|
||||
{"id":"bd-tcvh","title":"Test prefix beads","status":"tombstone","priority":2,"issue_type":"task","created_at":"2025-12-27T14:24:41.707092-08:00","created_by":"stevey","updated_at":"2025-12-27T14:24:50.421598-08:00","deleted_at":"2025-12-27T14:24:50.421598-08:00","deleted_by":"daemon","delete_reason":"delete","original_type":"task"}
|
||||
|
||||
Reference in New Issue
Block a user