/*
 * Runtime override surface for the colour theme. THIS FILE IS DELIBERATELY
 * EMPTY.
 *
 * The default values live in src/app/theme.css and ship inside the CSS
 * bundle. This file is loaded *after* that bundle (the <link> at the end of
 * <head> in src/app/layout.tsx), so any token redeclared here wins — plain
 * CSS cascade, no JavaScript, no hydration involved.
 *
 * Empty is the point: keeping a copy of every value here would immediately
 * create two places that have to agree, which is the exact failure mode
 * docs/adr/0008-env-build-time-thuan.md removed when it deleted env.json.
 * theme.css stays the single source of truth; this file only holds the
 * deltas, and only when somebody actually wants a different colour.
 *
 * To change the theme: uncomment the block below, edit the values, rebuild
 * and redeploy the image. Files under public/ are served with
 * `Cache-Control: no-cache` (see next.config.ts), so a redeployed pod serves
 * the new colours to the next request — no bundle rebuild of the JS/CSS
 * needed, and no cache-busting query string.
 *
 * Rules, each one a real way to break this — see docs/adr/0011:
 *
 * 1. Use `:root:root`, doubled on purpose. It beats theme.css by specificity
 *    rather than relying on the <link> order Next happens to emit today.
 *    Plain `html` is *lower* specificity than `:root` and would lose.
 * 2. Only redeclare tokens that already exist in theme.css. Tailwind never
 *    scans public/, so a new token here generates no utility class and a
 *    class name written here does nothing.
 * 3. Never delete this file, even while it is empty. Next fixes the list of
 *    public/ files at server start: replacing this file's *contents* is
 *    picked up on the next request, but adding it back as a *new* file at
 *    runtime returns 404.
 * 4. A syntax error here fails silently — CSS drops the broken rule and the
 *    colour simply stays at its default. There is nothing to typecheck; look
 *    at the page.
 *
 * The full token list is in src/app/theme.css. Values may be any CSS colour
 * syntax — hex is fine here even though theme.css writes oklch.
 */

/*
:root:root {
  --primary: #1ca8c3;
  --primary-hover: #74d9ee;
  --secondary: #38a696;
  --shell-band: #f0f0f0;
  --nav-active: #0ea5e9;
}
*/
