- Shipped
- May 16, 2026 at 3:24 AM UTC
- Author
- Kamo
- Commit
- 8de18ea
The homepage was statically prerendered (○ / in the build output), which means the same HTML — and its embedded references to specific chunk hashes — was served indefinitely until the browser revalidated. After a deploy that ships fixes (e.g. the welcome-back gate, "Start over" link), returning visitors continued to see the old shell because their browser served the cached HTML pointing at the old chunks. Marking the page `force-dynamic` makes Next.js render fresh HTML on every request. The chunks themselves remain content-hashed and cacheable, so this only adds a small server-side render cost and pays back by ensuring visitors always see the current build's UI without a hard-refresh.