fix(deploy): restore dist src runtime paths

[oakinh]

Summary

• Restore production start paths to the built dist/src layout (dist/src/otel.js, dist/src/main.js).
• Point the src module alias and bootstrap import back at dist/src so runtime absolute imports resolve.
• Keep the generated Prisma client copy aligned with the compiled dist/src/generated/prisma import path.

Test plan

• docker build -t election-api-dev-deploy-fix -f deploy/Dockerfile .
• docker run --rm --entrypoint node election-api-dev-deploy-fix -e "require('./module-alias'); require('src/prisma/prisma.service.js'); require('./dist/src/generated/prisma'); console.log('runtime-paths-ok')"
• docker run --rm --entrypoint node election-api-dev-deploy-fix -e "require.resolve('./dist/src/otel.js'); require.resolve('./dist/src/main.js'); console.log('entrypoint-files-ok')"

Root cause

The deploy image still builds into dist/src, but the SWC prep PR changed runtime references as if the image emitted a flat dist layout. ECS tasks could not start the app, so the service never became healthy and the deployment circuit breaker stopped the dev deploy.

Made with Cursor

---

Note

Medium Risk
Touches production entrypoints and module resolution; wrong paths would prevent containers from starting, but the change realigns paths with the existing build layout.

Overview
Restores production runtime paths so they match Nest’s dist/src build output instead of a flat dist layout that broke ECS deploys.

start:prod, deploy/entrypoint.sh, and module-alias.js now load ./dist/src/otel.js and dist/src/main.js, and map the src alias to dist/src so absolute src/... imports resolve. src/main.ts again imports module-alias from the app root via ../../module-alias (correct relative path from dist/src/main.js). The Dockerfile comment is updated to describe the dist/src/generated/prisma copy path; behavior is unchanged.

^{Reviewed by Cursor Bugbot for commit 131cb25. Configure here.}

[delegate-reviewer]

Approved.