@adia-ai/adia-ui-factory 0.8.8 → 0.8.10

package/skills/adia-charts/references/chart-type-catalog.md

@@ -0,0 +1,65 @@
+# chart-ui — the 18 types, by data shape
+
+All types except **sankey** share the `x`/`y` row shape from the main SKILL.md ( `data:
+[{[x]: label, [y]: value, …}]` ). Sankey is the one structural exception, called out below.
+Every entry is normative — grounded in `chart.class.js`'s actual `#render*()` methods, not the
+rendered docs page's prose.
+
+## Axis-based (categorical x, one numeric y)
+
+| `type` | Shape | When |
+| --- | --- | --- |
+| `bar` (default) | vertical bars, one series | the default choice for "compare N categories" |
+| `line` | line + soft area fill, `smooth` prop tunes the curve (0 = straight segments, 1 = max spline) | a single trend over an ordered axis (time, sequence) |
+| `area` | same renderer family as `line` with the fill emphasized | same use as `line`; visually heavier — prefer for one hero series, not several overlaid |
+| `sparkline` | line variant with minimal chrome, wrapped in `[data-sparkline]` | inline/compact — the canonical use is `<chart-ui slot="chart" type="sparkline">` inside `<stat-ui>` |
+| `scatter` | dots plotted at **evenly-spaced index positions** along x, height by `y` value | index-based, not a true bivariate (x-value, y-value) scatter — `x` still supplies the categorical label, not a second numeric axis. For a real two-numeric-axis scatter, none of the 18 types provide it as-is |
+
+## Categorical / part-of-whole
+
+| `type` | Shape | When |
+| --- | --- | --- |
+| `pie` | full-circle slices, one value key | share-of-total across few categories |
+| `donut` | ring slices (inner+outer radius); `radius` prop rounds slice corners | same as pie with a center hole — pairs well with a total/label in the empty center |
+| `segments` | ONE horizontal bar split into proportional colored slices | compact in-card distribution widget where a full pie is too heavy |
+| `treemap` | flat squarified rect tiling, area ∝ value; `x` labels each tile | many categories where relative size matters more than precise comparison; not nested (no `children` hierarchy yet) |
+| `funnel` | trapezoid stages, **array order = funnel order top-to-bottom** (not sorted by value) — auto-computes a drop-off % per stage vs. the first | ordered-stage conversion/dropoff (signup → activation → purchase) |
+
+## Radial
+
+| `type` | Shape | When |
+| --- | --- | --- |
+| `radar` | polygon, one series, `x` labels each spoke | multi-attribute comparison of a single subject (skill/score breakdown) |
+| `radial-bar` | concentric rings, one ring per datum, sweep ∝ value/max | comparing several progress-style metrics compactly (a "multi progress ring" widget) |
+| `gauge` | half-donut with center value | one KPI vs. a target — reads `max` from the first datum (`data[0].max`) if present; otherwise a single-row `data` treats the value as-is, multi-row `data` treats row 0 as numerator and the sum of all rows as the denominator ("X of Y") |
+
+## Multi-series (comma-separated `y`)
+
+| `type` | Shape | When |
+| --- | --- | --- |
+| `stacked-bar` | bars stacked per category, one segment per `y` key | part-of-whole across categories where the total also matters |
+| `grouped-bar` | bars side-by-side per category, one bar per `y` key | comparing series without summing them |
+| `multi-line` | one line per `y` key, shared axes | comparing several trends over the same axis |
+| `composed` | **bar + line combo** — the FIRST `y` key renders as bars, the SECOND as an overlaid line; a third+ key is ignored | two related metrics on different visual channels (e.g. revenue bars + margin % line) |
+
+Multi-series types (`stacked-bar` / `grouped-bar` / `multi-line` / `radial-bar`, plus `pie` /
+`donut`) auto-render an **internal legend** below the chart when no external
+`chart-legend-ui[for]` targets it — single-series types (`bar`, `line`, `area`, `scatter`,
+`sparkline`, `radar`, `gauge`, `funnel`, `treemap`, `segments`) never do, because there is only
+one series to label.
+
+## Sankey — the one non-`x`/`y` shape
+
+```html
+<chart-ui type="sankey"></chart-ui>
+```
+```js
+chartEl.data = [
+  { source: 'Visit',   target: 'Signup',  value: 480 },
+  { source: 'Signup',  target: 'Trial',   value: 210 },
+];
+```
+
+`x`/`y` attributes are unused for sankey. Each row is a flow link; node columns (left = sources,
+right = targets) and node heights are auto-derived from the unique `source`/`target` values and
+their summed `value` — `from`/`to`/`v` are accepted as aliases for `source`/`target`/`value`.

package/skills/adia-charts/references/composition-and-theming.md

@@ -0,0 +1,113 @@
+# Chart family — tokens, events, and the a11y contract
+
+## Token roster (`chart-ui`, `@scope (chart-ui)`)
+
+| Token | Controls | Default |
+| --- | --- | --- |
+| `--chart-fg` / `--chart-label` / `--chart-value` | axis text, tick labels, value overlays | `--md-sys-color-neutral-*` roles |
+| `--chart-bar` / `--chart-line` / `--chart-dot` | series fill/stroke when NOT per-series-keyed (single-series types) | `--md-sys-color-primary` |
+| `--chart-bar-hover` | bar hover fill | `--a-primary-bg-hover` |
+| `--chart-grid` / `--chart-axis` / `--chart-border` | gridlines, axis line, empty-state dashed border | `--md-sys-color-neutral-outline-variant` family |
+| `--chart-avg` | the optional overlaid average line (bar/line) | `--md-sys-color-warning` |
+| `--chart-area-opacity` | line-chart area fill opacity (`type="line"`'s `[data-area]`) | `0.15` |
+| `--chart-area-fill-opacity` | `type="area"`'s OWN fill opacity — overrides `--chart-area-opacity` for that type so the fill reads as the dominant series, not a soft accent | `0.35` |
+| `--chart-line-width` | line/multi-line stroke width | `2` |
+| `--chart-radius` | internal-legend swatch DOT corner radius only (`[data-legend-dot]`) — NOT the bar/donut/treemap corner radius; that fallback chain is `radius` PROP → `--a-radius` (computed, ancestor-set) → `6`, resolved per-render by `#resolveRadius()` | `4` |
+| `--chart-max-height` | responsive height cap | `28rem` |
+| `--chart-dot-stroke` | line-chart dot outline color | `--md-sys-color-neutral-background` |
+| `--chart-duration` / `--chart-easing` | hover/transition timing | `--a-duration-fast` / `--a-easing` |
+| `--chart-legend-size` / `--chart-legend-dot-size` | internal auto-legend sizing (pie/donut/stacked-bar/grouped-bar/multi-line/radial-bar) | — |
+| `--chart-segments-gap` / `--chart-pie-gap` | gap between segments/pie slices | `2px` / `1.25px` |
+| `--chart-currency-prefix` | `format="currency"` prefix string | `"$"` (falls back in JS — don't rely on a `:where(:scope)` default cascading) |
+| `--chart-perf-budget` | row count before the one-shot perf warning fires | `5000` |
+| `--chart-0` … `--chart-9` | the 10-slot categorical ramp, aliasing `--a-data-0`…`--a-data-9` | theme-stable data palette |
+
+Every color-bearing token above resolves through `--md-sys-color-*` or `--a-*` — never author a
+raw hex/`oklch()` override; recolor by overriding the alias, same law `adia-tokens` states for
+every other surface.
+
+## Per-series color override — `--color-{key}`
+
+For multi-series charts (`y="revenue,users"`), `chart-ui` injects one inline custom property per
+declared series onto the HOST at render time: `--color-revenue: var(--chart-0)`,
+`--color-users: var(--chart-1)`, etc. (slot = index into the 10-slot ramp, wrapping past 10).
+Every series-keyed SVG element's fill/stroke reads `var(--color-{key}, var(--chart-{slot}))`.
+
+To recolor ONE named series without touching the rest, set `--color-{key}` on the chart or any
+ancestor:
+
+```css
+chart-ui#revenue-trend { --color-users: var(--md-sys-color-tertiary); }
+```
+
+`chart-legend-ui` reads the SAME `--color-{key}` variable for its swatches (falling back to
+`--a-data-{slot}` directly, since a standalone legend may have no chart-ui ancestor to inherit
+the chart-scoped `--chart-{N}` alias from) — override once, chart and legend swatch stay in
+sync automatically.
+
+## Event contract
+
+All four event NAMES bubble and are shared by `chart-ui` and `heatmap-ui` (heatmap re-emits its
+own `cell-hover`/`cell-click` under these same names so a listener never needs to branch on
+chart kind) — the DETAIL shape differs in the two ways called out below the table, so treat
+`chart-ui`'s shape as the fuller case, not the shared contract:
+
+| Event | Fires | Detail |
+| --- | --- | --- |
+| `chart-hover` | pointer enters a datum (bar/dot/slice/cell); re-fires only when the hovered datum CHANGES | `{ label, value, pct, series, slot, payload, pointerX, pointerY }` |
+| `chart-leave` | pointer leaves the plot area, or a previously-hovered datum with nothing new entering | none |
+| `chart-select` | click/tap on a datum, or Enter/Space on the keyboard-focused datum | same shape as `chart-hover` (pointer coords are synthesized at the focused datum's center for keyboard-triggered selects, so `pointerX`/`pointerY` are always populated) |
+| `legend-update` | the chart's internal `legendData` payload regenerates | none — signal-only; `chart-legend-ui[for]` listens for this to repaint (chart-ui only — see the wiring section below) |
+
+`detail.payload` is an array, one entry per series AT THE SAME X COLUMN (multi-series types) —
+`{ series, label, value, pct, slot, hovered }` per entry — so a single `tooltip-ui` can render
+every series' value for the hovered category, not just the one datum the pointer is literally
+over. Single-series types populate `payload` with one entry mirroring the top-level fields.
+**`heatmap-ui`'s detail has no `payload` field at all** (cells are independent, not columns of a
+shared series) — a shared tooltip must treat `payload` as optional. `heatmap-ui` also re-fires
+`chart-hover` on every pointer move inside the SAME cell (to reposition a pointer-follow
+tooltip), which the "only fires when the hovered datum changes" row above describes for
+`chart-ui`, not for `heatmap-ui` — dedupe on `(r, c)` if a listener needs change-only semantics
+for heatmap cells.
+
+Wire ONE `tooltip-ui[follows="pointer"][for="chart-id"]` rather than a per-chart-kind listener —
+its presence suppresses `chart-ui`'s internal tooltip popup automatically (detected via
+`document.querySelector('tooltip-ui[follows="pointer"][for=...]')`), so there's no double-render
+to guard against.
+
+## `chart-legend-ui` wiring
+
+- `[for="chart-id"]` auto-mirrors **`chart-ui` targets only**: the legend reads the target's
+  `.legendData` property and re-paints on that target's `legend-update` event. Requires the
+  chart to have a matching `id`. Pointing `[for]` at a `heatmap-ui` id silently resolves to an
+  empty legend — heatmap-ui never sets `.legendData` or dispatches `legend-update`; use its own
+  built-in Less/More strip (`no-legend` prop to hide it) instead.
+- `items='[{"key","label","slot?","pct?"}, …]'` is explicit data and ALWAYS wins over `[for]`
+  when both are present — use it for a legend with no live chart-ui counterpart.
+- Clicking a row fires `toggle` (`{ key, active, mode }`); when wired via `[for]`, `chart-ui`
+  listens for this on `document` and hides (`on-toggle="hide"`, default) or fades
+  (`on-toggle="opacity"`) that series — no manual event handler needed for the common case.
+- `static` renders non-interactive `badge-ui` rows (no `role`/`tabindex`, no toggle affordance)
+  for a legend that's pure labeling, not a filter control — rows are `badge-ui` chips in both
+  modes (composed, not hand-rolled `<span>`s, since 2026-05-01).
+- `shape="dot|square|line|dashed"` — `line`/`dashed` exist because those swatch shapes aren't
+  representable as an icon glyph; match `line`/`multi-line` charts to `shape="line"`,
+  categorical charts to `dot` or `square`.
+
+## Accessibility & keyboard
+
+`chart-ui` sets `role="img"` and an auto-generated `aria-label` ("`{type} chart`") unless the
+author supplies their own. It is natively keyboard-navigable (`tabindex="0"` auto-applied):
+
+| Key | Action |
+| --- | --- |
+| `ArrowRight` / `ArrowDown` | move virtual focus to the next datum |
+| `ArrowLeft` / `ArrowUp` | move virtual focus to the previous datum |
+| `Home` / `End` | jump to first / last datum |
+| `Enter` / `Space` | fire `chart-select` for the focused datum |
+| `Escape` | clear focus, fire `chart-leave` |
+
+Keyboard focus emits the SAME `chart-hover` event the pointer path uses, so a
+`tooltip-ui[follows="pointer"][for]` tracks keyboard navigation for free — author it once and
+both interaction modes work. Per-datum focus paints via `[data-a11y-focus]` + the standard
+`--a-focus-ring` recipe; nothing extra to author.

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

@@ -0,0 +1,21 @@
+{
+  "skill": "adia-compose",
+  "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, with rationale) plus the SKILL.md description's own trigger/NOT-fence language.",
+  "cases": [
+    { "id": "t01", "prompt": "Build a settings screen for our app", "expect": "trigger" },
+    { "id": "t02", "prompt": "Generate UI for a dashboard from this PRD, as part of the build right now", "expect": "trigger" },
+    { "id": "t03", "prompt": "Compose a form from the catalog", "expect": "trigger" },
+    { "id": "t04", "prompt": "Turn this PRD into a working screen", "expect": "trigger" },
+    { "id": "t05", "prompt": "Convert this Figma export into adia-ui markup for our checkout app", "expect": "trigger" },
+    { "id": "t06", "prompt": "As a user I want to filter my orders — build the screen for that", "expect": "trigger" },
+    { "id": "t07", "prompt": "Theme this screen with our brand tokens and add dark mode", "expect": "trigger" },
+    { "id": "t08", "prompt": "The catalog has nothing for a rating stepper — author a project component in our checkout app to compose it", "expect": "trigger" },
+    { "id": "t09", "prompt": "Compose a confirmation modal flow for deleting a record", "expect": "trigger" },
+    { "id": "n01", "prompt": "Wire up the a2ui runtime so end users can generate their own dashboard layout at runtime", "expect": "no-trigger", "owner": "adia-genui" },
+    { "id": "n02", "prompt": "Pick a shell for the admin app with a sidebar and topbar", "expect": "no-trigger", "owner": "adia-shells" },
+    { "id": "n03", "prompt": "Set up index.html and SSR registration for our Next.js adia-ui app", "expect": "no-trigger", "owner": "adia-host" },
+    { "id": "n04", "prompt": "Add a new primitive component to packages/web-components in the adia-ui monorepo", "expect": "no-trigger", "owner": "adia-author" },
+    { "id": "n05", "prompt": "Run the browser QA gate on the settings screen we just built and check for console errors", "expect": "no-trigger", "owner": "adia-verify" },
+    { "id": "n06", "prompt": "Wire up state hydration for this island using signals", "expect": "no-trigger", "owner": "adia-data" }
+  ]
+}

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

@@ -1,216 +1,212 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "name": "adia-compose routing accuracy corpus",
-  "version": "1.0.0",
+  "version": "2.1.0",
   "purpose": "Routing-eval corpus for adia-compose (adia-ui-factory plugin). Each phrase declares whether adia-compose 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-compose routing — does this phrase activate adia-compose (build-time, one-shot screen construction from the light-DOM catalog)?",
-
-  "minimums_per_spec": {
-    "trigger_phrases": 21,
-    "adversarial_phrases": 6,
-    "task_shapes_covered": "generic-build, dashboard-generation, form-composition, prd-to-ui, spec-to-ui, mockup-to-ui, user-story-to-ui, navigation-pattern, theming, project-component-authoring, overlay-composition",
-    "adversarial_fraction": "22%"
-  },
-
+  "scope": "adia-compose routing \u2014 does this phrase activate adia-compose (build-time, one-shot screen construction from the light-DOM catalog)?",
   "phrases": [
     {
       "id": "compose-generic-01",
       "phrase": "build a settings screen for our app",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "generic-build",
-      "rationale": "Canonical 'build a screen' ask — the skill's own description phrase."
+      "rationale": "Canonical 'build a screen' ask \u2014 the skill's own description phrase."
     },
     {
       "id": "compose-generic-02",
       "phrase": "generate UI for a dashboard",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "dashboard-generation",
       "rationale": "'generate UI for' is the skill description's own trigger phrase."
     },
     {
       "id": "compose-generic-03",
       "phrase": "compose a form from the catalog",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "form-composition",
-      "rationale": "Explicit 'compose ... from the catalog' — the skill's core loop."
+      "rationale": "Explicit 'compose ... from the catalog' \u2014 the skill's core loop."
     },
     {
       "id": "compose-prd-01",
       "phrase": "turn this PRD into a working screen",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "prd-to-ui",
-      "rationale": "PRD-shaped input needing UI — triggers the spec-to-ui precondition gate."
+      "rationale": "PRD-shaped input needing UI \u2014 triggers the spec-to-ui precondition gate."
     },
     {
       "id": "compose-spec-01",
-      "phrase": "here's the product spec — build the UI for it",
-      "should_route_to_compose": true,
+      "phrase": "here's the product spec \u2014 build the UI for it",
+      "expected": "adia-compose",
       "expected_shape": "spec-to-ui",
       "rationale": "Spec-shaped input needing UI, per the skill description's 'PRD/spec/mockup needs UI'."
     },
     {
       "id": "compose-mockup-01",
       "phrase": "implement this mockup screenshot as adia-ui components",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "mockup-to-ui",
       "rationale": "Mockup-to-components composition, explicit adia-ui target."
     },
     {
       "id": "compose-mockup-02",
       "phrase": "convert this Figma export into adia-ui markup for our checkout app",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "mockup-to-ui",
       "rationale": "Consumer-side mockup composition into catalog primitives (distinct from figma-generate-* MCP skills, which push code INTO Figma, not the reverse)."
     },
     {
       "id": "compose-schema-01",
       "phrase": "given this user schema, generate the settings form",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "spec-to-ui",
-      "rationale": "Schema-shaped input driving form generation — spec-to-ui-reasoning gate applies."
+      "rationale": "Schema-shaped input driving form generation \u2014 spec-to-ui-reasoning gate applies."
     },
     {
       "id": "compose-userstory-01",
-      "phrase": "as a user I want to filter my orders — build the screen for that",
-      "should_route_to_compose": true,
+      "phrase": "as a user I want to filter my orders \u2014 build the screen for that",
+      "expected": "adia-compose",
       "expected_shape": "user-story-to-ui",
       "rationale": "User-story input needing a built screen."
     },
     {
       "id": "compose-dashboard-02",
       "phrase": "put together an analytics dashboard with charts and a legend",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "dashboard-generation",
       "rationale": "Dashboard build using chart-ui/chart-legend-ui catalog primitives."
     },
     {
       "id": "compose-nav-01",
       "phrase": "compose the sidebar navigation pattern for the app",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "navigation-pattern",
-      "rationale": "Navigation pattern composition — nav-ui/nav-item-ui selection, per description's 'navigation pattern' trigger."
+      "rationale": "Navigation pattern composition \u2014 nav-ui/nav-item-ui selection, per description's 'navigation pattern' trigger."
     },
     {
       "id": "compose-nav-02",
       "phrase": "build a command palette for quick actions",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "navigation-pattern",
-      "rationale": "command-ui composition — a named component-selection pick in the skill."
+      "rationale": "command-ui composition \u2014 a named component-selection pick in the skill."
     },
     {
       "id": "compose-form-02",
       "phrase": "wire up a multi-step form using field-ui and select-ui",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "form-composition",
-      "rationale": "Explicit catalog primitive names (field-ui, select-ui) — screen markup composition."
+      "rationale": "Explicit catalog primitive names (field-ui, select-ui) \u2014 screen markup composition."
     },
     {
       "id": "compose-theme-01",
       "phrase": "theme this screen with our brand tokens and add dark mode",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "theming",
-      "rationale": "Theming via --a-* tokens and scheme toggle — the skill's step 4."
+      "rationale": "Theming via --a-* tokens and scheme toggle \u2014 the skill's step 4."
     },
     {
       "id": "compose-theme-02",
       "phrase": "apply the --a-* token set and wire the scheme toggle for this page",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "theming",
       "rationale": "Direct --a-* token + <toggle-scheme-ui> mention, matches description's 'themes via --a-* tokens'."
     },
     {
       "id": "compose-project-comp-01",
-      "phrase": "the catalog has nothing for a rating stepper — author a project component in our checkout app to compose it",
-      "should_route_to_compose": true,
+      "phrase": "the catalog has nothing for a rating stepper \u2014 author a project component in our checkout app to compose it",
+      "expected": "adia-compose",
       "expected_shape": "project-component-authoring",
-      "rationale": "'Author only what's missing' — a light-DOM PROJECT component in a consumer app, step 3 of the compose loop (distinct from adia-author's framework primitives, see compose-adv-04)."
+      "rationale": "'Author only what's missing' \u2014 a light-DOM PROJECT component in a consumer app, step 3 of the compose loop (distinct from adia-author's framework primitives, see compose-adv-04)."
     },
     {
       "id": "compose-project-comp-02",
       "phrase": "no primitive fits this bespoke billing-summary widget; build it as a project component for our app",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "project-component-authoring",
       "rationale": "Consumer-app project component authored to fill a catalog gap, still inside adia-compose's remit."
     },
     {
       "id": "compose-empty-01",
       "phrase": "add an empty state to the search results screen",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "generic-build",
-      "rationale": "empty-state-ui selection inside an existing screen — ordinary composition edit."
+      "rationale": "empty-state-ui selection inside an existing screen \u2014 ordinary composition edit."
     },
     {
       "id": "compose-table-01",
       "phrase": "build a data table screen listing all invoices",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "generic-build",
       "rationale": "table-ui composition for a new screen."
     },
     {
       "id": "compose-modal-01",
       "phrase": "compose a confirmation modal flow for deleting a record",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "overlay-composition",
       "rationale": "confirm-dialog-ui/modal-ui overlay selection and wiring."
     },
     {
       "id": "compose-genui-boundary-01",
       "phrase": "generate UI for a one-off pricing page from this spec, right now, as part of the build",
-      "should_route_to_compose": true,
+      "expected": "adia-compose",
       "expected_shape": "prd-to-ui",
-      "rationale": "Boundary case (direction 1 of 2, paired with compose-adv-01): 'generate UI' language, but the ask is a single build-time authoring pass, not an end-user-triggered runtime experience — stays adia-compose."
+      "rationale": "Boundary case (direction 1 of 2, paired with compose-adv-01): 'generate UI' language, but the ask is a single build-time authoring pass, not an end-user-triggered runtime experience \u2014 stays adia-compose."
     },
-
     {
       "id": "compose-adv-01",
       "phrase": "wire up the a2ui runtime so end users can generate their own dashboard layout at runtime",
-      "should_route_to_compose": false,
-      "expected_alternative": "adia-genui (adia-factory plugin)",
-      "rationale": "Adversarial (direction 2 of 2, paired with compose-genui-boundary-01) — END USERS trigger generation at runtime via a2ui-root/gen-root; adia-compose's description NEG-fences 'runtime gen-UI (adia-genui)'."
+      "expected": "adia-genui",
+      "rationale": "Adversarial (direction 2 of 2, paired with compose-genui-boundary-01) \u2014 END USERS trigger generation at runtime via a2ui-root/gen-root; adia-compose's description NEG-fences 'runtime gen-UI (adia-genui)'.",
+      "expected_alternative_raw": "adia-genui (adia-factory plugin)"
     },
     {
       "id": "compose-adv-02",
       "phrase": "pick a shell for the admin app with a sidebar and topbar",
-      "should_route_to_compose": false,
-      "expected_alternative": "adia-shells (adia-factory plugin)",
-      "rationale": "Adversarial — shell CHROME selection (admin/chat/editor/simple/embed), not screen content inside one; adia-compose's description NEG-fences 'shell chrome (adia-shells)'."
+      "expected": "adia-shells",
+      "rationale": "Adversarial \u2014 shell CHROME selection (admin/chat/editor/simple/embed), not screen content inside one; adia-compose's description NEG-fences 'shell chrome (adia-shells)'.",
+      "expected_alternative_raw": "adia-shells (adia-factory plugin)"
     },
     {
       "id": "compose-adv-03",
       "phrase": "set up index.html and SSR registration for our Next.js adia-ui app",
-      "should_route_to_compose": false,
-      "expected_alternative": "adia-host (adia-factory plugin)",
-      "rationale": "Adversarial — host bootstrap/registration/SSR wiring; adia-compose's description NEG-fences 'host wiring (adia-host)'."
+      "expected": "adia-host",
+      "rationale": "Adversarial \u2014 host bootstrap/registration/SSR wiring; adia-compose's description NEG-fences 'host wiring (adia-host)'.",
+      "expected_alternative_raw": "adia-host (adia-factory plugin)"
     },
     {
       "id": "compose-adv-04",
       "phrase": "add a new primitive component to packages/web-components in the adia-ui monorepo",
-      "should_route_to_compose": false,
-      "expected_alternative": "adia-author (adia-ui-forge plugin)",
-      "rationale": "Adversarial — authoring a FRAMEWORK primitive inside the monorepo itself, not a project component in a consumer app; this is adia-author's remit ('primitives, shells, demos, component yaml SoTs'), the subtle authoring-side-of-the-house boundary paired with compose-project-comp-01/02."
+      "expected": "adia-author",
+      "rationale": "Adversarial \u2014 authoring a FRAMEWORK primitive inside the monorepo itself, not a project component in a consumer app; this is adia-author's remit ('primitives, shells, demos, component yaml SoTs'), the subtle authoring-side-of-the-house boundary paired with compose-project-comp-01/02.",
+      "expected_alternative_raw": "adia-author (adia-ui-forge plugin)"
     },
     {
       "id": "compose-adv-05",
       "phrase": "run the browser QA gate on the settings screen we just built and check for console errors",
-      "should_route_to_compose": false,
-      "expected_alternative": "adia-verify (adia-factory plugin)",
-      "rationale": "Adversarial — QA of an already-built screen (headless render, console errors, a11y checks), not composing or fixing the UI; adia-verify's description owns 'verify/QA this page'."
+      "expected": "adia-verify",
+      "rationale": "Adversarial \u2014 QA of an already-built screen (headless render, console errors, a11y checks), not composing or fixing the UI; adia-verify's description owns 'verify/QA this page'.",
+      "expected_alternative_raw": "adia-verify (adia-factory plugin)"
     },
     {
       "id": "compose-adv-06",
       "phrase": "wire up state hydration for this island using signals",
-      "should_route_to_compose": false,
-      "expected_alternative": "adia-data (adia-factory plugin)",
-      "rationale": "Adversarial — data/state/hydration pattern choice, not screen markup; adia-data's description owns 'wire up the data' / 'hydrate the island'."
+      "expected": "adia-data",
+      "rationale": "Adversarial \u2014 data/state/hydration pattern choice, not screen markup; adia-data's description owns 'wire up the data' / 'hydrate the island'.",
+      "expected_alternative_raw": "adia-data (adia-factory plugin)"
     }
   ],
-
+  "minimums_per_spec": {
+    "trigger_phrases": 21,
+    "adversarial_phrases": 6,
+    "task_shapes_covered": "generic-build, dashboard-generation, form-composition, prd-to-ui, spec-to-ui, mockup-to-ui, user-story-to-ui, navigation-pattern, theming, project-component-authoring, overlay-composition",
+    "adversarial_fraction": "22%"
+  },
   "evaluator_notes": {
     "current_state": "27 cases (21 trigger + 6 adversarial). Each of the 11 task shapes has at least 1 trigger case; the two highest-collision task shapes (dashboard-generation, form-composition, navigation-pattern) get 2 each. The adia-genui boundary is covered in both directions (compose-genui-boundary-01 stays adia-compose; compose-adv-01 routes away to adia-genui) since the build-time/runtime distinction is the sharpest and most-collided fence in the factory plugin.",
-    "promotion_criteria": "Promote to a CI gate (warn → hard-fail) when F1 ≥ 0.85 on this corpus across 3+ consecutive runs without description edits.",
+    "promotion_criteria": "Promote to a CI gate (warn \u2192 hard-fail) when F1 \u2265 0.85 on this corpus across 3+ consecutive runs without description edits.",
     "review_cadence": "Re-run on every adia-compose description edit. Add 1-2 new cases per checkpoint reflecting newly-observed routing failure modes, especially at the adia-genui and adia-author (forge) fences.",
-    "known_limitations": "compose-project-comp-01/02 vs compose-adv-04 (adia-author) share heavy token overlap ('primitive', 'component', 'author') — the heuristic TF-IDF scorer may not disambiguate monorepo-internal authoring from consumer-app project-component authoring; the harness's live project-context probe (`isFrameworkMonorepo`) disambiguates this in practice, which the heuristic corpus cannot see."
+    "known_limitations": "compose-project-comp-01/02 vs compose-adv-04 (adia-author) share heavy token overlap ('primitive', 'component', 'author') \u2014 the heuristic TF-IDF scorer may not disambiguate monorepo-internal authoring from consumer-app project-component authoring; the harness's live project-context probe (`isFrameworkMonorepo`) disambiguates this in practice, which the heuristic corpus cannot see."
   }
 }

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

@@ -0,0 +1,20 @@
+{
+  "skill": "adia-data",
+  "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, with rationale) plus the SKILL.md description's own trigger/NOT-fence language.",
+  "cases": [
+    { "id": "t01", "prompt": "Wire up the data for this dashboard's summary cards", "expect": "trigger" },
+    { "id": "t02", "prompt": "Pick a state pattern for this table — signals or DataClient?", "expect": "trigger" },
+    { "id": "t03", "prompt": "Add CRUD with undo support to the invoice list", "expect": "trigger" },
+    { "id": "t04", "prompt": "Connect the table-ui to the backend via typed reads and pure mappers", "expect": "trigger" },
+    { "id": "t05", "prompt": "Why does my chart-ui drop rows appended after connect?", "expect": "trigger" },
+    { "id": "t06", "prompt": "The state change isn't round-tripping through the signal — mutate doesn't update the projection", "expect": "trigger" },
+    { "id": "t07", "prompt": "Seed the server-fetched props into this SPA island's client-boot state", "expect": "trigger" },
+    { "id": "t08", "prompt": "The SSR framework already fetches the data — wire the initial props into the components", "expect": "trigger" },
+    { "id": "n01", "prompt": "Register the client-side components for this new SPA host", "expect": "no-trigger", "owner": "adia-host" },
+    { "id": "n02", "prompt": "Getting 'HTMLElement is not defined' after upgrading to Next.js", "expect": "no-trigger", "owner": "adia-host" },
+    { "id": "n03", "prompt": "Manage the state for the streaming chat responses in the chat box", "expect": "no-trigger", "owner": "adia-llm" },
+    { "id": "n04", "prompt": "Build the markup for this data table's screen", "expect": "no-trigger", "owner": "adia-compose" },
+    { "id": "n05", "prompt": "Pick the on-disk shape for this new rollup app", "expect": "no-trigger", "owner": "adia-project" },
+    { "id": "n06", "prompt": "Fix the double route owner — router-ui is mounted alongside the framework's router", "expect": "no-trigger", "owner": "adia-host" }
+  ]
+}