color.semantic is a sentiment palette — good / neutral / bad — and it cannot
express the five states an operations surface has to separate at a glance.
Building the Nagios Core overlay surfaced two failures that are properties of
the palette, not of that consumer:

  - semantic.success #3D5328 is a deep olive tuned to clear AAA as text on
    white. Used as a cell tint it loses its hue and reads grey-green.
  - There is no orange, so UNKNOWN had to borrow chart.5 #8C5A3C, a clay brown
    that reads as a weak red beside CRITICAL — after which PENDING's neutral
    grey sat too close to that near-grey brown and read as UNKNOWN.

Both survived review because the code referenced canonical tokens throughout
and passed every contrast check. What failed was legibility as a RAMP, which
nothing in the system was measuring.

Adds themes.<t>.status for tti, tti-dark and tti-hc: five states x three roles
(base for text and edges, fill for a chip, ink for the word inside it). Hues are
inherited from what Nagios Core itself ships, because green -> yellow -> orange
-> red is operator muscle memory and a prettier ramp would be a legibility
regression dressed as a brand win. tti-hc renders outlined chips so no state
depends on a colour-on-colour pair.

Values were derived in OKLCH and are authored in tokens.json like everything
else. scripts/audit-status-palette.mjs re-derives the constraints and fails on
any breach: hue identity within 14deg, chips >= 0.075 apart in OKLab, chip
lightness descending with severity, no status colour within 0.10 of brand
maroon, and WCAG 2.2 AA as the floor with tti-hc held to AAA. It needs neither a
browser nor a Nuxt build, unlike audit:contrast, so it can gate every commit.
Each rule was negative-tested.

Three of those guards exist because the unconstrained solve actually broke them:
CRITICAL landed at #77020b, 0.076 from brand maroon — "down" painted the colour
of the chrome.

Power BI's good/neutral/bad still resolve to the semantic palette. Re-pointing
them would change every report already built on tti-theme.json, and sentiment is
arguably right for a KPI card; ADR-0013 records that as an open decision rather
than an oversight.

@@ -0,0 +27,4 @@
+
+## 2. The 3 Primary Consumption Vectors for Comm
+
+### Vector A: WordPress & Kadence Websites

@@ -98,0 +552,4 @@
+    children: [
+      { label: "Document Verification", to: "/admin", icon: "lucide:shield-check" },
+      { label: "Review Cadence", to: "/admin", icon: "lucide:calendar-clock" },
+      { label: "Reader Issues Triage", to: "/admin", icon: "lucide:life-buoy" },

@@ -37,0 +309,4 @@
+  }
+
+  const crumbs: Crumb[] = [{ label: "Home", to: "/" }];
+

@@ -329,0 +1051,4 @@
+                <span
+                  class="w-1.5 h-1.5 rounded-full shrink-0"
+                  :class="selectedVersion === `v${pkgVersion}` ? 'bg-status-ok' : 'bg-status-warning animate-pulse'"
+                />

@@ -133,3 +143,3 @@
-  padding-bottom: 0.5rem;
+  padding-bottom: 0.625rem;
 }
 

@@ -19,6 +19,11 @@
   --tti-teal: #4A8892;
   --tti-sage: #66814F;
   --tti-charcoal: #221F1F;

@@ -358,3 +362,4 @@
+  padding-bottom: 0.625rem;
   margin: 0;
 }