@adia-ai/web-components 0.8.47 → 0.8.50

package/index.css

@@ -13,8 +13,7 @@
  *   @adia-ai/web-components/styles/index.css     (primitives only)
  *   @adia-ai/web-components/styles/tokens.css    (tokens only)
  *   @adia-ai/web-components/styles/themes.css    (optional — named theme presets)
- *   @adia-ai/web-components/styles/prose.css     (optional — prose context)
- *   @adia-ai/web-components/styles/verse.css     (optional — compact density)
+ *   @adia-ai/web-components/styles/scale.css     (optional — [scale] sizing register)
  */
 
 @import "./styles/host.css";

package/package.json

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

package/styles/README.md

@@ -297,7 +297,7 @@ styles/
 │   └── layout.css          #   [hidden] [nomargin] [grow]
 │
 ├── themes.css              # CONTEXT: 8 named themes + light/dark scheme overrides ([theme])
-├── prose.css               # CONTEXT: opt-in article typography ([prose])
+├── scale.css               # CONTEXT: six-tier ancestor sizing register ([scale])
 ├── resets.css              # global RESET (box-sizing, scrollbar, focus, normalize)
 ├── fonts.css               # @font-face declarations + font-family primitives
 ├── components.css          # per-component @import barrel

package/styles/api/sizing.css

@@ -172,7 +172,7 @@
 
    Sets --a-gap-self, a NON-inheriting token, so an explicit gap on a
    parent does NOT leak into nested layout primitives. This is the
-   counterpart to --a-gap, the AMBIENT gap set by [size]/[prose]/:root
+   counterpart to --a-gap, the AMBIENT gap set by [size]/[scale]/:root
    (which DOES inherit — `<div size="sm">` shifts the whole subtree).
    Gap-reading components resolve `var(--a-gap-self, var(--a-gap))`:
    explicit-if-present, else fall through to the inherited ambient.

package/styles/colors/material-static.css

@@ -28,18 +28,40 @@
    (host.css) puts `context` (where [theme="x"] rules live) after
    `tokens` (this file's :root block) in the cascade-layer order, and
    layer order always wins over selector specificity — so a themed
-   ancestor's raw-stop override wins, and every semantic role above that
-   reads `var(--md-sys-color-{family}-NNN)` re-resolves through it at
-   each descendant, by ordinary CSS custom-property inheritance (not
-   fixed to its :root declaration site). Verified two ways: the cascade
-   mechanics above, and empirically (Playwright, file:// harness) —
-   `--md-sys-color-primary-600` measured `oklch(0.5493 0.1051 226.08)`
-   at :root vs `oklch(0.5493 0.0946 216.96)` under `[theme="atlas"]`,
-   the atlas-rotated hue, not the default. info/success/warning/danger
-   are correctly left unthemed (deliberate — status meaning stays
-   constant across themes, themes.css's own header). Only
-   `--a-brand-hue`/`-radius-k`/`-density`/`-shadow-intensity` were ever
-   the OTHER stated-live knobs; that part of the original claim stands.
+   ancestor's raw-stop override wins there. Verified empirically
+   (Playwright, file:// harness) — `--md-sys-color-primary-600` measured
+   `oklch(0.5493 0.1051 226.08)` at :root vs `oklch(0.5493 0.0946
+   216.96)` under `[theme="atlas"]`, the atlas-rotated hue, not the
+   default.
+
+   CORRECTION #2 (gh#1863, 2026-08-22) — the "every semantic role...
+   re-resolves through it at each descendant, by ordinary CSS
+   custom-property inheritance" claim directly above was WRONG for a
+   descendant-scoped `[theme]` and has been removed; the raw-stop
+   measurement above never actually tested an alias. Per CSS
+   custom-property semantics, `var()` inside a property's value
+   substitutes at computed-value time on the element where THAT property
+   is declared — every alias in this file is declared once, at `:root`,
+   so it substitutes using `:root`'s own raw stops and that computed
+   value is what inherits downward as a plain value, not a live
+   reference. `[theme]` on `:root`/`<html>` itself works (root is also
+   the alias's declaration site, so the raw-stop override and the alias
+   substitution happen at the same element) — but `[theme]` on a
+   DESCENDANT (the documented, shipped `<theme-provider theme="X">`
+   nested-scoping shape, components/theme-provider/) only rotates the
+   raw stop there; every alias stayed pinned to the default theme,
+   silently, because no rule redeclares the alias itself at that
+   descendant. Confirmed both ways (Playwright, file:// harness,
+   `--md-sys-color-primary` vs `-primary-600` under root- and
+   descendant-scoped `[theme="atlas"]`) and closed by generating a
+   themed redeclaration of every alias into each of themes.css's 12
+   `[theme="X"]` blocks (`scripts/build/generate-theme-aliases.mjs`,
+   `npm run check:theme-scoped-alias` — the regression gate).
+   info/success/warning/danger are correctly left unthemed (deliberate —
+   status meaning stays constant across themes, themes.css's own
+   header). Only `--a-brand-hue`/`-radius-k`/`-density`/
+   `-shadow-intensity` were ever the OTHER stated-live knobs; that part
+   of the original 2026-07-14 claim stands.
 
    NOT touched by this replacement: `--a-brand-*` (no adia.css palette
    to source from), `--a-link*`/`--a-focus-*`/`--a-data-*` (no direct

package/styles/host.css

@@ -21,10 +21,7 @@
 
    ── Opt-in add-ons (link separately when wanted) ─────────────────────
      styles/themes.css   the [theme] preset switcher      (@layer context)
-     styles/prose.css    the [prose] content context           (@layer context)
-     styles/verse.css    the [verse] compact register          (opt-in density)
-     styles/scale.css    the [scale] six-tier register — supersedes
-                          [verse]/[prose]                       (@layer context)
+     styles/scale.css    the [scale] six-tier sizing register (@layer context)
 
    See ADR-0035 (foundation reorg) + ADR-0038 (cascade layers). */
 

package/styles/index.css

@@ -7,8 +7,8 @@
      <link rel="stylesheet" href="@adia-ai/web-components/styles/host.css" />
      <link rel="stylesheet" href="@adia-ai/web-components/styles/index.css" />
 
-   Opt-in layers (theme presets, prose context, verse density) are linked
-   separately — styles/themes.css, styles/prose.css, styles/verse.css.
+   Opt-in layers (theme presets, the [scale] sizing register) are linked
+   separately — styles/themes.css, styles/scale.css.
 
    Composite-element CSS (chat-shell, editor-shell, admin-shell, etc.)
    lives in @adia-ai/web-modules — link its barrel separately:

package/styles/scale.css

@@ -5,11 +5,11 @@
    lookup (never a multiplier — multipliers drift height/font/icon
    off coherent rows; agent-ui ADR-0038 precedent):
 
-     [scale="ui-sm"]       dense product UI    (≡ legacy [verse])
+     [scale="ui-sm"]       dense product UI
      [scale="ui-md"]       the base register   (≡ :root defaults)
      [scale="ui-lg"]       touch/presentation UI
      [scale="content-sm"]  compact article
-     [scale="content-md"]  long-form default   (≡ legacy [prose])
+     [scale="content-md"]  long-form default
      [scale="content-lg"]  hero / marketing
 
    Control-band overlap: content-sm ≡ ui-md and content-md ≡ ui-lg
@@ -20,25 +20,19 @@
    the full *-sm/md/lg families, so the universal [size] attribute
    keeps working on and below a scaled element. Tokens compute at
    their declaration site, so each tier RE-DECLARES every pointer it
-   shifts (the [verse]/[prose] gotcha), and carries explicit
-   [size] tier rules — this context layer shadows the utilities-layer
-   global [size] rules for any token the tier pins.
-
-   Selector shape: [scale][scale="X"] (0-2-0) so a tier
-   deterministically beats the legacy [verse]/[prose] attributes
-   (0-1-0) regardless of stylesheet adoption order. Never a bare
-   [scale] selector — heatmap-ui reflects scale="linear|log" and
-   legacy theme-provider reflects scale="verse|prose".
-
-   [verse]/[prose] are DEPRECATED in favor of ui-sm / content-md and
-   are removed at v1.0. Do not combine verse|prose with [scale] on
-   one element.
-
-   ui-sm, ui-md and content-md are byte-derived from verse.css,
-   :root and prose.css respectively — an unscaled page and a
-   [scale="ui-md"] page render identically. ui-lg, content-sm and
-   content-lg are DEDUCED rows (one-step shifts of their neighbors)
-   — proposed, tune to taste.
+   shifts, and carries explicit [size] tier rules — this context
+   layer shadows the utilities-layer global [size] rules for any
+   token the tier pins.
+
+   Selector shape: [scale][scale="X"] (0-2-0). Never a bare [scale]
+   selector — heatmap-ui reflects scale="linear|log", a different
+   vocabulary on the same attribute name.
+
+   ui-sm, ui-md and content-md were originally byte-derived from the
+   now-removed compact-density and long-form-content sheets (gh#1885) —
+   an unscaled page and a [scale="ui-md"] page render identically.
+   ui-lg, content-sm and content-lg are DEDUCED rows (one-step shifts
+   of their neighbors) — proposed, tune to taste.
 
    --a-density is orthogonal and composes: every spacing value rides
    the --a-space-* rungs and every control row multiplies
@@ -302,7 +296,7 @@
     --a-size-lg: calc(var(--a-density) * 2.75rem); /* 44px */
     --a-size: var(--a-size-md);
 
-    /* prose type register (prose.css byte-values) */
+    /* content-md type register (byte-values from the removed prose sheet, gh#1885) */
     --a-display-sm: clamp(24px, 20px + 1.5vw, 36px);
     --a-display-md: clamp(32px, 24px + 3vw, 56px);
     --a-display-lg: clamp(40px, 32px + 4vw, 80px);
@@ -644,10 +638,9 @@
      the base row). */
 
   /* ═══════════════ Content-band flow enhancements ═══════════════
-     Ported from prose.css so every content tier gets them.
-     [scale^="content-"] is value-prefixed — cannot collide with
-     heatmap-ui's scale="linear|log" or legacy theme-provider
-     scale="verse|prose". */
+     Ported from the removed prose sheet (gh#1885) so every content
+     tier gets them. [scale^="content-"] is value-prefixed — cannot
+     collide with heatmap-ui's scale="linear|log". */
   [scale^="content-"] > :is(p, ul, ol, blockquote, pre, table, dl) {
     max-width: var(--prose-max-width);
   }