Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m1s
Foundation / postgres-tools (push) Successful in 6s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
DEV runs one region at a time and moves to a new one before test cells die. A life left in the old region keeps its account's home there: the grant broker routes the account to a region nobody serves (503 region_unavailable) and any other region refuses its birth (existing life, one active life per world). tools/ops/retire-region-lives.sql, run as the database owner, ends each published life of the region at the region's latest commit (as end_cellular_lives does) and cancels unpublished reservations. It refuses while a server holds the region's lease, is a dry run unless confirm=yes, is idempotent, and leaves checkpoints and history unchanged. Tested on a disposable migrated cluster. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>