docs(phase 3.3+3.4): event-day runbook + rollback recipe #28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/phase-3.3-event-runbook"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Phase 3.3 + 3.4 of the Stream-a-Thon plan, combined into one artifact (
docs/RUNBOOK_EVENT.md) since they're both content in the same file.Phase 3.3 — the primary event-day playbook operators read start-to-finish:
RUNBOOK_FALLBACK.mdfor deep proceduresPhase 3.4 — lands as
§7 Rollback recipe: three independently-rollable surfaces (webui git revert + restart, OBS scene-collection xcopy fromscenes.backup.{ISO}, plugin = off-scope per Q6 pinning). Each surface has its own verify checklist; an end-to-end smoke sequence runs after any rollback so a broken rollback is itself caught immediately.Design choices
RUNBOOK_FALLBACK.md. That file (from Phase 0.5.4) already has detailed S1/S3/S7/S8 procedures; this file links into it rather than copying. The fallback is the "if you got here, you have a specific problem" appendix; RUNBOOK_EVENT.md is the primary start-to-finish playbook.\"--\").Acceptance gates
These are out-of-session human checks, recorded as §9 sign-offs in the file:
Files
docs/RUNBOOK_EVENT.md(new)Test plan
RUNBOOK_FALLBACK.mdresolve to real headingsPrimary event-day playbook operators read start-to-finish. Covers roles (Driver / Observer), T-60 pre-event checklist, T-time event-day timeline (T-60 setup → doors open → T+30 teardown), 5/30-min observer cadence, and an S1–S8 quick-reference matrix that links into RUNBOOK_FALLBACK.md for the deep emergency procedures rather than duplicating them. The S8 plugin-free operator mode drill is a concrete five-step exercise both operators run before doors open. Phase 3.4 lands as §7 Rollback recipe in the same file: three independently-rollable surfaces (webui git revert + restart, OBS scene-collection xcopy from scenes.backup.{ISO}, plugin = off-scope per Q6 pinning). Each surface has its own verify checklist; an end-to-end smoke test sequence runs after any rollback so a broken rollback is itself caught immediately. Internal links to RUNBOOK_FALLBACK.md anchors are verified against the existing section headings (GitHub-style slugs, em-dash → "--"). Acceptance gates (two-operator dry-run for 3.3; tested-on-real-host for 3.4) are out-of-session human checks, recorded as §9 sign-offs at the bottom of the runbook. 184/184 jest tests pass.