@adia-ai/web-components 0.8.9 → 0.8.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/web-components",
-  "version": "0.8.9",
+  "version": "0.8.10",
   "description": "AdiaUI web components \u2014 vanilla custom elements. A2UI runtime (renderer, registry, streams, wiring) lives in @adia-ai/a2ui-runtime.",
   "type": "module",
   "types": "./index.d.ts",

package/styles/colors/semantics/aliases.css

@@ -18,11 +18,24 @@
    mid-tone overlay (`light-dark(X, X)`, same both schemes) rather than
    the old near-black shade-primitive overlay — both are non-adaptive
    "always this color" scrims, but the static one reads lighter/greyer
-   than the old near-black veil. */
+   than the old near-black veil.
+
+   gh#373 (2026-07-20): --a-scrim-dialog was the worst-hit case of that
+   "lighter/greyer" regression — the neutral-500-tinted 50% mid-gray read
+   nowhere near the black ~80% veil modal/drawer/tour/sheet backdrops are
+   meant to be, and the static ladder's darkest tier (strongest, 60%) still
+   isn't black. The static ladder can't grow a black-based tier without
+   retinting itself for --a-scrim-weak/-toast/-default/-strong too (all
+   four stay mapped below, unaffected) — so --a-scrim-dialog alone was
+   re-pointed off the ladder to a purpose-built black token,
+   `--a-chrome-scrim-dialog` (features.css CHROME block, non-adaptive by
+   the same "always this color" contract the whole ladder already claims). */
 
 :root, theme-ui, [theme], theme-provider {
   /* ══════════════════════════════════════════════════════════════
-     SCRIMS — Role aliases onto the static 7-step scrim ladder.
+     SCRIMS — Role aliases. Four of five ride the static 7-step scrim
+     ladder; --a-scrim-dialog is the gh#373 exception (see header
+     comment) and reads a purpose-built black chrome token instead.
      Per-family semantic tiers (weak / default / strong / peak) live
      in surfaces.css.
      ══════════════════════════════════════════════════════════════ */
@@ -30,6 +43,6 @@
   --a-scrim-weak:    var(--md-sys-color-neutral-scrim-weak);      /* 20% — hover wash */
   --a-scrim-toast:   var(--md-sys-color-neutral-scrim);           /* 30% — toast veil */
   --a-scrim-default: var(--md-sys-color-neutral-scrim-strong);    /* 40% — generic overlay */
-  --a-scrim-dialog:  var(--md-sys-color-neutral-scrim-stronger);  /* 50% — modal backdrop */
+  --a-scrim-dialog:  var(--a-chrome-scrim-dialog);                /* 80% black — modal/drawer/tour/sheet backdrop (gh#373) */
   --a-scrim-strong:  var(--md-sys-color-neutral-scrim-strongest); /* 60% (was 70%) — heaviest veil */
 }

package/styles/colors/semantics/features.css

@@ -133,5 +133,15 @@
      readouts). Must read against red / blue / dark / light underlays. */
   --a-chrome-fg:         var(--a-chrome-light);
   --a-chrome-bg:         oklch(0 0 0 / 0.4);
+  /* gh#373: dialog-class scrim (modal/drawer/tour/sheet backdrops) —
+     purpose-built black-based chrome, deliberately NOT routed through
+     the static --md-sys-color-neutral-scrim-* ladder (material-static.css)
+     — that ladder is a fixed neutral-500 mid-tone tint, never black, so
+     it cannot express an 80%-black veil without perturbing its other
+     five roles (weak/toast/default/strong all stay on the ladder; see
+     semantics/aliases.css). Kept independent from --a-chrome-backdrop
+     (50%, its own token) rather than reused, so this fix's blast radius
+     stays scoped to the dialog role alone. */
+  --a-chrome-scrim-dialog: oklch(0 0 0 / 0.8);
 
 }