[E00-S03-T05] Migration failure produces structured diagnostic #394

Merged

kpcto merged 3 commits from feature/180 into main 2026-08-30 01:31:49 +00:00

Conversation 1 Commits 3 Files Changed 9

+1049 -10

3 Commits

Author	SHA1	Message	Date
implementer	bb3a68648a	fix: inject the ledger into MigrationRunner (type-only import) so probes load the committed module under type stripping ... Node's type stripping does not rewrite './ledger.js' to './ledger.ts', so the runner's runtime import of the ledger could not resolve when the behavioral probes execute the committed runner.ts directly (CI failure on Node 24). The ledger is now imported type-only and the caller passes the instance (new MigrationLedger(pool)) — the probes already do. runner.ts has no runtime imports left, so type stripping erases them and the committed module loads as-is.	2026-08-30 01:24:14 +00:00
implementer	52190d082c	test: lock in the migration failure diagnostic (E00-S03-T05) ... Static assertions + mutation probes on the committed runner source, a deterministic stub-pool behavioral probe (intentionally failing migration fixture -> structured diagnostic naming the failing migration, apply and record phases), a docker-gated real-stack probe against a real database (the issue's test plan), and CI enforcement via the additive database-postgres-diagnostic job.	2026-08-30 01:17:23 +00:00
implementer	f6d407394d	feat: add migration runner with structured failure diagnostic (E00-S03-T05) ... MigrationRunner applies pending migrations through the migration ledger exactly once; when a migration fails it throws a MigrationFailedError whose diagnostic is a structured object identifying the failing migration (version), the failure phase (apply/record), the underlying cause, and the applied/pending ledger state, serializable via toJSON. Re-exported from the driver boundary so no other package needs the pg driver to run migrations. Advisory lock (T04) and ready gate (T06) remain out of scope.	2026-08-30 01:17:23 +00:00