Reviewed migrations
A code deploy never applies schema changes. Migrations are reviewed first and classified as safe, warning or manual before anything runs.
`push` reports pending schema work; `migrate` shows what will change. Safe changes proceed, warnings and manual changes need explicit confirmation, and type changes may require hand-written SQL.
Removing a table or column is not a delete. It is marked `.deprecated(...)` first, so the data survives the rollout and the removal can be handled deliberately later.
Separate steps
Shipping code does not silently alter the database.
Safe / warning / manual
Every migration carries a classification before it is applied.
Deprecate, do not drop
Removals are marked and retained instead of deleted in place.
Explore more
Describe your next change.
The agent plans, writes, validates, and deploys it to Telegram.