/* Portal CSS override layer.
 *
 * This file is served verbatim by SvelteKit's static-asset handler
 * at /overrides.css and is linked from +layout.svelte AFTER the
 * bundled app stylesheets so anything declared here wins on
 * specificity ties.
 *
 * Why this exists: edits to bundled CSS (Svelte <style> blocks or
 * imported .css files) need a full Vite production rebuild + redeploy
 * pipeline (~30s+). Edits to THIS file ship via the auto-deploy
 * static lane — no build, no restart, ~2-5 seconds end-to-end.
 *
 * Scope: global utility tweaks only. Don't try to scope rules to a
 * single component from here — Svelte's scoped-class hashes are
 * regenerated on every build, so any selector tied to a `.svelte-xyz`
 * class will silently stop matching next deploy. If a tweak needs to
 * be component-scoped, put it in the component's own <style> block.
 *
 * Good fits here:
 *   - colour / spacing nudges on portal-wide classes (.field-help,
 *     .browse-row, .tree-name, .card, etc.)
 *   - typography overrides on element selectors (h1, h2, p)
 *   - body-level layout tweaks
 *
 * Bad fits:
 *   - selectors with Svelte's scoped-class hashes (svelte-abc123)
 *   - structural changes that need new DOM
 *   - anything that breaks if accidentally not loaded
 */