584608a14e
Cherry-picked website/, scripts/generate-llms-full.sh, and deploy-docs.yml from joyshmitz's PR. Fixed workflow to trigger on main branch instead of docs/docusaurus-site. Features: - Docusaurus documentation site with llms.txt support - Environment-variable driven config (defaults to steveyegge org) - Automated llms-full.txt generation from docs - GitHub Pages deployment workflow Co-authored-by: joyshmitz <joyshmitz@users.noreply.github.com> 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> Executed-By: beads/crew/dave Rig: beads Role: crew
1.3 KiB
1.3 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 1 | Recovery Overview | Diagnose and resolve common Beads issues |
Recovery Overview
This section provides step-by-step recovery procedures for common Beads issues. Each runbook follows a consistent format: Symptoms, Diagnosis, Solution (5 steps max), and Prevention.
Common Issues
| Issue | Symptoms | Runbook |
|---|---|---|
| Database Corruption | SQLite errors, missing data | Database Corruption |
| Merge Conflicts | JSONL conflicts during sync | Merge Conflicts |
| Circular Dependencies | Cycle detection errors | Circular Dependencies |
| Sync Failures | bd sync errors |
Sync Failures |
Quick Diagnostic
Before diving into specific runbooks, try these quick checks:
# Check Beads status
bd status
# Verify daemon is running
bd daemon status
# Check for blocked issues
bd blocked
:::tip
Most issues can be diagnosed with bd status. Start there before following specific runbooks.
:::
Getting Help
If these runbooks don't resolve your issue:
- Check the FAQ
- Search existing issues
- Open a new issue with diagnostic output