All checks were successful
CI / lint (push) Successful in 1m37s
Deploy / notebooks (push) Has been skipped
Deploy / zotero (push) Has been skipped
Deploy / docs (push) Has been skipped
Deploy / api (push) Has been skipped
Deploy / mc (push) Has been skipped
Infra CI / notebooks (push) Successful in 6m15s
Infra CI / zotero (push) Successful in 23s
Infra CI / docs (push) Successful in 22s
Infra CI / api (push) Successful in 13s
Infra CI / mc (push) Successful in 13s
Deploy / report (push) Successful in 13s
CI / test (push) Successful in 17m9s
Package Supply Chain / pkg-supply-chain (push) Successful in 59s
The overlay deleted marimo's pnpm-lock.yaml before 'pnpm install --no-frozen-lockfile', so every image build re-resolved the entire dependency graph (devDeps included — rolldown-vite beta among them) to latest-of-the-day. The 0.23.13 rebuild on 2026-07-08 produced a bundle that compiled clean but crashed the editor at runtime on every notebook open: 'TypeError: d is not a constructor' in the @codemirror/merge chunk (new StyleModule(...) receiving a non-constructor after bad bundler interop). The home page still rendered and the container reported healthy, so nothing caught it. Keep the lockfile: --no-frozen-lockfile already re-resolves only what the overlay actually changes (@tabler/icons-react + the two overrides); everything else stays at the versions upstream tested and shipped. Verified: rebuilt image, headless-browser probe of the editor on a throwaway container (0 console errors, cells render), then recreated the production container and re-probed — clean. Frontend smoke gate in CI to prevent recurrence is designed and pending approval.