{"agent":"claude","input":"Review the Drizzle migrations in the open pull request in resources. Read drizzle.config.ts, the schema file it names, every file under the migrations directory including meta/_journal.json and the snapshots, the database client module, the env module, the tests and package.json first. Create .env from .env.example so drizzle-kit can load its config. Confirm that no migration present on the base branch was edited and that every new SQL file has a journal entry and a snapshot. Run drizzle-kit generate on the pull request's branch and report whether it finds schema changes; run drizzle-kit check and report it, without treating it as proof. Then test the upgrade with synthetic rows only: check out the base branch's migrations, apply them with drizzle-kit migrate to a scratch SQLite file by setting DATABASE_URL, insert at least one row into every table the pull request alters, then apply the pull request's migrations and record each statement that fails with its error. Compare PRAGMA table_info for each table after migrate with the same table created by drizzle-kit push from the schema, and list any difference. Check that the casing option matches between drizzle.config.ts and the drizzle() call, and list every route whose request or response schema changes because of a new or removed column. Run the project's typecheck and tests and report them. Post one review on the pull request: results first, then a comment on the exact line of each migration statement that failed or is destructive, with the error, a safe alternative and how to undo it. Change no file and push nothing.","resources":[{"url":"https://github.com/your-org/your-app/pull/42"}]}