/*
 * Stale-asset fallback for deployment skew (Sentry digest: "Unable to
 * preload CSS for /assets/vibeStyles-<hash>.css" on vanity room routes such
 * as /legacyventure, /SCS, /jon).
 *
 * Both vercel.json configs rewrite MISSING hashed /assets/*.css requests
 * here (Vercel rewrites never override files that exist on the
 * deployment's filesystem, so real hashed stylesheets are always served
 * first). The rewrite requires a Vite hash suffix (-<8+ base64url chars>)
 * so a genuinely missing non-hashed stylesheet still 404s loudly.
 *
 * Why: after a deploy replaces hashed CSS assets, a still-open tab (or a
 * cached index.html in an in-app WebView) from the previous build asks for
 * its old hashed CSS chunk when a lazily loaded feature needs it. Without
 * this fallback the request 404s, Vite fires vite:preloadError, and builds
 * older than the graceful-degradation fix (#1326) re-throw and crash the
 * whole lazy import (element wizard would not open) while spamming Sentry
 * with an unhandled rejection on every attempt. Serving an empty but valid
 * stylesheet makes the <link rel="stylesheet"> preload SUCCEED: the JS
 * module loads and the feature keeps working with temporarily degraded
 * styling until the user's next natural reload pulls the current build.
 *
 * Intentionally CSS-only. A missing JS chunk can never be masked (an empty
 * module would crash with `default` undefined), so JS assets keep 404ing
 * and flow through the reload recovery in main.jsx.
 *
 * Do not add real rules here: this file stands in for arbitrary stylesheets,
 * so it must stay side-effect free.
 */