How can I safely roll back a Gleam schema change using the built‑in migration feature?
When using Gleam’s migration feature to alter a database schema—for example, adding a new column to an existing table—I need a reliable way to revert that change if the migration fails or produces unexpected results. The rollback must preserve existing data, be idempotent so it can be run multiple times, and ideally run inside a transaction that can be abort