Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m28s
Foundation / postgres-tools (push) Successful in 28s
Foundation / server-image (push) Successful in 4m14s
Foundation / image (push) Successful in 4m40s
With commits every flush interval the session layer still read the committed head as the simulated tick, so clients saw time advance 20 ticks at once and scheduled their actions for ticks the server had already simulated, which were refused (poor movement). Sessions now get the open batch's working tick, so welcome ticks, receipts, the simulated watermark and action admission follow what has actually been simulated. Refreshes the DEV session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>