It read the repo-root .env with a bare readFileSync and died on ENOENT
where there wasn't one — which is every container, including the server
this deploys to. Migrations and the seed both ran fine on the Dokploy
host; this was the only step of the deployment that could not.
The loop already used `??=`, so a variable present in the environment
always won and the file was never the authority. Its absence is now the
ordinary case it always should have been.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
