- Shipped
- September 5, 2026 at 12:05 AM UTC
- Author
- Kamo
- Commit
- 1bc222b
f0edd01 was pushed with the rest of the fleet-wide rollout-safety work and is the only one of that batch whose image never appeared: the deployment is still running 39d330c5 and the KlusterServices deploy-safety audit still flags this service for no-preStop and no-minReadySeconds. The build is not the problem — `npm run build` succeeds locally on this commit, including all five postbuild guards (static-routes, trusted-types-order, csp-nonce, response-compression, precompress-static). That points at the npm ci transfer corruption this Dockerfile already documents and retries five times for. Empty commit purely to re-run it.