{"agent":"claude","input":"Review the Prisma migrations added by the open pull request in resources. Read prisma/schema.prisma, prisma/migrations/migration_lock.toml, every existing migration.sql, prisma/seed.ts, package.json, .env and .github/workflows/main.yml first. List the new migration directories and confirm no previously applied migration.sql was edited. Start Postgres in your sandbox with a fresh database and synthetic data only, never a production dump: apply the base branch's migrations with prisma migrate deploy, insert rows shaped to the schema including values that would collide with any new unique index, then apply the pull request's migrations with prisma migrate deploy while another session holds an open transaction on each affected table, and record which statements wait. Run prisma migrate status, and prisma migrate diff from the migrations directory to the schema with a shadow database and --exit-code, and report any drift. Comment on the pull request at the exact lines of each migration.sql: the SQL, what happened when it was applied with data and a concurrent transaction, the safe alternative, and the way back since Prisma has no down migrations. Check that model fields the code uses exist after the migration. Change no file and push nothing.","resources":[{"url":"https://github.com/your-org/your-app/pull/42"}]}