Marc-André Bombeck 8a316f5820 Record that the cache pin was checked against the entrypoint the image runs ...

The reading behind the pin was taken under `next start`. The container runs
`node .next/standalone/server.js`, and a fix that is green everywhere and
inert in production is the failure this project has paid for before, so the
same probe was re-run under the standalone entrypoint with static assets and
public copied the way the Dockerfile copies them.

No difference: three module instantiations either way, one shared registry
with the pin, separate registries without it, and a measurement write made
through a route handler reaches the page render's cache only when the pin is
there. The note says which entrypoint the claim rests on so the next person
does not have to wonder.

2026-07-31 08:20:34 +02:00

..

__tests__

Share one server cache between the home page and the API routes

2026-07-31 08:03:21 +02:00

invalidate.ts

feat(analytics): replace health score with reference composite

2026-07-28 21:10:15 +02:00

server-cache.ts

Record that the cache pin was checked against the entrypoint the image runs

2026-07-31 08:20:34 +02:00