Schema migrations, planned not improvised
Schema evolution is planned, not ad hoc: a pure diff between two approved db-design versions produces the exact ALTER/CREATE/DROP sequence, with anything destructive requiring a conscious human choice to run.
How it works
MigrationAgent compares the db-design history — tables, columns, types, defaults, foreign keys, indexes — between an earlier approved version and the current one.
Statements come out in dependency order for the relational target, not just a flat list of changes.
Drops and other destructive operations are emitted commented out — nothing destructive runs until a human deliberately uncomments it.
The plan is review-only: a human applies it by hand after approval, keeping the human in the execution loop, not just the sign-off.
The agents behind it
Human control
Migration gate — a pure diff (no LLM) proposes the plan; a human reviews and chooses what actually gets uncommented and run.