@adia-ai/adia-ui-factory 0.8.48 → 0.8.50

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-ui-kit-factory",
-  "version": "0.8.48",
+  "version": "0.8.50",
   "description": "Author and verify apps built ON the adia-ui (@adia-ai) light-DOM web-component framework \u2014 orient, scaffold, compose, wire, verify, and migrate across SPA and SSR rendering modes. Wires the a2ui MCP for catalog retrieval, UI generation, and validation.",
   "author": {
     "name": "Kim",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-ui-kit-factory",
-  "version": "0.8.48",
+  "version": "0.8.50",
   "description": "Author and verify apps built ON the adia-ui (@adia-ai) light-DOM web-component framework — orient, scaffold, compose, wire, verify, and migrate across SPA and SSR rendering modes. Wires the a2ui MCP for catalog retrieval, UI generation, and validation.",
   "author": {
     "name": "Kim",

package/.mcp.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "adia-gen-ui": {
       "command": "npx",
-      "args": ["-y", "@adia-ai/mcp@0.8.48", "gen-ui"]
+      "args": ["-y", "@adia-ai/mcp@0.8.50", "gen-ui"]
     }
   }
 }

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog — adia-ui-kit-factory
 
+## [0.8.50] — 2026-08-23
+
+### Maintenance
+- **Lockstep bump riding the v0.8.50 cut** (`scripts/release/check-lockstep.mjs`); the headline v0.8.50 work ships in @adia-ai/web-components (prose/verse sheet removal gh#1885 / PR #1918, input/search fill-default posture gh#1856 — see `packages/web-components/CHANGELOG.md#0850--2026-08-23`). Package-local changes are listed below.
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+- **`.codex-plugin/` touched in this release window** (1 file(s), e.g. `.codex-plugin/plugin.json`) — carried by the entries above.
+
+### Docs
+- **`references/` + `skills/` docs refreshed for the release window** — `component-model.md` and `spa-architecture.md` plus the `find-unused` (`recon-and-audits.md`), `host-wiring` (`SKILL.md`, `mode-wiring-detail.md`), and `table-composition` (`base-table.md`) skill references updated to current framework contracts (incl. the gh#1918 `[prose]`/`[verse]` removal and gh#1856 fill-default posture).
+
 ## [0.8.48] — 2026-08-23
 
 ### Added

package/README.md

@@ -98,7 +98,7 @@ surface-qa-agent) · `component-model.md` · the `references/contracts/` twins.
 
 ## MCP
 
-`adia-gen-ui` server pinned: `@adia-ai/mcp@0.8.48` (tool SoT:
+`adia-gen-ui` server pinned: `@adia-ai/mcp@0.8.50` (tool SoT:
 `packages/gen-ui/mcp/TOOLS.md` — the `gen-ui` section; stability rule in
 `references/contracts/`; pin lives in `.mcp.json` — `check:plugin-count-claims`
 guards this README copy against it). The server is `adia-mcp gen-ui`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-factory",
-  "version": "0.8.48",
+  "version": "0.8.50",
   "description": "Author and verify apps built ON the adia-ui (@adia-ai) light-DOM web-component framework — orient, scaffold, compose, wire, verify, and migrate across SPA and SSR rendering modes. Wires the a2ui MCP for catalog retrieval, UI generation, and validation.",
   "keywords": [
     "adia-ui",

package/references/component-model.md

@@ -119,7 +119,7 @@ Three levels, all `--a-*`:
 
 ## "Registers" — typographic treatments, opt-in
 
-A _register_ (e.g. `verse`, `prose`) is a typographic treatment applied two ways together: **link the register stylesheet** (`styles/verse.css`) **and** put the **attribute** on the surface (`<my-surface verse>`). One without the other is a no-op — a common smell. Body/UI text defaults to `--a-font-family-ui`; registers opt a subtree into a different family/rhythm.
+A _register_ (e.g. `scale="ui-sm"`, `scale="content-md"`) is a typographic treatment applied two ways together: **link the register stylesheet** (`styles/scale.css`, or wrap the surface in `<theme-provider scale="…">`, which adopts it on demand) **and** put the **attribute** on the surface. One without the other is a no-op — a common smell. Body/UI text defaults to `--a-font-family-ui`; registers opt a subtree into a different family/rhythm.
 
 ## Layout realities
 

package/references/spa-architecture.md

@@ -53,7 +53,7 @@ alternatives:
 - **One registration script** — the side-effecting barrel `import '@adia-ai/web-components'`. Don't piecemeal-import primitives: composites render internal `*-ui` tags (e.g. `chat-input-ui` internally renders `textarea-ui` + `select-ui`) that stay unregistered and collapse to 0px unless the barrel ran.
 - Bespoke shell children need the **cluster barrel** (`@adia-ai/web-modules/shell`, `/chat`, `/editor`, `/simple`) — importing `admin-shell.js` alone registers only the host tag, not `admin-sidebar` / `admin-page` / the other children.
 - Never hand-roll `:where(html,body){}` — the foundation owns the page frame; re-rolling it drifts from the system (the classic serif-leak bug).
-- A `[scale]` register has two halves: link `scale.css` **and** put `scale="…"` (one of the six tiers — `ui-sm | ui-md | ui-lg | content-sm | content-md | content-lg`) on the surface. One without the other is a no-op. `[verse]`/`[prose]` still work as deprecated aliases (`ui-sm`/`content-md`) but are removed at v1.0 — new code should reach for `[scale]` directly.
+- A `[scale]` register has two halves: link `scale.css` **and** put `scale="…"` (one of the six tiers — `ui-sm | ui-md | ui-lg | content-sm | content-md | content-lg`) on the surface. One without the other is a no-op.
 - `themes.css` (named palettes) is **not** in the styles barrel — link it separately. `data-scheme` switches light/dark; `data-theme` picks the named palette.
 - Guards: `defineIfFree(tag, ctor)` (`core/register.js`) for defines; a `#booted` flag in `connected()` — the callback re-fires on DOM moves. And `customElements.whenDefined(name)` never rejects: a `Promise.all([...whenDefined])` boot gate hangs forever on one unimported tag — chrome renders (tag-keyed CSS), the page stays "empty", zero console errors.
 

package/skills/find-unused/references/recon-and-audits.md

@@ -85,7 +85,7 @@ proposing any edit.
 opt-in, confirm something imports it:
 
 ```bash
-git grep -n "styles/scale.css\|styles/themes.css\|styles/verse.css\|styles/prose.css"
+git grep -n "styles/scale.css\|styles/themes.css"
 
 # Attributes reach the DOM from markup AND from script — a setAttribute('scale', …)
 # in a .js module counts. Searching templates only produces a false "unused".

package/skills/host-wiring/SKILL.md

@@ -90,7 +90,7 @@ Mode:            SPA | SSR | hybrid                     — signal: <file / dep
 Framework:       <name, or none>                          — [D] documented | [G] inferred, per ssr-integration.md
 Registration:    <file>:<call site>                        — one side-effecting barrel import, client-only
 Route owner:     <router-ui> | <framework router>          — exactly one per scope
-CSS links:       host.css + styles/index.css (+ scale.css, or its deprecated verse.css/prose.css alias) — both live, or primitives render unstyled
+CSS links:       host.css + styles/index.css (+ scale.css) — both live, or primitives render unstyled
 State placement: cookies/localStorage/session | client signal — per mode's lifetime rule
 Gates:           registration / route-owner / CSS-links / state — pass | fail, each
 ```

package/skills/host-wiring/references/mode-wiring-detail.md

@@ -43,8 +43,7 @@ Build order — snippets and the full invariant list in `spa-architecture.md`;
 
 1. **Host document** — npm-consumer paths; cascade order later-wins:
    `host.css` → `styles/index.css` → opt-in `scale.css` (the ancestor
-   `[scale]` register — `verse.css`/`prose.css` are its deprecated,
-   still-working aliases) → page → component CSS. Link BOTH `host.css`
+   `[scale]` register) → page → component CSS. Link BOTH `host.css`
    and `styles/index.css` — the styles barrel is split and `host.css` is
    foundation-only; alone it renders primitives unstyled.
 2. **Surface container** — self-booting custom element rendering in

package/skills/table-composition/references/base-table.md

@@ -192,6 +192,22 @@ they're documented alongside the real `sortFn`.
   entirely and let the table's own internal pager work server-side alone, the ticket's literal
   headline case. See table.yaml's `[range-total]` prop doc and
   `docs/ops/adr/adr-0082-table-ui-server-range-total.md` for the full contract.
+  **[extended 2026-08-23, ADR-0082 amendment, gh#1877]** for cursor/`hasMore`
+  server paging where the total isn't known yet, `range-total="?"` is an open/
+  unproven-total state (still presence-gated into server mode — "?" is a value
+  of the same attribute, not a new one): `table-ui` keeps the pager exactly one
+  page ahead of the current page (`next` stays enabled indefinitely, never a
+  false "last page") instead of a fixed `ceil(...)`; `table-toolbar-ui` /
+  `table-footer-ui` render "Showing X–Y" with no "of N" until a real number
+  replaces the "?", at which point it resolves to the ordinary finite-total
+  behavior above with nothing else changed. Two more, additive, on
+  `table-toolbar-ui`/`table-footer-ui` only (never `table-ui` — no independent
+  second-total concern there): `range-of="<whole>"` appends "(of `<range-of>`
+  total)" onto the finite range text — a secondary filtered-of-whole total,
+  unset by default, never applies while the range is open or loading/empty —
+  and `range-noun="<noun>"` appends a per-slice noun after the range text in
+  both the finite and open cases ("of 80 users", "Showing 51–100
+  subscriptions"), also unset by default.
 
 ## table-toolbar-ui — the companion search/filter/sort/columns bar