deployment-verification-agent

A pre-deploy checklist for SQL migrations and data backfills is generated by identifying data invariants, producing read-only baseline SQL audits, and documenting migration steps with batching and runtime estimates to prevent silent data corruption.

SQL verification queries for post-deploy data validation are produced as read-only checks with expected results and tolerances, comparing baseline counts and constraints against post-deploy metrics to confirm no silent data loss or duplication occurred.

A rollback plan for a production data migration should include documented rollback procedures, batching strategies for backfills, and short-term monitoring metrics with expected thresholds and alerts for the first 24 hours after deployment.

Deployment verification is needed when a pull request adds a migration, transforms production data, or performs a backfill that could silently alter, duplicate, or lose records, requiring executable pre and post-deploy SQL checklists to make go/no-go decisions.

Baseline data audits before running a production backfill are automated by generating read-only SQL queries that verify specific conditions like counts, non-null constraints, and foreign keys that must hold before and after deployment.