FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Serving Activity details from a static cache
Including pre-generated responses in Static Assets to eliminate runtime 404s
Purpose
Serving pre-generated Activity details from the production Worker required the build cache to be included in actual Static Assets instead of falling back to a dummy runtime cache.
Implementation
Read-only Static Assets incremental caching and cache interception were enabled, and deployment plus dry-run now use OpenNext. The built cache is bundled with static assets, while production probes cover Activity details, the learning map, and cache hits. SSR, API, and database-dependent page execution remain unchanged.
Rendering diagram…
What was confirmed
Verification results
Dry-run confirmed 440 assets and cache population, and the local Worker returned 200 for Activity, the learning map, About, and health.
At the cutoff, production reachability had not been verified.
Basis for completion
The work was complete when pre-generated cache entries could ship as static assets and local Worker checks confirmed detail routes and cache hits.