[adamshiervani]

• Compile with tsc in a build stage. Type errors now fail the build, not container startup.
• Runtime stage: production dependencies only, USER node, tini as init, HEALTHCHECK on /healthz. Image is 524 MB (was 828 MB).
• Move ts-node, typescript, @tsconfig/node22 and @types/* to devDependencies. start runs dist/index.js.
• Exclude .env.* from the build context.
• CI runs on Node.js 22.23.4 to match engines.

Migrations stay manual.

Tested: image build, prisma migrate deploy as node, /healthz, Docker health healthy, docker stop in 254 ms, npm test (106 passed).

---

Note

Medium Risk
Changes production container startup, process supervision, and dependency/runtime footprint; verify orchestration still passes env/PORT and health probes behave as expected.

Overview
Runtime now ships compiled JS, not ts-node. npm start runs node dist/index.js, main points to dist/index.js, and TypeScript/ts-node tooling moves to devDependencies with engines tightened to Node >=22.23.4 <23 and a matching CI bump.

Docker image is multi-stage and slimmer. A build stage runs prisma generate, tsc, and npm prune --omit=dev; the runtime stage copies only prod node_modules and dist, runs as USER node, wraps Node with tini, and adds a /healthcheck via /healthz. .dockerignore now drops .env.* while keeping .env.example.

Risk / testing notes. Author reports image build/tests pass; ensure HEALTHCHECK aligns with any non-default PORT and that any non-Docker deploy paths also use the compiled entrypoint.

^{Reviewed by Cursor Bugbot for commit 0094779. Bugbot is set up for automated code reviews on this repo. Configure here.}