On SQLite, DuckDB and PostgreSQL, dropping a column that holds values MUST leave its values in the quarantine table and, run backwards by the step's down, MUST restore them; dropping a table MUST leave it under its quarantine name with its rows and, run backwards, MUST bring it back; a step whose check fails MUST leave the database and the ledger as they were; and a lock timeout MUST be tried again and then given up as an error value.
Enforced (check): .github: cd commons/data && bun run verify — suite/safety.test.ts: dropping a column keeps its values in a quarantine table, does not copy again, is data-dependent and quarantine-reversible, and undoing the step restores the values; suite/safety.test.ts: dropping a table renames it to its quarantined name with its rows, undoing brings it back, and a purge drops a quarantine table and nothing else; suite/safety.test.ts: with the protection layer and idempotency, dropping a column on three engines leaves the values in quarantine, the view without the column, and the step safe to run twice
Proved by: data/suite/safety.test.ts
Tests: passed: suite/safety.test.ts dropping a column keeps its values in a quarantine table, does not copy again, is data-dep; passed: suite/safety.test.ts dropping a table renames it to its quarantined name with its rows, undoing brings it back,; passed: suite/safety.test.ts with the protection layer and idempotency, dropping a column on three engines leaves the v