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

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/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,11 +1,11 @@
 # 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`.
 
@@ -216,13 +216,13 @@ 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/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/mcp/gen-ui/scripts/eval-diff.mjs --semantic
 ```
 
 ## Pitfalls
@@ -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

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

@@ -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

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" }
   ]
 }

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

@@ -1,125 +1,125 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "name": "adia-deploy routing accuracy corpus",
+  "name": "site-deployment routing accuracy corpus",
   "version": "2.1.0",
-  "purpose": "Routing-eval corpus for adia-deploy. 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 site-deployment. 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-deploy routing \u2014 does this phrase activate adia-deploy?",
+  "scope": "site-deployment routing \u2014 does this phrase activate site-deployment?",
   "phrases": [
     {
-      "id": "adia-deploy-pos-01",
+      "id": "site-deployment-pos-01",
       "phrase": "deploy the latest build to ui-kit.exe.xyz",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-02",
+      "id": "site-deployment-pos-02",
       "phrase": "push the dist folder to the VM",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-03",
+      "id": "site-deployment-pos-03",
       "phrase": "diagnose why the site returns Port 8000 unbound",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-04",
+      "id": "site-deployment-pos-04",
       "phrase": "the site is throwing a 502, check the VM service",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-05",
+      "id": "site-deployment-pos-05",
       "phrase": "restart the adia-ui service on the exe.dev VM",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-06",
+      "id": "site-deployment-pos-06",
       "phrase": "provision a fresh exe.dev VM for a new host",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-07",
+      "id": "site-deployment-pos-07",
       "phrase": "rotate the API keys on the production VM",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-08",
+      "id": "site-deployment-pos-08",
       "phrase": "push a site-v* tag to deploy the current build",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-09",
+      "id": "site-deployment-pos-09",
       "phrase": "the site looks stale, new fixtures are 404ing",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-10",
+      "id": "site-deployment-pos-10",
       "phrase": "check the dry-run delete summary before the deploy job runs",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-11",
+      "id": "site-deployment-pos-11",
       "phrase": "did we deploy the site after the last lockstep cut, or is it behind npm",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-pos-12",
+      "id": "site-deployment-pos-12",
       "phrase": "roll back the last site deploy, the new build is broken",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-01",
+      "id": "site-deployment-neg-01",
       "phrase": "cut a release of the next version and publish the npm packages",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-02",
+      "id": "site-deployment-neg-02",
       "phrase": "verify that this consumer app screen renders correctly before shipping",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-03",
+      "id": "site-deployment-neg-03",
       "phrase": "add a new prop to button-ui",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-04",
+      "id": "site-deployment-neg-04",
       "phrase": "run a dogfood sweep on the demo pages",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-05",
+      "id": "site-deployment-neg-05",
       "phrase": "tune the zettel retrieval coverage, eval dropped to 38%",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-06",
+      "id": "site-deployment-neg-06",
       "phrase": "publish the npm packages for the next lockstep cut",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-07",
+      "id": "site-deployment-neg-07",
       "phrase": "author the release notes and the migration guide",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-08",
+      "id": "site-deployment-neg-08",
       "phrase": "why does accordion-ui crash under SSR in Astro",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-09",
+      "id": "site-deployment-neg-09",
       "phrase": "fix the streaming adapter bug in the llm package",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-10",
+      "id": "site-deployment-neg-10",
       "phrase": "review the getting-started docs page for consistency",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     },
     {
-      "id": "adia-deploy-neg-11",
+      "id": "site-deployment-neg-11",
       "phrase": "score the gen-ui gallery outputs for this cycle",
-      "expected_not": "adia-deploy"
+      "expected_not": "site-deployment"
     }
   ],
   "_measured_historical": {

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

@@ -270,7 +270,7 @@ Common failures:
 
 Add new hosts here as they come online.
 
-## Hand-off from adia-release
+## Hand-off from package-release
 
-Release engineering (`adia-release`) builds and publishes artifacts; this
+Release engineering (`package-release`) builds and publishes artifacts; this
 playbook owns the deploy step that pushes them to the VM.

package/skills/{adia-site-docs → site-docs-authoring}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: adia-site-docs
+name: site-docs-authoring
 description: >-
   Review or author pages under site/pages/{architecture,getting-started,
   guides,patterns,reference}/ — the docs site (count the pages on disk; it
@@ -7,14 +7,14 @@ description: >-
   or edit a getting-started/architecture/guides/patterns/reference page,
   review a site docs page for consistency, fix a callout that reads as plain
   text, or explain why an inline-code chip or a demo gallery looks broken.
-  NOT for a component's own .examples.html demo (adia-author) or any
+  NOT for a component's own .examples.html demo (primitive-authoring) or any
   pure-primitive-composition training-harvest page (governed by
-  composition-and-examples.md's no-style-block rule; owner: adia-a2ui).
+  composition-and-examples.md's no-style-block rule; owner: a2ui-maintenance).
 disable-model-invocation: false
 user-invocable: true
 ---
 
-# adia-site-docs
+# site-docs-authoring
 
 Every page under `site/pages/{architecture,getting-started,guides,patterns,
 reference}/` shares one skeleton: `<header><h1>` + a deck `<p>`, then numbered

package/skills/{adia-site-docs → site-docs-authoring}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill": "adia-site-docs",
+  "skill": "site-docs-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": "Review this site docs page for consistency with the others", "expect": "trigger" },
@@ -10,11 +10,11 @@
     { "id": "t06", "prompt": "Create a reference page documenting the MCP tools", "expect": "trigger" },
     { "id": "t07", "prompt": "Audit site/pages/guides for the same callout bug we found elsewhere", "expect": "trigger" },
     { "id": "t08", "prompt": "What's the shared skeleton every site docs page should follow?", "expect": "trigger" },
-    { "id": "n01", "prompt": "Review this component's own demo gallery in its .examples.html file", "expect": "no-trigger", "owner": "adia-author" },
-    { "id": "n02", "prompt": "Fix this gen-ui training exemplar page under site/pages/examples", "expect": "no-trigger", "owner": "adia-a2ui" },
-    { "id": "n03", "prompt": "Tune the zettel retrieval threshold for the chunk corpus", "expect": "no-trigger", "owner": "adia-a2ui" },
-    { "id": "n04", "prompt": "Add a new prop to the button-ui primitive", "expect": "no-trigger", "owner": "adia-author" },
-    { "id": "n05", "prompt": "Cut the next npm release for the 9 @adia-ai packages", "expect": "no-trigger", "owner": "adia-release" },
-    { "id": "n06", "prompt": "Deploy the docs site to ui-kit.exe.xyz", "expect": "no-trigger", "owner": "adia-deploy" }
+    { "id": "n01", "prompt": "Review this component's own demo gallery in its .examples.html file", "expect": "no-trigger", "owner": "primitive-authoring" },
+    { "id": "n02", "prompt": "Fix this gen-ui training exemplar page under site/pages/examples", "expect": "no-trigger", "owner": "a2ui-maintenance" },
+    { "id": "n03", "prompt": "Tune the zettel retrieval threshold for the chunk corpus", "expect": "no-trigger", "owner": "a2ui-maintenance" },
+    { "id": "n04", "prompt": "Add a new prop to the button-ui primitive", "expect": "no-trigger", "owner": "primitive-authoring" },
+    { "id": "n05", "prompt": "Cut the next npm release for the 9 @adia-ai packages", "expect": "no-trigger", "owner": "package-release" },
+    { "id": "n06", "prompt": "Deploy the docs site to ui-kit.exe.xyz", "expect": "no-trigger", "owner": "site-deployment" }
   ]
 }