@adia-ai/adia-ui-forge 0.8.5 → 0.8.7

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

@@ -4,8 +4,11 @@
 // Chains the 5 CLI helpers (bump · promote-unreleased · insert-stub ·
 // tag-lockstep · dispatch-publish) plus the non-helper steps (lockfile ·
 // pre-flight gates · git commit · F-N1 · push · GH releases · site
-// deploy) into one walked sequence with 3 operator checkpoints (before
-// tag, before push, before publish) per SKILL.md operator checkpoints.
+// deploy) into one walked sequence with 4 confirmation boundaries (before
+// tag, before push, before publish, before deploy dispatch). Under the
+// single-authorization model (SKILL.md §Authorization, operator ruling
+// 2026-07-17) `--go` auto-confirms all of them — the evidence blocks still
+// print as a log; the granular flags below remain for cautious manual runs.
 //
 // MODES (two-phase since 2026-07-16 — invariant 3: release commits land via
 // PR, so the cut modes stop after the release commit; handoff runs the
@@ -35,22 +38,27 @@
 //   --stub-packages a,b,c             : packages getting the lockstep stub
 //
 // FLAGS:
+//   --go                 : single-authorization — the operator's cut-start go
+//                          covers the whole cycle; equals --yes --push --publish.
+//                          THE standard invocation for an operator-initiated
+//                          release. An F-N1 warn still refuses auto-confirm at
+//                          the push boundary (a gate failure, not ceremony).
 //   --dry                : preview all commands, no mutation, no prompts
-//   --yes                : auto-confirm CHECKPOINT 1 ONLY (before tagging). Tag
-//                          creation is the least destructive of the three
-//                          mutating boundaries (moving/deleting a local-only
-//                          tag is free); push and publish each need their own
-//                          explicit go — --yes does not cover them (H5/defect-2:
-//                          a single --yes used to flatten all 3 checkpoints).
-//   --push               : auto-confirm CHECKPOINT 2 (before pushing tags)
-//   --publish            : auto-confirm CHECKPOINT 3 (before dispatching publishes)
+//   --yes                : auto-confirm the tag boundary ONLY. Tag creation is
+//                          the least destructive of the mutating boundaries
+//                          (moving/deleting a local-only tag is free); push and
+//                          publish each need their own flag — --yes does not
+//                          cover them (H5/defect-2: a single --yes used to
+//                          flatten every boundary).
+//   --push               : auto-confirm the push-tags boundary
+//   --publish            : auto-confirm the publish + deploy-dispatch boundaries
 //   --skip-gates         : (DEBUG ONLY) skip pre-flight (don't ship anything!)
 //   --skip-site          : skip the EXE deploy step (rare; for offline cycles)
 //
 // Part of the adia-release skill. Mechanizes the cut procedure from
-// references/cut-procedure.md while preserving operator judgment at
-// the 3 mutating-checkpoint boundaries. Every checkpoint prints its evidence
-// block BEFORE the prompt (H5) — never a bare y/N.
+// references/cut-procedure.md. Every confirmation boundary prints its evidence
+// block BEFORE the prompt (H5) — never a bare y/N — whether it waits for input
+// (manual flags) or auto-confirms (--go).
 
 import { execSync } from 'node:child_process';
 import { createInterface } from 'node:readline/promises';
@@ -108,6 +116,14 @@ function parseArgs(argv) {
     else if (k === '--yes') args.yes = true;
     else if (k === '--push') args.push = true;
     else if (k === '--publish') args.publish = true;
+    // --go: the single-authorization model (operator ruling 2026-07-17,
+    // replacing the 4-checkpoint ceremony after the v0.8.5 cut spent ~40
+    // minutes on approval relays that produced zero safety). The operator's
+    // cut-start instruction covers the WHOLE cycle; the run stops only on
+    // gate failures. Equivalent to --yes --push --publish; the F-N1
+    // error hard-stop and the warn-blocks-auto-confirm rule still apply —
+    // those are gates, not approvals, and no flag skips them.
+    else if (k === '--go') { args.yes = true; args.push = true; args.publish = true; }
     else if (k === '--skip-gates') args.skipGates = true;
     else if (k === '--skip-site') args.skipSite = true;
     else if (k === '-h' || k === '--help') { help(); process.exit(0); }
@@ -144,7 +160,10 @@ function help() {
     --substantive-packages web-components,web-modules,a2ui/corpus \\
     --stub-packages llm,a2ui/compose,a2ui/mcp,a2ui/retrieval,a2ui/runtime,a2ui/validator
 
-Flags: --dry  (preview all)  --yes  (auto-confirm checkpoint 1 ONLY — tag)
+Flags: --go   (single-authorization: the operator's cut-start go covers the
+               whole cycle — auto-confirms ALL checkpoints; stops only on
+               gate failures. THE DEFAULT for an operator-initiated release.)
+       --dry  (preview all)  --yes  (auto-confirm checkpoint 1 ONLY — tag)
        --push  (auto-confirm checkpoint 2 — push tags)
        --publish  (auto-confirm checkpoint 3 — dispatch publishes)
        --skip-site  (skip EXE deploy)
@@ -311,6 +330,15 @@ function step4PromoteAndBump(args) {
   sh(`node ${SCRIPT_DIR}/bump.mjs --from ${args.previous} --to ${args.version}`, args);
   sh('npm install --package-lock-only --no-audit --no-fund', args);
   sh('npm run check:lockstep', args);
+
+  // Step 4f — pre-tag F-N1 coverage with auto-fix, run with the AUTHORITATIVE
+  // matcher (check-release.mjs itself, not the drifted 9-package
+  // check-changelog-coverage.mjs). Appends verified Maintenance bullets for
+  // any changed-but-unmentioned directory so the post-tag F-N1 (Step 7) is a
+  // formality. The v0.8.5 cut lacked this and paid 3 enrichment PRs + 3
+  // delete/retag rounds discovering the same gaps only after tagging.
+  console.log('\n  Step 4f — pre-tag coverage (+auto-fix) with the authoritative F-N1 matcher:');
+  sh(`node scripts/release/check-release.mjs --pending-version ${args.version} --fix`, args);
 }
 
 // ── Step 5 — Commit ──────────────────────────────────────────────

package/skills/adia-site-docs/SKILL.md

@@ -35,7 +35,7 @@ skill routes to it and enforces it, it does not restate it.
 | Task shape | Do |
 | --- | --- |
 | New page in an owned category | Read the convention doc's template section; copy the shared skeleton from a sibling page in the same category (narrative archetype vs. reference/gallery archetype). |
-| Callout / "meta content" block | `<alert-ui variant="warning\|info\|...">` with `<div slot="content">` (never `<span>` — the transpiler only treats `p`/`div`/`ul`/`ol` as prose; a `<span>` silently reorders mixed inline content on regen) for rich text — never a bare `data-*` attribute. A whole multi-heading section aimed at a different reader (not a short callout) is NOT `alert-ui`'s job either (wrong shape) — currently there's no working distinguishing treatment for this case beyond the heading text itself; see the convention doc's rule 2 for what's been tried and why it doesn't render. |
+| Callout / "meta content" block | `<alert-ui variant="warning\|info\|...">` with `<div slot="content">` (never `<span>` — the transpiler only treats `p`/`div`/`ul`/`ol` as prose; a `<span>` silently reorders mixed inline content on regen) for rich text — never a bare `data-*` attribute. A whole multi-heading section aimed at a different reader (not a short callout) is NOT `alert-ui`'s job either — wrong shape — the convention doc's rule 2 carries the working treatment (eyebrow `<tag-ui>` title-row, TKT-0011). |
 | Tamed admin-shell demo | Add `class="demo-frame"` to the shell instance + a page-local `<style>` block setting only `--demo-frame-height` (and any genuinely page-specific extra). That's `site/site.css`'s `.demo-frame` utility already covering `position`/`border`/`overflow`/`.demo-body` padding. |
 | A surface needs to read as "its own distinct object" against the page background (a chip, a pill) | Reuse `--a-canvas-well-strong` (`packages/web-components/styles/colors/semantics/core.css`) — verified ≥3:1 (WCAG 2.2 SC 1.4.11) in both schemes. `--a-canvas-well` alone is for a subtly-sunken panel; a new candidate token always runs through `color:color-verify` first. |
 | "Is this page consistent?" / review request | Check the page against the convention doc's rules 1–4 by name; a finding names the specific rule violated, not just "this looks off." |
@@ -63,6 +63,11 @@ A check that cannot run (missing script, no network for a build step) is a
 named blocker in the report — flag it and stop; never mark the page done on
 an assumed pass.
 
+The fresh-context critic for an authored page is the `framework-reviewer`
+agent (its dogfood visual probe covers rendered site surfaces) — the author
+never certifies their own page's rendered result; the mechanical checks
+above plus that read-only pass together are the review.
+
 Done when the touched page(s) pass the checks above and, for a reviewed
 page, every finding cites the specific rule in `site-pages-authoring.md` it
 violates.

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

@@ -1,176 +1,38 @@
 {
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "name": "adia-site-docs routing accuracy corpus",
-  "version": "1.0.0",
-  "purpose": "Routing-eval corpus for adia-site-docs (adia-forge plugin). Each phrase declares whether adia-site-docs SHOULD be the routing target. Scored by the estate's TF-IDF routing-eval runner against the skill's description (heuristic token overlap).",
-  "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.",
-  "license": "internal",
-  "scope": "adia-site-docs routing — does this phrase activate adia-site-docs?",
-
-  "minimums_per_spec": {
-    "trigger_phrases": 16,
-    "adversarial_phrases": 6,
-    "task_shapes_covered": "new-page, review-page, callout-fix, demo-frame-consistency, contrast-token, sibling-boundary",
-    "adversarial_fraction": "27%"
-  },
-
-  "phrases": [
-    {
-      "id": "site-docs-review-01",
-      "phrase": "review this site docs page for consistency",
-      "should_route_to_site_docs": true,
-      "expected_shape": "review-page",
-      "rationale": "Canonical review-a-page task shape."
-    },
-    {
-      "id": "site-docs-review-02",
-      "phrase": "does this callout look like plain text to you",
-      "should_route_to_site_docs": true,
-      "expected_shape": "callout-fix",
-      "rationale": "Symptom description matching Defect 2 (fabricated data-alert)."
-    },
-    {
-      "id": "site-docs-review-03",
-      "phrase": "why is the code background not visible on this page",
-      "should_route_to_site_docs": true,
-      "expected_shape": "contrast-token",
-      "rationale": "Symptom description matching Defect 1 (inline-code contrast)."
-    },
-    {
-      "id": "site-docs-new-page-01",
-      "phrase": "add a new pattern page under site/pages/patterns",
-      "should_route_to_site_docs": true,
-      "expected_shape": "new-page",
-      "rationale": "Explicit site/pages/patterns path mention."
-    },
-    {
-      "id": "site-docs-new-page-02",
-      "phrase": "author a new getting-started guide page",
-      "should_route_to_site_docs": true,
-      "expected_shape": "new-page",
-      "rationale": "getting-started/ is one of this skill's 5 owned categories."
-    },
-    {
-      "id": "site-docs-new-page-03",
-      "phrase": "write a new architecture explainer page for the docs site",
-      "should_route_to_site_docs": true,
-      "expected_shape": "new-page",
-      "rationale": "architecture/ is one of this skill's 5 owned categories."
-    },
-    {
-      "id": "site-docs-new-page-04",
-      "phrase": "create a reference page documenting the MCP tools",
-      "should_route_to_site_docs": true,
-      "expected_shape": "new-page",
-      "rationale": "reference/ is one of this skill's 5 owned categories."
-    },
-    {
-      "id": "site-docs-demo-frame-01",
-      "phrase": "this demo page needs a tamed static frame like the other pattern pages",
-      "should_route_to_site_docs": true,
-      "expected_shape": "demo-frame-consistency",
-      "rationale": "Matches the .demo-frame consolidation rule."
-    },
-    {
-      "id": "site-docs-demo-frame-02",
-      "phrase": "add a new admin-shell demo to this patterns page without duplicating the taming CSS",
-      "should_route_to_site_docs": true,
-      "expected_shape": "demo-frame-consistency",
-      "rationale": "Direct match on rule 3 (reuse .demo-frame)."
-    },
-    {
-      "id": "site-docs-review-04",
-      "phrase": "is this site page consistent with our authoring conventions",
-      "should_route_to_site_docs": true,
-      "expected_shape": "review-page",
-      "rationale": "Direct convention-compliance ask."
-    },
-    {
-      "id": "site-docs-review-05",
-      "phrase": "audit site/pages/guides for the same callout bug we found elsewhere",
-      "should_route_to_site_docs": true,
-      "expected_shape": "review-page",
-      "rationale": "Explicit guides/ path + defect-class reference."
-    },
-    {
-      "id": "site-docs-callout-01",
-      "phrase": "this warning box on the docs page has no background at all",
-      "should_route_to_site_docs": true,
-      "expected_shape": "callout-fix",
-      "rationale": "Symptom description matching the fabricated data-alert defect."
-    },
-    {
-      "id": "site-docs-new-page-05",
-      "phrase": "what's the shared skeleton every site docs page should follow",
-      "should_route_to_site_docs": true,
-      "expected_shape": "new-page",
-      "rationale": "Direct ask about the template decomposition this skill carries."
-    },
-    {
-      "id": "site-docs-contrast-01",
-      "phrase": "what token should a new chip-like surface use to stay readable against the page background",
-      "should_route_to_site_docs": true,
-      "expected_shape": "contrast-token",
-      "rationale": "Direct match on rule 1 (--a-canvas-well-strong)."
-    },
-    {
-      "id": "site-docs-review-06",
-      "phrase": "check the patterns pages for any other unstyled data attributes like data-alert",
-      "should_route_to_site_docs": true,
-      "expected_shape": "review-page",
-      "rationale": "Direct defect-class sweep request."
-    },
-    {
-      "id": "site-docs-new-page-06",
-      "phrase": "scaffold a new getting-started/theming-dark-mode.html page",
-      "should_route_to_site_docs": true,
-      "expected_shape": "new-page",
-      "rationale": "Explicit new-file-under-owned-category shape."
-    },
-
-    {
-      "id": "site-docs-adversarial-01",
-      "phrase": "review this component's own demo gallery in its .examples.html file",
-      "should_route_to_site_docs": false,
-      "expected_shape": "sibling-boundary",
-      "rationale": "packages/web-components/components/*/*.examples.html is adia-author's remit, not this skill's."
-    },
-    {
-      "id": "site-docs-adversarial-02",
-      "phrase": "fix this gen-ui training exemplar page under site/pages/examples",
-      "should_route_to_site_docs": false,
-      "expected_shape": "sibling-boundary",
-      "rationale": "site/pages/examples/** is the pure-primitive-composition training-harvest surface governed by composition-and-examples.md + adia-a2ui, explicitly fenced out."
-    },
-    {
-      "id": "site-docs-adversarial-03",
-      "phrase": "tune the zettel retrieval threshold for the chunk corpus",
-      "should_route_to_site_docs": false,
-      "expected_shape": "sibling-boundary",
-      "rationale": "A2UI pipeline internals belong to adia-a2ui, unrelated to site/pages authoring."
-    },
-    {
-      "id": "site-docs-adversarial-04",
-      "phrase": "add a new prop to the button-ui primitive",
-      "should_route_to_site_docs": false,
-      "expected_shape": "sibling-boundary",
-      "rationale": "Primitive authoring is adia-author's remit."
-    },
-    {
-      "id": "site-docs-adversarial-05",
-      "phrase": "cut the next npm release for the 9 @adia-ai packages",
-      "should_route_to_site_docs": false,
-      "expected_shape": "sibling-boundary",
-      "rationale": "Release engineering is adia-release's remit, unrelated to docs-page authoring."
-    },
-    {
-      "id": "site-docs-adversarial-06",
-      "phrase": "deploy the docs site to ui-kit.exe.xyz",
-      "should_route_to_site_docs": false,
-      "expected_shape": "sibling-boundary",
-      "rationale": "Deploy operations are adia-deploy's remit; this skill authors content, it doesn't ship it."
-    }
+  "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"
   ],
-
-  "evaluator_notes": "Adversarial phrases 1-2 specifically test the two hardest-to-distinguish fences (component .examples.html vs site/pages/patterns/*.html; site/pages/examples/** vs site/pages/{architecture,getting-started,guides,patterns,reference}/**) — both surfaces are literally *.html under similar-looking paths, so the description must lean on the explicit path lists, not just 'site pages' as a phrase."
+  "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": {
+    "as_of": "2026-07-18",
+    "scorer": "routing_eval.py (nonoun-plugins/forge)",
+    "f1": 0.733,
+    "precision": 0.786,
+    "recall": 0.688,
+    "exit_code": 0
+  }
 }

package/skills/adia-ssr/SKILL.md

@@ -2,12 +2,16 @@
 name: adia-ssr
 description: >-
   Answers why an AdiaUI component crashes, drops content, or renders wrong
-  under SSR (linkedom/Astro consumers) — the three known failure shapes,
+  under SSR (linkedom/Astro consumers) — the four known failure shapes,
   what's fixed vs open, how to test without a linkedom install. Use when
-  asked "does this work under SSR", "why does X crash/disappear when
-  server-rendered", or "is this connect-time read safe". ANSWERS only. NOT
-  for implementing a fix (adia-author) or consumer host/hydration wiring
-  (adia-host, adia-ui-factory plugin).
+  asked "does this work under SSR", why a component crashes on
+  attachInternals/ResizeObserver/adoptedStyleSheets under a DOM shim, why
+  table-ui/chart-ui/select-ui or a container CE renders empty or loses its
+  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).
 disable-model-invocation: false
 user-invocable: false
 ---
@@ -17,26 +21,40 @@ user-invocable: false
 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
 linkedom — a DOM shim with no layout engine and missing browser APIs the framework's
-base class assumes exist. Every SSR bug that's surfaced maps onto one of three root-cause
+base class assumes exist. Every SSR bug that's surfaced maps onto one of four root-cause
 shapes; misclassifying a new report against the wrong shape sends the investigation
 to the wrong fix (or worse, invents a redundant one). This pack answers "which shape is
 this" and "what's the state of each shape's fix" — it never carries the fix itself.
 
-## The three shapes, in one line each
+## The four shapes, in one line each
 
 1. **A browser-only API is called unconditionally → crash.** `attachInternals`,
    the four Observer constructors, `document.adoptedStyleSheets`. **Fixed** (gh#285).
 2. **`connectedCallback` destructively re-stamps existing DOM → silent content loss.**
-   The mechanism is real, but **narrowed to a static audit** (gh#284, 2026-07-17) —
-   zero shipped components currently pair a non-null template with real light-DOM
-   content, so nothing is exposed today; a forward audit catches a future regression.
+   The ORIGINAL diagnosis, narrowed to a static audit 2026-07-17 (gh#284) — zero
+   shipped components currently pair a non-null template with real light-DOM
+   content, so this specific mechanism isn't exposed today; a forward audit catches
+   a future regression. **Do not stop here** — see shape 2b, the actual live bug
+   found investigating the same report.
+2b. **Custom-element upgrade doesn't replay `attributeChangedCallback` for
+   pre-existing attributes → reflected properties stuck at their class default.**
+   The REAL mechanism behind gh#284's reported symptom. happy-dom and (by strong
+   inference) linkedom both skip the custom-elements spec's upgrade-time
+   attribute replay (§4.13.5 step 6); any `reflect: true` property seeded only
+   from pre-parsed/SSR HTML never initializes. **Fixed 2026-07-18** (gh#284,
+   PR #309) — `connectedCallback` now re-syncs every declared property from its
+   live attribute before `connected()` runs.
 3. **A connect-time layout measurement is treated as confirmed, not unknown.** A zero
    rect (shim, or real pre-layout connect) drives a wrong persistent decision.
    **Fixed for one component** (gh#286); the general pattern is unswept.
 
-A fourth item, **property-only components can't seed initial state from SSR HTML**
-(gh#288), is a feature gap explicitly blocked on shape 2's resolution — don't treat it
-as its own independent task.
+A fifth item, **property-only components can't seed initial state from SSR HTML**
+(gh#288), was a feature gap — **CLOSED 2026-07-18**. It was never actually blocked
+on shape 2/2b (table-ui/chart-ui/select-ui all use `static template = () => null`
+too), and the real scope was narrower than filed: `select-ui` already declares
+options via native `<option>` children, `chart-ui` already hydrates `.data` from a
+JSON `data="[…]"` attribute — only `table-ui`'s `.data` had no declarative form,
+now fixed the same way.
 
 Full symptom → root-cause → status detail, cited to the actual shipped/open code:
 [`references/failure-shapes.md`](references/failure-shapes.md).
@@ -51,7 +69,7 @@ Full symptom → root-cause → status detail, cited to the actual shipped/open
 | "what's fixed vs still open for SSR support" | [`status-ledger.md`](references/status-ledger.md) — re-verify against `gh issue view` before trusting it, it drifts |
 | "how do I test an SSR gap — we have no linkedom installed" | [`test-without-linkedom.md`](references/test-without-linkedom.md) — the delete/try/finally pattern, and what it does NOT prove |
 | "what's the consumer's current workaround, and can they drop it yet" | [`consumer-workarounds.md`](references/consumer-workarounds.md) |
-| "table/chart/select renders empty in the SSR response" | [`failure-shapes.md`](references/failure-shapes.md) §4 — shape 4, blocked on shape 2 |
+| "table/chart/select renders empty in the SSR response" | [`failure-shapes.md`](references/failure-shapes.md) §4 — shape 5, CLOSED (table-ui's `data="[…]"` attribute); check whether the reporting component is registered server-side first if it still reproduces |
 
 ## Deviation doctrine
 

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

@@ -1,138 +1,34 @@
 {
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "name": "adia-ssr routing accuracy corpus",
-  "version": "1.0.0",
-  "purpose": "Routing-eval corpus for adia-ssr (adia-forge plugin). Each phrase declares whether adia-ssr SHOULD be the routing target. Scored by the estate's TF-IDF routing-eval runner against the skill's description (heuristic token overlap).",
-  "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.",
-  "license": "internal",
-  "scope": "adia-ssr routing — does this phrase activate adia-ssr?",
-
-  "minimums_per_spec": {
-    "trigger_phrases": 12,
-    "adversarial_phrases": 5,
-    "task_shapes_covered": "failure-shapes, guard-patterns, status-ledger, test-without-linkedom, consumer-workarounds",
-    "adversarial_fraction": "~29%"
-  },
-
-  "phrases": [
-    {
-      "id": "ssr-trigger-01",
-      "phrase": "why does text-ui render empty when we server-render it with Astro",
-      "should_route_to_ssr": true,
-      "expected_shape": "failure-shapes",
-      "rationale": "Canonical shape-2 symptom (projected-text content loss) — the worked example in SKILL.md."
-    },
-    {
-      "id": "ssr-trigger-02",
-      "phrase": "our SSR pass crashes on attachInternals not being a function",
-      "should_route_to_ssr": true,
-      "expected_shape": "guard-patterns",
-      "rationale": "Directly names the highest-leverage shape-1 crash site the pack documents."
-    },
-    {
-      "id": "ssr-trigger-03",
-      "phrase": "does select-ui work under linkedom",
-      "should_route_to_ssr": true,
-      "expected_shape": "failure-shapes",
-      "rationale": "The pack's core orienting question — 'does X work under SSR'."
-    },
-    {
-      "id": "ssr-trigger-04",
-      "phrase": "admin-sidebar snaps collapsed on every server-rendered page load",
-      "should_route_to_ssr": true,
-      "expected_shape": "failure-shapes",
-      "rationale": "Shape-3 symptom (connect-time measurement treated as confirmed) — the gh#286 precedent."
-    },
-    {
-      "id": "ssr-trigger-05",
-      "phrase": "is gh#284 fixed yet, can we drop the attribute-only SSR registration restriction",
-      "should_route_to_ssr": true,
-      "expected_shape": "status-ledger",
-      "rationale": "Direct status-ledger ask, names the issue and the exact consumer workaround."
-    },
-    {
-      "id": "ssr-trigger-06",
-      "phrase": "how do we test that a new ResizeObserver guard actually works without installing linkedom",
-      "should_route_to_ssr": true,
-      "expected_shape": "test-without-linkedom",
-      "rationale": "Canonical test-methodology ask this pack's most concrete axis exists for."
-    },
-    {
-      "id": "ssr-trigger-07",
-      "phrase": "new ResizeObserver() throws under our DOM-shim SSR environment",
-      "should_route_to_ssr": true,
-      "expected_shape": "guard-patterns",
-      "rationale": "Shape-1 crash, observer-construction variant — guard-patterns §1 shape (a)/(b)/(c)."
-    },
-    {
-      "id": "ssr-trigger-08",
-      "phrase": "table-ui and chart-ui always render empty in our server-rendered HTML even though the data is set",
-      "should_route_to_ssr": true,
-      "expected_shape": "failure-shapes",
-      "rationale": "Shape-4 (property-only components, gh#288), explicitly named as blocked on shape 2."
-    },
-    {
-      "id": "ssr-trigger-09",
-      "phrase": "what's the actual root cause of the SSR content-loss bug, container CEs losing their nested children",
-      "should_route_to_ssr": true,
-      "expected_shape": "failure-shapes",
-      "rationale": "Shape-2 container-CE symptom, the other half of the worked example's shape."
-    },
-    {
-      "id": "ssr-trigger-10",
-      "phrase": "can our app finally delete the 110-line browser-API shim now that 0.8.5 is out",
-      "should_route_to_ssr": true,
-      "expected_shape": "consumer-workarounds",
-      "rationale": "Direct ask about a named consumer workaround's deletability."
-    },
-    {
-      "id": "ssr-trigger-11",
-      "phrase": "is it safe to call getBoundingClientRect() synchronously in connectedCallback",
-      "should_route_to_ssr": true,
-      "expected_shape": "guard-patterns",
-      "rationale": "Shape-3 general-principle ask ('unknown vs confirmed'), independent of any specific component."
-    },
-    {
-      "id": "ssr-trigger-12",
-      "phrase": "document.adoptedStyleSheets is undefined and our component library crashes on import",
-      "should_route_to_ssr": true,
-      "expected_shape": "guard-patterns",
-      "rationale": "Shape-1 crash, the adoptStyles() call site specifically."
-    },
-    {
-      "id": "ssr-adversarial-01",
-      "phrase": "add hydration-aware stamping so connectedCallback stops overwriting existing children",
-      "should_route_to_ssr": false,
-      "expected_alternative": "adia-author",
-      "rationale": "This is IMPLEMENTING the gh#284 fix, not asking whether/why something fails — routes to the builder, not this answers-only pack."
-    },
-    {
-      "id": "ssr-adversarial-02",
-      "phrase": "set up Astro's rendering mode and hydration boundaries for our admin app",
-      "should_route_to_ssr": false,
-      "expected_alternative": "adia-host",
-      "rationale": "Consumer-side host/hydration wiring — explicitly fenced to adia-host in the boundaries section."
-    },
-    {
-      "id": "ssr-adversarial-03",
-      "phrase": "explain how custom element hydration works in general, independent of any specific framework",
-      "should_route_to_ssr": false,
-      "expected_alternative": "general knowledge, no pack",
-      "rationale": "Generic web-components/SSR theory not grounded in THIS repo's own code/issues — explicitly out of scope per the boundaries section."
-    },
-    {
-      "id": "ssr-adversarial-04",
-      "phrase": "the icon registry comes back empty because of a workspace-hoisting import.meta.glob path bug",
-      "should_route_to_ssr": false,
-      "expected_alternative": "adia-author (gh#287, a bundler/dep-optimizer bug, not one of the three SSR lifecycle shapes)",
-      "rationale": "gh#287 is explicitly named in status-ledger.md as unrelated to this pack's failure taxonomy — a near-miss adversarial by design."
-    },
-    {
-      "id": "ssr-adversarial-05",
-      "phrase": "wire up the a2ui generation pipeline to run inside a server-rendered page",
-      "should_route_to_ssr": false,
-      "expected_alternative": "adia-a2ui",
-      "rationale": "A2UI runtime/pipeline concern, not the UIElement lifecycle this pack is scoped to — explicitly fenced in the boundaries section."
-    }
-  ]
+  "positives": [
+    "why does text-ui render empty when we server-render it with Astro",
+    "our SSR pass crashes on attachInternals not being a function",
+    "does select-ui work under linkedom",
+    "admin-sidebar snaps collapsed on every server-rendered page load",
+    "is gh#284 fixed yet, can we drop the attribute-only SSR registration restriction",
+    "how do we test that a new ResizeObserver guard actually works without installing linkedom",
+    "new ResizeObserver() throws under our DOM-shim SSR environment",
+    "table-ui and chart-ui always render empty in our server-rendered HTML even though the data is set",
+    "what's the actual root cause of the SSR content-loss bug, container CEs losing their nested children",
+    "can our app finally delete the 110-line browser-API shim now that 0.8.5 is out",
+    "is it safe to call getBoundingClientRect() synchronously in connectedCallback",
+    "document.adoptedStyleSheets is undefined and our component library crashes on import"
+  ],
+  "negatives": [
+    "add hydration-aware stamping so connectedCallback stops overwriting existing children",
+    "set up Astro's rendering mode and hydration boundaries for our admin app",
+    "explain how custom element hydration works in general, independent of any specific framework",
+    "the icon registry comes back empty because of a workspace-hoisting import.meta.glob path bug",
+    "wire up the a2ui generation pipeline to run inside a server-rendered page",
+    "add a new primitive to the component catalog",
+    "compose the billing settings screen from the catalog",
+    "deploy the latest build to ui-kit.exe.xyz"
+  ],
+  "_measured": {
+    "as_of": "2026-07-18",
+    "scorer": "routing_eval.py (nonoun-plugins/forge)",
+    "f1": 0.957,
+    "precision": 1.0,
+    "recall": 0.917,
+    "exit_code": 0
+  }
 }