Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0
Why this matters
There are three workflows (ci.yml, security.yml, pr-test-gate.yml) and none runs docker build on backend/Dockerfile or docker compose build. Because backend tests run via vitest against src/, the compiled dist/ runtime path and the image are never exercised in CI - which is why a broken production image can merge green.
Acceptance criteria
Files to touch
.github/workflows/ci.yml
backend/Dockerfile
docker-compose.yml
Out of scope
- Pushing images to a registry
- Multi-arch builds
Why this matters
There are three workflows (ci.yml, security.yml, pr-test-gate.yml) and none runs docker build on backend/Dockerfile or docker compose build. Because backend tests run via vitest against src/, the compiled dist/ runtime path and the image are never exercised in CI - which is why a broken production image can merge green.
Acceptance criteria
Files to touch
.github/workflows/ci.ymlbackend/Dockerfiledocker-compose.ymlOut of scope