/* ═══════════════════════════════════════════════════════════════════════
   __darmaster/css/skins/entity-darmaster.css
   DARMASTER skin — the internal platform's OWN base palette.

   DARMASTER is an aggregate scope (not a legal entity), so it never had an
   entity skin file and its colour fell through to the tokens.css
   --brand-primary fallback (#46331E, the DARX brown). That made the skin
   manager's "Reset to default" land on BROWN.

   This file gives DARMASTER a real default skin like every sibling entity,
   so CHARCOAL is the genuine default: it seeds the manager's inherited
   value (darx_skin_entity_css_vars) AND is loaded at render time by
   darx_load_skin('DARMASTER', …). Per-page overrides still live in
   __darmaster/api/skin_values.csv (scope DARMASTER) and win over this.
   ═══════════════════════════════════════════════════════════════════════ */

/* DARMASTER identity baseline. The skin manager can override from
   skin_values.csv; a Reset clears that override and falls back HERE. */
:root {
  --brand-primary:   #4A4A4C;   /* charcoal — the platform's neutral graphite */
}