fix: rewrite APP_ENV to prod in baked-in .env

[turegjorup]

Summary

The committed .env defaults APP_ENV=dev for local development. The API image only ships prod dependencies (composer install --no-dev), so any tooling that reads .env directly without going through docker-entrypoint.sh (which runs composer dump-env prod) would try to bootstrap a dev environment that can't resolve its services.

Files Changed

• infrastructure/display-api-service/Dockerfile — added a RUN sed step in the api_app_builder stage that rewrites APP_ENV=dev → APP_ENV=prod in the in-image .env, right after the full source COPY. The source .env is untouched, so local dev keeps defaulting to dev.
• CHANGELOG.md — entry under [Unreleased].

Test Plan

• Build the image: docker build -f infrastructure/display-api-service/Dockerfile .
• Inspect the baked-in .env: docker run --rm --entrypoint sh <image> -c 'grep ^APP_ENV= .env' — expect APP_ENV=prod.
• Boot the container normally and confirm the entrypoint still runs composer dump-env prod and cache:warmup without errors.
• Confirm local dev compose stack still picks up APP_ENV=dev from the source .env (the file on disk is unchanged).

🤖 Generated with Claude Code