Beads Cleanup

This skill is a routing layer over the existing Beads operating model.

• Repository workflow and ownership model: ../../../README.md
• Coordinator mutation authority and lease rules: ../beads-coordinator/references/runtime-and-safety.md
• Coordinator loop and PR-review lane behavior: ../beads-coordinator/references/coordinator-loop.md
• PR-review worker closure boundary and review-lock vocabulary: ../beads-pr-reviewer-worker/SKILL.md

If these sources disagree with this skill, fix this skill. Do not let cleanup become a competing doctrine.

Non-Negotiable Boundaries

• Never implement code.
• Never mutate a bead that has a live foreign lease. Use the lease rules from ../beads-coordinator/references/runtime-and-safety.md.
• Never close or reopen a bead without confirming the external state that justifies it.
• Never create new beads from cleanup. Missing wiring should be reported for the coordinator loop to self-heal.
• Never touch .beads/dolt/ manually.
• Append notes for every bead mutation so later operators can see what cleanup changed and why.

Load Only The Reference You Need

• references/local-state-reconciliation.md Load for stale in_progress claims, dependency unblocking, Dolt/worktree health, and stale review-running labels.
• references/pr-review-reconciliation.md Load for blocked original pr-review beads and blocked pr-review-task review beads.
• references/reporting.md Load for the cleanup report shape, rig-routing notes, command quick reference, and final mutation summary.

Workflow

1. Read ../beads-coordinator/references/runtime-and-safety.md if you need the exact lease and mutation-authority rules before touching Beads state.
2. Run the relevant passes from the reference files in order, skipping mutation when evidence is incomplete or a live foreign lease exists.
3. Keep canonical PR metadata on the original implementation bead only; review beads must not invent their own external_ref.
4. Clean worktrees and branches conservatively. Preserve anything that may still contain useful unpublished work.
5. Produce the structured report from references/reporting.md so the coordinator has a clear mutation ledger before dispatch begins.