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 (postgres) (push) Successful in 53m9s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 14s
Foundation / image (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 2m8s
Foundation / server-image (push) Successful in 5m13s
apply.sql matched v1..v21 against the full checked-in history but v22..v33 only against the final entry, so a changed checksum for any earlier migration was admitted once a database reached v22. postgres-check's checksum-drift rehearsal caught this (zeroed v14 sha256 migrated cleanly). Build the exact v21 history once and extend it per version. Verified on PostgreSQL 18.6: fresh migrate and re-run, v30 -> v33 upgrade, and refusal of a fake v34 and of zeroed checksums for v2, v14, v21, v22, v30 and v33, including a drifted v30 database. Refresh the dev session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>