Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m31s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
A window ending 5.2 h after start (b2f224d) put evo-region into a crashloop (error m10-window-too-long); the server only sees it at startup. The deploy policy now requires REGION_SESSION_WINDOW to name its UTC activation and end within 4 h of it, with two selftest cases (one is theb2f224dvalue). DEPLOYMENT.md documents the follow-on quarantine: syncs recorded as Deployment-only run no hooks, so a promoted build is never retained; the provision hook is re-run from the rendered manifest. VALIDATION records the incident and the recovery. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>