prisma-migration-drift-recovery

Safely handle Prisma migration drift on existing databases without data loss. Use when: (1) "prisma migrate dev" shows "Drift detected: Your database schema is not in sync", (2) Prisma asks "We need to reset the schema. All data will be lost. Do you want to continue?", (3) Database was created via Supabase, direct SQL, or another ORM before adopting Prisma, (4) Adding schema changes to a production database that wasn't initialized with Prisma migrations. Covers baselining existing databases and applying incremental changes safely.