@adia-ai/web-components 0.8.47 → 0.8.50

package/components/table-toolbar/table-toolbar.examples.md

@@ -3,11 +3,13 @@
 ## Wiring
 
 ```html
-<table-toolbar-ui for="members" text="All employees" count="32"></table-toolbar-ui>
 <card-ui>
-  <section-ui bleed>
-    <table-ui id="members" sortable raw>…</table-ui>
-  </section-ui>
+  <header>
+    <table-toolbar-ui for="members" text="All employees" count="32"></table-toolbar-ui>
+  </header>
+  <section bleed>
+    <table-ui id="members" sortable>…</table-ui>
+  </section>
 </card-ui>
 ```
 

package/components/table-toolbar/table-toolbar.yaml

@@ -88,11 +88,45 @@ props:
       in "Showing 1–25 of 320"). Distinct from pagination-ui's `total`
       (total PAGES) — this is total ROWS; deliberately not spelled `total`
       to avoid that cross-sibling name collision (ADR-0063 B5). See
-      rangeStart.
-    type: number
+      rangeStart. Explicit range-total="?" (gh#1877, ADR-0082 Amendment) is
+      the OPEN/unproven-total state — cursor/hasMore server paging with no
+      known row count yet: the summary reads "Showing X–Y" with no "of N",
+      requiring only [range-start]/[range-end] (> 0) to render, not
+      rangeTotal too. Resolves to the normal finite summary the moment a
+      real number replaces the "?". Named identically to table-footer-ui's
+      own [range-total] (ADR-0082 §"same name on both companions").
+    type: [number, string]
     default: 0
     reflect: true
     attribute: range-total
+  rangeOf:
+    description: >-
+      gh#1877, ADR-0082 Amendment — secondary whole-set total for the
+      "filtered-of-whole" shape: a client-side facet narrows [rangeTotal]
+      (a filtered count) while rangeOf names the unfiltered set size, e.g.
+      "Showing 1–4 of 4 traversals (6 total)". Appends "(of <rangeOf>
+      total)" onto the normal finite range summary; unset (the default)
+      changes nothing. Never applies while the summary is in its open
+      ("?") or opted-out (all-zero) state. Named identically to
+      table-footer-ui's own [range-of] (ADR-0082 §"same name on both
+      companions").
+    type: number
+    default: 0
+    reflect: true
+    attribute: range-of
+  rangeNoun:
+    description: >-
+      gh#1877, ADR-0082 Amendment — optional per-slice noun appended after
+      the range total ("of 80 users") so consumers stop hand-painting the
+      noun themselves. Applies in both the normal finite range summary and
+      the open/unproven-total summary ("Showing 51–100 users" with no "of
+      N"). Unset (the default) changes nothing. Named identically to
+      table-footer-ui's own [range-noun] (ADR-0082 §"same name on both
+      companions").
+    type: string
+    default: ""
+    reflect: true
+    attribute: range-noun
   pageSize:
     description: >-
       Current rows-per-page value, shown as the selected option in the
@@ -190,6 +224,19 @@ props:
     default: false
     reflect: true
     attribute: chrome-only
+  titleAlways:
+    description: >-
+      Opt out of the scope-reconciliation title hide: by default, a filled
+      [slot="scope"] region (a select/menu whose own displayed value already
+      names the entity being listed) hides the separate [text]/[count]
+      title cluster next to it, since together they'd say the same thing
+      twice. Set [title-always] to keep the title cluster visible alongside
+      a filled scope slot — e.g. a scope select PLUS an explicit
+      text/count title on the same row (gh#1879).
+    type: boolean
+    default: false
+    reflect: true
+    attribute: title-always
   placeholder:
     description: Placeholder text for the search input.
     type: string
@@ -270,6 +317,26 @@ slots:
       stamp. Empty (the default) has zero footprint on existing consumers.
   actions:
     description: Trailing action area — primary buttons (e.g. "New row") rendered after the search input, [slot="actions-leading"], and the page-size select.
+  summary:
+    description: >-
+      gh#1883 — trailing, text-tier cluster for an aggregate datum that
+      belongs with the table but has no home in the range summary or the
+      actions area (e.g. batch-detail's line-items Subtotal:
+      `<span slot="summary">Subtotal <strong>$1,240.00</strong></span>`).
+      Rendered in the same flex row, after [slot="actions-leading"] and
+      before the page-size select / [slot="actions"] — closer to the
+      trailing edge than [slot="scope"]/[range-*], since it reads as a
+      result/total rather than pagination or view-switching context. Text
+      sized via [--table-toolbar-summary-size] (shared with the
+      "Showing X–Y of N" range summary — both are the same text tier).
+      Plain author-supplied markup, same real-insertion-point pattern as
+      every other table-toolbar slot — no forced typography beyond the
+      font-size token. Stays visible at every ADR-0076 compaction stage: it
+      is DATA (an aggregate figure the consumer chose to show), not chrome,
+      so it is never dropped or compacted the way the range summary/
+      controls are — a consumer needing narrower-container behavior owns
+      that via its own slotted content, not a component-side compaction
+      rule. Empty (the default) has zero footprint on existing consumers.
 states:
   - name: idle
     description: Default, ready for interaction.
@@ -307,29 +374,40 @@ a2ui:
     - >-
       Pair <table-toolbar-ui> with <table-ui> via [for="<table-id>"]
       (or rely on first-sibling fallback when both are inside the
-      same parent). One toolbar per table. The doubled-chrome hazard is
-      a TITLE COLLISION, not a blanket card-header ban (gh#1807, SPEC
-      REQ-C-004): a toolbar carrying [text] must not share a card with
-      a heading-slotted <card-ui> <header> — that pairing doubles the
-      title row. A title-less toolbar (no [text]) inside a card whose
-      <header> owns the title is the canonical table-in-card
-      composition (see the table-in-card pattern) and is NOT doubled
-      chrome — the toolbar renders only its count/search/filter/sort/
-      columns cluster, with the title living in the card header alone.
+      same parent). One toolbar per table. <table-toolbar-ui> MAY sit
+      as <card-ui>'s <header>'s sole child — verified in a rendered
+      browser to lay out full-width identically to the
+      sibling-above-card pattern (gh#1807/#1884, ADR-0080) — but do
+      NOT also give that same <header> a slot="heading"/slot="action"
+      child: card.css's grid mode then shrinks the toolbar to its own
+      content width and collapses its flex-row layout. The
+      doubled-chrome hazard is a TITLE COLLISION, not a blanket
+      card-header ban (SPEC REQ-C-004): a toolbar carrying [text] must
+      not share a card with a separately heading-slotted <card-ui>
+      <header> — that pairing doubles the title row. As the header's
+      sole child, the toolbar's own [text]/[count] cluster IS the
+      card's title; there is no separate heading to collide with.
     - >-
       All four affordances (search, filter, sort, columns) default ON.
       Opt out individually via [no-search] / [no-filter] / [no-sort]
       / [no-columns]. The previous [searchable] / [filterable]
       attributes are deprecated — do NOT emit them.
     - >-
-      Three legitimate placements: ABOVE the <card-ui> containing the
-      table-ui; standing alone outside a card-ui parent with
-      [variant="card"] (wraps the toolbar in card-style chrome); or
-      INSIDE the card, in its own plain (non-bleed) <section> between
-      the card header and the bleed table section — the canonical
-      table-in-card shape (gh#1807) — title-less (no [text]) since the
-      card header already owns the title (see the title-collision rule
-      above).
+      Two legitimate in-card placements, chosen by whether the card
+      header needs content beyond the toolbar: ABOVE the <card-ui>
+      (sibling, typically wrapped with the table in a <col-ui>) when
+      the header carries its own slot="heading"/slot="action" content
+      alongside the toolbar; or AS <card-ui>'s <header> sole child —
+      the canonical in-card shape (gh#1807/#1884, ADR-0080) — when the
+      toolbar IS the header and no separate title/action row is
+      needed. A toolbar can also stand alone outside any card-ui
+      parent with [variant="card"], which wraps it in card-style
+      chrome. The previous plain (non-bleed) <section> placement
+      between the card header and the bleed table section — a
+      title-less toolbar leaving the title to a separately-slotted
+      header — is retired: no live demo or pattern documents it, and
+      the header-child shape supersedes it as the canonical in-card
+      composition.
     - >-
       Use slot="action" (or [slot="actions"]) for trailing primary
       buttons (Invite, Export, +New). Use [text] / [count] props for
@@ -343,13 +421,15 @@ a2ui:
       update the table.
     - >-
       Use [slot="scope"] for a leading scope/view switcher (an org's
-      teams, a saved view) rendered before [text]/[count]. Use
-      [range-start] / [range-end] / [range-total] together for a
-      "Showing X–Y of N" summary — it renders independently of, and
-      alongside, [text]/[count], never in place of them. Use [page-size]
-      + [page-size-options] for a rows-per-page select; it applies
-      directly to the bound table's [paginate] prop the same way
-      filter/sort/columns changes apply directly to the target.
+      teams, a saved view) rendered before [text]/[count]. By default, a
+      filled scope slot hides the [text]/[count] title cluster (they'd
+      otherwise repeat the same entity name) — set [title-always] to keep
+      both visible together. Use [range-start] / [range-end] /
+      [range-total] together for a "Showing X–Y of N" summary — it renders
+      independently of, and alongside, [text]/[count], never in place of
+      them. Use [page-size] + [page-size-options] for a rows-per-page
+      select; it applies directly to the bound table's [paginate] prop the
+      same way filter/sort/columns changes apply directly to the target.
     - >-
       Use [slot="actions-leading"] (gh#1649) for app-owned trigger
       buttons that must land BEFORE the page-size select — e.g. custom
@@ -373,6 +453,26 @@ a2ui:
       normal "Showing X-Y of N" text (ADR-0076, REQ-E). Only fires on an
       EXPLICIT range-total="0" — omitting range-* entirely (loading) never
       shows it.
+    - >-
+      gh#1877, ADR-0082 Amendment — cursor/hasMore server paging (no
+      server-reported row count) sets [range-total="?"] instead of a real
+      number: the summary reads "Showing 51–100" with no "of N" (needs only
+      [range-start]/[range-end] > 0 to render), resolving to the normal
+      finite summary once a real [range-total] arrives. Use [range-of] for
+      the separate "filtered-of-whole" shape (a filtered range-total plus a
+      secondary unfiltered-set total, e.g. "of 4 traversals (6 total)"),
+      and [range-noun] to stop hand-painting the per-slice noun ("of 80
+      users"). Same three attributes, same names, on table-footer-ui
+      (ADR-0082 §"same name on both companions").
+    - >-
+      Use [slot="summary"] (gh#1883) for a trailing aggregate/total datum
+      that belongs with the table but isn't pagination context — e.g.
+      batch-detail's line-items Subtotal:
+      `<span slot="summary">Subtotal <strong>$1,240.00</strong></span>`.
+      Renders after [slot="actions-leading"] and before the page-size
+      select / [slot="actions"]. Always visible — it is data, never
+      collapsed or hidden by the compaction stages that reduce
+      Filter/Sort/Columns/search or the range summary.
     - >-
       A plain <button-ui> slotted into [slot="actions-leading"] (e.g. the
       app-owned Filter/Columns triggers above) already collapses to
@@ -420,6 +520,20 @@ examples:
         {"id": "sec", "component": "Section", "bleed": true, "children": ["tbl"]},
         {"id": "tbl", "component": "Table", "id": "accounts", "sortable": true, "raw": true}
       ]
+  - name: table-toolbar-open-total
+    description: >-
+      gh#1877, ADR-0082 Amendment — cursor/hasMore server paging with no
+      known row count yet: [range-total="?"] renders "Showing 1–50
+      subscriptions" (via [range-noun]) with no "of N", resolving to the
+      normal finite summary once a real total arrives.
+    a2ui: >-
+      [
+        {"id": "root", "component": "Column", "gap": "3", "children": ["bar", "card"]},
+        {"id": "bar", "component": "TableToolbar", "for": "subs", "range-start": 1, "range-end": 50, "range-total": "?", "range-noun": "subscriptions"},
+        {"id": "card", "component": "Card", "children": ["sec"]},
+        {"id": "sec", "component": "Section", "bleed": true, "children": ["tbl"]},
+        {"id": "tbl", "component": "Table", "id": "subs", "raw": true}
+      ]
 keywords:
   - table-toolbar
   - data-grid

package/components/theme-provider/theme-provider.a2ui.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://adiaui.dev/a2ui/v0_9/components/ThemeProvider.json",
   "title": "ThemeProvider",
-  "description": "Foundation-providing wrapper — adopts the AdiaUI foundation (design tokens +\nresets + page-frame + every primitive's CSS) into the document from anywhere\nin the DOM, so a surface renders fully-styled WITHOUT a hand-wired\n<link rel=\"stylesheet\"> in <head>. Layout-transparent (display: contents): the\nelement owns no box; children lay out as if it weren't there.\n\nMechanism: it imports the constructable-stylesheet twin of web-components.min.css\n(byte-identical to the CDN bundle, emitted from the same build buffer) and\nadopts it once into document.adoptedStyleSheets, deduped — adoption fires at\nmodule load, before paint. Coexists with the render-blocking <link> path; both\ndeliver the same bytes. Use a <link> (-> the CDN web-components.min.css) for\nmulti-page / top-level surfaces (cacheable across navigations, zero flash); use\n<theme-provider> for SPA roots, embedded apps, and dynamic mounts where you do\nnot control <head> (e.g. <embed-shell>, an A2UI surface, a micro-frontend).\n\nTheming: the base foundation is OS light/dark via light-dark() tokens. Two opt-in\nattributes adopt their layer on demand — theme=\"ocean|forest|slate|…\" applies a\nnamed preset (adopts the themes layer; matches the [theme] hook) and\nscale=\"ui-sm|ui-md|ui-lg|content-sm|content-md|content-lg\" sets the sizing\nregister (adopts the matching register layer). Deprecated aliases \"verse\"\n(→ ui-sm) and \"prose\" (→ content-md) still map onto the legacy\n[verse]/[prose] attributes; removed at v1.0. Each layer is fetched only\nwhen its attribute is set, so a bare provider stays lean.\nOpt-in infra: NOT in the all-in-one @adia-ai/web-components barrel (it carries\nthe whole foundation); import @adia-ai/web-components/components/theme-provider\nexplicitly. Distinct from <frame-ui> (a layout skeleton, owns no CSS delivery)\nand the page shells (chrome over the same foundation).\n",
+  "description": "Foundation-providing wrapper — adopts the AdiaUI foundation (design tokens +\nresets + page-frame + every primitive's CSS) into the document from anywhere\nin the DOM, so a surface renders fully-styled WITHOUT a hand-wired\n<link rel=\"stylesheet\"> in <head>. Layout-transparent (display: contents): the\nelement owns no box; children lay out as if it weren't there.\n\nMechanism: it imports the constructable-stylesheet twin of web-components.min.css\n(byte-identical to the CDN bundle, emitted from the same build buffer) and\nadopts it once into document.adoptedStyleSheets, deduped — adoption fires at\nmodule load, before paint. Coexists with the render-blocking <link> path; both\ndeliver the same bytes. Use a <link> (-> the CDN web-components.min.css) for\nmulti-page / top-level surfaces (cacheable across navigations, zero flash); use\n<theme-provider> for SPA roots, embedded apps, and dynamic mounts where you do\nnot control <head> (e.g. <embed-shell>, an A2UI surface, a micro-frontend).\n\nTheming: the base foundation is OS light/dark via light-dark() tokens. Two opt-in\nattributes adopt their layer on demand — theme=\"ocean|forest|slate|…\" applies a\nnamed preset (adopts the themes layer; matches the [theme] hook) and\nscale=\"ui-sm|ui-md|ui-lg|content-sm|content-md|content-lg\" sets the sizing\nregister (adopts the matching register layer). Each layer is fetched only\nwhen its attribute is set, so a bare provider stays lean.\nOpt-in infra: NOT in the all-in-one @adia-ai/web-components barrel (it carries\nthe whole foundation); import @adia-ai/web-components/components/theme-provider\nexplicitly. Distinct from <frame-ui> (a layout skeleton, owns no CSS delivery)\nand the page shells (chrome over the same foundation).\n",
   "type": "object",
   "allOf": [
     {
@@ -22,7 +22,7 @@
       "const": "ThemeProvider"
     },
     "scale": {
-      "description": "Sizing register for the subtree — one of the six [scale] tiers: ui-sm (dense product UI), ui-md (base), ui-lg (touch/presentation), content-sm (compact article), content-md (long-form), content-lg (hero/marketing). Adopts the scale layer on demand; the reflected attribute is the [scale=\"…\"] CSS hook. Deprecated aliases \"verse\" (→ ui-sm) and \"prose\" (→ content-md) still map onto the legacy [verse]/[prose] attributes; removed at v1.0.",
+      "description": "Sizing register for the subtree — one of the six [scale] tiers: ui-sm (dense product UI), ui-md (base), ui-lg (touch/presentation), content-sm (compact article), content-md (long-form), content-lg (hero/marketing). Adopts the scale layer on demand; the reflected attribute is the [scale=\"…\"] CSS hook.",
       "type": "string",
       "enum": [
         "ui-sm",
@@ -30,9 +30,7 @@
         "ui-lg",
         "content-sm",
         "content-md",
-        "content-lg",
-        "verse",
-        "prose"
+        "content-lg"
       ],
       "default": ""
     }

package/components/theme-provider/theme-provider.class.js

@@ -28,12 +28,11 @@
  *
  * Scope (v1): the provider supplies the FOUNDATION only — design tokens, resets,
  * page-frame, and every primitive's CSS. OS light/dark resolves automatically
- * (the tokens are `light-dark()`-based). Named themes (`[theme]`) and the
- * `verse` / `prose` context registers live in OPT-IN layers (themes.css /
- * verse.css / prose.css) that are NOT in the foundation bundle, so setting
- * `theme` / `verse` on the wrapper does nothing until those layers are also
- * adopted — a planned `theme=` / `verse` provider option (the token-root selector
- * is pre-wired for it; see .brain/notes/theme-provider-design-2026-06-04.md).
+ * (the tokens are `light-dark()`-based). Named themes (`[theme]`) live in an
+ * OPT-IN layer (themes.css) that is NOT in the foundation bundle, so setting
+ * `theme` on the wrapper does nothing until that layer is also adopted — a
+ * planned `theme=` provider option (the token-root selector is pre-wired for
+ * it; see .brain/notes/theme-provider-design-2026-06-04.md).
  *
  * Deliberately NOT in the all-in-one `@adia-ai/web-components` barrel — it's
  * opt-in infra (it carries the whole foundation). Import it explicitly:
@@ -58,19 +57,17 @@ function provideFoundation() {
   }
 }
 
-// Opt-in context registers — themes (named `[theme]` presets), and the `verse` /
-// `prose` `scale` registers. Each is its own constructable-sheet twin (built by
+// Opt-in context registers — themes (named `[theme]` presets) and the `scale`
+// register. Each is its own constructable-sheet twin (built by
 // scripts/build/bundle-css.mjs, byte-identical to its .min.css). Adopted on demand
 // the first time a provider needs one, deduped by sheet identity. Dynamic-imported
 // (static paths, so bundlers can code-split) so the element stays lean — a provider
 // that does no theming never pulls these in.
-const TWIN_LOADED = { themes: false, verse: false, prose: false, scale: false };
+const TWIN_LOADED = { themes: false, scale: false };
 function loadTwin(name) {
   switch (name) {
     case 'themes': return import('../../dist/themes.sheet.js');
     case 'scale': return import('../../dist/scale.sheet.js');
-    case 'verse': return import('../../dist/verse.sheet.js');
-    case 'prose': return import('../../dist/prose.sheet.js');
     default: return null;
   }
 }
@@ -100,8 +97,6 @@ export class UIThemeProvider extends UIElement {
     // Sizing register — one of the six [scale] tiers (ui-sm | ui-md | ui-lg |
     // content-sm | content-md | content-lg). Reflected, so the attribute IS the
     // `[scale="…"]` CSS hook in scale.css (the `theme` prop's mechanism).
-    // DEPRECATED aliases: "verse" (→ ui-sm) and "prose" (→ content-md) still
-    // map onto the legacy [verse]/[prose] attributes; removed at v1.0.
     scale: { type: String, reflect: true },
   };
   static template = () => null;
@@ -128,15 +123,7 @@ export class UIThemeProvider extends UIElement {
     if (this.theme) ensureTwin('themes');
 
     const scale = this.scale;
-    this.toggleAttribute('verse', scale === 'verse');
-    this.toggleAttribute('prose', scale === 'prose');
-    if (scale === 'verse' || scale === 'prose') {
-      // Legacy register aliases — the reflected scale="verse|prose" attribute
-      // matches no scale.css tier selector, so only the toggled [verse]/[prose]
-      // attribute has CSS effect. Removed at v1.0.
-      warnDeprecatedScaleAlias(scale);
-      ensureTwin(scale);
-    } else if (SCALE_TIERS.has(scale)) {
+    if (SCALE_TIERS.has(scale)) {
       // Tier names match [scale="…"] in scale.css directly via reflection.
       ensureTwin('scale');
     }
@@ -144,11 +131,3 @@ export class UIThemeProvider extends UIElement {
 }
 
 const SCALE_TIERS = new Set(['ui-sm', 'ui-md', 'ui-lg', 'content-sm', 'content-md', 'content-lg']);
-
-const warnedAliases = new Set();
-function warnDeprecatedScaleAlias(alias) {
-  if (warnedAliases.has(alias)) return;
-  warnedAliases.add(alias);
-  const tier = alias === 'verse' ? 'ui-sm' : 'content-md';
-  console.warn(`[theme-provider] scale="${alias}" is deprecated — use scale="${tier}" (removed at v1.0).`);
-}

package/components/theme-provider/theme-provider.d.ts

@@ -18,9 +18,7 @@ Theming: the base foundation is OS light/dark via light-dark() tokens. Two opt-i
 attributes adopt their layer on demand — theme="ocean|forest|slate|…" applies a
 named preset (adopts the themes layer; matches the [theme] hook) and
 scale="ui-sm|ui-md|ui-lg|content-sm|content-md|content-lg" sets the sizing
-register (adopts the matching register layer). Deprecated aliases "verse"
-(→ ui-sm) and "prose" (→ content-md) still map onto the legacy
-[verse]/[prose] attributes; removed at v1.0. Each layer is fetched only
+register (adopts the matching register layer). Each layer is fetched only
 when its attribute is set, so a bare provider stays lean.
 Opt-in infra: NOT in the all-in-one @adia-ai/web-components barrel (it carries
 the whole foundation); import @adia-ai/web-components/components/theme-provider
@@ -42,6 +40,6 @@ import { UIElement } from '../../core/element.js';
 export class UIThemeProvider extends UIElement {
   /** Named theme preset for the wrapped subtree (default, ocean, forest, sunset, lavender, rose, slate, midnight). Adopts the themes layer on demand + matches the [theme="…"] hook. */
   theme: string;
-  /** Sizing register for the subtree — one of the six [scale] tiers: ui-sm (dense product UI), ui-md (base), ui-lg (touch/presentation), content-sm (compact article), content-md (long-form), content-lg (hero/marketing). Adopts the scale layer on demand; the reflected attribute is the [scale="…"] CSS hook. Deprecated aliases "verse" (→ ui-sm) and "prose" (→ content-md) still map onto the legacy [verse]/[prose] attributes; removed at v1.0. */
-  scale: 'ui-sm' | 'ui-md' | 'ui-lg' | 'content-sm' | 'content-md' | 'content-lg' | 'verse' | 'prose';
+  /** Sizing register for the subtree — one of the six [scale] tiers: ui-sm (dense product UI), ui-md (base), ui-lg (touch/presentation), content-sm (compact article), content-md (long-form), content-lg (hero/marketing). Adopts the scale layer on demand; the reflected attribute is the [scale="…"] CSS hook. */
+  scale: 'ui-sm' | 'ui-md' | 'ui-lg' | 'content-sm' | 'content-md' | 'content-lg';
 }

package/components/theme-provider/theme-provider.yaml

@@ -26,9 +26,7 @@ description: |
   attributes adopt their layer on demand — theme="ocean|forest|slate|…" applies a
   named preset (adopts the themes layer; matches the [theme] hook) and
   scale="ui-sm|ui-md|ui-lg|content-sm|content-md|content-lg" sets the sizing
-  register (adopts the matching register layer). Deprecated aliases "verse"
-  (→ ui-sm) and "prose" (→ content-md) still map onto the legacy
-  [verse]/[prose] attributes; removed at v1.0. Each layer is fetched only
+  register (adopts the matching register layer). Each layer is fetched only
   when its attribute is set, so a bare provider stays lean.
   Opt-in infra: NOT in the all-in-one @adia-ai/web-components barrel (it carries
   the whole foundation); import @adia-ai/web-components/components/theme-provider
@@ -41,7 +39,7 @@ props:
     default: ""
     reflect: true
   scale:
-    description: 'Sizing register for the subtree — one of the six [scale] tiers: ui-sm (dense product UI), ui-md (base), ui-lg (touch/presentation), content-sm (compact article), content-md (long-form), content-lg (hero/marketing). Adopts the scale layer on demand; the reflected attribute is the [scale="…"] CSS hook. Deprecated aliases "verse" (→ ui-sm) and "prose" (→ content-md) still map onto the legacy [verse]/[prose] attributes; removed at v1.0.'
+    description: 'Sizing register for the subtree — one of the six [scale] tiers: ui-sm (dense product UI), ui-md (base), ui-lg (touch/presentation), content-sm (compact article), content-md (long-form), content-lg (hero/marketing). Adopts the scale layer on demand; the reflected attribute is the [scale="…"] CSS hook.'
     type: string
     default: ""
     enum:
@@ -51,8 +49,6 @@ props:
       - content-sm
       - content-md
       - content-lg
-      - verse
-      - prose
     reflect: true
 events: {}
 slots: {}
@@ -67,8 +63,8 @@ a2ui:
       reason: 'Adopts the foundation bundle into the document from anywhere in the tree (document.adoptedStyleSheets).'
     - rule: 'For multi-page / top-level pages, prefer a render-blocking <link rel="stylesheet" href=".../web-components.min.css"> in <head> instead — cacheable across navigations, styled on the first frame. <theme-provider> and the link deliver byte-identical CSS, so they coexist.'
       reason: 'Link for multi-page (no flash); provider for SPA/embedded (no head access).'
-    - rule: 'Theme the wrapped subtree with theme="ocean" (a named preset) and/or scale="verse|prose" (compact / long-form register) — the provider adopts the matching opt-in layer on demand. The base foundation is OS light/dark automatically. Keep <theme-provider> at/near the mount root — display:contents means an ancestor "> " child selector will not reach its children.'
-      reason: 'theme/scale each fetch + adopt their layer (themes.css / verse.css / prose.css) on demand; display:contents preserves custom-property inheritance but not child-combinator reach (Light DOM, ADR-0033).'
+    - rule: 'Theme the wrapped subtree with theme="ocean" (a named preset) and/or scale="content-md" (a sizing register tier) — the provider adopts the matching opt-in layer on demand. The base foundation is OS light/dark automatically. Keep <theme-provider> at/near the mount root — display:contents means an ancestor "> " child selector will not reach its children.'
+      reason: 'theme/scale each fetch + adopt their layer (themes.css / scale.css) on demand; display:contents preserves custom-property inheritance but not child-combinator reach (Light DOM, ADR-0033).'
 anti_patterns: []
 examples:
   - name: spa-root

package/core/element.js

@@ -85,9 +85,22 @@ const NOOP_INTERNALS = Object.freeze({
 });
 
 function reflect(el, a, v, t) {
-  t === Boolean
-    ? v ? el.setAttribute(a, '') : el.removeAttribute(a)
-    : v == null ? el.removeAttribute(a) : el.setAttribute(a, String(v));
+  if (t === Boolean) {
+    v ? el.setAttribute(a, '') : el.removeAttribute(a);
+    return;
+  }
+  // gh#1895 — a Number-typed reflected prop set from an unparseable sentinel
+  // attribute (e.g. `range-total="?"`, ADR-0082 Amendment's open/unproven-
+  // total grammar) coerces to NaN. Writing `String(NaN)` back would stomp
+  // the author's sentinel with the literal string "NaN" on the very next
+  // render, so a non-finite Number value is deliberately left unreflected —
+  // the attribute keeps whatever the author wrote (or stays absent, for a
+  // NaN assigned straight from JS with no attribute yet). This mirrors how
+  // `null` already skips straight to removeAttribute below instead of
+  // stringifying: NaN gets its own no-write branch rather than one more
+  // Number.isFinite check duplicated at every "?"-sentinel call site.
+  if (t === Number && v != null && !Number.isFinite(v)) return;
+  v == null ? el.removeAttribute(a) : el.setAttribute(a, String(v));
 }
 
 const parseAttr = (v, t) =>