The agent wrote the migration. Are you really going to Approve it?

Tuesday afternoon, that Approve button

Tuesday, 3 p.m. A PR notification lands in Slack. Junior writes in the channel: "Cursor generated this migration for me — can you take a look?"

You open the diff. Eighty lines of ALTER TABLE. Add columns, change types, add indexes, attach foreign keys — every line is familiar on its own. Syntax is clean. Naming matches team conventions. Mechanically, it all looks plausible.

But together? That NOT NULL on biz_order has no default — will it pass on existing rows? How long does the type change on sys_user lock the table? Does the down migration actually restore the previous schema? The PR description says "Agent self-review: should be fine" — that is not evidence.

Reject the whole thing and you look like you are blocking the team or fighting AI. Click Approve and your name is on it. When production blows up, the postmortem asks "who approved this version?" and you say: "CI passed; it looked okay to me."