/* ═══════════════════════════════════════════════════════════════
   Material Design token bridge — RETIRED (2026-07-14)

   This file used to declare `--md-sys-color-X: var(--a-Y)` forward
   aliases (Phases 1-3 of the Material adoption, contract:
   .claude/docs/specs/material-color-bridge-contract.md) — the
   direction was `--a-*` computes the value, `--md-sys-color-*`
   aliases it for consumption.

   The "replace the computational layer" phase (same date) inverted
   this: `--md-sys-color-*` is now populated directly from the static
   export (colors/material-static.css, loaded in colors/index.css
   BEFORE this file used to load), and semantics/core.css's `--a-*`
   family blocks now read FROM `--md-sys-color-*` instead of the other
   way around. Keeping this file's old forward declarations active
   would create a real circular reference — `--md-sys-color-primary:
   var(--a-primary)` here fighting `--a-primary: var(--md-sys-color-
   primary)` in core.css, both on `:root` — which resolves to CSS's
   guaranteed-invalid value for both properties and blanks the whole
   color system. So this file now declares nothing; it is no longer
   imported by colors/index.css (removed from the active import list,
   left as a comment there pointing here).

   `scripts/refactor/adopt-material-tokens.mjs` parses this file's
   `--md-sys-color-X: var(--a-Y)` shape to build its rename map — that
   codemod already ran its one sweep (2472 call sites) and is a
   disposable one-time tool per this repo's established codemod
   pattern (see `scripts/refactor/undo-od5-token-shadowing.mjs`); it
   is not expected to run again against this file's now-empty body.
   ═══════════════════════════════════════════════════════════════ */
