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

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)