Files
Matt 331b67dae0 Round system redesign: Phases 1-7 complete
Full pipeline/track/stage architecture replacing the legacy round system.

Schema: 11 new models (Pipeline, Track, Stage, StageTransition,
ProjectStageState, RoutingRule, Cohort, CohortProject, LiveProgressCursor,
OverrideAction, AudienceVoter) + 8 new enums.

Backend: 9 new routers (pipeline, stage, routing, stageFiltering,
stageAssignment, cohort, live, decision, award) + 6 new services
(stage-engine, routing-engine, stage-filtering, stage-assignment,
stage-notifications, live-control).

Frontend: Pipeline wizard (17 components), jury stage pages (7),
applicant pipeline pages (3), public stage pages (2), admin pipeline
pages (5), shared stage components (3), SSE route, live hook.

Phase 6 refit: 23 routers/services migrated from roundId to stageId,
all frontend components refitted. Deleted round.ts (985 lines),
roundTemplate.ts, round-helpers.ts, round-settings.ts, round-type-settings.tsx,
10 legacy admin pages, 7 legacy jury pages, 3 legacy dialogs.

Phase 7 validation: 36 tests (10 unit + 8 integration files) all passing,
TypeScript 0 errors, Next.js build succeeds, 13 integrity checks,
legacy symbol sweep clean, auto-seed on first Docker startup.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 13:57:09 +01:00

1.0 KiB

Release Runbook (Atomic Cutover)

Preconditions

  • all prior phase gates complete
  • signed release checklist
  • rollback owner and communication owner assigned

Cutover Sequence

  1. freeze non-release writes and announce maintenance window
  2. execute final backup snapshot
  3. deploy release candidate build
  4. run reset/reseed as planned for production state model
  5. run post-deploy integrity and smoke checks
  6. run mandatory critical-path E2E subset
  7. publish completion and monitor

Immediate Post-Cutover Checks

  • auth and role gating paths
  • transition mutation sanity
  • assignment preview/execute path
  • live cursor operations
  • audience vote acceptance and dedupe
  • reporting endpoint correctness

Rollback Trigger Conditions

  • integrity check failures
  • critical mutation path failure
  • unacceptable error-rate spike

Rollback Plan (High Level)

  • restore backup snapshot
  • redeploy previous stable build
  • validate critical-path smoke tests
  • issue incident communication and postmortem schedule