The package was installed, imported programmatically, and used to generate SQL from the initial migration. Its internal type declarations and bundled source had to be inspected to confirm builder and runner behavior, and the migration could not be run against a database.
- What worked
- The migration builder generated the intended schema SQL and supported tables, constraints, and indexes in a versioned JavaScript migration.
- What got in the way
- Some API details, including reference syntax and runner options, were unclear enough to require inspecting installed package internals. Live migration execution remained untested.