@adia-ai/web-components 0.8.40 → 0.8.42

package/CHANGELOG.md

@@ -1,13 +1,81 @@
 # Changelog — @adia-ai/web-components
 
+## [0.8.42] — 2026-08-17
+
+### Added
+- **ADR-0063 `0.8.42` compat shims (gh#1562 wave, PR #1569).** Dual-read/alias shims easing the planned 0.9.0 renames: chart `no-*` boolean axes, `chart-legend-ui[interactive]`, `pane-ui[edge]`, the `color-area-ui` alias, and `menu-item-ui[description]`. Old names keep working this cut; the breaking removals ride 0.9.0 per the migration guide.
+- **Rename-wave W1 compat shims (gh#1560, PR #1565).** `data-sidebar-resize` / `data-layout-grid` are dual-read alongside the legacy `data-resize` / `data-grid` stamps.
+
+### Changed
+- **Rename-wave W2 (gh#1561, PR #1567).** In-repo consumers, demos, and docs migrate to the new `data-sidebar-resize` / `data-layout-grid` names; the W1 shims keep external consumers working.
+
+### Fixed
+- **`table-toolbar`** falls back to the column key when a column label is whitespace-only, and hides the title cluster when it has nothing to show (PR #1573, gh#1571 family).
+
+### Maintenance
+- ADR-0069 Class-R derived artifacts re-derived on main by the new `derived-resync` job (PR #1568).
+- Demo-attribute sweep touched `traits/view-transition`'s examples (one dead attribute dropped, gh#1576 family, PR #1584) — no trait API change.
+- **`components/` touched in this release window** (62 file(s), e.g. `chart-legend/chart-legend.a2ui.json`) — carried by the entries above.
+- **`core/` touched in this release window** (1 file(s), e.g. `core/icons.js`) — carried by the entries above.
+- **`dist/` bundles rebuilt** in this cut's window (4 file(s)) — regenerated from the source changes described above, not independent edits.
+- **`patterns/` touched in this release window** (2 file(s), e.g. `admin-shell/admin-shell.examples.html`) — carried by the entries above.
+- **`styles/` touched in this release window** (1 file(s), e.g. `styles/components.css`) — carried by the entries above.
+
+## [0.8.41] — 2026-08-17
+
+### Added
+- **`segmented-ui` gains a `multiple: Boolean` axis (gh#1369, gh#1363 C1).** Under `[multiple]`, `value` is a comma-separated set (the same encoding `select-ui[multiple]` and the deprecated `toggle-group-ui` already use), the sliding indicator is suppressed in favor of a per-segment selected background, and Space/Enter toggles the focused segment instead of arrow-move selecting it. `components/segmented/segmented.yaml`. Successor surface for the deprecated `toggle-group-ui`/`toggle-option-ui` pair (§Deprecated below). See the migration guide's [§ Shipped in `0.8.41` — `segmented-ui` gains `[multiple]`](../../.claude/docs/MIGRATION%20GUIDE.md).
+- **`progress-ui` gains `label` + `meta` props (gh#1373, gh#1363 C4).** A non-empty `label` activates the identical labeled-row layout `progress-row-ui` used to own (a new Sanctioned Mode Attribute per the component-token-contract) — `components/progress/progress.yaml`. Fixes the catalog exemplar that already put `label` on a `Progress` node, which made generation copying it fail validation. `progress-row-ui` is deprecated below.
+- **`calendar-picker-ui` gains a `precision` axis (`date` | `minute` | `second`, default `date` — unchanged for existing consumers) plus `step`/`hour-cycle`/`locale` props and `input`/`open`/`close`/`invalid` events (gh#1372, gh#1363 C3c/C3d).** Absorbs datetime mode from the now-deprecated `datetime-picker-ui`; the day grid also composes the `calendar-grid-ui` substrate instead of an inlined day grid (gh#1371, C3a). `components/calendar-picker/`.
+- **`upload-ui` — public `.open()` method + compact trigger mode (gh#1493).** `open()` raises the OS file picker programmatically; `[compact]` renders the trigger-only affordance for toolbar/inline placements. `components/upload/upload.yaml`.
+- **`audit-template-child-conflict` ships as a package bin (gh#1446).** The adopt-or-stamp template/child conflict auditor is now runnable by downstream consumers against their own markup, not just in-repo.
+- **`core/dom.js` — `isNode(v)` / `isElement(v)`**, re-exported from the core barrel.
+- **SSR admissibility gate — `scripts/dev/ssr-linkedom-smoke.mjs` + `test/ssr-linkedom-smoke.test.js`.** `linkedom` is now a root devDependency; the script installs exactly the six globals `custom-elements-ssr/server-shim.js` installs, imports every `components/*/*.js` entry and constructs + connects every registered tag the way `CustomElementRender` does. 124/124 import, every tag renders; a new browser-only-API-at-import/connect regression fails the unit suite instead of a consumer's build.
+
+### Changed
+- **BREAKING, no deprecation aliases — global-attribute-shadowing collision sweep, primitive side (gh#1335; the ADR-0053/0054 decision-4 ledger).** `header-ui[padding]` → `[padded]`; `menu-ui`/`popover-ui[gap]` → `[offset]`; `skeleton-ui`/`image-ui[radius]` → `[corner-radius]`; `text-ui[weight]` value `regular` → `normal`; `text-ui[text-align]` converges onto the global physical vocabulary (`start`/`end` → `left`/`right`; `justify` newly supported by the global grammar); `tags-input-ui[transform]` → `[normalize]`. `button-ui`/`toggle-scheme-ui`/`text-ui[color]` are §11-ratified exemptions (ADR-0044/ADR-0064 — they play the color FAMILY axis), and `qr-code-ui[color]` + `icon-ui[weight]` were subsequently ratified as §11 exemptions by ADR-0070 (gh#1500), closing the ledger at 17/17 with no further code change. Composite-side renames shipped in `@adia-ai/web-modules`. See the migration guide's [§ Shipped in `0.8.41` — global-attribute-shadowing collision sweep](../../.claude/docs/MIGRATION%20GUIDE.md).
+- **BREAKING, no deprecation alias — primitive-tier `data-*` state converges to bare attributes (gh#1332, residual round).** `feed-item-ui[data-open]`/`[data-closing]`/`[data-queued]` → `[open]`/`[closing]`/`[queued]`; `slider-ui`/`range-ui[data-dragging]` → `[dragging]`; `pane-ui[data-resizing]` → `[resizing]`; `chart-ui[data-has-data]` → `[has-data]`; `select-ui`'s private `[data-multi-chips]` mirror is dropped outright — its CSS now keys off the compound `[multiple]:not([summary-label])`, both already-declared reflected props. Any CSS/script targeting the old `data-*` forms moves to the bare attributes.
+- **BREAKING, no deprecation alias — `image-ui` declares `loaded`/`error` states as bare attributes (gh#1464, gh#1332 final residue).** The undeclared `[data-loaded]`/`[data-error]` host stamps are now declared `states:` in `components/image/image.yaml` with bare `attribute:` mappings (matching `qr-code-ui`'s converged `error`). The unrelated `[data-overlay]` skeleton-proximity marker (gh#1362) is untouched, and the `data-msg-*` validation-message config family is dispositioned exempt by design (component-side config read by `core/form.js`, not host-reflected state).
+- **BREAKING, no deprecation alias (zero known consumer sites) — `action-item-ui` converges onto `menu-item-ui`'s row contract (gh#1374, gh#1363 C5).** Gains a `subtitle` prop + `text`/`subtitle`/`trailing` slot overrides; the unnamed default slot previously used for trailing content (kbd shortcut, badge, caret) is retired — external consumers slotting trailing children add `slot="trailing"`. The container-level "fold action-list into `list-ui`" question was decided NO; only this row-level convergence ships.
+- **BREAKING for raw A2UI documents only — `chat-thread-ui`'s catalog identity renames `ChatThread` → `UIChatThread` (gh#1427).** The primitive's yaml `component:` collided with the chat web-module's own `ChatThread` at the catalog-build key; `registry.js` maps `UIChatThread` → the unchanged `chat-thread-ui` tag. Generated/hand-authored a2ui trees meaning the standalone primitive update the `component:` name; DOM/JS API and tag are unaffected.
+- **`tab-ui` + `list-item-ui` gain a declared, reflected `[selected]` prop (ADR-0056, gh#1379, gh#1363 B7) — additive.** `tabs-ui` stamps `selected` on the active tab alongside its existing internal wiring; under `list-ui[selectable]` the selection style keys off `[selected]` instead of `[aria-selected="true"]`. `radio-ui[checked]` audited and left as-is (native form-control convention).
+- **yaml/catalog contract sweep — the authoring SoT now distinguishes template-owned anatomy from consumer-fillable slots (ADR-0067, gh#1447).** yaml gains a `parts:` key for anatomy the component always stamps itself; the remaining 143 ambiguous `slots:` entries were classified source-verified (gh#1454 sweep). Related catalog-truth fixes ride along: slot keys renamed to source-stamped names across six components (gh#1461 — button drops phantom `leading`, calendar-picker `calendar` → `popover`, drawer drops `backdrop`, image `img` → `image` + `skeleton`, otp-input `field` → `digit`); enum-shaped props gain their missing `enum` blocks (gh#1363 B6); number/string props with `null` defaults emit nullable schemas (gh#1329); the category vocabulary is ratified and yaml-declared (gh#1363 B9); six primitive yamls stop teaching the invalid `surface` prop (#1387); `toast-ui` is the taught default for transient notices with a real-prop canonical example (gh#1363 C6, gh#1491).
+- **`check-ui` / `radio-ui` / `switch-ui` yaml + a2ui `slots` descriptions now state that `box`/`dot`/`track`/`thumb`/`label`/`hint` are template-OWNED anatomy parts set via `label=`/`hint=` — not light-DOM insertion points (gh#1435).** No behavior change: a foreign `<span slot="label">` child was never a supported form (it is replaced on any late upgrade, SSR or CSR alike). Clarifies the contract a downstream SSR audit and the gen-ui catalog read; the schema-level owned-vs-fillable distinction is gh#1447.
+
+### Deprecated
+- **`progress-row-ui` — absorbed into `progress-ui` (gh#1373, gh#1363 C4).** Keeps working unchanged (still composes `progress-ui`) but ships `status: deprecated` and is no longer taught to the A2UI catalog. Migrate `<progress-row-ui label value meta>` → `<progress-ui label value meta>` (mechanical tag rename); its old `variant` color prop has no successor — recolor via `--progress-fill`.
+- **`toggle-group-ui` / `toggle-option-ui` — superseded by `segmented-ui[multiple]` (gh#1369, gh#1363 C1).** Both ship `status: deprecated` + a one-time `console.warn`; behavior unchanged. Migrate `<toggle-group-ui value>` + `<toggle-option-ui>` → `<segmented-ui multiple value>` + `<segment-ui>` (identical value encoding; `text`/`icon`/`disabled` map directly).
+- **`datetime-picker-ui` — absorbed into `calendar-picker-ui` (gh#1372, gh#1363 C3c).** Now a thin `calendar-picker-ui` subclass defaulting `precision="minute"`; keeps working unchanged. Migrate to `<calendar-picker-ui precision="minute">`.
+
+### Removed
+- **BREAKING, no deprecation alias — `progress-ui[variant]` (gh#1370, gh#1363 C2).** Progress is bar-only; `spinner-ui` owns circular loading indicators (`arc` is the nearest visual match to the old `variant="spinner"` render; `variant="bar"` → drop the attribute). Un-forks the two-circular-answers catalog defect. See the migration guide's [§ Shipped in `0.8.41` — `progress-ui` retires `variant`](../../.claude/docs/MIGRATION%20GUIDE.md).
+- **BREAKING, no deprecation alias — `input-ui[type]` trims to implemented types (gh#1381, gh#1363 B10).** Drops `search`/`date`/`datetime-local`/`time`/`month`/`week`/`color` — none ever rendered a native affordance (all fell back to a plain contenteditable surface). The set is now exactly `text`/`email`/`password`/`number`/`tel`/`url`; route `search` → `search-ui`, `date`/`month`/`week` → `calendar-picker-ui`, `datetime-local` → `calendar-picker-ui precision="minute"`, `time` → `time-picker-ui`, `color` → `color-input-ui`.
+- **BREAKING, no deprecation alias — `calendar-picker-ui`'s own `label` prop/slot and the `--datetime-picker-*` token family (gh#1372).** Wrap in `<field-ui label>` like every sibling picker (label was calendar-picker's own outlier); datetime styling flows through the shared `--calendar-picker-*` tokens.
+
+### Fixed
+- **`card-ui[padding]` implemented (gh#1416).** The prop was fully documented in `components/card/card.yaml` (named scale + numeric rung, `--card-padding` override) but never declared in `card.class.js` nor styled in `card.css` — `<card-ui padding="lg">` did nothing. Now follows `block-ui`'s established `[padding]` contract (`none/xs/sm/md/lg/xl` + numeric rungs → the parametric `--a-padding-*` tokens).
+- **`select-ui` — trigger text reconciles with `[data-empty]` on every write (ADIA2-8927).** The empty-placeholder state could disagree with the rendered trigger text after programmatic value writes.
+- **`image-ui` — `skeleton-ui` `@scope` proximity no longer clips the image out of view (gh#1362).**
+- **`datetime-picker-ui` — static `requiredIcons` restated on the alias class (gh#1503).** The gh#1372 subclass fold dropped the static, so icon preloading for the deprecated alias tag silently stopped.
+- **`stepper-ui` / `timeline-ui` — adopt-or-stamp guard for consumer-authored slot content (gh#1462).** Consumer-provided `[slot]` children are adopted instead of being duplicated by the template stamp.
+- **SSR — `core/responsive.js` no longer calls `window.matchMedia` at module import behind a `typeof window` guard (gh#1430).** linkedom (custom-elements-ssr) defines `window` but neither `matchMedia` nor a numeric `innerWidth`, so `block`/`col`/`grid`/`row`/`text`/`demo-toggle` could not be imported server-side at all, and the breakpoint fallback would have been `'xs'` (mobile layout) rather than the intended `'lg'`. Both sites now feature-detect. `swiper-ui`'s `play()` (`[autoplay]` at connect) guards `matchMedia` the same way.
+- **SSR — bare `instanceof Node/Element/HTMLElement` replaced by structural guards (gh#1436).** Under custom-elements-ssr only `HTMLElement` is a global, so `core/template.js`'s `applyValue` (any template interpolating a node), `table-ui`/`list-window-ui` renderer results and a dozen event-target checks threw `ReferenceError`. New `core/dom.js` exports `isNode()` / `isElement()` (`nodeType`-based; also accept other-realm nodes) — 15 sites swept.
+- **SSR — connect-time `requestAnimationFrame` / `MutationObserver` / `getBoundingClientRect` guarded** in `feed-item-ui`/`toast-ui`, `noodles-ui`, `preview-ui`, `toolbar-ui` (rAF: emit settled state / skip the layout measurement), `nav-group-ui`, `stepper-ui` (MutationObserver — the gh#285 sweep missed these two) and `nav-ui` (`getBoundingClientRect` is absent, not zero, on linkedom). Found by the new render sweep above.
+
+### Maintenance
+- **`dist/` bundles rebuilt** in this cut's window (6 file(s)) — regenerated from the source changes described above, not independent edits.
+- **`patterns/` touched in this release window** (5 file(s), e.g. `conversion-funnel/conversion-funnel.examples.html`) — carried by the entries above.
+- **`styles/` touched in this release window** (1 file(s), e.g. `api/text.css`) — carried by the entries above.
+- **`traits/` touched in this release window** (21 file(s), e.g. `traits/_api-table.js`) — carried by the entries above.
+
 ## [0.8.40] — 2026-08-15
 
 ### Changed
-- **BREAKING (ships in 0.8.40, no deprecation alias): `toggle-group-ui` drops the legacy `data-selected` parallel stamp on `toggle-option-ui` children, per [ADR-0056](../../docs/adr/adr-0056-selection-item-selected-convention.md) (gh#1303).** The additive half of ADR-0056 (`0.8.39`) shipped `toggle-option-ui`'s declared, reflected `selected` prop alongside the pre-existing `data-selected` stamp, scoped that way pending operator sign-off on when the breaking removal would ride. That removal now lands: `toggle-group.class.js`'s render pass no longer sets/clears `data-selected`; `selected` (already the only prop `toggle-group.css` styled) is the sole current-state surface, matching `segment-ui`'s convention. The `DEPRECATED` markers in `toggle-option.yaml`/`toggle-group.yaml` are removed along with the attribute they described. `toggle-group.test.js`'s named deprecation case (`'DEPRECATED — still stamps data-selected in parallel'`) flips to assert the stamp is gone. See the migration guide's [§ Upcoming — `toggle-option-ui` drops the legacy `data-selected` stamp](../../.claude/docs/MIGRATION%20GUIDE.md#upcoming--toggle-option-ui-drops-the-legacy-data-selected-stamp-0840-adr-0056).
+- **BREAKING (ships in 0.8.40, no deprecation alias): `toggle-group-ui` drops the legacy `data-selected` parallel stamp on `toggle-option-ui` children, per [ADR-0056](../../docs/ops/adr/adr-0056-selection-item-selected-convention.md) (gh#1303).** The additive half of ADR-0056 (`0.8.39`) shipped `toggle-option-ui`'s declared, reflected `selected` prop alongside the pre-existing `data-selected` stamp, scoped that way pending operator sign-off on when the breaking removal would ride. That removal now lands: `toggle-group.class.js`'s render pass no longer sets/clears `data-selected`; `selected` (already the only prop `toggle-group.css` styled) is the sole current-state surface, matching `segment-ui`'s convention. The `DEPRECATED` markers in `toggle-option.yaml`/`toggle-group.yaml` are removed along with the attribute they described. `toggle-group.test.js`'s named deprecation case (`'DEPRECATED — still stamps data-selected in parallel'`) flips to assert the stamp is gone. See the migration guide's [§ Upcoming — `toggle-option-ui` drops the legacy `data-selected` stamp](../../.claude/docs/MIGRATION%20GUIDE.md#upcoming--toggle-option-ui-drops-the-legacy-data-selected-stamp-0840-adr-0056).
 - **`table-ui[density]` converges onto the global attribute grammar (ADR-0054, gh#1300).** The component-local `compact | standard | comfortable` enum is removed (`table.yaml`, the reflected `density` prop + `getState()`/`setState()` persistence in `table.class.js`, the `:scope[density="…"]` CSS overrides in `table.css`) — `[density]` on `table-ui` is now the ordinary ambient global attribute (`compact | spacious`, unset = the middle), which `--table-py`/`--table-px` already read via `--a-space-*` (no CSS change needed beyond removing the now-redundant local override). **Breaking, no deprecation alias:** `density="compact"` is unchanged, `density="standard"` becomes the absent attribute, `density="comfortable"` becomes `density="spacious"`. Rides the ratified **0.8.40** breaking wave.
 - **`chart-ui[radius]` renamed to `chart-ui[corner-radius]` (ADR-0054, gh#1300).** Same `Number` type, same `default: null` (falls back to `--a-radius`), same behavior — the collision was with the global preset-enum `[radius]` (`sharp`/`rounded`/`round`), which a numeric px value can't share a name with. **Breaking, no deprecation alias**, rides the ratified **0.8.40** breaking wave.
-- **BREAKING (ships in 0.8.40): `qr-code-ui`'s reflected `[margin]` attribute is renamed `[quiet-zone]` (property `quietZone`), per [ADR-0053](../../docs/adr/adr-0053-no-shadowing-global-attributes.md) (gh#1299).** `qr-code-ui[margin]` silently collided with the framework's global `[margin]` Scale attribute — both accepted the identical `margin="4"` syntax but resolved to unrelated meanings (QR quiet zone in grid cells vs. global box-model spacing) with no error surfaced. Same type/default/reflection; only the name changes. No deprecation alias — `margin` on `qr-code-ui` now means the global Scale attribute. See the migration guide's [§ Upcoming — qr-code-ui quiet-zone rename](../../.claude/docs/MIGRATION%20GUIDE.md#upcoming--qr-code-ui-quiet-zone-rename-adr-0053).
-- **BREAKING (ships in 0.8.40): the legacy `--a-leading-*` line-height token family is retired; `--a-font-leading-*` is the single canonical leading scale, per [ADR-0052](../../docs/adr/adr-0052-leading-scale-consolidation.md) (gh#1298).** Two leading families coexisted in `styles/type/scale.css` with the same step names resolving to different values (`--a-leading-snug` = `1.3` vs. `--a-font-leading-snug` = `1.2`) — no obviously-correct token choice, which is why 55 component files had reached for a bare numeric literal instead. `--a-font-leading-*` gains a `none: 1` step to close its only gap; the 4 in-repo `--a-leading-*` consumers (`button`, `chat-thread`, `inline-message`, `segment`) are migrated by value-nearest judgment (no name-preserving aliases: `snug`→`normal`, `normal`→`relaxed`). The same sweep tokenized every other hardcoded typography literal in `components/*/*.css`: bare numeric `line-height` (56 files; `1.3`/`1.4` → `--a-font-leading-normal`, escape-valve `--a-font-leading-relaxed` for multi-line body copy), `em`-literal `letter-spacing` (12 files; `0.05em` → `--a-font-tracking-wide`), numeric `font-weight` (7 files, on-scale). New `npm run check:typography-tokens` gate (mirrors the brand-chrome/foundation-layer audit gates) fails on any of the three literal classes reappearing. See the migration guide's [§ Upcoming — leading-scale consolidation](../../.claude/docs/MIGRATION%20GUIDE.md#upcoming--leading-scale-consolidation-adr-0052).
+- **BREAKING (ships in 0.8.40): `qr-code-ui`'s reflected `[margin]` attribute is renamed `[quiet-zone]` (property `quietZone`), per [ADR-0053](../../docs/ops/adr/adr-0053-no-shadowing-global-attributes.md) (gh#1299).** `qr-code-ui[margin]` silently collided with the framework's global `[margin]` Scale attribute — both accepted the identical `margin="4"` syntax but resolved to unrelated meanings (QR quiet zone in grid cells vs. global box-model spacing) with no error surfaced. Same type/default/reflection; only the name changes. No deprecation alias — `margin` on `qr-code-ui` now means the global Scale attribute. See the migration guide's [§ Upcoming — qr-code-ui quiet-zone rename](../../.claude/docs/MIGRATION%20GUIDE.md#upcoming--qr-code-ui-quiet-zone-rename-adr-0053).
+- **BREAKING (ships in 0.8.40): the legacy `--a-leading-*` line-height token family is retired; `--a-font-leading-*` is the single canonical leading scale, per [ADR-0052](../../docs/ops/adr/adr-0052-leading-scale-consolidation.md) (gh#1298).** Two leading families coexisted in `styles/type/scale.css` with the same step names resolving to different values (`--a-leading-snug` = `1.3` vs. `--a-font-leading-snug` = `1.2`) — no obviously-correct token choice, which is why 55 component files had reached for a bare numeric literal instead. `--a-font-leading-*` gains a `none: 1` step to close its only gap; the 4 in-repo `--a-leading-*` consumers (`button`, `chat-thread`, `inline-message`, `segment`) are migrated by value-nearest judgment (no name-preserving aliases: `snug`→`normal`, `normal`→`relaxed`). The same sweep tokenized every other hardcoded typography literal in `components/*/*.css`: bare numeric `line-height` (56 files; `1.3`/`1.4` → `--a-font-leading-normal`, escape-valve `--a-font-leading-relaxed` for multi-line body copy), `em`-literal `letter-spacing` (12 files; `0.05em` → `--a-font-tracking-wide`), numeric `font-weight` (7 files, on-scale). New `npm run check:typography-tokens` gate (mirrors the brand-chrome/foundation-layer audit gates) fails on any of the three literal classes reappearing. See the migration guide's [§ Upcoming — leading-scale consolidation](../../.claude/docs/MIGRATION%20GUIDE.md#upcoming--leading-scale-consolidation-adr-0052).
 
 ### Maintenance
 - **`dist/` bundles rebuilt** in this cut's window (6 file(s)) — regenerated from the source changes described above, not independent edits.