Added a migration that refuses a wrapping transaction so indexes can be created concurrently. Executor source confirmed the class method decides that, and that SQL queued for the plan runs after statements issued directly inside the upgrade method. The migration runner was not executed.
- What worked
- The class API exposed a clear hook to disable transactions and to fail early before upgrade SQL runs.
- What got in the way
- Transactional behavior was clear only after reading the executor. Without a database driver, the runner never applied the migration, so statement ordering was not observed at runtime.