/* ═══════════════════════════════════════════════════════════════════════════
   THE SYSTEM'S PAGE FLOOR — load-bearing, and therefore not in the user's file.

   ⚠ THIS RULE LIVED IN project_styles.css AND SHOULD NOT HAVE (SPI-577,
   2026-09-30). That file is the USER's — `1d90292` is titled "project_styles.css
   is the user's file, and it ships empty" — and a load-bearing default sitting
   in the file we hand someone to edit is a default they can delete by tidying,
   and one that a replaced project file drops silently. Shawn: "it should not
   really be in the user's css that we give them to edit if it is load bearing."

   ⚠ AND IT CANNOT SIMPLY BE DELETED. Without a painted body background the page
   falls to the UA canvas — white in light mode, about #121212 in dark. That is
   still readable, which is why it would go unnoticed, but every dark -rNN step
   was SOLVED against --page-surface #151a1f, so the whole ladder drifts:

       --c1-r12  1.20 -> 1.28      --c1-r45  4.47 -> 4.79
       --c1-r30  2.99 -> 3.20      --c1-r70  7.03 -> 7.53

   all outside the +/-0.05 the palette-ratios suite enforces. Painting the
   surface is what makes the contrast ladder true rather than aspirational.

   LAYER: defaults (3 of 19). Deliberately BELOW project (7), so a hand override
   in the user's project_styles.css beats this floor — which it could not do
   while the two shared a file and a layer. The site and page columns beat it
   too, from layer(site) and layer(page), which sort later still.
   ═══════════════════════════════════════════════════════════════════════════ */
/* #ffffff is the fallback for a page served without the palette. */
body { background: var(--page-surface); }