8 Commits

Include renames

Author	SHA1	Message	Date
implementer	ebdee5daa5	feat: app reports ready only after the startup migration run (E00-S03-T06)	2026-08-30 01:56:19 +00:00
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	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
implementer	cb1b161ce9	fix: destroy the connection on unlock failure so a still-locked session is never reused (E00-S03-T04) ... release() previously returned the connection to the pool in a finally even when the pg_advisory_unlock statement failed, so a pooled connection could be reused while its session still held the migration advisory lock - the next borrower would block every other runner (reviewer finding F4). On unlock failure the connection is now destroyed (client.release(error) removes the client from the pool, ending the session and its lock); the plain client.release() is kept only on the success path. Locked in by a static assertion, a mutation probe, and a deterministic stub-pool behavioral probe of the committed release() control flow.	2026-08-30 00:49:56 +00:00
implementer	dac3679e33	fix: memoize in-flight acquire so concurrent acquire() is re-entrant-safe (E00-S03-T04) ... Security-review finding F2: two concurrent acquire() calls on the same MigrationLock instance could each check out a connection; the second pg_advisory_lock would overwrite this.client, leaking the first locked connection until session end. acquire() now memoizes the in-flight acquire in acquireInFlight and returns it on re-entry, so exactly one connection is checked out and no locked connection leaks. The memo is cleared once the acquire settles. tryAcquire()/release() paths unchanged. Locked in by: - static criterion test: acquireInFlight field, re-entry guard returns the in-flight acquire, memo cleared on settle - mutation probe: removing the re-entry guard fails the criterion - real-stack probe: two concurrent acquire() calls on one instance leave pool.totalCount at 1 (exactly one connection), the lock granted once, nothing left after release; probe fails (hangs) on the pre-fix code - CI job comment updated to reflect the re-entrancy criterion	2026-08-30 00:29:20 +00:00
implementer	3f80063303	feat: add migration advisory lock to database-postgres (E00-S03-T04)	2026-08-30 00:08:57 +00:00
implementer	7f6450410e	feat: add migration ledger to database-postgres (E00-S03-T03) ... MigrationLedger over the package-owned pg Pool: ensure() creates the schema_migrations table (version text PRIMARY KEY, applied_at timestamptz NOT NULL DEFAULT now()) with idempotent DDL; record() inserts an applied migration with a parameterized, idempotent statement (ON CONFLICT DO NOTHING — a rerun never double-applies); has()/applied() read the ledger back in apply order. Re-exported from the driver boundary (src/index.ts) so no other package needs the pg driver to touch migration state.	2026-08-29 23:19:56 +00:00
implementer	5c202ba21e	feat: add database-postgres driver boundary package (E00-S03-T02) ... - packages/database-postgres (@personal-blog/database-postgres): the single workspace package allowed to import the PostgreSQL driver — declares pg and kysely as exact dependencies (@types/pg for types) and its src/index.ts imports and re-exports the driver pieces (Pool, Kysely, PostgresDialect) so the isolation is real, not a placeholder - pnpm-lock.yaml: importer for packages/database-postgres plus the resolved pg/kysely dependency tree (frozen-lockfile install keeps working) - .gitea/workflows/ci.yml: new database-postgres-imports job runs tests/database-postgres-imports.test.mjs on every PR so the isolation criterion gates merges	2026-08-29 11:14:14 +00:00