@adia-ai/gen-ui 0.8.52 → 0.8.54

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog — @adia-ai/gen-ui
 
+## [0.8.54] — 2026-08-27
+
+### Changed
+- **`corpus/` re-harvested for the release window** — `_source-hashes.json` regenerated
+  against source drift in `@adia-ai/web-components` (`drilldown.examples.html`, the
+  `slot="chevron"`→`slot="caret"` migration, gh#1977) and site content (`admin-shell.html`,
+  `cdn-usage.html`, three new guide pages — `bundle-loading.html`, `bundle-sizes.html`,
+  `css-architecture.html` — and `patterns/index.html`). No chunk content changed, hashes
+  only; `chunks/_index.json` and `manifest.json` are unchanged.
+
+## [0.8.53] — 2026-08-26
+
+### Fixed
+- **`compose/transpiler/transpiler-maps.js`'s `ALIAS_TYPES` set corrected — dropped the stale `'SegmentedControl'` alias (gh#2116).** That entry let a pre-0.8.43 component name squat on `Segmented`'s reverse-mapping slot in the HTML-harvest lookup, causing 22 corpus chunks to reference a catalog type the current catalog never declares. Fixing the mapping (rather than hand-editing each chunk, which the harvester would silently overwrite on the next `build:components` run) also surfaced and required fixing 4 downstream call sites that still emitted the retired literal: `apps/genui/app/patient-visit/surfaces.js` (a real application surface builder — `CATALOG_UNKNOWN_COMPONENT_TYPE` broke `validateFinal` for two builders), its own test file, `packages/genui/adia-catalog/composition-constraints.test.js`, and `apps/genui/app/patient-visit/verbs.test.js`. Also corrected an LLM generation prompt in `compose/strategies/monolithic/_shared.js` ("Toggle → SegmentedControl") that would have steered the model toward generating now-invalid envelopes.
+
+### Changed
+- **`corpus/` re-harvested for the release window** — 22 chunks' `SegmentedControl` references corrected to `Segmented` (gh#2116); chunks regenerated against the ~70 primitive docs+catalog fixes shipped in `@adia-ai/web-components` (gh#2032); `chunks/_index.json`, `_source-hashes.json`, `manifest.json` regenerated.
+
 ## [0.8.52] — 2026-08-25
 
 ### Changed

package/compose/strategies/monolithic/_shared.js

@@ -1075,7 +1075,7 @@ Instructions:
 - Change text content, labels, icons to match the new intent
 - Preserve slot attributes and Card anatomy rules
 - CRITICAL: Preserve layout container types — do NOT change Grid to Column or Row to Column. If the canvas has a Grid with columns="3" for a card collection, keep it as Grid. Only change layout types when the user explicitly requests a layout change.
-- CONTENT CARRY-OVER on component swaps: when the user asks to upgrade a component to a richer variant (e.g. Image → Carousel, Text → Stat, Toggle → SegmentedControl, Input → Select), the original's content props (src, alt, textContent, text, value, label, name) MUST be carried into the equivalent prop on the new component. The original src becomes the first slide of a Carousel; the original textContent becomes the first item; the original value becomes the default. NEVER emit a swapped component with placeholder/lorem content when real content was present in the original.
+- CONTENT CARRY-OVER on component swaps: when the user asks to upgrade a component to a richer variant (e.g. Image → Carousel, Text → Stat, Toggle → Segmented, Input → Select), the original's content props (src, alt, textContent, text, value, label, name) MUST be carried into the equivalent prop on the new component. The original src becomes the first slide of a Carousel; the original textContent becomes the first item; the original value becomes the default. NEVER emit a swapped component with placeholder/lorem content when real content was present in the original.
 - You MUST return the COMPLETE component array including all existing components plus your modifications
 - Generate at least ${priorComponents.length} components (the existing ones plus any additions)
 - SCOPE GUARD: Only add sections/components that the user explicitly requested. Do NOT speculatively add features, panels, or sections not mentioned in the intent. If adding more than 3 new top-level sections, reconsider whether the user actually asked for them.
@@ -1093,7 +1093,7 @@ CRITICAL PRESERVATION RULES:
 - NEVER change layout container types (Grid→Column, Row→Column, Grid→Row) unless the user explicitly asks to change the layout structure.
 - If a Grid has columns="3", keep it as Grid with columns="3". Adding a toggle/filter/button to a toolbar does NOT change the content layout below.
 - Preserve parent-child relationships — adding a control to a toolbar row doesn't affect sibling containers.
-- CONTENT CARRY-OVER on component swaps: when upgrading a component to a richer variant (Image→Carousel, Text→Stat, Toggle→SegmentedControl, Input→Select), the original's content props (src, alt, textContent, text, value, label, name) MUST flow into the equivalent prop on the new component (or become its first item, where applicable). NEVER emit a swapped component with placeholder content when real content was present.
+- CONTENT CARRY-OVER on component swaps: when upgrading a component to a richer variant (Image→Carousel, Text→Stat, Toggle→Segmented, Input→Select), the original's content props (src, alt, textContent, text, value, label, name) MUST flow into the equivalent prop on the new component (or become its first item, where applicable). NEVER emit a swapped component with placeholder content when real content was present.
 
 DIFF FORMAT:
 - To ADD a new component: include the full component JSON object (with a new unique id)

package/compose/transpiler/transpiler-maps.js

@@ -244,7 +244,24 @@ function extractCatalogProps(el, a2uiType) {
 
 const ALIAS_TYPES = new Set([
   'Select', 'LoadingIndicator', 'ErrorContainer', 'Keyboard',
-  'DatePicker', 'CommandPalette', 'Segmented', 'OTP', 'SideNav', 'IconSource',
+  'DatePicker', 'CommandPalette', 'SegmentedControl', 'OTP', 'SideNav', 'IconSource',
+  // 'SegmentedControl' (not 'Segmented') — registry.js lists the deprecated
+  // pre-0.8.43 alias `['SegmentedControl', 'segmented-ui']` BEFORE the
+  // canonical `['Segmented', 'segmented-ui']` entry; first-write-wins let
+  // the deprecated alias claim the reverse-registry slot, so the harvester
+  // emitted `"component": "SegmentedControl"` (not a real catalog
+  // component — catalog only defines `Segmented`, with `SegmentedControl`
+  // as a tag synonym) for every harvested chunk composing <segmented-ui>
+  // directly (gh#2116 — 22 corrupted corpus chunks). Forward resolution
+  // (`resolveTag('SegmentedControl')`) is untouched — this only reorders
+  // which type wins the REVERSE (tag → canonical type) lookup, same
+  // mechanism already used for 'Select'/'search-ui' above.
+  // 'segmented-control-ui' — same class of bug, same tag: registry.js's
+  // "AgentUI Aliases" block ALSO self-references the old tag name
+  // (`['segmented-control-ui', 'segmented-ui']`) ahead of the canonical
+  // `['Segmented', 'segmented-ui']` entry — excluding 'SegmentedControl'
+  // alone only uncovers this second squatter on the same tag.
+  'segmented-control-ui',
   // 'search-ui' — registry.js's "AgentUI Aliases (backwards compat with
   // -ui tags)" block registers the tag name itself as a self-referencing
   // type (`['search-ui', 'search-ui']`) ahead of the real canonical