@adia-ai/adia-ui-forge 0.8.9 → 0.8.11

package/skills/adia-llm-internals/evals/routing-corpus.json

@@ -1,37 +1,134 @@
 {
-  "positives": [
-    "the gemini adapter is dropping usage tokens on streamed responses",
-    "stopReason from openai never reaches the client as MAX_TOKENS",
-    "the SSE parser chokes when a chunk splits mid-line",
-    "the passthrough proxy is returning 401 for anthropic requests in production",
-    "add a new model to the MODELS registry and set it as DEFAULT_MODEL",
-    "createAdapter() is leaking a real API key to the browser on a production host",
-    "add support for a new OpenAI-compatible gateway provider adapter",
-    "streamChat() never emits a terminal done chunk",
-    "detectProvider isn't resolving the new model id to the right adapter",
-    "the anthropic adapter's buildRequest() diverges from the passthrough proxy path",
-    "the StreamChunk union is missing a variant for tool_use deltas",
-    "the stub LLM adapter isn't returning parseable A2UI JSON in dev mode"
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "name": "adia-llm-internals routing accuracy corpus",
+  "version": "2.1.0",
+  "purpose": "Routing-eval corpus for adia-llm-internals. 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-llm-internals routing \u2014 does this phrase activate adia-llm-internals?",
+  "phrases": [
+    {
+      "id": "adia-llm-internals-pos-01",
+      "phrase": "the gemini adapter is dropping usage tokens on streamed responses",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-02",
+      "phrase": "stopReason from openai never reaches the client as MAX_TOKENS",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-03",
+      "phrase": "the SSE parser chokes when a chunk splits mid-line",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-04",
+      "phrase": "the passthrough proxy is returning 401 for anthropic requests in production",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-05",
+      "phrase": "add a new model to the MODELS registry and set it as DEFAULT_MODEL",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-06",
+      "phrase": "createAdapter() is leaking a real API key to the browser on a production host",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-07",
+      "phrase": "add support for a new OpenAI-compatible gateway provider adapter",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-08",
+      "phrase": "streamChat() never emits a terminal done chunk",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-09",
+      "phrase": "detectProvider isn't resolving the new model id to the right adapter",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-10",
+      "phrase": "the anthropic adapter's buildRequest() diverges from the passthrough proxy path",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-11",
+      "phrase": "the StreamChunk union is missing a variant for tool_use deltas",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-pos-12",
+      "phrase": "the stub LLM adapter isn't returning parseable A2UI JSON in dev mode",
+      "expected": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-01",
+      "phrase": "wire the chat client into our admin app's chat-shell",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-02",
+      "phrase": "why did the composer emit composition-synthesized instead of composition-match",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-03",
+      "phrase": "cut a release and bump @adia-ai/llm's version with the rest of the lockstep packages",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-04",
+      "phrase": "add a new prop to the chat-input-ui primitive",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-05",
+      "phrase": "explain how Server-Sent Events work in general",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-06",
+      "phrase": "add a chat box to the admin app",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-07",
+      "phrase": "the chat-shell message list isn't rendering streamed replies",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-08",
+      "phrase": "tune STRONG_MATCH and lift the eval fails in the compose strategies",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-09",
+      "phrase": "deploy the ui-kit dist to exe.dev and restart the service",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-10",
+      "phrase": "run a dogfood sweep to find broken demos",
+      "expected_not": "adia-llm-internals"
+    },
+    {
+      "id": "adia-llm-internals-neg-11",
+      "phrase": "score the gen-ui gallery outputs against the exit gate",
+      "expected_not": "adia-llm-internals"
+    }
   ],
-  "negatives": [
-    "wire the chat client into our admin app's chat-shell",
-    "why did the composer emit composition-synthesized instead of composition-match",
-    "cut a release and bump @adia-ai/llm's version with the rest of the lockstep packages",
-    "add a new prop to the chat-input-ui primitive",
-    "explain how Server-Sent Events work in general",
-    "add a chat box to the admin app",
-    "the chat-shell message list isn't rendering streamed replies",
-    "tune STRONG_MATCH and lift the eval fails in the compose strategies",
-    "deploy the ui-kit dist to exe.dev and restart the service",
-    "run a dogfood sweep to find broken demos",
-    "score the gen-ui gallery outputs against the exit gate"
-  ],
-  "_measured": {
+  "_measured_historical": {
     "as_of": "2026-07-18",
     "scorer": "routing_eval.py (nonoun-plugins/forge)",
     "f1": 0.857,
     "precision": 1.0,
     "recall": 0.75,
-    "exit_code": 0
+    "exit_code": 0,
+    "note": "measured by the external routing_eval.py (nonoun-plugins/forge) against the pre-conversion positives/negatives shape; historical record only, not regenerated by run-skill-evals.mjs."
   }
 }

package/skills/adia-release/evals/routing-corpus.json

@@ -1,35 +1,124 @@
 {
-  "positives": [
-    "Cut and ship v0.8.5 of the AdiaUI packages",
-    "The [Unreleased] CHANGELOG entries are piling up, let's cut a release",
-    "Tag the lockstep packages and push them to origin",
-    "check:lockstep is failing \u2014 one package didn't bump",
-    "Dispatch the publish workflows for v0.8.5 and verify npm",
-    "We have three unpushed release commits piled up, batch-push them",
-    "F-N1 is warning about a CHANGELOG entry not covering a touched directory",
-    "The release cut landed on the wrong branch, help me recover",
-    "Author the release notes and Slack post for the last two versions",
-    "This cut removes the variant prop from button-ui, write the MIGRATION GUIDE section",
-    "Publish the adia-ui-forge plugin independently of the lockstep set",
-    "Just verify the release gates are green without cutting anything",
-    "Tags are pushed but zero publish workflows fired, what happened"
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "name": "adia-release routing accuracy corpus",
+  "version": "2.1.0",
+  "purpose": "Routing-eval corpus for adia-release. 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-release routing \u2014 does this phrase activate adia-release?",
+  "phrases": [
+    {
+      "id": "adia-release-pos-01",
+      "phrase": "Cut and ship v0.8.5 of the AdiaUI packages",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-02",
+      "phrase": "The [Unreleased] CHANGELOG entries are piling up, let's cut a release",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-03",
+      "phrase": "Tag the lockstep packages and push them to origin",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-04",
+      "phrase": "check:lockstep is failing \u2014 one package didn't bump",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-05",
+      "phrase": "Dispatch the publish workflows for v0.8.5 and verify npm",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-06",
+      "phrase": "We have three unpushed release commits piled up, batch-push them",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-07",
+      "phrase": "F-N1 is warning about a CHANGELOG entry not covering a touched directory",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-08",
+      "phrase": "The release cut landed on the wrong branch, help me recover",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-09",
+      "phrase": "Author the release notes and Slack post for the last two versions",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-10",
+      "phrase": "This cut removes the variant prop from button-ui, write the MIGRATION GUIDE section",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-11",
+      "phrase": "Publish the adia-ui-forge plugin independently of the lockstep set",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-12",
+      "phrase": "Just verify the release gates are green without cutting anything",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-pos-13",
+      "phrase": "Tags are pushed but zero publish workflows fired, what happened",
+      "expected": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-01",
+      "phrase": "Restart the exe.dev VM, it's returning 502s",
+      "expected_not": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-02",
+      "phrase": "Rsync the built dist folder to ui-kit.exe.xyz",
+      "expected_not": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-03",
+      "phrase": "Sweep our consumer app for the renamed variant prop after the last breaking release",
+      "expected_not": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-04",
+      "phrase": "Add a new size variant to the button-ui primitive",
+      "expected_not": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-05",
+      "phrase": "Compose a settings screen for our app from the AdiaUI catalog",
+      "expected_not": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-06",
+      "phrase": "zettel coverage dropped on the nightly eval, find out why",
+      "expected_not": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-07",
+      "phrase": "sweep the component demos for native-primitive leaks before we cut",
+      "expected_not": "adia-release"
+    },
+    {
+      "id": "adia-release-neg-08",
+      "phrase": "the gemini adapter is dropping usage tokens on streamed responses",
+      "expected": "adia-llm-internals"
+    }
   ],
-  "negatives": [
-    "Restart the exe.dev VM, it's returning 502s",
-    "Rsync the built dist folder to ui-kit.exe.xyz",
-    "Sweep our consumer app for the renamed variant prop after the last breaking release",
-    "Add a new size variant to the button-ui primitive",
-    "Compose a settings screen for our app from the AdiaUI catalog",
-    "zettel coverage dropped on the nightly eval, find out why",
-    "sweep the component demos for native-primitive leaks before we cut",
-    "the gemini adapter is dropping usage tokens on streamed responses"
-  ],
-  "_measured": {
+  "_measured_historical": {
     "as_of": "2026-07-18",
     "scorer": "routing_eval.py (nonoun-plugins/forge)",
     "f1": 1.0,
     "precision": 1.0,
     "recall": 1.0,
-    "exit_code": 0
+    "exit_code": 0,
+    "note": "measured by the external routing_eval.py (nonoun-plugins/forge) against the pre-conversion positives/negatives shape; historical record only, not regenerated by run-skill-evals.mjs."
   }
 }

package/skills/adia-release/references/changelog-discipline.md

@@ -92,6 +92,7 @@ The inserted block:
 
 - **Make the PATCH-cut asymmetry visible** when an entry mentions a dependency: version bumps to `X.Y.Z` while internal ranges hold at `^X.Y.0` — spell it as `dependencies["@adia-ai/<x>"]: ^X.Y.0 (covers X.Y.Z)` so it doesn't read as a bug.
 - **Stale stubs are an F-N1 hazard.** A "no source changes" stub on a package that DID change earns a warn; the fix is authoring (§Authoring), not stubbing.
+- **The tool owns stub packages — never hand-write their `[Unreleased]`.** `insert-stub.mjs` INSERTS a fresh dated block at the top; it does not promote or replace existing content. A hand-authored `[Unreleased]` stub in a `--stub-packages` target survives the insert as a second, orphaned block below it, and the orchestrator's loud guard then fails the whole run ("N packages still have non-empty [Unreleased]") — the v0.8.10 cut lost a full cycle to exactly this across 6 packages. Ride-along packages get NO hand-written entry at cut time: leave them untouched and list them in `--stub-packages`. (A package that deserves hand-written content isn't a stub — it belongs in `--substantive-packages`.)
 
 ## §F-N1 diff-coverage — mechanized at cut time (Step 4f)
 

package/skills/adia-release/references/cut-procedure.md

@@ -127,6 +127,34 @@ tag-creation/tag-push/publish-dispatch commands until it passes, and
 shipped tarballs with unpromoted `[Unreleased]` CHANGELOG headers because
 this class of check ran only after tagging).
 
+**4-resume. Resuming a cut that died mid-Step-4** (v0.8.10 hit this live):
+`release-pack.mjs` always re-runs the FULL sequence from Step 1, and
+`promote-unreleased.mjs` hard-errors on already-promoted packages ("already
+has ## [X.Y.Z]") — so once ANY promotion has landed, re-invoking the
+orchestrator can never get past Step 4. That error is the idempotency guard
+working, not a corrupted state. Do NOT hand-edit CHANGELOGs back to
+`[Unreleased]` to appease it. Instead, verify the promotion state with the
+authoritative gate — `node scripts/release/check-release-docs.mjs --version
+X.Y.Z` covers every lockstep package (including the nested `a2ui/*` and
+`plugins/*` paths a shallow `packages/*` glob misses) and fails on any
+leftover `[Unreleased]` content or missing `[X.Y.Z]` heading; it will still
+flag the not-yet-generated `docs/releases/vX.Y.Z.md`, which 4e below creates.
+Then run the remaining steps as the standalone pieces the Mechanization
+section already names, in this order:
+
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/skills/adia-release/scripts/bump.mjs" --from X.Y.Z-1 --to X.Y.Z   # 4b
+npm install --package-lock-only --no-audit --no-fund                                          # 4c
+npm run check:lockstep                                                                        # 4d
+node scripts/release/check-release.mjs --pending-version X.Y.Z --fix                          # 4f
+node scripts/release/generate-release-notes.mjs --version X.Y.Z --write                       # 4e
+node scripts/release/check-release-docs.mjs --version X.Y.Z                                   # 4e gate
+node scripts/release/check-cut-hygiene.mjs --version X.Y.Z                                    # 4g — post-bump proof
+# then Step 5 by hand (branch, stage, commit) — Step 5.5's freshness
+# trip-wire runs on the staged set exactly as on a normal cut, don't skip it —
+# and Step 5.7 via pr-bridge.mjs
+```
+
 ## §Step 5 — Stage and commit (on a release branch)
 
 The release commit lands via PR, never a direct push to `main` (repo

package/skills/adia-release/scripts/release-pack.mjs

@@ -143,11 +143,29 @@ function parseArgs(argv) {
     console.error(`error: --mode must be cut|from-scratch|handoff (got: ${args.mode})`);
     process.exit(2);
   }
+  // Handoff needs the GH-notes body at Step 10 — validate at PARSE time, not
+  // there: on the v0.8.10 cut the missing flag surfaced only after tags and
+  // npm publish were already irreversible (Step 10 is the LAST step). An arg
+  // error must never cost half a shipped release.
+  if (args.mode === 'handoff') {
+    if (!args.ghNotesFile) {
+      console.error('error: --mode handoff requires --gh-notes-file (Step 10 creates the 11 GH');
+      console.error('       releases from it; tags/publish would land first, then the run would');
+      console.error('       die on the missing flag — v0.8.10 hit exactly this).');
+      process.exit(2);
+    }
+    if (!args.dry && !(fs.existsSync(args.ghNotesFile) && fs.statSync(args.ghNotesFile).isFile())) {
+      console.error(`error: GH notes file not found or not a regular file: ${args.ghNotesFile}`);
+      process.exit(2);
+    }
+  }
   return args;
 }
 
 function help() {
   console.log(`Usage:
+  node release-pack.mjs --mode handoff --version X.Y.Z --date YYYY-MM-DD \\
+    --previous-version X.Y.Z-1 --gh-notes-file /tmp/release-v$X.Y.Z.md   # REQUIRED for handoff
   node release-pack.mjs --mode cut --version X.Y.Z --date YYYY-MM-DD \\
     --previous-version X.Y.Z-1 \\
     --commit-message-file /tmp/v$X.Y.Z-commit.txt \\
@@ -734,6 +752,21 @@ function selftest() {
       process.exit(1);
     }
 
+    // Handoff without --gh-notes-file must die at PARSE time (v0.8.10: the old
+    // Step-10-only check fired after tags+publish were irreversible).
+    let handoffFailed = false;
+    let handoffOut = '';
+    try {
+      execSync(`node "${scriptPath}" --mode handoff --version 9.9.9 --date 2026-01-01 --previous-version 9.9.8 --dry`, { cwd: REPO, encoding: 'utf8' });
+    } catch (e) {
+      handoffFailed = true;
+      handoffOut = (e.stdout || '') + (e.stderr || '');
+    }
+    if (!handoffFailed || !handoffOut.includes('--gh-notes-file')) {
+      console.error('selftest FAIL: --mode handoff without --gh-notes-file must hard-reject at parse time');
+      process.exit(1);
+    }
+
     console.log('selftest OK');
   } finally {
     fs.rmSync(tmp, { recursive: true, force: true });

package/skills/adia-site-docs/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "adia-site-docs",
+  "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" },
+    { "id": "t02", "prompt": "This callout on the docs page reads as plain text, not a styled box — why?", "expect": "trigger" },
+    { "id": "t03", "prompt": "Add a new pattern page under site/pages/patterns for the kanban-board pattern", "expect": "trigger" },
+    { "id": "t04", "prompt": "Author a new getting-started guide page for theming dark mode", "expect": "trigger" },
+    { "id": "t05", "prompt": "Write a new architecture explainer page for the docs site", "expect": "trigger" },
+    { "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" }
+  ]
+}

package/skills/adia-site-docs/evals/routing-corpus.json

@@ -1,38 +1,139 @@
 {
-  "positives": [
-    "review this site docs page for consistency",
-    "does this callout look like plain text to you",
-    "why is the code background not visible on this page",
-    "add a new pattern page under site/pages/patterns",
-    "author a new getting-started guide page",
-    "write a new architecture explainer page for the docs site",
-    "create a reference page documenting the MCP tools",
-    "this demo page needs a tamed static frame like the other pattern pages",
-    "add a new admin-shell demo to this patterns page without duplicating the taming CSS",
-    "is this site page consistent with our authoring conventions",
-    "audit site/pages/guides for the same callout bug we found elsewhere",
-    "this warning box on the docs page has no background at all",
-    "what's the shared skeleton every site docs page should follow",
-    "what token should a new chip-like surface use to stay readable against the page background",
-    "check the patterns pages for any other unstyled data attributes like data-alert",
-    "scaffold a new getting-started/theming-dark-mode.html page"
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "name": "adia-site-docs 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).",
+  "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?",
+  "phrases": [
+    {
+      "id": "adia-site-docs-pos-01",
+      "phrase": "review this site docs page for consistency",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-02",
+      "phrase": "does this callout look like plain text to you",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-03",
+      "phrase": "why is the code background not visible on this page",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-04",
+      "phrase": "add a new pattern page under site/pages/patterns",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-05",
+      "phrase": "author a new getting-started guide page",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-06",
+      "phrase": "write a new architecture explainer page for the docs site",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-07",
+      "phrase": "create a reference page documenting the MCP tools",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-08",
+      "phrase": "this demo page needs a tamed static frame like the other pattern pages",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-09",
+      "phrase": "add a new admin-shell demo to this patterns page without duplicating the taming CSS",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-10",
+      "phrase": "is this site page consistent with our authoring conventions",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-11",
+      "phrase": "audit site/pages/guides for the same callout bug we found elsewhere",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-12",
+      "phrase": "this warning box on the docs page has no background at all",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-13",
+      "phrase": "what's the shared skeleton every site docs page should follow",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-14",
+      "phrase": "what token should a new chip-like surface use to stay readable against the page background",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-15",
+      "phrase": "check the patterns pages for any other unstyled data attributes like data-alert",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-pos-16",
+      "phrase": "scaffold a new getting-started/theming-dark-mode.html page",
+      "expected": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-01",
+      "phrase": "review this component's own demo gallery in its .examples.html file",
+      "expected_not": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-02",
+      "phrase": "fix this gen-ui training exemplar page under site/pages/examples",
+      "expected_not": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-03",
+      "phrase": "tune the zettel retrieval threshold for the chunk corpus",
+      "expected_not": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-04",
+      "phrase": "add a new prop to the button-ui primitive",
+      "expected_not": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-05",
+      "phrase": "cut the next npm release for the 9 @adia-ai packages",
+      "expected_not": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-06",
+      "phrase": "deploy the docs site to ui-kit.exe.xyz",
+      "expected_not": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-07",
+      "phrase": "fix this gen-ui training exemplar page",
+      "expected_not": "adia-site-docs"
+    },
+    {
+      "id": "adia-site-docs-neg-08",
+      "phrase": "add a demo to the patterns page for card-ui",
+      "expected_not": "adia-site-docs"
+    }
   ],
-  "negatives": [
-    "review this component's own demo gallery in its .examples.html file",
-    "fix this gen-ui training exemplar page under site/pages/examples",
-    "tune the zettel retrieval threshold for the chunk corpus",
-    "add a new prop to the button-ui primitive",
-    "cut the next npm release for the 9 @adia-ai packages",
-    "deploy the docs site to ui-kit.exe.xyz",
-    "fix this gen-ui training exemplar page",
-    "add a demo to the patterns page for card-ui"
-  ],
-  "_measured": {
+  "_measured_historical": {
     "as_of": "2026-07-18",
     "scorer": "routing_eval.py (nonoun-plugins/forge)",
     "f1": 0.733,
     "precision": 0.786,
     "recall": 0.688,
-    "exit_code": 0
+    "exit_code": 0,
+    "note": "measured by the external routing_eval.py (nonoun-plugins/forge) against the pre-conversion positives/negatives shape; historical record only, not regenerated by run-skill-evals.mjs."
   }
 }

package/skills/adia-ssr/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "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.",
+  "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" },
+    { "id": "t03", "prompt": "Does select-ui work under linkedom?", "expect": "trigger" },
+    { "id": "t04", "prompt": "table-ui and chart-ui always render empty in our server-rendered HTML even though the data is set", "expect": "trigger" },
+    { "id": "t05", "prompt": "Is it safe to call getBoundingClientRect() synchronously in connectedCallback?", "expect": "trigger" },
+    { "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": "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" }
+  ]
+}