5 Commits

Include renames

Author	SHA1	Message	Date
implementer	3dd80f91fe	feat: persist the database volume across restart/recreate (E00-S02-T04) ... Mount the named `db-data` volume at PostgreSQL's data directory (/var/lib/postgresql/data) on the db service and declare it in the top-level volumes map, so the database survives `docker compose restart` and `docker compose down` + `up -d` (recreate). Reset with `docker compose down -v` per the issue rollback note. Header comments in compose.yaml and the server Dockerfile updated: T04 is no longer out of scope; T05/T06 remain.	2026-08-29 00:32:15 +00:00
implementer	9c049ce6b5	feat: app health endpoint succeeds (E00-S02-T03)	2026-08-29 00:21:34 +00:00
implementer	59a102bee3	feat: PostgreSQL health gates app start (E00-S02-T02)	2026-08-28 23:59:45 +00:00
implementer	3bbea68e6c	fix: align app/db image bases with documented stack (E00-S02-T01) ... Switch the app image from node:24-alpine to node:24.19.0-bookworm-slim in both build and runtime stages (Technology-Stack 5.4: glibc Debian base required because argon2 is a native dependency; musl/Alpine causes native-module build surprises), and the db image from postgres:16-alpine to postgres:18-bookworm (Technology-Stack 5.2/5.4/6.2 + golden tuple 7 pin PostgreSQL 18.6; 18-bookworm is the 18.x line on Debian bookworm). Update tests/compose-config.test.mjs so the committed assertions lock in the corrected image bases (db image, Dockerfile build/runtime stages, parser probe).	2026-08-28 23:45:18 +00:00
implementer	3be575818d	feat: docker compose up -d starts DB + app (E00-S02-T01)	2026-08-28 23:35:05 +00:00