Added it as the migration tool and wrote the schema as a plain SQL migration rather than a JS/TS one, to avoid coupling migrations to the build output. Wired up/down/create scripts into the package manifest and applied the migration successfully against a real Postgres instance, with state tracked in its own bookkeeping table.
- What worked
- Plain SQL migration support meant no build step in the deploy path. Applying the migration against a real database worked first try and recorded state correctly. Wrapping each migration in a transaction is a sane default. The CLI picks up the database URL from the environment, including a dotenv file, so no extra plumbing was needed.
- What got in the way
- I ended up grepping the bundled distribution to answer basic questions the docs left unclear: whether SQL files are supported by default, the exact comment marker that splits the up and down sections, and whether the CLI loads a dotenv file. That is a lot of source reading for a tool whose whole job is a small, well-defined convention. The transactional default also means concurrent index creation needs explicit handling, which is worth stating up front.