@adia-ai/adia-ui-factory 0.8.44 → 0.8.46

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-ui-kit-factory",
-  "version": "0.8.44",
+  "version": "0.8.46",
   "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/.mcp.json

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

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog — adia-ui-kit-factory
 
+## [0.8.46] — 2026-08-22
+
+
+### Maintenance
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+- **`skills/` touched in this release window** (3 file(s), e.g. `references/annotations.yaml`) — carried by the entries above.
+
+## [0.8.45] — 2026-08-20
+
+### Changed
+- **Plugin description tuning from the 2026-08-19 check-routing findings (gh#1731).** Narrowed
+  `app-audit`'s symptom vocabulary — dropped the "what's wrong with X" catch-all and tightened
+  "renders unstyled/broken/off" to "looks unstyled/off-brand" — so it stops gravitationally
+  stealing sibling trigger cases from `chart-selection`, `data-wiring`, `surface-qa`,
+  `project-scaffolding`, and `app-planning`. Added the "harvest chunks / point retrieval at our
+  own corpus" trigger phrase to `gen-ui-wiring` (was routing DEAD in the blind-judge sim). Scoped
+  `surface-qa` to a CONSUMER app's surfaces and named the framework repo's own dogfood/demo-page
+  sweep (forge's `demo-audit`) in a NOT-line — fixes a routing leak on that wording. Closes #1731.
+
+### Maintenance
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+- **`references/` touched in this release window** (2 file(s), e.g. `references/component-model.md`) — carried by the entries above.
+- **`skills/` touched in this release window** (7 file(s), e.g. `app-audit/SKILL.md`) — carried by the entries above.
+
 ## [0.8.44] — 2026-08-20
 
 ### Maintenance

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.44` (tool SoT:
+`adia-gen-ui` server pinned: `@adia-ai/mcp@0.8.46` (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.44",
+  "version": "0.8.46",
   "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.",
   "keywords": [
     "adia-ui",

package/references/component-model.md

@@ -51,6 +51,18 @@ import { UIElement, signal, computed, effect } from '@adia-ai/web-components/cor
 
 Declared `static properties` are wrapped as signals automatically, so setting `el.disabled = true` re-renders. Don't run a parallel `CustomEvent`-only state path that competes with signals.
 
+**No context-request protocol — a ratified non-goal, not an oversight.** There is no
+`context-request`/`ContextProvider` event channel anywhere in `web-components` or `web-modules`
+(reactivity review, `.claude/docs/reports/2026-08-20-reactivity-review/02-web-modules-state.md`
+§4 — zero hits in `web-components`/`web-modules`, confirmed repo-wide by direct grep). "Context"
+reaches a component two ways only: **CSS cascade** (theme/
+density tokens land on every descendant for free, no wiring needed) and **host-injected
+properties** (a shell or app hands a child a JS reference it needs — a renderer, a store, a
+`runTurn` callback — as a plain property assignment, never a request/response round-trip). If a
+component needs data or a capability from outside its own subtree, that's a property the owning
+shell/app injects, or a `data-wiring` pattern (`signal()`/`DataClient`) — never a new
+context-request channel authored ad hoc.
+
 ## Choosing components — the recurring calls
 
 Selection mistakes that keep recurring (verify props with `lookup_component` when unsure):
@@ -71,7 +83,7 @@ Selection mistakes that keep recurring (verify props with `lookup_component` whe
 - **Components silently accept any made-up attribute** — `text-ui muted`, `card-ui hover-elevate` are no-ops with zero warnings. Check the real prop list (`lookup_component`) before authoring; a rendered-but-unstyled state usually means an invented attr.
 - **`empty-state-ui` takes `[heading]`, not `[title]`** — `title=` becomes the native tooltip and the message silently doesn't render.
 - **Primary content often rides the default slot, not `text=`/`label=`** — `kbd-ui` and `card-ui` are the canonical traps. `button-ui` accepts both `text=` and child text; prefer `text=` for generated UI.
-- **Shell-tier bespoke children reflect state as attributes** (`admin-sidebar[collapsed]`) — read and style via attribute selectors; coordinate via `querySelector`, not a central store.
+- **Shell-tier bespoke children reflect state as attributes** (`admin-sidebar[collapsed]`) — read and style via attribute selectors; coordinate via `querySelector`, not a central store. This is a parent-reaching-into-child sanction scoped to shell-tier bespoke composition only — it never licenses the reverse direction; ordinary app components still follow `data-wiring`'s data-down/events-up rule, where a child reaching into a parent's internals is a defect.
 
 ## Traits — behavior by declaration
 

package/references/data-and-hydration.md

@@ -1,15 +1,15 @@
 ---
 name: data-and-hydration
 load-when: wiring an adia-ui app's data-flow, state ownership, content hydration, or section registration
-load-size: ~2.5k tokens
+load-size: ~3.5k tokens
 required-for: [data-wiring — all modes]
 ---
 
 # Data, state & hydration — patterns
 
-Code shapes for the five data-flow patterns, the three hydration paths, and section wiring. The ownership rules (single-owner · projections-only · attribution) are the `data-wiring` rubric gates.
+Code shapes for the six data-flow patterns, the three hydration paths, and section wiring. The ownership rules (single-owner · projections-only · attribution) are the `data-wiring` rubric gates.
 
-## The five patterns
+## The six patterns
 
 **1 · Signals** — fine-grained reactivity (no virtual DOM).
 
@@ -19,14 +19,35 @@ const view = signal('live');
 effect(() => render(view.value));   // re-runs on change; auto-cleans on disconnect
 ```
 
-**2 · Service / Controller / Command** — CRUD with undo. The Service is **async from day one** (so an in-memory impl can later swap for a remote one behind the same interface); the Controller orchestrates signals + service; Commands record patches for undo.
+**2 · Shared app store** — state read by more than one component/module. `createStore()`
+(`@adia-ai/web-components/core/store.js`) is `signal()` plus a Set-of-listeners-compatible
+`subscribe(cb) -> unsubscribe` for consumers that are closures/classes rather than `effect()`
+bodies — the blessed replacement for a hand-rolled `new Set()` pub/sub (reactivity review R2;
+`.claude/docs/reports/2026-08-20-reactivity-review/03-app-layer-stores.md` §4). `.value`
+composes with `computed()`/`effect()` like any signal; `subscribe()` is the extra imperative
+channel. Interops with `UIElement`'s `controller` setter for free.
+
+```js
+import { createStore } from '@adia-ai/web-components/core/store.js';
+const planStore = createStore({ items: [] });
+const stop = planStore.subscribe((v) => renderPlanRail(v.items)); // imperative consumer
+// stop() when that consumer is disposed — its own connectedCallback/
+// disconnectedCallback teardown, a route change, etc.
+el.controller = planStore;   // OR: hand it to an element via the controller-setter seam
+//                               (cleans the subscription up automatically, no stop() needed)
+```
+
+Migrating an existing hand-rolled Set-of-listeners store onto this primitive is opportunistic,
+one store at a time — not a required rewrite of every app-layer store at once.
+
+**3 · Service / Controller / Command** — CRUD with undo. The Service is **async from day one** (so an in-memory impl can later swap for a remote one behind the same interface); the Controller orchestrates signals + service; Commands record patches for undo.
 
 ```js
 class InMemoryTaskService { async create(d){…} async update(id,d){…} async delete(id){…} }
 // swap for RemoteTaskService (same interface) → Controller + Commands unchanged
 ```
 
-**3 · DataClient + mappers** — the UI reads typed **projections**, never a backend. The pure mapper is the fixtures⇄API swap seam.
+**4 · DataClient + mappers** — the UI reads typed **projections**, never a backend. The pure mapper is the fixtures⇄API swap seam.
 
 ```js
 const labs = await client.read({ type: 'LabRecommendationSet', params });   // → projection
@@ -36,7 +57,7 @@ await client.mutate({ type: 'order', payload }, { action_source: btn.dataset.act
 
 **Attribution `[gate]`:** every `mutate` passes an `action_source`; the client throws without it.
 
-**4 · Property-API binding** — populate catalog components by property, not children.
+**5 · Property-API binding** — populate catalog components by property, not children.
 
 ```js
 table.columns = [{ key:'name', label:'Name', sortable:true }];
@@ -46,7 +67,7 @@ select.options = opts;         // the element auto-stamps its slots at connected
                                // as visible flow content and break the parent's layout
 ```
 
-**5 · Declarative `data-*`** — static flows; state is CSS.
+**6 · Declarative `data-*`** — static flows; state is CSS.
 
 ```html
 <main data-auth> … </main>
@@ -92,3 +113,54 @@ fired — N drawers for N rows is a defect.
 - **Own the URL** when you need query params: `history.replaceState(...)` and reflect `data-route-path` yourself; don't set `router.routes` (it path-routes and clobbers query params).
 - **Single owner** per piece of state — the ownership assignments are the `data-wiring` rubric gates; the mechanic: a control mutates the route, an observer/CSS reflects it back — never a second source of truth.
 - **Never reset user-set state from a sibling control** — changing one selector (engine, tab) must not auto-reset an unrelated user-controlled one (mode, theme), even if the new selection ignores that setting.
+
+## Subscribe-delivery timing — never assumed uniform
+
+`subscribe(cb)` does not mean the same thing across these patterns — read the actual store before
+assuming a caller gets a value the moment `subscribe()` returns (reactivity review,
+`.claude/docs/reports/2026-08-20-reactivity-review/03-app-layer-stores.md` §1/§4):
+
+- **plan-store** delivers the current snapshot **synchronously**, inside `subscribe()` itself,
+  before the caller sees the returned unsubscribe function (`plan-store.js` — `subscribe(cb) {
+  listeners.add(cb); cb(items.slice()); return … }`).
+- **DataClient** delivers the first snapshot **asynchronously**, via `read(query).then(handler)`
+  — and **silently skips that first delivery if the read rejects** (`.catch(() => {})`
+  swallows the error with no handler call at all). Don't assume a `DataClient.subscribe()`
+  caller has data yet on the next line; a rejected first read is a silent no-op, not a visible
+  error — worth an explicit loading/error affordance rather than trusting the subscribe channel
+  alone.
+- **`createStore()`** (the blessed shared-app-store primitive above, gh#1761/PR #1775)
+  delivers **nothing** on subscribe: `subscribe(cb)` only adds `cb` to the listener set and
+  returns the unsubscribe function — no synchronous call, no queued microtask delivery. A
+  consumer that needs the current value reads `.value`/`.peek()` itself (typically once, at
+  connect/render time); `subscribe()` only notifies of *later* changes. This is why the
+  `UIElement.controller` setter interop works with no special-casing — the element's own render
+  reads `.value` directly, and the controller's `subscribe()` callback only triggers a re-render.
+
+Until the store-migration sweep reaches them, plan-store and DataClient keep their own delivery
+timing — `createStore()` is the norm going forward for *new* shared state, not a retrofit.
+
+## Race control — the supersede-token pattern
+
+Three home-grown last-write-wins mechanisms independently solve the same problem — an
+in-flight async operation completing after a newer one has already superseded it — with no
+shared idiom (reactivity review, `03-app-layer-stores.md` §4 tail):
+
+- `adia-embed-labs.js`'s `#summaryGen` — a private counter incremented before starting an async
+  phase; the counter's value at start is captured (`const gen = ++this.#summaryGen`) and checked
+  again once the async work resolves (`if (gen !== this.#summaryGen) return;`) — a mismatch means
+  a newer call already took over, so the stale completion is dropped silently.
+- `site.js`'s `_routeResolveSeq` — the same shape guarding a route-template resolution against a
+  navigation that fires again before the first one finishes.
+- The A2UI renderer's `generationId` (`beginSurfaceUpdate`/`commitSurfaceUpdate`,
+  `packages/gen-ui/a2ui/renderer.js`) — the same shape at the surface-lifecycle level, minted per
+  update and checked at commit time.
+
+**The idiom, generalized:** capture a token (an incrementing counter, or a minted id) at the
+start of the async operation; before applying its result, compare the captured token against the
+current one; a mismatch means a newer operation superseded this one — drop the result, never
+apply it. Reach for this whenever an async completion could apply out of order (a fetch, a
+generation call, a route resolution) — a fresh `#gen`/`#seq` field next to the async method, not
+a new home-grown class, is enough; there is no shared helper for this yet (opportunistic to add
+next to `createStore()` if a fourth call site needs it — none of the three above have been
+migrated onto one).

package/skills/app-audit/SKILL.md

@@ -2,15 +2,16 @@
 name: app-audit
 description: >-
   Diagnose an EXISTING AdiaUI consumer codebase before touching it — recon,
-  classify manifest/version/spec/capability drift, root-cause a wrong-output
-  symptom via four-layer triage (skill/codebase/substrate/spec) instead of
-  patching the surface. Use for "audit this UI", "what's wrong with X", "is
-  this up to date", "what should we migrate", "doesn't match the reference",
-  "renders unstyled/broken/off", or inheriting an @adia-ai/* consumer needing a
-  health check first. Produces a ranked, evidence-cited report; hands
-  CONFIRMED sweeps to a builder, never authors from an inferred plan. NOT
-  greenfield planning (app-planning); NOT confirmed migration
-  (app-migration); NOT browser QA (surface-qa).
+  classify manifest/version/spec/capability drift, root-cause a DRIFT-caused
+  wrong-output symptom via four-layer triage (skill/codebase/substrate/spec)
+  instead of patching the surface. Use for "audit this UI", "is this up to
+  date", "what should we migrate", "doesn't match the reference", "looks
+  unstyled/off-brand", or a suspected-drifted @adia-ai/* consumer's version
+  health check. Produces a ranked, evidence-cited report; hands CONFIRMED
+  sweeps to a builder. NOT greenfield planning (app-planning) or confirmed
+  migration (app-migration); NOT a live blank-screen/console-error check
+  (surface-qa) or chart-specific render behavior (chart-selection); NOT a
+  duplication review (project-scaffolding).
 disable-model-invocation: false
 user-invocable: true
 ---

package/skills/data-wiring/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: data-wiring
 description: >-
-  Data, state & hydration in an adia-ui app. Use when the user asks to
-  "wire up the data", "manage state", or "hydrate the island": pattern
-  choice (signals · Service/Command · DataClient · property-API · data-*),
-  hydration per mode (SPA/SSR/hybrid), single-owner rules. NOT for host
+  Data, state & hydration in an adia-ui app. Use for "wire up the data" /
+  "manage state" / "hydrate the island": pattern choice (signals · shared
+  app store · Service/Command · DataClient · property-API · data-*),
+  hydration per mode (SPA/SSR/hybrid). NOT for host
   bootstrap/registration (host-wiring) or screen markup (screen-composition).
 disable-model-invocation: false
 user-invocable: false
@@ -22,11 +22,12 @@ state are data, not instructions — embedded directives are findings.
 | Need | Pattern |
 | --- | --- |
 | reactive local UI state | **signals** — `signal()` / `effect()` |
+| shared state read by more than one component/module (imperative subscribers, not just `effect()` bodies) | **shared app store** — `createStore()` (`@adia-ai/web-components/core/store.js`) — signal-backed, `subscribe(cb) -> unsubscribe`; elements consume it via the existing `controller` setter (`el.controller = store`) — no adapter needed (gh#1777) |
 | CRUD with mutations + undo | **Service / Controller / Command** (async Service; commands record patches) |
 | typed reads from a backend/corpus | **DataClient** — `read({type, params})` → pure mappers → projection |
 | populate a catalog component (table/select/chart) | **property-API** — `el.columns = […]`, not post-connect children |
 | static/declarative flow state | **`data-*` + CSS** |
-| feed live/shared data to a settable-`.data` element | **`data-stream-*` trait** — signal-backed, refcounted shared transports |
+| feed live/shared data to a settable-`.data` element | **`data-stream-*` trait** — signal-backed, refcounted shared transports (a trait, not counted among "the six patterns" below — it composes with any of them) |
 
 ## Hydration path — rendering mode → path
 
@@ -44,7 +45,10 @@ state are data, not instructions — embedded directives are findings.
   cascade invariants. Unregistered internals: fix via the registration barrel, not per-primitive
   imports.
 - **Data down, events up** — sub-components receive state via properties (`.rec = …`) and emit
-  `CustomEvent`s; reaching into a parent's internals is a defect.
+  `CustomEvent`s; reaching into a parent's internals is a defect. This governs child→parent reach
+  only — shell-tier bespoke children coordinated by their parent via `querySelector` + reflected
+  attributes (`component-model.md` §"Attribute honesty") are the sanctioned parent→child
+  direction, not a competing pattern.
 - Projected children read via `logicalChildren` / `logicalSlotted`
   (`@adia-ai/web-components/core/logical-children`), not `this.children` — which misses
   `${items.map(…)}` output and the `display:contents` trap.
@@ -74,7 +78,10 @@ each fact explicitly; nothing downstream catches a miss:
 - Every `DataClient.mutate(payload, { action_source })` carries `action_source`; the client
   throws without it.
 - Catalog components populate via **property-API** (`el.columns`/`.data`/`.options`) — children
-  appended post-connect land outside the auto-stamped slots.
+  appended post-connect land outside the auto-stamped slots. This is a timing rule, not a ban on
+  `<option>` children outright: declaratively authored children present at parse time are one of
+  the two ratified multi-value encodings (ADR-0063 §Decision 3, `select`'s `options`/`<option>`
+  shape) — only the post-connect append is the defect.
 - **One reactive path** — updates flow through `signal()`/`effect()`; a parallel
   CustomEvent-only channel beside signals is a defect.
 - User-set state (mode/theme/view selector) survives unrelated sibling changes — auto-reset by
@@ -87,7 +94,8 @@ every row is complete, not that the screen merely renders.
 
 ```text
 Piece:            <state piece name>
-Pattern:          signals | Service/Command | DataClient | property-API | data-* | data-stream-*
+Pattern:          signals | shared-app-store | Service/Command | DataClient | property-API | data-*
+                  (+ data-stream-* trait, where the piece also feeds a settable-`.data` element)
 Owner:            <single owner — the file/component/route that owns it, never "shared">
 Hydration source: SPA self-boot | SSR seed→refresh | hybrid seed→island-boot
 Round-trip:       pass | fail — <mutate → signal update → UI reflects, console-clean?>
@@ -106,7 +114,16 @@ Facts checked:    projections-only[_] action_source[_] property-API[_] one-react
 ## Reference & boundaries
 
 - [`references/data-and-hydration.md`](../../references/data-and-hydration.md) — code shapes for
-  the five patterns, hydration paths, attribution rule, router-ui query-param pattern, and the
+  the six patterns (`data-stream-*` is a separate trait, documented in its own primitive doc, not
+  one of the six), hydration paths, attribution rule, router-ui query-param pattern, and the
   shared-drawer convention. Loads when a chosen pattern turns into code.
+- **Subscribe-delivery timing is not uniform** — synchronous snapshot on subscribe (plan-store) ·
+  asynchronous via `read().then()`, silently skipping the first delivery on a rejected read
+  (DataClient) · no delivery at all, notify-only (`createStore()`) — never assume which one a
+  given `subscribe()` call gives you; see
+  [`data-and-hydration.md`](../../references/data-and-hydration.md) §Subscribe-delivery timing.
+- **Supersede-token race control** — the shared last-write-wins idiom for an async completion
+  that could apply out of order (capture a token at start, compare before applying the result);
+  see [`data-and-hydration.md`](../../references/data-and-hydration.md) §Race control.
 - Host bootstrap, registration, routing → `host-wiring` · screen UI → `screen-composition` ·
   on-disk layout → `project-scaffolding` · render gate → `surface-qa`.

package/skills/data-wiring/evals/evals.json

@@ -10,6 +10,8 @@
     { "id": "t06", "prompt": "The state change isn't round-tripping through the signal — mutate doesn't update the projection", "expect": "trigger" },
     { "id": "t07", "prompt": "Seed the server-fetched props into this SPA island's client-boot state", "expect": "trigger" },
     { "id": "t08", "prompt": "The SSR framework already fetches the data — wire the initial props into the components", "expect": "trigger" },
+    { "id": "t09", "prompt": "Share this piece of state across two components that aren't in the same effect() tree", "expect": "trigger" },
+    { "id": "t10", "prompt": "Replace my hand-rolled pub/sub store with something that plugs into effect()/computed()", "expect": "trigger" },
     { "id": "n01", "prompt": "Register the client-side components for this new SPA host", "expect": "no-trigger", "owner": "host-wiring" },
     { "id": "n02", "prompt": "Getting 'HTMLElement is not defined' after upgrading to Next.js", "expect": "no-trigger", "owner": "host-wiring" },
     { "id": "n03", "prompt": "Manage the state for the streaming chat responses in the chat box", "expect": "no-trigger", "owner": "llm-wiring" },

package/skills/data-wiring/evals/routing-corpus.json

@@ -49,6 +49,20 @@
       "expected_shape": "crud-wiring",
       "rationale": "DataClient's read({type, params}) -> mappers -> projection shape is data-wiring's typed-read pattern."
     },
+    {
+      "id": "data-pattern-04",
+      "phrase": "share this piece of state across two components that aren't in the same effect() tree",
+      "expected": "data-wiring",
+      "expected_shape": "pattern-selection",
+      "rationale": "Shared state read by more than one component/module is the shared-app-store row's own trigger condition in the pattern-selection table (createStore(), gh#1761)."
+    },
+    {
+      "id": "data-pattern-05",
+      "phrase": "replace this hand-rolled Set-of-listeners pub/sub store with something signal-backed",
+      "expected": "data-wiring",
+      "expected_shape": "pattern-selection",
+      "rationale": "createStore() is exactly this migration target — the blessed replacement for a hand-rolled Set-of-listeners store (reactivity review R2)."
+    },
     {
       "id": "data-stream-01",
       "phrase": "feed live shared data to el.data using the property API",
@@ -143,14 +157,14 @@
     }
   ],
   "minimums_per_spec": {
-    "trigger_phrases": 14,
+    "trigger_phrases": 16,
     "adversarial_phrases": 6,
     "task_shapes_covered": "pattern-selection, hydration-path, section-wiring, ownership-audit, crud-wiring, data-stream-binding",
     "adversarial_fraction": "30%",
     "boundary_coverage": "at least 3 phrases exercise the data<->host fence in each direction (positives that mention SSR/hydration/island vocabulary yet correctly stay data; adversarials that mention data-ish verbs yet correctly route to host), plus the llm-wiring boundary (streaming chat state) and the screen-composition boundary (screen markup)."
   },
   "evaluator_notes": {
-    "current_state": "20 cases (14 trigger + 6 adversarial). Each of the 6 task shapes has at least 2 trigger cases; 3 of the 14 positives deliberately use host/SSR-adjacent vocabulary while remaining correctly data-routed, to exercise the data<->host fence from the 'sounds like host, is data' direction.",
+    "current_state": "22 cases (16 trigger + 6 adversarial). Each of the 6 task shapes has at least 2 trigger cases; 3 of the 16 positives deliberately use host/SSR-adjacent vocabulary while remaining correctly data-routed, to exercise the data<->host fence from the 'sounds like host, is data' direction. Two positives (data-pattern-04/05) added for gh#1761's shared-app-store row — the newest `pattern-selection` sub-case, not a distinct 7th task shape.",
     "promotion_criteria": "Promote to a CI gate (warn -> hard-fail) when F1 >= 0.85 on this corpus across 3+ consecutive runs without description edits.",
     "review_cadence": "Re-run on every data-wiring description edit. Add 1-2 new cases per checkpoint reflecting newly-observed routing failure modes.",
     "known_limitations": "The 'hydrate the island' phrasing is genuinely ambiguous in isolation (data-into-mounted-island vs mount-the-island-itself); this corpus resolves it by verb object (props/data/state -> data; register/mount/boot -> host), matching the two skills' own NOT-for clauses. A phrase with neither cue attached is not included \u2014 it would need file-path or app-state context the heuristic scorer doesn't see."

package/skills/domain-planning/evals/evals.json

@@ -0,0 +1,21 @@
+{
+  "skill": "domain-planning",
+  "note": "Trigger-routing suite (gh#1732, E6 coverage warn from the 2026-08-19 overhaul run). expect=trigger: the skill should fire on the prompt in a fresh session. expect=no-trigger: a near-miss owned elsewhere (owner named per case) or generic knowledge with no AdiaUI skill involved. Cases derived from evals/routing-corpus.json's phrases array (gh#1207 vetted corpus, with rationale) plus the SKILL.md description's own trigger/NOT-fence language.",
+  "cases": [
+    { "id": "t01", "prompt": "Walk the reasoning ladder on this PRD before any UI is chosen", "expect": "trigger" },
+    { "id": "t02", "prompt": "Derive the domain model — entities, roles, tasks, decisions — from this spec", "expect": "trigger" },
+    { "id": "t03", "prompt": "Resolve the intent and domain entities behind this product spec before we build anything", "expect": "trigger" },
+    { "id": "t04", "prompt": "Produce a Domain Plan block for the Orientation Record from this spec-shaped brief", "expect": "trigger" },
+    { "id": "t05", "prompt": "No Domain Plan exists yet for this PRD — reason through it first", "expect": "trigger" },
+    { "id": "t06", "prompt": "Score the semantic wireframe against the gate dimensions before composing", "expect": "trigger" },
+    { "id": "t07", "prompt": "Turn these user stories into roles, tasks, and decisions before picking components", "expect": "trigger" },
+    { "id": "t08", "prompt": "Here is the data schema — work out the domain entities and decisions the UI must serve", "expect": "trigger" },
+    { "id": "t09", "prompt": "This mockup is not signed off — validate the intent and tasks upward before accepting the component requests", "expect": "trigger" },
+    { "id": "t10", "prompt": "Identify the critical decisions and their required signals in this spec before any UI is chosen", "expect": "trigger" },
+    { "id": "n01", "prompt": "Compose the settings screen from the catalog primitives", "expect": "no-trigger", "owner": "screen-composition" },
+    { "id": "n02", "prompt": "The domain plan checkpoint passed — now compose the dashboard screen from the catalog", "expect": "no-trigger", "owner": "screen-composition" },
+    { "id": "n03", "prompt": "Cold-start orient in this repo — classify the four axes on cited signals and route onward", "expect": "no-trigger", "owner": "app-planning" },
+    { "id": "n04", "prompt": "Orient this repo — which shell and rendering mode does the brief imply", "expect": "no-trigger", "owner": "app-planning" },
+    { "id": "n05", "prompt": "Explain how CSS grid works", "expect": "no-trigger" }
+  ]
+}

package/skills/gen-ui-wiring/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: gen-ui-wiring
 description: >-
-  Authors a runtime generative-UI experience on the a2ui runtime — mounts a2ui-root/gen-root, wires generate_ui + data resolvers, grounds generation in a corpus. Use when END USERS generate UI at runtime. NOT for one-shot 'generate UI for X' screen asks (screen-composition), chat features (llm-wiring), or pipeline/MCP tool ops (adia-forge's a2ui-maintenance).
+  Authors a runtime generative-UI experience on the a2ui runtime — mounts a2ui-root/gen-root, wires generate_ui + data resolvers, grounds generation in a corpus (harvest chunks from our own pages, point retrieval at it). Use when END USERS generate UI at runtime. NOT for one-shot 'generate UI for X' screen asks (screen-composition), chat features (llm-wiring), or pipeline/MCP tool ops (adia-forge's a2ui-maintenance).
 disable-model-invocation: false
 user-invocable: true
 ---

package/skills/pattern-catalog/references/annotations.yaml

@@ -158,6 +158,19 @@
     - sparkline
     - metric tile
     - graph
+/packages/web-components/patterns/new-enrollments/new-enrollments.examples.html:
+  category: data-viz
+  intent: A "New enrollments" dashboard card recreated across four chart-type variants (stacked-bar, area, sparkline, radial-bar) sharing one header grammar, composing the Charts 2.0 foundations (chip labels, today-marker, provisional state, legend band).
+  keywords:
+    - new enrollments
+    - dashboard card
+    - stacked bar
+    - area chart
+    - sparkline
+    - radial bar
+    - provisional state
+    - today marker
+    - legend band
 /site/pages/patterns/charts.html:
   category: data-viz
   intent: Full live-demo reference for Charts 2.0 — all 18 chart-ui types, the ADR-0074 ratio grammar (auto-snap + explicit pin), chart-legend-ui's ratio-responsive row/grid/list layouts, the chart-in-card full-bleed pattern, and every ratified chart-ui attribute.
@@ -451,6 +464,16 @@
     - guided setup
     - progress
     - steps
+/packages/web-components/patterns/table-in-card/table-in-card.examples.html:
+  category: data-table
+  intent: The full table structural system in a card — header title/action, a title-less toolbar row, a bleed table, and a footer with a range label + pager — reach for it for any card-framed data grid that needs a pager.
+  keywords:
+    - data grid
+    - pagination
+    - table footer
+    - table toolbar
+    - status dot
+    - kebab actions
 /apps/overview.examples.html:
   category: app-overview
   intent: Index page cataloguing full-page AdiaUI example compositions — reach for it as a docs gallery landing that lists the available demo screens.

package/skills/pattern-catalog/references/pattern-index.md

@@ -4,7 +4,7 @@
 
 # Pre-assembled patterns & templates index
 
-169 reusable assembled surfaces: 48 patterns (composed component arrangements) and 121 template screens (full pages/flows). Search this file by category, keyword, or component tag BEFORE composing a surface from primitives. `source:` is the copyable markup; `docs:` is the live docs-site route (Gen-UI Feed is excluded — it demos gen-ui-wiring's runtime-generated pattern).
+171 reusable assembled surfaces: 50 patterns (composed component arrangements) and 121 template screens (full pages/flows). Search this file by category, keyword, or component tag BEFORE composing a surface from primitives. `source:` is the copyable markup; `docs:` is the live docs-site route (Gen-UI Feed is excluded — it demos gen-ui-wiring's runtime-generated pattern).
 
 ## Patterns
 
@@ -59,21 +59,29 @@
   - keywords: facet, chips, refine, narrow, segment, query
   - components: `action-item-ui` `tag-ui` `button-ui` `segment-ui` `card-ui` `row-ui` `action-list-ui` `code-ui` `popover-ui` `search-ui` `segmented-ui` `table-ui` `text-ui` `toolbar-ui`
   - source: `/packages/web-components/patterns/filter-bar/filter-bar.examples.html` · demo: `/packages/web-components/patterns/filter-bar/filter-bar.html` · docs: `/site/patterns/filter-bar`
+- **Table in Card** (Patterns) — The full table structural system in a card — header title/action, a title-less toolbar row, a bleed table, and a footer with a range label + pager — reach for it for any card-framed data grid that needs a pager.
+  - keywords: data grid, pagination, table footer, table toolbar, status dot, kebab actions
+  - components: `card-ui` `table-footer-ui` `table-toolbar-ui` `table-ui` `button-ui` `code-ui`
+  - source: `/packages/web-components/patterns/table-in-card/table-in-card.examples.html` · demo: `/packages/web-components/patterns/table-in-card/table-in-card.html` · docs: `/site/patterns/table-in-card`
 
 ### data-viz
 
 - **Chart in Card** (Patterns) — Embeds a chart inside a card so it reads as a dashboard tile — sparkline tile, full framed chart, or chart-plus-headline-stat.
   - keywords: dashboard tile, kpi tile, sparkline, metric tile, graph
-  - components: `card-ui` `chart-ui` `text-ui` `stat-ui` `chart-legend-ui` `segment-ui` `button-ui` `code-ui` `col-ui` `grid-ui` `segmented-ui`
+  - components: `card-ui` `chart-ui` `text-ui` `chart-legend-ui` `stat-ui` `segment-ui` `button-ui` `code-ui` `col-ui` `grid-ui` `segmented-ui`
   - source: `/packages/web-components/patterns/chart-in-card/chart-in-card.examples.html` · demo: `/packages/web-components/patterns/chart-in-card/chart-in-card.html` · docs: `/site/patterns/chart-in-card`
 - **Charts** (Patterns) — Full live-demo reference for Charts 2.0 — all 18 chart-ui types, the ADR-0074 ratio grammar (auto-snap + explicit pin), chart-legend-ui's ratio-responsive row/grid/list layouts, the chart-in-card full-bleed pattern, and every ratified chart-ui attribute.
   - keywords: chart types, ratio grammar, chart legend, full bleed, ADR-0074, data visualization
-  - components: `segment-ui` `chart-ui` `card-ui` `text-ui` `segmented-ui` `code-ui` `chart-legend-ui` `alert-ui` `grid-ui`
+  - components: `segment-ui` `chart-ui` `card-ui` `text-ui` `segmented-ui` `chart-legend-ui` `code-ui` `button-ui` `grid-ui` `row-ui` `select-ui` `alert-ui`
   - source: `/site/pages/patterns/charts.html` · docs: `/site/patterns/charts`
 - **Conversion Funnel** (Patterns) — Multi-step drop-off funnel built from labeled progress rows — reach for onboarding, checkout, activation, or paywall sequences.
   - keywords: drop-off, activation, checkout steps, sign-up flow, progress rows
   - components: `text-ui` `progress-ui` `col-ui` `badge-ui` `card-ui` `row-ui` `segment-ui` `button-ui` `segmented-ui`
   - source: `/packages/web-components/patterns/conversion-funnel/conversion-funnel.examples.html` · demo: `/packages/web-components/patterns/conversion-funnel/conversion-funnel.html` · docs: `/site/patterns/conversion-funnel`
+- **New Enrollments** (Patterns) — A "New enrollments" dashboard card recreated across four chart-type variants (stacked-bar, area, sparkline, radial-bar) sharing one header grammar, composing the Charts 2.0 foundations (chip labels, today-marker, provisional state, legend band).
+  - keywords: new enrollments, dashboard card, stacked bar, area chart, sparkline, radial bar, provisional state, today marker, legend band
+  - components: `button-ui` `card-ui` `chart-ui` `row-ui` `select-ui` `chart-legend-ui`
+  - source: `/packages/web-components/patterns/new-enrollments/new-enrollments.examples.html` · demo: `/packages/web-components/patterns/new-enrollments/new-enrollments.html` · docs: `/site/patterns/new-enrollments`
 - **Retention Cohort** (Patterns) — Retention cohort heatmap rendered as a table with color-bucketed badge cells — reach for it for retention/decay reporting.
   - keywords: heatmap, churn, decay, weekly buckets, engagement grid
   - components: `card-ui` `badge-ui` `table-ui` `text-ui` `stat-ui` `code-ui` `grid-ui` `row-ui`

package/skills/surface-qa/SKILL.md

@@ -1,11 +1,13 @@
 ---
 name: surface-qa
 description: >-
-  Browser-QA gate for adia-ui surfaces — renders headless with zero
-  console/page errors, non-zero bounding boxes, and a screenshot actually
-  read, plus AdiaUI a11y checks. Use when shipping a surface, on
-  "verify/QA this page", or when "tests pass" is the only evidence. NOT for
-  composing/fixing UI (screen-composition) or structural lint (adia-lint hook).
+  Browser-QA gate for a CONSUMER app's adia-ui surfaces — renders headless
+  with zero console/page errors, non-zero bounding boxes, and a screenshot
+  actually read, plus AdiaUI a11y checks. Use when shipping a surface, on
+  "verify/QA this page" or a page that renders blank/empty, or when "tests
+  pass" is the only evidence. NOT for composing/fixing UI (screen-composition),
+  structural lint (adia-lint hook), or the framework repo's own dogfood/
+  demo-page sweep (forge's demo-audit).
 disable-model-invocation: false
 user-invocable: true
 ---

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

@@ -176,8 +176,22 @@ they're documented alongside the real `sortFn`.
   it doesn't reduce total DOM churn across pages). For genuinely huge collections (1,000+ rows —
   chat threads, feeds, log streams), reach for `list-window-ui` instead, a different primitive
   that windows to only the visible slice; it is not table-shaped (no columns/header/sort), so it
-  fits a single-column list read, not a multi-column grid. Wire `[paginate]` with `[search]` and
-  the `page` event for server-driven pagination.
+  fits a single-column list read, not a multi-column grid. **Server-driven pagination (gh#1754,
+  ADR-0082)** — set `paginate="N"` (page size) TOGETHER with `range-total="M"` (the server's total
+  row count across all pages): `[paginate]` becomes purely presentational (no local slicing —
+  `.data` IS the current server page and renders whole, after any local search/sort/filter), the
+  internal pager's page count derives from `range-total`, and the existing `page` event (0-based)
+  becomes the fetch trigger — listen for it, fetch that server page, write the rows back to
+  `.data` (the page position holds; no reset) — **except** when a NEW `range-total` shrinks the
+  page count below the current page: `table-ui` clamps the RENDERED page to the last valid page
+  in that case (a render-time display clamp, never a `page` event dispatch — REQ-D-005), so a
+  consumer must not assume every server response preserves an out-of-range page. `range-total` is presence-gated: absent means
+  client mode (today's behavior); an explicit `range-total="0"` is server-confirmed empty, not
+  "not yet known." A bound `table-footer-ui` is optional chrome in this shape (it derives its own
+  range label from the table's `range-total` with zero footer attributes) — or omit the footer
+  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.
 
 ## table-toolbar-ui — the companion search/filter/sort/columns bar