Improve HTTP Cache-Control headers for static assets and API endpoints

PageSpeed Insights currently scores 0/100 on "Leverage browser caching of static assets" for Base44-hosted apps because the platform's edge/server layer either omits Cache-Control headers entirely or sets them too short. Since these are server-side response headers, app developers cannot fix this from within their codebase.

Requested changes:

• Vite-hashed static assets (

  /assets/index-*.css

  ,

  /assets/index-*.js

  ):

  Cache-Control: public, max-age=31536000, immutable

  These filenames are content-hashed by Vite, so a 1-year cache is safe and standard practice.

• Un-hashed static files (

  /manifest.json

  ,

  /robots.txt

  ):

  Cache-Control: public, max-age=3600

• Dynamic API endpoints (

  /api/apps/...

  ):

  Cache-Control: no-cache

  or

  no-store

  These shouldn't be edge-cached, but PageSpeed penalizes the absence of any Cache-Control header.

Impact: This is a platform-level fix that would meaningfully improve PageSpeed scores for all Base44 apps on custom domains, with no risk to app functionality.