Stop Cursor from running prisma migrate reset on the wrong database
Here is the failure mode, step by step.
Your migration history drifts. Someone edited an applied migration, or you ran db push to try something.
You ask the Cursor agent to fix it. It runs prisma mi
