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

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

@@ -1,130 +1,130 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "name": "adia-site-docs routing accuracy corpus",
+  "name": "site-docs-authoring routing accuracy corpus",
   "version": "2.1.0",
-  "purpose": "Routing-eval corpus for adia-site-docs. 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-docs-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-site-docs routing \u2014 does this phrase activate adia-site-docs?",
+  "scope": "site-docs-authoring routing \u2014 does this phrase activate site-docs-authoring?",
   "phrases": [
     {
-      "id": "adia-site-docs-pos-01",
+      "id": "site-docs-authoring-pos-01",
       "phrase": "review this site docs page for consistency",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-02",
+      "id": "site-docs-authoring-pos-02",
       "phrase": "does this callout look like plain text to you",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-03",
+      "id": "site-docs-authoring-pos-03",
       "phrase": "why is the code background not visible on this page",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-04",
+      "id": "site-docs-authoring-pos-04",
       "phrase": "add a new pattern page under site/pages/patterns",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-05",
+      "id": "site-docs-authoring-pos-05",
       "phrase": "author a new getting-started guide page",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-06",
+      "id": "site-docs-authoring-pos-06",
       "phrase": "write a new architecture explainer page for the docs site",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-07",
+      "id": "site-docs-authoring-pos-07",
       "phrase": "create a reference page documenting the MCP tools",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-08",
+      "id": "site-docs-authoring-pos-08",
       "phrase": "this demo page needs a tamed static frame like the other pattern pages",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-09",
+      "id": "site-docs-authoring-pos-09",
       "phrase": "add a new admin-shell demo to this patterns page without duplicating the taming CSS",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-10",
+      "id": "site-docs-authoring-pos-10",
       "phrase": "is this site page consistent with our authoring conventions",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-11",
+      "id": "site-docs-authoring-pos-11",
       "phrase": "audit site/pages/guides for the same callout bug we found elsewhere",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-12",
+      "id": "site-docs-authoring-pos-12",
       "phrase": "this warning box on the docs page has no background at all",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-13",
+      "id": "site-docs-authoring-pos-13",
       "phrase": "what's the shared skeleton every site docs page should follow",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-14",
+      "id": "site-docs-authoring-pos-14",
       "phrase": "what token should a new chip-like surface use to stay readable against the page background",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-15",
+      "id": "site-docs-authoring-pos-15",
       "phrase": "check the patterns pages for any other unstyled data attributes like data-alert",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-pos-16",
+      "id": "site-docs-authoring-pos-16",
       "phrase": "scaffold a new getting-started/theming-dark-mode.html page",
-      "expected": "adia-site-docs"
+      "expected": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-01",
+      "id": "site-docs-authoring-neg-01",
       "phrase": "review this component's own demo gallery in its .examples.html file",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-02",
+      "id": "site-docs-authoring-neg-02",
       "phrase": "fix this gen-ui training exemplar page under site/pages/examples",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-03",
+      "id": "site-docs-authoring-neg-03",
       "phrase": "tune the zettel retrieval threshold for the chunk corpus",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-04",
+      "id": "site-docs-authoring-neg-04",
       "phrase": "add a new prop to the button-ui primitive",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-05",
+      "id": "site-docs-authoring-neg-05",
       "phrase": "cut the next npm release for the 9 @adia-ai packages",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-06",
+      "id": "site-docs-authoring-neg-06",
       "phrase": "deploy the docs site to ui-kit.exe.xyz",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-07",
+      "id": "site-docs-authoring-neg-07",
       "phrase": "fix this gen-ui training exemplar page",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     },
     {
-      "id": "adia-site-docs-neg-08",
+      "id": "site-docs-authoring-neg-08",
       "phrase": "add a demo to the patterns page for card-ui",
-      "expected_not": "adia-site-docs"
+      "expected_not": "site-docs-authoring"
     }
   ],
   "_measured_historical": {

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

@@ -1,4 +1,4 @@
-# intent — adia-site-docs
+# intent — site-docs-authoring
 status: shipped
 species: procedural
 dials: { disable-model-invocation: false, user-invocable: true }
@@ -23,8 +23,8 @@ should:
   - "author a new page under site/pages/getting-started"
   - "is this site page consistent with our conventions"
 should_not:
-  - "review this component demo gallery" (packages/web-components/components/*/*.examples.html — adia-author)
-  - "fix this gen-ui training exemplar page" (site/pages/examples/**, site/pages/gen-ui/** — composition-and-examples.md's no-style-block rule + adia-a2ui)
+  - "review this component demo gallery" (packages/web-components/components/*/*.examples.html — primitive-authoring)
+  - "fix this gen-ui training exemplar page" (site/pages/examples/**, site/pages/gen-ui/** — composition-and-examples.md's no-style-block rule + a2ui-maintenance)
 
 ## delta
 Without this skill, Claude (or a human author) reaches for whatever
@@ -48,9 +48,9 @@ block, because nothing routes them to `alert-ui` or `.demo-frame`
 before they start typing.
 
 ## fences
-- NOT for `packages/web-components/components/*/*.examples.html` component demo pages (adia-author)
-- NOT for `site/pages/examples/**`, `site/pages/gen-ui/**`, `packages/a2ui/corpus/exemplars/**` — pure primitive-composition training-harvest surfaces with their own no-style-block rule (`composition-and-examples.md`, adia-a2ui)
-- NOT for the A2UI generation pipeline itself, chunk corpus, or MCP tools (adia-a2ui)
+- NOT for `packages/web-components/components/*/*.examples.html` component demo pages (primitive-authoring)
+- NOT for `site/pages/examples/**`, `site/pages/gen-ui/**`, `packages/a2ui/corpus/exemplars/**` — pure primitive-composition training-harvest surfaces with their own no-style-block rule (`composition-and-examples.md`, a2ui-maintenance)
+- NOT for the A2UI generation pipeline itself, chunk corpus, or MCP tools (a2ui-maintenance)
 
 ## assertions
 1. A new callout block the skill produces uses `<alert-ui variant="...">` with a `[slot="content"]` wrapper for rich text — never a bare `data-*` attribute with no matching CSS.
@@ -61,10 +61,10 @@ before they start typing.
 ## gates
 P0 route:      PASS — 2026-07-14 — knowledge/procedure needed on demand (author or review a site/pages doc), not mechanically checkable (hook), not always-true-every-turn (entry file), no tool-wall/parallelism need (agent). Skill.
 P1 intent:     PASS — 2026-07-14 — slots filled from the approved plan + this session's research; operator confirmed the plan's Phase 4 scope (doc + dedicated skill) via AskUserQuestion before forging began.
-P2 evals:      PASS — 2026-07-14 — see evals/routing-corpus.json (trigger cases, matching this repo's adia-author sibling's own eval-file convention) and assertions above (behavioral). No literal fresh-session baseline captured (this is a same-session, plan-driven forge, not an interactive intent interview) — the delta section above records the concrete "without this skill" failure mode from direct evidence (the 3 defect classes this session found and fixed) in place of a baseline transcript.
+P2 evals:      PASS — 2026-07-14 — see evals/routing-corpus.json (trigger cases, matching this repo's primitive-authoring sibling's own eval-file convention) and assertions above (behavioral). No literal fresh-session baseline captured (this is a same-session, plan-driven forge, not an interactive intent interview) — the delta section above records the concrete "without this skill" failure mode from direct evidence (the 3 defect classes this session found and fixed) in place of a baseline transcript.
 P3 draft:      PASS — 2026-07-14 — SKILL.md + evals/routing-corpus.json exist; both dials explicit; body 61 lines, well under the 500-line budget.
 P4 language:   PASS — 2026-07-14 — self-audited against the 5 instantiation checks: task-shape rows commit to concrete actions (not descriptions); ~3 hard-gate ceiling held (never restate demo-frame properties, never a bare data-* callout, don't reach for a raw ramp step without color-verify); numeric anchors present (>=3:1, 34-page, 4 rules); contracts (task-shape table) precede the verify-steps tail; the labeled good/bad alert-ui pair lives in the referenced convention doc rather than duplicated here (reference, never restate).
-P5 validate:   PASS — 2026-07-14 — skill_lint.py clean; skill-auditor FLOOR audit verdict PASS (report at evals/audit-report.md), 3 minor non-blocking findings, all fixed same-change (phantom fence trimmed to reference composition-and-examples.md by name rather than specific paths; 2 negative imperatives demoted to positive form; intent.md's routing-corpus.json citation corrected). No fence-reciprocity step run against adia-author's own evals — adia-author's corpus already covers "primitive authoring" as should_route_to_author:true, which is the correct answer for those phrases; no reciprocal edit needed there.
+P5 validate:   PASS — 2026-07-14 — skill_lint.py clean; skill-auditor FLOOR audit verdict PASS (report at evals/audit-report.md), 3 minor non-blocking findings, all fixed same-change (phantom fence trimmed to reference composition-and-examples.md by name rather than specific paths; 2 negative imperatives demoted to positive form; intent.md's routing-corpus.json citation corrected). No fence-reciprocity step run against primitive-authoring's own evals — primitive-authoring's corpus already covers "primitive authoring" as should_route_to_author:true, which is the correct answer for those phrases; no reciprocal edit needed there.
 
 ## rulings
 - Accepted with note: no literal fresh-session baseline transcript (P2) — this forge ran from an already-approved plan's research rather than a live interview; the delta section's direct evidence substitutes. Not re-litigated.

package/skills/{adia-ssr → ssr-compatibility}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: adia-ssr
+name: ssr-compatibility
 description: >-
   Answers why an AdiaUI component crashes, drops content, or renders wrong
   under SSR (linkedom/Astro consumers) — the four known failure shapes,
@@ -10,13 +10,13 @@ description: >-
   nested children when server-rendered, whether it's safe to call
   getBoundingClientRect() synchronously in connectedCallback, or whether a
   browser-API shim/workaround can finally be deleted after a fix ships.
-  ANSWERS only. NOT for implementing a fix (adia-author) or consumer
-  host/hydration wiring (adia-host, adia-ui-factory plugin).
+  ANSWERS only. NOT for implementing a fix (primitive-authoring) or consumer
+  host/hydration wiring (host-wiring, adia-ui-factory plugin).
 disable-model-invocation: false
 user-invocable: false
 ---
 
-# adia-ssr — does it work under SSR, and why not if it doesn't
+# ssr-compatibility — does it work under SSR, and why not if it doesn't
 
 Two real consumers (adiav2's `admin-portal-fe` and `factory-dashboard`) server-render
 AdiaUI's light-DOM components via Astro 5 + `custom-elements-ssr`, which runs on
@@ -78,20 +78,20 @@ carries the reasoning for why it looks the way it does — the no-op `ElementInt
 shim exists because leaving the field `undefined` would relocate a crash, not remove
 it; deletion-based testing exists because this repo has no `linkedom` devDependency.
 If a new case doesn't fit an existing pattern's reasoning, that's a signal to design a
-new pattern. Route it through `adia-author` — don't force-fit the nearest existing
+new pattern. Route it through `primitive-authoring` — don't force-fit the nearest existing
 shape.
 
 ## Boundaries
 
 - **Implementing any fix — new or matching an existing pattern.** Route to
-  `adia-author`. This pack orients and cites; it never edits
+  `primitive-authoring`. This pack orients and cites; it never edits
   `packages/web-components/core/` or any component source.
 - **Consumer-side SSR/hydration host wiring** (an app's own Astro/Next config, which
   rendering mode to pick, how to structure the hydration boundary). Route to
-  `adia-host` (adia-ui-factory plugin) — this pack answers whether the FRAMEWORK's own
+  `host-wiring` (adia-ui-factory plugin) — this pack answers whether the FRAMEWORK's own
   components are SSR-safe, not how a consumer app should be structured around them.
 - **A2UI runtime/generation-pipeline SSR concerns** (if any surface later). Route to
-  `adia-a2ui` — this pack is scoped to `UIElement`'s own lifecycle and the
+  `a2ui-maintenance` — this pack is scoped to `UIElement`'s own lifecycle and the
   component/trait/module layer, not the generative pipeline.
 - **Not a general web-components-SSR tutorial.** Every claim here is cited to this
   specific framework's actual code, issues, and PRs — general SSR/custom-elements

package/skills/{adia-ssr → ssr-compatibility}/evals/evals.json

@@ -1,6 +1,6 @@
 {
-  "skill": "adia-ssr",
-  "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. adia-ssr is user-invocable:false but disable-model-invocation:false, so it remains model-invocable and is in G7's scope.",
+  "skill": "ssr-compatibility",
+  "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. ssr-compatibility is user-invocable:false but disable-model-invocation:false, so it remains model-invocable and is in G7's scope.",
   "cases": [
     { "id": "t01", "prompt": "Why does text-ui render empty when we server-render it with Astro?", "expect": "trigger" },
     { "id": "t02", "prompt": "Our SSR pass crashes because attachInternals isn't a function under linkedom", "expect": "trigger" },
@@ -10,11 +10,11 @@
     { "id": "t06", "prompt": "document.adoptedStyleSheets is undefined and our component library crashes on import under SSR", "expect": "trigger" },
     { "id": "t07", "prompt": "What's the actual root cause of the SSR content-loss bug — container CEs losing their nested children?", "expect": "trigger" },
     { "id": "t08", "prompt": "Can our app finally delete the 110-line browser-API SSR shim now that 0.8.5 is out?", "expect": "trigger" },
-    { "id": "n01", "prompt": "Add hydration-aware stamping so connectedCallback stops overwriting existing children", "expect": "no-trigger", "owner": "adia-author" },
-    { "id": "n02", "prompt": "Set up Astro's rendering mode and hydration boundaries for our admin app", "expect": "no-trigger", "owner": "adia-host" },
+    { "id": "n01", "prompt": "Add hydration-aware stamping so connectedCallback stops overwriting existing children", "expect": "no-trigger", "owner": "primitive-authoring" },
+    { "id": "n02", "prompt": "Set up Astro's rendering mode and hydration boundaries for our admin app", "expect": "no-trigger", "owner": "host-wiring" },
     { "id": "n03", "prompt": "Explain how custom element hydration works in general, independent of any specific framework", "expect": "no-trigger" },
-    { "id": "n04", "prompt": "Wire up the a2ui generation pipeline to run inside a server-rendered page", "expect": "no-trigger", "owner": "adia-a2ui" },
-    { "id": "n05", "prompt": "Add a new primitive to the component catalog", "expect": "no-trigger", "owner": "adia-author" },
-    { "id": "n06", "prompt": "Deploy the latest build to ui-kit.exe.xyz", "expect": "no-trigger", "owner": "adia-deploy" }
+    { "id": "n04", "prompt": "Wire up the a2ui generation pipeline to run inside a server-rendered page", "expect": "no-trigger", "owner": "a2ui-maintenance" },
+    { "id": "n05", "prompt": "Add a new primitive to the component catalog", "expect": "no-trigger", "owner": "primitive-authoring" },
+    { "id": "n06", "prompt": "Deploy the latest build to ui-kit.exe.xyz", "expect": "no-trigger", "owner": "site-deployment" }
   ]
 }

package/skills/{adia-ssr → ssr-compatibility}/evals/routing-corpus.json

@@ -1,110 +1,110 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "name": "adia-ssr routing accuracy corpus",
+  "name": "ssr-compatibility routing accuracy corpus",
   "version": "2.1.0",
-  "purpose": "Routing-eval corpus for adia-ssr. 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 ssr-compatibility. 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-ssr routing \u2014 does this phrase activate adia-ssr?",
+  "scope": "ssr-compatibility routing \u2014 does this phrase activate ssr-compatibility?",
   "phrases": [
     {
-      "id": "adia-ssr-pos-01",
+      "id": "ssr-compatibility-pos-01",
       "phrase": "why does text-ui render empty when we server-render it with Astro",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-02",
+      "id": "ssr-compatibility-pos-02",
       "phrase": "our SSR pass crashes on attachInternals not being a function",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-03",
+      "id": "ssr-compatibility-pos-03",
       "phrase": "does select-ui work under linkedom",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-04",
+      "id": "ssr-compatibility-pos-04",
       "phrase": "admin-sidebar snaps collapsed on every server-rendered page load",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-05",
+      "id": "ssr-compatibility-pos-05",
       "phrase": "is gh#284 fixed yet, can we drop the attribute-only SSR registration restriction",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-06",
+      "id": "ssr-compatibility-pos-06",
       "phrase": "how do we test that a new ResizeObserver guard actually works without installing linkedom",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-07",
+      "id": "ssr-compatibility-pos-07",
       "phrase": "new ResizeObserver() throws under our DOM-shim SSR environment",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-08",
+      "id": "ssr-compatibility-pos-08",
       "phrase": "table-ui and chart-ui always render empty in our server-rendered HTML even though the data is set",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-09",
+      "id": "ssr-compatibility-pos-09",
       "phrase": "what's the actual root cause of the SSR content-loss bug, container CEs losing their nested children",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-10",
+      "id": "ssr-compatibility-pos-10",
       "phrase": "can our app finally delete the 110-line browser-API shim now that 0.8.5 is out",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-11",
+      "id": "ssr-compatibility-pos-11",
       "phrase": "is it safe to call getBoundingClientRect() synchronously in connectedCallback",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-pos-12",
+      "id": "ssr-compatibility-pos-12",
       "phrase": "document.adoptedStyleSheets is undefined and our component library crashes on import",
-      "expected": "adia-ssr"
+      "expected": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-01",
+      "id": "ssr-compatibility-neg-01",
       "phrase": "add hydration-aware stamping so connectedCallback stops overwriting existing children",
-      "expected_not": "adia-ssr"
+      "expected_not": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-02",
+      "id": "ssr-compatibility-neg-02",
       "phrase": "set up Astro's rendering mode and hydration boundaries for our admin app",
-      "expected_not": "adia-ssr"
+      "expected_not": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-03",
+      "id": "ssr-compatibility-neg-03",
       "phrase": "explain how custom element hydration works in general, independent of any specific framework",
-      "expected_not": "adia-ssr"
+      "expected_not": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-04",
+      "id": "ssr-compatibility-neg-04",
       "phrase": "the icon registry comes back empty because of a workspace-hoisting import.meta.glob path bug",
-      "expected_not": "adia-ssr"
+      "expected_not": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-05",
+      "id": "ssr-compatibility-neg-05",
       "phrase": "wire up the a2ui generation pipeline to run inside a server-rendered page",
-      "expected_not": "adia-ssr"
+      "expected_not": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-06",
+      "id": "ssr-compatibility-neg-06",
       "phrase": "add a new primitive to the component catalog",
-      "expected_not": "adia-ssr"
+      "expected_not": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-07",
+      "id": "ssr-compatibility-neg-07",
       "phrase": "compose the billing settings screen from the catalog",
-      "expected_not": "adia-ssr"
+      "expected_not": "ssr-compatibility"
     },
     {
-      "id": "adia-ssr-neg-08",
+      "id": "ssr-compatibility-neg-08",
       "phrase": "deploy the latest build to ui-kit.exe.xyz",
-      "expected": "adia-deploy"
+      "expected": "site-deployment"
     }
   ],
   "_measured_historical": {

package/skills/{adia-ssr → ssr-compatibility}/references/failure-shapes.md

@@ -69,7 +69,7 @@ instances. Shipped a forward-looking STATIC AUDIT instead:
 component pairing a non-null `static template` with a yaml `slots.default` entry
 (the container shape), and (advisory) a non-null template paired with a body-text
 usage example (the projected-text shape, no mechanical yaml signal to check). Wired
-into `adia-author`'s structural-gate sequence. This is an operator ruling (not a
+into `primitive-authoring`'s structural-gate sequence. This is an operator ruling (not a
 unilateral call) — see gh#284's comment thread for the full reasoning and the
 empirical survey it's based on.
 

package/skills/{adia-ssr → ssr-compatibility}/references/guard-patterns.md

@@ -100,7 +100,7 @@ pattern) — NOT by inventing a component-local stamp-skip flag or a marker
 attribute; either of those drifts from the established convention and isn't
 covered by this audit's "safe" classification. If a genuinely new component NEEDS
 both a non-null template AND real consumer children (unlike anything shipped
-today), route through `adia-author` before authoring it — that's a real design
+today), route through `primitive-authoring` before authoring it — that's a real design
 question, not a mechanical fix.
 
 ## §2b · Reflected properties not initialized from pre-existing attributes on upgrade (gh#284's REAL fix, PR #309)