@adia-ai/web-components 0.8.46 → 0.8.48

package/components/table-toolbar/table-toolbar.css

@@ -284,6 +284,21 @@
     flex: 0 0 auto;
   }
 
+  /* See [data-page-size]'s own comment below — same --select-min-width
+     floor, same fix, but targeted at the select-ui DESCENDANT directly
+     rather than set as an inheriting custom property on the [data-scope]
+     wrapper: select-ui's own `:where(:scope) { --select-min-width: 20ch }`
+     (select.css) directly assigns the property on the select-ui element
+     itself — a direct assignment always wins over an inherited value
+     regardless of the assigning rule's (here, zero) specificity, so a
+     value merely inherited from an ancestor wrapper never actually
+     reaches it. Matching the select-ui element directly puts this
+     override in the same competition as that rule, where normal
+     specificity comparison (0,2,0) vs (0,0,0) applies and this wins. */
+  [data-scope] select-ui {
+    --select-min-width: 0;
+  }
+
   [data-scope]:empty { display: none; }
 
   /* ═══════ Title cluster ═══════ */
@@ -305,6 +320,25 @@
 
   [data-toolbar-count-badge][hidden] { display: none; }
 
+  /* Scope reconciliation — a filled [slot="scope"] already names the
+     entity being listed (a select/menu whose own displayed value IS the
+     label, e.g. "All Accounts (3)"), so the separate [text]/[count] title
+     cluster next to it says the same thing twice ("All accounts" +
+     "Accounts 3"). CSS-only, not #updateTitle() (JS never even sees
+     [text]/[count] are redundant here — [count] still falls back to the
+     bound table's row length regardless, so a JS hide would need a new
+     prop; this reads what's already in the DOM, same `:has()` idiom the
+     [data-summary]/[data-page-size] reconciliation above already uses).
+     A consumer wanting BOTH visible can still override with normal CSS
+     specificity — this isn't a hard mode switch, just the default.
+     [title-always] (gh#1879) is the declared opt-out for that same case:
+     a consumer wanting BOTH the scope select AND the explicit text/count
+     title visible together sets the attribute instead of reaching for an
+     app-side CSS override. */
+  :scope:not([title-always]):has([data-scope]:not(:empty)) [data-title] {
+    display: none;
+  }
+
   /* ═══════ Range summary ═══════ (gh#1615 — "Showing X–Y of N", independent of [data-title]) */
 
   [data-summary] {
@@ -371,7 +405,17 @@
      --table-toolbar-bp-overflow's own default (same duplication +
      source-assertion discipline as the search-tight/icon-only boundaries
      above). */
-  [data-toolbar-overflow] { display: none; }
+  /* BUG (found live, verified in a real browser — a fresh table-toolbar-ui
+     at ANY stage, including "full", rendered Filter/Sort/Columns AND the
+     "More" trigger simultaneously): menu-ui's own base rule (menu.css,
+     `:scope { display: flex; }`) is the same (0,1,0) specificity as a bare
+     `[data-toolbar-overflow]` selector — a cascade TIE this file's source
+     order loses (menu.css wins), so this default-hide rule never actually
+     applied. The `:scope … [data-toolbar-overflow][hidden]` override below
+     already carries the `:scope` prefix for exactly this reason (its own
+     comment: "must match or exceed the (0,3,0) specificity … to win the
+     tie") — this rule needed the same prefix and never got it. */
+  :scope [data-toolbar-overflow] { display: none; }
 
   @container table-toolbar (max-width: 26rem) {
     :scope:is(:not([stage]), [stage=""]) [data-toolbar-btn] {
@@ -405,19 +449,62 @@
      conflicting author rule. */
   :scope [data-toolbar-overflow][hidden] { display: none; }
 
+  /* menu-ui's own popover carries a hardcoded `min-width: 10rem` (menu.css
+     — a LITERAL, not even the `--menu-popover-min-width` token declared
+     next to it: the popover is promoted to the top layer via the Popover
+     API but stays a real light-DOM child of <menu-ui>, per menu.css's own
+     comment "the top-layer element can't inherit the scoped token", so
+     that rule hardcodes the value instead of reading the custom property).
+     Same class of bug as --input-min-width/--select-min-width above: sized
+     for a generic dropdown menu of arbitrary action items, not this
+     specific "More" trigger's three short labels (Filter/Sort/Columns),
+     each already narrower than 10rem on its own. Scoped to JUST this
+     menu-ui instance (`[data-toolbar-overflow]`) — the [data-menu-popover]
+     it targets is menu-ui's own internal implementation selector, not
+     table-toolbar's; overriding the LITERAL selector directly here rather
+     than touching menu.css keeps every other menu-ui consumer's own
+     10rem floor (a reasonable default for a menu of arbitrary items)
+     untouched. */
+  :scope [data-toolbar-overflow] [data-menu-popover] {
+    min-width: 0;
+  }
+
   /* ═══════ Search ═══════ */
 
   [data-search] {
     flex: 1 1 var(--table-toolbar-search-min);
     /* gh#1076 — never collapse to 0: floor at a usable width and let the
-       flex-wrap above move it to its own row when the container is tight. */
-    min-width: min(10rem, 100%);
+       flex-wrap above move it to its own row when the container is tight.
+       BUG (found live, 2026-08-22): this used to be a hardcoded
+       `min(10rem, 100%)`, independent of `--table-toolbar-search-min` —
+       at the search-tight/icon-only/overflow stages that token gets
+       reassigned to `--table-toolbar-search-tight-min` (9rem default),
+       but the hardcoded 10rem floor here still won, so the tight tier's
+       own declared 9rem target could never actually be reached. Deriving
+       the floor from the SAME token as the flex-basis keeps them in sync
+       at every stage instead of drifting against each other. */
+    min-width: min(var(--table-toolbar-search-min), 100%);
     max-width: var(--table-toolbar-search-max);
     margin-inline-start: auto;
   }
 
   [data-search][hidden] { display: none; }
 
+  /* input-ui's own --input-min-width default (20ch — input.css) is sized
+     for a BARE, standalone field where the component has no other context
+     to size against. Inside [data-search] that's a second, independent
+     floor competing with the one above — at the tight/icon-only/overflow
+     stages input-ui's 20ch (~164px) is WIDER than
+     --table-toolbar-search-tight-min (9rem/144px), so it silently won
+     regardless of what [data-search]'s own min-width — even after the fix
+     above — asked for. table-toolbar-ui owns the search field's sizing
+     budget end-to-end (it's the one deciding how much room is left after
+     the title/controls/page-size clusters); input-ui's independent
+     opinion has nothing to add here and only fights the outer token. */
+  [data-search] input-ui {
+    --input-min-width: 0;
+  }
+
   /* ═══════ Actions-leading slot ═══════ (gh#1649 — app-owned triggers, e.g.
      custom Filter/Columns buttons, that land BEFORE the page-size select)
      Carries the SAME margin-inline-start:auto as [data-search]/[data-page-size]
@@ -449,9 +536,23 @@
      is safe — only the first one with unclaimed free space to its left
      actually receives it. */
 
+  /* select-ui's own --select-min-width default (20ch — select.css,
+     gh#1633, the SAME UA-baseline floor input.css's --input-min-width
+     already documents for input-ui) is sized for a bare, standalone
+     select. Found live (root-caused alongside the earlier search-field
+     min-width fix, same shape): with no override here, [data-page-size]
+     and [data-scope] select-ui both floor at ~151px regardless of how
+     short their actual content is ("25 / page", "All Accounts (3)") —
+     visible dead space inside the trigger. The filter/sort/columns
+     popover's OWN per-column selects already avoid this (they share the
+     `[data-filter-input]` marker with the text-input case, and
+     `[data-toolbar-popover] [data-filter-input] { min-width: 0; }`
+     already resets it there) — this is the same fix for the two
+     main-row selects that marker doesn't reach. */
   [data-page-size] {
     flex: 0 0 auto;
     margin-inline-start: auto;
+    --select-min-width: 0;
   }
 
   [data-page-size][hidden] { display: none; }

package/components/table-toolbar/table-toolbar.d.ts

@@ -46,14 +46,22 @@ export class UITableToolbar extends UIElement {
   placeholder: string;
   /** 1-indexed last row number of the current page, for the range summary (e.g. `25` in "Showing 1–25 of 320"). See rangeStart. */
   rangeEnd: number;
+  /** 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"). */
+  rangeNoun: string;
+  /** 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"). */
+  rangeOf: number;
   /** 1-indexed first row number of the current page, for the "Showing X–Y of N" range summary (e.g. `1` in "Showing 1–25 of 320"). Renders alongside — never in place of — [text]/[count]; the range summary is its own cluster, independent of the title cluster. All three of rangeStart/rangeEnd/rangeTotal must be set (> 0) for the summary to render; omit all three (the default) to opt out entirely. */
   rangeStart: number;
-  /** Total row count across all pages, for the range summary (e.g. `320` 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. */
-  rangeTotal: number;
+  /** Total row count across all pages, for the range summary (e.g. `320` 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. 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"). */
+  rangeTotal: number | string;
+  /** Toolbar scale, via sizing.css's universal [size="sm|md|lg"] ambient tokens. Not table-toolbar-specific chrome — the same attribute that scales any component. Set it once on the toolbar instead of on each slotted scope/actions-leading/actions control individually; anything slotted with no [size] of its own inherits the ambient value. Default (empty) = md. */
+  size: 'sm' | 'md' | 'lg';
   /** Explicit compaction-stage override (ADR-0076). Unset (the default, empty string) means auto-snap: the toolbar's own inline-size container query picks the nearest stage from its live width against the three --table-toolbar-bp-* breakpoints, snapping discretely, never interpolating. Setting stage explicitly pins that stage's rendering regardless of the container's actual width — overriding the container query, mirroring chart-ui's ratio override shape. Primary use: visual-eval fixtures that need a deterministic stage without resizing a real container, and a consumer embedding the toolbar inside a known-narrow panel who wants to skip auto-detection entirely. All four stages' CSS is now live (ADR-0076): search-tight steps the search field down (step 2); icon-only drops control labels and compacts/hides the range summary (steps 3+4); overflow collapses Filter/Sort/Columns into one "More" trigger routed through the same menu-ui/menu-item-ui pattern used elsewhere in the corpus (step 5). The resolved stage — the pin if set, otherwise the live width classification — also reflects onto the host as `data-stage-resolved` (step 7, informational only, mirrors chart-ui's `data-ratio-resolved` convention — never drives table-toolbar's own rendering, which stays 100% CSS-driven). */
   stage: '' | 'full' | 'search-tight' | 'icon-only' | 'overflow';
   /** Title text shown on the left. */
   text: string;
+  /** 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). */
+  titleAlways: boolean;
   /** Toolbar visual variant. `default` renders bare on parent surface; `card` adds the same chrome as a card-ui header. */
   variant: 'default' | 'card';
 

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

@@ -3,56 +3,58 @@
 ## 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>
 ```
 
 ## Rendered demos
 
 ```html
-<col-ui gap="0">
-  <table-toolbar-ui for="demo-table" text="All employees" count="32" placeholder="Search employees…"></table-toolbar-ui>
-  <card-ui>
-    <section bleed>
-      <table-ui id="demo-table" sortable raw>
-        <table>
-          <thead>
-            <tr>
-              <th>Name</th>
-              <th>Role</th>
-              <th>Status</th>
-            </tr>
-          </thead>
-          <tbody>
-            <tr>
-              <td>Maya Chen</td>
-              <td>Designer</td>
-              <td>
-                <tag-ui variant="success">Active</tag-ui>
-              </td>
-            </tr>
-            <tr>
-              <td>Alex Park</td>
-              <td>Engineer</td>
-              <td>
-                <tag-ui variant="success">Active</tag-ui>
-              </td>
-            </tr>
-            <tr>
-              <td>Jordan Lee</td>
-              <td>Product</td>
-              <td>
-                <tag-ui variant="warning">Away</tag-ui>
-              </td>
-            </tr>
-          </tbody>
-        </table>
-      </table-ui>
-    </section>
-  </card-ui>
-</col-ui>
+<card-ui>
+  <header>
+    <table-toolbar-ui for="demo-table" text="All employees" count="32" placeholder="Search employees…"></table-toolbar-ui>
+  </header>
+  <section bleed>
+    <table-ui id="demo-table" sortable raw>
+      <table>
+        <thead>
+          <tr>
+            <th>Name</th>
+            <th>Role</th>
+            <th>Status</th>
+          </tr>
+        </thead>
+        <tbody>
+          <tr>
+            <td>Maya Chen</td>
+            <td>Designer</td>
+            <td>
+              <tag-ui variant="success">Active</tag-ui>
+            </td>
+          </tr>
+          <tr>
+            <td>Alex Park</td>
+            <td>Engineer</td>
+            <td>
+              <tag-ui variant="success">Active</tag-ui>
+            </td>
+          </tr>
+          <tr>
+            <td>Jordan Lee</td>
+            <td>Product</td>
+            <td>
+              <tag-ui variant="warning">Away</tag-ui>
+            </td>
+          </tr>
+        </tbody>
+      </table>
+    </table-ui>
+  </section>
+</card-ui>
 ```

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

@@ -40,6 +40,20 @@ props:
     type: string
     default: ""
     reflect: true
+  size:
+    description: >-
+      Toolbar scale, via sizing.css's universal [size="sm|md|lg"] ambient
+      tokens. Not table-toolbar-specific chrome — the same attribute that
+      scales any component. Set it once on the toolbar instead of on each
+      slotted scope/actions-leading/actions control individually; anything
+      slotted with no [size] of its own inherits the ambient value.
+      Default (empty) = md.
+    type: string
+    default: ""
+    enum:
+    - sm
+    - md
+    - lg
   text:
     description: Title text shown on the left.
     type: string
@@ -74,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
@@ -176,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
@@ -329,13 +390,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
@@ -359,6 +422,17 @@ 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").
     - >-
       A plain <button-ui> slotted into [slot="actions-leading"] (e.g. the
       app-owned Filter/Columns triggers above) already collapses to
@@ -406,6 +480,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/core/anchor.js

@@ -122,7 +122,27 @@ function anchorNative(anchor, popover, { placement, gap, matchWidth }) {
   popover.style.left = '';
 
   return () => {
-    anchor.style.anchorName = prevAnchorName;
+    // Ownership-guarded restore (bug, found live): a trigger element that
+    // is ITSELF a popover's own `[slot="trigger"]` can become the anchor
+    // for a SECOND, nested popover opened from inside the first (menu-ui's
+    // dropdown item dispatching `action`, which table-toolbar-ui's overflow
+    // "More" trigger handles by re-anchoring a filter/sort/columns panel to
+    // that SAME element). Anchor-name assignment here is a blind overwrite,
+    // never a set/append — so whichever `anchorPopover()` call's cleanup
+    // runs LAST always wins, even when it's cleaning up a DIFFERENT,
+    // already-superseded anchor-name than the one currently on the element.
+    // menu-ui's own close (`render()`'s reactive `#hide()`, scheduled async
+    // — reordering the synchronous call site doesn't change when this
+    // runs) fires after the nested popover's `anchorPopover()` has already
+    // claimed the trigger, and unconditionally restoring `prevAnchorName`
+    // clobbered that fresh claim back to empty — the nested popover's own
+    // `position-anchor` was left pointing at a name resolving to nothing,
+    // rendering unpositioned at the viewport origin instead of near its
+    // trigger. Only restore when this cleanup's OWN name is still the
+    // current value — i.e., nobody has claimed the anchor since; otherwise
+    // leave it alone, since undoing someone else's still-active claim is
+    // never correct regardless of call order.
+    if (anchor.style.anchorName === name) anchor.style.anchorName = prevAnchorName;
     for (const [k, v] of Object.entries(prevStyles)) popover.style[k] = v;
   };
 }

package/custom-elements.json

@@ -2089,7 +2089,7 @@
               "type": {
                 "text": "string"
               },
-              "description": "Chart 2.0 aspect-ratio bucket (ADR-0074). Unset (default) auto-snaps to the nearest of the three studied ratios by comparing the chart's own live box aspect against two midpoint boundaries (5:4 between 3:2/1:1, 4:5 between 1:1/2:3) — never interpolated; the resolved bucket reflects onto the host as `data-ratio-resolved`. Setting `ratio` explicitly pins that bucket regardless of the box's actual aspect, overriding the auto-snap. Orthogonal to `size` (overall scale) and `type`/`color` (ADR-0064's family axis) — this attribute lands the grammar + snap plumbing only; per-type studied renderings per bucket are later waves (gh#1624 plan steps 2-4)."
+              "description": "Chart 2.0 aspect-ratio bucket (ADR-0074). Unset (default) auto-snaps to the nearest of the three studied ratios by comparing the chart's own live box aspect against two midpoint boundaries (5:4 between 3:2/1:1, 4:5 between 1:1/2:3) — never interpolated; the resolved bucket reflects onto the host as `data-ratio-resolved`. Setting `ratio` explicitly pins that bucket regardless of the box's actual aspect, overriding the auto-snap. Orthogonal to `size` (overall scale) and `type`/`color` (ADR-0064's family axis) — per-type studied renderings per bucket shipped across Waves A-C (gh#1624 plan steps 2-4: radial-bar/gauge/segments/stacked-bar/grouped-bar/multi-line, funnel/treemap/sankey/composed) — all 18 types have dedicated per-ratio render paths."
             },
             {
               "name": "labels",
@@ -9965,11 +9965,26 @@
             },
             {
               "name": "range-total",
+              "type": {
+                "text": "[number, string]"
+              },
+              "default": "0",
+              "description": "Total ROWS across all pages. Absent (the default) means \"not yet known\" (loading) — never \"zero\"; both the range label and the pager stay hidden until this is set. Explicit range-total=\"0\" is the confirmed-empty state (pager hidden; the `empty` slot renders in the range label's position when supplied). Named identically to table-toolbar-ui's [range-total] and table-ui's own [range-total] (gh#1754, ADR-0082) and deliberately NOT `total` (pagination-ui's `total` is total PAGES — the ADR-0063 B5 collision rule). 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 range label renders \"Showing X–Y\" with no \"of N\", and the pager stays in has-more mode (next enabled) rather than hiding — distinct from both \"loading\" (attribute absent) and \"confirmed empty\" (range-total=\"0\"). Resolves to the normal finite behavior the moment a real number replaces the \"?\". When this attribute is unset, the footer derives it from the resolved target via a two-branch ladder (REQ-W-006, amended 0.2.0/ADR-0082): (1) the target's own [range-total] attribute, when present — the table-authoritative SERVER mode (gh#1754 Shape 1's second lawful composition; the target's own \"?\" carries through identically); the identity rule: the footer's range-total derives from the table's range-total, never the table's filteredCount, and this branch wins even when the target's [paginate] is also > 0; (2) otherwise, when the target has [paginate] > 0, CLIENT mode: the target's filtered row count (search + column filters applied, before pagination). Refreshes on the target's `page` / `filter-change` / `sort` events in either branch. Widened named staleness edge: a programmatic `.data` swap on the target — or a `range-total` update on the target without an accompanying page move — emits no event; either re-set this footer's own attributes after such a change, or accept staleness until the target's next event."
+            },
+            {
+              "name": "range-of",
               "type": {
                 "text": "number"
               },
               "default": "0",
-              "description": "Total ROWS across all pages. Absent (the default) means \"not yet known\" (loading) — never \"zero\"; both the range label and the pager stay hidden until this is set. Explicit range-total=\"0\" is the confirmed-empty state (pager hidden; the `empty` slot renders in the range label's position when supplied). Named identically to table-toolbar-ui's [range-total] and table-ui's own [range-total] (gh#1754, ADR-0082) and deliberately NOT `total` (pagination-ui's `total` is total PAGES — the ADR-0063 B5 collision rule). When this attribute is unset, the footer derives it from the resolved target via a two-branch ladder (REQ-W-006, amended 0.2.0/ADR-0082): (1) the target's own [range-total] attribute, when present — the table-authoritative SERVER mode (gh#1754 Shape 1's second lawful composition); the identity rule: the footer's range-total derives from the table's range-total, never the table's filteredCount, and this branch wins even when the target's [paginate] is also > 0; (2) otherwise, when the target has [paginate] > 0, CLIENT mode: the target's filtered row count (search + column filters applied, before pagination). Refreshes on the target's `page` / `filter-change` / `sort` events in either branch. Widened named staleness edge: a programmatic `.data` swap on the target — or a `range-total` update on the target without an accompanying page move — emits no event; either re-set this footer's own attributes after such a change, or accept staleness until the target's next event."
+              "description": "gh#1877, ADR-0082 Amendment — secondary whole-set total for the \"filtered-of-whole\" shape: a client-side facet narrows [range-total] (a filtered count) while range-of names the unfiltered set size, e.g. \"Showing 1–4 of 4 traversals (6 total)\". Appends \"(of <range-of> total)\" onto the normal finite range text; unset (the default) changes nothing. Never applies while [range-total] is absent (loading) or \"?\" (open/unproven) — there's no finite range text to append onto yet. Named identically on table-toolbar-ui (ADR-0082 §\"same name on both companions\")."
+            },
+            {
+              "name": "range-noun",
+              "type": {
+                "text": "string"
+              },
+              "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 text and the open/unproven-total text (\"Showing 51–100 users\" with no \"of N\"). Unset (the default) changes nothing. Named identically on table-toolbar-ui (ADR-0082 §\"same name on both companions\")."
             },
             {
               "name": "siblings",
@@ -10044,6 +10059,13 @@
               },
               "description": "id-ref of the table-ui to control. Falls back to the first sibling table-ui within the same parent when omitted."
             },
+            {
+              "name": "size",
+              "type": {
+                "text": "string"
+              },
+              "description": "Toolbar scale, via sizing.css's universal [size=\"sm|md|lg\"] ambient tokens. Not table-toolbar-specific chrome — the same attribute that scales any component. Set it once on the toolbar instead of on each slotted scope/actions-leading/actions control individually; anything slotted with no [size] of its own inherits the ambient value. Default (empty) = md."
+            },
             {
               "name": "text",
               "type": {
@@ -10076,11 +10098,26 @@
             },
             {
               "name": "range-total",
+              "type": {
+                "text": "[number, string]"
+              },
+              "default": "0",
+              "description": "Total row count across all pages, for the range summary (e.g. `320` 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. 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\")."
+            },
+            {
+              "name": "range-of",
               "type": {
                 "text": "number"
               },
               "default": "0",
-              "description": "Total row count across all pages, for the range summary (e.g. `320` 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."
+              "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\")."
+            },
+            {
+              "name": "range-noun",
+              "type": {
+                "text": "string"
+              },
+              "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\")."
             },
             {
               "name": "page-size",
@@ -10145,6 +10182,14 @@
               "default": "false",
               "description": "Suppress all four native controls/search at once (filter, sort, columns, search) as additive sugar over noFilter/noSort/noColumns/ noSearch (ADR-0076, ADIA2-9123). Precedence is pure, absolute OR — while set, all four stay off regardless of any individual no-* attribute's own value, with no partial re-enable path; to re-enable one control, remove chrome-only entirely and set the other three no-* attributes explicitly instead. The four granular attributes are not deprecated or removed — they remain the independently-addressable shipped API; chrome-only never replaces them, it's a convenience preset on top."
             },
+            {
+              "name": "title-always",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "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)."
+            },
             {
               "name": "placeholder",
               "type": {
@@ -10330,10 +10375,10 @@
             {
               "name": "range-total",
               "type": {
-                "text": "number"
+                "text": "[number, string]"
               },
               "default": "0",
-              "description": "Total row count across ALL server pages (gh#1754, ADR-0082) — the table-authoritative server-mode data contract. Presence-gated: the attribute's PRESENCE, not its value, is the mode switch (checked via hasAttribute, never the coerced value alone — the same discipline table-footer-ui's own [range-total] ships). Absent (the default) means client mode: today's behavior exactly, [paginate] slices `.data` as always. Present with [paginate] > 0 means server mode: no local slicing (`.data` IS the current page and renders whole, after local search/sort/filter), the internal pager's page count becomes `max(1, ceil(range-total / paginate))` (one calc site, consolidated), and the internal page-reset sites (`data` set, `setFilter`, `clearFilters`) are suppressed so a fetch write-back never fights the pager back to page 0 — page state then moves only via pager interaction, the `footer-page` command, or `setState()`. The existing `page` event (0-based, unchanged) becomes the fetch trigger: the consumer listens for it, fetches that server page, and writes `.data` back. Explicit `range-total=\"0\"` is server-confirmed empty (pager hidden), never conflated with absent. With [paginate] absent/0, [range-total] is inert for this table's own rendering but stays readable by a bound table-footer-ui (REQ-W-006 branch 2) for its count-only label — see the footer-authoritative shape below, which remains lawful and is unaffected by this attribute. Named identically to table-toolbar-ui's and table-footer-ui's own [range-total] (rows, never `pagination-ui[total]`'s pages — the ADR-0063 B5 collision rule); a third instance of one name for one concept."
+              "description": "Total row count across ALL server pages (gh#1754, ADR-0082) — the table-authoritative server-mode data contract. Presence-gated: the attribute's PRESENCE, not its value, is the mode switch (checked via hasAttribute, never the coerced value alone — the same discipline table-footer-ui's own [range-total] ships). Absent (the default) means client mode: today's behavior exactly, [paginate] slices `.data` as always. Present with [paginate] > 0 means server mode: no local slicing (`.data` IS the current page and renders whole, after local search/sort/filter), the internal pager's page count becomes `max(1, ceil(range-total / paginate))` (one calc site, consolidated), and the internal page-reset sites (`data` set, `setFilter`, `clearFilters`) are suppressed so a fetch write-back never fights the pager back to page 0 — page state then moves only via pager interaction, the `footer-page` command, or `setState()`. The existing `page` event (0-based, unchanged) becomes the fetch trigger: the consumer listens for it, fetches that server page, and writes `.data` back. Explicit `range-total=\"0\"` is server-confirmed empty (pager hidden), never conflated with absent. With [paginate] absent/0, [range-total] is inert for this table's own rendering but stays readable by a bound table-footer-ui (REQ-W-006 branch 2) for its count-only label — see the footer-authoritative shape below, which remains lawful and is unaffected by this attribute. Named identically to table-toolbar-ui's and table-footer-ui's own [range-total] (rows, never `pagination-ui[total]`'s pages — the ADR-0063 B5 collision rule); a third instance of one name for one concept. Explicit `range-total=\"?\"` (gh#1877, ADR-0082 Amendment) is the OPEN/unproven-total state — cursor/hasMore server paging with no known row count yet: still server mode (still presence-gated), but the internal pager's page count stays exactly one page ahead of wherever the pager currently sits (never a fixed ceil(...) total), keeping `next` enabled indefinitely instead of hiding the pager the way a confirmed `range-total=\"0\"` would. Resolves to the normal finite server-mode behavior the instant a real number replaces the \"?\" — every reader downstream (table-toolbar-ui, table-footer-ui) shares this same distinction. Note: since this prop is Number-typed and reflected, the framework's own attribute-reflection immediately rewrites the DOM attribute to the literal string \"NaN\" once \"?\" is parsed (`+\"?\"` → NaN, then stringified back onto the attribute) — the coerced numeric PROPERTY is what carries the open/unproven signal (non-finite), never a literal \"?\" surviving as the live DOM attribute value."
             },
             {
               "name": "filteredCount",