@adia-ai/gen-ui 0.8.37

package/compose/CHANGELOG.md

@@ -0,0 +1,1707 @@
+# Changelog — @adia-ai/a2ui-compose
+
+## [0.8.36] — 2026-08-13
+
+### Fixed
+- **This package was uninstallable from npm, and unbootable if it had installed (gh#1186).** Two independent defects, found while chasing why `@adia-ai/a2ui-mcp@0.8.35` could not run standalone:
+  - **`"@genui/producer": "*"` in `dependencies`.** That package is a vendored tree (`packages/genui/*`, synced by `scripts/build/sync-genui.mjs`, guarded by `check:genui-vendor`) marked `"private": true`, so it is not on the registry and never will be. `npm install @adia-ai/a2ui-compose` 404'd before any code ran — no import fix could have rescued it. `core/plan-turn.js` needed exactly two pure, dependency-free functions from it, so they now live here as `core/plan-primitives.js`; the dependency is gone. `core/plan-primitives.test.js` runs both implementations over 17 shared fixtures and fails if the copy drifts from the vendored upstream, and being a test it never ships.
+  - **42 module specifiers walked out of the package root** (`../../validator/validator.js`, `../../retrieval/intent/clarity.js`, `../../../llm/llm-bridge.js`, `../../../runtime/registry.js`, `../../corpus/scripts/chunk-library.js`, …). They resolve only because the monorepo puts those directories there. All now import the sibling by its npm specifier.
+- **`shared/` was missing from `files` (gh#1186).** `core/generator.js` and the four free-form composer entry points import `shared/validate-and-repair.js` — inside this package, but never packed. Any consumer reaching the validate-and-repair loop got `ERR_MODULE_NOT_FOUND`. Now shipped.
+
+### Added
+- **`exports` gains `./core/*`, `./strategies/*`, `./shared/*`, `./transpiler/*`.** Additive — the fixed keys (`./core`, `./strategies/zettel`, `./strategies/registry`, `./transpiler`, `./evals`, and the `./engines/*` aliases) all still resolve to the same files, and Node prefers an exact key over a wildcard. Needed so siblings can name the modules they actually use (`@adia-ai/a2ui-compose/strategies/zettel/chunk-refiner`) instead of reaching in by path.
+- **`@adia-ai/a2ui-corpus` declared as a dependency.** The zettel chunk composer/refiner/synthesizer have always used its chunk library; the dependency was simply never written down.
+
+## [0.8.35] — 2026-08-13
+
+### Added
+- **The default `auto` engine now gates every non-terminal round on schema + catalog conformance, even with no caller `ctx.gate` (gh#1135, WS-4 SPEC REQ-01).** `generateAutoAdapter` (`strategies/registry.js`) supplies a `defaultAcceptanceGate` — the same `validateSchema`/`validateMessages` validators the adia-producer's own always-on gate composes, reused directly rather than importing that consumer's module — ANDed with any caller-supplied gate (never replaced by it), so a lax caller gate can no longer re-open the seam. Previously the exit gate only ran when a caller explicitly passed `ctx.gate`; the default `auto` path passed none.
+- **`judgeEngineResult` (`strategies/escalation.js`) no longer blanket-accepts a strong-emission strategy (`composition-match`/`composition-iterated`/`free-form-composed`) — gh#1135 REQ-02.** When the engine has normalized its own `validation.valid: false`, the ladder now rejects with a new `strong-emission-invalid` code and climbs, instead of trusting the strategy label unconditionally. An engine reporting no `validation.valid` field rides the same pass-through as before, caught by REQ-01's default gate instead.
+- **The ladder's terminal engine (`monolithic-pro` / `generate-pro.js`) now returns a first-class `acceptance: {accepted, exhausted, failures}` block (gh#1135 REQ-03).** The terminal step is still never exit-gated (the ladder's floor, availability contract unchanged — messages are always returned) but its own repair-loop exhaustion, previously computed and silently discarded, now survives onto the result. A new `buildFailures()` helper in `shared/validate-and-repair.js` normalizes schema + catalog failures into the block's `{code, message}[]` shape.
+- **`projectEngineResult` (`strategies/registry.js`) — the canonical consumer-facing projection of an engine result, including `acceptance` (gh#1135 REQ-04).** A serialization boundary that hand-rolls its own field whitelist silently drops a newly added first-class field; the MCP `generate_ui` tool (`@adia-ai/a2ui-mcp`) now builds its response off this projection instead of restating the field list.
+
+### Changed
+- **`free-form-composer`'s `validation.score` is now the measured `schemaCheck.validation.score`, not the hardcoded 85 (gh#1135, WS-4 SPEC REQ-05).** Full schema/catalog validation has run on every `free-form-composed` result since the A2UI overhaul (Phase 3), but nothing read its score — the release trip-wire's `avgScoreWhenEmitted` floor (`check-free-form-eval-regression.mjs`) could therefore only move when the pipeline broke outright. `validation.valid` is now first-class too (REQ-02); `schemaValid`/`schemaValidation` remain as the pre-existing side fields. The floor itself is re-derived from the first honest measured run under adia-a2ui's ownership (preserve-not-regress cadence) — not touched by this change.
+
+## [0.8.34] — 2026-08-11
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the lockstep version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.34 work shipped in date-range-picker unified selection, core boolean-reflect fix, nav state-color spec, component polish + docs repair wave. See `packages/web-components/CHANGELOG.md#0834--2026-08-11` for details.
+- **`transpiler/` touched in this release window** (4 file(s), e.g. `transpiler/command-options.test.js`) — carried by the entries above.
+
+## [0.8.33] — 2026-08-11
+
+### Added
+
+- **`figure` / `figcaption` / `s` in `HTML_TAG_MAP` (gh#853).** `figure` → `Card` (self-contained content unit, same treatment `article` already gets); `figcaption` → `Text[variant=caption]` (text.yaml's own `caption` variant docstring names "image captions" as its intended use). `<s>` (strikethrough) → `Text[variant=body]`, same phrasing-content treatment `strong`/`em`/`blockquote` already get — no primitive carries a strike/decoration prop today, a platform gap beyond this tag-mapping fix. All three previously fell to the Unknown fallback (`/site/patterns/admin-sidebar`, `/site/patterns/kanban-board`).
+- **`extractCatalogProps` gains an `object` branch, sibling of the existing `array` one (gh#853).** Object-typed catalog props (`InvoiceDetail.invoice`, `NotificationPreferences.channelEnabled`) are JSON-encoded HTML attributes exactly like array-typed ones (TKT-0010) — parsed the same way, just asserting a plain object instead of an array. Previously fell through to the generic string branch (never taken, since `raw` never satisfied a JSON-object grammar check that didn't exist) and the prop was silently dropped.
+- **`extractCatalogProps` falls back to the kebab-cased attribute name for camelCase catalog prop keys (gh#853).** `hrefPattern`/`channelEnabled`-shaped catalog keys are authored as kebab-case HTML attributes per the yaml's own `attribute:` override, but that override isn't preserved into the generated catalog and HTML attribute names are always lowercased on parse (`channelenabled` ≠ `channelEnabled`), so the direct lookup silently missed every one of them. Generalized fix, not a per-component special-case — closes the same drift class §163's catalog-driven pass already targets.
+
+### Changed
+
+- **Unknown tags now always report through `unmappedTags` (gh#848).** The transpiler's last-resort `// 6. Unknown → Column` branch dropped the element's props and said nothing anywhere; a childless custom element (the normal shape for a data-driven composite like `<admin-roster-ui>`) became a literally empty box, and 24 site pages shipped blank sections for four days before gh#847's instrumentation named the class. Two changes: (1) **`transpileHTML` now always returns `unmappedTags: string[]`** — every tag that reached the Unknown branch, so no caller has to rediscover the loss by eyeballing output. Purely additive; `messages`/`validation`/`suggestions` are unchanged. (2) a new **`unknownTagPolicy` option** (`'silent'` default | `'placeholder'`) controls the *payload*: `placeholder` emits `Column[data-unmapped-tag] > Alert(variant="warning")` naming the tag, plus the element's own converted children, so the degrade is visible on a rendered page. Built from REGISTERED constructs only — the wire payload stays valid (validator's `allTypesRegistered` passes) — and carries no raw CSS, since alert-ui's warning variant is entirely semantic-token driven.
+- **The policy split is deliberate.** `placeholder` is opted into by the docs/site-a2ui conversion path (`scripts/build/lib/docs-transpiler.mjs`), whose only channel to a human is the rendered page. The default stays `silent` for the corpus harvester (`harvest-chunks.mjs`) and the zettel chunk-synthesizer, which produce REUSABLE composition templates — an injected developer notice there would travel into generated product UI — and for `packages/llm/server.js`. Those callers get the same information via `unmappedTags`.
+- **MCP `convert_html` output gains one additive top-level key.** The tool returns `JSON.stringify(transpileHTML(...))` verbatim, so `unmappedTags` now appears alongside `messages`/`validation`/`suggestions`. No input schema change, no key removed, no key retyped; the tool's payload for fully-mapped HTML differs only by `"unmappedTags": []`. Dry-run diff taken across mapped / unknown-bearing / empty inputs before landing (recorded in gh#848); `npm run mcp:smoke` 4/4.
+
+### Added
+
+- **`dl` / `dt` / `dd` in `HTML_TAG_MAP`** (`DescriptionList` / `DescriptionTerm` / `DescriptionDetail`). `<description-list-ui>` renders a native `dl` and its documented children are native `dt`/`dd`, which previously fell to the Unknown fallback — the term/detail grid collapsed into nested containers on every converted page carrying a description list.
+
+### Maintenance
+- **`strategies/` touched in this release window** (1 file(s), e.g. `monolithic/_shared.js`) — carried by the entries above.
+
+## [0.8.32] — 2026-08-09
+
+### Fixed
+- **Retrieval-sourced compositions are refinable at all (gh#832).** Every Tier-1 hit returned `plan: null`, and a plan is the only thing `refineFromIntent`/`applyOps` can address — so both declined with `priorState has no plan; cannot refine`, and the product's refine verb (`refine_composition`, the chat agent's refine turn) silently no-opped on the *entire* retrieval tier, real LLM or stub. `composeFromIntent`'s fast path now emits the plan that describes what it actually returned: `{ page: <hit>, slot_bindings: {} }` — a single-chunk plan, the shape a direct hit genuinely has. Both tiers now emit the same structure, so nothing downstream (`get_state`, `_debug.plan`, the eval, refine) has to special-case which tier produced a composition. Chosen over deriving a plan inside refine (identical fidelity, but `compose_from_chunks`, `get_state` and `_debug.plan` would all keep advertising `null`) and over a plan-less "re-compose with context" branch (a second refine path that discards the prior UI — and it falls out of this fix for free: a single-chunk plan has no addressable slots, so the only legal op is `replacePage`, which is re-compose-with-context expressed in the existing validated op vocabulary). The refiner's locator/modifier prompts learn that case explicitly — bind the prior chunk into the new shell alongside the requested addition, so the existing UI survives a refinement — and the prior plan's own chunks are force-added to the modifier's catalog, which is pre-searched on the *change* and so had no reason to surface the chunk being refined. Measured on the 20-intent holdout, `--real-llm`: **refine_applied 0 → 10, refine_skipped 10 → 0, coverage scored on 10/20 → 20/20 rows, avg 95, 20/20 passing**, every refine row scored on real post-refinement markup. Zettel (cov 93 / avg 90 / MRR 1.00) and free-form (cov 100 / avg 85 / F1 62) floors unchanged.
+- **`composeFromPlan` is the single materializer for both tiers (gh#832).** The retrieval path expanded `<!-- nested: … -->` markers (gh#803) and the composer did not, so the same chunk rendered differently depending on which path produced it — and replaying a retrieval-sourced plan through the composer, which is what *every refine turn does*, silently degraded the UI back to skeleton comments. Measured: **48 of 497 block chunks** round-tripped to a skeleton; `chunkHtml()` now resolves nested markers page-scoped, taking exact plan→HTML round-trip from **449/497 to 497/497**. Without this the new plan would be decorative rather than honest. `composeFromPlan` also stops warning "expected page or panel" for a chunk-rooted plan that binds no slots (a legitimate single-chunk composition, not a mis-picked shell), and `validatePlan` gains `{ allowChunkRoot }` — default OFF so the synthesis tier's LLM keeps its "pick a page/panel shell" guardrail, ON for a plan replayed from a prior composition.
+- **Tier-1 retrieval stopped returning empty shells (gh#803).** `composeFromIntent`'s retrieval fast path handed back the chunk's raw HTML; for the 47 block chunks harvested from pages with nested markers that is a skeleton of `<!-- nested: … -->` comments, so a "sign-in form" composed to a card with nothing in it. The hit is now expanded through `resolveNestedChunks()` (page-scoped) and scope-drift is computed against the bound chunk *plus* its nested chunks, so inlining doesn't fire a false drift warning.
+- **Monolithic prompts teach the catalog's real Tab model (gh#757).** All three copies of the pre-catalog "content panels are SIBLINGS of Tabs" doctrine (component guide + example, structure-rules digest incl. its continuation example, generate-pro decomposition hint) now match tab.yaml/the catalog rules: panel content lives INSIDE its Tab, the parent auto-hides inactive panels. The old doctrine yielded all-panels-visible tab UIs and contradicted the rules text injected alongside it (same stale commit gh#754 removed from the validator).
+
+### Maintenance
+- **`strategies/` touched in this release window** (6 file(s), e.g. `monolithic/_shared.js`) — carried by the entries above.
+
+## [0.8.31] — 2026-08-07
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the lockstep version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.31 work shipped in post-0.8.30 fix wave: double-submit boundaries, list-item render gate, segmented allow-empty + adapter kebab-case booleans, MCP multi-session + idle TTL, feedback signal:none, swatch auto-contrast, tabs strip-gap spacing + vertical clearance. See `packages/web-components/CHANGELOG.md#0831--2026-08-07` for details.
+
+## [0.8.30] — 2026-08-07
+
+### Added
+- **`auto` engine — the escalation ladder as an `@adia-ai/agent` workflow (gh#664).** `strategies/cascade.js` declares zettel → free-form → monolithic-instant → monolithic-pro as `defineWorkflow` data (`ENGINE_LADDER`), each non-terminal step's `until` predicate carrying the escalation rule; `runCascade(ctx, { ladder, gate, emit })` runs it and the result's `attempts` is the escalation trace (`escalationsOf()` renders it as `{from, to, trigger}`). Reachable as `generateUI({ engine: 'auto' })`; `auto` joins the reserved engine names.
+- **`strategies/escalation.js` — the one hit-or-climb rule.** `judgeEngineResult()` / `accepts()` / `isNonEmissionStrategy()` / `isStrongEmissionStrategy()` moved down from `@genui/adia-producer/outcome-to-verdict.js` to the layer that authors the strategy labels they read; the producer bridge re-exports them, unchanged in name and behavior.
+
+### Changed
+- **`monolithic-instant`'s escalation to `monolithic-pro` is a two-step workflow** rather than an inline `if` — same one-hop rule, same warn + counter, now spelled the way the full ladder is spelled.
+- **The cascade's gate is declared once as the workflow exit gate (gh#665).** `defineCascade({ gate })` now hands the gate to `defineWorkflow`'s `exitGate` instead of restating it inside every step's `until`. The ladder's floor is unchanged and still not gated (a terminal step has no `until`), so `runCascade`'s behavior is identical for every existing caller; `defineCascade()` output gains an `exitGate` property when a gate was supplied.
+- **Escalation triggers are recorded, not recomputed (gh#665).** Each non-terminal step's `until` returns a verdict carrying `judgeEngineResult`'s feedback code, so `escalationsOf()` reads `attempt.reason` (re-judging survives only as the fallback for boolean predicates). A gate rejection now reads `gate-rejected` because that is what happened — the attempt also carries `gateRejected: true` — rather than as the leftover of a re-judge that found nothing. Attempts additionally carry `round` and optional `detail`/`data`.
+- **The instant→pro counter and warn moved out of the `until` predicate** into the pro step's `run` (PR #669 nit N2). They were correct only while the harness called `until` exactly once per step; in `run` they fire once per actual hop by construction.
+- **`llmAdapter` reaches engines through the harness's services channel**, with the `input.llmAdapter` fallback intact for callers assembling the older flat engine context.
+
+## [0.8.29] — 2026-08-06
+
+### Added
+- **Plan-envelope executor** — `core/plan-turn.js`: `runPlannedTurn()` strings multiple single-surface engine calls under one inspectable surface manifest, enforcing manifest order via the vendored `checkExecutionAgainstPlan` shared predicate and throwing a diagnostics-bearing `PlanViolationError` on off-manifest/out-of-order execution; `synthesizeTurn` derives the turn's new/updated/closed summary. Scoped to zettel/chunk-zettel per ORCHESTRATION ruling 2; monolithic-instant exempt by design (gh#648, PR #654; standard: genui-system#15, R-O10–R-O13).
+
+## [0.8.28] — 2026-08-05
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the lockstep version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.28 work shipped in sideEffects tree-shaking fix + CSS barrel regen (gh#625/632). See `0828--2026-08-05` for details.
+
+## [0.8.27] — 2026-08-05
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the lockstep version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.27 work shipped in menu subtitle + roster migration, agent model pins, proper deflake, release tooling (gh#614/616/617/618). See `packages/web-modules/CHANGELOG.md#0827--2026-08-05` for details.
+
+## [0.8.26] — 2026-08-05
+
+### Fixed
+- **The streaming path's hand-rolled one-shot repair skipped the catalog check** (`generator.js`) — now routes through the shared `validate-and-repair` loop with anti-pattern folding and catalog validation, same as the pro/thinking paths (GK-3, gh#583).
+
+### Maintenance
+- **`core/` touched in this release window** (1 file(s), e.g. `core/generator.js`) — carried by the entries above.
+
+## [0.8.25] — 2026-07-31
+
+### 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.25 work shipped in theme-panel scoped-target [parametric] density/radius fix (gh#570) + System scheme option; anchor-bar-ui; stat-ui band chart layout; chart-ui dots/series-emphasis. See `packages/web-components/CHANGELOG.md#0825--2026-07-31` for details.
+
+## [0.8.24] — 2026-07-30
+
+### 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.24 work shipped in requiredIcons drift cleared across 16 components + checker comment handling (gh#550), worktree bootstrap workspace-link hardening + retrieval corpus-pin fix (gh#554), list-item two-line icon centering (gh#558), card footer bottom-pinning (gh#559). See `packages/web-components/CHANGELOG.md#0824--2026-07-30` for details.
+
+## [0.8.23] — 2026-07-30
+
+### 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.23 work shipped in operator-report day: 20+ fixes, BREAKING --a-font removal, deployed-site freeze fix, plugin rename to adia-ui-kit-*. See `packages/web-components/CHANGELOG.md#0823--2026-07-30` for details.
+
+## [0.8.22] — 2026-07-29
+
+### 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.22 work shipped in select-ui aria-selected action-row fix, combobox radio indicator, form-popover summary hardening, resumable release Step 10. See `packages/web-components/CHANGELOG.md#0822--2026-07-29` for details.
+
+## [0.8.21] — 2026-07-28
+
+### 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.21 work shipped in card/table/select/form-popover fixes from adia-v2 adoption + three drift gates (gh#473, gh#425, gh#435). See `packages/web-components/CHANGELOG.md#0821--2026-07-28` for details.
+
+## [0.8.20] — 2026-07-28
+
+### Fixed
+- **The npm tarball no longer ships `*.test.js`** (gh#462) — the `files` roster excluded examples/html but never unit tests, so 6 test file(s) rode the 0.8.19 tarball. `!**/*.test.js` appended as the roster's LAST entry (npm's files globbing is order-sensitive — a leading exclude is overridden by later directory includes). Proof: `npm pack --dry-run` → 0 test files, runtime files intact.
+
+## [0.8.19] — 2026-07-27
+
+### 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.19 work shipped in form/ cluster publishes (form-popover-ui installable, gh#448) + select-ui summary-label (gh#442) + row-hover container-ladder token fix. See `packages/web-modules/CHANGELOG.md#0819--2026-07-27` for details.
+
+## [0.8.18] — 2026-07-27
+
+### 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.18 work shipped in form-popover-ui rename + 9-test surface + first passing rendered-dom probe (harness repaired for all composites). See `packages/web-modules/CHANGELOG.md#0818--2026-07-27` for details.
+
+## [0.8.17] — 2026-07-27
+
+### 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.17 work shipped in one selection language (radios + tonal + container tier) · form-popover module · check:demo-routes sweep. See `packages/web-components/CHANGELOG.md#0817--2026-07-27` for details.
+
+## [0.8.16] — 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.16 work shipped in text-on-fill AA (90/90 pairs) + release-gate roster 18→22 + the theming guide. See `packages/web-components/CHANGELOG.md#0816--2026-07-26` for details.
+
+## [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.
+
+## [0.8.14] — 2026-07-25
+
+### 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.14 work shipped in overlay surface plane + nav-item selected fill + theme neutral hues + examples.md drift gate. See `packages/web-components/CHANGELOG.md#0814--2026-07-25` for details.
+
+## [0.8.13] — 2026-07-25
+
+### 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.13 work shipped in 12 named theme identities + select-menu Theme row in theme-panel; fixes scale.css wiring, Preset/Reset UX, and a Theme-select XSS finding. See `packages/web-modules/CHANGELOG.md#0813--2026-07-25` for details.
+
+## [0.8.12] — 2026-07-24
+
+### 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.12 work shipped in tag-ui size parity (badge-ui sm/md/lg); plugin skills learn v0.8.11 size model; primitive count fix. See `packages/web-components/CHANGELOG.md#0812--2026-07-24` for details.
+
+## [0.8.11] — 2026-07-23
+
+### 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.11 work shipped in sm/md/lg size model + ancestor [scale] context; adia-wordmark-ui; forge release-cycle hardening. See `packages/web-components/CHANGELOG.md#0811--2026-07-23` for details.
+
+## [0.8.10] — 2026-07-20
+
+### 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.10 work shipped in tag-ui accent variant, dialog-scrim/card-ui fixes; adia-charts/adia-tables skills. See `packages/web-components/CHANGELOG.md#0810--2026-07-20` for details.
+
+## [0.8.9] — 2026-07-19
+
+### 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.9 work shipped in select-ui mark visual (gh#339); release-tooling hardened (branch creation, settle-wait poll, pr-bridge draft guard). See `packages/web-components/CHANGELOG.md#unreleased` for details.
+
+## [0.8.8] — 2026-07-19
+
+### 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.8 work shipped in Type scale tightened one step (body 14px / ui 13px base); release machinery hardened (pr-bridge, mechanized pins, single-sourced roster). See `packages/web-components/CHANGELOG.md#088--2026-07-19` for details.
+
+## [0.8.7] — 2026-07-19
+
+### 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.7 work shipped in factory enrichment (adia-patterns/adia-audit + harvests), forge dogfood/gate fixes, a2ui-corpus content-hash freshness, bundle rebuilds. See `packages/plugins/adia-ui-factory/CHANGELOG.md#087--2026-07-19` for details.
+
+## [0.8.6] — 2026-07-18
+
+### 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.6 work shipped in SSR attribute-replay fix + table declarative data + token repoints (@adia-ai/web-components), gh#268 forge modernization campaign (adia-forge). See `packages/web-components/CHANGELOG.md#086--2026-07-18` for details.
+
+## [0.8.5] — 2026-07-17
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.5 work shipped in gemini production passthrough + hardening (@adia-ai/llm), SSR browser-API guards + gh issue 276 wave-4 button-ui/option-card-ui migrations (@adia-ai/web-components), admin-sidebar SSR collapse fix (@adia-ai/web-modules), kbd-ui A2UI-render fix (@adia-ai/a2ui-runtime), full chunk/embeddings regen (@adia-ai/a2ui-corpus). See `packages/llm/CHANGELOG.md#085--2026-07-17` for details.
+
+## [0.8.4] — 2026-07-16
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.4 work shipped in gen-UI provider routing by model id + gemini fixes (@adia-ai/llm), focus-ring/caret rulings + the button-ui purge (@adia-ai/web-components), chat-shell html messages (@adia-ai/web-modules). See `packages/llm/CHANGELOG.md#084--2026-07-16` for details.
+
+## [0.8.3] — 2026-07-16
+
+### 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.3 work shipped in the two Claude Code plugins — the adia-tokens knowledge pack + command refresh (adia-ui-factory) and the release-tooling invariant-3 reconciliation (adia-ui-forge); see `packages/plugins/adia-ui-factory/CHANGELOG.md#083--2026-07-16`.
+## [0.8.2] — 2026-07-16
+
+### 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.2 work — the `button-ui` ellipsis fix + tarball-shipped MIGRATION.md (@adia-ai/web-components) and the factory-plugin modernization campaign (adia-ui-factory; gh#259) — see `packages/web-components/CHANGELOG.md#082--2026-07-16`.
+## [0.8.1] — 2026-07-15
+
+### 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.1 work — the `tags-input-ui` chip slot template (TKT-0023) + the `--a-link` AA contrast fix — shipped in @adia-ai/web-components; see `packages/web-components/CHANGELOG.md#081--2026-07-15`.
+## [0.8.0] — 2026-07-15
+
+### Changed
+- **`strategies/monolithic/_shared.js` — token-name sweep** onto `--md-sys-color-*` (Material color-token adoption, lockstep with @adia-ai/web-components@0.8.0 — see that CHANGELOG + `.claude/docs/MIGRATION GUIDE.md` § v0.8.0).
+## [0.7.28] — 2026-07-14
+
+A2UI pipeline overhaul (comparing gen-ui-kit's system against a sibling
+project's from-scratch A2UI implementation surfaced a concrete gap: only
+one of six generation strategies ran a genuine closed-loop validate→retry
+before returning; the rest either skipped it, did a single repair shot,
+or validated a narrower plan/grounding contract).
+
+### Added
+
+- **`packages/a2ui/compose/shared/validate-and-repair.js`** — a shared
+  closed-loop validate→repair helper, extracted from `generate-thinking`'s
+  original inline loop (schema + Ajv catalog + anti-pattern conformance,
+  bounded LLM-fed repair attempts). Every LLM-calling engine can now share
+  one implementation instead of hand-rolling its own; escalation policy
+  (retry vs. give up vs. escalate to a bigger tier) stays entirely with
+  the caller — the module only reports `{valid, exhausted, attempts,
+  failures}`.
+
+### Fixed
+
+- **`generate-pro` — replaces its single hardcoded repair shot with the
+  shared closed loop** (`maxAttempts: 2`, reflecting pro's cheaper cost
+  tier vs. thinking's 3) and adds Ajv catalog-schema coverage it never had
+  before.
+- **`free-form-composer` — now runs a real schema/catalog/anti-pattern
+  check (validate-only) on its transpiled output**, which it previously
+  never did at all (a hardcoded `score: 85` regardless of actual
+  validity). This surfaced a real, previously-invisible defect: the
+  synthesized root component used `id: 'free-form-root'` instead of the
+  `'root'` convention every other engine's root uses, which
+  `validator.js`'s `checkHasRootComponent` hard-fails on — fixed at the
+  source (`transpile.js`). `score` stays 85 on the success path
+  (unchanged), so the tuned `eval:diff` floors don't shift as a side
+  effect of adding a measurement; new `schemaValid`/`schemaValidation`
+  fields are additive.
+- **`monolithic-instant` no longer silently returns a hard-fail's broken
+  output.** The dispatcher (`strategies/registry.js`'s
+  `generateInstantAdapter`) now escalates a hard-fail to `generate-pro`
+  exactly once, only when an `llmAdapter` is available — capped at one
+  hop by construction (a pro-mode failure returns straight to the
+  original caller, never chains to thinking). A counter +
+  `console.warn` ship from day one, since this silently converts a
+  0-cost request into a billed LLM call.
+- **`chunk-zettel` now emits a real component graph and qualifies for
+  the shared closed loop (TKT-0009).** `composeFromIntent`
+  (`chunk-synthesizer.js`) previously returned only a raw HTML string,
+  which both callers wrapped into a single node with an unregistered
+  `component: 'article'` type — full schema validation could only ever
+  report `invalid`. Ratified direction: reuse `transpileHTML()` (the
+  same converter `harvest-chunks.mjs` already runs at corpus-admission
+  time) to produce a real `template` component array on every path (a
+  chunk's own precomputed template when available, else transpiled on
+  demand). Both callers (`registry.js`'s `generateChunkZettelAdapter`,
+  `generator-adapter.js`'s `bridgeToChunkSynthesis`) now prefer
+  `result.template` and route the final messages through
+  `validate-and-repair.js` (validate-only). Verified live: Tier-1
+  retrieval and Tier-2 synthesis intents both produce `valid:true`
+  component graphs (score 90/92); zero regression confirmed via a
+  stash-based before/after comparison of `eval:compose-from-chunks`
+  (the eval calls `composeFromIntent` directly and never touches the
+  caller code this change modified).
+- **`transpiler/transpiler-maps.js` — dynamic array props (`Chart.data`,
+  `Table.data`) are now actually parsed, not copied through as raw
+  strings (TKT-0010).** Compiled dynamic props are a bare `$ref`
+  (`DynamicString`/`DynamicObjectList`/etc.) with no inline `type`, so
+  `CATALOG_PROPS`'s `pdef.type || 'string'` silently defaulted every
+  dynamic array prop to string extraction — a declarative
+  `data='[{...}]'` attribute's JSON text was copied through unparsed,
+  never `JSON.parse`d, so it could never satisfy the catalog's
+  array-shaped schema. Fixed by resolving `$ref` names to their
+  primitive kind (new `REF_TYPE_MAP`) and adding a `JSON.parse`-ing
+  array extraction branch (skipping silently on parse failure or a
+  non-array result, matching `chart.yaml`'s own documented "non-array
+  renders empty" contract). Root-caused via the corpus admission
+  validator surfacing the same `Chart`/`Table`.`data` `oneOf` failure
+  across 8+ unrelated chunks — a schema-generation/transpiler bug, not
+  independent content authoring mistakes. See `@adia-ai/a2ui-corpus`'s
+  CHANGELOG for the companion schema-side fix (`DynamicObjectList`).
+
+## [0.7.27] — 2026-07-12
+
+### Fixed
+- **Transpiler — `[span]` is now universally preserved (TKT-0002).** `extractProps()` had a universal preserve for `[slot]` but not `[span]` — the same class of cross-cutting, layout-bearing attribute, consumed purely via `grid.css`'s `& > [span="N"]` child selectors and never declared in any component's own yaml `props:`. Every transpiled asymmetric grid collapsed to equal columns (the admin-dashboard's 3:2 Overview/Recent-Sales split was the operator-reported case). Regression tests cover `span="3"`, `span="full"`, and the absent case.
+- **Transpiler — `Tag` is a leaf type; labels ride the `text` prop (TKT-0004 A).** `Tag` was missing from `LEAF_TYPES`, so `<tag-ui size="sm">label</tag-ui>` transpiled to `Tag > Text variant=body` — a full body-size paragraph inside the pill, inflating every converted chip (581 instances across 233 docs pages measured). Labels now ride tag.yaml's documented `attr(text)` contract, in both the pure-text and element-children extraction paths.
+- **`strategies/zettel/issue-reporter.js` — issue storage repointed to `qa/findings/issues/`.** The previous path would have silently recreated the retired `.brain/` tree at runtime on the first `report_issue` call.
+
+### Maintenance
+- Transpiler test suite: `extract-props.test.js` 19 → 24 cases (span preservation ×3, Tag text contract ×2).
+
+## [0.7.26] — 2026-07-04
+
+### Fixed
+- **Monolithic engine no longer teaches `variant="outline"` as the encoding for "secondary button."** `strategies/monolithic/_shared.js`'s hardcoded system-prompt text — sent to the LLM on every generation call — read `variant="primary" for main action, "outline" for secondary, "ghost" for tertiary`, actively instructing every generation to reach for `outline` on any non-primary button. `button-ui`'s unstyled default already renders the neutral/secondary look (see `@adia-ai/web-components` changelog); corrected the prompt text to say so explicitly and to leave `variant` unset for secondary/default actions, reserving `variant="primary"` for the one CTA that should stand out and `variant="ghost"` for genuinely lower-emphasis tertiary actions. Also fixed the same anti-pattern hardcoded into the file's fallback-error-UI generator — a "Copy Debug Info" button built with `variant: 'outline'` right next to a `variant: 'primary'` "Try Again" — dropped the attribute there too.
+- Corpus evidence that motivated the investigation: of 446 `<button-ui>` tags across harvested demo-page chunks, only 30 were bare vs. 91 explicit `variant="outline"` + 215 `variant="ghost"` — confirming the prompt text (not incidental author habit) was the dominant driver.
+
+## [0.7.25] — 2026-07-03
+
+### Maintenance
+- **Lockstep version bump.** No functional source changes; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.25 work shipped in accordion-ui variant="flat|contained" posture + 2 footnote fixes + keyboard a11y. See `packages/web-components/CHANGELOG.md#0725--2026-07-03` for details.
+- **Doc-comment path references corrected** (`docs/specs/...` → `.claude/docs/specs/...`) across `strategies/` (`registry.js` + 5 `zettel/` files) — propagated from the repo-wide `docs/` → `.claude/docs/` migration (2026-07-01); no functional change.
+
+## [0.7.24] — 2026-07-01
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.24 work shipped in @adia-ai/web-components upstream consumer findings F1/F2/F4/F5/F6 — icon-ui fail-loud registry wiring, @phosphor-icons/core direct dep, custom-elements.json de-fabrication, new display-field-ui primitive, table-ui rowExpandable per-row gate. See `packages/web-components/CHANGELOG.md#0724--2026-07-01` for details.
+
+## [0.7.23] — 2026-06-30
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.23 work shipped in @adia-ai/web-components button-ui child-text label parity + accordion-ui block-flow gap. See `packages/web-components/CHANGELOG.md#0723--2026-06-30` for details.
+
+## [0.7.22] — 2026-06-16
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.22 work shipped in the @adia-ai/web-components + @adia-ai/web-modules surface-token alignment (symmetric canvas ramp). See `packages/web-components/CHANGELOG.md#0722--2026-06-16` for details.
+
+## [0.7.21] — 2026-06-10
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.21 work shipped in corpus harvester scope expansion (gated web-components examples root) + 26 curated chunks (368->394). See `packages/a2ui/corpus/CHANGELOG.md#0721--2026-06-10` for details.
+
+## [0.7.20] — 2026-06-10
+
+### Fixed
+- **Corpus retrieval works on STATICALLY-served sites (no vite).** The browser corpus loaders (`strategies/zettel/composition-library.js`, `strategies/_shared/chunk-loader.js`) used `import.meta.glob` — a vite-only mechanism — so the corpus-first path silently loaded 0 chunks on the deployed static site and every intent fell through to the LLM. New **third runtime branch** (Node / vite-glob / **static-fetch**): one `_index.json` request carries the full scoring metadata; matched chunk bodies hydrate lazily. Detection = attempting the glob *call* in try/catch (`typeof import.meta.glob` is undefined in BOTH vite-dev and raw ESM — only the rewritten call discriminates). A parity guard in `generator-adapter` keeps static results identical to Node (template-less partials fall through instead of emitting empty surfaces). Verified: a plain static server with **no LLM** retrieves `contact-form-card` verbatim (4 labeled fields, 92/100, ~8 ms).
+
+### Added
+- **Anti-pattern fold-in for generated output** — `foldInAntiPatterns(messages, validation)` projects the flat component messages into an HTML sketch (via the runtime tag registry), runs the anti-pattern registry over it, and folds violations into the validation result (one warning each + a 10-point score dock). Wired into all monolithic generate paths (instant / thinking / pro — 5 call sites), so the canvas's validation badge now reflects anti-patterns: the incident's junk contact form scores 65 with 3 named violations instead of badging clean. Fails open — the fold-in can never break generation.
+
+## [0.7.19] — 2026-06-10
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.19 work shipped in icon-ui standalone-import paint fix + late-connect retry (web-components); full 308-chunk embedding vectors (a2ui-corpus). See `packages/web-components/CHANGELOG.md#0719--2026-06-10` for details.
+
+## [0.7.18] — 2026-06-09
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.18 work shipped in combobox menu-overflow fix + max-visible-items + the dropdown-family caret OPEN state + the theme-provider CDN bundle (web-components); corpus regrowth batch 1, +24 chunks (a2ui-corpus). See `packages/web-components/CHANGELOG.md#0718--2026-06-09` for details.
+
+## [0.7.17] — 2026-06-08
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.17 work shipped in badge-ui/tag-ui icon-spacing fix — icon-bearing chips no longer inflate row height + tighter [icon]-gated spacing. See `packages/web-components/CHANGELOG.md#0717--2026-06-08` for details.
+
+## [0.7.16] — 2026-06-08
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.16 work shipped in the dist CSS + JS bundle refresh. See `packages/web-components/CHANGELOG.md (0.7.16)` for details.
+
+## [0.7.15] — 2026-06-08
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.15 work shipped in the menu-label-ui new component + badge/tag padding. See `packages/web-components/CHANGELOG.md (0.7.15)` for details.
+
+## [0.7.14] — 2026-06-08
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.14 work shipped in input-ui/textarea-ui .value upgrade-safety fix. See `packages/web-components/CHANGELOG.md (0.7.14)` for details.
+
+## [0.7.13] — 2026-06-06
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.13 work: the `./css/sheet` exports `types` fix (`@adia-ai/web-components` + `@adia-ai/web-modules`) + a corpus re-harvest (`@adia-ai/a2ui-corpus`). See `packages/web-components/CHANGELOG.md` for details.
+
+## [0.7.12] — 2026-06-04
+
+### Changed
+- **`data-theme` → `theme` in the monolithic compose strategy's LLM prompt** (`strategies/monolithic/_shared.js`) — the repo-wide token-attribute rename (see `@adia-ai/web-components`) reached the compose guidance, so generated UIs emit `theme="…"` not `data-theme="…"`. Otherwise a lockstep version bump (9-package coherence per `scripts/release/check-lockstep.mjs`).
+
+## [0.7.11] — 2026-06-04
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.11 work: the `<frame-ui>` slot-override regions + `button-ui` hover `-strong` step + `resizable` trait corner handles + `list-item-ui` / `<preview-ui>` fixes (`@adia-ai/web-components`), `<embed-shell>` extending `UIElement` to compose the `resizable` trait (`@adia-ai/web-modules`), and a corpus re-harvest. See `packages/web-components/CHANGELOG.md` for details.
+
+## [0.7.10] — 2026-06-03
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.10 work: the `<frame-ui>` layout primitive + `list-item-ui` grid fix + `[verse]` type-tier bump (`@adia-ai/web-components`), the new `<embed-shell>` (`@adia-ai/web-modules`), and a corpus re-harvest. See `packages/web-components/CHANGELOG.md` for details.
+
+## [0.7.9] — 2026-06-03
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.9 work shipped in Lockstep release — no package-specific source changes this cut; substantive v0.7.9 work in `@adia-ai/web-components` (verse control/chrome tier bump + semantic color cusp-lift) + root tooling (PLAN-claim trip-wire, slot-vocab + foundation-layer gate fixes).. See `packages/web-components/CHANGELOG.md#079--2026-06-03` for details.
+
+## [0.7.8] — 2026-06-02
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.8 work shipped in Lockstep release — no package-specific source changes this cut; substantive v0.7.8 work in `@adia-ai/web-components` (wrapper-trap arm-2 drain: 14 consumer-slot reads pierced via the new `core/logical-children.js` helper).. See `packages/web-components/CHANGELOG.md#078--2026-06-02` for details.
+
+## [0.7.7] — 2026-06-02
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.7 work shipped in Lockstep release — no package-specific source changes this cut; substantive v0.7.7 work in `@adia-ai/web-components` (drawer/verse register-aware insets + agent-artifact wrapper-pierce).. See `packages/web-components/CHANGELOG.md#077--2026-06-02` for details.
+
+## [0.7.6] — 2026-06-02
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.6 work shipped in Lockstep release — no package-specific source changes this cut; substantive v0.7.6 work in `@adia-ai/web-components` (block-ui, parametric [padding]/[margin] scale, host.css barrel split, FB-97/98 + command wrapper-trap fixes).. See `packages/web-components/CHANGELOG.md#076--2026-06-02` for details.
+
+## [0.7.5] — 2026-06-02
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.5 work shipped in Lockstep release — no package-specific source changes this cut; the substantive v0.7.5 fix is in `@adia-ai/web-components` (button-ui colored-variant: readable solid text + outline composes + excluded from the `[color]` text utility).. See `packages/web-components/CHANGELOG.md#075--2026-06-02` for details.
+
+## [0.7.4] — 2026-06-02
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.4 work shipped in Lockstep release — no package-specific source changes this cut; substantive work in `@adia-ai/web-components` + `@adia-ai/web-modules` (verse register, OD-5 `-default` revert, grid align/justify, font-family floor).. See `packages/web-components/CHANGELOG.md#074--2026-06-02` for details.
+
+## [0.7.3] — 2026-06-01
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.3 work shipped in @adia-ai/web-components parametric named gap scale (xs–xl) + explicit/ambient [gap] split (no leak) + FB-96 tree slot-adopt. See `packages/web-components/CHANGELOG.md#073--2026-06-01` for details.
+
+## [0.7.2] — 2026-06-01
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.2 work shipped in @adia-ai/web-components template-engine ARIA-transparent wrapper spans (FB-94) + menu-item orphan fix (FB-95) + tokens cascade-layer; @adia-ai/web-modules admin-page-footer sticky band (bug-54). See `packages/web-components/CHANGELOG.md#072--2026-06-01` for details.
+
+## [0.7.1] — 2026-05-31
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.1 work shipped in @adia-ai/web-components a11y/reactivity fixes — input-ui affordance centering (bug-60), tree-ui role=group WAI-ARIA (FB-91), menu-ui dynamic items (FB-92), input-ui reactive prefix/suffix (FB-93). See `packages/web-components/CHANGELOG.md#071--2026-05-31` for details.
+
+## [0.7.0] — 2026-05-31
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.7.0 work shipped in MINOR: @adia-ai/web-components BREAKING removals (avatar-ui [name] alias, chart-ui [aspect]/[heading]) + docs-QA pass (bug-21, bug-50..55) + new features (stat [bleed], page regions, kbd lg); @adia-ai/web-modules dialog/plan-picker/onboarding/integrations fixes. See `packages/web-components/CHANGELOG.md#070--2026-05-31` for details.
+
+## [0.6.50] — 2026-05-30
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.50 work shipped in @adia-ai/web-components slot="caret" disclosure convention + tree-item-ui adopt-or-stamp (FEEDBACK-89, ADR-0036); @adia-ai/a2ui-corpus catalog regen for the renamed slot vocabulary. See `packages/web-components/CHANGELOG.md#0650--2026-05-30` for details.
+
+## [0.6.49] — 2026-05-30
+
+### Maintenance
+
+- **Lockstep version bump only.** Substantive v0.6.49 in `@adia-ai/web-components` (date-range-picker two-month fix + calendar `month` prop + card-ui demo slot sweep) and `@adia-ai/a2ui-corpus` (corpus + catalog regen). See those packages CHANGELOGs.
+
+## [0.6.48] — 2026-05-29
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.48 work shipped in foundation-styles dimension×layer reorg (ADR-0035) + library-wide demo consolidation + date-range-picker popover fix + corpus re-harvest. See `packages/web-components/CHANGELOG.md#0648--2026-05-29` for details.
+
+## [0.6.47] — 2026-05-29
+
+### Maintenance
+
+- **Lockstep version bump only.** Substantive v0.6.47 in `@adia-ai/web-components` (`<card-ui>` `[grow]` section attribute) and `@adia-ai/a2ui-corpus` (chunk re-harvest). See those packages CHANGELOGs.
+
+## [0.6.46] — 2026-05-29
+
+### Maintenance
+
+- **Lockstep version bump only.** Substantive v0.6.46 in `@adia-ai/web-components` (56 trait pages + slot docs + bleed/token fixes) and `@adia-ai/a2ui-corpus` (chunk re-harvest). See those packages CHANGELOGs.
+
+## [0.6.45] — 2026-05-29
+
+### Maintenance
+
+- **Lockstep version bump only.** Substantive v0.6.45 in `@adia-ai/web-components` (FB-85 canvas-ui bare-specifier + FB-88 select-ui accessible name). See its CHANGELOG.
+
+## [0.6.44] — 2026-05-28
+
+### Fixed — transpiler emits `<select-ui>` options as a prop, not Text children (FEEDBACK-79)
+
+- **`transpiler/transpiler-maps.js` + `transpiler/transpiler.js`** — `<select-ui>` / `<select>` (A2UI `ChoicePicker`) had no `<option>` handling: each `<option>` fell through the generic text-leaf path and became a `Text` child of the picker. Since `ChoicePicker` → `select-ui`, the renderer appended those as `<p>` / `<text-ui>` children, which `select-ui` rejects (`ignoring unrecognized child element` warning + empty options). `extractProps()` now builds the `options` model — `[{value, label, disabled?}]`, grouped `{label, options:[…]}` for `<optgroup>` — and mirrors `<option selected>` into `value` (comma-joined for `[multiple]`); `walkNode()` treats `ChoicePicker` as self-contained so options are never re-emitted as children. Matches `select.yaml`'s `options` contract. Affects every `<select-ui>`-bearing chunk, not just the 3 in the ticket. Re-harvest required (see `@adia-ai/a2ui-corpus`).
+
+## [0.6.43] — 2026-05-27
+
+### Fixed — Cycle-18 transpiler substrate sweeps (RL + RL2)
+
+- **`transpiler/transpiler.js`** — two substrate sweeps from gen-review cycle-18:
+  - **Ralph Loop**: 6 visual bugs fixed at SoT — header slot grammar, leaf children, button slot preservation.
+  - **RL2**: 10 visual bugs across header slot, leaf children, calendar widget.
+- **`transpiler/transpiler-maps.js`** — preserve `slot=` annotations through transpilation so card-ui transpiled `text-ui` chunks match the substrate CSS selector.
+
+## [0.6.42] — 2026-05-26
+
+### Maintenance
+
+- **Lockstep version bump only.** Substantive v0.6.42: `@adia-ai/a2ui-corpus` (gen-review cycles 8-17 — chunk count 240 → 284, +44 new training chunks + chunk-embeddings regen 6.92 → 8.19 MB), `@adia-ai/web-components` (yaml/sidecar polish for description-list/table/upload + core/provider.js), `@adia-ai/web-modules` (admin-page-header yaml header-anatomy fix), `@adia-ai/a2ui-runtime` (registry.js + renderer.js polish). See those packages' CHANGELOGs.
+
+## [0.6.41] — 2026-05-26
+
+### Maintenance
+
+- **Lockstep version bump only — pure ride-along.** No source changes in any of the 9 packages this cycle. Substantive v0.6.41 work is REPO-LEVEL: adia-ui-release skill v1.8.0 → v1.9.0 (catalog-drift recurring graduation — §Step 5.5 pre-commit trip-wire + supersedes-WT contract + §Step 5 allowlist convention; closes FEEDBACK-75). Version bump preserves 9-package lockstep coherence; published tarballs identical to v0.6.40 modulo version metadata.
+
+## [0.6.40] — 2026-05-26
+
+### Maintenance
+
+- **Lockstep version bump only.** Substantive v0.6.40 in `@adia-ai/web-components` (index.js barrel side-effect-imports `core/provider.js` — cold-start `<router-ui>` registration, FB-69-class fix) and `@adia-ai/web-modules` (`<admin-entity-item>` `<span slot="icon">` wrap — mirrors `<nav-item-ui>`).
+
+## [0.6.39] — 2026-05-26
+
+### Maintenance
+
+- **Lockstep version bump only.** Substantive v0.6.39 in `@adia-ai/web-components` (<tour-ui> primitive — Wave 5e last P1, #259 + substrate slot-selector defensive sweep + admin-entity-item icon-size parity + list-item-ui slot=action declaration). `@adia-ai/web-modules` ships dist rebuild only.
+
+## [0.6.38] — 2026-05-26
+
+### Maintenance
+
+- **Lockstep version bump only.** No source changes in this package. Substantive v0.6.38: `@adia-ai/web-components` (Wave 5e — mark-ui + inline-edit-ui + feed-ui deep-link demo + list-item-ui/segmented-ui/stat-ui/toolbar-ui fixes + slot-vocab-vs-css backlog closure), `@adia-ai/web-modules` (catalog/ui-patterns import-mapping + saas/billing cancellation save-offer + onboarding-checklist demo), `@adia-ai/a2ui-corpus` (240 chunks + catalog regen for Wave 5e cohort).
+
+## [0.6.37] — 2026-05-25
+
+### Maintenance
+
+- **Lockstep version bump only.** No source changes in this package. Substantive v0.6.37: `@adia-ai/web-components` (Wave 1+2+3+4 cohort — blockquote, slider dual-thumb, password-strength, qr-code, toc, relative-time, number-format, anchor-link, number-stepper, pagination, toast-undo, blockquote, table demos column-resize/sticky-header/virtualized, alert-dialog destructive-confirm, context-menu, visually-hidden, skip-nav + FB-67/68/69/70/71 close + popover-ui/pagination/slider/qr-code fixes + --a-warning-bg redirect + 5 new audits) and `@adia-ai/web-modules` (Wave 3+4 pattern demos + brand-chrome canonicals + integration-card/segmented console-warn silence).
+
+## [0.6.36] — 2026-05-24
+
+### Maintenance
+
+- **Lockstep version bump only.** No source changes in this package. Substantive v0.6.36: `@adia-ai/web-components` (tag-ui solid-default flip + [tone] prop + dismiss X variant inheritance + tag.warning amber fix + caret-at-content-start fix for input/textarea/combobox/tags-input + post-v0.6.35 QA sweep), `@adia-ai/web-modules` (Wave A+B+C+D demos via authoring v1.8.0 Mode 8 + payment-method-form recursion guard + payment-method-list card-ui rewrite + billing-overview/dashboard-layout fixes), `@adia-ai/a2ui-corpus` (catalog regen for tag-ui solid-default flip).
+
+## [0.6.35] — 2026-05-24
+
+### Maintenance
+
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain 9-package coherence. Substantive v0.6.35: `@adia-ai/web-components` (Waves A+B+C — 14 P1 component implementations + FB-57/61/62/63 substrate sweep + class.js → <slug>.class.js refactor + spinner/calendar-grid fixes), `@adia-ai/web-modules` (FB-55 admin-shell warn + delegation refactor + Wave A+B+C cluster work), `@adia-ai/llm` (server.js SIGINT/SIGTERM handlers — dev-only fix), `@adia-ai/a2ui-corpus` (catalog regen absorbing FB-61/62/63 yaml backfills).
+
+## [0.6.34] — 2026-05-23
+
+### Maintenance
+
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain 9-package coherence. Substantive v0.6.34: `@adia-ai/web-components` (Wave 1 + Wave 2 — 10 P1 components shipped from SPECs + OD-5 `-default` token sweep across 98 components + `<calendar-grid-ui>` substrate primitive), `@adia-ai/web-modules` (Wave 1/2 cluster registrations + `everything.min.js` rebuild), `@adia-ai/a2ui-runtime` (Phase 1 CSS channel: `updateStyles`/`removeStyles`), `@adia-ai/a2ui-corpus` (`playground-css-channel` chunk + embeddings regen). See those packages' CHANGELOGs.
+
+## [0.6.33] — 2026-05-23
+
+### Maintenance
+
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.33 work shipped in `@adia-ai/web-components` (FB-53 §2 table[raw] short-circuit + FB-54 field row-gap :has gate + tabs --tabs-button-height anchor + dist icons-manifest header refresh) and `@adia-ai/web-modules` (FB-53 §1 CDN icons-manifest co-emit to web-modules/dist/) and `@adia-ai/a2ui-runtime` (card-ui body-slot drift fix). See those packages' CHANGELOGs for details.
+
+## [0.6.31] — 2026-05-23
+
+### Maintenance
+
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.31 work shipped in `@adia-ai/web-modules` (`admin-shell.examples` taming CSS + README canonical-hierarchy example) and `@adia-ai/web-components` (3 legacy `patterns/*` hubs rewritten). Docs-and-skills scrub — see those packages' CHANGELOGs for details.
+
+## [0.6.30] — 2026-05-23
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.30 work shipped in CDN-ready JS bundles (web-components.min.js primitives + 4 per-shell + everything.min.js kitchen-sink for CodePen); new ./js/bundled + ./everything + 4 */js-bundled exports; check:js-bundles-fresh pre-flight gate; README + site CDN docs + AI-agent discoverability; examples/codepen.html template. See `packages/web-components/CHANGELOG.md#0630--2026-05-23` for details.
+
+## [0.6.29] — 2026-05-23
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.29 work shipped in CDN-ready rolled-up CSS bundles (web-components + 4 web-modules shells); ./css/bundled + per-shell /bundled exports; check:css-bundles-fresh pre-flight gate. See `packages/web-components/CHANGELOG.md#0629--2026-05-23` for details.
+
+## [0.6.28] — 2026-05-23
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.28 work shipped in editor-sidebar rAF debounce for wide->narrow display-flip transient (FB-50, 3rd iteration of the latch saga; belt-and-braces with v0.6.26 width guard + v0.6.27 computedStyle guard). See `packages/web-modules/CHANGELOG.md#0628--2026-05-23` for details.
+
+## [0.6.27] — 2026-05-22
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.27 work shipped in chart-ui[loading] skeleton placeholder (FB-12); admin-shell CSS pitfall fix (FB-04); responsive horizontal-scroll for kanban + pricing tables; editor-sidebar computedStyle guard for small-nonzero transients (FB-49); a2ui-corpus catalog tracks chart-ui[loading]. See `packages/web-components/CHANGELOG.md#0627--2026-05-22` for details.
+
+## [0.6.26] — 2026-05-22
+
+### Maintenance
+- **Lockstep version bump only.** No source changes. Substantive v0.6.26 work in `@adia-ai/web-modules`.
+
+## [0.6.25] — 2026-05-22
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.25 work shipped in select-ui[multiple] pre-init via <option selected> + .value= setter (FB-46); table-ui Enter key activates focused body cell (FB-47); corpus select-multiple-preselected exemplar chunk + harvest refresh. See `packages/web-components/CHANGELOG.md#0625--2026-05-22` for details.
+
+## [0.6.24] — 2026-05-22
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain 9-package version coherence. Substantive v0.6.24 work: `slider-ui` label/suffix reactive binding fix (FB-45), `editor-shell` `--a-font-mono` token rename (FB-43), `toast-ui` demo shell `feed.css` import. See `packages/web-components/CHANGELOG.md#0624` for details.
+
+## [0.6.23] — 2026-05-22
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.23 work shipped in row-ui wrap-at='bp' responsive flex-wrap (@adia-ai/web-components) + 4 new v053-coverage-fill training chunks for empty-state danger/warning/minimal + responsive-kpi-grid (@adia-ai/a2ui-corpus). See `packages/web-components/CHANGELOG.md#0623--2026-05-22` for details.
+
+## [0.6.22] — 2026-05-22
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.22 work shipped in @bp responsive attribute system (grid/col/row/text/block accept @bp), empty-state-ui variant=danger|warning, alert/segmented/stat/table truncation fixes, UI inset/gap scale reduction, 21 component example pages corrected; @adia-ai/web-modules admin-topbar/statusbar padding + admin-page-header/body breakpoint refinements. See `packages/web-components/CHANGELOG.md#0622--2026-05-22` for details.
+
+## [0.6.21] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.21 work shipped in `@adia-ai/web-components` (`table-ui` truncate-by-default + `[wrap]` opt-in §403; toast / feed-item variant text colour; `input-ui` slot-label crowding fix) and `@adia-ai/web-modules` (`<admin-entity-item>` row-inset alignment; FEEDBACK-37 retraction — spurious slot-contract `console.warn` removed; page-header title row no longer stacks under `?chunks` dev overlay). See `packages/web-modules/CHANGELOG.md#0621--2026-05-21` for details.
+
+## [0.6.20] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.20 work shipped in `@adia-ai/web-components` + `@adia-ai/web-modules` — the claims-ui-v5 inbound feedback batch (FEEDBACK-34…39: `table-ui` / `select-ui` / `chart-ui` fixes, the new `<admin-entity-item>` shell primitive, `admin-topbar` / `admin-statusbar` slot diagnostics) plus the `<admin-page-header>` `--a-canvas-0` rebase. See `packages/web-modules/CHANGELOG.md#0620--2026-05-21` for details.
+
+## [0.6.19] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.19 work shipped in `@adia-ai/web-components` + `@adia-ai/web-modules` — the claims-ui-v4 inbound feedback batch (FEEDBACK-22…33: `drawer-ui` / `chart-ui` / `segmented-ui` fixes, `UIElement` lifecycle, exports-map `types` conditions) — plus an `@adia-ai/a2ui-corpus` drift remediation. See `packages/web-components/CHANGELOG.md#0619--2026-05-21` for details.
+
+## [0.6.18] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.18 work shipped in `@adia-ai/web-components` — `stat-ui` + `table-ui` `loading` props (FB-12 P2) and `text-ui` `size` / `color` / `weight` / `text-align` overlay attributes (FB-10). See `packages/web-components/CHANGELOG.md#0618--2026-05-21` for details.
+
+## [0.6.17] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.17 work shipped in `@adia-ai/web-modules` — collapsed-sidebar rules grew a forgiving fallback block for vanilla HTML consumers (`<button class="nav-item">`, `[slot="heading"]`) so text labels don't overflow the 48px rail. See `packages/web-modules/CHANGELOG.md#0617--2026-05-21` for details.
+
+## [0.6.16] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.16 work shipped in `@adia-ai/web-modules`: (1) `<admin-page>` selector relaxed to descendant combinator so router-wrapped layouts no longer collapse to `display: inline` at narrow viewports (was the root of the page-header/KPI overlap regression); (2) `--page-content-header-bg` rebased from `--a-canvas-2` to `--a-canvas-1` so the page-header reads as shell-chrome continuation. See `packages/web-modules/CHANGELOG.md#0616--2026-05-21` for details.
+
+## [0.6.15] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.15 work shipped in `@adia-ai/web-components` — `installIconLoaders` shape-detects malformed flat globs (FB-07 auto-promote + warn), `icons-phosphor.js` surfaces silent-fail diagnostics (FB-08), and .claude/docs/skill examples corrected (FB-09). See `packages/web-components/CHANGELOG.md#0615--2026-05-21` for details.
+
+## [0.6.14] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.14 work shipped in `@adia-ai/web-modules` — `<admin-page-header>` now uses `var(--page-content-header-bg)` (= `--a-canvas-2`) + `var(--a-shadow-sm)` so the page-header band reads as elevated chrome over the body canvas. See `packages/web-modules/CHANGELOG.md#0614--2026-05-21` for details.
+
+## [0.6.13] — 2026-05-20
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.13 work shipped in `@adia-ai/web-modules` — `<admin-shell>` default `mode` is now `"rounded borderless"` (bare-tag auto-promote on connect; any explicit `mode` attribute still wins). See `packages/web-modules/CHANGELOG.md#0613--2026-05-20` for details.
+
+## [0.6.12] — 2026-05-20
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.12 work shipped in `@adia-ai/web-modules` — admin-shell legacy CSS bridges retired per ADR-0032 (continuation of ADR-0023 + ADR-0024). See `packages/web-modules/CHANGELOG.md#0612--2026-05-20` for the breaking-change details + migration path.
+
+## [0.6.11] — 2026-05-20
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.11 work shipped in `@adia-ai/web-components` (`<canvas-ui>` `.d.ts` hand-author covering 9 imperative runtime methods, claims-ui-v2 inbound FB-02 finding 2 closure) and `adia-ui-kit` skill v2.8.0 bundled feedback close (FB-01, FB-02 findings 1+3, FB-03; graduated `/with-css` opt-in docs + `ADIA_TICKETS_DIR` central-inbound workflow).
+
+## [0.6.10] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.10 work shipped in `@adia-ai/web-modules` (4 shell `/with-css` opt-in companion subpaths, claims-ui FB-06 closure, ADR-0030) and `@adia-ai/web-components` (`<table-toolbar-ui>` unknown-attr `console.warn`, FB-04 enhancement; release-gate hygiene).
+
+## [0.6.9] — 2026-05-21
+
+### Maintenance
+- **Lockstep version bump only.** No source changes in this package; bumped to maintain the 9-package version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.6.9 work shipped in `@adia-ai/web-components` (CSS `@scope` codemod, F-002) and `@adia-ai/web-modules` (cross-package subpath docs, FB-08).
+
+## [0.6.8] — 2026-05-20
+
+- Lockstep version bump. Headlining work in `@adia-ai/web-components`
+  (FB-55 `.camelCaseProp=${expr}` two-layer name resolution + FB-57
+  SVG/MathML namespace-aware `mount()` + USAGE.md docs cluster) and
+  `@adia-ai/web-modules` (claims-ui F-001 chat-shell.js barrel-import
+  fix + F-006 required-CSS callouts). No source changes in this package.
+
+## [0.6.7] — 2026-05-19
+
+- Lockstep version bump; no source changes.
+
+## [0.6.6] — 2026-05-18
+
+### Changed
+- Lockstep version bump for §304 `<field-ui align>` prop.
+## [0.6.5] — 2026-05-18
+
+### Added
+- `test/type-bugs.test.ts`: Phase 5 exit gate compile-only tests. Verifies
+  branded ID cross-contamination and A2UIMessage switch exhaustiveness as
+  compile errors (see ADR-0029 + migration plan §9.2).
+
+### Changed
+- `tsconfig.json`: include `../node-shims.d.ts` so node: imports in
+  transitively-included retrieval sources resolve under `tsc -p`.
+Follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+Scope: generation engines (monolithic + zettel), LLM adapters,
+transpiler, evals. Retrieval + validation now ship as sibling
+packages (`@adia-ai/a2ui-retrieval`, `@adia-ai/a2ui-validator`) so
+non-compose consumers can depend on them without pulling the
+generator graph.
+## [0.6.32] — 2026-05-23
+
+_No pending changes._
+
+## [0.6.4] - 2026-05-18
+
+### v0.6.4 — Lockstep ride-along
+
+TS Phase 5: a2ui.schema.json schema-driven codegen (§359). No source changes in this package.
+
+## [0.6.3] - 2026-05-18
+
+### v0.6.3 — Phase 5 branded IDs
+
+`strategies/zettel/types.ts` adds `FragmentId`, `ChunkId`, `CompositionId` branded types.
+**No BREAKING changes.**
+
+## [0.6.2] - 2026-05-18
+
+### v0.6.2 — TS-MIG-001 closed
+
+`skipLibCheck: true` override removed from `tsconfig.json`. Phase 4 retrieval +
+mcp `.ts` sources provide real declarations. **No BREAKING changes.**
+
+## [0.6.1] - 2026-05-18
+
+### v0.6.1 §355 — TypeScript-first Phase 3: `@adia-ai/a2ui-compose` sources → `.ts`
+
+All 29 npm-published `.js` sources gain `.ts` counterparts. `tsconfig.json` gains
+TS-MIG-001 `skipLibCheck` until Phase 4 replaces stub declarations in sibling packages.
+Emit deferred per migration plan §7.6 contingency. **No BREAKING changes.**
+
+## [0.6.0] - 2026-05-18
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.6.0 — see root CHANGELOG)._
+
+**MINOR-line internal-dep range update:** internal `@adia-ai/*` dependency ranges move from `^0.5.0` to `^0.6.0` per AdiaUI lockstep policy.
+
+## [0.5.21] - 2026-05-18
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.21 — see root CHANGELOG)._
+
+## [0.5.20] - 2026-05-18
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.20 — see root CHANGELOG)._
+
+## [0.5.19] - 2026-05-17
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.19 — see root CHANGELOG)._
+
+## [0.5.18] - 2026-05-16
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.18 — see root CHANGELOG)._
+
+## [0.5.17] - 2026-05-16
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.17 — see root CHANGELOG)._
+
+## [0.5.16] - 2026-05-16
+
+### Changed
+- §335 `core/generator.js` — removed dead `currentCanvas.html` references. The `hasClientCanvas` truth-check at line 71 ORed in `currentCanvas.html`, and a `// TODO(tier-2)` comment at line 134 referenced a never-implemented `htmlToComponents()` helper. Verified across `packages/` + `apps/` + `playgrounds/`: zero consumers pass `{ html: "..." }` to `generateUI()`. Also trimmed the speculative "Future:" block from the `currentCanvas` JSDoc (the `{ a2ui, originalIntent, meta }` shape was equally orphan). The shape union is now strictly `{ components } | { messages }`. Closes gemini-review refactor-backlog P2-2.
+
+## [0.5.15] - 2026-05-16
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.15 — see root CHANGELOG)._
+
+## [0.5.14] - 2026-05-15
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.14 — see root CHANGELOG)._
+
+## [0.5.13] - 2026-05-15
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.13 — see root CHANGELOG)._
+
+## [0.5.12] - 2026-05-15
+
+_Lockstep ride-along (no source change in this package; companion to web-components v0.5.12 — see root CHANGELOG)._
+
+## [0.5.11] - 2026-05-15
+
+_Lockstep ride-along (no source change)._
+
+## [0.5.10] - 2026-05-15
+
+_Lockstep ride-along (no source change)._
+
+## [0.5.9] - 2026-05-15
+
+_Lockstep ride-along (no source change)._
+
+## [0.5.8] - 2026-05-15
+
+_Lockstep ride-along (no source change)._
+
+## [0.5.7] - 2026-05-15
+
+### Changed — §210 cross-package sweep — `transpiler/`+`strategies/` text-variant retargeting (v0.5.7)
+
+Companion to `@adia-ai/web-components@0.5.7` §210 (`<text-ui>` variant enum cleanup — removed 6 phantom entries `h1`-`h6` + `subheading`).
+
+- `transpiler/transpiler-maps.js` — `HTML_TAG_MAP` retargets native `<h1>`-`<h6>` + `<summary>` from removed `h1`-`h6` variants to working role tokens (`display` / `title` / `heading` / `subsection`). Pre-§210 the mapping rendered silent body-default; post-§210 each level renders at its declared token size.
+- `strategies/monolithic/_shared.js` — TEXT TYPES system-prompt block updated to enumerate the actual `<text-ui>` variant enum (display/title/heading/subsection/section for headings; body / caption / label / kicker / code / deck / metric for inline / meta / lede). Generator prompt now matches the runtime contract.
+- `strategies/free-form-composer/free-form-composer.test.js` — fixture variant `'h1'` → `'display'` (test stub uses real variant).
+
+## [0.5.6] - 2026-05-14
+
+### Removed — §195 (v0.5.6) — retired fragment-graph iteration codepath
+
+Deleted `packages/a2ui/compose/strategies/zettel/synthesizer.js`. The
+file shipped the `synthesizeComposition` function as a throwing stub
+since §37 (v0.4.7, 2026-05-12, fragment retirement). The dangling
+caller in `generator-adapter.js` (iteration branch, turn ≥ 2 + LLM
+present) caught the throw and auto-fired an `iteration-synthesis-failure`
+issue ticket on every multi-turn refinement — surfaced as an auto-fired
+bug at `.brain/audit-history/issues/2026-05-14-iteration-synthesis-failed-on-turn-3-for-4bfb.json`.
+
+### Changed — §195 (v0.5.6) — weak-retrieval branch bridges to chunk-zettel
+
+Replaced the `synthesizeComposition()` call in `generateZettel`'s
+weak-retrieval-with-LLM branch with a bridge to
+`chunk-synthesizer.js::composeFromIntent` (the §37 successor codepath).
+Return shape is preserved (`messages`, `validation`, `strategy:
+'composition-synthesized'`, `fragments_used: []`, `synthesized_template`,
+`synthesis`). Fragment instances are no longer tracked on this path —
+the chunk-bridge emits a single html-bearing component. Consumers that
+need fragment-level resolution should wire via `engine: 'chunk-zettel'`
+directly.
+
+The `composition-iterated` strategy is retired — turn ≥ 2 on
+`engine: 'zettel'` now takes the same path as turn 1. True
+history-aware iteration lives in `chunk-refiner.js::refineFromIntent`
+behind `engine: 'chunk-zettel'`.
+
+### Added — §195 (v0.5.6) — smoke probe
+
+NEW `scripts/smoke-iteration-synthesis.mjs` (npm run
+`smoke:iteration-synthesis`) verifies the §195 invariants at three
+layers: filesystem (`synthesizer.js` deleted), source
+(`generator-adapter.js` has no surviving reference to the retired
+identifiers), and runtime (4 sequential turns against the same
+sessionId neither throw nor emit `composition-iterated`).
+## [0.5.5] - 2026-05-14
+
+### Changed — §179 (v0.5.5) — principled `deprecated:` yaml field
+
+Three new yaml schema fields under each prop:
+
+- **`deprecated`** (boolean, default `false`) — when `true`, the LLM prompt builder appends `(deprecated, do not use)` to the prop's line in CORPUS CONTEXT.
+- **`deprecated_since`** (string) — version when deprecation was introduced.
+- **`deprecated_reason`** (string) — human-readable migration guidance.
+
+Build pipeline (`scripts/build/components.mjs::compileProp`) collects deprecation metadata and inlines onto the prop schema. Prompt builder (`packages/a2ui/compose/strategies/monolithic/_shared.js`) reads `v.deprecated === true` FIRST; falls back to `/deprecated/i.test(v.description)` (the v0.5.4 §167a substring detection) for back-compat. Existing §167a-tagged props continue to work without yaml changes.
+
+Demonstrated on `Avatar.name`. Verified via `buildSystemPrompt`: `name:String[] (deprecated, do not use)` surfaces in CORPUS CONTEXT.
+
+Commit `0379dd498`. See root CHANGELOG and journal §179 for full context.
+## [0.5.4] - 2026-05-14
+
+### Fixed — §163 transpiler prop-fidelity; catalog-driven extractor closes the harvester drop class (v0.5.4)
+
+`packages/a2ui/compose/transpiler/transpiler-maps.js` rewritten to derive
+the extractable-prop set from the v0.9 catalog at module init, replacing
+the pre-§163 hand-maintained per-type allowlists that omitted `label`,
+`icon`, literal `variant=`, and similar first-class props.
+
+**Bug class diagnosed 2026-05-14** against composition `auth-signin-card-password`
+rendering blank rectangles in the gen-ui canvas. Verified pre-§163 vs post-§163
+against `apps/user-flow/app/auth/sign-in/password/password.contents.html`:
+
+  Password Input  pre={} post={label,type,autocomplete,name,placeholder,required}
+  Remember check  pre={name} post={name,label}
+  Sign in button  pre={type} post={type,text,variant}
+  Divider         pre={} post={label}
+  Magic-link btn  pre={} post={icon,text,variant}
+  6-digit btn     pre={} post={icon,text,variant}
+
+**Implementation**: `CATALOG_PROPS` Map built at module init from
+`@adia-ai/a2ui-corpus/catalog-a2ui_0_9.json`; `TYPE_ALIAS` map with
+4 resolution passes (catalog-self-map + direct registry-match +
+shared-tag-match + kebab-to-PascalCase fallback) — closes the
+registry-vs-catalog name drift (registry has `CheckBox → check-ui`;
+catalog uses `Check`). Generic catalog-driven pass runs FIRST in
+`extractProps()`; legacy per-type blocks defer with `if (props.X === undefined)`
+guards so catalog values win on conflict.
+
+**Side-effect fixes**: pre-existing legacy quirks (Slider `'0'` → `'0'`
+returning string instead of numeric `0`, Button `disabled="false"` → `true`)
+incidentally fixed by the deferred-legacy pattern.
+
+NEW `packages/a2ui/compose/transpiler/extract-props.test.js` (+228 LOC,
+19 tests) pinning the regression class.
+
+Cycle followup: §164 re-harvested all 230 chunks with the §163-fixed
+transpiler (corpus package; +2920 LOC restored prop fidelity). §166a
+added audit-script-family slot 12 (`check-extract-props-coverage.mjs`)
+that re-verifies the catalog-vs-extractor invariant at every commit.
+
+### Fixed — §168 canvas-iteration merge always-on; close the 50-threshold mismatch (v0.5.4)
+
+`packages/a2ui/compose/strategies/monolithic/generate-pro.js:374` —
+removed the `priorComponents.length >= 50` gate. `mergeCanvasDiff()`
+now runs on every iteration turn regardless of canvas size.
+
+Closes the chart-workflow regression diagnosed 2026-05-14:
+32-component canvas + "add a chart" intent → 202-component response
+wholesale-replaced the user's prior work (`exec_mp4zbj47_1`,
+`comps= 202 score= 105`). Pre-§168 the 0–49 band had no merge gate
+even though the prompt asked the LLM to return COMPLETE; LLM canvas
+explosions wholesale-replaced. Now: `mergeCanvasDiff` runs always,
+the hallucination-detection guards (matchRatio < 0.2 reject + < 0.6
+accept-with-warning) discriminate by match ratio (more principled than
+canvas-size heuristics), and small-canvas iterations correctly preserve
+prior work when LLM speculatively expands.
+
+`mergeCanvasDiff` is a strict superset of "wholesale-replace"
+behaviorally: COMPLETE arrays merge to identical shape; DIFF arrays
+process unchanged; hallucinated rewrites get rejected with
+"Hallucinated replacement rejected" + canvas preservation.
+
+NEW `merge-canvas-diff.test.js` (+251 LOC, 12 tests) pinning behavior
+across all three bands (strict-superset-of-replace, hallucination
+guards, DIFF format, layout-type guards, the §168 chart-workflow
+regression fixture).
+
+### Fixed — §169 iteration-prompt structural priming; Card/Stat/Chart anatomy carry-over (v0.5.4)
+
+`packages/a2ui/compose/strategies/monolithic/_shared.js`
+`buildCanvasDiffPrompt()` — added NEW `ITERATION_STRUCTURAL_RULES`
+block injected into both the full-canvas + compact-summary branches.
+
+Pre-§169 the iteration prompts said "Preserve slot attributes and
+Card anatomy rules" without defining what those rules ARE. The
+fresh-generation prompt at `buildSystemPrompt()` defines them
+explicitly (Card > Header > [slot=heading...], Card > Section >
+Column > [content], etc.) but iteration mode relied on multi-turn
+context retention, which is unreliable.
+
+Empirically the corpus enforces Card > Section > Column > Chart
+(233 Section→Column + 95 Card→Section across 230 chunks). The
+2026-05-14 user-reported "where chart data should live in the tree"
+ticket was the LLM emitting Chart at the wrong depth during
+iteration.
+
+Token cost: ~150 tokens added to a 500-1500-token iteration prompt;
+well within 32k max_tokens budget.
+
+### Fixed — §167 surface yaml-declared deprecation to LLM via prompt builder (v0.5.4)
+
+`packages/a2ui/compose/strategies/monolithic/_shared.js:274` (+ legacy
+fallback at `:312`) — when building the per-component prop string,
+append `(deprecated, do not use)` to any prop whose description
+matches `/deprecated/i`.
+
+Closes the `<avatar-ui name="...">` false-positive class observed
+2026-05-14 console:
+
+  ```
+  class.js:60  [AdiaUI] <avatar-ui name="…"> is deprecated — use text="…" instead.
+  ```
+
+Root cause: `avatar.yaml` + sidecar + catalog all declare
+`Avatar.name` as a prop with description `"Deprecated alias for
+text..."`. The prompt builder captured description into
+`out.description` (line ~56) but never read it when assembling the
+`props:` line. LLM saw both `name` and `text` as equally-valid prop
+names and naturally picked `name` for "team member names" intents.
+
+Post-§167 prompt:
+  ```
+  - Avatar: ...  props: icon:String, name:String (deprecated, do not use), ...
+  ```
+
+### Fixed — §172 ChatInput catalog entry + scanner sibling-yaml fix + intent-keyword family inclusion (v0.5.4)
+
+Closes ticket `20260514045025-chatinput-training-data-unclea` —
+user reported the generator created a redundant Button(primary)
+sibling next to ChatInput, duplicating the built-in send button
+that `<chat-input-ui>` already stamps.
+
+**Three architectural layers fixed:**
+
+1. **Build scanner sibling-yaml discovery** —
+   `scripts/build/components.mjs` (+15 LOC). Pre-§172 the scanner
+   only looked for `<name>/<name>.yaml`; sibling yamls in the same
+   dir were invisible. `<chat-input-ui>` (sibling of chat-thread)
+   and `<feed-item-ui>` (sibling of feed) were orphans —
+   registered at runtime but invisible to the catalog. Post-§172
+   sibling discovery is automatic.
+
+2. **Retrieval catalog loader sibling-sidecar discovery** —
+   `packages/a2ui/retrieval/component-catalog.js:_loadNode()`
+   (+24 LOC). Same blind spot; same fix. Browser path already
+   recursive via `import.meta.glob('**/*.a2ui.json')`; Node path
+   now matches.
+
+3. **Intent-keyword family inclusion in prompt builder** —
+   `packages/a2ui/compose/strategies/monolithic/_shared.js`
+   (+26 LOC). Pre-§172 the prompt's always-include list had generic
+   primitives only; chat/table/form/chart/nav components only
+   entered via retrieval-pattern match. Post-§172 the chat family
+   (`ChatInput, ChatThread, ChatComposer, ChatShell, ChatHeader,
+   ChatSidebar`) is force-included when the intent mentions
+   `chat/message/conversation/composer/thread`. Same for the other
+   4 families.
+
+Together: ChatInput's full description, 3 a2ui rules, and 3
+anti-patterns (the "DO NOT add a separate Button sibling for send"
+guidance) now appear in every chat-intent prompt's CORPUS CONTEXT
+block.
+
+**Sixth distinct application of the SoT-coherence pattern** in
+v0.5.4 (§163 + §167 + §168 + §169 + §170 + §172).
+
+Commit `514e72697`.
+
+### Maintenance — audit-script companions §173 + §175 ship in v0.5.4 (no source change to compose)
+
+Repo-level audit scripts targeting compose drift classes:
+
+- **§173 `check-iteration-prompt-coherence.mjs`** (slot 14) — guards against
+  regressions in `monolithic/_shared.js` deprecation-marker logic (§167) +
+  iteration-prompt structural rules block (§169).
+- **§175 `check-registry-catalog-coherence.mjs`** (slot 16) — guards against
+  registry/catalog drift like §172 ChatInput orphan-component class.
+
+No compose source change in §173/§175 — both detect future drift in compose's
+catalog-vs-prompt + registry-vs-catalog invariants.
+
+### Changed — `version`: `0.5.3` → `0.5.4`.
+## [0.5.3] - 2026-05-14
+
+### Fixed — Deterministic chunk-loading order in zettel composition library (§160, v0.5.3)
+
+`strategies/zettel/composition-library.js`: `walk()` now sorts `fs.readdirSync` output via `localeCompare` before recursing. Pre-§160 the directory walker relied on filesystem-defined entry order, which varies across processes on APFS/ext4. When two chunks tied on retrieval score for a given intent, the first-loaded won the tie-break — so the same intent could match chunk A in one process and chunk B in the next.
+
+Surfaced as ~40% flake rate on the `admin dashboard with kpi cards` retrieval probe post-§143 (the 8 new UI-primitive chunks compete with the original `dashboard-kpi-grid` template). Sorted walk pins load order; remaining flakiness is now constrained to a corpus-quality bug (Stat chunks strip `label`/`value`/`change` attrs in the `template` field) tracked as v0.5.4 F-S1a.
+
+No behavior change for callers that don't hit a tie-break — most intents have a clear retrieval winner.
+
+### Deprecated — `_debug.attempts` and `_debug.warnings` on free-form-composed results (§146, v0.5.3)
+
+Finalizes the v0.6.0 deprecation schedule for the last two `_debug.*` fields that consumers might still read on `generateFreeFormAdapter`'s result. Both fields are dialog-recorder-gated (silently `undefined` when not recording) — the same access pattern §109 (v0.5.1) + §107a (v0.5.2) removed for `usedIngredients` / `rationale` / `plan`.
+
+**v0.6.0 migration path** (folded into the inline `@deprecated` JSDoc on `strategies/registry.js`):
+
+- `result._debug?.attempts` → `result.attempts: number` (LLM round-trips: 1 normally; 2-3 with hallucination retry or paraphrase-retry)
+- `result._debug?.warnings` → `result.warnings: string[]` (non-fatal transpile findings: unknown substitution keys, layout-value fall-throughs, chunk-resolution warns)
+
+**Scheduled removal**: v0.6.0 drops the `_debug` block entirely from the free-form-composed result shape. The dialog-recorder will read first-class fields directly. v0.5.3 is the **migration window** — any external consumers reading `_debug.attempts` / `_debug.warnings` should switch to the first-class fields before v0.6.0 ships.
+
+**Internal verification**: zero live in-repo consumers (`grep -rn '_debug\?\.attempts\|_debug\.attempts\|_debug\?\.warnings\|_debug\.warnings' apps/ playgrounds/ catalog/ packages/` returns only the deprecation comment itself).
+## [0.5.2] - 2026-05-13
+
+### Changed — `plan` graduates from `_debug.*` to first-class on free-form-composed result (§107a infra, v0.5.2)
+
+`strategies/registry.js` `generateFreeFormAdapter` returns `plan` as a top-level result field (paired with v0.5.1's §109 graduation of `usedIngredients` + `rationale`). The `_debug.plan` field is no longer populated — consumers should read `result.plan` directly. Soft-API change (`_debug` was always documented as volatile).
+
+Enables substitution-coverage measurement at eval time without dialog-recorder coupling. Companion to `@adia-ai/a2ui-mcp` `--report-substitutions` flag.
+
+### Deprecated — individual `_debug.*` field reads on free-form-composed results (§131, v0.5.2)
+
+Documents the `_debug`-volatility contract that §109 (v0.5.1) + §107a (v0.5.2) established de-facto. The `_debug` block on `generateFreeFormAdapter`'s result is **dialog-recorder-gated** — populated only when `isRecording()` returns true; otherwise `undefined`. Individual field reads (`result._debug?.usedIngredients`, `result._debug?.rationale`, `result._debug?.plan`) were silently broken under that gating, which is why §109 + §107a graduated the consumer-relevant fields to first-class.
+
+**Migration:** any consumer reading `result._debug?.<field>` for a field other than `systemPrompt` / `rawLLMResponse` / `tokens` / `attempts` / `warnings` should switch to the first-class field. The currently-stable first-class set: `usedIngredients`, `rationale`, `plan`.
+
+**Scheduled removal:** v0.6.0 folds `attempts` + `warnings` into first-class result fields and drops the `_debug` block entirely from the free-form adapter's return value. The dialog-recorder will read first-class fields directly.
+
+No live in-repo consumers of the soft-API path remain (verified `grep -rn '_debug?\.\|_debug\.' apps/ playgrounds/ catalog/` → 0 hits). One dead fallback in `@adia-ai/a2ui-mcp`'s `eval-diff.mjs` (`result.plan || result._debug?.plan || null`) removed in the same cut.
+
+### Changed — Free-form system prompt: 5 per-shape substitution examples + self-check pattern (§126, v0.5.2)
+
+`strategies/free-form-composer/system-prompt.js` constraint 3 extends the v0.5.1 §107b ALWAYS-substitute paragraph with 5 concrete examples (one per substitutable shape: Text/Kbd, Button, Badge/Tag, Icon, Image, Link) plus a self-check sentence at the end ("Before emitting, self-check: re-read the user's intent…").
+
+Targets the v0.5.1 §107a finding that Haiku 4.5 underweights `ALWAYS`-style directives relative to Opus: example-density beats directive-strength for Haiku's prompt-following. Per-shape examples chosen to span the substitution-key namespace (Button:"text", Badge:"text", Icon:"name", Image:"alt", Link:"href") so the LLM sees the substitution-routing rules for each component type.
+
+Cost: ~120 additional prompt tokens per call (~0.5% of total). Acceptable.
+
+Expected impact: lifts substitution ratio 27.4% → ~35-40% (target ≥30%); F1 may lift incrementally as substituted text now matches user-intent vocabulary better. Paired with §125 (component-type structural sweep) — both target the F1 plateau from orthogonal angles.
+
+### Changed — `generateFreeFormAdapter` accepts `ctx.model` override + reads `FREE_FORM_MODEL_OVERRIDE` env var (§127 infra, v0.5.2)
+
+`strategies/registry.js` reads model priority chain at call-time (not module-load): `ctx.model` > `process.env.FREE_FORM_MODEL_OVERRIDE` > `FREE_FORM_MODEL_DEFAULT` (Haiku 4.5). Enables `eval-diff.mjs --model <id>` to run the Haiku-vs-Opus A/B for §127 without env-dance or static-import-ordering hazards. `FREE_FORM_MODEL` constant renamed to `FREE_FORM_MODEL_DEFAULT` to reflect the new priority chain.
+
+Default behavior unchanged when no override set — the v0.5.1 §108 Haiku pin holds for every consumer that doesn't explicitly override.
+## [0.5.1] - 2026-05-13
+
+### Added — Free-form composer INTENT-PARAPHRASE block + paraphrase-retry (§106, v0.5.1)
+
+System prompt for `strategies/free-form-composer/` now includes an INTENT-PARAPHRASE block guiding the LLM to re-read keyword-mismatch intents in alternate phrasings before declaring `empty-plan`. On `empty-plan` emission, the strategy retries once with an explicit paraphrase instruction. Targets the 8 keyword-mismatch intents identified in §92's full-100 characterization (e.g. "show me the leaderboard" vs the corpus chunk's `leaderboard-table` keywords).
+
+Targeted lift: closes 5-6 of the 8 keyword-mismatch failures from §104's 92% baseline. F1 on the remaining 2-3 is intent-shape-dependent; v0.5.2+ corpus regrowth handles those.
+
+### Changed — Haiku 4.5 pinned for free-form ingredient picker (§108, v0.5.1)
+
+`strategies/registry.js` `generateFreeFormAdapter` now mints a Haiku 4.5 adapter (`claude-haiku-4-5-20251001`) for the picker task instead of inheriting `ctx.llmAdapter`. Rationale: the picker task is "select N from 86 ingredients + emit strict JSON" — Haiku handles this well at ~5× cheaper + ~3× faster than Opus, freeing the Opus budget for `monolithic-pro` fall-throughs. User-decided pre-A/B per the v0.5.1 plan question 2.
+
+Consumers passing `ctx.llmAdapter` keep getting their adapter via the mint-failure fallback path (no proxy / no key → falls back to `ctx.llmAdapter`).
+
+### Changed — `usedIngredients` + `rationale` graduate from `_debug.*` to first-class (§109, v0.5.1)
+
+`strategies/registry.js` `generateFreeFormAdapter` lifts `usedIngredients` + `rationale` out of the `_debug` block to top-level result fields. Auto-engine + factory-chat UI both depend on `usedIngredients` for trace labels; coupling visibility to dialog-recorder state was fragile (silently null when not recording). Soft-API addition — consumers reading `result.usedIngredients` get the array reliably; old `result._debug?.usedIngredients` access path becomes redundant but isn't removed (deprecation path lives in v0.5.x or v0.6.0).
+
+### Coverage at v0.5.1 cut
+
+Post-§106 prompt-tuning + §108 picker pin + §109 first-class graduation, free-form composer coverage measured at **~96-97%** on the 100-intent held-out set (up from §104's 92%). New AGENTS.md regression threshold floor: `cov≥96%, avg≥85, F1≥0.60` (§115 trip-wire baseline).
+## [0.5.0] - 2026-05-13
+
+### Added — Free-form composer auto-grouping (§103, v0.5.0)
+
+Free-form composer (`strategies/free-form-composer/`) now accepts an optional `layout: "column" | "row" | "grid"` field on the LLM's plan, picking the root container instead of always wrapping in `Column`. System prompt teaches the schema; `transpile.js` validates against a `VALID_LAYOUTS` set + falls through to `Column` with a warning on unknowns. Unit-tested across 6 cases (Column / Row / Grid root, lowercase normalization, unknown→fallback, omitted→default). Lifts F1 on the ~20 grid/row-shaped intents identified in §92's full-100 characterization — coverage stays put; the same plans now render with the right root primitive.
+
+Plan-schema change is non-recursive — only the ROOT container choice. Nested-container composition (a Grid of Cards each containing a Row) deferred to v0.5.x+.
+
+### Added — Free-form structural substitutions (§104, v0.5.0)
+
+Extends `applyTextSubstitutions()` beyond `Text.textContent` to Button.text, Badge.text, Tag.text, Icon.name, Image.alt, Link.href, and Kbd.textContent — the seven primitive surfaces where a substitution-driven F1 lift is meaningful. The LLM's plan declares per-component substitutions with named target keys (e.g. `Button: { text: "Sign in" }`), and the transpiler routes each substitution to the correct prop on the matched primitive.
+
+Schema validation rejects unknown target keys; downgrade warnings fire when a target-key doesn't match the matched ingredient's primitive (e.g. consumer asked for Icon.name but the matched ingredient is a Button — falls through to Button.text with a diagnostic so the eval harness can surface the miss).
+
+### Coverage at v0.5.0 cut
+
+After §93 (layout regrowth) + §94 (forms regrowth) + §103 (auto-grouping) + §104 (structural substitutions + v0.5.1 deferred regrowth fold-in), free-form composer coverage measured at **92% on the 100-intent held-out set** (up from 21% at §92 baseline). New AGENTS.md regression threshold floor: `cov≥80%, avg≥85, F1≥0.45` (§97 rebaseline).
+## [0.4.9] - 2026-05-13
+
+_No pending changes._
+## [0.4.8] - 2026-05-12
+
+### Fixed — `strategies/zettel/generator-adapter.js` `ensureBooted()` race (§87a, v0.4.8)
+
+The zettel composition library's lazy boot had a race condition where concurrent `ensureBooted()` calls could each kick off a separate boot promise. Under contention (multiple requests landing simultaneously at server cold-start), the composition map could be partially populated when consumers reached the synchronous getters. Fix: memoize the boot promise on first call so all subsequent callers await the same promise. Pairs with the v0.4.8 §87 honest-floor eval threshold rebaseline — without the boot race fix, the 1% rebaseline was actually undercounting due to occasional empty-map reads.
+## [0.4.7] - 2026-05-12
+
+### Changed — `strategies/monolithic/_shared.js` `getComponentCatalog()` reads canonical catalog (§72)
+
+The legacy reader of `@adia-ai/a2ui-corpus/patterns/_components.json` has been migrated to read `@adia-ai/a2ui-corpus/catalog-a2ui_0_9.json` (the canonical v0.9 catalog, already the package root export). Per-component aliases are now lifted from `components[name].x-adiaui.synonyms.tags`. Same legacy output shape (`{ <Name>: { aliases: string[] } }`); zero behavior change for downstream callers.
+
+Closes the §65 carry-over from v0.4.6 — `@adia-ai/a2ui-corpus` `patterns/` + `compositions/` are now deleted from disk + tarball.
+## [0.4.6] - 2026-05-12
+
+### Changed — `core/` retirement follow-through (§64, v0.4.6)
+
+Companion to `@adia-ai/a2ui-retrieval@0.4.6` retiring `pattern-library.js`:
+
+- **`compose/core/pattern-export.js`** retired — no consumers post-§64 (the export shape targeted the retired pattern-library surface).
+- **`compose/core/reference.js`** — updated to delegate to `composition-library` instead of the retired `pattern-library`.
+- **`compose/core/generator.js`** — dropped pattern-export wiring; system-prompt path consumes compositions directly via §66's `adaptV09Component()`.
+
+### Changed — `buildSystemPrompt` reads canonical `.a2ui.json` sidecars (§66, v0.4.6)
+
+Closes the catalog-drift surface that §56 explicitly deferred ("different schema shapes; restructuring `getComponentCatalog()` is its own arc"). The monolithic prompt builder now reads from the v0.9 `.a2ui.json` sidecars (generated from yamls by `npm run components`) instead of the legacy hand-maintained `_components.json` catalog.
+
+**Root cause uncovered during audit:** `strategies/monolithic/_shared.js` (pre-§66) called `getComponentData(typeName)` returning the raw v0.9 sidecar — `{title, description, properties, x-adiaui}` (JSON Schema shape) — but the prompt builder code did `a2uiData.props ? Object.entries(a2uiData.props)`. The v0.9 shape uses `properties`, not `props`. **Every prompt was silently falling through to the legacy `_components.json` catalog** because every v0.9 lookup looked empty. The "canonical sidecar reads" path was wired but dead code.
+
+**Fix:** new `adaptV09Component()` helper at the top of `_shared.js` (~90 LOC) normalizes the v0.9 sidecar shape to the legacy `{tag, category, description, props, events, slots, examples, aliases, keywords}` shape the rest of the prompt builder was written for. Properties map 1:1 (skipping `component` discriminator + `children` container + `const`-only fields). Type names map JSON-Schema lowercase → legacy Title-Case (`string`→`String`, `boolean`→`Boolean`, etc.).
+
+**Empirical fidelity gain** (Button as canonical primitive):
+
+| Source | Props surfaced |
+|---|---|
+| `_components.json` (legacy, before §66) | 7: `text, variant, size, disabled, block, icon, type` (`block` is stale — removed from yaml in an earlier arc but never cleaned up in the hand-maintained catalog) |
+| v0.9 sidecar (canonical, after §66) | 10: `type, aria-label, color, disabled, icon, size, stretch, text, textContent, variant` |
+
+**§66 surfaces ~30% more catalog data** for the LLM, all traceable to a yaml SoT that `npm run components` regenerates on demand. This is exactly the catalog drift §56 flagged: when the team added `Select.size` (§50) and `inputmode`/`autocomplete` (§51) to the yamls, those props went into the v0.9 sidecars but never propagated to `_components.json`. The LLM was getting a stale catalog view that excluded recent additions. After §66, the LLM gets the actual ground truth.
+
+**Pitfalls encoded in the adapter** (5 v0.9-shape gotchas):
+1. `events` is an object `{eventName: {description}}`, not an array. Normalize to `string[]`.
+2. `slots` is also object-shaped. Same fix.
+3. `synonyms.tags` may be null/undefined. Wrap in `Array.isArray()` guard.
+4. `component` and `children` properties on every v0.9 sidecar are discriminator/container fields, not user-facing props. Skip in the adapter loop.
+5. `const` fields (e.g. `{const: 'Button'}`) are discriminator-only. Skip.
+
+Source: `packages/a2ui/compose/strategies/monolithic/_shared.js` (+91, -2 lines, commit `afda98f5`).
+## [0.4.5] - 2026-05-12
+
+### Changed — GenUI overhaul prompt-engineering (§56, v0.4.5)
+
+- **`strategies/monolithic/_shared.js` — CORPUS CONTEXT block added to `buildSystemPrompt`** (~30 new lines between role/output-format and CARD-N content model). Surgical insertion explaining the §36-§51 retrieval-augmented pipeline:
+  - Pipeline searches PATTERNS / COMPOSITIONS first (full-canvas A2UI templates: login-form, pricing-tiers, dashboard-admin-page)
+  - Pipeline also searches ANNOTATED CHUNKS (real production HTML with `metadata.{domain, keywords, description}`)
+  - When matched, `MATCHED PATTERN` / `STRUCTURAL REFERENCE` blocks carry the actual reference
+  - Only AVAILABLE COMPONENTS are usable — anything else is a hallucination
+
+  Cost: ~150 tokens per request. Benefit: LLM understands what the pipeline around it IS instead of treating the matched-pattern block as anonymous instructions. Existing rules unchanged; no removed lines.
+
+- **`strategies/monolithic/generate-pro.js` — STRUCTURAL REFERENCE prose enriched.** Prior copy: "a real production block from the codebase matched this intent." New copy: "this chunk was retrieved from the AdiaUI training corpus (annotated production HTML, harvested from real app pages). It matched your intent on keyword/domain ranking." Threads chunk `metadata.domain`, `metadata.description`, `metadata.keywords` into the prompt when present. Reframes "do not copy the HTML" as "the chunk represents the SHAPE the user wants; instantiate it with their content" — more actionable framing.
+
+See root [CHANGELOG.md `[Unreleased]`](../../../CHANGELOG.md) for the v0.4.5 overhaul arc + apps/genui/CHANGELOG.md `[Unreleased]` for the per-§ rollup.
+## [0.4.4] - 2026-05-12
+
+### Changed
+
+- **`strategies/zettel/fragment-library.js` → `composition-library.js` rename (§38).** Reflects the actual responsibility post-§37 (fragments retired; library now loads compositions + annotated chunks). API shape unchanged for callers; back-compat shims dropped after grep-verified zero external consumers.
+- **`strategies/zettel/composer.js` simplified (§37).** `resolveComposition` becomes a defensive copy + strip pass now that compositions are flat A2UI templates (no slot machinery). `templateToMessages` preserved for callers.
+- **`strategies/zettel/composition-library.js` — read annotated chunks alongside hand-authored compositions (§41).** `loadAll()` walks both `corpus/compositions/` (hand-authored) AND `corpus/chunks/` (annotated + transpiled). Chunks with a `metadata` field AND a `template` field get normalized to composition shape via `chunkToComposition()`. Name collisions: hand-authored wins with a loud warn. Boot reports `compositionCount=127, handAuthored=100, annotatedChunks=27` post-§50.
+- **`strategies/zettel/synthesizer.js` retired as throwing stub (§37).** Throws `SYNTHESIZER_RETIRED`; generator-adapter's try/catch handles it gracefully. Deferred follow-up: chunk-based synthesizer for zettel iteration.
+- **`compose/transpiler/transpiler-maps.js` — `<a>` → `Link` (was: `Button + variant=ghost`) (§47).** button.yaml line 60 explicitly documents `<link-ui>` is the canonical link primitive: *"Mixing navigation and action affordances under the same primitive is a category error fixed at this junction."* The transpiler had been making this category error since project inception. Added a Link-specific extractor block (parallels the Button extractor at line 154) that pulls `href` / `target` / `rel` from the source attrs.
+
+### Fixed
+
+- **`compose/strategies/monolithic/generate-pro.js` + companion `_shared/fragment-expander.js` — fragment machinery removed (§37).** Fragments retired; 85 compositions inlined with previously-referenced fragment content. Expander deleted; its caller's try/catch in `generator-adapter.js` handles the absence gracefully.
+- **MCP server `mcp/server.js` (§37).** Removed `get_fragment` tool, simplified `zettel_stats`, updated imports + boot logs + engine description to reflect the post-fragment world.
+
+See root [CHANGELOG.md `[Unreleased]`](../../../CHANGELOG.md) for the cross-cutting arc narrative + `.claude/docs/journal/2026/05/2026-05-12.md` §§ 37 / 38 / 41 / 47 for per-§ details.
+## [0.4.3] - 2026-05-11
+
+### Fixed
+
+- **`process.env` browser-compat guard** — `core/generator.js` and `strategies/zettel/state-cache.js` were accessing `process.env` directly, which throws `ReferenceError: process is not defined` in browser execution paths (e.g. the gen-ui playground importing compose directly). Both sites now guard via `const IS_NODE = typeof process !== 'undefined' && process.versions?.node;` before reading `process.env`. The `A2UI_COMPOSE_TRACE` debug-trace and `STATE_CACHE_DIR` env-lookup paths are Node-only by design; the dynamic `node:fs/promises` + `node:path` imports also short-circuit when `IS_NODE` is false.
+
+### Lockstep
+
+9-package coordinated PATCH cut to v0.4.3 (per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy)). Internal `@adia-ai/*` dep ranges stay at `^0.4.0` (patch-cut asymmetry — `^0.4.0` covers `0.4.x` under semver). Source change scoped to `core/generator.js` + `strategies/zettel/state-cache.js`. Rides alongside `@adia-ai/web-components` v0.4.3 (input-ui locale + thousands grouping + hold-to-repeat). See root [CHANGELOG.md `## [0.4.3]`](../../../CHANGELOG.md) for the cut narrative.
+## [0.4.2] - 2026-05-11
+
+### Ride-along (no source changes)
+
+Lockstep PATCH cut alongside `@adia-ai/web-components@0.4.2` (`<input-ui type="number">` rewrite drops native `<input type=number>` wrapping) + `@adia-ai/web-modules@0.4.2` (`<editor-sidebar>` grid-track width-mirror fix). Source byte-identical to v0.4.1.
+
+Internal `@adia-ai/*` dep ranges stay at `^0.4.0` (patch-cut asymmetry — `^0.4.0` covers `0.4.x` under semver). See root [CHANGELOG.md `## [0.4.2]`](../../../CHANGELOG.md) for the cut narrative.
+## [0.4.1] - 2026-05-10
+
+### Ride-along (no source changes)
+
+Lockstep PATCH cut alongside `@adia-ai/web-modules@0.4.1` (simple cluster) + `@adia-ai/a2ui-validator@0.4.1` (Phase 3 foundation) + `@adia-ai/a2ui-corpus@0.4.1` (fragment metrics reconciliation). Source byte-identical to v0.4.0.
+
+Internal `@adia-ai/*` dep ranges bumped from `^0.4.0` to `^0.4.1`. See root [CHANGELOG.md `## [0.4.1]`](../../../CHANGELOG.md) for the cut narrative.
+## [0.4.0] - 2026-05-10
+
+### Ride-along (no source changes)
+
+Lockstep MINOR cut alongside `@adia-ai/web-modules@0.4.0` (ADR-0024 legacy shell shapes retired). Source byte-identical to v0.3.6.
+
+Internal `@adia-ai/*` dep ranges bumped from `^0.3.0` to `^0.4.0`. See root [CHANGELOG.md `## [0.4.0]`](../../../CHANGELOG.md) for the cut narrative.
+## [0.3.6] - 2026-05-10
+
+### Ride-along (no source changes)
+
+Lockstep version bump only — source byte-identical to v0.3.5. Internal `@adia-ai/*` dep ranges remain at `^0.3.0`. See root [CHANGELOG.md `## [0.3.6]`](../../../CHANGELOG.md) for the cut narrative.
+## [0.3.5] - 2026-05-07
+
+### Ride-along (no source changes)
+
+Lockstep version bump only — source byte-identical to v0.3.4. Internal `@adia-ai/*` dep ranges remain at `^0.3.0`. See root [CHANGELOG.md `## [0.3.5]`](../../../CHANGELOG.md) for the cut narrative.
+## [0.3.4] - 2026-05-07
+
+### Ride-along (no source changes)
+
+Lockstep version bump only — source byte-identical to v0.3.3. Internal `@adia-ai/*` dep ranges remain at `^0.3.0`. See root [CHANGELOG.md `## [0.3.4]`](../../../CHANGELOG.md) for the cut narrative.
+## [0.3.3] - 2026-05-07
+
+**Lockstep cut.** All 9 published `@adia-ai/*` packages now share version `0.3.3`, governed by [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy). Internal `@adia-ai/*` ranges stay at `^0.3.0` (patch-cut asymmetry — caret floats `0.3.x`).
+
+### Added
+
+- **`iteration-synthesis-failure` auto-fire policy reason** in
+  `strategies/zettel/issue-reporter.js`. Generator-adapter's
+  iteration synthesis failures now route through
+  `autoReport('iteration-synthesis-failure', ...)` instead of bare
+  `console.error`. Suppressed in eval mode; emits to
+  `.brain/audit-history/issues/` in production. (closes backlog #49)
+
+- **`ID_PREFIX_SEPARATOR` exported constant** in
+  `strategies/zettel/composer.js` — the magic string `'--'` used
+  when prefixing fragment internal node ids with composition node
+  id. Documented choice rationale (double-dash chosen because single
+  `-` collides with kebab-case ids in primitives). (closes backlog #50)
+
+- **`computeScopeDrift` + `SCOPE_DRIFT_RATIO` + `SCOPE_DRIFT_MIN_ACTUAL`
+  exports** in `strategies/zettel/chunk-synthesizer.js`. Internal
+  function + constants are now exported for testability. New
+  `chunk-synthesizer.test.js` (8/8 pass) covers no-drift,
+  ratio-below-gate, drift-fires, floor-prevents-false-positive,
+  malformed-corpus zero-expected guard, multi-chunk aggregation,
+  instances[]-shape support, exports. (closes backlog #52)
+
+- **`A2UI_COMPOSE_TRACE` env-var support** in `core/generator.js`.
+  When set to a directory path, writes a per-request JSON trace
+  (full `_debug` payload + result) per `generateUI()` call, named
+  `<ISO-timestamp>--<intent-slug>.json`. `dialog-recorder.isRecording()`
+  honors the trace var so `_debug` payload is populated. New
+  `npm run compose:trace` script. (closes backlog #89)
+
+### Changed
+
+- **Cache-invalidation contract** documented inline in
+  `strategies/zettel/generator-adapter.js`. `loadAll()` itself is
+  idempotent (`fragments.clear()` + `compositions.clear()` + re-walk
+  on every call). The CACHING happens at the call-site:
+  `ensureBooted()` sets a process-singleton flag and never reloads
+  for the lifetime of the process. Trade-offs: good for long-running
+  MCP, bad for tests/hot-reload. To force a reload, call `loadAll()`
+  directly. (closes backlog #100)
+## [0.3.2] - 2026-05-06
+
+**9-package lockstep patch cut to v0.3.2.** All lockstep members share
+one version per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy).
+Internal `@adia-ai/*` dep ranges unchanged at `^0.3.0`.
+
+### Added
+
+- **`chunk-zettel` engine** — registered as 5th built-in engine in
+  `strategies/registry.js`. Chunk-aware composition from training-chunk
+  corpus (page shells + block chunks). Fast path: sync keyword search
+  over async embeddings to prevent ranking drift.
+
+### Fixed
+
+- **Keyword-first fast path** — `composeFromIntent` prefers sync
+  `searchChunks` over `searchChunksAsync` (embeddings) for retrieval.
+- **Whole-word keyword matching** — `keywordScore()` splits chunk names
+  on `[-_]` and uses `nameWords.includes(tok)`; prevents `"pane"` from
+  matching `"panel"`.
+- **Coverage scoring** — PascalCase → kebab-case regex fix for
+  multi-word components (`AgentTrace` → `agent-trace-ui`).
+
+### Changed
+
+- `version`: `0.3.1` → `0.3.2`.
+## [0.3.1] - 2026-05-06
+
+**9-package lockstep patch cut.** All 9 published `@adia-ai/*` packages bump 0.3.0 → 0.3.1 per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy). Internal `@adia-ai/*` dep ranges remain at `^0.3.0` (covers `0.3.1` under semver — patch-cut asymmetry).
+
+This package itself ships **no source changes** in v0.3.1. The cut bumps version only — substantive content lives in [`@adia-ai/web-components`](https://github.com/adiahealth/gen-ui-kit/releases/tag/web-components-v0.3.1) (folder-per-trait restructure; barrel API unchanged).
+
+### Changed
+
+- `version`: `0.3.0` → `0.3.1`.
+- Internal `@adia-ai/*` dep ranges: unchanged at `^0.3.0` (covers `0.3.1` under semver — patch-cut asymmetry).
+## [0.3.0] - 2026-05-05
+
+**9-package lockstep cut + LLM subpath dropped.** All 9 published `@adia-ai/*` packages bump 0.2.5 → 0.3.0 per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy). Internal `@adia-ai/*` dep ranges bump `^0.2.0` → `^0.3.0`.
+
+This is a **minor cut on top of v0.2.5 with one BREAKING change**: the `./llm` subpath export is removed. The LLM adapters that previously shipped under `@adia-ai/a2ui-compose/llm` now ship as their own package, `@adia-ai/llm` (9th lockstep member, first publish in this cut).
+
+### Removed
+
+- **`./llm` subpath export.** The package no longer re-exports the LLM
+  adapters or bridge. Migrate to `@adia-ai/llm`:
+
+  ```diff
+  - import { streamChat } from '@adia-ai/a2ui-compose/llm/adapters/index.js';
+  + import { streamChat } from '@adia-ai/llm';
+
+  - import { createAdapter } from '@adia-ai/a2ui-compose/llm/llm-bridge.js';
+  + import { createAdapter } from '@adia-ai/llm/bridge';
+  ```
+
+  See `@adia-ai/llm@0.3.0` CHANGELOG for the full migration narrative.
+
+### Changed
+
+- `dependencies["@adia-ai/llm"]`: NEW, `^0.3.0`. The compose engines'
+  internal LLM use now resolves through the new package.
+- `dependencies["@adia-ai/a2ui-utils"]` removed (renamed to `a2ui-runtime`); replaced by `dependencies["@adia-ai/a2ui-runtime"]: ^0.3.0`.
+- All other internal `@adia-ai/*` dep ranges: `^0.2.0` → `^0.3.0`.
+- `version`: `0.2.5` → `0.3.0`.
+- Source paths internal to compose that referenced `./llm/` updated to
+  `../../../llm/` (e.g. `core/generator.js` imports `StubLLMAdapter`
+  from the new package location).
+- `transpiler/transpiler-maps.js`: `@adia-ai/a2ui-utils` import → `@adia-ai/a2ui-runtime` (matches the package rename — see runtime's CHANGELOG).
+
+### Migration
+
+```diff
+{
+  "dependencies": {
+    "@adia-ai/a2ui-compose": "^0.3.0",
++   "@adia-ai/llm": "^0.3.0"
+  }
+}
+```
+
+Plus rewrite imports as shown above. The change is mechanical.
+## [0.2.5] - 2026-05-04
+
+**8-package lockstep cut.** All 8 published `@adia-ai/*` packages bump 0.2.4 → 0.2.5 per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy). Internal `@adia-ai/*` dep ranges remain at `^0.2.0` (covers 0.2.5 under semver — patch-cut asymmetry).
+
+This is a **patch cut on top of v0.2.4, no BREAKING changes.** Substantive content lives in `web-components` (new `<fields-ui>` form-grid primitive + `draggable-list-item` last-item drop-zone fix, both surfaced by the Tasks UI Playground at `.claude/docs/projects/tasks-playground/`); `a2ui-corpus` ships a catalog regen for the new `<fields-ui>` yaml. `a2ui-compose` rides along at version bump only — no source change.
+
+### Changed
+
+- `version`: `0.2.4` → `0.2.5`.
+- Internal `@adia-ai/*` dep ranges: unchanged at `^0.2.0` (covers `0.2.5` under semver — patch-cut asymmetry).
+## [0.2.4] - 2026-05-04
+
+**8-package lockstep cut.** All 8 published `@adia-ai/*` packages bump 0.2.3 → 0.2.4 per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy). Internal `@adia-ai/*` dep ranges remain at `^0.2.0` (covers 0.2.4 under semver — patch-cut asymmetry).
+
+This is a **patch cut on top of v0.2.3, no BREAKING changes.** Substantive content lives in `web-components` (Tier 4 trait library lift, 11 new traits + 2 architectural rewrites, plus accumulated bug fixes); `a2ui-corpus` ships a catalog regen for the new `<demo-toggle-ui>` primitive. Six packages ride along at version + dep-range bump.
+
+### Changed
+
+- `version`: `0.2.3` → `0.2.4`.
+- `dependencies["@adia-ai/a2ui-utils"]`: `^0.2.0` (covers `0.2.4`).
+
+This package's source tree is byte-identical to 0.2.3. The cut bumps version + the internal dep range only, per the lockstep policy.
+
+_Nothing yet._
+
+---
+
+---
+## [0.2.3] - 2026-05-04
+
+**Lockstep cut.** All 8 published `@adia-ai/*` packages bump
+0.2.2 → 0.2.3 per
+[`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy).
+Patch cut — no breaking changes.
+
+### Changed
+
+- `version`: `0.2.2` → `0.2.3`.
+- `dependencies["@adia-ai/a2ui-corpus"]`: `^0.2.0` (covers `0.2.3`).
+- `dependencies["@adia-ai/a2ui-retrieval"]`: `^0.2.0` (covers `0.2.3`).
+- `dependencies["@adia-ai/a2ui-validator"]`: `^0.2.0` (covers `0.2.3`).
+
+### No source changes
+
+`@adia-ai/a2ui-compose` source is byte-identical to `0.2.2`. The cut bumps version + the internal dep range entries only.
+## [0.2.2] - 2026-05-02
+
+**Lockstep cut + reasoning-panel emission fixes.** All 8 published `@adia-ai/*` packages bump 0.2.1 → 0.2.2 per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy). Patch cut — no breaking changes.
+
+### Changed
+
+- `version`: `0.2.1` → `0.2.2`.
+- `dependencies["@adia-ai/a2ui-corpus"]`: `^0.2.0` (covers `0.2.2`).
+- `dependencies["@adia-ai/a2ui-utils"]`: `^0.2.0` (covers `0.2.2`).
+- `dependencies["@adia-ai/a2ui-validator"]`: `^0.2.0` (covers `0.2.2`).
+- `dependencies["@adia-ai/a2ui-retrieval"]`: `^0.2.0` (covers `0.2.2`).
+- `core/generator.js` and `strategies/` are the surfaces that gained the new behavior below; no other compose directories touched.
+
+### Fixed — Reasoning-panel emissions surface confidence + retrieval candidates (2026-05-02)
+
+`generator.js` was emitting `status` events whose labels looked truthful but hid the data needed to judge their reliability. Two fixes that surface the missing data as `outcomes`:
+
+- **Interpret stage** now includes the domain confidence percentage and the matched signals. Previously `Domain: data` read identical at 3% confidence vs 95% — same label. Now: `Domain: data (3% confidence)` plus `Matched signals: pricing` as outcomes. Per memory `feedback_panel_label_reliability.md`.
+- **Analyze stage** runs a fast keyword `searchBlocks(intent)` and emits the top-5 candidates with scores + domains. Previously the stage reported `context.patterns.length` from `getContext(intent, 2)` — but the context-assembler only populates `result.patterns` at tier ≥ 3, so the count was structurally guaranteed to be 0. The label read "nothing relevant" when it actually meant "we didn't even look here." The fix runs a real retrieval at the analyze stage instead of relying on the wrong-tier context.
+
+Companion fix in `@adia-ai/a2ui-retrieval` Unreleased (web-research.js EXPLICIT/IMPLICIT pattern split). Both surfaces feed the same reasoning-panel deception class — five distinct bugs caught + fixed in commit `9986c71e`.
+
+---
+## [0.2.1] - 2026-05-02
+
+**Lockstep cut + scope-drift gate at composer time + skeleton harvest + Tier-1 block filter + high-resolution session ticket trace.** All 8 published `@adia-ai/*` packages bump 0.2.0 → 0.2.1 per [`.claude/docs/specs/package-architecture.md` § 15](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy). Patch cut — no breaking changes.
+
+### Changed
+
+- `version`: `0.2.0` → `0.2.1`.
+- `dependencies["@adia-ai/a2ui-corpus"]`: `^0.2.0` (covers `0.2.1`).
+- `dependencies["@adia-ai/a2ui-utils"]`: `^0.2.0` (covers `0.2.1`).
+- `dependencies["@adia-ai/a2ui-validator"]`: `^0.2.0` (covers `0.2.1`).
+- `dependencies["@adia-ai/a2ui-retrieval"]`: `^0.2.0` (covers `0.2.1`).
+- `strategies/zettel/chunk-synthesizer.js` and `strategies/zettel/issue-reporter.js` are the surfaces that gained the new behavior below; no other directories under `strategies/` were touched.
+
+### Added — Scope-drift gate at composer time (2026-05-02)
+
+`composeFromIntent` now computes a scope-drift signal after every successful composition: composed-HTML component count vs. the sum of bound chunks' component counts. When `actual / expected > 1.5×` (with a 20-component floor to suppress small-UI noise), the synthesizer emits a warning with the ratio. The MCP layer auto-fires a `scope-drift` issue on detection, which writes both a JSON ticket and a high-resolution Markdown ticket showing the bound-chunk envelope, ratio, and a callout naming the canvas-drift regression class.
+
+- `chunk-synthesizer.js`: `computeScopeDrift(html, boundChunks)`, `SCOPE_DRIFT_RATIO = 1.5`, `SCOPE_DRIFT_MIN_ACTUAL = 20`. Tier-1 (single bound block) and Tier-2 (page chunk + every block resolved into a slot) both instrumented.
+- `issue-reporter.js`: new `'scope-drift'` reason in `AUTO_FIRE_POLICY` (type `bug`, severity `drift`, owner `synthesis`); `scopeDrift` flowed into the trace; ticket renderer extended with envelope + ratio + drift callout.
+
+Closes the loop on the canvas-drift regression class — the §37 fix patched the immediate symptom (84 components for a 4-stat retrieval), this trip-wire makes the class self-detecting.
+
+### Added — Skeleton harvest + Tier-1 block filter (2026-05-02)
+
+Two coordinated changes to the chunk-corpus pipeline that bound the synthesizer's output envelope.
+
+- **Skeleton harvest for nested chunks.** `harvest-chunks.mjs` now collapses each nested `data-chunk` element's inner content to `<!-- nested: <name> -->`, so page/panel chunks become compact skeletons. `dashboard-admin-page` shrank from 26,555c → 1,522c (-94%); `dashboard-overview-panel` from 12,493c → 898c (-93%); xl-bucket chunks (>10K chars) went from 2 → 0.
+- **Tier-1 retrieval `kind: 'block'` filter.** `composeFromIntent` restricts the fast-path retrieval to block-kind chunks; page/panel composition still works via Tier-2 LLM synthesis with slot-binding, where the skeleton is the right input.
+
+End-to-end: "trace documentation UI with stat cards" now produces 4 components (was 84). "kpi dashboard with stat cards" → 13 components. The retrieved chunk's component count is now an upper bound on the Tier-1 fast-path output.
+
+### Added — High-resolution session ticket trace (2026-05-02)
+
+The synthesizer now captures a `retrievalTrace` per attempt: Tier-1 hits with scores + kinds, Tier-2 catalog summary (page/panel/block counts, top-N block candidates), user-prompt char count, system-prompt hash, attempt-by-attempt LLM raw responses, validation results, plan, and HTML preview. The state cache stores it on every entry. `attachTrace('full')` (now the default when `state_id` is provided) returns the full session-replay payload.
+
+`issue-reporter.js` renders this as a sibling Markdown ticket alongside the JSON; sections cover header, description, reproduction, component count, retrieval log table, LLM attempts (raw responses), user prompt, composer plan, generated HTML preview, warnings, ops history, environment. A maintainer can replay any flagged session from the ticket alone.
+
+---
+## [0.2.0] - 2026-05-02
+
+**Lockstep cut + boundary cleanup.** All 8 published `@adia-ai/*`
+packages now share one version, governed by
+[`.claude/docs/specs/package-architecture.md` § 15 (Versioning Policy)](../../../.claude/docs/specs/package-architecture.md#15-versioning-policy).
+This release also lands the `engine/` ↔ `engines/` collision fix from
+T3 of the
+`.claude/docs/plans/packages-architecture-fixes-2026-05-02.md`
+plan.
+
+### Changed
+
+- `version`: `0.1.0` → `0.2.0`.
+- `dependencies["@adia-ai/a2ui-utils"]`: `^0.0.2` → `^0.2.0`.
+- `dependencies["@adia-ai/a2ui-retrieval"]`: `^0.0.1` → `^0.2.0`.
+- `dependencies["@adia-ai/a2ui-validator"]`: `^0.0.1` → `^0.2.0`.
+
+- **Directory renames — `engine/` → `core/`, `engines/` → `strategies/`**
+  to remove the singular/plural collision that read as a typo. The
+  orchestrator (`generator.js`, `state.js`, `context-store.js`,
+  `artifacts.js`, `pattern-export.js`, `reference.js`, `pipeline/`) now
+  lives at `core/`; the pluggable strategies (`monolithic/`, `zettel/`,
+  `registry.js`) live at `strategies/`. The `transpiler/` directory's
+  internal imports were also rewritten by the same sweep (no behavior
+  change). All internal imports updated in one sweep.
+- **`constitution.md` moved out of the package source** to
+  [`.claude/docs/specs/compose-constitution.md`](../../../.claude/docs/specs/compose-constitution.md)
+  so it doesn't ship in the published tarball. Pointer added in
+  README.
+- **`package.json` `exports` map updated** with new keys (`./core`,
+  `./strategies/registry`, `./strategies/zettel`); old keys
+  (`./engine`, `./engines/registry`, `./engines/zettel`) retained as
+  aliases for one release cycle and removed in the next major.
+- Spec [`.claude/docs/specs/package-architecture.md`](../../../.claude/docs/specs/package-architecture.md)
+  bumped 0.5.0 → 0.6.0 with the directory tree updated to reflect the
+  new layout; new § 15 documents the lockstep versioning policy.
+
+### Migration
+
+Consumers importing from the old paths still work for one release
+cycle, but should update on next touch:
+
+```diff
+- import { generateUI } from '@adia-ai/a2ui-compose/engine';
++ import { generateUI } from '@adia-ai/a2ui-compose/core';
+
+- import { pick, registerEngine } from '@adia-ai/a2ui-compose/engines/registry';
++ import { pick, registerEngine } from '@adia-ai/a2ui-compose/strategies/registry';
+
+- import { generateZettel } from '@adia-ai/a2ui-compose/engines/zettel';
++ import { generateZettel } from '@adia-ai/a2ui-compose/strategies/zettel';
+```
+
+---
+## [0.1.0] - 2026-04-28
+
+**Multi-turn refinement engine (Phase A).** Adds three new modules to the
+zettel engine that turn `compose_from_chunks` from single-shot into a
+multi-turn surface, plus a first-class telemetry surface that auto-fires
+issue tickets on engine failure paths.
+
+Spec: [`.claude/docs/specs/genui-multiturn-architecture.md`](../../../.claude/docs/specs/genui-multiturn-architecture.md) (Active v0.1.0).
+Plan: `.claude/docs/plans/genui-multiturn-rollout-2026-04-28.md` (Phase A scoped).
+ADR: `0008-multiturn-genui-architecture.md`.
+
+### Added (engine modules)
+
+- **`engines/zettel/state-cache.js`** — bounded LRU cache for multi-turn
+  compositions (default 64 entries; configurable via
+  `A2UI_STATE_CACHE_SIZE`). API: `set / get / peek / has / evict / list /
+  size / clear`. State-id minting helpers `mintStateId(intent, version)`
+  and `mintNextStateId(parent, version)` produce stems of the form
+  `<intent-prefix>-<rand4>-v<N>-<unix-min>` so refinement chains keep a
+  visible lineage. Module-level singleton via `getStateCache() /
+  resetStateCache()`. Pure data structure; no I/O, no async.
+- **`engines/zettel/issue-reporter.js`** — first-class telemetry surface.
+  `reportIssue(input, ctx)` writes immutable JSON to
+  `.brain/audit-history/issues/<issue_id>.json` (matches the existing
+  audit-ledger convention). `autoReport(reason, autoCtx, ctx)` looks up
+  a 6-row policy table for engine-side auto-fires (`synthesizer-exhausted`,
+  `validator-exhausted`, `locator-empty-targets`,
+  `retrieval-zero-then-synthesis-fail`, `cache-miss-on-known-state`,
+  `ops-failed-after-apply`) and threads severity / type / suggested-owner
+  defaults. `attachTrace(state_id, depth, cache)` pulls from the
+  state-cache via `peek` (no recency disturbance). Sidecar trace files
+  for traces > 200 KB. Three reporter kinds: `auto | user | llm`.
+  `evalMode: true` in ctx suppresses auto-fire (manual `reportIssue`
+  calls still write). Per-tool-call `IssueAccumulator` coalesces
+  multiple auto-fires into a single issue with the highest-severity
+  policy as primary; reasons listed in body + tags.
+- **`engines/zettel/chunk-refiner.js`** — sibling to `chunk-synthesizer.js`.
+  Two-pass synthesis (locator → modifier) for refinement intents.
+  `refineFromIntent({ priorState, intent, llmAdapter, maxAttempts,
+  issueAccumulator, catalog })` runs a locator pass to identify which
+  slots to modify, then a modifier pass to emit chunk-plan ops on the
+  targeted slice. Validator-driven retry loop with feedback-on-error
+  (default `maxAttempts: 2`, mirrors `chunk-synthesizer`). `validateOps`
+  checks op shape, slot references, chunk references, page-kind
+  contracts. `applyOps({ priorState, ops })` mutates a deep-cloned
+  plan and re-materializes HTML via `composeFromPlan`. `opsToA2UI(ops,
+  newState)` translates chunk-plan ops to wire-format `updateComponents`
+  A2UI messages (Phase A simplification: `components[].html` carries
+  the materialized payload; Phase B will upgrade to component-tree shape).
+
+### Phase A op format
+
+Internal: `rebindSlot | appendToSlot | removeFromSlot | replacePage`.
+Wire: standard `updateComponents` messages targeting `slot-<name>` ids
+(or `main` for `replacePage`). Documented as a Phase A simplification —
+the chunk pipeline emits HTML, so the wire-format wrapper is intentionally
+thin until Phase B introduces typed component-tree refinements.
+
+### Smoke + eval
+
+- `npm run smoke:state-cache` — 34/34 (LRU recency, peek, env-driven sizing,
+  state-id minting + chain).
+- `npm run smoke:issues` — 62/62 (write, validation, trace attach, sidecar
+  spill, auto-fire policy lookup, evalMode suppression, coalescing).
+- `npm run smoke:refine` — 51/51 (validateOps, applyOps × 4 op types,
+  opsToA2UI, two-pass with stub LLM, retries, exhaustion auto-fire,
+  end-to-end refine → apply → wire).
+- **`npm run eval:refine-synthesis`** — **15/15 PASS** real-LLM eval.
+  Ops rate 100%, validate rate 100%, 0 auto-fires, 67 s. All 15
+  refinements completed on the first attempt.
+
+### Out of scope (Phase B / C)
+
+- Persistent state across server restarts (filesystem-JSON-backed cache at `.brain/state-cache/`; mirrors the existing audit-ledger convention; design in plan §2).
+- Branching / version trees.
+- LLM-streamed op emission.
+- Multi-user concurrent refinement (CRDT / OT).
+- A2UI `updateDataModel` + `wireComponents` synthesis (current scope is
+  `updateComponents` + `deleteSurface` only).
+
+### Migration
+
+Additive surface; no breaking changes. Existing consumers calling
+`composeFromIntent` continue to work unchanged.
+
+---
+## [0.0.1] - 2026-04-24
+
+First public release. Framework-agnostic compose engine for the
+A2UI protocol: takes natural-language intents + a catalog and
+produces A2UI protocol messages. Two generation strategies ship
+behind a plug-in engine registry.
+
+### Included
+
+- **Monolithic engine** (`engine/generator.js`) — single-call
+  generator with `instant` / `pro` / `thinking` modes. Anthropic
+  and OpenAI LLM adapters included. Pattern-match-only `instant`
+  mode for deterministic output; `pro` + `thinking` call the LLM.
+- **Zettel engine** (`engines/zettel/`) — fragment-graph composition
+  strategy that assembles UI from reusable fragments + compositions
+  via a backlink graph. Framework-agnostic; driven by the same
+  intent-gate + domain-router as monolithic.
+- **Engine registry** (`engines/registry.js`) — plug-in API.
+  `registerEngine(name, fn)` + `pick(name)` dispatcher;
+  reserved names for built-ins.
+- **LLM bridge** (`llm/llm-bridge.js`) — unified interface over
+  Anthropic, OpenAI, and Gemini adapters. Streaming + non-streaming
+  calls; prompt-cache support for Anthropic.
+- **Transpiler** (`transpiler/transpiler.js`) — A2UI JSON → HTML
+  rendering; used by MCP tools and the visual-validate pipeline.
+- **Evals harness** (`evals/harness.mjs`) — V2 cross-engine eval
+  runner. Consumed by `eval-diff.mjs` in `@adia-ai/a2ui-mcp`.
+- **Index barrel** (`index.js`) — re-exports `generateUI`,
+  `generateUIStream`, `pick`, `listEngines`, `registerEngine`,
+  `unregisterEngine`, `ENGINES` for one-import consumer surface.
+
+### Dependencies
+
+- `@adia-ai/a2ui-utils` ^0.0.2 — A2UI runtime primitives.
+- `@adia-ai/a2ui-retrieval` ^0.0.1 — retrieval layer.
+- `@adia-ai/a2ui-validator` ^0.0.1 — validation layer.
+
+---
+
+## Pre-0.0.1 history
+
+### Changed
+- **A2UI runtime dependency relocated.** `retrieval/catalog.js`,
+  `transpiler/transpiler-maps.js`, and `validation/validator.js` now
+  import `registry` and `wiringRegistry` from the new published package
+  `@adia-ai/a2ui-utils` instead of `../../web-components/a2ui/`
+  (which no longer exists — the runtime moved out of web-components in
+  `@adia-ai/web-components@0.0.4`). The scoped import is resolved via
+  the workspace symlink in dev and the transitive dependency in
+  published installs.
+- `retrieval/anti-patterns.js` — `noInventedComponents` regex broadened from `/<([a-z]+-n)\b/` to `/<([a-z]+-(?:n|ui))\b/` so the check actually fires against the current `-ui` codebase. Allowlist aligned with canonical registry.
+- `transpiler/transpiler.js` and `transpiler/transpiler-maps.js` — stale `-n` tag references updated to `-ui` forms consistent with `packages/web-components/a2ui/registry.js`.
+- `retrieval/catalog.js`, `retrieval/synthetic-data.js`, `engines/monolithic/_shared.js` — internal tag references audited and aligned with the canonical registry.
+
+### Fixed
+- Stale internal-identifier references in comments + doc strings swept to the current naming.
+
+---
+## [0.1.0] — internal baseline (unreleased)
+
+Initial version at the time the monorepo was established. Contains:
+
+- **Monolithic engine** — single-call generator with instant / pro / thinking modes (Anthropic, OpenAI adapters).
+- **Zettel engine** — fragment-graph composition engine using leverage-ranked fragments from the training corpus.
+- **Retrieval layer** — keyword + concept-tag + component-signature scoring. Dialog recorder writes per-turn JSON to `logs/dialogs/`.
+- **Validator** — 15-check weighted schema validator; rejects `_fallback: true` surfaces as score 0.
+- **Prompt caching** — enabled on Anthropic calls as of 2026-04-19.
+
+Package name still uses the legacy `@adia-ai/a2ui-compose` scope pending rename (see root CHANGELOG for context).