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

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-ui-kit-forge",
-  "version": "0.8.48",
+  "version": "0.8.50",
   "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.48",
+  "version": "0.8.50",
   "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,15 @@
 # Changelog — adia-ui-kit-forge
 
+## [0.8.50] — 2026-08-23
+
+### Maintenance
+- **Lockstep bump riding the v0.8.50 cut** (`scripts/release/check-lockstep.mjs`); the headline v0.8.50 work ships in @adia-ai/web-components (prose/verse sheet removal gh#1885 / PR #1918, input/search fill-default posture gh#1856 — see `packages/web-components/CHANGELOG.md#0850--2026-08-23`). Package-local changes are listed below.
+- **`.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.
+
+### Fixed
+- **`skills/package-release` regenerates Codex plugin manifests in Step 4 (gh#1899, PR #1917)** — `release-pack.mjs` + `cut-procedure.md` gain the post-bump `build:codex-manifests` regen so `check:codex-manifests-fresh` stays green through a cut; `a2ui-maintenance` (`mcp-pipeline-ops.md`) and `primitive-authoring` (`api-contract.md`) references refreshed in the same window.
+
 ## [0.8.48] — 2026-08-23
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-forge",
-  "version": "0.8.48",
+  "version": "0.8.50",
   "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",

package/skills/a2ui-maintenance/references/mcp-pipeline-ops.md

@@ -59,9 +59,13 @@ MCP server restart, re-run `compose_from_chunks` for a fresh `state_id`.
 When the engine breaks expectations, fire `report_issue` with the most recent
 `state_id` (reporter: `llm` for agent self-fire, `user` for a human request).
 The record lands in the engine-internal telemetry store — scratch data for
-diagnosis. Anything worth durable tracking (a recurring pattern, a fix
-proposal) belongs in a GitHub issue or the PR description of the fixing
-change.
+diagnosis. **[corrected 2026-08-23, ADR-0008 amendment]** that store is
+`qa/findings/issues/<issue_id>.json`
+(`packages/gen-ui/engine/compose/strategies/zettel/issue-reporter.js:10,26`,
+`DEFAULT_STORAGE_ROOT`) — not the original `.brain/audit-history/issues/`
+path, which was retired. Anything worth durable tracking (a recurring
+pattern, a fix proposal) belongs in a GitHub issue or the PR description of
+the fixing change.
 
 ## Validation checks
 

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

@@ -151,6 +151,8 @@ Any red → route via [`gates-catalog.md`](gates-catalog.md); fix at the source,
 
 **4d.5b. Regenerate catalog tiers + re-harvest the chunk corpus if it goes stale** (gh#1361, automated — this was a recurring manual rider before): `npm run build:catalog-tiers`, then `npm run check:chunks-fresh`; if that probe goes stale, `npm run harvest:chunks`. `tier-index.json` derives from the same post-bump catalog 4d.5 just refreshed, and the chunk harvester hashes `tier-index.json` as a harvest SOURCE — regenerating tiers without re-harvesting left `check:chunks-fresh` red on the next run, needing a manual rider commit both cuts it happened live: v0.8.39 (`72417beff`) and v0.8.40/CUT-0840-B (`d9ca8b323`, "Ran `npm run build:catalog-tiers` ... That regen staled `check:chunks-fresh` ... so re-harvested"). The re-harvest is CONDITIONAL on the freshness probe, not unconditional — a tier regen that produces a byte-identical index owes no re-harvest. `tier-index.json`, `packages/gen-ui/engine/corpus/manifest.json`, and `packages/gen-ui/engine/corpus/chunks/` all ride the release commit (Step 5 stages them).
 
+**4d.6. Regenerate the Codex plugin manifests** (gh#1888, gh#1899): `node scripts/build/codex-manifests.mjs`, then `npm run check:codex-manifests-fresh` to confirm. Both plugins' `.codex-plugin/plugin.json` embed `version` from `.claude-plugin/plugin.json`, which the 4b bump just moved — same "derived artifact carries the lockstep version" class as 4d.5's genui catalog. Gate 31 runs pre-bump in Step 3 and only proves freshness against the PREVIOUS version; nothing re-ran the generator post-bump before this line existed — the v0.8.48 release PR (#1897) shipped stale manifests as a result, caught by `check:codex-manifests-fresh` in CI and fixed by hand on the release branch. `packages/plugins/*/.codex-plugin/plugin.json` and `packages/plugins/*/skills/*/agents/openai.yaml` ride the release commit (Step 5 stages them).
+
 **4e. Release docs + team notes** (gated, not optional): review the entry
 files the release touches (root README/CHANGELOG, per-package READMEs —
 content currency is YOUR judgment; the gate only proves presence), then
@@ -212,6 +214,7 @@ node "${CLAUDE_PLUGIN_ROOT}/skills/package-release/scripts/bump.mjs" --from X.Y.
 npm install --package-lock-only --no-audit --no-fund                                          # 4c
 npm run check:lockstep                                                                        # 4d
 node scripts/build/derive-genui-catalog.mjs                                                   # 4d.5 — catalogId carries the bumped version (gh#617)
+node scripts/build/codex-manifests.mjs                                                        # 4d.6 — Codex manifest version carries the bumped version (gh#1899)
 node scripts/release/check-release.mjs --pending-version X.Y.Z --fix                          # 4f — AFTER the stubs exist
 node scripts/release/generate-release-notes.mjs --version X.Y.Z --write                       # 4e
 node scripts/release/check-release-docs.mjs --version X.Y.Z                                   # 4e gate

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

@@ -627,6 +627,29 @@ function step4PromoteAndBump(args) {
     console.log('  ✓ chunk corpus still fresh after catalog-tiers regen — no re-harvest needed');
   }
 
+  // Step 4d.6 — regenerate the Codex plugin manifests (gh#1888, gh#1899): both
+  // .codex-plugin/plugin.json's `version` and each per-skill agents/openai.yaml
+  // derive from .claude-plugin/plugin.json, which the bump above just moved —
+  // same "derived artifact embeds the lockstep version" class as 4d.5's genui
+  // catalog. Gate 31 (check:codex-manifests-fresh) runs pre-bump in Step 3, so
+  // it only proves freshness against the PREVIOUS version; nothing re-ran the
+  // generator after the bump until now — the release PR for v0.8.48 (#1897)
+  // shipped stale manifests as a result (Static checks + MCP smoke failed on
+  // check:codex-manifests-fresh, fixed by hand on the release branch). Step 5
+  // stages both plugins' .codex-plugin/plugin.json + skills/*/agents/openai.yaml.
+  console.log('\n  Step 4d.6 — regenerate Codex plugin manifests (version embeds the lockstep bump):');
+  sh('node scripts/build/codex-manifests.mjs', args);
+  if (args.dry) {
+    console.log('  [dry] npm run check:codex-manifests-fresh (post-regen proof)');
+  } else if (!shOk('npm run check:codex-manifests-fresh')) {
+    console.error('\nERROR: Codex plugin manifests still stale after regeneration — codex-manifests.mjs');
+    console.error('       did not produce output matching check:codex-manifests-fresh\'s expectations.');
+    console.error('       Run both by hand to diagnose before re-running the cut.');
+    process.exit(1);
+  } else {
+    console.log('  ✓ Codex plugin manifests fresh after regeneration');
+  }
+
   // Step 4e — generate docs/ops/releases/vX.Y.Z.md (gh#399: neither this step nor
   // its staging into the release commit existed before — check-cut-hygiene's
   // "notes present" claim (Step 4g, below) went unverified until
@@ -747,7 +770,17 @@ function step5Commit(args) {
       // generation MCP (@adia-ai/mcp) in .mcp.json (SKILL invariant 8 —
       // bump.mjs moves the pin too).
       const files = [`${dir}/package.json`, `${dir}/CHANGELOG.md`];
-      if (plugin) files.push(`${dir}/.claude-plugin/plugin.json`);
+      if (plugin) {
+        files.push(`${dir}/.claude-plugin/plugin.json`);
+        // gh#1899: Step 4d.6 regenerates both plugins' Codex manifest tree
+        // post-bump (version embeds the lockstep bump, same class as the
+        // genui catalog outputs above) — stage it here or CI catches the
+        // drift the way v0.8.48's release PR (#1897) did. `skills/*/
+        // agents/openai.yaml` is a glob: `git add` expands it via the shell,
+        // and the per-skill count isn't statically knowable (same shape as
+        // the chunk-corpus directory pathspec above).
+        files.push(`${dir}/.codex-plugin/plugin.json`, `${dir}/skills/*/agents/openai.yaml`);
+      }
       if (name === 'adia-ui-factory') files.push(`${dir}/.mcp.json`);
       return files;
     }),
@@ -1169,6 +1202,17 @@ function selftest() {
       // health record, or it rides untracked past the release commit
       // (v0.8.35/v0.8.36 both did, PR #1196 swept them by hand).
       'evals/health/9.9.9.json',
+      // gh#1899 — Step 4 must regenerate the Codex plugin manifests post-bump
+      // (the v0.8.48 release PR #1897 shipped stale ones without this step).
+      'Step 4d.6 — regenerate Codex plugin manifests',
+      '[dry] node scripts/build/codex-manifests.mjs',
+      // gh#1899 — Step 5's staging pathspec must carry both plugins' Codex
+      // manifest tree, or it rides untracked/uncommitted past the release
+      // commit the same way the genui catalog outputs did before gh#617.
+      'packages/plugins/adia-ui-forge/.codex-plugin/plugin.json',
+      'packages/plugins/adia-ui-forge/skills/*/agents/openai.yaml',
+      'packages/plugins/adia-ui-factory/.codex-plugin/plugin.json',
+      'packages/plugins/adia-ui-factory/skills/*/agents/openai.yaml',
     ];
     for (const marker of need) {
       if (!out.includes(marker)) {

package/skills/primitive-authoring/references/api-contract.md

@@ -119,6 +119,30 @@ shape — see the ADR-0063 conventions list in
 
 Source: [ADR-0074](../../../../../../docs/ops/adr/adr-0074-chart-ratio-attribute-grammar.md).
 
+**[verified 2026-08-23] Failure mode — DOM-ancestry auto-detection is riskier
+than container-query auto-detection.** ADR-0081 Decision 1 (`chart-ui[labels]`,
+a 3-value enum: `""`/`chip`/`outside`) initially mirrored this same
+auto/explicit-override shape, but auto-detected via DOM ancestry — resolving
+unset `labels=""` to `chip` whenever the element sat inside a `section[bleed]`
+or `card-ui[padding="none"]` ancestor — instead of a container query on the
+element's own box. The 2026-08-21 amendment walked that back entirely after it
+silently flipped 2 of 60 fixtures on the Charts visual-eval floor
+(`comp-chart-in-card-n-*`, pre-existing full-bleed compositions), caught only
+by the floor's pixel-diff gate — neither the unit-test suite nor code review
+renders real CSS/layout. Amended decision: unset `labels=""` resolves to
+`outside` unconditionally; `chip` mode activates only via the explicit
+`labels="chip"` attribute — no ancestry detection at all. ADR-0081's Decision
+2 (a `today` marker attribute) independently rejects clock-derived
+auto-detection for the same reliability reason (cites IDR-0006). Lesson for a
+new auto-snap attribute of this shape: auto-detection is safe when it reads
+the element's *own* rendered geometry (a container query against its own box,
+as `ratio` does); it is risky when it reads *ancestor* DOM state or wall-clock
+time, because neither is guaranteed stable across every composition that
+happens to nest the element — verify any such default against a real
+pixel-diff/visual-eval gate, not unit tests or review alone. Source:
+[ADR-0081](../../../../../../docs/ops/adr/adr-0081-chart-2-0-foundations-attribute-grammar.md)
+Amendment (2026-08-21).
+
 ## Numeric props — `null` over sentinels
 
 Indeterminate, unknown, or "not yet set" numeric state uses `null`, not `-1` or `Infinity`: