/* ══════════════════════════════════════════════════════════════════
   theme-paper.css — the non-VFD look.

   Palette AND weight — not the palette alone. Confirmed against Figma
   1:67 (desktop_photograph, a full paper page): title, description,
   and even the tree/toggle sharing that page all run Doto SemiBold,
   where terminal runs Medium everywhere. So weight is a property of
   which surface you're reading, the same as colour is — a paper page
   is not a recoloured terminal page, it's set in a heavier cut.

   Everything else about this file is still true: it declares none of
   --fx-crest, --fx-panel, --fx-toggle, --glow-crest or --glow-text,
   so base.css falls back to `none` for every one of them: no glow, no
   flicker, no phosphor.

   That is the standing rule made structural. Paper is not terminal
   turned down — there is no dial. A page is in the VFD vibe or it
   isn't, and the way it isn't is by this file staying empty of
   effects. Adding a faint glow here to "soften the transition" would
   be the exact mistake the rule exists to prevent.

   js/theme.js also stops the flicker rAF loop while paper is active,
   so --b1/--b2 aren't merely unread — nothing is computing them.

   Colour from Figma 1:67 (desktop_photograph): surface #b8c2c2,
   text #070909.
══════════════════════════════════════════════════════════════════ */

:root[data-theme="paper"]{
  --bg: #b8c2c2;
  --fg: #070909;
  --weight: 600;          /* Doto SemiBold — Figma 1:109 / 1:111 / 1:1199 */
}