/* PrintWizzard — Legacy CSS variable shim
 * v2.51.0
 *
 * Pure aliases mapping the legacy `--bg` / `--text` / `--surface` /
 * `--border` / `--muted` / `--accent` / `--good` / `--warn` / `--bad`
 * variables (defined in `style.css :root` for years) onto the new
 * `--pw-*` semantic tokens defined in `tokens.css`.
 *
 * WHY THIS EXISTS
 * ───────────────
 * The legacy `style.css` defines its own `:root { --bg: #f7f7f8 }`
 * etc. and loads AFTER tokens.css. So any rule like
 * `background: var(--bg)` picks up the hardcoded light hex and
 * IGNORES the dark-mode override that tokens.css ships. Result was
 * the unreadable disaster Eric saw on 2026-05-29 — dark page bg
 * (from `--pw-bg`), light tables (from `var(--surface)` = `#fff`),
 * cream muted text (from `var(--pw-text-muted)`) all colliding.
 *
 * This shim loads BETWEEN components.css and style.css. Its `:root`
 * block re-defines the legacy names to FORWARD to the new semantic
 * tokens. Now `background: var(--bg)` resolves through the shim to
 * `var(--pw-bg)` which is dark-mode-aware automatically. The
 * legacy `:root` block in style.css gets cascade-shadowed by the
 * shim because shim → loads later.
 *
 * Going forward (Phase 5 of the v2.44 plan, finishing in v2.52.0):
 * the template sweep in §4 of v2.51.0 moves any remaining rule
 * referencing `--bg` / `--text` / etc. directly onto the `--pw-*`
 * names. Once that's done, style.css can be deleted entirely and
 * this shim follows in the same commit.
 *
 * The shim is intentionally NO LOGIC — pure aliases. Any tweak to
 * dark-mode parity lives in `tokens.css`, not here.
 */

:root {
  /* Page surfaces */
  --bg:       var(--pw-bg);
  --surface:  var(--pw-surface);
  --border:   var(--pw-border);

  /* Text colors */
  --text:     var(--pw-text);
  --muted:    var(--pw-text-muted);

  /* Brand + semantic */
  --accent:   var(--pw-primary);
  --good:     var(--pw-success);
  --warn:     var(--pw-warning);
  --bad:      var(--pw-danger);
}