fix(db): exclude the one-off-script ledger from drizzle management

script_migrations is created and read by script-migrations/index.ts, not
the schema. Dev's db:push saw it as an unknown table: it prompted
'created or renamed?' (no TTY in CI, job red since the revamp landed on
dev) and on --force would have DROPPED the ledger, re-running every
applied one-off script. tablesFilter tells drizzle the table is not its
business.

Claude-Session: https://claude.ai/code/session_01CgaxNAaeD3taGdghbXn17w

Author: Sg312

packages/db/drizzle.config.ts

@@ -15,4 +15,9 @@ export default {
   dbCredentials: {
     url: process.env.DATABASE_URL!,
   },
+  /* script_migrations is the one-off-script ledger (script-migrations/index.ts) —
+     deliberately managed outside drizzle. Without this filter, dev's `db:push` sees an
+     unknown table: it prompts "created or renamed?" (no TTY in CI → red) and would DROP
+     the ledger, making every applied one-off script re-run. */
+  tablesFilter: ['!script_migrations'],
 } satisfies Config