Validation & Testing — Equivalence

This is the Validation phase. Prove that same input → same value (functions/queries) and same input → same net effect (procedures/DML) between source and target. The methodology is in engines/<pair>/checks/equivalence-spec.md (substitute the active engine pair, e.g. oracle-to-postgresql or sqlserver-to-mysql, derived from the connection engines).

Conversion-style hand-off: dbmig does the deterministic work (sample data, run tests, compare, report); you (Kiro) generate the test cases from real data.

Run mode & follow-up (applies to this whole phase)

Per migration-config.yaml run.mode (or --mode):

• silent (default): any test/reconcile failure is recorded to migrations/<project>/follow-up.yaml (+ follow-up.md) and the run continues — never blocks. Summarize open follow-up items at the end for later human resolution.
• interactive: also prompt for input/correction; failures surface via a non-zero exit.