@adia-ai/adia-ui-forge 0.8.20 → 0.8.21

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-forge",
-  "version": "0.8.20",
+  "version": "0.8.21",
   "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-factory (the consumer/app-author plugin).",
   "author": {
     "name": "Kim",

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog — adia-forge
 
+## [0.8.21] — 2026-07-28
+
+### Fixed
+- **Pre-cut gate roster 23 → 24** (`skills/adia-release/scripts/gate-roster.mjs`) — adds `check:brand-assets` (the Adia mark must be token-driven, never a baked `agent-ui-*.svg`; gh#473). `cut-procedure.md` §3.1's transcribed table and the SKILL/gates-catalog counts moved with it, and the cut-hygiene gate renumbered 23 → 24; doc-vs-module equality re-verified programmatically (24/24 in sync, contiguous numbering).
+
+- **`release-pack.mjs` stages the root CHANGELOG it promotes** — the gh#453 machinery renamed root `[Unreleased]` → `[X.Y.Z]` at Step 4 but the Step 5 stage roster predated it, so the v0.8.20 cut promoted the heading and shipped without it (main kept `[Unreleased]`; the rename sat uncommitted in the cutter's working tree). `CHANGELOG.md` joins `releaseFiles`; the stranded v0.8.20 rename rides this same PR.
+
+### Maintenance
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+
 ## [0.8.20] — 2026-07-28
 
 ### Maintenance

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-forge",
-  "version": "0.8.20",
+  "version": "0.8.21",
   "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-factory (the consumer/app-author plugin).",
   "keywords": [
     "adia-ui",

package/skills/adia-deploy/SKILL.md

@@ -95,7 +95,13 @@ delete-adjudication classes.
    prod-only runtime-written files (feedback logs wiped 2026-06-10).
 3. Snapshot prod: `cp -al /srv/<app>/dist /srv/<app>/dist.bak-<date>`
    (hardlink farm — instant, and the only rollback).
-4. Real rsync — the dry-run minus `-n`, SAME excludes.
+4. Real rsync — the dry-run minus `-n`, SAME excludes, and the SAME BYTES:
+   both jobs rsync the artifact-round-tripped tree, and the deploy job aborts
+   if its tree's sha256 fingerprint differs from the one whose delete summary
+   was approved (gh#425 — the dry-run used to read the build job's own
+   `dist/`, so the v0.8.14 summary listed 3,128 deletions the real send never
+   performed; an over-reporting summary trains reviewers to approve past scary
+   numbers, and the same gap can under-report).
 5. Verify a fixture **file** that only exists in the new build, then
    render-check a `/site/components/*` page headlessly (SPA returns 200 shell
    for any route; file presence alone misses the llm-404 class).

package/skills/adia-release/SKILL.md

@@ -93,7 +93,7 @@ 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 of the 11 packages 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 23-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 of the 11 packages 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 24-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` (12 tags, `--delete` to move), `dispatch-publish.mjs` (publish workflows; `--verify-triggered` re-dispatches only missing runs; `--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.
 

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

@@ -111,7 +111,8 @@ npm run verify:site-a2ui                       # 19 site-a2ui rows vs source fra
 npm run verify:contrast                        # 20 WCAG AA — canvas-text AND text-on-fill
 npm run check:token-semantics-sync             # 21 adia-tokens generated refs vs token sources
 npm run check:demo-routes                      # 22 demo surfaces routed + patterns indexed
-node scripts/release/check-cut-hygiene.mjs --version <mode-dependent>  # 23 README CDN-pin + version currency — CUT modes pre-flight at the PREVIOUS version (the README claim is exact-match and only moves at the Step-4 bump; Step 4g re-proves at the cut version), HANDOFF pre-flights at the CUT version (post-merge, the claim already moved)
+npm run check:brand-assets                     # 23 brand mark token-driven, not baked raster
+node scripts/release/check-cut-hygiene.mjs --version <mode-dependent>  # 24 README CDN-pin + version currency — CUT modes pre-flight at the PREVIOUS version (the README claim is exact-match and only moves at the Step-4 bump; Step 4g re-proves at the cut version), HANDOFF pre-flights at the CUT version (post-merge, the claim already moved)
 ```
 
 Any red → route via [`gates-catalog.md`](gates-catalog.md); fix at the source, re-run the narrowest gate, then re-run the full sequence. The canonical miss: a cut that ran 7 of the gates shipped a stale-embeddings defect that surfaced a day later and cost a tag-move recovery.

package/skills/adia-release/references/gates-catalog.md

@@ -202,7 +202,7 @@ npm run check:demo-shells
 
 Add `verify:corpus` + `check:embeddings-fresh` if chunks were touched; `check:lightningcss-build` if CSS was touched; F-N1 if unpushed release tags exist.
 
-**Full pre-cut sweep** — the 23-gate roster in [`cut-procedure.md`](cut-procedure.md) §Step 3, sourced from `` `${CLAUDE_PLUGIN_ROOT}/skills/adia-release/scripts/gate-roster.mjs` `` (the ONE list; `release-pack.mjs` imports and runs it in full — a subset run is impossible without editing that file). ~90s wall time.
+**Full pre-cut sweep** — the 24-gate roster in [`cut-procedure.md`](cut-procedure.md) §Step 3, sourced from `` `${CLAUDE_PLUGIN_ROOT}/skills/adia-release/scripts/gate-roster.mjs` `` (the ONE list; `release-pack.mjs` imports and runs it in full — a subset run is impossible without editing that file). ~90s wall time.
 
 **Omnibus** — `npm run check` invokes everything. Heavy; use when re-baselining a stale checkout.
 

package/skills/adia-release/scripts/gate-roster.mjs

@@ -54,11 +54,16 @@ export const GATE_ROSTER = [
   // components/modules with .examples.html need a /site/components route,
   // catalog patterns need their Pattern Library sitemap entry.
   { n: 22, cmd: 'npm run check:demo-routes',                   what: 'demo surfaces routed + patterns indexed' },
+  // gh#473: the brand mark must be token-driven (<adia-mark-ui>), never a
+  // baked agent-ui-*.svg — a light-only raster cannot invert for dark mode,
+  // and 54 authored files (mostly harvested *.contents.html) had been
+  // teaching the anti-pattern to the generative corpus.
+  { n: 23, cmd: 'npm run check:brand-assets',                  what: 'brand mark token-driven, not baked raster' },
   // versionArg: the runner appends ` --version X.Y.Z` (release-pack knows the
   // cut version; the roster stays a static list). Objective half of the
   // v0.7.13-retro hygiene checker — README CDN pins / "Current version"
   // claims vs the cut version; branch/worktree limbo prints as warns (H2).
-  { n: 23, cmd: 'node scripts/release/check-cut-hygiene.mjs',  what: 'README CDN-pin + version currency', versionArg: true },
+  { n: 24, cmd: 'node scripts/release/check-cut-hygiene.mjs',  what: 'README CDN-pin + version currency', versionArg: true },
 ];
 
 // -- CLI ------------------------------------------------------------------

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

@@ -453,6 +453,12 @@ function step5Commit(args) {
     // (REPO_PINNED_REFS); gate 18 (check-cut-hygiene doc-currency) exact-matches
     // it against the cut version, so it must ride the release commit.
     'README.md',
+    // Root CHANGELOG — the gh#453 promotion machinery renames its
+    // [Unreleased] heading at Step 4, but this roster predated it, so the
+    // v0.8.20 cut promoted the heading and then shipped WITHOUT it (the
+    // rename sat uncommitted in the cutter's working tree while main kept
+    // [Unreleased]). Promotion and staging must travel together.
+    'CHANGELOG.md',
     // gh#399: Step 4e generates this but never staged it before — it landed
     // in a second PR after the release commit instead (v0.8.11 cut).
     `docs/releases/v${args.version}.md`,