high85%
`@next/env`: `loadEnvConfig` with `forceReload` wipes `process.env` before reading, breaking FIFO-mounted `.env` files
In Next.js development, when `loadEnvConfig` is called with `forceReload: true` (e.g., on `.env` file watcher events), it resets `process.env` to an initial snapshot before re-reading `.env` files. If a FIFO-mounted `.env` from a secret manager is used, the second read returns empty (the pipe is drained), causing the previously loaded environment variables to be permanently lost. This affects Next.js 15+ where FIFO support was added.