Configure correct Cache-Control headers for Vite SPA assets at the CDN level

Problem: Base44 deploys Vite-based SPAs but does not currently serve correct Cache-Control headers from the CDN. This causes "TypeError: Importing a module script failed" errors after every deploy, because users with cached index.html files try to load JS chunks with old content hashes that no longer exist on the server.

Impact:

• Affects every production Base44 app using Vite (which is the default)

• Customers must independently implement client-side mitigations (vite:preloadError handlers, hard reload logic, sessionStorage loop prevention) for an issue that should be solved once at the platform level

• Real production errors hitting paying users — in my case, 21 errors across 3 affected users in 24h before mitigations

Requested solution: Configure the Base44 CDN (Cloudflare) to serve:

• Cache-Control: no-cache on index.html (forces browser revalidation on every request)

• Cache-Control: public, max-age=31536000, immutable on /assets/*.js (safe long-term cache since filenames include content hashes)

Additionally, document or extend the chunk retention policy so old hashed JS chunks remain on the server for at least 24-48 hours after a new deploy, so mid-session users don't break during a deploy window.

Reference: This is the standard configuration used by Vercel, Netlify, and Cloudflare Pages by default for any Vite/React/Vue SPA. It is documented in Vite's official deployment guide.

Context: Elite plan customer running yonashavin.com in production. Support ticket [add ticket #] has full investigation context.