@bsuite/theme 0.11.1 → 0.11.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bsuite/theme",
-  "version": "0.11.1",
+  "version": "0.11.2",
   "type": "module",
   "license": "UNLICENSED",
   "publishConfig": {

package/src/css/vars.css

@@ -67,6 +67,25 @@
   --neon-electric-teal:  oklch(0.600 0.130 195);   /* success */
   --neon-electric-deep:  oklch(0.380 0.140 270);   /* secondary action */
 
+  /* The two words the estate uses loosely, pinned to values. Operator ruling
+     2026-08-02 ("white is primary: #f8f9fa") in terms: "define --white and
+     --black once in the token source and reference them everywhere; never
+     write either literal inline." This is that definition — it did not exist
+     until 2026-08-13, which is why the sanctioned replacement values named in
+     packages/eslint-config/rules/no-hardcoded-colours.js had no token to point
+     at and every legacy pure-white literal got fixed by inventing a fresh
+     near-white instead.
+     CHOSEN FROM THE CONTRACT, NOT INVENTED — both are now recorded in
+     packages/theme/docs/d2c-theme-source-of-truth.html (L1), which is what the
+     palette gate reads. Mode-invariant on purpose: these name the colours, not
+     a surface role, so they are NOT overridden under .dark. If you want "the
+     page background", that is --role-bg-body and it does flip.
+     Note the banned endpoints are DESCRIBED here and never spelled out. C1
+     scans comments and counts a literal whether or not the sentence around it
+     says "never" — writing one to forbid it raises the ratchet. */
+  --white:               oklch(0.982 0.002 247.8); /* the near-white, #f8f9fa */
+  --black:               oklch(0.166 0.026 269.4); /* the near-black, #0a0e1a */
+
   /* ============================================================
      LAYER 2 — SURFACE PRIMITIVES (light mode)
      ============================================================ */
@@ -554,6 +573,23 @@
   --role-bg-input:   oklch(0.240 0.020 260);
   --role-bg-sunken:  oklch(0.145 0.022 268);
   --role-border:     var(--dark-border);
+  /* Dark-mode `--role-border-strong` was MISSING, so `.dark` inherited the
+     light value from `:root` — oklch(0.880 0.008 250), i.e. #d4d8dd. Measured
+     against `--role-bg-panel` that is 12.88:1: a near-white hairline on navy,
+     in the 50 files across crm7, conduit, BSU and throughput that use
+     `border-strong`. Not a subtle miss — the brightest thing on the panel.
+
+     `braden.css` has carried both variants since it was written (0.900/0.840
+     light, 0.320/0.420 dark). Only the D2C theme was half-defined, which is
+     why nobody reading the corporate theme would spot it.
+
+     Value is oklch(0.52 0.02 248) from the D2C source-of-truth document, so
+     the palette whitelist accepts it. It sits +0.09 L above `--dark-border`
+     (0.428), mirroring the light pair's step, and measures 3.36:1 against
+     `--role-bg-panel` and 3.61:1 against `--role-bg-sunken` — clearing the
+     WCAG 1.4.11 non-text-contrast floor of 3:1 on both dark surfaces.
+     `--role-border` itself is 2.26:1, which is why "strong" has to exist. */
+  --role-border-strong: oklch(0.52 0.02 248);
 
   /* Role text variants rebind for the dark surface — all AAA on navy. */
   --role-primary-text: oklch(0.721 0.215 262.9);  /*  7.01:1 ✓ AAA */