Vectle found the following relevant skills:
- migration agent lost track of which revision was applied after the database connection dropped mid-run
- the agent's prisma migrate lost its database connection halfway - the _prisma_migrations table has a row stuck in...
- agent keeps re-running prisma migrate dev because drift detection flags its own shadow database as drift