/* =========================================================================== KREIS SUITE — shared stylesheet (single source of cross-app chrome). ONE physical file at C:\KreisOps\shared\suite.css, served by every app at /suite.css from local disk (no cross-origin runtime dependency - a module keeps this styling even if the auth server is down). Link it in each app's BEFORE that app's own stylesheet, so the app can still override. Started 2026-09-11 (Nick: standardize the shared chrome, not the rendering model). Migrate a component here once, then delete the per-app copies - the back-to-home button is the first. Keep additions self-contained and hardcode the suite palette below so a rule never depends on which app's variables happen to be defined. =========================================================================== */ /* ---- suite palette (canonical color VALUES for the whole suite) --------- Namespaced with --k so defining them here can never clobber an app's own variables. An app opts in by sourcing its own tokens from these, e.g. `--bg: var(--kbg, #000)` - the fallback keeps the app rendering even if this file fails to load. Change a colour ONCE here and every opted-in app follows. The Auth server (home + Suite System + all its pages) sources its whole palette from these as of 2026-09-11. */ :root { --kbg:#000; --kink:#e8edf3; --kmuted:#8b9aac; --kpanel:#0f141b; --kpanel-hi:#171d25; --kline:#2a3340; --kline-hi:#5c6675; --klive:#1e8a46; --klive-ink:#8fe6b0; --kbad:#8a1e1e; --kbad-ink:#e6a0a0; --kpend:#e8a13c; } /* ---- ONLY the palette lives here -------------------------------------- LESSON (2026-09-11): visual chrome - the header wordmark, the back button - was briefly shared here too, but removing an app's LOCAL copy and depending on this file to arrive left the guest-mailer header huge when a stale/missing suite.css did not reach the browser. A regular CSS rule has no fallback, so a page that DELETES its local copy has nothing to fall back on. Only the palette can be shared safely, because `var(--kbg, #000)` carries its own fallback. So: palette here (opt-in via var + fallback), visual chrome stays LOCAL in each app (they match by convention, kept in sync by hand). Do NOT move header/button/card rules here again unless a cache-busted `?v=` link makes delivery reliable AND every consumer keeps a local fallback. */