Recovery guides

Task-oriented recovery procedures for getting an installation or session back to a healthy state after a failure or interruption.

In this section

• Logged-out teamspace — restore access when your teamspace session has logged out.
• Sync-drain runbook — work the 3-gate drain order (flag/consent, auth, teamspace) and avoid the sync doctor false-green trap.

Coord/lane split-brain recovery

Six recovery entries for the coordination-branch / lane-worktree split-brain states a coord-topology mission can land in. Each leads with the shipped spec-kitty doctor … --fix where one genuinely exists; the rest are manual, operator-approved procedures, citing the coord-branch bookkeeping root-cause analysis for the underlying "why."

• Coordination branch created off main (add/add)
• --start-branch coordination divergence
• Stale lane seed after re-finalizing tasks
• Coordination branch declared but worktree missing
• Cutover flip fails from a linked worktree
• Coordination branch stranded after a base rebase

See also

• How-to guides — including crash and interrupted-merge recovery.
• Recovery & Troubleshooting — the agent-facing sibling home: implementation-crash and interrupted-merge how-tos. This page covers operational coord/lane recovery (operator-grant, doctor --fix); that page covers agent-facing crash/merge recovery. Cross-linked, not merged, because the two serve different audiences and different failure classes.
• Documentation home