feat: add beads as third backlog backend option - #6
Conversation
When config/backlog-backend=beads is set, firstmate uses the beads federated 'task' store as the queue source instead of data/backlog.md. Session-start's digest lists items with status:ready label from the beads store. - Add fm_beads_backend_available() check in fm-tasks-axi-lib.sh - Add print_backlog_beads_compact() rendering function in fm-session-start.sh - Update print_backlog_compact() to prioritize beads backend when configured - Add beads backend validation to bootstrap (checks task CLI and store reachability) - Update docs/configuration.md to document beads backend option - Update AGENTS.md section 10 to reference beads backend in backlog contract - Beads backend reuses existing task linkage machinery (task set-state, task close) The beads backend is fail-open: if task CLI is missing or store is unreachable, bootstrap reports a MISSING: diagnostic line and the home can still operate.
Tests for: - fm_backlog_backend_value() reading beads config - fm_beads_backend_available() checking task CLI and store - fm_tasks_axi_backend_available() returning false when beads is set - whitespace handling in backend config values
The install_cmd() function now recognizes 'task' and provides an install command for the beads CLI tool.
Update print_backlog_pointer() to provide backend-specific guidance: - beads backend: suggest 'task show <id>' for beads task store - manual backend: suggest 'inspect data/backlog.md' - default/tasks-axi: original message with tasks-axi and data/backlog.md
|
Warning Review limit reached
Next review available in: 25 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closing in favor of PR created via no-mistakes pipeline |
1 participant
Add beads federated task store as a third supported backlog backend alongside tasks-axi (default) and manual.
Changes
Validation
Beads backend reuses existing per-task beads linkage machinery (task set-state, task close) for lifecycle management while adding new queue-source discovery functionality.