EventHorizon deployment pipeline run 84 failed during Kubernetes rollout because the new application pod exited during SQLx startup migration validation.
Root cause: production had already applied SQLx migration version 5 as 0005_persona_versions.sql. A later change introduced 0005_contracts.sql, creating a second migration with version 5. SQLx treats migration versions as immutable and unique, so the new image failed with migration 5 was previously applied but has been modified.
apps/backend/migrations/0005_contracts.sql to apps/backend/migrations/0006_contracts.sql.0006_contracts.sql.547d66b (Fix contracts migration version) to main.cargo fmt --all -- --check passed.cargo test --locked passed: 50 tests.547d66b5a1fb.event-horizon/event-horizon rolled out successfully to image gitea.app.lan/eventhorizon/eventhorizon:sha-547d66b5a1fb.6 applied as contracts.https://eventhorizon.app.lan/healthz returned {"status":"ok"}.https://eventhorizon.app.lan/readyz returned ready for Postgres and Qdrant.Do not edit or renumber SQLx migration files after they have been applied in production. New schema changes must use a new migration version number.