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

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-forge",
-  "version": "0.8.21",
+  "version": "0.8.22",
   "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.22] — 2026-07-29
+
+### Fixed
+- **`release-pack.mjs` Step 10 failures name their reason** — `shOk` discarded stderr, so a release-create that failed twice reported "could not be created" with an expired gh token, a network reset, and a bad notes file all indistinguishable. Create calls now pass `{ report: true }` (stderr surfaced, first 3 lines); existence probes stay silent since their failure is the answer.
+- **`release-pack.mjs` Step 10 is idempotent and resumable** — the GH-release loop called `gh release create` unconditionally, so ONE network blip aborted the whole handoff. The v0.8.21 cut hit exactly that: `connection reset by peer` with 4 of 11 releases made, *after* tags were pushed and all 9 packages published — the irreversible half done, the bookkeeping half stranded, and a plain re-run then failing on "release already exists" for the first 4 (repaired by hand). Now: a non-throwing `shOk()` probe skips releases that already exist, one retry absorbs a transient reset, and a genuine failure reports created/skipped/failed counts plus the fact that tags and publishes are unaffected — re-running the same handoff command finishes the job. Verified against the live v0.8.21 releases: 11 detected as existing, 0 would be re-created, and the probe returns false for a bogus tag (no false-positive skips).
+
+### Maintenance
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+- **`skills/` touched in this release window** (1 file(s), e.g. `scripts/release-pack.mjs`) — carried by the entries above.
+
 ## [0.8.21] — 2026-07-28
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-forge",
-  "version": "0.8.21",
+  "version": "0.8.22",
   "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-release/scripts/release-pack.mjs

@@ -226,6 +226,28 @@ function shQuiet(cmd, args) {
   return execSync(cmd, { cwd: REPO, encoding: 'utf8' });
 }
 
+/** Run a command for its EXIT STATUS only — true on 0, false on anything
+ *  else, never throws and never streams. For probes and retryable steps
+ *  where a non-zero exit is an expected answer, not a crash (Step 10's
+ *  "does this release already exist?" and its one transient retry).
+ *  Pass { report: true } for the CREATE calls: stderr is then captured and
+ *  printed on failure, so "could not be created" names its reason — an
+ *  expired gh token, a network reset, and a bad notes file were previously
+ *  indistinguishable (reviewer note, 2026-07-29). Probes stay silent:
+ *  their failure IS the answer. */
+function shOk(cmd, { report = false } = {}) {
+  try {
+    execSync(cmd, { cwd: REPO, encoding: 'utf8', stdio: ['ignore', 'ignore', 'pipe'] });
+    return true;
+  } catch (e) {
+    if (report) {
+      const err = (e.stderr || e.message || '').toString().trim().split('\n').slice(0, 3).join('\n    ');
+      if (err) console.error(`    stderr: ${err}`);
+    }
+    return false;
+  }
+}
+
 // Runs a command and CAPTURES its combined output instead of streaming it —
 // used where the output itself becomes evidence in a later checkpoint's
 // evidence block (H5), rather than just scrolling past in the terminal.
@@ -660,9 +682,47 @@ async function step10GhAndSite(args) {
     console.error(`ERROR: GH notes file not found: ${args.ghNotesFile}`);
     process.exit(2);
   }
+  // Idempotent + resumable (v0.8.21 incident): this loop used to `gh release
+  // create` unconditionally, so ONE network blip aborted the whole handoff —
+  // that cut died on `connection reset by peer` with 4 of 11 releases made,
+  // after tags were pushed and all 9 packages were already published. The
+  // irreversible half of the release had happened; only the bookkeeping half
+  // was half-done, and a plain re-run then failed on "release already exists"
+  // for the first 4. So: skip what exists, create what doesn't, retry a
+  // transient failure, and report what remains instead of throwing away the
+  // work that succeeded. Re-running Step 10 after ANY partial failure is now
+  // safe and finishes the job.
+  const created = [];
+  const skipped = [];
+  const failed = [];
   for (const pkg of PACKAGES) {
-    sh(`gh release create "${pkg}-v${args.version}" --title "${args.scope}/${pkg} v${args.version}" --notes-file ${args.ghNotesFile}`, args);
+    const tag = `${pkg}-v${args.version}`;
+    if (!args.dry && shOk(`gh release view "${tag}"`)) {
+      skipped.push(pkg);
+      console.log(`  = ${tag} — already exists, skipping`);
+      continue;
+    }
+    const cmd = `gh release create "${tag}" --title "${args.scope}/${pkg} v${args.version}" --notes-file ${args.ghNotesFile}`;
+    // One retry: the observed failure mode is a transient TLS/connection
+    // reset against api.github.com, not a bad request.
+    let ok = args.dry ? (sh(cmd, args), true) : shOk(cmd, { report: true });
+    if (!ok && !args.dry) {
+      console.log(`  … ${tag} failed once (transient?) — retrying in 3s`);
+      sh('sleep 3', args);
+      ok = shOk(cmd, { report: true });
+    }
+    (ok ? created : failed).push(pkg);
+    if (ok) console.log(`  ✓ ${tag}`);
+  }
+  if (failed.length > 0) {
+    console.error(`\nERROR: ${failed.length}/${PACKAGES.length} GH release(s) could not be created: ${failed.join(', ')}`);
+    console.error(`  ${created.length} created, ${skipped.length} already existed.`);
+    console.error('  Tags and npm publishes are DONE and unaffected — only the GH-release');
+    console.error('  bookkeeping is incomplete. Re-run this same handoff command: the loop');
+    console.error('  skips what exists and creates only the remainder.');
+    process.exit(1);
   }
+  console.log(`  ✓ GH releases: ${created.length} created, ${skipped.length} already present (${PACKAGES.length} total)`);
   if (args.skipSite) {
     console.log('  --skip-site set; skipping EXE deploy');
     return;