@adia-ai/adia-ui-forge 0.8.37 → 0.8.38

package/skills/primitive-authoring/references/module-promotion.md

@@ -119,7 +119,7 @@ The "stripped" consumer. Same structural change minus persistence.
 
 ### Phase 4 — Migrate the chunk corpus
 
-The harvested training-corpus chunk (`packages/a2ui/corpus/chunks/<name>.json`) embeds the consumer's HTML as an escaped string. Update it so the LLM sees the new authoring shape.
+The harvested training-corpus chunk (`packages/gen-ui/a2ui/corpus/chunks/<name>.json`) embeds the consumer's HTML as an escaped string. Update it so the LLM sees the new authoring shape.
 
 1. **Preferred** — re-run the harvester:
 
@@ -144,7 +144,7 @@ The harvested training-corpus chunk (`packages/a2ui/corpus/chunks/<name>.json`)
 3. **Defensive grep across all chunks** for the legacy markers:
 
    ```bash
-   grep -l 'id="<old-id>"' packages/a2ui/corpus/chunks/*.json
+   grep -l 'id="<old-id>"' packages/gen-ui/a2ui/corpus/chunks/*.json
    ```
 
 4. **Gotcha — hand-edit + later re-harvest** — if you used the fallback (step 2) AND a peer later adds your consumer's directory to harvester SOURCES, the next `harvest:chunks` run will overwrite your hand-edit with the live consumer HTML. Usually that's _good_ (the re-harvest captures the live state, including any post-edit consumer updates), but diff before assuming. Concrete example: theme-panel's `playground-app-shell.json` was hand-edited, then re-harvested after `playgrounds/` was added to SOURCES — the re-harvest captured the `<aside-ui>` → `<admin-sidebar>` bespoke conversion that the hand-edit missed.

package/skills/site-deployment/SKILL.md

@@ -88,9 +88,9 @@ delete-adjudication classes.
 1. Build from clean, fully-merged `main`. In a fresh worktree,
    `npm run build -w @adia-ai/llm` runs **before** `build:site` — llm compiles
    at publish time and its outputs are gitignored, so without it
-   `/packages/llm/index.js` 404s and component registration breaks site-wide
+   `/packages/llm/core/index.js` 404s and component registration breaks site-wide
    (found live 2026-06-09).
-2. Dry-run `rsync -azni --delete --exclude='packages/a2ui/corpus/feedback/'`
+2. Dry-run `rsync -azni --delete --exclude='packages/gen-ui/a2ui/corpus/feedback/'`
    and bucket **every** `*deleting` line into a known-safe class; any
    unexplained served-content delete aborts the deploy. The exclude protects
    prod-only runtime-written files (feedback logs wiped 2026-06-10).

package/skills/site-deployment/references/deploy-playbooks.md

@@ -129,8 +129,8 @@ itself is unavailable.
      ```
      The `llm` package **compiles its JS at publish time** and its outputs are
      **gitignored** — so a fresh worktree (or any tree that hasn't published llm
-     locally) has no `packages/llm/index.js`, `build:site` copies nothing, and
-     **`/packages/llm/index.js` 404s on the deployed site → component registration
+     locally) has no `packages/llm/core/index.js`, `build:site` copies nothing, and
+     **`/packages/llm/core/index.js` 404s on the deployed site → component registration
      breaks on every `/site/components/*` page** (the docs components reference it). Found
      **live 2026-06-09**; the **0-delete dry-run proved it had never been deployed** (the
      file was absent on the server, so there was nothing to delete — not a regression, a
@@ -145,22 +145,22 @@ itself is unavailable.
      deploy gaps). After any package add/rename, check `site.mjs` before deploying.
 2. **Dry-run first, and adjudicate every delete — BEFORE the real rsync, never after:**
    ```sh
-   rsync -azni --delete --exclude='packages/a2ui/corpus/feedback/' \
+   rsync -azni --delete --exclude='packages/gen-ui/a2ui/corpus/feedback/' \
      dist/ <host>.exe.xyz:/srv/<app>/dist/   # -n simulates · -i itemizes
    ```
    - **Exclude server-side runtime-written paths.** Some files exist ONLY on prod —
      written by the running service at runtime, never present in a local build — so
      `--delete` wipes them on every deploy. Known class on ui-kit:
-     `packages/a2ui/corpus/feedback/*.jsonl` (the gen-UI canvas training-feedback log).
+     `packages/gen-ui/a2ui/corpus/feedback/*.jsonl` (the gen-UI canvas training-feedback log).
      Found **live 2026-06-10** (the deploy deleted the day's feedback log; restored from
      the pre-deploy snapshot). Carry the same `--exclude` list on BOTH the dry-run and
      the real rsync; when a new runtime-written path appears, add it here.
    - `*deleting` lines = files removed from prod. Bucket **every one** into a known-safe
      class; **abort if any served-content delete is unexplained.** Safe classes seen on
      ui-kit: gallery review artifacts (`apps/genui/.../review/cycle-*/`), stale
-     `packages/a2ui/retrieval/` + eval reports, **content-hash-rotated** CodeMirror
+     `packages/gen-ui/a2ui/retrieval/` + eval reports, **content-hash-rotated** CodeMirror
      chunks (`code/{chunk,dist}-<hash>.js` — old hash deleted, new hash sent = rotation,
-     not loss), restructured `packages/llm/*.js` dist copies, `node_modules/`
+     not loss), restructured `packages/llm/core/*.js` dist copies, `node_modules/`
      symlink-farm dirs, and refactor-orphaned app files. None are served HTML.
    - **Don't panic at the send count.** A fresh local build never mtime-aligns with the
      remote, so `rsync -a` flags ~every file as a send (`<f..t` = mtime-only touch). Only
@@ -176,7 +176,7 @@ itself is unavailable.
    mutating in place. Restore with `rm -rf dist && mv dist.bak-<date> dist`.
 4. **Deploy** (the dry-run, minus `-n` — SAME excludes):
    ```sh
-   rsync -az --delete --exclude='packages/a2ui/corpus/feedback/' \
+   rsync -az --delete --exclude='packages/gen-ui/a2ui/corpus/feedback/' \
      dist/ <host>.exe.xyz:/srv/<app>/dist/
    ```
 5. **Verify the FILE, not the route.** A SPA returns `200` + the app shell for *any*
@@ -205,7 +205,7 @@ itself is unavailable.
 >
 > **The one exception — `@adia-ai/llm` (2026-06-09):** llm is NOT a source-tree
 > component; it **builds its JS at publish** (gitignored outputs), so `build:site` copies
-> nothing for it in a fresh worktree and `/packages/llm/index.js` 404s → component
+> nothing for it in a fresh worktree and `/packages/llm/core/index.js` 404s → component
 > registration breaks site-wide. Run `npm run build -w @adia-ai/llm` **before** `build:site`
 > (step 1 above). This is exactly why step 5 render-checks a **`/site/components/*`** page,
 > not just a fixture file — the 404 is invisible to file-presence and to the SPA shell.

package/skills/site-docs-authoring/intent.md

@@ -49,7 +49,7 @@ before they start typing.
 
 ## fences
 - NOT for `packages/web-components/components/*/*.examples.html` component demo pages (primitive-authoring)
-- NOT for `site/pages/examples/**`, `site/pages/gen-ui/**`, `packages/a2ui/corpus/exemplars/**` — pure primitive-composition training-harvest surfaces with their own no-style-block rule (`composition-and-examples.md`, a2ui-maintenance)
+- NOT for `site/pages/examples/**`, `site/pages/gen-ui/**`, `packages/gen-ui/a2ui/corpus/exemplars/**` — pure primitive-composition training-harvest surfaces with their own no-style-block rule (`composition-and-examples.md`, a2ui-maintenance)
 - NOT for the A2UI generation pipeline itself, chunk corpus, or MCP tools (a2ui-maintenance)
 
 ## assertions