@adia-ai/adia-ui-factory 0.8.57 → 0.8.59

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-ui-kit-factory",
-  "version": "0.8.57",
+  "version": "0.8.59",
   "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.57",
+  "version": "0.8.59",
   "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.57", "gen-ui"]
+      "args": ["-y", "@adia-ai/mcp@0.8.59", "gen-ui"]
     }
   }
 }

package/CHANGELOG.md

@@ -1,5 +1,63 @@
 # Changelog — adia-ui-kit-factory
 
+## [0.8.59] — 2026-09-04
+
+### Added
+- **`scripts/adia-posture.d.mts`: ambient TypeScript types for `scripts/adia-posture.mjs` (gh#2875).** Lets `@adia-ai/mcp`'s factory server's new `scaffold_prototype` tool import `readPosture()` directly (the SAME reader `lab-posture-guard.mjs` uses) once vendored, without pulling the plain-JS module into that package's TypeScript build as a compiled input. No behavior change to `adia-posture.mjs` itself; see `@adia-ai/mcp`'s own CHANGELOG for the tool this enables.
+
+### Fixed
+- **`skills/pattern-catalog/references/pattern-index.md` regenerated after gh#2916's `dashboard-page-header` corpus-chunk rebuild reordered `dashboard-admin-page`'s components list.** Derived-only (`npm run build:factory-mcp-assets`), no source change in this package.
+
+### Changed
+- **`scripts/lint-rules.generated.mjs` (vendored lab-posture bank) regenerated after gh#2939's EXAMPLE-PROP-CONTRACT `data-*` exemption and GENUI-DOC-CONFLICT self-scope fix landed in the shared rule sources.** Derived-only, no source change in this package; the vendored bank picks up both predicate narrowings — full-corpus warn count 1413 → 1410 (see repo-root CHANGELOG.md for the gate's own detail).
+- **`scripts/lint-rules.generated.mjs` (vendored lab-posture bank) regenerated after gh#2937's `tagTree()` memoization landed in `scripts/lint/engine/primitives.mjs` (root).** Derived-only, no source change in this package; the vendored bank picks up the shared engine's single-slot memo, so the 48 generated `COMPOSITION-*` rules now share one tag-tree parse per file instead of each re-parsing it — full golden-corpus `check:lint-efficacy`: 110.9s → 9.45s. Byte-identical rule semantics (38/38 seeded-fixture catch rate, 0 error-severity across 438 files, unchanged).
+- **`scripts/lint-rules.generated.mjs` (vendored lab-posture bank) regenerated to carry `enum_meta` tier data for gh#2831 batch 2's 9 components** (feed-item-ui, inline-message-ui, link-ui, loading-overlay-ui, mark-ui, menu-item-ui, nav-group-ui, nav-item-ui, nav-ui). Derived-only, no source change in this package; the vendored bank follows the yaml `enum_meta` authored in `@adia-ai/web-components`.
+- **`scripts/lint-rules.generated.mjs` (vendored lab-posture bank) regenerated to carry `enum_meta` tier data for gh#2831 batch 3's 13 components (FINAL batch)** (pagination-ui, preview-ui, rating-ui, select-ui, shader-texture-ui, spinner-ui, table-toolbar-ui, tabs-ui, tag-ui, text-ui, timeline-item-ui, toast-ui, toggle-scheme-ui). Derived-only, no source change in this package; the vendored bank follows the yaml `enum_meta` authored in `@adia-ai/web-components`. Closes the 31-component sweep (gh#2831).
+
+### Maintenance
+- **`.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.
+
+## [0.8.58] — 2026-09-02
+
+### Added
+- **Lab posture: `.adia` marker, manifest-derived lint rules, and a blocking `PreToolUse` write-time hook (ADR-0108 D1/D5, LLD-0019 C3-C5, gh#2856).** New `Posture` README section documents the `.adia` marker schema (`{ "posture": "lab" | "bare-repo", "kit"?: { "web-components": "<version>" } }`) and `scripts/adia-posture.mjs`'s `readPosture(repoRoot)` reader, posture is explicit, never inferred from `package.json`/`node_modules`. New `lab-posture-guard` hook (`PreToolUse`, `Write|Edit`): in lab posture, denies a write containing an unknown tag/attribute/enum value or an `internal`-tier value (the same four rules, `UNKNOWN-TAG`/`UNKNOWN-ATTR`/`ENUM-VALUE`/`INTERNAL-TIER`, imported straight from this plugin's own vendored `lint-rules.generated.mjs`, never a second matcher implementation), with the violating tag/attr/value and the manifest's allowed set in the deny reason; a no-op in bare-repo/absent posture, `adia-lint`'s existing advisory `PostToolUse` contract is completely unchanged. New `SessionStart` hook warms the manifest cache once per session. Reads a lab consumer's LIVE installed manifest via a new dependency-free `adia-manifest-lite.mjs` (JSON-only: none of the four rules needs `a2ui.rules`, so no vendored yaml parser required for this path), cached per-session by `adia-manifest-cache.mjs` under the OS temp dir (never a tracked repo artifact). Hook integration selftest (`npm run check:lab-posture-guard-selftest`) builds two tmp-dir fixture consumer repos (lab / bare-repo, mirroring `get-manifest.test.js`'s own fixture-building pattern rather than committing a real `.a2ui.json` fixture, which would trip `adia-ui-forge`'s `sidecar-prewrite-guard`) and asserts an unknown-tag write is denied in lab and allowed bare-repo, plus clean/enum/internal-tier/unknown-attr/non-markup cases. Non-Claude harnesses (Codex/Hermes/Pi) get no hook runtime, see the README's "Non-Claude harnesses" section for the `npm run lint`-at-`warn` degradation. Hooks roster: 1 → 2 (site's `factory-plugin.html` roster page updated, `check:plugin-count-claims` guards it).
+
+### Changed
+- **`adia-scaffold spa`'s `_SPA_JS`/`_SPA_HTML` templates register only the tags the placeholder markup uses (page-ui, text-ui) via per-component JS + CSS imports, instead of the full `@adia-ai/web-components` / `@adia-ai/web-components/css` barrel (ADR-0107, gh#2765).** The generated app's `dist/` shrinks from ~39MB / 9,092 files (barrel JS + the full Phosphor icon glob) to ~272KB / 3 files, JS gzip 430KB→7.7KB, CSS gzip drops similarly, measured against this checkout's own `packages/web-components`. The barrel stays fully supported: the template's own header comment documents the two-line kitchen-sink opt-in (`import '@adia-ai/web-components'` + `/css`) for consumers who want zero-config registration of every primitive. Scaffolded SPAs now also get a `README.md` with a "Bundle cost" section stating this trade-off, the icon-subsetting `installIconLoaders()` path, and the kitchen-sink opt-in.
+- **`selftest`'s `_resolve_export` wildcard-match tie-break fixed to match Node's own exports-resolution specificity rule** (prefix+suffix length, not prefix length alone), the old tie-break could resolve a `.css`-suffixed subpath against the wrong same-prefix wildcard key (e.g. `./components/*` instead of the more specific `./components/*.css`), which the previous templates never exercised but the new per-component CSS imports do.
+
+### Fixed
+- **Pi `ui-architect` self-test now re-execs with Node's explicit TypeScript-stripping flag on early Node 22 patch releases (gh#2803).** Direct and npm-script invocations can import `ui-architect.extension.ts` across the supported Node 22 major instead of depending on the later patch that enabled type stripping by default.
+- **ATTR-TYPO/LLM-KEY-IN-CLIENT/NATIVE-PRIMITIVE matcher hardening (gh#2708)**, propagated to this plugin's vendored `scripts/lint-rules.generated.mjs` via `npm run build:lint-rules`, byte-identical to the shared lint-rule bank, no change to `adia-lint.mjs`'s own CLI contract.
+
+### Docs
+- **`scripts/lint-rules.generated.mjs` (vendored lab-posture bank) regenerated to carry `enum_meta` tier data for gh#2831 batch 3's 13 components** (pagination-ui, preview-ui, rating-ui, select-ui, shader-texture-ui, spinner-ui, table-toolbar-ui, tabs-ui, tag-ui, text-ui, timeline-item-ui, toast-ui, toggle-scheme-ui). Derived-only, no source change in this package; the vendored bank follows the yaml `enum_meta` authored in `@adia-ai/web-components`. Closes the 31-component sweep (gh#2831).
+- **generated lint-rule bank refreshed (gh#2821, gh#2824)**: a full `npm run build:lint-rules` regen pass, run while rebasing the heatmap/noodles a11y fixes onto main, picked up `enum_meta` `tier`/`when` data already landed upstream (gh#2864) that this vendored copy hadn't caught up to yet; vendored copy byte-identical to the shared bank, no behavior change.
+- **generated lint-rule bank refreshed (gh#2845)**: `gen-composition-rules.mjs`'s scan widened from `<dirname>.yaml` only to every `*.yaml` in a component directory, discovering 14 previously-missed child/sub-item yamls; composition-rule count 34 → 48 (mechanics: repo-root CHANGELOG.md); vendored copy byte-identical to the shared bank, no behavior change.
+- **generated lint-rule bank refreshed (gh#2801)**: `gen-composition-rules.mjs`'s eligibility widened from 1 to 34 generated composition rules, decoupled from component.md pilot status (mechanics: repo-root CHANGELOG.md); vendored copy byte-identical to the shared bank, no behavior change.
+- **generated lint-rule bank refreshed** by wave-5A component.md eligibility regen (lld-0018).
+- **generated lint-rule bank refreshed** by wave-5B component.md eligibility regen (lld-0018).
+- **generated lint-rule bank refreshed**: wave-1A component.md eligibility added 3 composition rules (accordion/action-list/choice-card, lld-0018).
+- **pattern-catalog `pattern-index.md` regenerated** for the header-ui→header sweep (gh#2793).
+- **pattern-catalog `pattern-index.md` regenerated** for the admin-page-header pattern entry's admin-scroll→page-scroll wrapper swap (gh#2734).
+- **`pattern-catalog/SKILL.md`'s ADR-0084 forward note gains a build-status update (gh#2736).** The generated `templates/` npm mirror generator has landed (`@adia-ai/web-components`'s CHANGELOG carries the mechanics); this note records that the `ships:`/resolution-table flip is a separate, not-yet-built wave.
+- **ADR-0098 drain: remaining admin-page prose in `references/shell-admin.md`, `skills/app-audit/references/gap-classes.md`, and `skills/screen-composition/assets/figma-make/guidelines/components.md` rewritten to `<page-ui band>`.** These three still described the retired `<admin-page>`/`<admin-page-header>`/`<admin-page-body>` triad as the current admin-shell chrome pattern, the canonical skeleton example, the chrome-tier allocation table, a gotcha row on the "without inner column-owner" failure mode, and the Figma-Make shells vocabulary/skeleton all now show `<page-ui band>` with `<header-ui>`/`<section-ui>` children. `demo-audit/references/admin-shell-anatomy.md`, `demo-audit/references/app-shell-pitfalls.md`, and `primitive-authoring/references/shell-patterns.md` were checked and already carry correct dated ADR-0098 deprecation notes from an earlier harvest, no change needed there.
+- **`pattern-catalog/references/pattern-index.md` + `annotations.yaml` updated for `admin-page-header.html`'s ADR-0098 rewrite (gh#2748).** The docs-site pattern page itself moved off the deprecated `<admin-page-header>`/`<admin-page>`/`<admin-page-body>` triad onto `<page-ui band>`'s direct `<header-ui>` child (root `CHANGELOG.md` carries the page-rewrite detail); `annotations.yaml`'s `admin-page-header.html` entry intent/keywords updated to name `page-ui band` instead of `admin-page`, and `pattern-index.md` regenerated (`npm run build:patterns-index`) picks up the entry's `components:` list dropping `admin-page`/`admin-page-body`/`admin-page-header`/`alert-ui` for `page-ui`.
+- **`pattern-catalog/references/pattern-index.md` regenerated (`npm run build:patterns-index`, gh#2730).** `patterns-form-drawer`'s `components:` list re-sorts after gh#2730's label-variant sweep collapsed `form-drawer.examples.html`'s `field-ui[inline]`-wrapping-`switch-ui` anti-pattern to the switch's own `[label]` attribute, shifting the extracted tag order.
+- **ADR-0098 knowledge-harvest applied to `shell-selection/SKILL.md`.** The "Canonical nesting" verify-target row gains a dated deprecation note (2026-09-01) pointing the `admin-page`/`admin-scroll` nesting example at its successor, `page-ui[band]` nested inside `page-scroll`.
+- **`pattern-catalog/references/pattern-index.md` regenerated (`npm run build:patterns-index`, gh#2706).** The "Admin Shell" and "Admin Content Aside" pattern entries' `components:` lists still named `admin-page`/`admin-page-header`/`admin-page-body`/`admin-scroll`, their source demo (`packages/web-components/patterns/admin-shell/admin-shell.examples.html`) had been missed by the earlier ADR-0098 sweep; now byte-resynced to `page-scroll`/`page-ui[band]` after the source migration.
+- **ADR-0084 knowledge-harvest applied to `pattern-catalog/SKILL.md`.** The "Reach the source" section's "none of them a template screen" `ships:` claim gains a dated forward-note (2026-09-01) recording ADR-0084's ruled `templates/` npm-mirror plan for all 121 template screens (Class R, build-at-publish); the 6 `/site/pages/patterns/` docs-hub pages stay `monorepo-only` permanently either way.
+- **ADR-0102 harvest: `surface-qa/references/verification.md:62`'s superseded heading-role workaround corrected.** The Accessibility checklist row recommending `role="heading"` + `aria-level` or an `<h*>` wrapper for a `text-ui variant="heading"` node now points at `text-ui[level]` (1-6, promotes to a real native `<h1>`-`<h6>`) as the current fix, citing ADR-0102 (2026-09-01); `variant` stays presentational-only, `level` is the tag-promoting prop.
+
+### Chore
+- **Author email in `package.json` updated to `kim.granlund@adia.ai`** (was a stale personal address).
+
+### Maintenance
+- **`.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.
+- **`adapters/` touched in this release window** (1 file(s), e.g. `claude/hooks.json`) — carried by the entries above.
+
 ## [0.8.57] — 2026-09-01
 
 ### Fixed

package/README.md

@@ -96,6 +96,58 @@ surface-qa-agent) · `component-model.md` · the `references/contracts/` twins.
 
 `adia-lint` — PostToolUse advisory consumer-smell repair loop (selftest ships).
 
+`lab-posture-guard` — PreToolUse (`Write|Edit`) blocking guard, active only
+in lab posture (see Posture, below); a no-op in bare-repo/absent posture,
+leaving `adia-lint`'s existing advisory contract completely unchanged. A
+`SessionStart` hook warms its manifest cache once per session; selftest
+ships (`npm run check:lab-posture-guard-selftest`).
+
+## Posture
+
+Two postures a consumer repo can declare (ADR-0108, LLD-0019 §C3): **bare-repo**
+(ADR-0040, the default — this plugin working standalone with no monorepo
+path assumptions) and **lab** (ADR-0108 — a repo that installs
+`@adia-ai/web-components` at root, pinned, and scaffolds prototypes that
+consume those root packages directly as app source). Posture is an
+EXPLICIT marker, never inferred from `package.json` or `node_modules` —
+that inventory-only question ("what's installed") is `adia-info`'s
+separate probe, not a declared-intent signal.
+
+A repo-root `.adia` JSON file declares posture:
+
+```json
+{
+  "posture": "lab",
+  "kit": { "web-components": "9.9.9" }
+}
+```
+
+- `posture` — `"lab"` or `"bare-repo"`, required when the file exists. An
+  explicit `"bare-repo"` value is accepted alongside the file's plain
+  absence — both read as bare-repo behavior — so a repo can affirmatively
+  opt OUT of lab posture in its own marker rather than relying on absence
+  alone.
+- `kit` — optional. When present, `kit["web-components"]` records the
+  installed `@adia-ai/web-components` version the marker was written
+  against — informational only; nothing in this plugin reads it yet.
+- Missing file, unparseable JSON, or a missing/unrecognized `posture`
+  value all resolve to bare-repo behavior — the permissive branch. A
+  corrupt marker must never accidentally turn ON the stricter lab-posture
+  enforcement below.
+
+`scripts/adia-posture.mjs` (`readPosture(repoRoot)` → `'lab' | 'bare-repo' |
+'absent'`) is the one reader both `lab-posture-guard` and a future
+`scaffold_prototype` (LLD-0019 §C6, not shipped yet) key on.
+
+**In lab posture**, `lab-posture-guard` validates every `Write`/`Edit`
+against the installed manifest's tags, attributes, and declared enum
+values (`UNKNOWN-TAG`/`UNKNOWN-ATTR`/`ENUM-VALUE`/`INTERNAL-TIER`) and
+DENIES a violating write before it lands, naming the offending
+tag/attr/value and the manifest's allowed set in the deny reason so the
+agent can self-correct. **In bare-repo or absent posture**, this hook is a
+complete no-op — `adia-lint`'s existing `PostToolUse` advisory contract is
+the only signal, unchanged.
+
 ## Commands
 
 `/project-scaffolding` · `/app-planning` · `/surface-qa` · `/app-migration` · `/find-unused` · `/gen-ui-wiring` · `/app-audit` · `/theme-audit`
@@ -111,7 +163,7 @@ attributes vs. the shipped component contracts), and `adia-theme-audit.mjs`
 
 ## MCP
 
-`adia-gen-ui` server pinned: `@adia-ai/mcp@0.8.57` (tool SoT:
+`adia-gen-ui` server pinned: `@adia-ai/mcp@0.8.59` (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`,
@@ -136,6 +188,22 @@ plain Node script with no Claude-specific runtime dependency; the
 Hermes, and becomes a genuine `prompts/theme-audit.md` Pi command via
 `build:harness-manifests`.
 
+**Lab posture's write-time enforcement (ADR-0108 D5/D6) is a Claude Code-only
+guarantee** — `AGENTS.md`'s own "Non-Claude harnesses" section states plainly
+that none of Codex, Hermes, or Pi has a manifest key for `hooks/`, and none
+has a hook runtime a `PreToolUse` deny could wire into, so `lab-posture-guard`
+simply does not run on any of the three. They degrade to `npm run lint` in
+the monorepo (or the equivalent vendored `adia-lint`/lint-bank invocation in
+a consumer repo) picking up the same four manifest-derived rules
+(`UNKNOWN-TAG`/`UNKNOWN-ATTR`/`ENUM-VALUE`/`INTERNAL-TIER`, ADR-0108 D5) at
+`warn` severity — after the fact, at lint/check time, rather than before the
+write lands. `get_manifest` reachability without the hook is not uniform
+either: Codex reaches it through its plain `.mcp.json` passthrough; Hermes
+needs its `hermes-mcp.yaml` fragment hand-merged into `~/.hermes/config.yaml`;
+Pi has no native MCP support at all, so a Pi session without the third-party
+`pi-mcp-adapter` gets neither the manifest nor the lint-time signal until a
+`npm run check`/`npm run lint` pass runs.
+
 - **Codex** (gh#1888): `.codex-plugin/plugin.json` + per-skill
   `agents/openai.yaml`, derived; `mcpServers` points at the same
   `.mcp.json` Claude Code uses. No manifest key for hooks/commands/agents —

package/hermes-mcp.yaml

@@ -6,5 +6,5 @@ mcp_servers:
     command: "npx"
     args:
       - "-y"
-      - "@adia-ai/mcp@0.8.57"
+      - "@adia-ai/mcp@0.8.59"
       - "gen-ui"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-factory",
-  "version": "0.8.57",
+  "version": "0.8.59",
   "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",
@@ -14,7 +14,7 @@
   "license": "MIT",
   "author": {
     "name": "Kim",
-    "email": "kim@sublimeheroics.com"
+    "email": "kim.granlund@adia.ai"
   },
   "bugs": {
     "email": "kim.granlund@adia.ai"

package/plugin.yaml

@@ -1,4 +1,4 @@
 name: "adia-ui-kit-factory"
-version: "0.8.57"
+version: "0.8.59"
 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."
 manifest_version: 1

package/references/shell-admin.md

@@ -11,7 +11,7 @@ Full SaaS/admin chrome from `@adia-ai/web-modules`. Register the **cluster barre
 
 ## Cluster roster
 
-`<admin-shell>` (host coordinator) · `<admin-sidebar>` (resizable/collapsible, `slot="leading"|"trailing"`) · `<admin-command>` (Cmd+K palette) · `<admin-content>` (center column) · `<admin-topbar>` / `<admin-statusbar>` (chrome bars, shared slots) · `<admin-scroll>` (vertical scroll container) · `<admin-page>` + `<admin-page-header>` / `<admin-page-body>` / `<admin-page-footer>` (the page; header/footer sticky, body scrolls) · `<admin-entity-item>` (icon+label+badge identity row). Three are JS-bearing (shell, sidebar, command); the rest are CSS-only structure.
+`<admin-shell>` (host coordinator) · `<admin-sidebar>` (resizable/collapsible, `slot="leading"|"trailing"`) · `<admin-command>` (Cmd+K palette) · `<admin-content>` (center column) · `<admin-topbar>` / `<admin-statusbar>` (chrome bars, shared slots) · `<admin-scroll>` (vertical scroll container) · `<page-ui band>` + `<header-ui>` / `<section-ui>` / `<footer-ui>` (the page; header/footer always-sticky with border+background, body scrolls) · `<admin-entity-item>` (icon+label+badge identity row). Three are JS-bearing (shell, sidebar, command); the rest are CSS-only structure.
 
 ## Canonical skeleton
 
@@ -29,10 +29,10 @@ Full SaaS/admin chrome from `@adia-ai/web-modules`. Register the **cluster barre
       <breadcrumb-ui slot="heading">…</breadcrumb-ui>
     </admin-topbar>
     <admin-scroll>
-      <admin-page>
-        <admin-page-header slot="header"><header-ui><span slot="heading">Page</span></header-ui></admin-page-header>
-        <admin-page-body slot="body"><section-ui>…</section-ui></admin-page-body>
-      </admin-page>
+      <page-ui band max-width="xwide" padding="10">
+        <header-ui><span slot="heading">Page</span></header-ui>
+        <section-ui>…</section-ui>
+      </page-ui>
     </admin-scroll>
     <admin-statusbar slot="footer"><span>Status</span></admin-statusbar>
   </admin-content>
@@ -69,14 +69,14 @@ the command palette, the statusbar). Page-tier content is *per-route* — it cha
 |---|---|---|---|
 | Shell sidebar | `<admin-sidebar slot="leading">` | primary nav; brand in `slot="header"`; **user-account controls only** in `slot="footer"` | app-wide preference toggles (scheme/theme) |
 | Shell topbar | `<admin-topbar>` in `<admin-content>` | sidebar-toggle + **breadcrumb** (location); trailing cluster = **persistent global controls** (theme, notifications, command trigger) | page title, page CTAs, dataset search |
-| Page header | `<admin-page-header>` | **page title `<h1>`** + page-scoped CTAs (`+ New`, `Export`) via `slot="action"` | location chrome |
-| Page body | `<admin-page-body>` | the page's primary content | — |
+| Page header | `<header-ui>` inside `<page-ui band>` | **page title `<h1>`** + page-scoped CTAs (`+ New`, `Export`) via `slot="action"` | location chrome |
+| Page body | `<section-ui>` inside `<page-ui band>` | the page's primary content | — |
 | Table toolbar | `<table-toolbar-ui>` adjacent to `<table-ui>` | in-page search/filter/sort scoped to the table | — |
 | Statusbar | `<admin-statusbar slot="footer">` | app-wide status (sync, row count, version) | — |
 
 **The four allocation anti-patterns** (each silently breaks the model, no warning):
 
-- ❌ **Page CTA (`+ New Claim`) in the shell topbar** → it sticks across every route and never updates. Page CTAs go in `<admin-page-header>`.
+- ❌ **Page CTA (`+ New Claim`) in the shell topbar** → it sticks across every route and never updates. Page CTAs go in the `<header-ui>` inside `<page-ui band>`, via `slot="action"`.
 - ❌ **Page title (`<h1>`) in the topbar** instead of a breadcrumb → the topbar carries *location*; the breadcrumb's terminal segment IS the page title.
 - ❌ **Dataset-search input in the topbar** → a search scoped to one dataset belongs in `<table-toolbar-ui>`, not the app-wide topbar.
 - ❌ **Scheme/theme toggle in the sidebar footer** → it reads as nav and vanishes when the sidebar collapses. App-wide preferences belong in the topbar trailing cluster.
@@ -88,16 +88,16 @@ SPA mounts the full markup. SSR keeps the shell + chrome fixed and swaps only th
 ## Gotchas (mechanized where noted)
 
 - **Piecemeal import** → `AdminSidebar`/`AdminCommand` unregistered; `.toggle()/.show()` undefined. Import the barrel.
-- **Wrapping shell children in `<col-ui>`/`<row-ui>`** → breaks the grid (it reads tag selectors). Generics go _inside_ `admin-content`/`admin-page-body`.
-- **Raw `<header>` vs `<header-ui>` inside `<admin-page-header>`**: always use `<header-ui>`. The shell CSS targets `admin-page-header > :is(header, header-ui)` identically for geometry (css/admin-shell.templates.css:39), but only `<header-ui>` has the shadow DOM that routes `slot="heading"` / `slot="description"` / `slot="icon"` / `slot="action"` children — a raw `<header>` matches the CSS rhythm but silently drops every named slot.
+- **Wrapping shell children in `<col-ui>`/`<row-ui>`** → breaks the grid (it reads tag selectors). Generics go _inside_ `admin-content`/`page-ui`'s `<section-ui>`.
+- **Raw `<header>` vs `<header-ui>` inside `<page-ui band>`**: prefer `<header-ui>`. `page-ui`'s `@scope` rules target both `<header>` and `<header-ui>` identically for geometry, but only `<header-ui>` has the shadow DOM that routes `slot="heading"` / `slot="description"` / `slot="icon"` / `slot="action"` children — a raw `<header>` matches the layout rhythm but silently drops every named slot.
 - **`[resizable]` without a child `<div data-sidebar-resize>`** → no drag handle.
 - **Hardcoded `[collapsed]`** → won't auto-clear on resize; use `.collapse()/.expand()`.
-- **Multiple `<admin-page>` in one `<admin-scroll>`** → single-axis scroll breaks; one page per scroll.
+- **Multiple `<page-ui>` in one `<admin-scroll>`** → single-axis scroll breaks; one page per scroll.
 - **`@container (…)` instead of `@container page-content (…)`** → won't react to sidebar collapse.
 - **Legacy shapes** (`<aside data-sidebar>`, `<dialog data-command>`) — retired v0.4.0 (`adia-lint` `LEGACY-SHELL`).
 - **Sidebar nav is `<nav-ui>` + `<nav-item-ui>`**, never `<menu-ui>`/`<menu-item-ui>` — menu-ui is for Popover-API dropdowns, not persistent navigation.
 - **Full-height mount:** an intermediate wrapper (`<main id="app">`) between `body { height: 100dvh; display: flex }` and the shell needs `flex: 1; display: flex; min-height: 0` — without it the flex chain breaks and the shell collapses to content height.
-- **`header-ui` has no CSS of its own** — its icon/heading/description/action grid comes from the parent's `@scope` (`admin-page-header` provides it); bespoke chrome reusing the header-ui vocabulary must supply the grid + text ellipsis locally.
+- **`header-ui` has no CSS of its own** — its icon/heading/description/action grid comes from the parent's `@scope` (`page-ui` provides it); bespoke chrome reusing the header-ui vocabulary must supply the grid + text ellipsis locally.
 - **A persistent `<drawer-ui data-mobile-nav-drawer>` is always in the DOM** (relocated mobile-nav mechanism, gh#1984/ADR-0090), not conditionally created — only its visibility responds to a container query at the shell's mobile-nav breakpoint. A selector assuming exactly one `drawer-ui`/`dialog` on the page (e.g. an E2E test) must scope past it: `drawer-ui:not([data-mobile-nav-drawer])`.
 
 Real usage: `apps/saas/app/admin-dashboard/`.

package/scripts/adia-manifest-cache.mjs

@@ -0,0 +1,77 @@
+/**
+ * adia-manifest-cache.mjs — ADR-0108 D6 / LLD-0019 C4: the session-scoped
+ * manifest cache the lab-posture write-time hook reads instead of calling
+ * `get_manifest` over MCP at write time. A hook invocation is a fresh Node
+ * process every time (no in-memory persistence across PreToolUse calls),
+ * so "cache built once per session" is realized as a small file under the
+ * OS temp dir, keyed by the hook event's `session_id` when the harness
+ * supplies one (every refresh call from a new session gets a fresh file —
+ * LLD-0019 §C4's own "refreshes once per session" contract) and falling
+ * back to a `repoRoot`-only key when it doesn't (a run outside a hook
+ * event, e.g. this module's own tests) — LLD-0019 R-2/OQ-2 already name
+ * mid-session staleness as an accepted, unsolved risk; this cache's own
+ * "session-keyed when possible" behavior does not attempt to solve it,
+ * only to match the design's stated refresh point as closely as a
+ * stateless-process hook can.
+ *
+ * Never a tracked repo artifact (LLD-0019 §Data: "generated, session-
+ * scoped, not committed... never classified R or C").
+ */
+import { existsSync, mkdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { createHash } from 'node:crypto';
+import { tmpdir } from 'node:os';
+import { join } from 'node:path';
+import { readManifestLite } from './adia-manifest-lite.mjs';
+
+const CACHE_DIR_NAME = 'adia-lab-posture-manifest-cache';
+
+function cacheKey(repoRoot, sessionId) {
+  const basis = sessionId ? `session:${sessionId}` : `repo:${repoRoot}`;
+  return createHash('sha256').update(basis).digest('hex').slice(0, 32);
+}
+
+function cachePath(repoRoot, sessionId) {
+  return join(tmpdir(), CACHE_DIR_NAME, `${cacheKey(repoRoot, sessionId)}.json`);
+}
+
+/** Reads the cached manifest for this `(repoRoot, sessionId)` pair, if
+ * any. Returns `null` on a cache miss or an unreadable/corrupt cache file
+ * — a miss is the caller's cue to refresh (§refreshManifestCache), never a
+ * crash. */
+export function readManifestCache(repoRoot, sessionId) {
+  const path = cachePath(repoRoot, sessionId);
+  if (!existsSync(path)) return null;
+  try {
+    const parsed = JSON.parse(readFileSync(path, 'utf8'));
+    return parsed?.manifest ?? null;
+  } catch {
+    return null;
+  }
+}
+
+/** Builds a fresh manifest from `repoRoot`'s installed `node_modules`
+ * (`adia-manifest-lite.mjs`) and writes it to the session cache. Returns
+ * the manifest (or `null` when `@adia-ai/web-components` is not
+ * installed — a lab-posture repo missing its own root install, distinct
+ * from "no cache yet"). */
+export function refreshManifestCache(repoRoot, sessionId) {
+  const manifest = readManifestLite(repoRoot);
+  const path = cachePath(repoRoot, sessionId);
+  mkdirSync(join(tmpdir(), CACHE_DIR_NAME), { recursive: true });
+  writeFileSync(path, JSON.stringify({ repoRoot, builtAt: new Date().toISOString(), manifest }));
+  return manifest;
+}
+
+/** Cache-or-refresh: the one entry point both the hook and a SessionStart
+ * warm call use. Never returns stale-by-construction data — a hit returns
+ * exactly what the last refresh in this session wrote; a miss refreshes
+ * inline before returning (LLD-0019 D6: "a write attempted before [the
+ * refresh] has completed denies against an empty cache the same way an
+ * unknown tag would" — this function IS that refresh, so by the time it
+ * returns, the cache is never empty except when the consumer repo truly
+ * has no installed manifest). */
+export function getOrBuildManifest(repoRoot, sessionId) {
+  const cached = readManifestCache(repoRoot, sessionId);
+  if (cached) return cached;
+  return refreshManifestCache(repoRoot, sessionId);
+}

package/scripts/adia-manifest-lite.mjs

@@ -0,0 +1,137 @@
+/**
+ * adia-manifest-lite.mjs — ADR-0108 D6 / LLD-0019 C2, C4: a small,
+ * dependency-free reader of a CONSUMER repo's installed
+ * `node_modules/@adia-ai/web-components` (+ `@adia-ai/web-modules`)
+ * manifest, scoped to exactly what the lab-posture write-time hook
+ * (lab-posture-guard.mjs, LLD-0019 C4) needs: `{ tag, attrs: [{ name,
+ * values?: [{ value, tier }] }] }` per component — the same shape
+ * `unknownTagFindings`/`unknownAttrFindings`/`enumValueFindings`/
+ * `internalTierFindings` (this plugin's vendored lint-rules.generated.mjs,
+ * ADR-0108 D5) already expect.
+ *
+ * WHY A SECOND READER, NOT packages/gen-ui/mcp/factory/manifest.js's
+ * `getManifest` DIRECTLY: that module lives in the `@adia-ai/mcp` package
+ * tree, reachable inside THIS monorepo checkout via a relative import, but
+ * NOT present at all once this plugin is installed standalone into a lab
+ * consumer repo (ADR-0108's actual deployment target) — `@adia-ai/mcp` is
+ * not a dependency of `@adia-ai/adia-ui-factory` (this plugin ships
+ * self-contained, vendored scripts, no npm dependency on sibling
+ * packages). The narrower scope also means this reader needs NO yaml
+ * parsing at all: `getManifest`'s one yaml-only field is `a2ui.rules`
+ * (packages/gen-ui/mcp/factory/manifest.ts's own header explains why:
+ * `components.mjs` never forwards it onto the `.a2ui.json` sidecar), and
+ * none of the four lab-posture rules reads `rules` — every field they DO
+ * need (`tag`, attr names, enum `value`/`tier` pairs) already lives in the
+ * sidecar's plain JSON `properties`/`x-adiaui` blocks. So this reader is a
+ * pure `JSON.parse` walk, no vendored yaml-lite parser needed for the hook
+ * path (gh#2856 Open Question 5's other half, resolved: the GENERATOR
+ * reads in-tree yaml via manifest.ts's `buildManifestFromRoots`; the HOOK
+ * reads a consumer's installed JSON sidecars via this file — two readers,
+ * same shape, deliberately different dependency footprints for their two
+ * different execution contexts).
+ */
+import { existsSync, readFileSync, readdirSync, statSync } from 'node:fs';
+import { join } from 'node:path';
+
+function resolvePackageRoot(repoRoot, pkgName) {
+  const root = join(repoRoot, 'node_modules', ...pkgName.split('/'));
+  return existsSync(join(root, 'package.json')) ? root : null;
+}
+
+function listSubdirs(dirPath) {
+  if (!existsSync(dirPath)) return [];
+  return readdirSync(dirPath).filter((name) => {
+    try {
+      return statSync(join(dirPath, name)).isDirectory();
+    } catch {
+      return false;
+    }
+  });
+}
+
+function listSidecarsInDir(dirPath) {
+  let files;
+  try {
+    files = readdirSync(dirPath);
+  } catch {
+    return [];
+  }
+  return files.filter((f) => f.endsWith('.a2ui.json')).map((f) => join(dirPath, f));
+}
+
+function buildAttrs(sidecar, includeInternal) {
+  const props = sidecar.properties ?? {};
+  const attrs = [];
+  for (const [name, meta] of Object.entries(props)) {
+    if (meta.const !== undefined) continue; // the `component` discriminator — not an author-facing attribute
+    const attr = { name };
+    if (Array.isArray(meta.enum) && meta.enum.length) {
+      const enumMeta = meta.enum_meta ?? {};
+      attr.values = meta.enum
+        .map((v) => {
+          const key = String(v);
+          const tier = enumMeta[key]?.tier;
+          return tier ? { value: key, tier } : { value: key };
+        })
+        .filter((v) => includeInternal || v.tier !== 'internal');
+    }
+    attrs.push(attr);
+  }
+  return attrs;
+}
+
+function readOneComponent(sidecarPath, includeInternal) {
+  let sidecar;
+  try {
+    sidecar = JSON.parse(readFileSync(sidecarPath, 'utf8'));
+  } catch {
+    return null; // an unreadable sidecar must never crash the hook — treated as "not in the manifest"
+  }
+  const tag = sidecar['x-adiaui']?.tag;
+  if (!tag) return null;
+  return { tag, attrs: buildAttrs(sidecar, includeInternal) };
+}
+
+function readComponentsDir(componentsDir, includeInternal) {
+  const out = [];
+  for (const dirName of listSubdirs(componentsDir)) {
+    for (const sidecarPath of listSidecarsInDir(join(componentsDir, dirName))) {
+      const c = readOneComponent(sidecarPath, includeInternal);
+      if (c) out.push(c);
+    }
+  }
+  return out;
+}
+
+const WEB_MODULES_NON_CLUSTER_DIRS = new Set(['dist', 'node_modules']);
+
+function readWebModulesComponents(wmRoot, includeInternal) {
+  const out = [];
+  for (const clusterName of listSubdirs(wmRoot)) {
+    if (WEB_MODULES_NON_CLUSTER_DIRS.has(clusterName)) continue;
+    const clusterDir = join(wmRoot, clusterName);
+    for (const compositeName of listSubdirs(clusterDir)) {
+      for (const sidecarPath of listSidecarsInDir(join(clusterDir, compositeName))) {
+        const c = readOneComponent(sidecarPath, includeInternal);
+        if (c) out.push(c);
+      }
+    }
+  }
+  return out;
+}
+
+/**
+ * Reads `{ components: [{ tag, attrs }] }` from `repoRoot`'s installed
+ * `@adia-ai/web-components` (+ `@adia-ai/web-modules` when present).
+ * Returns `null` when `@adia-ai/web-components` is not installed —
+ * callers treat that the same as "no manifest cached yet" (LLD-0019 C4's
+ * own "deny against an empty cache" contract), never a crash.
+ */
+export function readManifestLite(repoRoot, { includeInternal = true } = {}) {
+  const wcRoot = resolvePackageRoot(repoRoot, '@adia-ai/web-components');
+  if (!wcRoot) return null;
+  const components = readComponentsDir(join(wcRoot, 'components'), includeInternal);
+  const wmRoot = resolvePackageRoot(repoRoot, '@adia-ai/web-modules');
+  if (wmRoot) components.push(...readWebModulesComponents(wmRoot, includeInternal));
+  return { components };
+}

package/scripts/adia-posture.d.mts

@@ -0,0 +1,11 @@
+/** Ambient types for adia-posture.mjs (vendored alongside it into the
+ * factory MCP package, gh#2875) — lets a TypeScript consumer
+ * (packages/gen-ui/mcp/factory/tools/factory.ts) import the plain-JS module
+ * for types without pulling it into the program as a compiled INPUT, same
+ * outDir/rootDir emit-collision avoidance as yaml-lite.d.mts.
+ */
+export function readPostureMarker(repoRoot: string): { posture: 'lab' | 'bare-repo'; kit?: { 'web-components'?: string } } | null;
+
+export function readPosture(repoRoot: string): 'lab' | 'bare-repo' | 'absent';
+
+export function isLabPosture(repoRoot: string): boolean;

package/scripts/adia-posture.mjs

@@ -0,0 +1,81 @@
+/**
+ * adia-posture.mjs — ADR-0108 D1 / LLD-0019 C3: reads a repo's `.adia`
+ * posture marker. The ONE thing both the lab-posture write-time hook
+ * (lab-posture-guard.mjs, LLD-0019 C4) and a future `scaffold_prototype`
+ * (LLD-0019 C6, ticket 6, out of scope here) check — posture is an
+ * EXPLICIT declared marker, never inferred from `package.json` or
+ * `node_modules` (that's `adia-info`'s separate inventory probe, a
+ * different question: "what's installed", not "what posture is
+ * declared" — ADR-0108 D1's own rejected-alternative note).
+ *
+ * MARKER SHAPE (gh#2856 Open Question 1, resolved — broader than
+ * ADR-0108 D1's own minimal `{ "posture": "lab" }`):
+ *   { "posture": "lab" | "bare-repo", "kit"?: { "web-components": "<installed version>" } }
+ * `posture` is required; an explicit `"bare-repo"` value is accepted
+ * alongside plain absence (both read as bare-repo behavior, ADR-0040
+ * unchanged) so a repo can affirmatively opt OUT of lab posture in its own
+ * marker file rather than relying on the file's absence alone — useful for
+ * a repo that once ran lab posture and deliberately reverted. `kit` is
+ * optional: when present, `kit["web-components"]` records the installed
+ * `@adia-ai/web-components` version the marker was written against (a
+ * version-drift signal for a human or a future `scaffold_prototype`
+ * refresh check — LLD-0019 C3 left this open, this ticket resolves it as
+ * informational only; nothing in this ticket's build reads it yet).
+ *
+ * Malformed marker handling: missing file, unparseable JSON, missing/
+ * unrecognized `posture` value all resolve to `'bare-repo'` — the
+ * PERMISSIVE branch — never `'lab'`. A corrupt marker must never
+ * accidentally turn ON the stricter PreToolUse deny hook (ADR-0108 D5); a
+ * corrupt marker silently falling back to advisory-only bare-repo
+ * behavior is the safe failure direction. `'absent'` is reported
+ * separately from `'bare-repo'` only for callers that want to distinguish
+ * "no marker at all" from "marker present, explicitly bare-repo" — both
+ * behave identically everywhere in this plugin today.
+ */
+import { existsSync, readFileSync } from 'node:fs';
+import { join } from 'node:path';
+
+const MARKER_FILENAME = '.adia';
+const RECOGNIZED_POSTURES = new Set(['lab', 'bare-repo']);
+
+/**
+ * Reads and validates the raw `.adia` marker at `repoRoot`. Returns the
+ * parsed object when the file exists, is valid JSON, and carries a
+ * recognized `posture` value; returns `null` in every other case
+ * (absent, unreadable, malformed JSON, or an unrecognized `posture`).
+ * Never throws.
+ */
+export function readPostureMarker(repoRoot) {
+  const path = join(repoRoot, MARKER_FILENAME);
+  if (!existsSync(path)) return null;
+  let raw;
+  try {
+    raw = JSON.parse(readFileSync(path, 'utf8'));
+  } catch {
+    return null;
+  }
+  if (!raw || typeof raw !== 'object' || Array.isArray(raw)) return null;
+  if (!RECOGNIZED_POSTURES.has(raw.posture)) return null;
+  return raw;
+}
+
+/**
+ * Returns `'lab'`, `'bare-repo'`, or `'absent'` for `repoRoot` — the one
+ * signal LLD-0019 C4 (the write-time hook) and any future C6
+ * (`scaffold_prototype`) key on. A malformed or unreadable marker resolves
+ * to `'bare-repo'`, not `'absent'` — see the module header's "malformed
+ * marker handling" note for why the distinction stops there.
+ */
+export function readPosture(repoRoot) {
+  const path = join(repoRoot, MARKER_FILENAME);
+  if (!existsSync(path)) return 'absent';
+  const marker = readPostureMarker(repoRoot);
+  if (!marker) return 'bare-repo';
+  return marker.posture;
+}
+
+/** `true` only when `readPosture(repoRoot)` is exactly `'lab'` — the
+ * single boolean the write-time hook (LLD-0019 C4) gates on. */
+export function isLabPosture(repoRoot) {
+  return readPosture(repoRoot) === 'lab';
+}