@adia-ai/gen-ui 0.8.42 → 0.8.44

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog — @adia-ai/gen-ui
 
+## [0.8.44] — 2026-08-20
+
+### Maintenance
+- **Corpus re-harvested after gh#1669's corpus dead-attribute sweep** (111 findings across 46 source files fixed at SOURCE in `@adia-ai/web-components`; see that package's CHANGELOG). `harvest-chunks.mjs`'s unknown-attribute gate promoted from advisory to blocking-by-default now that the known findings are zero. No engine API change.
+
+## [0.8.43] — 2026-08-18
+
+### Changed
+- **Transpiler + retrieval `ColorPicker` references swapped to `ColorArea` (gh#1617).** `compose/transpiler/transpiler-maps.js`'s `type="color"` HTML→A2UI mapping, `compose/transpiler/transpiler.js`'s leaf-type set, and `retrieval/domain-router.js`'s forms-domain component list now emit `ColorArea` — `ColorPicker`/`color-picker-ui` was cut from `@adia-ai/web-components` in the same release. `compose/strategies/monolithic/_shared.js`'s content-carry-over prompt example (`Toggle → ToggleGroup`) swapped to `Toggle → SegmentedControl` for the same reason (`ToggleGroup` was cut).
+
+### Maintenance
+- **`corpus/` touched in this release window** (27 file(s), e.g. `corpus/chunk-embeddings.json`) — carried by the entries above.
+
 ## [0.8.42] — 2026-08-17
 
 ### Maintenance

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 → ToggleGroup, 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 → 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.
 - 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→ToggleGroup, 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→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.
 
 DIFF FORMAT:
 - To ADD a new component: include the full component JSON object (with a new unique id)

package/compose/transpiler/transpiler-maps.js

@@ -373,7 +373,7 @@ export const INPUT_TYPE_MAP = {
   time:              { type: 'DateTimeInput' },
   'datetime-local':  { type: 'DateTimeInput' },
   file:              { type: 'Upload' },
-  color:             { type: 'ColorPicker' },
+  color:             { type: 'ColorArea' },
   submit:            { type: 'Button', props: { variant: 'primary', type: 'submit' } },
   reset:             { type: 'Button', props: { variant: 'outline', type: 'reset' } },
 };

package/compose/transpiler/transpiler.js

@@ -242,7 +242,7 @@ function walkNode(el, context) {
   const LEAF_TYPES = new Set([
     'Text', 'Button', 'Kbd', 'Code', 'Badge', 'Tag', 'Image', 'Divider',
     'TextField', 'CheckBox', 'Toggle', 'Radio', 'Slider', 'Search',
-    'Upload', 'ColorPicker', 'DateTimeInput', 'TextArea', 'OtpInput',
+    'Upload', 'ColorArea', 'DateTimeInput', 'TextArea', 'OtpInput',
   ]);
 
   if (LEAF_TYPES.has(a2uiType)) {