URGENT: Railway CDN serving cached frontend files despite successful deployments

PROBLEM:

- Deployments are building successfully (logs show success)

- Server is running correctly on port 8080

- API endpoints work (/api/me requests visible in logs)

- Static files served from /app/build

- BUT live website still shows old cached frontend content

EVIDENCE:

1. Build logs show successful deployments

2. Server logs show: "Serving static files from: /app/build"

3. API requests work (visible in Railway logs)

4. Backend has correct files (verified)

5. Live site still shows old cached version

WHAT I'VE TRIED:

- Multiple clean rebuilds with fresh node_modules

- Cache-busting headers (Cache-Control: no-cache, no-store, must-revalidate)

- Cloudflare cache purge

- Multiple deployment pushes with different file hashes

- Cache-busting parameters in URLs

TECHNICAL DETAILS:

- Domain: stmtfusion.com

- Railway Edge: railway/europe-west4-drams3a

- Container restarts working properly

- Database connected and working

- API endpoints responding correctly

ISSUE:

Railway CDN is aggressively caching frontend files and not invalidating cache despite successful deployments.

REQUEST:

Please clear Railway CDN cache for stmtfusion.com or provide guidance on how to force cache invalidation.

This is blocking all frontend updates and affecting the live website.