#2618 made a red drill name its step and phase (fetch, manifest, files, unpack, bundles, key, open, count, unseal, health). The 3 a.m. page does not yet say what each one means or what to check.
Done looks like:
[ ] A section "When the drill is red" in docs/RECOVERY.md has one short entry per step and phase: what it was doing, the likely cause, and the first thing to check. Example: bundles → slow store or many repositories, compare its counts with the snapshot's, retry the restore by hand with Route 1.
[ ] A test reads the doc and fails if a DrillStep from src/snapshot/drill.ts or a restore phase from src/snapshot/restore.ts has no entry, so the page cannot drift from the code.
[ ] Name the new test file in GATE in scripts/gate.ts. Run bun x tsc --noEmit and the new test.
#2618 made a red drill name its step and phase (fetch, manifest, files, unpack, bundles, key, open, count, unseal, health). The 3 a.m. page does not yet say what each one means or what to check.
Done looks like:
DrillStepfromsrc/snapshot/drill.tsor a restore phase fromsrc/snapshot/restore.tshas no entry, so the page cannot drift from the code.GATEinscripts/gate.ts. Runbun x tsc --noEmitand the new test.