/*
 * SWDS-GCAMS design tokens — where they are, and why not here.
 *
 * This file used to re-declare the whole `--gc-*` block as a hand-kept copy of
 * the block already compiled into `vendor/oneui/oneui.min.css`. Its own header
 * admitted the duplication and asked whoever edited the Sass to remember to
 * regenerate this file.
 *
 * The copy was not merely redundant. It is linked *after* the theme stylesheet,
 * so once a theme began emitting its own palette this file overrode it on every
 * token, and a themed page would have rendered in the calm palette under a
 * themed sidebar. A second copy of a value is a second answer to the same
 * question, and load order decided which one won.
 *
 * The tokens now live in exactly one place:
 *
 *   OneUI_Template_HTML/src/assets/_scss/custom/_tokens.scss   the mixin
 *   OneUI_Template_HTML/src/assets/_scss/custom/_main.scss     :root, the calm default
 *   OneUI_Template_HTML/src/assets/_scss/oneui/themes/*.scss   one call per theme
 *
 * compiled into `oneui.min.css` and `themes/*.min.css`. Edit the Sass and
 * rebuild; section 13 of docs/dev/12-Frontend-Integration-Guide.md has the
 * commands.
 *
 * `src/tests/test_palette_contrast.py` reads the compiled files and measures
 * every pair in every theme, so a token that drifts fails a test rather than a
 * page.
 *
 * The file is kept rather than deleted because both base templates link it, and
 * a 404 on every page view is a worse trade than an empty stylesheet. It is the
 * right home for any token that is genuinely runtime-only. There are none today.
 */