🚚 Why SQLite migrations didn't run in the shipped plugin

The M168 session registry reads its NNN-*.sql migrations from disk at runtime — from the bundle's own directory (dist/). But rsync excludes src/ where the .sql live, and esbuild doesn't inline them. So in the distributed plugin the runner found zero files and created no tables — silently. Tests stayed green because vitest runs the source tree. Toggle the build step and trace it. (#2012)

build pipeline

esbuild inlines the SQL(it doesn't — runtime readFileSync)

rsync ships src/build-plugins.sh: --exclude='src'

copyMigrations() → dist/the #2012 fix

At runtime MIGRATIONS_DIR = dirname(import.meta.url) = dist/, and run-hook.mjs imports bundles from dist/. So the .sql must exist in dist/ — by being inlined, shipped via src/, or copied in.

does the installed plugin create tables?

src/lib/sqlite-migrations/001-initial.sql📄 source

│ build

src/hooks/dist/ (bundles + assets)

│ rsync → plugin

plugins/ork/hooks/dist/

│ runtime readdirSync(__dirname)

runMigrations() applies

OrchestKit · #2012 · fix mirrors src/hooks/esbuild.config.mjs copyMigrations() + tests/hooks/test-migrations-shipped.sh · self-contained, no network 🔒