@adia-ai/adia-ui-forge 0.8.13 → 0.8.15

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-forge",
-  "version": "0.8.13",
+  "version": "0.8.15",
   "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,24 @@
 # Changelog — adia-forge
 
+## [0.8.15] — 2026-07-26
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 11-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.15 work shipped in hover darkens in both schemes (600/550 role + filled-button wiring); find-unused adoption skill + measured routing evals. See `packages/web-components/CHANGELOG.md#0815--2026-07-26` for details.
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+
+## [0.8.14] — 2026-07-25
+
+### Fixed
+- **The in-repo plugin marketplace resolves again** (`.claude-plugin/marketplace.json`, relocated to the repo root; PR #412) — `claude plugin marketplace add` looks for the manifest at the checkout **root** unconditionally (the `owner/repo` shorthand and a git URL alike, `--sparse` or not; `--sparse` only limits which directories are checked out, it does not relocate the lookup). The old `packages/plugins/.claude-plugin/marketplace.json` location never resolved, so the documented install command had never worked. The manifest's two `source` fields were repointed at `./packages/plugins/adia-ui-{factory,forge}`.
+- **`.claude/settings.json`'s directory marketplace repointed at the repo root** — it still pointed at `./packages/plugins` after that relocation, so the repo's own dogfood plugins silently stopped loading (which is what the hooks and skills in this plugin are served through). The manifest's `name` is `adia`, so the enabled ids are `adia-forge@adia` / `adia-factory@adia`.
+- **`release-pack.mjs` generates and stages `docs/releases/vX.Y.Z.md` during the cut** (gh#399; PR #415) — the cut/from-scratch modes never produced the release-notes doc, and `check-cut-hygiene`'s success message claimed it was present without ever checking, so the gap surfaced a full cycle later at `release-pretag-docs-gate`. The v0.8.11 cut paid for it with a second PR and v0.8.13 hit the identical stop. New Step 4e runs `generate-release-notes.mjs --write` right after the bump (so the doc reads post-bump state) and Step 5 stages it; `check-cut-hygiene.mjs` gained a real `checkReleaseNotesPresent()` existence check.
+
+### Added
+- **`adia-author` records the LightningCSS remote-`@import` failure** (`skills/adia-author/references/authoring-cycle.md`; PR #418) — `bundleAsync` resolves every `@import` as a local file, `http(s)` URLs included, with no option to skip or externalize one, so a CSS-level `@import` of a Google Fonts URL breaks `npm run build:bundle-css`. It bit the 12-theme work twice; the note lives in the bundle-regen paragraph, where the failure actually surfaces.
+
+### Maintenance
+- **Plugin README version footer corrected** — it read v0.8.5 against a 0.8.13 manifest. Known gap, deliberately not fixed here: `check-cut-hygiene`'s doc-currency regex does not match that line's phrasing, which is why it drifted silently past every prior cut.
+
 ## [0.8.13] — 2026-07-25
 
 ### Maintenance

package/README.md

@@ -52,7 +52,7 @@ monorepo checkout.
 
 ---
 
-v0.8.5 — versions move with the `@adia-ai` lockstep (`npm run check:lockstep`);
+v0.8.13 — versions move with the `@adia-ai` lockstep (`npm run check:lockstep`);
 content merged between cuts is invisible to the installed plugin cache until
 the next lockstep bump or a manual sync (see `adia-release`
 `references/cut-procedure.md` §Plugin cache).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-forge",
-  "version": "0.8.13",
+  "version": "0.8.15",
   "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-author/references/authoring-cycle.md

@@ -204,7 +204,24 @@ A primitive also needs BOTH barrel registrations — the CSS `@import` in
 registration drifts the built `dist/` bundles — regenerate them in the same
 change (`npm run build:bundle-css && npm run build:bundle-js`) and commit the
 `dist/` updates, or CI's `check:{css,js}-bundles-fresh` gates fail on the PR
-(gh#390's PR shipped without this and failed exactly there).
+(gh#390's PR shipped without this and failed exactly there). Both commands,
+not just one — `theme-provider.min.js` (a JS bundle) inlines the co-emitted
+`dist/web-components.sheet.js` twin, so a CSS-only edit still drifts a JS
+bundle if only `build:bundle-css` runs (bit the v0.8.13 theme-panel work
+twice).
+
+**Never `@import` a remote URL from any file `build:bundle-css` bundles.**
+LightningCSS's `bundleAsync` (the engine behind it) resolves every `@import`
+as a local filesystem path, remote `http(s)` URLs included — a CSS-level
+`@import url('https://fonts.googleapis.com/...')` breaks the build with
+`ResolverError: No such file or directory`, not a lint warning; there's no
+`bundleAsync` option to skip or externalize one `@import`. Link web fonts
+(or anything else external) as a real `<link>` in the consumer's `<head>`
+instead — see `styles/theme-fonts-url.txt` for the pattern this repo's 12
+named themes use. A generated CSS file's own fix doesn't survive its next
+regen unless the generator is fixed too, not just the committed output —
+the standing "generated artifacts are never hand-edited" invariant
+(AGENTS.md) cuts both ways.
 
 ## Step 5 — Run the project's verification gates
 

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

@@ -369,6 +369,16 @@ function step4PromoteAndBump(args) {
   sh('npm install --package-lock-only --no-audit --no-fund', args);
   sh('npm run check:lockstep', args);
 
+  // Step 4e — generate docs/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
+  // release-pretag-docs-gate caught the SAME missing file at handoff, a full
+  // cycle later, forcing a second PR between the release PR and the tag (the
+  // v0.8.11 cut). Runs after bump so the doc's own version-currency content
+  // (package versions, CHANGELOG links) reads the post-bump state.
+  console.log('\n  Step 4e — generate docs/releases/vX.Y.Z.md:');
+  sh(`node scripts/release/generate-release-notes.mjs --version ${args.version} --write`, args);
+
   // Step 4f — pre-tag F-N1 coverage with auto-fix, run with the AUTHORITATIVE
   // matcher (check-release.mjs itself, not the drifted 9-package
   // check-changelog-coverage.mjs). Appends verified Maintenance bullets for
@@ -426,6 +436,9 @@ 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',
+    // 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`,
     ...PACKAGE_ROSTER.flatMap(({ name, dir, plugin }) => {
       // Roster-driven (H3): each package stages its manifest + CHANGELOG;
       // plugins also stage .claude-plugin/plugin.json (the /plugin-update