Backfill & data-migration verification
Batching, transaction scope, idempotency, lock duration against live traffic stats, the UPDATE scripts AI writes alongside every schema change.
Every schema change ships with a data change next to it: the UPDATE that fills the new column, the DELETE that clears the old one. Today a few rules read those statements, unbounded UPDATE and DELETE, backfills over large tables on unindexed columns, and bolvrk explain over the plan. A full backfill corpus is planned: batching and its absence, transaction scope, idempotency on re-run, and lock duration judged against live traffic counters.
Want this built sooner?
What gets built next bends toward what connected teams actually need, tell us.