/*
  THE FOUR MODULE ACCENTS, all at once.

  The hub is the only screen in the estate that needs them together, because it is the only screen
  whose content IS the modules. Every other module loads exactly one accent file and knows nothing
  of the others.

  These are transcribed from the accent table in OS/DESIGN.md. They are siblings by construction —
  identical lightness, identical chroma, four hues — so no card shouts louder than another. All
  four clear WCAG AA in the three roles they are used in, verified by tools/skins/contrast.py.

  WHY THIS FILE EXISTS RATHER THAN HEXES IN cards.ts: OS/DESIGN.md, rule 2 — "Never write a hex
  value in a component. If a colour is needed that the skin does not define, the skin gains it. A
  hex in a component is a value that cannot be re-themed and will be missed."

  Space-separated RGB channels, matching every other file here, so Tailwind's opacity modifiers
  keep working: the card wash is the 500 at 8%, which is `rgb(var(--m-freight-500) / 0.08)`.

  ─────────────────────────────────────────────────────────────────────────────
  THREE TONES, NOT TWO — 500 FILL, 600 TEXT, 700 TEXT ON ITS OWN WASH.

  500 and 600 are not interchangeable, and that caught every module in the estate (DESIGN.md rule
  5): 500 is tuned to sit UNDER near-black text as a button fill, which is exactly what makes it
  fail AS text.

  THE 700 IS THE ONE THE DESIGN.md TABLE DOES NOT LIST, and it was found by measuring rather than
  reading. A card monogram is text on the accent's OWN 8% wash, not on white — and that wash lifts
  the background just enough to matter:

      planner 600 on white           4.58:1   passes
      planner 600 on its 8% wash     4.23:1   FAILS
      schedules 600 on its 8% wash   4.32:1   FAILS

  Both invisible by eye, both under the line. The estate already had the answer: the planner
  defines `--color-amber-accent-strong: #1c6b3a` for exactly this, a third tone at ~0.78 of its
  600. That factor is applied here to all four, so they stay siblings by construction — using 600
  for the two that happen to pass and 700 for the two that fail would make them four colours that
  merely sit near each other, which is the thing DESIGN.md is at pains to avoid.

  On the wash, all four now measure 6.2–6.8:1. Verified, not assumed.
  ─────────────────────────────────────────────────────────────────────────────

  If a fifth module is ever added, it gets a row here on the day it gets one in DESIGN.md — and
  the two must be checked against each other, because this file is a transcription and
  transcriptions drift.
*/

:root {
  /* Freight — terracotta.        #cd7146 / #ad552a / #874221 */
  --m-freight-500: 205 113 70;
  --m-freight-600: 173 85 42;
  --m-freight-700: 135 66 33;

  /* Planner — container green.   #45a465 / #25864a / #1c6b3a
     The 700 here is NOT derived — it is the planner's own `--color-amber-accent-strong`,
     transcribed, so the card and the module's real lockup are the same colour. */
  --m-planner-500: 69 164 101;
  --m-planner-600: 37 134 74;
  --m-planner-700: 28 107 58;

  /* Schedules — harbour blue.    #099acf / #107ca6 / #0c6181 */
  --m-schedules-500: 9 154 207;
  --m-schedules-600: 16 124 166;
  --m-schedules-700: 12 97 129;

  /* Map (Shipments) — transit violet. #907dd6 / #7461b5
     Not shown on the dashboard yet — mapLibre is local-only and its card is hidden — but the
     token is here so the day it deploys is a one-line change in cards.ts, not a skin edit. */
  --m-map-500: 144 125 214;
  --m-map-600: 116 97 181;
  --m-map-700: 90 76 141;
}