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

Close bd-306 (implemented daemon/auto-sync instead)

Browse Source 
Amp-Thread-ID: https://ampcode.com/threads/T-6185b498-94d8-4034-b5e6-fe9bd3075592
Co-authored-by: Amp <amp@ampcode.com>
This commit is contained in:
Steve Yegge
2025-10-16 14:24:26 -07:00
parent a3023cd42c
commit 5bfecf85f0
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
.beads/issues.jsonl
View File

@@ -221,6 +221,7 @@
{"id":"bd-299","title":"Phase 4: Add metrics and monitoring","description":"Add metrics collection and monitoring for gateway operations and sync performance.","design":"Metrics to collect:\n- API request count and latency\n- Sync operation count and duration\n- Conflict resolution count\n- WebSocket connection count\n- Git operation duration\n- Database query performance\n\nExpose metrics:\n- Prometheus format at /metrics\n- JSON format at /api/metrics\n\nOptional: Grafana dashboard template.","acceptance_criteria":"- Metrics collection implemented\n- Prometheus exposition format\n- Key metrics covered (requests, latency, sync)\n- /metrics endpoint\n- /api/metrics JSON endpoint\n- Grafana dashboard template\n- Documentation in MONITORING.md\n\n---","status":"open","priority":3,"issue_type":"feature","created_at":"2025-10-16T11:01:26.971795-07:00","updated_at":"2025-10-16T13:19:06.922693-07:00","dependencies":[{"issue_id":"bd-299","depends_on_id":"bd-395","type":"blocks","created_at":"2025-10-16T13:19:06.76523-07:00","created_by":"import-remap"},{"issue_id":"bd-299","depends_on_id":"bd-436","type":"blocks","created_at":"2025-10-16T13:36:12.873825-07:00","created_by":"import-remap"},{"issue_id":"bd-299","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T13:36:32.978444-07:00","created_by":"auto-import"}]}
{"id":"bd-3","title":"Normal task","description":"","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-14T14:43:06.912905-07:00","updated_at":"2025-10-16T10:36:49.33175-07:00"}
{"id":"bd-30","title":"Remove unused issueMap in scoreCollisions","description":"scoreCollisions() creates issueMap and populates it (lines 135-138) but never uses it. Either remove it or add a TODO comment explaining future use. Located in collision.go:135-138. Cosmetic cleanup.","status":"open","priority":4,"issue_type":"chore","created_at":"2025-10-14T14:43:06.913242-07:00","updated_at":"2025-10-16T10:36:49.337317-07:00"}
<<<<<<< HEAD
{"id":"bd-300","title":"Phase 4: Create performance benchmarks","description":"Create comprehensive performance benchmarks for sync operations and gateway API.","design":"Benchmarks for:\n1. JSONL import/export performance\n2. Collision detection performance\n3. Three-way merge performance\n4. Gateway API latency\n5. WebSocket throughput\n6. Concurrent client handling\n7. Large database operations (10k+ issues)\n\nUse Go benchmarking and profiling tools.\n\nTrack performance over time in CI.","acceptance_criteria":"- Benchmark suite implemented\n- All key operations benchmarked\n- CPU and memory profiling\n- Large database benchmarks\n- Concurrent operation benchmarks\n- CI integration for regression detection\n- Performance baseline documented\n- Documentation in PERFORMANCE.md\n\n---","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T11:01:26.9723-07:00","updated_at":"2025-10-16T13:19:06.923173-07:00","dependencies":[{"issue_id":"bd-300","depends_on_id":"bd-395","type":"blocks","created_at":"2025-10-16T13:19:06.786999-07:00","created_by":"import-remap"},{"issue_id":"bd-300","depends_on_id":"bd-436","type":"blocks","created_at":"2025-10-16T13:36:12.89076-07:00","created_by":"import-remap"},{"issue_id":"bd-300","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T13:36:32.9791-07:00","created_by":"auto-import"}]}
{"id":"bd-301","title":"Phase 4: Add multi-gateway federation (optional)","description":"Add support for federating multiple gateway instances for distributed team workflows.","design":"Federation allows:\n- Multiple gateways sync with each other\n- Each gateway has authoritative set of issues\n- Peer-to-peer sync protocol\n- Conflict resolution across gateways\n\nArchitecture:\n- Gateway-to-gateway API\n- Peer discovery\n- Sync protocol between gateways\n- Distributed conflict resolution\n\nComplex feature - only if team usage emerges.","acceptance_criteria":"- Gateway federation protocol designed\n- Peer discovery mechanism\n- Gateway-to-gateway sync\n- Distributed conflict resolution\n- Tests for federation\n- Documentation in FEDERATION.md\n\n---","status":"open","priority":4,"issue_type":"feature","created_at":"2025-10-16T11:01:26.97242-07:00","updated_at":"2025-10-16T13:19:06.923471-07:00","dependencies":[{"issue_id":"bd-301","depends_on_id":"bd-395","type":"blocks","created_at":"2025-10-16T13:19:06.762023-07:00","created_by":"import-remap"},{"issue_id":"bd-301","depends_on_id":"bd-436","type":"blocks","created_at":"2025-10-16T13:36:12.895826-07:00","created_by":"import-remap"},{"issue_id":"bd-301","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T13:36:32.979839-07:00","created_by":"auto-import"}]}
{"id":"bd-302","title":"Phase 4: Create production deployment guide","description":"Create comprehensive production deployment guide for running gateway in production environments.","design":"Guide should cover:\n- Deployment options (Docker, Kubernetes, systemd)\n- Security best practices\n- Monitoring and alerting\n- Backup and recovery\n- Scaling considerations\n- Troubleshooting\n- Maintenance procedures","acceptance_criteria":"- DEPLOYMENT.md created\n- Docker deployment guide\n- Kubernetes manifests\n- Systemd service file\n- Security hardening checklist\n- Monitoring setup guide\n- Backup procedures\n- Troubleshooting section\n- Scaling recommendations\n- Links from README.md\n\n---","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T11:01:26.972547-07:00","updated_at":"2025-10-16T13:19:06.923645-07:00","dependencies":[{"issue_id":"bd-302","depends_on_id":"bd-395","type":"blocks","created_at":"2025-10-16T13:19:06.740597-07:00","created_by":"import-remap"},{"issue_id":"bd-302","depends_on_id":"bd-436","type":"blocks","created_at":"2025-10-16T13:36:12.874279-07:00","created_by":"import-remap"},{"issue_id":"bd-302","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T13:36:32.981585-07:00","created_by":"auto-import"}]}
@@ -231,6 +232,18 @@
{"id":"bd-307","title":"Fix circular dependency detection and prevention","description":"Implement robust detection, prevention, and user guidance for circular dependencies that cross edge types. Current system only prevents cycles within \"blocks\" type dependencies, allowing cross-type cycles (e.g., A blocks B, B parent-child A) that can hide work from ready list and confuse dependency visualization.","design":"Analysis shows that cycle prevention is type-specific (blocks only) while detection is type-agnostic. All current operations are safe from infinite loops (depth-limited), but semantic confusion and future maintenance hazards exist. Need validation, warnings, and potentially full cross-type prevention.","acceptance_criteria":"- Cross-type cycles are prevented or warned about\n- Semantic validation prevents child→parent dependencies\n- Users receive clear diagnostic messages\n- Documentation explains cycle handling behavior\n- All existing safe operations remain protected","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-10-16T11:01:26.973279-07:00","updated_at":"2025-10-16T13:37:34.910129-07:00","closed_at":"2025-10-16T13:37:34.910129-07:00"}
{"id":"bd-308","title":"Add semantic validation for parent-child dependency direction","description":"Prevent backwards parent-child dependencies where child tasks depend on their parent epics. This is semantically incorrect - parents should depend on children completing, not the reverse.","design":"Add validation in AddDependency that checks if dep.Type == DepParentChild and validates the direction is correct (parent depends on child, not child on parent). Reject with clear error message if direction is backwards.","acceptance_criteria":"- Child→parent dependencies are rejected with clear error\n- Parent→child dependencies work as expected\n- Error message explains correct direction\n- Tests cover both valid and invalid cases","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-16T11:01:26.9734-07:00","updated_at":"2025-10-16T13:19:25.892685-07:00","closed_at":"2025-10-16T13:19:25.892685-07:00","dependencies":[{"issue_id":"bd-308","depends_on_id":"bd-434","type":"parent-child","created_at":"2025-10-16T13:36:12.893541-07:00","created_by":"import-remap"},{"issue_id":"bd-308","depends_on_id":"bd-307","type":"parent-child","created_at":"2025-10-16T13:36:32.984028-07:00","created_by":"auto-import"}]}
{"id":"bd-309","title":"Add diagnostic warnings when cycles are detected after dep add","description":"Run DetectCycles() after adding dependencies and warn users if cycles exist. Provide clear, actionable messages about which issues form the cycle and potential impact on ready work visibility.","design":"In bd dep add command, after successful dependency addition, call DetectCycles(). If cycles found, print warning to stderr showing cycle path and explanation. Include suggestion to run 'bd dep cycles' for full analysis.","acceptance_criteria":"- Warnings appear after dep add when cycles exist\n- Warning shows cycle path clearly\n- Explains impact on ready work calculation\n- Suggests next steps for user\n- Does not block operation (warning only)","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-16T11:01:26.973528-07:00","updated_at":"2025-10-16T13:19:25.918179-07:00","closed_at":"2025-10-16T13:19:25.918179-07:00","dependencies":[{"issue_id":"bd-309","depends_on_id":"bd-434","type":"parent-child","created_at":"2025-10-16T13:36:12.873354-07:00","created_by":"import-remap"},{"issue_id":"bd-309","depends_on_id":"bd-307","type":"parent-child","created_at":"2025-10-16T13:36:32.984535-07:00","created_by":"auto-import"}]}
=======
{"id":"bd-300","title":"Phase 4: Create performance benchmarks","description":"Create comprehensive performance benchmarks for sync operations and gateway API.","design":"Benchmarks for:\n1. JSONL import/export performance\n2. Collision detection performance\n3. Three-way merge performance\n4. Gateway API latency\n5. WebSocket throughput\n6. Concurrent client handling\n7. Large database operations (10k+ issues)\n\nUse Go benchmarking and profiling tools.\n\nTrack performance over time in CI.","acceptance_criteria":"- Benchmark suite implemented\n- All key operations benchmarked\n- CPU and memory profiling\n- Large database benchmarks\n- Concurrent operation benchmarks\n- CI integration for regression detection\n- Performance baseline documented\n- Documentation in PERFORMANCE.md\n\n---","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T01:40:06.20052-07:00","updated_at":"2025-10-16T10:36:49.338002-07:00","dependencies":[{"issue_id":"bd-300","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T01:40:06.423731-07:00","created_by":"stevey"}]}
{"id":"bd-301","title":"Phase 4: Add multi-gateway federation (optional)","description":"Add support for federating multiple gateway instances for distributed team workflows.","design":"Federation allows:\n- Multiple gateways sync with each other\n- Each gateway has authoritative set of issues\n- Peer-to-peer sync protocol\n- Conflict resolution across gateways\n\nArchitecture:\n- Gateway-to-gateway API\n- Peer discovery\n- Sync protocol between gateways\n- Distributed conflict resolution\n\nComplex feature - only if team usage emerges.","acceptance_criteria":"- Gateway federation protocol designed\n- Peer discovery mechanism\n- Gateway-to-gateway sync\n- Distributed conflict resolution\n- Tests for federation\n- Documentation in FEDERATION.md\n\n---","status":"open","priority":4,"issue_type":"feature","created_at":"2025-10-16T01:40:06.429639-07:00","updated_at":"2025-10-16T10:36:49.339239-07:00","dependencies":[{"issue_id":"bd-301","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T01:40:06.443166-07:00","created_by":"stevey"}]}
{"id":"bd-302","title":"Phase 4: Create production deployment guide","description":"Create comprehensive production deployment guide for running gateway in production environments.","design":"Guide should cover:\n- Deployment options (Docker, Kubernetes, systemd)\n- Security best practices\n- Monitoring and alerting\n- Backup and recovery\n- Scaling considerations\n- Troubleshooting\n- Maintenance procedures","acceptance_criteria":"- DEPLOYMENT.md created\n- Docker deployment guide\n- Kubernetes manifests\n- Systemd service file\n- Security hardening checklist\n- Monitoring setup guide\n- Backup procedures\n- Troubleshooting section\n- Scaling recommendations\n- Links from README.md\n\n---","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T01:40:06.465354-07:00","updated_at":"2025-10-16T10:36:49.344116-07:00","dependencies":[{"issue_id":"bd-302","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T01:40:06.475326-07:00","created_by":"stevey"}]}
{"id":"bd-303","title":"Update README.md with git-sync overview","description":"Update main README.md to include overview of git-sync feature and link to detailed documentation.","design":"Add new section: \"Multi-Device Sync\"\n\nContent:\n- Brief overview of git-based sync\n- Link to SYNC.md for details\n- Link to GATEWAY.md for gateway mode\n- Quick start examples\n- Configuration options\n\nKeep brief - detailed docs in separate files.","acceptance_criteria":"- README.md updated with sync section\n- Links to SYNC.md and GATEWAY.md\n- Quick start examples\n- Configuration overview\n- Maintains existing structure\n- All links working\n\n---","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T01:40:06.534879-07:00","updated_at":"2025-10-16T10:36:49.347185-07:00","dependencies":[{"issue_id":"bd-303","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T01:40:06.540695-07:00","created_by":"stevey"}]}
{"id":"bd-304","title":"Create SYNC.md comprehensive guide","description":"Create detailed SYNC.md guide covering all aspects of git-based synchronization.","design":"Sections:\n1. Introduction\n2. Quick Start\n3. Manual Git Workflow\n4. bd sync Command\n5. bd daemon Background Sync\n6. Git Hooks\n7. Conflict Resolution\n8. Best Practices\n9. Troubleshooting\n10. FAQ\n\nInclude examples, code snippets, and diagrams.","acceptance_criteria":"- SYNC.md created with all sections\n- Quick start guide for new users\n- Detailed workflow examples\n- Conflict resolution guide\n- Best practices section\n- Troubleshooting with solutions\n- FAQ with common questions\n- Code examples working\n- Links from README.md\n\n---","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T01:40:06.562753-07:00","updated_at":"2025-10-16T10:36:49.352494-07:00","dependencies":[{"issue_id":"bd-304","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T01:40:06.59025-07:00","created_by":"stevey"}]}
{"id":"bd-305","title":"Create API.md for gateway API documentation","description":"Create comprehensive API.md documenting the gateway REST API and WebSocket protocol.","design":"Sections:\n1. Introduction\n2. Authentication\n3. REST Endpoints\n4. WebSocket Protocol\n5. Error Handling\n6. Rate Limits\n7. Examples\n\nFor each endpoint:\n- URL and method\n- Request parameters\n- Request body schema\n- Response schema\n- Error responses\n- Code example","acceptance_criteria":"- API.md created with all sections\n- All endpoints documented\n- Request/response schemas\n- WebSocket protocol docs\n- Error codes and handling\n- Rate limit documentation\n- Examples in multiple languages\n- Links from README.md\n\n---","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T01:40:06.631897-07:00","updated_at":"2025-10-16T10:36:49.352984-07:00","dependencies":[{"issue_id":"bd-305","depends_on_id":"bd-251","type":"blocks","created_at":"2025-10-16T01:40:06.672163-07:00","created_by":"stevey"}]}
{"id":"bd-306","title":"Close GH-11 (Docker support) or update with sync approach","description":"Resolve GitHub issue 11 about Docker support - either close as completed via gateway or update with new sync approach.","design":"Review GH-11 requirements:\n- User wants to use beads across multiple dev machines\n- Docker hosting was proposed solution\n\nNew approach:\n- Phase 1: Pure git-based sync (no Docker needed)\n- Phase 2: Optional Docker gateway for convenience\n- Addresses use case without mandating server\n\nUpdate GH-11 with:\n- Link to DESIGN-GIT-SYNC.md\n- Explain git-based approach\n- Note optional Docker gateway\n- Ask for feedback\n\nClose issue when sync features implemented.","acceptance_criteria":"- GH-11 reviewed and understood\n- Comment added explaining sync approach\n- Link to design document\n- User feedback requested\n- Issue closed when Phase 1-2 complete\n- Documentation cross-referenced","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-16T01:40:06.674765-07:00","updated_at":"2025-10-16T13:43:29.009604-07:00","closed_at":"2025-10-16T13:43:29.009604-07:00"}
{"id":"bd-307","title":"Fix circular dependency detection and prevention","description":"Implement robust detection, prevention, and user guidance for circular dependencies that cross edge types. Current system only prevents cycles within \"blocks\" type dependencies, allowing cross-type cycles (e.g., A blocks B, B parent-child A) that can hide work from ready list and confuse dependency visualization.","design":"Analysis shows that cycle prevention is type-specific (blocks only) while detection is type-agnostic. All current operations are safe from infinite loops (depth-limited), but semantic confusion and future maintenance hazards exist. Need validation, warnings, and potentially full cross-type prevention.","acceptance_criteria":"- Cross-type cycles are prevented or warned about\n- Semantic validation prevents child→parent dependencies\n- Users receive clear diagnostic messages\n- Documentation explains cycle handling behavior\n- All existing safe operations remain protected","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-10-16T10:27:48.21284-07:00","updated_at":"2025-10-16T13:32:31.150118-07:00","closed_at":"2025-10-16T13:32:31.150118-07:00"}
{"id":"bd-308","title":"Add semantic validation for parent-child dependency direction","description":"Prevent backwards parent-child dependencies where child tasks depend on their parent epics. This is semantically incorrect - parents should depend on children completing, not the reverse.","design":"Add validation in AddDependency that checks if dep.Type == DepParentChild and validates the direction is correct (parent depends on child, not child on parent). Reject with clear error message if direction is backwards.","acceptance_criteria":"- Child→parent dependencies are rejected with clear error\n- Parent→child dependencies work as expected\n- Error message explains correct direction\n- Tests cover both valid and invalid cases","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-16T10:28:24.205615-07:00","updated_at":"2025-10-16T13:04:55.724216-07:00","closed_at":"2025-10-16T13:04:55.724216-07:00","dependencies":[{"issue_id":"bd-308","depends_on_id":"bd-307","type":"parent-child","created_at":"2025-10-16T10:28:40.951661-07:00","created_by":"stevey"}]}
{"id":"bd-309","title":"Add diagnostic warnings when cycles are detected after dep add","description":"Run DetectCycles() after adding dependencies and warn users if cycles exist. Provide clear, actionable messages about which issues form the cycle and potential impact on ready work visibility.","design":"In bd dep add command, after successful dependency addition, call DetectCycles(). If cycles found, print warning to stderr showing cycle path and explanation. Include suggestion to run 'bd dep cycles' for full analysis.","acceptance_criteria":"- Warnings appear after dep add when cycles exist\n- Warning shows cycle path clearly\n- Explains impact on ready work calculation\n- Suggests next steps for user\n- Does not block operation (warning only)","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-16T10:28:24.215511-07:00","updated_at":"2025-10-16T13:00:35.578468-07:00","closed_at":"2025-10-16T13:00:35.578468-07:00","dependencies":[{"issue_id":"bd-309","depends_on_id":"bd-307","type":"parent-child","created_at":"2025-10-16T10:28:40.946661-07:00","created_by":"stevey"}]}
>>>>>>> 44f05ad (Close bd-306 (implemented daemon/auto-sync instead))
{"id":"bd-31","title":"Test issue for design field","description":"Testing the new update flags","design":"## Design Plan\\n- Add flags to update command\\n- Test thoroughly\\n- Document changes","acceptance_criteria":"- All three fields (design, notes, acceptance-criteria) can be updated\\n- Changes persist in database\\n- bd show displays the fields correctly","notes":"Implementation complete. All tests passing.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-10-14T14:43:06.91361-07:00","updated_at":"2025-10-16T10:36:49.355948-07:00","closed_at":"2025-10-15T03:01:29.573031-07:00"}
{"id":"bd-310","title":"Document cycle handling behavior and limitations","description":"Add comprehensive documentation explaining which dependency types are checked for cycles, why cross-type cycles matter, what operations are safe, and how users should think about dependency design.","design":"Add comments to AddDependency explaining cycle checking logic. Update README.md with section on cycles. Add to DESIGN.md explaining technical decisions. Include examples of problematic and correct dependency patterns.","acceptance_criteria":"- Code comments explain cycle checking\n- README has user-facing cycle guidance\n- DESIGN.md has technical rationale\n- Examples show good and bad patterns\n- Explains ready work implications","status":"closed","priority":2,"issue_type":"task","created_at":"2025-10-16T11:01:26.976667-07:00","updated_at":"2025-10-16T13:19:25.892624-07:00","closed_at":"2025-10-16T13:19:25.892624-07:00","dependencies":[{"issue_id":"bd-310","depends_on_id":"bd-434","type":"parent-child","created_at":"2025-10-16T13:36:12.892254-07:00","created_by":"import-remap"},{"issue_id":"bd-310","depends_on_id":"bd-307","type":"parent-child","created_at":"2025-10-16T13:36:32.987715-07:00","created_by":"auto-import"}]}
{"id":"bd-311","title":"Benchmark cycle detection performance on large dependency graphs","description":"Measure performance impact of cross-type cycle checking on large graphs (1000+ issues). Determine if optimization needed before enabling full prevention. Test various graph structures (sparse, dense, deeply nested).","design":"Create benchmark test with synthetic dependency graphs of varying sizes and structures. Measure AddDependency performance with type-specific vs all-types cycle checking. Document findings and optimization recommendations if needed.","acceptance_criteria":"- Benchmark test covers 100, 1000, 5000 issue graphs\n- Tests sparse and dense dependency patterns\n- Measures time for both checking approaches\n- Documents results in comments or DESIGN.md\n- Recommends optimization if \u003e100ms impact found","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-16T11:01:26.97681-07:00","updated_at":"2025-10-16T13:19:06.925812-07:00"}