@adia-ai/adia-ui-forge 0.8.36 → 0.8.38

package/skills/{adia-author → primitive-authoring}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill": "adia-author",
+  "skill": "primitive-authoring",
   "note": "Trigger-routing suite (gh#369). 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#355 vetted corpus) plus the SKILL.md description's own trigger/NOT-fence language.",
   "cases": [
     { "id": "t01", "prompt": "Add a new <toggle-ui> primitive component from scratch", "expect": "trigger" },
@@ -11,12 +11,12 @@
     { "id": "t07", "prompt": "Audit the four-axis contract for table-ui — token usage and lifecycle symmetry", "expect": "trigger" },
     { "id": "t08", "prompt": "Author a demo for the billing-overview composite, an examples.html", "expect": "trigger" },
     { "id": "t09", "prompt": "Add a pane behaviour to admin-shell per the bespoke shell-tier convention", "expect": "trigger" },
-    { "id": "n01", "prompt": "Compose this Figma mock into AdiaUI components for our consumer app", "expect": "no-trigger", "owner": "adia-compose" },
-    { "id": "n02", "prompt": "Cut a release of the next version and publish the npm packages", "expect": "no-trigger", "owner": "adia-release" },
-    { "id": "n03", "prompt": "Tune the zettel composition coverage, the eval is at 38%", "expect": "no-trigger", "owner": "adia-a2ui" },
-    { "id": "n04", "prompt": "Deploy the API service to the hosting platform", "expect": "no-trigger", "owner": "adia-deploy" },
-    { "id": "n05", "prompt": "The gemini adapter is dropping usage tokens on streamed responses", "expect": "no-trigger", "owner": "adia-llm-internals" },
-    { "id": "n06", "prompt": "Extend the LLM bridge in @adia-ai/llm to add a new provider", "expect": "no-trigger", "owner": "adia-llm-internals" },
+    { "id": "n01", "prompt": "Compose this Figma mock into AdiaUI components for our consumer app", "expect": "no-trigger", "owner": "screen-composition" },
+    { "id": "n02", "prompt": "Cut a release of the next version and publish the npm packages", "expect": "no-trigger", "owner": "package-release" },
+    { "id": "n03", "prompt": "Tune the zettel composition coverage, the eval is at 38%", "expect": "no-trigger", "owner": "a2ui-maintenance" },
+    { "id": "n04", "prompt": "Deploy the API service to the hosting platform", "expect": "no-trigger", "owner": "site-deployment" },
+    { "id": "n05", "prompt": "The gemini adapter is dropping usage tokens on streamed responses", "expect": "no-trigger", "owner": "llm-client-maintenance" },
+    { "id": "n06", "prompt": "Extend the LLM bridge in @adia-ai/llm to add a new provider", "expect": "no-trigger", "owner": "llm-client-maintenance" },
     { "id": "n07", "prompt": "Explain how React hooks work in general", "expect": "no-trigger" }
   ]
 }

package/skills/{adia-author → primitive-authoring}/evals/routing-corpus.json

@@ -1,155 +1,155 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "name": "adia-author routing accuracy corpus",
+  "name": "primitive-authoring routing accuracy corpus",
   "version": "2.1.0",
-  "purpose": "Routing-eval corpus for adia-author. Each phrase declares the skill (expected), a forbidden skill (expected_not, for phrases the source data only ever asserted as \"not this skill\"), or neither. Scored by scripts/skills/run-skill-evals.mjs (TF-IDF token overlap over per-skill description+triggers).",
+  "purpose": "Routing-eval corpus for primitive-authoring. Each phrase declares the skill (expected), a forbidden skill (expected_not, for phrases the source data only ever asserted as \"not this skill\"), or neither. Scored by scripts/skills/run-skill-evals.mjs (TF-IDF token overlap over per-skill description+triggers).",
   "scoring_notes": "Heuristic signal, not ground truth. Treat misroutes as a prompt to tighten the skill description, never as a reason to keyword-stuff it. Real harness routing is LLM-driven.",
-  "scope": "adia-author routing \u2014 does this phrase activate adia-author?",
+  "scope": "primitive-authoring routing \u2014 does this phrase activate primitive-authoring?",
   "phrases": [
     {
-      "id": "adia-author-pos-01",
+      "id": "primitive-authoring-pos-01",
       "phrase": "add a new button-ui primitive component",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-02",
+      "id": "primitive-authoring-pos-02",
       "phrase": "build a new <toggle-ui> component from scratch",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-03",
+      "id": "primitive-authoring-pos-03",
       "phrase": "create a new primitive web component in packages/web-components",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-04",
+      "id": "primitive-authoring-pos-04",
       "phrase": "add a new prop to table-ui",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-05",
+      "id": "primitive-authoring-pos-05",
       "phrase": "fix the CSS in card-ui to handle the new bleed variant",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-06",
+      "id": "primitive-authoring-pos-06",
       "phrase": "update the input-ui yaml to add a placeholder attribute",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-07",
+      "id": "primitive-authoring-pos-07",
       "phrase": "build the chat-shell composition with the new sidebar slot",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-08",
+      "id": "primitive-authoring-pos-08",
       "phrase": "author a new web-module shell at packages/web-modules/editor/editor-shell",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-09",
+      "id": "primitive-authoring-pos-09",
       "phrase": "add a pane behaviour to admin-shell per the bespoke shell-tier convention",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-10",
+      "id": "primitive-authoring-pos-10",
       "phrase": "promote this inline content to a shared web-modules module",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-11",
+      "id": "primitive-authoring-pos-11",
       "phrase": "this content keeps repeating across apps, extract to a shared module",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-12",
+      "id": "primitive-authoring-pos-12",
       "phrase": "lift this billing-summary block from apps/saas to web-modules",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-13",
+      "id": "primitive-authoring-pos-13",
       "phrase": "audit the four-axis contract for table-ui",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-14",
+      "id": "primitive-authoring-pos-14",
       "phrase": "check the token usage in card-ui for drift",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-15",
+      "id": "primitive-authoring-pos-15",
       "phrase": "lifecycle audit on dropdown-ui \u2014 symmetric connected/disconnected?",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-16",
+      "id": "primitive-authoring-pos-16",
       "phrase": "author a demo for the billing-overview composite",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-17",
+      "id": "primitive-authoring-pos-17",
       "phrase": "compose the examples.html for dashboard-layout",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-pos-18",
+      "id": "primitive-authoring-pos-18",
       "phrase": "write the demo for <integrations-page-ui> in packages/web-modules/settings",
-      "expected": "adia-author"
+      "expected": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-01",
+      "id": "primitive-authoring-neg-01",
       "phrase": "compose this Figma mock into AdiaUI components for our consumer app",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-02",
+      "id": "primitive-authoring-neg-02",
       "phrase": "cut a release of the next version and publish the npm packages",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-03",
+      "id": "primitive-authoring-neg-03",
       "phrase": "tune the zettel composition coverage; eval is at 38%",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-04",
+      "id": "primitive-authoring-neg-04",
       "phrase": "build a user profile card with avatar and edit actions",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-05",
+      "id": "primitive-authoring-neg-05",
       "phrase": "deploy the api service to the hosting platform",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-06",
+      "id": "primitive-authoring-neg-06",
       "phrase": "explain how React hooks work",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-07",
+      "id": "primitive-authoring-neg-07",
       "phrase": "the gemini adapter is dropping usage tokens on streamed responses",
-      "expected": "adia-llm-internals"
+      "expected": "llm-client-maintenance"
     },
     {
-      "id": "adia-author-neg-08",
+      "id": "primitive-authoring-neg-08",
       "phrase": "fix the openai stopReason mapping in the llm client",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-09",
+      "id": "primitive-authoring-neg-09",
       "phrase": "extend the LLM bridge to add a new provider",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-10",
+      "id": "primitive-authoring-neg-10",
       "phrase": "modify createAdapter in @adia-ai/llm to add chunk-shape support",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     },
     {
-      "id": "adia-author-neg-11",
+      "id": "primitive-authoring-neg-11",
       "phrase": "set up the LLM-bridge surface for a new tool-call provider",
-      "expected_not": "adia-author"
+      "expected_not": "primitive-authoring"
     }
   ],
   "_measured_historical": {

package/skills/{adia-author → primitive-authoring}/references/INDEX.md

@@ -1,4 +1,4 @@
-# adia-author references — retrieval map
+# primitive-authoring references — retrieval map
 
 One line per file: `path — the question it answers`. Load this first; load
 files on demand from it. Axes are topical (no severity ranking applies).
@@ -38,4 +38,4 @@ file, including the depth references those entries cross-link.
 
 ## Historical
 
-- [llm-bridge.md](llm-bridge.md) — superseded 2026-07-18 pointer: `@adia-ai/llm` internals belong to `adia-llm-internals`; kept only to redirect.
+- [llm-bridge.md](llm-bridge.md) — superseded 2026-07-18 pointer: `@adia-ai/llm` internals belong to `llm-client-maintenance`; kept only to redirect.

package/skills/{adia-author → primitive-authoring}/references/authoring-cycle.md

@@ -233,7 +233,7 @@ npm run verify:palette      # CVD thresholds across theme × scheme
 node -c path/to/new/file.js # JS syntax check
 ```
 
-The full release-side gate roster lives in the sibling **adia-release** skill; run its pre-flight sweep after any structural change.
+The full release-side gate roster lives in the sibling **package-release** skill; run its pre-flight sweep after any structural change.
 
 If a gate fails, fix before declaring done.
 

package/skills/{adia-author → primitive-authoring}/references/code-style.md

@@ -132,7 +132,7 @@ Static markup written by hand uses the components directly. UIs generated from i
 
 The runtime handles `createSurface` / `updateComponents` / `wireComponents` messages and binds `FormController` / `DataStreamController` controllers automatically. Don't roll your own message handler — the wiring lives in `@adia-ai/a2ui-runtime`.
 
-For multi-turn refinement, pass back `state_id` from prior responses so the engine can chain through `parent_state_id`. See the sibling **adia-a2ui** skill for the operator playbook.
+For multi-turn refinement, pass back `state_id` from prior responses so the engine can chain through `parent_state_id`. See the sibling **a2ui-maintenance** skill for the operator playbook.
 
 ## Two-block `@scope` CSS
 
@@ -316,7 +316,7 @@ Other deprecated forms swept in an early cut:
 - `'chat-submit'` event → `'submit'`
 - `<field-ui error="…">` → message moves to the slotted control
 
-For a wholesale consumer-side migration, use `adia-migrate` (adia-factory plugin) — it reads the MIGRATION GUIDE and runs the mechanical sweeps.
+For a wholesale consumer-side migration, use `app-migration` (adia-factory plugin) — it reads the MIGRATION GUIDE and runs the mechanical sweeps.
 
 ## Validate, always
 
@@ -328,7 +328,7 @@ For consumer markup (HTML pages, exemplars, training data), the checks are manua
 - Run the project's lint if applicable: `npx eslint <path>`.
 - Smoke the rendered output via `npm run dev` and load the touched page.
 
-For component source under `packages/web-components/components/**`, the gate is heavier — see [authoring-cycle.md](authoring-cycle.md) Step 5 + the full release-side gate roster in the sibling **adia-release** skill.
+For component source under `packages/web-components/components/**`, the gate is heavier — see [authoring-cycle.md](authoring-cycle.md) Step 5 + the full release-side gate roster in the sibling **package-release** skill.
 
 ## Cross-references
 
@@ -339,6 +339,6 @@ For component source under `packages/web-components/components/**`, the gate is
 - [token-contract.md](token-contract.md) — token audit procedure
 - [module-promotion.md](module-promotion.md) — promote inline → module
 - [anti-patterns.md](anti-patterns.md) — failure-mode catalogue with file:line refs
-- **adia-a2ui** (sibling skill) — generator / corpus / MCP pipeline
-- **adia-dogfood** (sibling skill) — cross-surface visual / static QA
+- **a2ui-maintenance** (sibling skill) — generator / corpus / MCP pipeline
+- **demo-audit** (sibling skill) — cross-surface visual / static QA
 - the **adia-factory** plugin — composition playbook for consumers building apps on the framework

package/skills/{adia-author → primitive-authoring}/references/common-gotchas.md

@@ -125,7 +125,7 @@ async #loadContent(route) {
 
 ## 7. Minting a wrapper-shaped component before its registry.js entry lands — site-a2ui silently deletes the node, not just mis-types it
 
-**Pattern**: a tag is gated first and only, for `*-ui` tags, by `packages/a2ui/runtime/registry.js`'s hand-maintained `registry` map — inverted into `reverseRegistry` at `transpiler-maps.js`'s module init, consulted first thing in `compose/transpiler/transpiler.js:149-150`. `registry.js` is hand-edited, not generated by `node scripts/build/components.mjs` (that script writes sidecars/prop-catalog data, consumed only for prop-extraction fidelity on tags the transpiler ALREADY resolved — `transpiler-maps.js:22-26`); a runtime `registerType()` call doesn't rescue a stale row either — `reverseRegistry` is a one-time init snapshot, not live. Regenerate a site-a2ui row for a demo using a component minted in the SAME change, before its `registry.js` line lands, and the tag falls through to `transpiler.js`'s "Unknown → Column" branch (line 180-183) — same mechanism as gh#535's toolbar-group breakage, which at least rendered visibly-wrong. A NEW component is usually wrapper-shaped (one child, author-defined attributes like `anchor="bottom"` the transpiler doesn't map to any real A2UI prop). That shape trips a SECOND, separate rule right after — "single-child container chains flatten" (`transpiler.js:282-285`): a retyped Column with exactly one child and zero recognized props is discarded outright, and its child is spliced directly into the PARENT's children in its place. The wrapper's own id and node are never pushed to the tree at all — not visible-but-wrong, just gone. The row is then internally self-consistent (content hash matches source) so `check:chunks-fresh`/`verify:site-a2ui` both report clean.
+**Pattern**: a tag is gated first and only, for `*-ui` tags, by `packages/gen-ui/a2ui/registry.js`'s hand-maintained `registry` map — inverted into `reverseRegistry` at `transpiler-maps.js`'s module init, consulted first thing in `compose/transpiler/transpiler.js:149-150`. `registry.js` is hand-edited, not generated by `node scripts/build/components.mjs` (that script writes sidecars/prop-catalog data, consumed only for prop-extraction fidelity on tags the transpiler ALREADY resolved — `transpiler-maps.js:22-26`); a runtime `registerType()` call doesn't rescue a stale row either — `reverseRegistry` is a one-time init snapshot, not live. Regenerate a site-a2ui row for a demo using a component minted in the SAME change, before its `registry.js` line lands, and the tag falls through to `transpiler.js`'s "Unknown → Column" branch (line 180-183) — same mechanism as gh#535's toolbar-group breakage, which at least rendered visibly-wrong. A NEW component is usually wrapper-shaped (one child, author-defined attributes like `anchor="bottom"` the transpiler doesn't map to any real A2UI prop). That shape trips a SECOND, separate rule right after — "single-child container chains flatten" (`transpiler.js:282-285`): a retyped Column with exactly one child and zero recognized props is discarded outright, and its child is spliced directly into the PARENT's children in its place. The wrapper's own id and node are never pushed to the tree at all — not visible-but-wrong, just gone. The row is then internally self-consistent (content hash matches source) so `check:chunks-fresh`/`verify:site-a2ui` both report clean.
 
 **Example**: minting `anchor-bar-ui` (gh#495, PR #569) and regenerating the `bulk-action-toolbar` pattern's site-a2ui row before the worktree's `registry.js` entry for it existed. Git-verified on the pre-fix commit (`ebf71832d`): `site-a2ui/pages/site__patterns__bulk-action-toolbar.a2ui.json` contains zero occurrences of `pat-bulk-float-bar` (the anchor-bar-ui's own authored id) anywhere — not retyped-and-visible, genuinely absent — while its single child (the toolbar content) survived, reparented one level up. `verify:site-a2ui` reported 321/321 clean.
 

package/skills/{adia-author → primitive-authoring}/references/llm-bridge.md

@@ -1,15 +1,15 @@
 # LLM Bridge extension — @adia-ai/llm
 
-**Superseded 2026-07-18 — `@adia-ai/llm` internals are `adia-llm-internals`'s charter, not
-`adia-author`'s.** That skill's references (`adapter-contract.md`, `streaming-sse.md`,
+**Superseded 2026-07-18 — `@adia-ai/llm` internals are `llm-client-maintenance`'s charter, not
+`primitive-authoring`'s.** That skill's references (`adapter-contract.md`, `streaming-sse.md`,
 `model-registry.md`, `bridge-facade.md`, `browser-proxy-boundary.md`, `add-a-provider.md`)
 are the current, maintained source — this file is kept only as a historical pointer and is
-no longer linked from `adia-author`'s task-shape table or `code-style.md`. Route provider/
-streaming/bridge work to `adia-llm-internals`.
+no longer linked from `primitive-authoring`'s task-shape table or `code-style.md`. Route provider/
+streaming/bridge work to `llm-client-maintenance`.
 
-Use when adding a 4th provider, modifying `createAdapter()`, changing the streaming chunk shape, or extending `packages/llm/server.js`.
+Use when adding a 4th provider, modifying `createAdapter()`, changing the streaming chunk shape, or extending `packages/llm/core/server.js`.
 
-This reference is about **modifying** the package. For day-to-day consumption (import + call), the README at `packages/llm/README.md` is sufficient.
+This reference is about **modifying** the package. For day-to-day consumption (import + call), the README at `packages/llm/core/README.md` is sufficient.
 
 ---
 
@@ -18,7 +18,7 @@ This reference is about **modifying** the package. For day-to-day consumption (i
 - Adding a new provider adapter (e.g., DeepSeek, Cohere, Mistral)
 - Changing `maxTokens`, `temperature`, or another bridge default
 - Extending the streaming chunk type set (currently: `text` / `thinking` / `done` / `error`)
-- Adding a new endpoint to `packages/llm/server.js`
+- Adding a new endpoint to `packages/llm/core/server.js`
 - Modifying the bridge's `complete()` / `stream()` shape
 - Debugging "why does my LLM call return truncated JSON?"
 
@@ -112,7 +112,7 @@ If you add a new endpoint, document it in the npm README under "Browser proxy mo
 
 ### Step 1: Create the adapter
 
-`packages/llm/adapters/<name>.js` exports a single object matching the shape used by anthropic / openai / gemini:
+`packages/llm/core/adapters/<name>.js` exports a single object matching the shape used by anthropic / openai / gemini:
 
 ```js
 import { readSSE } from './sse.js';
@@ -139,7 +139,7 @@ export const myProvider = {
 
 ### Step 2: Register in the facade
 
-Edit `packages/llm/adapters/index.js`:
+Edit `packages/llm/core/adapters/index.js`:
 
 ```js
 import { myProvider } from './myprovider.js';
@@ -154,7 +154,7 @@ function detectProvider(model) {
 
 ### Step 3: Subpath export
 
-Edit `packages/llm/package.json`:
+Edit `packages/llm/core/package.json`:
 
 ```json
 "exports": {
@@ -216,19 +216,19 @@ const DEFAULT_MODELS = {
 Run the smoke tests against the new provider:
 
 ```bash
-MYPROVIDER_API_KEY=*** node packages/a2ui/mcp/scripts/smoke-engine-registry.mjs
+MYPROVIDER_API_KEY=*** node packages/gen-ui/mcp/gen-ui/scripts/smoke-engine-registry.mjs
 ```
 
 Then run real-LLM eval at low intent count:
 
 ```bash
-LLM_PROVIDER=myprovider node packages/a2ui/mcp/scripts/eval-diff.mjs --semantic
+LLM_PROVIDER=myprovider node packages/gen-ui/mcp/gen-ui/scripts/eval-diff.mjs --semantic
 ```
 
 ## Pitfalls
 
-- **Two proxy shapes — `proxyUrl` is overloaded.** The bridge supports two architecturally different proxies and the dispatcher in `packages/llm/adapters/index.js` chooses between them by URL shape. Get this wrong and you get silent 401s in the browser even though `node packages/llm/server.js` works fine.
-  - **Smart proxy** (`packages/llm/server.js`, route `POST /api/chat`): accepts a **provider-neutral body** `{ provider, model, messages, ... }`, holds the API key server-side, and dispatches internally to the right adapter. Headers are just `content-type: application/json`.
+- **Two proxy shapes — `proxyUrl` is overloaded.** The bridge supports two architecturally different proxies and the dispatcher in `packages/llm/core/adapters/index.js` chooses between them by URL shape. Get this wrong and you get silent 401s in the browser even though `node packages/llm/core/server.js` works fine.
+  - **Smart proxy** (`packages/llm/core/server.js`, route `POST /api/chat`): accepts a **provider-neutral body** `{ provider, model, messages, ... }`, holds the API key server-side, and dispatches internally to the right adapter. Headers are just `content-type: application/json`.
   - **Passthrough proxy** (Vite dev `/api/llm/<provider>/<rest>` → real upstream URL `https://api.<provider>.com/<rest>`): expects the **real upstream body shape** (Anthropic-shaped for `/anthropic/`, OpenAI-shaped for `/openai/`, etc.) plus the **adapter's own auth headers** (`x-api-key` + `anthropic-version`, or `Authorization: Bearer …`). The proxy is dumb — it just rewrites the URL and forwards bytes.
   - Dispatcher: `chat()` and `streamChat()` in `adapters/index.js` call `isPassthroughProxy(proxyUrl)` (regex `/\/api\/llm\/[a-z]+(\/|$)/`). If true, they call `passthroughRequest()` which builds the real upstream body via `adapter.buildRequest()` then swaps in `proxyUrl`. If false, they call `proxyRequest()` with the provider-neutral body.
   - **When adding a new provider**, make sure: (1) `buildRequest()` omits the API key header when `proxyUrl` is the smart proxy (already handled), (2) `buildRequest()` _includes_ the API key header when called from `passthroughRequest()` (also already handled — passthroughRequest forwards adapter headers). The adapter's `buildRequest()` is the single source of truth for upstream-shape body + headers. Don't fork it for proxy mode.
@@ -246,7 +246,7 @@ After any extension:
 npm run check:lockstep         # @adia-ai/llm version must match the others
 npm run smoke:engines          # engines still register; pick still works
 npm run test:a2ui              # 22 pass / 0 fail / 1 skipped
-node packages/llm/server.js    # boots cleanly; .env auto-loads
+node packages/llm/core/server.js    # boots cleanly; .env auto-loads
 ```
 
 If you added a new SSE chunk type to the streaming protocol, verify all 7 consumers (chat-shell, generator.js, synthesis.js, eval-chunk-synthesis, eval-refine-synthesis, playgrounds/chat, apps/genui) still handle it correctly or fall through gracefully.
@@ -254,6 +254,6 @@ If you added a new SSE chunk type to the streaming protocol, verify all 7 consum
 ## Cross-references
 
 - [code-style.md](code-style.md) — general AdiaUI conventions (this is a specialty path; start there if you need broader context)
-- **adia-a2ui** (sibling skill) — generator / MCP / zettel synthesis (consumes the bridge)
+- **a2ui-maintenance** (sibling skill) — generator / MCP / zettel synthesis (consumes the bridge)
 - Spec: `.claude/docs/specs/package-architecture.md` § 11 (Phase 5 — engine registry)
-- README: `packages/llm/README.md` — consumer-facing docs
+- README: `packages/llm/core/README.md` — consumer-facing docs

package/skills/{adia-author → primitive-authoring}/references/module-promotion.md

@@ -119,7 +119,7 @@ The "stripped" consumer. Same structural change minus persistence.
 
 ### Phase 4 — Migrate the chunk corpus
 
-The harvested training-corpus chunk (`packages/a2ui/corpus/chunks/<name>.json`) embeds the consumer's HTML as an escaped string. Update it so the LLM sees the new authoring shape.
+The harvested training-corpus chunk (`packages/gen-ui/a2ui/corpus/chunks/<name>.json`) embeds the consumer's HTML as an escaped string. Update it so the LLM sees the new authoring shape.
 
 1. **Preferred** — re-run the harvester:
 
@@ -144,7 +144,7 @@ The harvested training-corpus chunk (`packages/a2ui/corpus/chunks/<name>.json`)
 3. **Defensive grep across all chunks** for the legacy markers:
 
    ```bash
-   grep -l 'id="<old-id>"' packages/a2ui/corpus/chunks/*.json
+   grep -l 'id="<old-id>"' packages/gen-ui/a2ui/corpus/chunks/*.json
    ```
 
 4. **Gotcha — hand-edit + later re-harvest** — if you used the fallback (step 2) AND a peer later adds your consumer's directory to harvester SOURCES, the next `harvest:chunks` run will overwrite your hand-edit with the live consumer HTML. Usually that's _good_ (the re-harvest captures the live state, including any post-edit consumer updates), but diff before assuming. Concrete example: theme-panel's `playground-app-shell.json` was hand-edited, then re-harvested after `playgrounds/` was added to SOURCES — the re-harvest captured the `<aside-ui>` → `<admin-sidebar>` bespoke conversion that the hand-edit missed.
@@ -159,7 +159,7 @@ The harvested training-corpus chunk (`packages/a2ui/corpus/chunks/<name>.json`)
 
 ### Phase 5 — Release
 
-Either ship as a standalone lockstep cut (per the sibling **adia-release** skill), OR ride a bundled cut that the user is already coordinating. Either way:
+Either ship as a standalone lockstep cut (per the sibling **package-release** skill), OR ride a bundled cut that the user is already coordinating. Either way:
 
 1. **CHANGELOGs** — `packages/web-modules/CHANGELOG.md` `[Unreleased]` (or the dated bump block if you're cutting now) + root `CHANGELOG.md`.
 2. **README** — `packages/web-modules/README.md`: cluster table row, Layout tree entry, Quick start `import` line.
@@ -265,7 +265,7 @@ apps/playgrounds/catalog layout.
 - [shell-patterns.md](shell-patterns.md) — bespoke shell-tier decomposition (ADR-0023; the _different_ activity)
 - [authoring-cycle.md](authoring-cycle.md) — the standard 5-step authoring cycle
 - [api-contract.md](api-contract.md) — prop naming, reflection, the legacy forms
-- **adia-release** (sibling skill) — lockstep release cycle (Phase 5)
-- **adia-a2ui** (sibling skill) — chunk corpus harvest + smoke gates (Phase 4)
+- **package-release** (sibling skill) — lockstep release cycle (Phase 5)
+- **a2ui-maintenance** (sibling skill) — chunk corpus harvest + smoke gates (Phase 4)
 - Spec: `.claude/docs/specs/package-architecture.md` — three-tier package layout
 - ADR-0012 / ADR-0023 — decision labels: primitives-vs-modules-vs-themes and the bespoke shell pattern (history lives in git + PR descriptions)

package/skills/{adia-author → primitive-authoring}/references/shell-patterns.md

@@ -532,8 +532,8 @@ When you encounter a legacy reference in old documentation or commit history, th
 ## After implementation
 
 1. Update this reference if you discover new pitfalls
-2. Cut a lockstep release using the sibling **adia-release** skill
-3. **When all consumers have migrated**, author the breaking-change migration recipe (adia-release owns the MIGRATION GUIDE) and cut a breaking release. Don't let the compat window outlive its usefulness.
+2. Cut a lockstep release using the sibling **package-release** skill
+3. **When all consumers have migrated**, author the breaking-change migration recipe (package-release owns the MIGRATION GUIDE) and cut a breaking release. Don't let the compat window outlive its usefulness.
 
 ## Anti-patterns specific to shells (deduplicated)
 

package/skills/{adia-author → primitive-authoring}/references/trait-pages.md

@@ -2,7 +2,7 @@
 
 Every trait detail page under `site/pages/traits/<name>/` follows one binding section template. The 41-page Phase B sweep proved what a loose contract produces: bimodal quality (portfolio-grade pages next to abstract-box demos) and zero pages teaching restraint. Navigate-by-template is the contract. Source: ADR-0019.
 
-Trait pages are this skill's charter (traits live in `packages/web-components/traits/`); `adia-site-docs` owns `site/pages/{architecture,getting-started,guides,patterns,reference}` — not `traits/`.
+Trait pages are this skill's charter (traits live in `packages/web-components/traits/`); `site-docs-authoring` owns `site/pages/{architecture,getting-started,guides,patterns,reference}` — not `traits/`.
 
 ## Required sections, in order
 

package/skills/{adia-author → primitive-authoring}/scripts/build-canonical-pattern-index.mjs

@@ -9,7 +9,7 @@
  * Run from the framework monorepo root (the dirs it scans — apps/, catalog/,
  * playgrounds/ — are monorepo roots):
  *
- *   node packages/plugins/adia-ui-forge/skills/adia-author/scripts/build-canonical-pattern-index.mjs
+ *   node packages/plugins/adia-ui-forge/skills/primitive-authoring/scripts/build-canonical-pattern-index.mjs
  *
  * The output `references/canonical-pattern-index.md` is checked in so agents
  * reading the skill always see the current state without running the script

package/skills/{adia-deploy → site-deployment}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: adia-deploy
+name: site-deployment
 description: >-
   Deploys and operates the AdiaUI site + services on exe.dev VMs — pushing a
   `site-v*` tag through the hardened rsync --delete deploy to ui-kit.exe.xyz
@@ -9,12 +9,12 @@ description: >-
   rotation. Use for "deploy to exe.dev", "push a site-v* tag", "the site is
   502ing / looks stale", "roll back the last deploy", "restart/diagnose the
   exe service", "rotate keys on the VM". NOT for cutting the release itself
-  (adia-release).
+  (package-release).
 disable-model-invocation: false
 user-invocable: true
 ---
 
-# adia-deploy
+# site-deployment
 
 Operates AdiaUI services on **exe.dev** — shared Linux VMs reached via
 `ssh <host>.exe.xyz`. Four playbooks: deploy an update, diagnose a down
@@ -47,7 +47,7 @@ Standard layout: `/srv/<app>/dist/` webroot (exedev-owned) ·
 
 ## Deploy-freshness cadence — a lockstep cut is not a site deploy
 
-`adia-release` cutting and publishing the lockstep version (the roster in
+`package-release` cutting and publishing the lockstep version (the roster in
 `scripts/package-paths.mjs` is the live count) does
 **not** itself update `ui-kit.exe.xyz` — that only happens on a `site-v*` tag
 push (see below). Any lockstep cut that changes a package the site actually
@@ -88,9 +88,9 @@ delete-adjudication classes.
 1. Build from clean, fully-merged `main`. In a fresh worktree,
    `npm run build -w @adia-ai/llm` runs **before** `build:site` — llm compiles
    at publish time and its outputs are gitignored, so without it
-   `/packages/llm/index.js` 404s and component registration breaks site-wide
+   `/packages/llm/core/index.js` 404s and component registration breaks site-wide
    (found live 2026-06-09).
-2. Dry-run `rsync -azni --delete --exclude='packages/a2ui/corpus/feedback/'`
+2. Dry-run `rsync -azni --delete --exclude='packages/gen-ui/a2ui/corpus/feedback/'`
    and bucket **every** `*deleting` line into a known-safe class; any
    unexplained served-content delete aborts the deploy. The exclude protects
    prod-only runtime-written files (feedback logs wiped 2026-06-10).

package/skills/{adia-deploy → site-deployment}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill": "adia-deploy",
+  "skill": "site-deployment",
   "note": "Trigger-routing suite (gh#369). 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#355 vetted corpus) plus the SKILL.md description's own trigger/NOT-fence language.",
   "cases": [
     { "id": "t01", "prompt": "Deploy the latest build to ui-kit.exe.xyz", "expect": "trigger" },
@@ -11,12 +11,12 @@
     { "id": "t07", "prompt": "Push a site-v* tag to deploy the current build, review the dry-run delete summary first", "expect": "trigger" },
     { "id": "t08", "prompt": "Did we deploy the site after the last lockstep cut, or is it behind npm?", "expect": "trigger" },
     { "id": "t09", "prompt": "Roll back the last site deploy, the new build is broken", "expect": "trigger" },
-    { "id": "n01", "prompt": "Cut a release of the next version and publish the npm packages", "expect": "no-trigger", "owner": "adia-release" },
-    { "id": "n02", "prompt": "Verify that this consumer app screen renders correctly before shipping", "expect": "no-trigger", "owner": "adia-verify" },
-    { "id": "n03", "prompt": "Add a new prop to button-ui", "expect": "no-trigger", "owner": "adia-author" },
-    { "id": "n04", "prompt": "Run a dogfood sweep on the demo pages", "expect": "no-trigger", "owner": "adia-dogfood" },
-    { "id": "n05", "prompt": "Tune the zettel retrieval coverage, the eval dropped to 38%", "expect": "no-trigger", "owner": "adia-a2ui" },
-    { "id": "n06", "prompt": "Why does accordion-ui crash under SSR in Astro?", "expect": "no-trigger", "owner": "adia-ssr" },
-    { "id": "n07", "prompt": "Fix the streaming adapter bug in the @adia-ai/llm package", "expect": "no-trigger", "owner": "adia-llm-internals" }
+    { "id": "n01", "prompt": "Cut a release of the next version and publish the npm packages", "expect": "no-trigger", "owner": "package-release" },
+    { "id": "n02", "prompt": "Verify that this consumer app screen renders correctly before shipping", "expect": "no-trigger", "owner": "surface-qa" },
+    { "id": "n03", "prompt": "Add a new prop to button-ui", "expect": "no-trigger", "owner": "primitive-authoring" },
+    { "id": "n04", "prompt": "Run a dogfood sweep on the demo pages", "expect": "no-trigger", "owner": "demo-audit" },
+    { "id": "n05", "prompt": "Tune the zettel retrieval coverage, the eval dropped to 38%", "expect": "no-trigger", "owner": "a2ui-maintenance" },
+    { "id": "n06", "prompt": "Why does accordion-ui crash under SSR in Astro?", "expect": "no-trigger", "owner": "ssr-compatibility" },
+    { "id": "n07", "prompt": "Fix the streaming adapter bug in the @adia-ai/llm package", "expect": "no-trigger", "owner": "llm-client-maintenance" }
   ]
 }