curriculum-project-hub/.scratch/saas-production-readiness/issues/14-migration-compatibility-and-recovery.md

Establish migration compatibility and failed-migration recovery

Type: task Status: open Blocked by: 06

Question

Define and enforce the application/schema compatibility rule for each release, require expand-and-contract sequencing for destructive changes, add migration status/checksum and production-like rehearsal gates, and move schema mutation out of ordinary service start into an explicit release phase. Require a recent verified recovery checkpoint, bounded lock/runtime evidence, and an operator procedure for resolving or restoring a failed Prisma migration without pretending that an application rollback reverses the database.