@adia-ai/adia-ui-forge 0.8.50 → 0.8.52

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-ui-kit-forge",
-  "version": "0.8.50",
+  "version": "0.8.52",
   "description": "Maintain the adia-ui (@adia-ai) framework itself \u2014 author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-ui-kit-factory (the consumer/app-author plugin).",
   "author": {
     "name": "Kim",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-ui-kit-forge",
-  "version": "0.8.50",
+  "version": "0.8.52",
   "description": "Maintain the adia-ui (@adia-ai) framework itself — author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-ui-kit-factory (the consumer/app-author plugin).",
   "author": {
     "name": "Kim",

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # Changelog — adia-ui-kit-forge
 
+## [0.8.52] — 2026-08-25
+
+### Added
+- **`cross-harness-authoring-standards` (renamed from `writing-harness-install-instructions`, which had only ever existed as uncommitted worktree content) + new sibling skill `cross-harness-compatibility-standards` (gh#1975, PR #2003).** The rename is byte-faithful aside from the three self-referential mentions (frontmatter name, H1, one in-body reference). The new skill is the upstream engineering standard for actually building a capability that works across Claude Code, Codex, Pi, and Hermes — distinct from the renamed sibling's downstream consumer-facing install-docs concern — extracted from ADR-0091 and the four PRs (#1997-#2000) that built and shipped it: the skill-vs-thin-adapter classification rule, verify-before-coding per harness, one authored skill body with every runtime as a thin consumer, one contract grammar (record-lint family) instead of a schema per runtime, and naming distribution channels distinctly. Codex and Hermes derived manifests regenerated for both skills; README/`AGENTS.md` skill-roster and count updated.
+
+### Changed
+- **`package-release`'s pre-cut roster runs in three phases instead of one serial for-loop (gh#2006, follow-up from gh#1987's audit)** — `release-pack.mjs`'s `step3PreFlight()` now runs gate 4 (`test:unit:serial`) solo, the eval-health chain (gates 16 → 27 → 28 — a real CSS-before-JS-shaped file-write ordering dependency: gate 28 reads whichever `evals/mcp/runs/` directory sorts lexically last, so gate 27's free-form run must land uninterrupted) strictly in order, and every other gate in a concurrency-capped pool (`PREFLIGHT_CONCURRENCY`, default 4) — all concurrent with the chain. Cuts real wall-clock with zero coverage loss: no gate dropped, none renumbered, none silently skipped. `--dry` previews are unchanged (still the original flat serial walk, byte-for-byte, so `selftest`'s exact-output assertions keep passing).
+- **All agent seats pinned to `sonnet` + `xhigh` reasoning effort, replacing the prior fable/opus ceiling-ladder pins (PR #1999).** Operator's direct standing instruction, applied across `a2ui-maintenance-agent`, `a2ui-planner-agent`, `demo-audit-agent`, `framework-checker`, `framework-planner-agent`, `gen-ui-review-agent`, `package-release-agent`, `primitive-authoring-agent`. See root `CHANGELOG.md` for the cross-plugin note.
+
+### Fixed
+- **`__init__.py`'s Hermes manifest generator's `register_skill` call passed a plain string where the runtime requires a `pathlib.Path` (calls `path.exists()`) — wrapped, discovered incidentally while building `adia-ui-factory`'s Hermes `delegate_task` command (PR #2000).**
+
+### Maintenance
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+- **`.codex-plugin/` touched in this release window** (1 file(s), e.g. `.codex-plugin/plugin.json`) — carried by the entries above.
+
+## [0.8.51] — 2026-08-24
+
+### Added
+- Hermes + Pi external-distribution manifests (gh#1954) — `plugin.yaml` +
+  `__init__.py` (Hermes) and `prompts/*.md` + a `"pi"` field in
+  `package.json` (Pi), derived from `.claude-plugin/plugin.json` +
+  `skills/` + `commands/` via `npm run build:harness-manifests`
+  (`check:harness-manifests-fresh` gates freshness). Additive: the Claude
+  Code plugin surface is unchanged. This plugin ships no `.mcp.json`, so
+  neither harness's MCP story applies to it.
+
+### Maintenance
+- **`.codex-plugin/` touched in this release window** (1 file(s), e.g. `.codex-plugin/plugin.json`) — carried by the entries above.
+
 ## [0.8.50] — 2026-08-23
 
 ### Maintenance

package/README.md

@@ -8,7 +8,7 @@ Re-engineered 2026-07 for the Fable 5 harness (design:
 `.claude/docs/specs/plugin-estate-v2.md`): one skill per job, explicit
 invocation dials, references for depth, mechanical rules in hooks, thin agents.
 
-## Skills (9)
+## Skills (11)
 
 | Skill | Species | Job |
 |---|---|---|
@@ -21,6 +21,8 @@ invocation dials, references for depth, mechanical rules in hooks, thin agents.
 | `site-deployment` | procedural | exe.dev service ops — site deploys, VM diagnosis, secret rotation |
 | `site-docs-authoring` | procedural | author/review `site/pages/` docs pages against the shared skeleton |
 | `ssr-compatibility` | knowledge | answers SSR failure-shape questions (linkedom/Astro consumers) |
+| `cross-harness-authoring-standards` | procedural | author consumer-facing multi-harness install instructions |
+| `cross-harness-compatibility-standards` | procedural | engineering standard for building a capability that genuinely works across Claude/Codex/Pi/Hermes (ADR-0091) |
 
 ## Agents (8, thin shells)
 
@@ -48,6 +50,26 @@ ship `selftest` modes.
 
 `/package-release` · `/site-deployment` · `/demo-audit` · `/gen-ui-review`
 
+## Non-Claude harnesses
+
+External install beyond Claude Code (AGENTS.md's own "Non-Claude harnesses"
+section carries the shared degradation table this summarizes):
+
+- **Codex** (gh#1888): `.codex-plugin/plugin.json` + per-skill
+  `agents/openai.yaml`, derived. No manifest key for hooks/commands/agents —
+  a command degrades to invoking its skill directly.
+- **Hermes** (gh#1954): `plugin.yaml` + `__init__.py` at this package's
+  root — point Hermes's plugin loading at the installed
+  `node_modules/@adia-ai/adia-ui-forge` directory. No hooks/agents surface.
+  This plugin ships no `.mcp.json`, so there's no MCP story to wire either
+  way.
+- **Pi** (gh#1954): discovered via the `pi-package` keyword and the `"pi"`
+  field in `package.json`; `prompts/*.md` gives every `/command` — including
+  the two consent-gated ones, `/package-release` and `/site-deployment` — a
+  genuine Pi prompt template (Pi's prompt layer is human-keystroke-only, the
+  same trust boundary those two already sit behind in Claude Code). No
+  hooks/agents surface.
+
 ## Contracts
 
 `references/contracts/` — the producer side of the MIGRATION GUIDE format and

package/__init__.py

@@ -0,0 +1,63 @@
+"""adia-ui-kit-forge — generated by scripts/build/harness-manifests.mjs. Do not edit."""
+import os
+from pathlib import Path
+
+_HERE = os.path.dirname(os.path.abspath(__file__))
+
+
+def register(ctx):
+    ctx.register_skill(
+        name="a2ui-maintenance",
+        path=Path(os.path.join(_HERE, "skills", "a2ui-maintenance", "SKILL.md")),
+        description="Maintains the A2UI pipeline (packages/gen-ui/a2ui/): the chunk corpus, compose strategies (zettel, chunk-zettel, free-form, monolithic), retrieval, validator, calibration, evals, the a2ui MCP server. Use to author/harvest/fix chunks, tune STRONG_MATCH or zettel thresholds, validate an A2UI document, diagnose an eval gap/regression or lift a semantic fail, change MCP tools (generate_ui, compose_from_chunks, check_anti_patterns, refine_composition), scan anti-patterns, run pipeline ops, or when a contract can't express a shape. NOT for app screens (screen-composition), runtime gen-UI features (gen-ui-wiring), primitive authoring (primitive-authoring), or gallery scoring (gen-ui-review).",
+    )
+    ctx.register_skill(
+        name="cross-harness-authoring-standards",
+        path=Path(os.path.join(_HERE, "skills", "cross-harness-authoring-standards", "SKILL.md")),
+        description="Authors copy-paste install instructions for an adia-ui plugin (or any Claude Code plugin) across multiple agent harnesses — Claude Code, Codex, Pi, Hermes. Use when asked to \"write a Slack post for installing our plugins\", \"how do devs on Codex/Pi/Hermes install this\", \"update the multi-harness install docs\", or after a harness-distribution change (a new .codex-plugin/, plugin.yaml, or package.json \"pi\" field) needs its install instructions to catch up. NOT for the manifest/build mechanics themselves (package-release's Codex-manifest step, gh#1888/gh#1954) — this skill only writes the consumer-facing instructions once those exist.",
+    )
+    ctx.register_skill(
+        name="cross-harness-compatibility-standards",
+        path=Path(os.path.join(_HERE, "skills", "cross-harness-compatibility-standards", "SKILL.md")),
+        description="The engineering/architecture standard for actually BUILDING a Claude agent-family (or any multi-runtime capability) so it genuinely works across Claude Code, Codex, Pi, and Hermes — not the consumer-facing install docs once it already works (that's cross-harness-authoring-standards). Use when deciding whether a capability earns a new user-facing skill or should stay a thin runtime-specific agent/seat/extension, before writing a Pi extension or Hermes command and unsure whether the target API actually exists, defining a structured handoff record two or more runtimes must exchange, or naming a new plugin distribution/marketplace channel alongside an existing one. NOT for writing the resulting per-harness install commands (cross-harness-authoring-standards owns that, once the capability already works).",
+    )
+    ctx.register_skill(
+        name="demo-audit",
+        path=Path(os.path.join(_HERE, "skills", "demo-audit", "SKILL.md")),
+        description="Seven-mode QA sweep of the monorepo's demo/app surfaces: visual probe, app-shell QA, attr-quote typos, native-primitive leak, admin-shell composition, card anatomy, plus an aggregated token/contrast/lifecycle drift battery (`npm run dogfood:status`). Use for \"run a dogfood sweep\", \"find broken demos\", \"audit native primitive leaks\". NOT for gen-UI gallery scoring (gen-ui-review) or authoring primitives (primitive-authoring).",
+    )
+    ctx.register_skill(
+        name="gen-ui-review",
+        path=Path(os.path.join(_HERE, "skills", "gen-ui-review", "SKILL.md")),
+        description="Closed-loop Gen UI gallery quality review — per cycle: derive ideal specs, decompose the rendered canvas, score the gap, root-cause, emit fix plans until every prompt clears the exit gate. Use for /gen-review, \"score the gallery\", \"review gen-ui outputs\". NOT for corpus fixes (a2ui-maintenance), primitive authoring (primitive-authoring), or a hand-authored demo/app-shell QA sweep (demo-audit).",
+    )
+    ctx.register_skill(
+        name="llm-client-maintenance",
+        path=Path(os.path.join(_HERE, "skills", "llm-client-maintenance", "SKILL.md")),
+        description="Maintains @adia-ai/llm (packages/llm/core/): provider adapters (anthropic/openai/ gemini), the shared SSE parser, model registry, chat()/streamChat() facade, createAdapter() bridge. Use when adding or fixing a provider adapter, debugging streaming bugs (StreamChunk, no terminal `done` chunk), raw `stopReason`/usage mapping, buildRequest() or passthrough proxy dispatch (browser 401s, API key in browser), detectProvider/MODELS registry changes, or the stub adapter. NOT for wiring the client into an app (llm-wiring, adia-ui-factory plugin).",
+    )
+    ctx.register_skill(
+        name="package-release",
+        path=Path(os.path.join(_HERE, "skills", "package-release", "SKILL.md")),
+        description="Release engineering for the @adia-ai lockstep monorepo. Use to cut and ship a release, promote [Unreleased] CHANGELOG entries, tag and push lockstep packages to origin, publish a 10-package release (roster: scripts/package-paths.mjs), publish a single plugin independently of the lockstep set (Class B), 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 warning, verify release gates without cutting anything, or author release notes/a MIGRATION GUIDE section. NOT for consumer-app migration sweeps (app-migration) or exe.dev VM ops (site-deployment).",
+    )
+    ctx.register_skill(
+        name="primitive-authoring",
+        path=Path(os.path.join(_HERE, "skills", "primitive-authoring", "SKILL.md")),
+        description="Author or modify AdiaUI framework source inside the monorepo — primitives (packages/web-components), shells/composites (packages/web-modules), yaml SoTs, demos. Use to add a new primitive, fix a prop/slot/attribute/CSS variant, update a yaml, build or fix a shell (chat-shell, admin-shell, editor-shell — sidebar/pane/bespoke-tier composition), promote repeated inline content into a shared module, audit a component's four-axis contract/token usage/lifecycle for drift, or author a demo or examples.html. NOT for app screens (screen-composition), A2UI internals (a2ui-maintenance), @adia-ai/llm internals (llm-client-maintenance), or site/pages docs (site-docs-authoring).",
+    )
+    ctx.register_skill(
+        name="site-deployment",
+        path=Path(os.path.join(_HERE, "skills", "site-deployment", "SKILL.md")),
+        description="Deploys and operates the AdiaUI site + services on exe.dev VMs — pushing a `site-v*` tag through the hardened rsync --delete deploy to ui-kit.exe.xyz (dry-run delete summary reviewed before the real deploy job runs), diagnosis (\"Port 8000 unbound\", a 502, a stale/404ing build behind npm after the last lockstep cut), rolling back a broken deploy, VM provisioning, secret rotation. Use for \"deploy to exe.dev\", \"push a site-v* tag\", \"the site is 502ing / looks stale\", \"roll back the last deploy\", \"restart/diagnose the exe service\", \"rotate keys on the VM\". NOT for cutting the release itself (package-release).",
+    )
+    ctx.register_skill(
+        name="site-docs-authoring",
+        path=Path(os.path.join(_HERE, "skills", "site-docs-authoring", "SKILL.md")),
+        description="Review or author pages under site/pages/{architecture,getting-started, guides,patterns,reference}/ — the docs site (count the pages on disk; it grows). Use when asked to add or edit a getting-started/architecture/guides/patterns/reference page, review a site docs page for consistency, fix a callout that reads as plain text, or explain why an inline-code chip or a demo gallery looks broken. NOT for a component's own .examples.html demo (primitive-authoring) or any pure-primitive-composition training-harvest page (governed by composition-and-examples.md's no-style-block rule; owner: a2ui-maintenance).",
+    )
+    ctx.register_skill(
+        name="ssr-compatibility",
+        path=Path(os.path.join(_HERE, "skills", "ssr-compatibility", "SKILL.md")),
+        description="Answers why an AdiaUI component crashes, drops content, renders wrong, or mutates a byte-identical subtree under SSR (linkedom/Astro) — the known failure shapes, what's fixed vs open, how to prove a fix under the linkedom shim gate. Use for \"does this work under SSR\", why a component crashes on attachInternals/ResizeObserver/adoptedStyleSheets/matchMedia/ `instanceof Node` under a DOM shim, why table-ui/chart-ui/select-ui or a container CE renders empty or drops nested children server-rendered, whether getBoundingClientRect() is safe in connectedCallback, whether a custom render()/connected() path adopts-in-place or rebuilds a server-rendered subtree that already matches (zero-subtree-mutation / AC-004a-shaped asks), whether a querySelector-guard-before-innerHTML component is SSR-safe, or whether a shim can be deleted after a fix ships. ANSWERS only. NOT for a fix (primitive-authoring) or host/hydration wiring (host-wiring, adia-ui-factory).",
+    )

package/agents/a2ui-maintenance-agent.md

@@ -12,10 +12,12 @@ description: |
 tools: Read, Grep, Glob, Edit, Write, Bash
 skills:
   - a2ui-maintenance
-# Explicit pin (gh#618): never `inherit` — a Fable/planning caller would
-# silently run this seat's pipeline-tuning and eval-diagnosis work on the
-# caller's tier. Coding/execution seat → opus.
-model: opus
+# Explicit pin (gh#618): never `inherit` — a caller on a cheaper tier would
+# silently run this seat's pipeline-tuning and eval-diagnosis work on its
+# own tier instead. Operator's explicit standing instruction for this seat
+# family: sonnet + xhigh.
+model: sonnet
+effort: xhigh
 ---
 
 The a2ui-maintenance-agent works the pipeline to the preloaded `a2ui-maintenance` procedure:

package/agents/a2ui-planner-agent.md

@@ -15,11 +15,11 @@ skills:
   - break-down-problem
   - doc-writing-rules
   - a2ui-maintenance
-# Planning & architecture row (agent-writing-rules' seat ladder): fable + high, never
-# below fable. Same reasoning as framework-planner-agent — a catalog-cohesion decision
-# sets the ceiling on what a2ui-maintenance-agent builds against it.
-model: fable
-effort: high
+# Explicit pin: never `inherit` — a catalog-cohesion decision sets the
+# ceiling on what a2ui-maintenance-agent builds against it. Operator's
+# explicit standing instruction for this seat family: sonnet + xhigh.
+model: sonnet
+effort: xhigh
 ---
 
 The a2ui-planner-agent decomposes one named A2UI catalog-system change via the preloaded

package/agents/demo-audit-agent.md

@@ -16,10 +16,10 @@ tools: Read, Grep, Glob, Bash
 skills:
   - demo-audit
 # Explicit pin (gh#618, tier corrected gh#1045): a review/critic seat's
-# verdict must not depend on the caller's model tier — never `inherit`,
-# never below fable (the ceiling ladder's Review row).
-model: fable
-effort: high
+# verdict must not depend on the caller's model tier — never `inherit`.
+# Operator's explicit standing instruction for this seat family: sonnet + xhigh.
+model: sonnet
+effort: xhigh
 ---
 
 The demo-audit-agent runs the preloaded dogfood sweep procedure and returns

package/agents/framework-checker.md

@@ -13,11 +13,11 @@ description: |
 tools: Read, Grep, Glob, Bash
 skills:
   - primitive-authoring
-# Review / hard-bug analysis row (agent-writing-rules' seat ladder), pinned explicitly —
-# never `inherit`, same reasoning as demo-audit-agent's own explicit pin (gh#618): a
-# critic's verdict must not depend on the caller's tier.
-model: fable
-effort: high
+# Explicit pin (gh#618) — never `inherit`, same reasoning as demo-audit-agent's
+# own explicit pin: a critic's verdict must not depend on the caller's tier.
+# Operator's explicit standing instruction for this seat family: sonnet + xhigh.
+model: sonnet
+effort: xhigh
 ---
 
 The framework-checker sweeps the named scope (the whole primitive corpus, or a

package/agents/framework-planner-agent.md

@@ -14,12 +14,13 @@ tools: Read, Grep, Glob, Write, Edit
 skills:
   - break-down-problem
   - doc-writing-rules
-# Planning & architecture row (agent-writing-rules' seat ladder, ratified 2026-07-12):
-# fable + high, never below fable, effort range high-xhigh. A decomposition seat's
-# output sets the ceiling on everything primitive-authoring-agent builds downstream from
-# it; a cheap tier would make load-bearing architectural calls with no independent check.
-model: fable
-effort: high
+# Explicit pin: never `inherit` — a decomposition seat's output sets the
+# ceiling on everything primitive-authoring-agent builds downstream from it;
+# a cheap tier would make load-bearing architectural calls with no
+# independent check. Operator's explicit standing instruction for this seat
+# family: sonnet + xhigh.
+model: sonnet
+effort: xhigh
 ---
 
 The framework-planner-agent decomposes one named framework change via the preloaded

package/agents/gen-ui-review-agent.md

@@ -17,10 +17,10 @@ tools: Read, Grep, Glob, Bash
 skills:
   - gen-ui-review
 # Explicit pin (gh#618, tier corrected gh#1045): a review/critic seat's
-# verdict must not depend on the caller's model tier — never `inherit`,
-# never below fable (the ceiling ladder's Review row).
-model: fable
-effort: high
+# verdict must not depend on the caller's model tier — never `inherit`.
+# Operator's explicit standing instruction for this seat family: sonnet + xhigh.
+model: sonnet
+effort: xhigh
 ---
 
 The gen-ui-review-agent runs the preloaded gen-ui-review cycle and returns

package/agents/package-release-agent.md

@@ -14,8 +14,10 @@ skills:
   - package-release
 # Explicit pin (gh#618): never `inherit` — this seat runs UNATTENDED cuts,
 # where a cheap caller tier would make live gate-failure judgment calls
-# with no operator watching. Execution seat with real judgment → opus.
-model: opus
+# with no operator watching. Operator's explicit standing instruction for
+# this seat family: sonnet + xhigh.
+model: sonnet
+effort: xhigh
 ---
 
 The package-release-agent runs the preloaded `package-release` procedure under its

package/agents/primitive-authoring-agent.md

@@ -11,6 +11,7 @@ tools: Read, Grep, Glob, Edit, Write, Bash
 skills:
   - primitive-authoring
 model: sonnet
+effort: xhigh
 ---
 
 The primitive-authoring-agent builds framework source to the preloaded `primitive-authoring`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-forge",
-  "version": "0.8.50",
+  "version": "0.8.52",
   "description": "Maintain the adia-ui (@adia-ai) framework itself — author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-factory (the consumer/app-author plugin).",
   "keywords": [
     "adia-ui",
@@ -9,7 +9,8 @@
     "web-components",
     "framework-authoring",
     "release-engineering",
-    "maintainer"
+    "maintainer",
+    "pi-package"
   ],
   "license": "MIT",
   "author": {
@@ -19,15 +20,22 @@
   "bugs": {
     "email": "kim.granlund@adia.ai"
   },
+  "pi": {
+    "skills": ["./skills"],
+    "prompts": ["./prompts"]
+  },
   "files": [
     ".claude-plugin",
     ".codex-plugin",
     "skills",
     "agents",
     "commands",
+    "prompts",
     "references",
     "scripts",
     "hooks",
+    "plugin.yaml",
+    "__init__.py",
     "README.md",
     "CHANGELOG.md",
     "codex.interface.json"

package/plugin.yaml

@@ -0,0 +1,4 @@
+name: "adia-ui-kit-forge"
+version: "0.8.52"
+description: "Maintain the adia-ui (@adia-ai) framework itself — author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-ui-kit-factory (the consumer/app-author plugin)."
+manifest_version: 1

package/prompts/demo-audit.md

@@ -0,0 +1,10 @@
+---
+description: "Run the multi-mode QA sweep (visual probe, static QA, typo, native-primitive leak, shell composition, anatomy) across component demos, apps, playgrounds, and catalog."
+argument-hint: "[mode or surface]"
+---
+
+Run a dogfood sweep. **$ARGUMENTS**
+
+Invoke **`demo-audit`**; run the requested modes (all, if unscoped), then
+triage findings per its severity contract. Detection is script-driven; the
+skill owns triage and the auto-fix boundary.

package/prompts/gen-ui-review.md

@@ -0,0 +1,9 @@
+---
+description: "Run the closed-loop gen-UI quality review — score gallery outputs against ideal specs, trace root causes, produce the ranked improvement plan."
+argument-hint: "[prompt subset]"
+---
+
+Run a gen-UI review cycle. **$ARGUMENTS**
+
+Invoke **`gen-ui-review`** and run its loop: derive ideal → decompose actual
+→ score → root-cause → plan. Corpus fixes route to `a2ui-maintenance`.

package/prompts/package-release.md

@@ -0,0 +1,12 @@
+---
+description: "Cut, tag, publish, and deploy an @adia-ai release (lockstep roster in skills/package-release/scripts/package-paths.mjs — npm libraries + the 2 Claude Code plugins). This invocation IS the authorization for the whole cycle; only gate failures stop it."
+argument-hint: "[version or package]"
+---
+
+Run a release. **$ARGUMENTS**
+
+Invoke **`package-release`** and run its cut procedure end-to-end: pre-flight
+gates → cut → tag → publish → deploy → notes. This command's invocation is
+the operator's single authorization for the entire cycle (§Authorization,
+operator ruling 2026-07-17) — run inline, don't re-ask per step; stop only
+on a gate failure. The skill owns the discipline; don't restate it here.

package/prompts/site-deployment.md

@@ -0,0 +1,9 @@
+---
+description: "Deploy a service or dist to the exe.dev VMs (ui-kit.exe.xyz and siblings), or diagnose a running exe service."
+argument-hint: "[host or service]"
+---
+
+Deploy or diagnose an exe.dev surface. **$ARGUMENTS**
+
+Invoke **`site-deployment`** and follow its playbook for the named host; verify
+against the live endpoint before reporting done.

package/skills/cross-harness-authoring-standards/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: cross-harness-authoring-standards
+description: >-
+  Authors copy-paste install instructions for an adia-ui plugin (or any
+  Claude Code plugin) across multiple agent harnesses — Claude Code, Codex,
+  Pi, Hermes. Use when asked to "write a Slack post for installing our
+  plugins", "how do devs on Codex/Pi/Hermes install this", "update the
+  multi-harness install docs", or after a harness-distribution change
+  (a new .codex-plugin/, plugin.yaml, or package.json "pi" field) needs its
+  install instructions to catch up. NOT for the manifest/build mechanics
+  themselves (package-release's Codex-manifest step, gh#1888/gh#1954) — this
+  skill only writes the consumer-facing instructions once those exist.
+disable-model-invocation: false
+user-invocable: true
+---
+
+# cross-harness-authoring-standards — one command per harness, zero invented syntax
+
+Every harness's install path is a claim someone will paste verbatim into a terminal. A
+plausible-looking command that was never verified against this repo's actual shipped
+manifests is worse than no instructions — it fails silently or errors somewhere the
+author never sees. The whole discipline is: **read the real generated file before
+describing what it does.**
+
+## The verification-before-writing gate `[gate]`
+
+Before writing one line of install instructions for a harness, verify against the strongest
+source actually reachable — never infer a harness's install surface from another harness's
+shape, and never invent a CLI subcommand you have not seen documented or confirmed:
+
+- **Strongest: the target harness's own agent, live.** If a Codex/Pi/Hermes agent is
+  reachable (a peer session, a cross-harness message), have it check or correct the draft
+  against its own real CLI/config surface directly — it knows its own tool's commands with
+  more authority than any manifest file a human read once and wrote down. A harness section
+  corrected this way outranks a manifest-file read on the same point; update the draft to
+  match, don't average the two.
+- **Fallback: the repo's own shipped manifest for that harness** (below), when no live
+  agent is reachable.
+
+| Harness | What to read before writing anything |
+| --- | --- |
+| Claude Code | The plugin's own `README.md` "Install" section + `.claude-plugin/marketplace.json` (or the published npm marketplace manifest) |
+| Codex | `.codex-plugin/plugin.json` + `codex.interface.json` + the repo's own `AGENTS.md` "Non-Claude harnesses" section (gh#1888 — the canonical degradation-table citation) |
+| Hermes | `plugin.yaml` + `__init__.py` at the package root, and whether an `hermes-mcp.yaml` (or equivalent) fragment exists — Hermes MCP is user-level config, not a plugin field, in every verified case so far |
+| Pi | `package.json`'s `"pi"` field + `pi-package` keyword, and `prompts/*.md` if present |
+
+If a harness's manifest file doesn't exist yet in the repo, that harness has **no verified
+install path** — say so plainly (`cross-harness-authoring-standards` never fabricates a
+"probably works like X" command) and route the gap to the maintainer skill/issue that owns
+harness-manifest generation, rather than guessing syntax.
+
+## The four-axis degradation table
+
+Every harness other than Claude Code lacks at least one of: commands, agent seats, hooks,
+native MCP. State the gap plainly per harness, in the instructions themselves — a dev who
+installs expecting the full surface and silently gets less is worse served than one told
+up front:
+
+- **Commands** → Codex/Pi/Hermes have no slash-command layer in the verified cases; a
+  command degrades to invoking its underlying skill directly (Codex, Hermes) or, where the
+  harness's own prompt-template layer supports genuine commands (Pi's `prompts/*.md`),
+  upgrades instead of degrading — check per harness, don't assume degradation is universal.
+- **Agent seats** → do not exist outside Claude Code. Never write "then invoke
+  `<agent-name>`" for Codex/Pi/Hermes; give the entry-point *skill* that agent dispatches
+  internally instead (see "The common starting prompt" below).
+- **Hooks** → Codex/Pi/Hermes have no hook runtime in the verified cases; state "no
+  hooks surface" rather than omitting the topic (an omission reads as "works the same").
+- **MCP** → the highest-risk gap. Verify per harness: does it read `.mcp.json` unmodified
+  (Codex — verified), read it via a third-party adapter the dev must separately install
+  (Pi's `pi-mcp-adapter` — verified 2026-08-24), or require hand-merging a generated
+  fragment into the harness's own user-level config (Hermes — verified, no plugin-level MCP
+  field exists)? If the plugin's whole value proposition is its MCP server, say that
+  explicitly before promising support — a silent no-op MCP install is the worst failure
+  mode this skill exists to prevent.
+
+## The common starting prompt
+
+A "getting started" prompt that opens with an agent name breaks on every harness but
+Claude Code. Give two forms:
+
+- **Claude Code**: name the coordinating agent directly (`Use <agent-name> to build
+  [...]`).
+- **Everywhere else**: name the entry-point *skill* that agent dispatches internally —
+  same routing, no agent-seat dependency. Confirm the skill is genuinely the entry point
+  (its own description says "run FIRST" / "cold-start router") rather than picking an
+  arbitrary skill from the roster.
+
+```
+Bad (breaks on Codex/Pi/Hermes — no agent seat exists):
+  Use ui-architect to build a settings page.
+
+Good (Claude Code):
+  Use ui-architect to build a settings page. Check pattern-catalog for an
+  existing pattern before composing from scratch.
+
+Good (Codex/Pi/Hermes — same routing, no agent dependency):
+  Use the app-planning skill to orient a new settings page. Check
+  pattern-catalog for an existing pattern before composing from scratch,
+  then use screen-composition to build it.
+```
+
+## Structure
+
+One block per harness, each self-contained (a reader only cares about their own harness):
+install command(s) → any manual wiring step (config file edit, separate adapter install) →
+the degradation summary (what's full-strength, what's reduced, what's absent) for that
+harness specifically. Never a single combined command block trying to cover two harnesses —
+the reader copy-pastes the whole block for their tool and nothing else.
+
+## Failure branches
+
+A harness with no verified manifest in the repo → report the gap, do not draft syntax for
+it. A degradation claim that contradicts what a just-read manifest file actually shows
+(e.g. writing "no MCP" for a harness whose `.mcp.json` passthrough is confirmed working) →
+re-read the source file; the manifest is authoritative over any prior draft, including this
+skill's own past output for an earlier plugin version.
+
+Done when every harness section cites the specific file it was verified against (in prose,
+not a footnote) and no command exists in the output that wasn't read from a real shipped
+artifact.

package/skills/cross-harness-authoring-standards/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Cross Harness Authoring Standards"
+  short_description: "Authors copy-paste install instructions for an adia-ui plugin (or any Claude Code plugin) across multiple agent harnesses — Claude Code, Codex, Pi, Hermes."