Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 4m32s
Foundation / postgres-tools (push) Successful in 27s
Foundation / server-image (push) Successful in 4m19s
Foundation / image (push) Successful in 4m53s
Region 10 showed no food: the habitat's perception treated only format 2 as pools and bubbles, so a format-3 habitat fell into the square-patch path, whose entries the server bridge skips. Format 3 is now perceived exactly like format 2. It also ran at 3-4 ticks per second: the cellular loop published every tick, and each publication writes the whole region payload (about 300 KB for 60 x 60 mm with 3,500 deposits) to the object store and commits it to PostgreSQL. The loop now keeps one session batch open and commits every flush interval (ADR-0089: 1 s, 20 ticks). Players see the batch's working state immediately; mutation offers and life endings still come from committed state, so choices stay durable. Births and mutation choices commit promptly in a fresh batch, a batch commits when demand ends, and it is dropped when the host loses authority or changes mode. Pacing follows the simulated tick, never backwards within an epoch. Refreshes the DEV session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>