chore: Update issue tracker and documentation
- Close completed test issues (bd-5, bd-51) - Add versioning strategy task (bd-65) - Add version sync bug (bd-66) - Update CLAUDE.md to reflect MCP server implementation status 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -42,9 +42,9 @@
|
||||
{"id":"bd-47","title":"Test incremental export","description":"Testing bd-39 implementation","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-14T02:51:52.200724-07:00","updated_at":"2025-10-14T02:51:52.200724-07:00"}
|
||||
{"id":"bd-48","title":"Test incremental 2","description":"","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-14T02:51:52.200786-07:00","updated_at":"2025-10-14T02:51:52.200786-07:00"}
|
||||
{"id":"bd-49","title":"Final test","description":"Testing with new binary","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-14T02:51:52.200877-07:00","updated_at":"2025-10-14T02:51:52.200877-07:00"}
|
||||
{"id":"bd-5","title":"Test issue","description":"Testing prefix","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-12T00:19:15.407647-07:00","updated_at":"2025-10-12T00:19:15.407647-07:00","dependencies":[{"issue_id":"bd-5","depends_on_id":"bd-8","type":"parent-child","created_at":"2025-10-14T02:51:52.202237-07:00","created_by":"import"}]}
|
||||
{"id":"bd-5","title":"Test issue","description":"Testing prefix","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-12T00:19:15.407647-07:00","updated_at":"2025-10-14T13:39:55.828804-07:00","closed_at":"2025-10-14T13:39:55.828804-07:00","dependencies":[{"issue_id":"bd-5","depends_on_id":"bd-8","type":"parent-child","created_at":"2025-10-14T02:51:52.202237-07:00","created_by":"import"}]}
|
||||
{"id":"bd-50","title":"Test label dirty tracking","description":"","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-14T02:51:52.201021-07:00","updated_at":"2025-10-14T02:51:52.201021-07:00"}
|
||||
{"id":"bd-51","title":"Test hash-based import","description":"","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-14T02:53:38.351403-07:00","updated_at":"2025-10-14T02:53:38.351403-07:00"}
|
||||
{"id":"bd-51","title":"Test hash-based import","description":"","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-14T02:53:38.351403-07:00","updated_at":"2025-10-14T13:39:56.958248-07:00","closed_at":"2025-10-14T13:39:56.958248-07:00"}
|
||||
{"id":"bd-52","title":"Create Claude Code plugin for beads","description":"Package beads as a Claude Code plugin for easy installation via /plugin command.\n\nContext: GitHub issue #28 - https://github.com/steveyegge/beads/issues/28\n\nCurrent state:\n- MCP server exists in integrations/beads-mcp/\n- No plugin packaging yet\n\nDeliverables:\n1. .claude-plugin/plugin.json with metadata\n2. .claude-plugin/marketplace.json for distribution\n3. Custom slash commands (/bd-ready, /bd-create, /bd-show, etc.)\n4. Bundle MCP server configuration\n5. Optional: Pre-configured hooks for auto-sync\n6. Documentation for installation and usage\n\nBenefits:\n- Makes beads instantly discoverable in Claude Code ecosystem\n- Single-command installation vs. manual setup\n- Bundled cohesive experience\n- Lowers adoption barrier significantly\n\nReferences:\n- https://www.anthropic.com/news/claude-code-plugins\n- https://docs.claude.com/en/docs/claude-code/plugins","status":"closed","priority":1,"issue_type":"feature","created_at":"2025-10-14T12:47:11.917393-07:00","updated_at":"2025-10-14T12:59:39.974612-07:00","closed_at":"2025-10-14T12:59:39.974612-07:00"}
|
||||
{"id":"bd-53","title":"Research Claude Code plugin structure and requirements","description":"Study the plugin format, required files, and best practices.\n\nTasks:\n- Review official plugin documentation\n- Examine example plugins if available\n- Document plugin.json schema\n- Understand marketplace.json requirements\n- Identify slash command format","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-14T12:47:26.729256-07:00","updated_at":"2025-10-14T12:55:23.358165-07:00","closed_at":"2025-10-14T12:55:23.358165-07:00","dependencies":[{"issue_id":"bd-53","depends_on_id":"bd-52","type":"parent-child","created_at":"2025-10-14T12:47:26.729676-07:00","created_by":"stevey"}]}
|
||||
{"id":"bd-54","title":"Create plugin metadata files","description":"Create .claude-plugin/plugin.json and marketplace.json.\n\nRequirements:\n- Name, description, version, author\n- MCP server configuration bundling\n- License and repository info\n- Installation instructions","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-14T12:47:27.743905-07:00","updated_at":"2025-10-14T12:55:59.029894-07:00","closed_at":"2025-10-14T12:55:59.029894-07:00","dependencies":[{"issue_id":"bd-54","depends_on_id":"bd-52","type":"parent-child","created_at":"2025-10-14T12:47:27.74444-07:00","created_by":"stevey"}]}
|
||||
@@ -59,6 +59,8 @@
|
||||
{"id":"bd-62","title":"Document hierarchical blocking behavior in README","description":"The fix for bd-58 changes user-visible behavior: children of blocked epics are now automatically blocked.\n\n**What needs documenting:**\n1. README.md dependency section should explain blocking propagation\n2. Clarify that 'blocks' + 'parent-child' together create transitive blocking\n3. Note that 'related' and 'discovered-from' do NOT propagate blocking\n4. Add example showing epic → child blocking propagation\n\n**Example to add:**\n```bash\n# If epic is blocked, children are too\nbd create \"Epic 1\" -t epic -p 1\nbd create \"Task 1\" -t task -p 1\nbd dep add task-1 epic-1 --type parent-child\n\n# Block the epic\nbd create \"Blocker\" -t task -p 0\nbd dep add epic-1 blocker-1 --type blocks\n\n# Now both epic-1 AND task-1 are blocked\nbd ready # Neither will show up\n```","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-14T12:55:52.895182-07:00","updated_at":"2025-10-14T13:10:38.482538-07:00","closed_at":"2025-10-14T13:10:38.482538-07:00"}
|
||||
{"id":"bd-63","title":"Add EXPLAIN QUERY PLAN tests for ready work query","description":"Verify that the hierarchical blocking query uses proper indexes and doesn't do full table scans.\n\n**Queries to analyze:**\n1. The recursive CTE (both base case and recursive case)\n2. The final SELECT with NOT EXISTS\n3. Impact of various filters (status, priority, assignee)\n\n**Implementation:**\nAdd test function that:\n- Runs EXPLAIN QUERY PLAN on GetReadyWork query\n- Parses output to verify no SCAN TABLE operations\n- Documents expected query plan in comments\n- Fails if query plan degrades\n\n**Benefits:**\n- Catch performance regressions in tests\n- Document expected query behavior\n- Ensure indexes are being used\n\nRelated to: bd-59 (composite index on depends_on_id, type)","status":"open","priority":3,"issue_type":"task","created_at":"2025-10-14T12:55:54.023115-07:00","updated_at":"2025-10-14T12:55:54.023115-07:00"}
|
||||
{"id":"bd-64","title":"Verify and test Claude Code plugin","description":"Address remaining items from code review:\n\nCritical:\n1. Test plugin installation locally with /plugin marketplace add\n2. Verify ${CLAUDE_PLUGIN_ROOT} variable works correctly\n3. Test each slash command works\n4. Test @task-agent execution\n5. Verify MCP server connects properly\n\nDocumentation:\n1. Clarify 'one-command installation' vs prerequisites\n2. Add note about plugin development status\n3. Verify all paths and examples work\n\nNice-to-have:\n1. Add icon for marketplace (optional)\n2. Add categories field to plugin.json\n3. Add engines field for version compatibility","status":"open","priority":1,"issue_type":"task","created_at":"2025-10-14T13:03:54.529639-07:00","updated_at":"2025-10-14T13:03:54.529639-07:00"}
|
||||
{"id":"bd-65","title":"Document versioning and release strategy","description":"Create comprehensive versioning strategy for beads ecosystem.\n\nComponents to document:\n1. bd CLI (Go binary) - main version number\n2. Plugin (Claude Code) - tracks CLI version\n3. MCP server (Python) - bundled with plugin\n4. Release workflow - how to sync all three\n\nDecisions to make:\n- Should plugin.json auto-update from bd CLI version?\n- Should we have a VERSION file at repo root?\n- How to handle breaking changes across components?\n- What's the update notification strategy?\n\nReferences:\n- plugin.json engines field now requires bd \u003e=0.9.0\n- /bd-version command added for checking compatibility\n- PLUGIN.md now documents update workflow","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-14T13:28:30.157646-07:00","updated_at":"2025-10-14T13:28:30.157646-07:00"}
|
||||
{"id":"bd-66","title":"Sync versions to 0.9.2 across all components","description":"Version mismatch discovered: bd CLI is 0.9.2 but other components still at 0.9.0 or 1.0.0.\n\nCurrent state:\n- bd CLI (cmd/bd/version.go): 0.9.2 ✓\n- Plugin (.claude-plugin/plugin.json): 0.9.0 ✗\n- MCP Server (integrations/beads-mcp): 1.0.0 ✗\n- README.md: 0.9.0 ✗\n\nFiles to update:\n1. .claude-plugin/plugin.json\n2. integrations/beads-mcp/pyproject.toml\n3. README.md (all mentions)\n4. PLUGIN.md (if any mentions)\n5. CHANGELOG.md (add 0.9.1 and 0.9.2 entries)\n\nRoot cause: Version bumps only updated version.go, not other components.\nSolution needed: Script or process to sync versions across all files.","status":"open","priority":0,"issue_type":"bug","created_at":"2025-10-14T13:37:38.177053-07:00","updated_at":"2025-10-14T13:37:38.177053-07:00"}
|
||||
{"id":"bd-7","title":"Add performance benchmarks document","description":"Document actual performance metrics with hyperfine tests","status":"open","priority":3,"issue_type":"task","created_at":"2025-10-14T02:51:52.197257-07:00","updated_at":"2025-10-14T02:51:52.201178-07:00","dependencies":[{"issue_id":"bd-7","depends_on_id":"bd-8","type":"parent-child","created_at":"2025-10-14T02:51:52.202398-07:00","created_by":"import"}]}
|
||||
{"id":"bd-8","title":"Reach 1.0 release milestone","description":"Stabilize API, finalize documentation, comprehensive testing","status":"open","priority":1,"issue_type":"epic","created_at":"2025-10-14T02:51:52.197347-07:00","updated_at":"2025-10-14T02:51:52.201254-07:00"}
|
||||
{"id":"bd-9","title":"Build collision resolution tooling for distributed branch workflows","description":"When branches diverge and both create issues, auto-incrementing IDs collide on merge. Build excellent tooling to detect collisions during import, auto-renumber issues with fewer dependencies, update all references in descriptions and dependency links, and provide clear user feedback. Goal: keep beautiful brevity of numeric IDs (bd-302) while handling distributed creation gracefully.","status":"in_progress","priority":1,"issue_type":"feature","created_at":"2025-10-14T02:51:52.197433-07:00","updated_at":"2025-10-14T02:51:52.201328-07:00"}
|
||||
|
||||
@@ -181,7 +181,7 @@ Run `bd stats` to see overall progress.
|
||||
- **Core CLI**: Mature, but always room for polish
|
||||
- **Examples**: Growing collection of agent integrations
|
||||
- **Documentation**: Comprehensive but can always improve
|
||||
- **MCP Server**: Planned (see bd-5)
|
||||
- **MCP Server**: Implemented at `integrations/beads-mcp/` with Claude Code plugin
|
||||
- **Migration Tools**: Planned (see bd-6)
|
||||
|
||||
### 1.0 Milestone
|
||||
|
||||
Reference in New Issue
Block a user