@adia-ai/a2ui 0.8.45 → 0.8.46

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog — @adia-ai/a2ui
 
+## [0.8.46] — 2026-08-22
+
+
+### Maintenance
+- **`catalog/` touched in this release window** (3 file(s), e.g. `catalog/catalog-a2ui_0_9.json`) — carried by the entries above.
+
 ## [0.8.45] — 2026-08-20
 
 ### Added

package/catalog/catalog-a2ui_0_9.json

@@ -5836,7 +5836,7 @@
           "default": null
         },
         "data": {
-          "description": "JS property (set programmatically — `el.data = [...]`). An array of plain objects; each object's keys are named by the `x` and `y` attributes — e.g. `<chart-ui x=\"month\" y=\"revenue\">` consumes `[{month:'Jan', revenue:3200}, {month:'Feb', revenue:4100}]`. The Chart.js `{labels, datasets}` envelope is NOT chart-ui's API — passing it (or any non-array value) renders an empty chart. May also be supplied declaratively as a JSON-array `data=\"[…]\"` attribute, hydrated once at connect. Custom accessor on the element class, not a reflected attribute.",
+          "description": "JS property (set programmatically — `el.data = [...]`). An array of plain objects; each object's keys are named by the `x` and `y` attributes — e.g. `<chart-ui x=\"month\" y=\"revenue\">` consumes `[{month:'Jan', revenue:3200}, {month:'Feb', revenue:4100}]`. The Chart.js `{labels, datasets}` envelope is NOT chart-ui's API — passing it (or any non-array value) renders an empty chart. May also be supplied declaratively as a JSON-array `data=\"[…]\"` attribute, hydrated once at connect. Custom accessor on the element class, not a reflected attribute. A datum object carrying a truthy `provisional` key (ADR-0081) renders that period's type-specific incomplete-period treatment (hollow/dashed bar, dashed line + faded area, hollow ring dot) on cartesian types; a no-op on radial/part-to-whole types and sparkline (gh#1690's N/A list). Provisional state is per-datum data-shape, not a chart-ui attribute — see ADR-0081 §3.",
           "$ref": "#/$defs/DynamicObjectList"
         },
         "dots": {
@@ -5861,6 +5861,16 @@
           ],
           "default": "abbr"
         },
+        "labels": {
+          "description": "Chart 2.0 axis-label mode (ADR-0081). Unset (default, \"\") always resolves to `outside` — today's pre-2.0 outside-the-plot axis labels, byte-for-byte unchanged. Set explicitly to `chip` to opt into the pill-treated overlay labels inset within the plot box (never hanging outside it) — the resolved value reflects onto the host as `data-labels-resolved=\"chip\"|\"outside\"`. Deliberately explicit-opt-in rather than auto-detected from full-bleed ancestry (`section[bleed]`/ `card-ui[padding=\"none\"]`): an earlier draft auto-activated chip mode on any full-bleed composition, which silently changed the rendering of every ALREADY-SHIPPED full-bleed chart the moment it shipped — this build's own 60-fixture Charts visual-eval floor caught it (2 `comp-chart-in-card-n-*` regressions). `chart-in-card` compositions opt in explicitly once their own examples are updated (gh#1805).",
+          "type": "string",
+          "enum": [
+            "",
+            "chip",
+            "outside"
+          ],
+          "default": ""
+        },
         "loading": {
           "description": "Show a skeleton placeholder instead of the chart body. Set to true while data is being fetched; clear once data arrives. Preserves the element's aspect-ratio dimensions so the skeleton occupies the same space the chart will fill. Parity with stat-ui[loading] and table-ui[loading] (§FB-12, v0.6.27).",
           "type": "boolean",
@@ -5911,6 +5921,11 @@
           "type": "number",
           "default": 0.4
         },
+        "today": {
+          "description": "Names the datum whose x-axis value marks \"today\" (ADR-0081). Unset (default, \"\") renders no marker — additive. Compared against each datum's x-key value via a loose string comparison (`String(datum[x]) === String(today)`), so category axes (\"month\", \"region\") work the same as literal date strings; chart-ui never auto-derives today from the clock. Renders a baseline dot + a short band tick (REQ-F-008) on cartesian types (bar, line, area, scatter, multi-line, stacked-bar, grouped-bar, composed); a no-op on every radial/part-to-whole type and on sparkline (gh#1690's N/A list). Fallback (not the primary mechanism): a datum already carrying a truthy `today` key is treated as an equivalent marker even with this attribute unset.",
+          "type": "string",
+          "default": ""
+        },
         "x": {
           "description": "Data key for x-axis (category) values",
           "type": "string",
@@ -25003,6 +25018,11 @@
           "type": "boolean",
           "default": false
         },
+        "filteredCount": {
+          "description": "Read-only. The row count AFTER search + column filters apply but BEFORE pagination slices it (gh#1807, ADR-0080, REQ-W-006) — a plain JS getter, no setter, never a reflected attribute. table-footer-ui's client-mode range-total derivation reads this directly; a raw `.data.length` read (the toolbar's own `count` fallback precedent) would double-count a filtered-out row. In server mode ([range-total] set, gh#1754, ADR-0082), filteredCount stays page-scoped — the loaded page's rows after local filters, NOT the server total across all pages; [range-total] is the server total, filteredCount never is (REQ-D-006).",
+          "type": "number",
+          "readOnly": true
+        },
         "frameless": {
           "description": "Drop the table's outer 1px perimeter and nothing else (gh#511) — row dividers are untouched (the perimeter is split onto its own --table-perimeter token, defaulting to --table-border). For card-composed tables: the card owns the frame, so the table's square perimeter otherwise renders a doubled edge (flush bleed) or a stray inner box (with content above). Standalone tables keep their chrome by default. Theming path without the attribute: set --table-perimeter to transparent per instance. Note: `<card-ui><section bleed>` already drops a direct-child table-ui's chrome automatically (card.css, gh#796) — `frameless`/`raw` on the instance still applies and is honored, but is no longer required just to avoid the doubled-edge look in that composition.",
           "type": "boolean",
@@ -25013,8 +25033,18 @@
           "type": "boolean",
           "default": false
         },
+        "no-pager": {
+          "description": "Hide the internal pagination bar while leaving [paginate] slicing, page state, the `page` event, and the `footer-page` command listener all intact (gh#1807, ADR-0080). The anti-doubled-pager mechanism for a table-footer-ui composition, client- or server-mode alike (gh#1754, ADR-0082): without it, a bound footer's own composed pager and the table's own internal one would both render for any non-empty paginated table. Explicit author intent — never suppressed automatically just because a footer happens to be bound.",
+          "type": "boolean",
+          "default": false
+        },
         "paginate": {
-          "description": "Rows per page. 0 = show all rows without pagination. When > 0, renders a pagination bar below the table.",
+          "description": "Rows per page. 0 = show all rows without pagination. When > 0, renders the internal pagination bar below the table — UNLESS [no-pager] is also set (gh#1807, ADR-0080), which keeps [paginate]'s slicing/page-state/`page`-event/`footer-page`-listener behavior but suppresses only the bar itself (the anti-doubled-pager path for a table-footer-ui composition). When [range-total] is also set (gh#1754, ADR-0082), [paginate] becomes purely presentational — it supplies only the page-size for pager math; no local slicing runs.",
+          "type": "number",
+          "default": 0
+        },
+        "range-total": {
+          "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.",
           "type": "number",
           "default": 0
         },
@@ -25024,7 +25054,7 @@
           "default": false
         },
         "search": {
-          "description": "Global search/filter string. Filters visible rows across all columns using case-insensitive substring matching. Resets to page 1 on change.",
+          "description": "Global search/filter string. Filters visible rows across all columns using case-insensitive substring matching. Does NOT reset the current page (verified against source at the gh#1754/ADR-0082 build — unlike setFilter()/clearFilters(), no internal page reset ever ran for a search change; this description previously claimed \"resets to page 1 on change,\" which the source never did). Aligning the doc to observed behavior here, not a behavior change — a page reset on search, if wanted, is a separate client-mode ticket.",
           "type": "string",
           "default": ""
         },
@@ -25110,10 +25140,10 @@
             }
           },
           "page": {
-            "description": "Fired when the user navigates to a different page.",
+            "description": "Fired when the table's own internal page state changes — an internal pager click, or a `footer-page` command applied (REQ-W-002). This is a RESYNC notification a bound `<table-footer-ui>` listens to for its own `page` attribute (REQ-W-004) — it is NOT the public server-mode fetch trigger a consumer should listen to; use `<table-footer-ui>`'s own `page-change` event for that (1-based, gh#1754/ADR-0082 REQ-W-003). Listening to both risks a duplicate fetch or an index-base mismatch.",
             "detail": {
               "page": {
-                "description": "New active page index (1-based).",
+                "description": "New active page index (0-based — gh#1808; the `footer-page` command and the `page` attribute on <table-footer-ui> are 1-based, this event's own detail is not).",
                 "type": "number"
               }
             }
@@ -25564,6 +25594,154 @@
         "version": 1
       }
     },
+    "TableFooter": {
+      "title": "TableFooter",
+      "description": "Footer / companion bar for a sibling table-ui (gh#1807, ADR-0080) — a \"Showing X–Y of N\" range label paired with a composed pagination-ui. Derivation-model API: set `page` / `page-size` / `range-total` and the footer derives total pages and the range window itself, so it never drifts out of sync with its own pager. Wired to the target table via a [for] id-ref and CustomEvents only (ADR-0079/ADR-0080) — the footer never writes a property or calls a method on the bound table. Drop below (or inside a card-ui footer alongside) any table-ui to add the standard data-grid pager + range summary without re-implementing pagination-ui's ellipsis truncation, keyboard handling, or ARIA.",
+      "type": "object",
+      "allOf": [
+        {
+          "$ref": "#/$defs/ComponentCommon"
+        },
+        {
+          "$ref": "#/$defs/CatalogComponentCommon"
+        }
+      ],
+      "properties": {
+        "component": {
+          "const": "TableFooter"
+        },
+        "for": {
+          "description": "id-ref of the table-ui to control. Falls back to the first sibling table-ui within the same parent when omitted.",
+          "type": "string",
+          "default": ""
+        },
+        "page": {
+          "description": "Current page, 1-based. Explicit attributes always win over derivation (per-attribute, not all-or-nothing) — see page-size/range-total.",
+          "type": "number",
+          "default": 1
+        },
+        "page-size": {
+          "description": "Rows per page. Default 0 (unknown) is the ORDINARY default state, not an exotic edge case: with page-size absent/0 and range-total present, the range label renders in count-only form (\"128 items\") and the pager does not render — the derivation math (pages = range-total / page-size) is undefined without a page size. In a client-mode composition (the resolved target has [paginate] > 0) and this attribute is unset, the footer derives page-size from the target's own [paginate] value.",
+          "type": "number",
+          "default": 0
+        },
+        "range-total": {
+          "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.",
+          "type": "number",
+          "default": 0
+        },
+        "siblings": {
+          "description": "Passed through to the composed pagination-ui's own [siblings] (page-number window size on each side of the current page).",
+          "type": "number",
+          "default": 1
+        },
+        "size": {
+          "description": "Passed through to the composed pagination-ui's own [size] (sm | md | lg, the universal size system).",
+          "type": "string",
+          "default": "md"
+        }
+      },
+      "required": [
+        "component"
+      ],
+      "unevaluatedProperties": false,
+      "x-adiaui": {
+        "anti_patterns": [
+          {
+            "fix": "<table-footer-ui page=\"1\" page-size=\"10\" range-total=\"128\"></table-footer-ui>",
+            "why": "table-footer-ui is derivation-only (REQ-F-002) — there is no [range-start]/[range-end] attribute pair (that shape belongs to table-toolbar-ui, which has no page/page-size knowledge of its own). Setting [page] + [page-size] + [range-total] derives the range window instead; a permanent three-way drift hazard is exactly what the derivation model exists to avoid.",
+            "wrong": "<table-footer-ui range-start=\"1\" range-end=\"10\" range-total=\"128\"></table-footer-ui>"
+          }
+        ],
+        "category": "agent",
+        "composes": [
+          "pagination-ui"
+        ],
+        "events": {
+          "footer-page": {
+            "description": "gh#1807, ADR-0080 (events-only interaction contract, extending ADR-0079's sender-prefixed toolbar-* precedent to a second sender) — dispatched directly at the resolved [for] target on every pager interaction. Detail: { page } (1-based). table-ui listens for this on itself, applied only when [paginate] > 0 (clamped to the valid page range; a non-numeric/NaN detail.page is a no-op); at [paginate=\"0\"] the command is a documented no-op on the table. Additive: any consumer, not only table-footer-ui, may dispatch this at a table-ui."
+          },
+          "page-change": {
+            "description": "The footer's own consumer-facing notification — a distinct name from the inbound footer-page command (ADR-0079's command≠notification separation). Fires on every pager interaction, in both client- and server-mode. Detail: { page } (1-based). This is the server-mode fetch hook: a consumer listens for it, fetches the new page, then sets `table.data` and the footer's own `page` (and `range-total` if the server's total moved) — the footer never optimistically advances its own state in server-mode."
+          }
+        },
+        "examples": [
+          {
+            "description": "Server-mode footer (gh#1754 Shape 1) paired with a for=-bound table-ui.",
+            "a2ui": "[\n  {\"id\": \"root\", \"component\": \"Column\", \"gap\": \"0\", \"children\": [\"tests\", \"ftr\"]},\n  {\"id\": \"tests\", \"component\": \"Table\", \"raw\": true},\n  {\"id\": \"ftr\", \"component\": \"TableFooter\", \"for\": \"tests\", \"page\": 1, \"page-size\": 10, \"range-total\": 128}\n]",
+            "name": "table-footer-server-mode"
+          },
+          {
+            "description": "Client-mode footer bound to a [paginate]d table-ui with its own internal pager suppressed via [no-pager].",
+            "a2ui": "[\n  {\"id\": \"root\", \"component\": \"Column\", \"gap\": \"0\", \"children\": [\"tests-c\", \"ftr\"]},\n  {\"id\": \"tests-c\", \"component\": \"Table\", \"paginate\": 10, \"no-pager\": true, \"raw\": true},\n  {\"id\": \"ftr\", \"component\": \"TableFooter\", \"for\": \"tests-c\"}\n]",
+            "name": "table-footer-client-mode"
+          }
+        ],
+        "keywords": [
+          "table-footer",
+          "pagination",
+          "pager",
+          "range",
+          "showing",
+          "data-grid",
+          "directory",
+          "admin",
+          "backoffice",
+          "listing",
+          "records"
+        ],
+        "name": "UITableFooter",
+        "parts": {},
+        "related": [
+          "table",
+          "table-toolbar",
+          "pagination",
+          "card"
+        ],
+        "slots": {
+          "empty": {
+            "description": "Renders in place of the range label — the same [data-range] region — when [range-total] is EXPLICITLY present and equal to \"0\" (checked via hasAttribute, never the computed value alone, so an unset range-total during loading never flashes this content). Mutually exclusive with a positive [range-total]: the normal \"Showing X–Y of N\" (or count-only) text always wins whenever range-total resolves positive. Plain author-supplied markup — table-footer-ui does not template or constrain its shape. Naming matches table-toolbar-ui's own `empty` slot convention."
+          }
+        },
+        "states": [
+          {
+            "description": "Default, ready for interaction.",
+            "name": "idle"
+          }
+        ],
+        "status": "beta",
+        "synonyms": {
+          "pager": [
+            "table-footer",
+            "pagination"
+          ],
+          "pagination": [
+            "table-footer",
+            "pagination"
+          ]
+        },
+        "tag": "table-footer-ui",
+        "tokens": {
+          "--table-footer-gap": {
+            "description": "Gap between the range label and the pager"
+          },
+          "--table-footer-px": {
+            "description": "Horizontal padding"
+          },
+          "--table-footer-py": {
+            "description": "Vertical padding"
+          },
+          "--table-footer-summary-fg": {
+            "description": "Range-label text color"
+          },
+          "--table-footer-summary-size": {
+            "description": "Range-label font size"
+          }
+        },
+        "traits": [],
+        "version": 1
+      }
+    },
     "TableOfContents": {
       "title": "TableOfContents",
       "description": "Auto-generated in-page table of contents. Scans a target container\nfor headings (default `h2,h3`), ensures each has an `id` (slugifies\nthe text content if missing), and stamps a `<nav>` list of anchor\nlinks. An `IntersectionObserver` tracks the active heading and\napplies `[data-active]` to the matching link so consumers can style\nthe currently-visible section. Smooth-scroll on click is handled by\nthe global `scroll-behavior: smooth` set in resets.css.\n\nPair with a sticky container (`position: sticky; top: <offset>;`) in\nan aside / right rail for the classic docs-site outline pattern.\n",

package/catalog/catalog-a2ui_0_9_rules.txt

@@ -158,6 +158,7 @@
 - Heading slot accepts inline badges/metadata: <span slot="heading"><text-ui strong>Title</text-ui><badge-ui text="New" variant="primary"></badge-ui></span> renders title + badge on one row.
 - Description slot also accepts bare <p> or <small> elements as siblings of the heading — they participate in the grid's row 2 without needing slot="description".
 - Multiple <section> siblings are allowed and stack vertically. [bleed] on a section removes its margin for edge-to-edge content (tables, charts); [padding] adds a canvas-scrim background for hero regions.
+- [bleed] is unconditionally author-controlled — card.css never restores the section's inset on your behalf (gh#1801, operator ruling 2026-08-20; supersedes gh#1095's removed auto-restore guard). A full-bleed <chart-ui> that still draws gridlines or value labels, or is paired with a <chart-legend-ui>, can clip that text under the card's own corner-rounded overflow:hidden — keeping it clear of the card frame is YOUR responsibility as the author, e.g. by rendering value/ guide text as overlay chips INSET within the plot area rather than hanging outside it, or by placing a <chart-legend-ui> in its own non-bled section. See chart-in-card.examples.html for the pattern.
 - When neither [raw] nor [frameless] is present, a <table-ui> placed directly inside a <section bleed> automatically renders chromeless (background/box-shadow/border-radius reset; card.css, gh#796): the card already owns the frame, so the table doesn't need its own. table.yaml's [raw]/[frameless] docs describe the same composition; an explicit [raw] or [frameless] on the table still applies and is honored. A plain (non-bleed) <section> is unaffected — its own padding keeps a nested table's frame legible as an intentional nested surface.
 - [grow] on a section makes it fill the card's remaining height (flex:1 — same semantics as col-ui[grow]/row-ui[grow]). The card becomes a flex column so the section absorbs the leftover space after the header/footer. Requires the card to have a definite height (inline height, grid row track, or flex parent) — a content-sized card has nothing to fill. Combine with [bleed] for edge-to-edge fill: <section bleed grow>. A <chart-ui> directly inside a <section bleed> auto-grows without [grow] (zero-config convenience for the common chart case).
 - Footer with a [slot="description"] + [slot="action"] pair triggers justify-content: space-between — useful for a "Last saved …" note on the left and a Save/Cancel button group on the right.
@@ -701,10 +702,17 @@
 - Binary on/off only — no third state. For tri-state controls use <check-ui> with [indeterminate].
 - Use for settings toggles, feature flags, mode switches; for form gates / consent / multi-select use <check-ui> instead.
 
+## TableFooter
+- Pair <table-footer-ui> with <table-ui> via [for="<table-id>"] (or rely on first-sibling fallback when both are inside the same parent). Client-mode composition (a [paginate]-sliced table): set [no-pager] on the table-ui so its own internal pagination bar doesn't render alongside the footer's composed one — table-footer-ui never auto-suppresses it for you.
+- Server-mode composition (gh#1754 Shape 1 — the server returns the page's rows plus the total row count): set [range-total] to the server's total, [page] / [page-size] from your own request state, and listen for the footer's `page-change` event to fetch the next page — the footer does not optimistically advance its own [page] in server-mode; write it back after the fetch resolves.
+- The toolbar's [count] badge and this footer's range label coexist by design — they answer different questions (the collection summary vs. the page-window position) and neither replaces the other. In a composition that includes a table-footer-ui, leave the toolbar's [range-start]/[range-end]/[range-total] unset — the range summary's home is the footer.
+- Canonical composition: card-ui header (title + primary action) → a plain <section> wrapping a title-less <table-toolbar-ui for> → a <section bleed> wrapping the <table-ui id> → a <footer divider> wrapping this <table-footer-ui for> — see the table-in-card pattern.
+- Use <span slot="empty"> (or any markup) inside a table-footer-ui that also sets [range-total="0"] to show a "no results" message in the range label's own position, without a layout shift versus the normal range text. Only fires on an EXPLICIT range-total="0" — omitting range-total entirely (loading) never shows it.
+
 ## TableToolbar
-- 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. Do NOT also use <card-ui>'s <header> on the same card — that produces a doubled chrome row.
+- 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.
 - 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.
-- Place the toolbar ABOVE the <card-ui> containing the table-ui, or use [variant="card"] when standing alone outside a card-ui parent (the variant wraps the toolbar in card-style chrome).
+- 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).
 - Use slot="action" (or [slot="actions"]) for trailing primary buttons (Invite, Export, +New). Use [text] / [count] props for the left cluster, or slotted [slot="title"] / [slot="count"] when content is markup (a <span> + <badge-ui>, etc.).
 - Listen for toolbar events (`search`, `filter-change`, `sort-change`, `columns-change`, `page-size-change`) only to mirror state to URL / persistence / analytics. The toolbar already wires its changes into the bound table — you don't need to manually 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.
@@ -716,10 +724,11 @@
 ## Table
 - Canonical composition: wrap <table-ui> in <card-ui><section bleed> for edge-to-edge tables. The [bleed] removes section padding so columns span the full card width (see apps/saas/members, billing, admin-dashboard).
 - Pair with <table-toolbar-ui for="<table-id>"> for any table that needs search / filter / sort / columns visibility. Do NOT re-implement those affordances in the card header — the toolbar auto-wires search/filter/sort/columns changes into the bound table via `toolbar-*` CustomEvents (gh#1764/#1780, ADR-0079 — events-only interaction contract; table-ui listens for toolbar-search/toolbar-filter-set/toolbar-filter-clear/ toolbar-columns-set/toolbar-paginate on itself). Any consumer, not only table-toolbar-ui, may dispatch these events directly at a table-ui instance.
+- Pair with <table-footer-ui for="<table-id>"> for the pager + "Showing X-Y of N" range label (gh#1807, ADR-0080; gh#1754, ADR-0082) — table-ui listens for its `footer-page` command (detail {page}, 1-based) on itself, applied whenever [paginate] > 0 — client mode AND table-authoritative server mode ([range-total] set) alike — clamped to the valid page range (server-derived when [range-total] is set). Only at [paginate="0"] does the table treat it as a documented no-op, in either mode. Set [no-pager] on the table when a composition also binds a footer (client- or server-mode), or the internal pagination bar and the footer's composed one both render — [no-pager] leaves slicing/page-state/the `page` event untouched, it only hides the internal bar.
 - Cells truncate single-line by default (v0.6.21 §403 truncate-default). Opt out per-table with [wrap] for whole-table multiline, or per-cell with [data-wrap] on a single column / cell.
 - [raw] is a visual-and-lifecycle chrome reset for consumer-owned body markup — render()'s early return (`if (this.raw) return;`) is unconditional: no header injection, no .data/.columns reconciliation, no empty/loading overlays, no aggregation or pagination footers, even if .columns and .data are set. Reach for it only when the consumer authors 100% of the body (spreadsheet / inline-edit style patterns wrapping a native <table>) — never to "keep the data lifecycle but skip demo seeding."
 - Listen for the `sort` event with detail.key + detail.dir (NOT .column / .direction). `cell-click` detail carries {key, row, value, dataIndex}. Per ADR-0027, table-ui composes check-ui, icon-ui, progress-ui, pagination-ui, skeleton-ui, badge-ui — consumer pages must explicitly import the ones they use.
-- For large datasets (100+ rows), use [paginate="N"] to limit rendered rows and add a pagination bar. [virtual] is NOT a recognized prop and is silently ignored — there is no DOM-level virtual scrolling in table-ui. [paginate] is the supported performance mechanism. Wire [paginate] with optional [search] and the `page` event for server-driven pagination.
+- For large datasets (100+ rows), use [paginate="N"] to limit rendered rows and add a pagination bar. [virtual] is NOT a recognized prop and is silently ignored — there is no DOM-level virtual scrolling in table-ui. [paginate] is the supported performance mechanism. For server-driven pagination (gh#1754, ADR-0082), set [paginate="N"] (page size) + [range-total="M"] (server total row count) together — [paginate] then becomes purely presentational (no local slicing), `.data` holds exactly the current server page. The table's own `page` event (0-based) is an internal resync notification, not the fetch trigger — a bound <table-footer-ui> listens to it to keep its own [page] in sync. The PUBLIC fetch trigger is <table-footer-ui>'s own `page-change` event (1-based): listen for it, fetch that server page, then write the rows back to `.data` and the footer's own [page]. Listening to the table's `page` event instead risks a duplicate fetch or an index-base mismatch (0-based vs 1-based). [search]/[sort]/column filters, when used alongside server paging, still operate on the loaded page only — not a server-side query.
 
 ## Tab
 - <tab-ui> only renders inside <tabs-ui>. Never use it standalone. The parent reads each tab's [text] + [icon] + [value] to render the button strip; the tab's default slot is the panel content that the parent auto-hides when inactive.

package/catalog/tier-index.json

@@ -1,14 +1,14 @@
 {
-  "catalogId": "adia.tiers@0.8.45",
+  "catalogId": "adia.tiers@0.8.46",
   "description": "Tier index of the AdiaUI catalog contract (ADR-0050). L0-L4 ladder; every tier-N entry is a declared composition of tier-(N-1) entries. L1 `composes` edges speak A2UI component TYPE names — the R-C7 catalogs’ `components` keys (genui-system SPEC R-C13). Derived — regenerate with `npm run build:catalog-tiers`, never hand-edit.",
   "extends": {
     "catalogId": "adia.base",
-    "version": "0.8.45"
+    "version": "0.8.46"
   },
   "tiers": {
     "L0": {
       "composesTier": null,
-      "count": 189,
+      "count": 190,
       "entries": {
         "A2UIRoot": {
           "category": "container",
@@ -1000,6 +1000,12 @@
           "origin": "primitive",
           "tag": "table-ui"
         },
+        "TableFooter": {
+          "category": "agent",
+          "composes": [],
+          "origin": "primitive",
+          "tag": "table-footer-ui"
+        },
         "TableOfContents": {
           "category": "navigation",
           "composes": [],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/a2ui",
-  "version": "0.8.45",
+  "version": "0.8.46",
   "description": "The A2UI protocol — runtime (renderer, registry, streams, surface manifest, wiring primitives, dockable base classes) plus protocol-side validation. Framework-agnostic and dependency-free; pairs with any A2UI-conformant component set. Folded from @adia-ai/a2ui-runtime + the protocol half of @adia-ai/a2ui-validator (ADR-0048).",
   "type": "module",
   "exports": {

package/registry.js

@@ -339,6 +339,8 @@ export const registry = new Map([
   ['Spinner',           'spinner-ui'],
   ['StepProgress',      'step-progress-ui'],
   ['Swatch',            'swatch-ui'],
+  // gh#1807, ADR-0080 — footer/companion bar for a sibling table-ui.
+  ['TableFooter',       'table-footer-ui'],
   // sidecar directory is `toc/toc.a2ui.json`; catalog title is TableOfContents
   // but the component's own tag is the shorter `toc-ui` (x-adiaui.tag) — not
   // the naive `table-of-contents-ui` kebab expansion of the type name.