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

package/skills/{adia-llm-internals → llm-client-maintenance}/evals/routing-corpus.json

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

package/skills/{adia-release → package-release}/SKILL.md

@@ -1,24 +1,24 @@
 ---
-name: adia-release
+name: package-release
 description: >-
   Release engineering for the @adia-ai lockstep monorepo. Use when asked to
   cut and ship a release, promote [Unreleased] CHANGELOG entries, tag and push the
-  lockstep packages to origin, publish a 13-package release (11
-  npm libraries + 2 Claude Code plugins, as of gh#607 — see
+  lockstep packages to origin, publish a 16-package release (14
+  npm libraries + 2 Claude Code plugins, as of gh#1240's MCP fold — see
   scripts/package-paths.mjs), batch-push piled-up release commits,
   recover a cut that landed wrong or whose publish workflows didn't fire,
   fix a check:lockstep bump failure or an F-N1 CHANGELOG-coverage warning,
   verify the release gates without cutting anything, or author release
   notes/a MIGRATION GUIDE section for a breaking change. NOT for
-  consumer-app migration sweeps (adia-migrate) or exe.dev VM ops
-  (adia-deploy).
+  consumer-app migration sweeps (app-migration) or exe.dev VM ops
+  (site-deployment).
 disable-model-invocation: false
 user-invocable: true
 ---
 
-# adia-release
+# package-release
 
-Release engineering for an @adia-ai-style lockstep monorepo: the `@adia-ai/*` packages on the roster (`scripts/package-paths.mjs`, the single source — 13 lockstep as of gh#607: 11 npm libraries plus the 2 Claude Code plugins under `packages/plugins/*`) version and publish together (class A; the plugins joined the lockstep 2026-07-15 after class-B independence let npm drift a full harness-reset behind the repo). Class B (independent versioning) has one member — `@adia-ai/adia-plugins` (gh#1133/gh#1160, ADR-0045), the npm-sourced marketplace manifest package, marked `lockstep: false` on the roster; it cuts on its own version line and its own tag, never the umbrella ([`references/independent-package-release.md`](references/independent-package-release.md)). The substrate — `scripts/release/*`, the `check:*` gates, the tag-triggered publish workflows — encodes the invariants; this skill routes, sequences, and stops at the judgment calls.
+Release engineering for an @adia-ai-style lockstep monorepo: the `@adia-ai/*` packages on the roster (`scripts/package-paths.mjs`, the single source — 16 lockstep as of gh#1240's MCP-distribution fold (ADR-0048 P5, amended): 14 npm libraries plus the 2 Claude Code plugins under `packages/plugins/*`; 6 of those libraries are the old-name shims marked `shim: true`, which ride the 0.8.37 cut once and are deleted in the P7 follow-up, taking the count to 10) version and publish together (class A; the plugins joined the lockstep 2026-07-15 after class-B independence let npm drift a full harness-reset behind the repo). Class B (independent versioning) has one member — `@adia-ai/adia-plugins` (gh#1133/gh#1160, ADR-0045), the npm-sourced marketplace manifest package, marked `lockstep: false` on the roster; it cuts on its own version line and its own tag, never the umbrella ([`references/independent-package-release.md`](references/independent-package-release.md)). The substrate — `scripts/release/*`, the `check:*` gates, the tag-triggered publish workflows — encodes the invariants; this skill routes, sequences, and stops at the judgment calls.
 
 ## Authorization — one go, gates do the rest (operator ruling 2026-07-17)
 
@@ -26,20 +26,20 @@ Release engineering for an @adia-ai-style lockstep monorepo: the `@adia-ai/*` pa
 
 This replaced the 4-checkpoint sign-off ceremony after the v0.8.5 cut (2026-07-17): ~40 minutes of approval relays that produced zero safety — every real protection had already fired deterministically (the `release-pretag-docs-gate` hook, the pre-push F-N1 trip-wire, the one-tag-per-push rule, the registry verify). Those deterministic gates are untouched and remain non-skippable: **an F-N1 error hard-stops unconditionally — no flag, no instruction wording, bypasses it.**
 
-**Releases run INLINE in the operator's session by default.** Do not dispatch a subagent to run an interactive release — a dispatched seat cannot receive the operator's words directly, which the v0.8.5 cut proved structurally deadlocks on any consent question (the relay-refusal loop). The `release-builder` agent exists for UNATTENDED contexts only (scheduled/batch/CI cuts), where the dispatch itself carries the operator's authorization.
+**Releases run INLINE in the operator's session by default.** Do not dispatch a subagent to run an interactive release — a dispatched seat cannot receive the operator's words directly, which the v0.8.5 cut proved structurally deadlocks on any consent question (the relay-refusal loop). The `package-release-agent` agent exists for UNATTENDED contexts only (scheduled/batch/CI cuts), where the dispatch itself carries the operator's authorization.
 
 Mechanics: `release-pack.mjs --go` auto-confirms all checkpoints (it equals `--yes --push --publish`); the evidence blocks still print as a log — the audit trail survives, nothing waits on input. The granular flags remain for cautious manual runs; interactive prompts fire for whatever flag is absent. A cosmetic F-N1 warn still refuses auto-confirmation at the push boundary — with Step 4f (mechanized pre-tag coverage) warns should be extinct, so one appearing means something novel: treat it as a gate failure, not ceremony.
 
 ## Invariants (class-A lockstep cut)
 
-1. **Lockstep coherence** — every roster package bumps together (`check:lockstep`; the roster lives in `scripts/package-paths.mjs`, currently `web-components`, `web-modules`, `llm`, `agent`, `persona`, `a2ui-{runtime,compose,corpus,mcp,retrieval,validator}`, and the plugins `adia-ui-{factory,forge}`) (each plugin's `.claude-plugin/plugin.json` version moves with its package.json — `bump.mjs` handles both; `verify:plugins` gates the sync).
+1. **Lockstep coherence** — every roster package bumps together (`check:lockstep`). **The roster is `scripts/package-paths.mjs`'s `PACKAGE_ROSTER` — read it, never a copy.** This line used to enumerate the names inline and went stale the first time the roster moved (ADR-0048 P4 added a package while the list still read the pre-split six); a name list here has no gate behind it, so it can only decay. Each plugin's `.claude-plugin/plugin.json` version moves with its package.json — `bump.mjs` handles both; `verify:plugins` gates the sync.
 2. **PATCH-cut asymmetry** — internal `@adia-ai/*` ranges hold at `^X.Y.0` during PATCH cuts; only MINOR bumps the floor. `^0.0.x` is forbidden (pre-1.0 caret locks exact — shipped a real stale-sibling bug).
 3. **Release commits land via PR, never a direct push to `main`** (repo policy, operator ruling 2026-07-12): commit on `release/vX.Y.Z` → PR → CI → merge — THEN tag at `main`'s post-merge HEAD, not at the bump commit; post-bump fixes merge before tagging and belong in the tarball. Exception: batch push tags each version at its own release-merge SHA.
-4. **One umbrella + one per-package tag per cut** (`vX.Y.Z` + 13 × `<pkg>-vX.Y.Z`, one per lockstep-roster package — `scripts/package-paths.mjs`); publish workflows key off the per-package tags. Push tags **one per `git push`** — a batched multi-tag push drops the trigger event.
+4. **One umbrella + one per-package tag per cut** (`vX.Y.Z` + 16 × `<pkg>-vX.Y.Z`, one per lockstep-roster package — `scripts/package-paths.mjs`); publish workflows key off the per-package tags. Push tags **one per `git push`** — a batched multi-tag push drops the trigger event.
 5. **F-N1 (`check:release --all-pending`) per-package clean** — the umbrella-tag mismatch error is expected noise. Coverage is mechanized at cut time: Step 4f (`check-release.mjs --pending-version X.Y.Z --fix`) runs the SAME matcher pre-PR and auto-appends verified Maintenance bullets, so a post-tag warn means something novel — stop and investigate, don't loop enrichment PRs.
 6. **`npm dist-tag latest` is set by publish order** — batch pushes publish oldest first and WAIT for settle.
 7. **A breaking (MINOR) cut MUST ship its MIGRATION GUIDE section in the same cycle** — MINOR is reserved for removed/renamed API symbols; everything else, including visible behavior changes, stays PATCH.
-8. **The adia-factory plugin's `.mcp.json` pins `@adia-ai/a2ui-mcp` exactly** — bump the pin in `packages/plugins/adia-ui-factory/.mcp.json` in the same cut (the consumer never floats; with the plugins in-lockstep this lands in the release commit itself, not a follow-up).
+8. **The adia-factory plugin's `.mcp.json` pins the generation MCP exactly** — bump the pin in `packages/plugins/adia-ui-factory/.mcp.json` in the same cut (the consumer never floats; with the plugins in-lockstep this lands in the release commit itself, not a follow-up). The pinned NAME is still `@adia-ai/a2ui-mcp` and flips to `@adia-ai/gen-ui-mcp` in the ADR-0048 P7 release commit — never before it, because invariant 8 forces the pin to the current lockstep version and the new name has no `0.8.x` on npm (`references/cut-procedure.md` §the P7 cut).
 
 The release is done only when reality confirms it: **the npm registry, the GH release page, and the deployed endpoint — a workflow's green check or any self-report is never the verify target.**
 
@@ -59,7 +59,7 @@ The release is done only when reality confirms it: **the npm registry, the GH re
 
 | Task shape | Done when |
 | --- | --- |
-| Lockstep cut / handoff | `npm view @adia-ai/<pkg> version` = X.Y.Z for all 13 lockstep packages AND `dist-tags.latest` = X.Y.Z AND a deployed content file (not an SPA route) serves real bytes |
+| Lockstep cut / handoff | `npm view @adia-ai/<pkg> version` = X.Y.Z for all 16 lockstep packages AND `dist-tags.latest` = X.Y.Z AND a deployed content file (not an SPA route) serves real bytes |
 | Batch push | every batched tag on `git ls-remote --tags origin` + every version on the registry, `latest` on the newest |
 | Verify-only | the failing gate re-runs green |
 | Recovery | the trip-wire that surfaced the issue passes |
@@ -69,13 +69,13 @@ The release is done only when reality confirms it: **the npm registry, the GH re
 
 ## The Cut Record — the output contract
 
-Every cut reports, whether it ran inline or via `release-builder`:
+Every cut reports, whether it ran inline or via `package-release-agent`:
 
 | Field | Value |
 | --- | --- |
 | Version | X.Y.Z — all roster packages at this version (`check:lockstep`) |
 | Commit / PR | release commit SHA, PR # (merged) |
-| Tags | umbrella `vX.Y.Z` + 13 per-package tags pushed (or: which are still pending, and why) |
+| Tags | umbrella `vX.Y.Z` + 16 per-package tags pushed (or: which are still pending, and why) |
 | Registry | `npm view @adia-ai/<pkg> version` per package, cited (not "publish workflow green") |
 | `dist-tags.latest` | confirmed = X.Y.Z |
 | Deploy | dispatched (`deploy-site.yml` run URL) / N/A this cut |
@@ -94,9 +94,9 @@ assumed pass, or "published" without the actual `npm view` output.
 
 ## Mechanization (bundled `scripts/`, stdlib Node, all support `--dry`)
 
-`release-pack.mjs` walks the cycle in two phases per invariant 3 — `--mode cut` / `--mode from-scratch` promote `[Unreleased]` (BOTH modes now — a peer's hand-authored section must be promoted whichever mode cut it, and a loud guard blocks the bump if any roster package still carries non-empty `[Unreleased]` content after promotion), run Step 4f (pre-tag coverage `--fix` with the authoritative F-N1 matcher), and stop at the release commit (PR → merge); `--mode handoff` tags/publishes/deploys from post-merge main. **`--go` is the standard invocation for an operator-initiated release** — the single authorization covers the cycle; evidence blocks print as a log; granular `--yes`/`--push`/`--publish` remain for cautious manual runs (`--push` still refuses to auto-fire past any F-N1 finding). `--mode batch` is not implemented — it hard-rejects with a pointer to [`recovery-paths.md`](references/recovery-paths.md) §Scenario 2 rather than silently misbehaving; a real batch tags each version at its own release-merge SHA, which this single-version orchestrator has no model for. Pre-flight (Step 3) runs the full 28-gate roster from the single shared list in `scripts/gate-roster.mjs` — the same list [`cut-procedure.md`](references/cut-procedure.md) §3.1 transcribes, so a subset run requires editing that one file, not two.
+`release-pack.mjs` walks the cycle in two phases per invariant 3 — `--mode cut` / `--mode from-scratch` promote `[Unreleased]` (BOTH modes now — a peer's hand-authored section must be promoted whichever mode cut it, and a loud guard blocks the bump if any roster package still carries non-empty `[Unreleased]` content after promotion), run Step 4f (pre-tag coverage `--fix` with the authoritative F-N1 matcher), and stop at the release commit (PR → merge); `--mode handoff` tags/publishes/deploys from post-merge main. **`--go` is the standard invocation for an operator-initiated release** — the single authorization covers the cycle; evidence blocks print as a log; granular `--yes`/`--push`/`--publish` remain for cautious manual runs (`--push` still refuses to auto-fire past any F-N1 finding). `--mode batch` is not implemented — it hard-rejects with a pointer to [`recovery-paths.md`](references/recovery-paths.md) §Scenario 2 rather than silently misbehaving; a real batch tags each version at its own release-merge SHA, which this single-version orchestrator has no model for. Pre-flight (Step 3) runs the full 29-gate roster from the single shared list in `scripts/gate-roster.mjs` — the same list [`cut-procedure.md`](references/cut-procedure.md) §3.1 transcribes, so a subset run requires editing that one file, not two.
 
-The pieces are callable alone: `bump.mjs` (version fields + the factory `.mcp.json` a2ui-mcp pin, invariant 8), `promote-unreleased.mjs` / `insert-stub.mjs` (CHANGELOG blocks), `tag-lockstep.mjs` (umbrella + one tag per roster package — 14 today, `--delete` to move), `dispatch-publish.mjs` (publish workflows; `--verify-triggered` re-dispatches missing AND dead — cancelled/failed/timed-out — runs, each gated behind an npm-registry check so an already-published version is never re-dispatched (gh#763); `--after` enforces batch ordering — dispatch output states what WAS done, never a to-do phrased as if it hadn't fired), and `pr-bridge.mjs` (the two-phase bridge: pushes the release branch, opens the PR, waits out CI, and merges ONLY on all-non-fail-soft-checks-green + zero unresolved threads + no changes-requested; any other state stops with evidence — §5.7 mechanized, `--dry` to preview the decision). All fail fast outside a monorepo root (`assert-monorepo-root.mjs`); fork-configurable via `--host` / `--scope`. All 6 CLI scripts (plus `scripts/release/check-release.mjs`) have a `selftest` mode wired into CI's Plugin bin selftests step; the 3 helper modules (`assert-monorepo-root`, `gate-roster`, `package-paths`) are exercised through the CLIs' selftests, not their own.
+The pieces are callable alone: `bump.mjs` (version fields + the factory `.mcp.json` a2ui-mcp pin, invariant 8), `promote-unreleased.mjs` / `insert-stub.mjs` (CHANGELOG blocks), `tag-lockstep.mjs` (umbrella + one tag per lockstep roster package — the set is derived from `PACKAGE_ROSTER`, never a number written here: it went stale at 14 while the roster said 17, 17 went stale in turn when gh#1240 folded two planned MCP rows into one (now 16), and 16 goes stale again the day the ADR-0048 shims retire; run `--dry` to see the live list, `--delete` to move), `dispatch-publish.mjs` (publish workflows; `--verify-triggered` re-dispatches missing AND dead — cancelled/failed/timed-out — runs, each gated behind an npm-registry check so an already-published version is never re-dispatched (gh#763); `--after` enforces batch ordering — dispatch output states what WAS done, never a to-do phrased as if it hadn't fired), and `pr-bridge.mjs` (the two-phase bridge: pushes the release branch, opens the PR, waits out CI, and merges ONLY on all-non-fail-soft-checks-green + zero unresolved threads + no changes-requested; any other state stops with evidence — §5.7 mechanized, `--dry` to preview the decision). All fail fast outside a monorepo root (`assert-monorepo-root.mjs`); fork-configurable via `--host` / `--scope`. All 6 CLI scripts (plus `scripts/release/check-release.mjs`) have a `selftest` mode wired into CI's Plugin bin selftests step; the 3 helper modules (`assert-monorepo-root`, `gate-roster`, `package-paths`) are exercised through the CLIs' selftests, not their own.
 
 Site deploy (Step 10 of the handoff) dispatches `deploy-site.yml` (its own pre-flight verify → snapshot → hardened rsync → post-deploy verify → auto-rollback), never a raw local `rsync` — H1 (forge-campaign gh#268 audit): the script had drifted into bypassing that pipeline even though this doc already taught the workflow-dispatch path. The dispatch rides the cycle's single authorization (`--go`, or `--publish` on a manual run); the workflow's own GitHub environment gate is the human stop for the deploy itself.
 

package/skills/{adia-release → package-release}/evals/evals.json

@@ -1,6 +1,6 @@
 {
-  "skill": "adia-release",
-  "note": "Trigger-routing suite (forge-campaign gh#268, item 10). 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) — exe.dev VM ops route to adia-deploy, consumer-app migration sweeps route to adia-migrate, and framework authoring/consumer composition route to adia-author/adia-compose. Covers cut/tag/publish/batch/recovery/notes phrasings per the audit's ask.",
+  "skill": "package-release",
+  "note": "Trigger-routing suite (forge-campaign gh#268, item 10). 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) — exe.dev VM ops route to site-deployment, consumer-app migration sweeps route to app-migration, and framework authoring/consumer composition route to primitive-authoring/screen-composition. Covers cut/tag/publish/batch/recovery/notes phrasings per the audit's ask.",
   "cases": [
     { "id": "t01", "prompt": "Cut and ship v0.8.5 of the AdiaUI packages", "expect": "trigger" },
     { "id": "t02", "prompt": "The [Unreleased] CHANGELOG entries are piling up, let's cut a release", "expect": "trigger" },
@@ -15,10 +15,10 @@
     { "id": "t11", "prompt": "Publish the adia-ui-forge plugin independently of the lockstep set", "expect": "trigger" },
     { "id": "t12", "prompt": "Just verify the release gates are green without cutting anything", "expect": "trigger" },
     { "id": "t13", "prompt": "Tags are pushed but zero publish workflows fired, what happened", "expect": "trigger" },
-    { "id": "n01", "prompt": "Restart the exe.dev VM, it's returning 502s", "expect": "no-trigger", "owner": "adia-deploy" },
-    { "id": "n02", "prompt": "Rsync the built dist folder to ui-kit.exe.xyz", "expect": "no-trigger", "owner": "adia-deploy" },
-    { "id": "n03", "prompt": "Sweep our consumer app for the renamed variant prop after the last breaking release", "expect": "no-trigger", "owner": "adia-migrate" },
-    { "id": "n04", "prompt": "Add a new size variant to the button-ui primitive", "expect": "no-trigger", "owner": "adia-author" },
-    { "id": "n05", "prompt": "Compose a settings screen for our app from the AdiaUI catalog", "expect": "no-trigger", "owner": "adia-compose" }
+    { "id": "n01", "prompt": "Restart the exe.dev VM, it's returning 502s", "expect": "no-trigger", "owner": "site-deployment" },
+    { "id": "n02", "prompt": "Rsync the built dist folder to ui-kit.exe.xyz", "expect": "no-trigger", "owner": "site-deployment" },
+    { "id": "n03", "prompt": "Sweep our consumer app for the renamed variant prop after the last breaking release", "expect": "no-trigger", "owner": "app-migration" },
+    { "id": "n04", "prompt": "Add a new size variant to the button-ui primitive", "expect": "no-trigger", "owner": "primitive-authoring" },
+    { "id": "n05", "prompt": "Compose a settings screen for our app from the AdiaUI catalog", "expect": "no-trigger", "owner": "screen-composition" }
   ]
 }

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

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

package/skills/{adia-release → package-release}/references/changelog-discipline.md

@@ -18,7 +18,7 @@
 The heading swap is all that happens; content under it stays:
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/skills/adia-release/scripts/promote-unreleased.mjs" \
+node "${CLAUDE_PLUGIN_ROOT}/skills/package-release/scripts/promote-unreleased.mjs" \
   --version 0.X.Y --date YYYY-MM-DD --packages web-components,web-modules,a2ui/corpus
 ```
 
@@ -70,12 +70,12 @@ Why this recurs: cross-package sweeps leave 1–3 incidental touches (a docstrin
 ## §Stubs — ride-along lockstep
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/skills/adia-release/scripts/insert-stub.mjs" \
+node "${CLAUDE_PLUGIN_ROOT}/skills/package-release/scripts/insert-stub.mjs" \
   --version 0.X.Y --date YYYY-MM-DD \
   --substantive "<one-line> in @adia-ai/<pkg>" \
   --xref "packages/web-modules/CHANGELOG.md#0XY--YYYY-MM-DD" \
   --previous-version 0.X.Y-1 \
-  --packages llm,a2ui/compose,a2ui/mcp,a2ui/retrieval,a2ui/runtime,a2ui/validator
+  --packages llm,a2ui-compose,a2ui-mcp,a2ui-retrieval,a2ui-runtime,a2ui-validator
 ```
 
 The inserted block:
@@ -111,7 +111,7 @@ This is cut-procedure §Step 4f: the SAME matcher F-N1 uses at tag time (every r
 **Recovery — a warn AFTER tagging** (Step 4f skipped, or an interleaved merge added uncovered changes): the release commit is already merged via PR, so `--amend` is not possible —
 
 1. Run `--pending-version X.Y.Z --fix`; `git add` the CHANGELOGs; `git commit -m "fix(release): F-N1 enrichment — vX.Y.Z"`; push the branch → PR → CI → merge.
-2. The SHA moved: `node "${CLAUDE_PLUGIN_ROOT}/skills/adia-release/scripts/tag-lockstep.mjs" --version X.Y.Z --delete`, then re-tag at `main`'s new post-merge HEAD.
+2. The SHA moved: `node "${CLAUDE_PLUGIN_ROOT}/skills/package-release/scripts/tag-lockstep.mjs" --version X.Y.Z --delete`, then re-tag at `main`'s new post-merge HEAD.
 3. Re-run F-N1; expect per-package clean (umbrella error stays, ignored). ONE recovery round — if a second warn appears, the cause is upstream (find what keeps merging into the window), not another enrichment.
 
 ## §Dating and anchors