[E00-S03] PostgreSQL adapter and migration runner #60

New Issue

2026-08-26T23:59:56Z

kpcto commented

2026-08-26 23:59:56 +00:00

Parent epic: [E00] Repository and runtime foundation (#28)

Intent

Provide a PostgreSQL database adapter isolated to the database-postgres package and a migration runner with a migration ledger and advisory locking.

Acceptance criteria

PostgreSQL 18.6 container is the database
pg/Kysely imports are isolated to database-postgres
migration ledger is created
advisory lock prevents concurrent migration runners
migration failure produces a structured diagnostic
app does not report ready before migrations complete

Explicitly out of scope

Docker Compose baseline stack (E00-S02)
configuration service validation (E00-S04)
CI quality baseline pipeline (E00-S05)

Test plan

empty database migration succeeds
second migration run is idempotent
concurrent migration lock test passes
intentionally failing migration fixture is covered

Rollback note

revert the migration file/commit; the advisory lock releases when the runner exits with no data change

Owning stream

platform

Risk quadrant

agent-full

> Parent epic: [E00] Repository and runtime foundation (#28) ## Intent Provide a PostgreSQL database adapter isolated to the `database-postgres` package and a migration runner with a migration ledger and advisory locking. ## Acceptance criteria - PostgreSQL 18.6 container is the database - `pg`/Kysely imports are isolated to `database-postgres` - migration ledger is created - advisory lock prevents concurrent migration runners - migration failure produces a structured diagnostic - app does not report ready before migrations complete ## Explicitly out of scope - Docker Compose baseline stack (E00-S02) - configuration service validation (E00-S04) - CI quality baseline pipeline (E00-S05) ## Test plan - empty database migration succeeds - second migration run is idempotent - concurrent migration lock test passes - intentionally failing migration fixture is covered ## Rollback note - revert the migration file/commit; the advisory lock releases when the runner exits with no data change ### Owning stream platform ### Risk quadrant agent-full

kpcto added this to the Sprint 0 milestone 2026-08-26 23:59:56 +00:00

kpcto added the

labels 2026-08-26 23:59:56 +00:00

bot-dispatcher added

and removed

labels 2026-08-26 23:59:58 +00:00

bot-dispatcher commented

2026-08-26 23:59:59 +00:00

Auto-reverted by dispatcher: DoR lint: required section "Intent" is empty; required section "Explicitly out of scope" is empty; required section "Test plan" is empty; required section "Rollback note" is empty

status/ready may only be applied by a human maintainer.

> Auto-reverted by dispatcher: DoR lint: required section "Intent" is empty; required section "Explicitly out of scope" is empty; required section "Test plan" is empty; required section "Rollback note" is empty `status/ready` may only be applied by a human maintainer.

kpcto referenced this issue

2026-08-27 00:07:19 +00:00

[E00-S03-T01] PostgreSQL 18.6 container #176

kpcto referenced this issue

2026-08-27 00:07:20 +00:00

[E00-S03-T02] pg/Kysely imports isolated to database-postgres #177

kpcto referenced this issue

2026-08-27 00:07:21 +00:00

[E00-S03-T03] Migration ledger created #178

kpcto referenced this issue

2026-08-27 00:07:22 +00:00

[E00-S03-T04] Advisory lock prevents concurrent migration runners #179