@adia-ai/web-components 0.8.42 → 0.8.44

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # Changelog — @adia-ai/web-components
 
+## [0.8.44] — 2026-08-20
+
+### Added
+- **`chart-ui[y-min]`/`[y-max]` — pins the value-axis domain for cartesian types (gh#1690, ADIA2-9137).** `bar`, `line`, `area`, `scatter`, `multi-line`, `stacked-bar`, `grouped-bar`, and `composed` all read the pinned domain instead of auto-scaling to the data's own range — unset (default) is byte-identical to today's auto-scale (floor 0, ceiling the data max). Auto-scale already zero-floors a positive series (a migrating d3 consumer's own "pin the floor to 0" habit is the built-in default, not something to configure) — the pins earn their keep for three OTHER cases (review correction, replacing an earlier draft's inaccurate "auto-scale reads a percent drift as a cliff" claim): zooming a narrow window (`y-min="0.9" y-max="1"` magnifies a percent series clustered near 92-95%, which reads flatter against the full auto-scaled [0,1]), a mixed-sign series (the unpinned floor never goes below 0, so negative values clip at the axis unless `y-min` is pinned negative), and aligning two charts to one shared scale. N/A for radial/part-to-whole types (pie, donut, radar, radial-bar, gauge, funnel, treemap, sankey, segments, sparkline) — those never read a shared linear value axis. New `evals/visual/fixtures/comp-chart-n-ydomain-pinned.json` golden (outside the strict 60-fixture Charts floor's ratio-suffix sweep, same convention as the pre-existing `chart-dashboard` fixture) exercises the pinned path; the 60-fixture floor itself stays green, proving the unset path is unchanged. Added to the `/site/patterns/charts` showcase's ratified-attributes table + a zoomed-window demo (verified in a rendered DOM to produce visibly different axis labels and plotted positions, not just different attributes). Review finding: a datum exceeding the pinned domain now CLAMPS to the nearest edge for rendering (chart-ui's SVG is `overflow: visible`, so an unclamped value previously rendered off-canvas — e.g. `y-max="1"`, value `1.5` resolved to a negative y-coordinate bursting above the plot) — the displayed value label/tooltip still shows the real, unclamped value. 7 new regression tests assert every render path's geometry stays within its own `viewBox` for an out-of-domain datum.
+
+### Fixed
+- **`text-ui[variant="label"|"kicker"|"section"]` render in the mono font stack instead of the UI-sans/heading families (gh#1718).** `label`/`kicker` are now `--a-font-family-code` at regular (400) weight; `section` is the same mono stack at medium (500) — operator-ruled component-level, answering the issue's own open question. Fixed at the shared L3 role tokens (`styles/type/roles.css`'s `--a-kicker-family`/`-weight`, `--a-label-family`/`-weight`, `--a-section-family`/`-weight`), not `text.css`'s own `[variant]` rules — those per-variant `--text-family`/`--text-weight` overrides are dead code for these three properties, since `roles.css`'s `[variant="<role>"]` attribute rule lives in the `utilities` cascade layer, which always wins over `text.css`'s `components`-layer rule by layer order regardless of selector specificity (ADR-0038 step 6 — text-ui is deliberately not excluded from this shared grammar). Side effect of fixing the true single-source token: `menu-ui`'s kicker-styled group headers and `richtext-ui`'s h2 (aliases `--richtext-h2-weight` to `--a-section-weight`) also move to the mono stack, as does `@adia-ai/web-modules`'s `admin-shell` settings-tab section `<h2>` (`--page-section-weight: var(--a-kicker-weight)`) — a weight-only bleed to regular/400, since its own `--page-section-size` reads `--a-kicker-size` (unchanged); `nav`/`nav-item`/`nav-group`'s own structural `[variant="section"]` is already excluded from this token's global rule and is unaffected.
+- **`pagination-ui` first-connect adoption — `connected()` no longer duplicates its `<nav>` when upgrading over server-rendered light DOM (gh#1687, ADIA2-6243).** It guarded on a private `#nav` field (always `null` at construction) and unconditionally appended a fresh `<nav>`; it now queries for a pre-existing `<nav slot="nav">` child first and adopts it, matching `empty-state-ui`'s existing adoption pattern. Adopting the element alone wasn't the whole fix (review finding) — `render()`'s keyed reconcile diffs against `parent[KEY_MAP]`, a keyed `Map` populated by this element's own prior render calls, which a freshly-parsed SSR fragment never has; without seeding it, the first render treated every adopted child as unrecognized and stamped a full duplicate set of buttons alongside the originals. `#seedKeyMapFromAdoptedNav()` positionally zips the adopted children against the same key order the next render would produce, falling back to a normal rebuild on any shape mismatch — two further review findings on that fallback: (1) it bare-returned without clearing the adopted nav's stale children, so `reconcile()`'s own cleanup (which only removes entries already IN its key-map) left the stale children sitting alongside a full fresh render (reproduced: 3 stale placeholders + a correct 9-item render = 12 nodes); (2) child COUNT alone isn't a reliable correlation signal — a same-length fixture with the wrong tag/marker per position (e.g. bare `<span>`s standing in for `<button-ui>` page-cells) would pass a count-only check and get seeded, then `#updateItem()` (attribute-only, never a tag swap) leaves it permanently wrong. Fixed by validating each adopted child's tag + `data-*` marker against its expected item shape (`#childMatchesItem()`) and clearing the adopted nav's children on ANY mismatch before falling through, so the fallback is a genuine clean rebuild either way. Steady-state reconcile is unaffected.
+- **`ssr-linkedom-smoke.mjs` gains a nested-rendering sweep (gh#1699) — proves gen-ui-kit's own light-DOM lifecycle never drops content when one registered custom element's children are themselves other registered custom elements, covering both `col-ui` wrapping `card-ui` DIRECTLY (gh#1699's reported shape) and one level deeper via an anchor wrapper (the mapped-JSX shape gh#1699's own repro used).** Investigated as an SSR content-loss report (Astro dropping `col-ui`/`card-ui` children under `custom-elements-ssr`, adiav2 ADIA2-9483) — root-caused to Astro core's own `renderComponent`/`renderSlots` nesting resolution, entirely outside this repo's dependency graph (no `astro`/`custom-elements-ssr` dep here to reproduce that pipeline against). This sweep is the durable proof of the one thing gen-ui-kit's lifecycle IS responsible for: a fully synchronous `connectedCallback()` round-trip never loses nested light-DOM children on its own. No production code changed.
+- **`command-ui`'s search input rendered its placeholder (and, structurally, any typed text) centered instead of left-aligned next to the leading icon (gh#1697).** Root cause: the search input span and the list's own "No results found." empty-state `<div>` both toggle the same `data-empty` attribute for unrelated reasons, and `command.css`'s empty-state rule was a bare, unscoped `[data-empty]` selector that matched both — its `text-align: center` (meant only for the centered empty-state message) leaked onto the input whenever the input itself was empty. Scoped the rule to `[slot="list"] [data-empty]`, matching the DOM position the empty-state `<div>` actually renders at, removing the collision at its root.
+- **Restored kebab-case props silently dropped from `.d.ts` (gh#1686, `dts-codegen.mjs` fix — see repo-root CHANGELOG).** `button-ui[iconTrailing]`/`[ariaLabel]`, and props on `context-menu-ui`, `integration-card-ui`, `noodles-ui`, `popover-ui`, `stream-ui`, `text-ui`, and `tour-ui` are restored to their `.d.ts` files. No runtime behavior change — these props already worked at runtime; only the shipped TypeScript surface was affected.
+- **Corpus dead-attribute sweep (gh#1669, gh#1611 pt 2 / PR #1668's full-depth harvest-gate findings) — 111 findings across 46 demo/pattern/app-shell source files burned down to zero.** Each fix rewrites the SOURCE usage to the component's real yaml-contract prop rather than inventing a new one: `button-ui[icon-leading|icon-position|icon-only|formnovalidate|tooltip]` → `icon`/`icon-trailing`/(dropped, already auto-computed)/(dropped, unwired)/`title`; `input-ui[icon|icon-leading|icon-trailing|hint]` → `prefix`/`prefix`/`suffix`/`error`; `tag-ui[icon|icon-leading]` dropped (tag-ui has no icon slot); `text-ui[muted|align|tracking]` → `color="subtle"`/`text-align`/dropped; `card-ui[span|compact]` → inline `style="grid-column: span N"`/`size="sm"`; `image-ui[span]` → same grid-column style move; `stat-ui[delta]` → `change`; `nav-item-ui[active]` → `selected`; `otp-input-ui[autocomplete]` dropped (hardcoded internally); `chat-composer[placeholder]` dropped (no such prop); `chart-ui[height]` → inline style; `popover-ui[anchor]` dropped (no such prop — anchoring is implicit); `integration-card-ui[icon]` → `logo`; `progress-ui[indeterminate]` dropped (component's own contract: omit `value`). `input.yaml`'s own `a2ui.rules` doc text corrected alongside — it falsely claimed input-ui supports an inline `[hint]` prop (only `field-ui` does); that false claim was itself feeding the misuse this sweep just fixed.
+
+### Changed
+- **`harvest-chunks.mjs`'s attr-gate promoted from advisory to blocking-by-default (gh#1669)**, now that the 111 known findings are zero — `npm run build:components` / `harvest:chunks` now REFUSE to write when a dead attribute reappears; pass `--advisory-attrs` to warn-only for a one-off triage run. `findAllOpenTagsInRange` hardened to blank `<script>`/`<style>` bodies and HTML comments before matching (reviewer note on PR #1668 — previously harmless only because `attrSchemas` drops unknown tag names, but latent).
+
+### Added
+- **`table-ui` render-cell truncation contract via `[data-truncate]` (gh#1681).** Built-in cell types get single-line ellipsis truncation for free because their output is always a bare `<span>`/`<a>` direct child of the gridcell — a `column.render` function's markup isn't guaranteed to match that shape, so consumer-rendered cells clipped with no ellipsis and no documented opt-in. Set `data-truncate` on whichever rendered element (any tag, including a custom element) should single-line-ellipsis to extend the identical CSS contract built-ins already have; `[wrap]`/`[data-wrap]` override it back to multi-line the same way they do for built-ins. Built-in cell truncation is unchanged.
+- **`table-ui[clickable-rows]` cursor affordance (gh#1680).** adiav2's zero-overrides purge deleted an app-side `[data-clickable]` cursor rule with no kit-side replacement, leaving row-click tables reading as inert. `row-click` fires unconditionally regardless of whether a listener is attached, so the cursor can't be inferred from listener presence — `clickable-rows` is an explicit boolean opt-in (reflected attribute, default `false`) that sets `cursor: pointer` on body rows. No behavior change for tables without it.
+- **`table-toolbar-ui` container-query substrate + `stage` override attribute + breakpoint custom properties (gh#1660 step 1, ADR-0076).** `:scope` now declares `container-type: inline-size; container-name: table-toolbar` (width-only measurement, per `chart.css`'s own documented `size`-containment trap). A new `stage` attribute (enum `full | search-tight | icon-only | overflow`, default `""` = auto-snap, reflects) pins a compaction stage regardless of container width. Three normative `--table-toolbar-bp-search-tight`/`-icon-only`/`-overflow` custom properties (defaults `56rem`/`40rem`/`26rem`) are the single source of truth the coming compaction stages' `@container` rules and the `data-stage-resolved` reflection will both read. No stage-specific rendering lands yet — this step only lands the measurement substrate (PLAN step 1 of the compaction ladder).
+- **`table-toolbar-ui` search-tight compaction stage (gh#1660 step 2, ADR-0076).** The search field's `--table-toolbar-search-min`/`-max` now step down to `--table-toolbar-search-tight-min`/`-max` (defaults `9rem`/`14rem`) once the toolbar's own `inline-size` container crosses `--table-toolbar-bp-search-tight` (`56rem` default), via `@container table-toolbar (max-width: 56rem)`. An explicit `stage="search-tight"` (or the tighter `"icon-only"`/`"overflow"` pins, ahead of their own steps 3/5 CSS) forces the same narrowed extents regardless of the container's actual width, per ADR-0076's `stage` override.
+- **`table-toolbar-ui` icon-only controls stage + title tooltip + range-summary compact/hide (gh#1660 steps 3+4, ADR-0076).** At `--table-toolbar-bp-icon-only` (`40rem` default) — or an explicit `stage="icon-only"`/`"overflow"` pin — Filter/Sort/Columns drop their rendered text label (`::after { content: none }`, overriding `button.css`'s own generated-content rule) and take on square icon-button geometry; `aria-label` stays intact throughout (set unconditionally by `button-ui`'s own `render()`). Every control button now also carries a native `title` attribute unconditionally — harmless at wider stages, the hover-tooltip affordance once the label is visually hidden. At the same breakpoint, the range summary (`"Showing X–Y of N"`) hides only when a visible `[page-size]` select already carries the same context; when page-size is absent, the summary compacts to a short form (`"1–25/320"`) instead of disappearing — the toolbar's sole range indicator never fully vanishes.
+- **`table-toolbar-ui` overflow-menu compaction stage for Filter/Sort/Columns (gh#1660 step 5, ADR-0076).** At `--table-toolbar-bp-overflow` (`26rem` default) — or an explicit `stage="overflow"` pin — the three granular control buttons hide (CSS-only; they stay in the DOM, never destroyed) and one "More" trigger appears instead — reuses the existing `menu-ui`/`menu-item-ui` primitives; adds `menu-ui` to `table-toolbar-ui`'s composition list. Selecting a menu item routes through the same `#togglePopover(kind, btn)` every granular button already calls. The trigger carries a static `aria-label="More table actions"` + `aria-haspopup="menu"` (a genuinely new interactive element). The overflow menu mirrors `chrome-only`/`no-*` suppression — a suppressed control stays suppressed inside the menu too, and the whole trigger hides once every item it would offer is suppressed.
+- **`table-toolbar-ui` visual-eval fixture floor for the compaction ladder (gh#1660 step 6, ADR-0076).** Seven golden fixtures under `evals/visual/` — the four compaction stages (`full`/`search-tight`/`icon-only`/`overflow`, pinned deterministically via `[stage]`), the ratified adiav2 `chrome-only` list-page-toolbar-row shape at the icon-only stage (REQ-A-003's reduced-region case), and AC-003b's two range-summary branches (hide vs compact) as separate fixtures — wired into `npm run check` as `check:table-toolbar-visual-eval`, mirroring the Charts 2.0 visual-eval floor's own harness shape (`scripts/eval/visual-charts-ci.mjs`, gh#1624 step 8).
+- **`table-toolbar-ui` reflects its resolved compaction stage as `data-stage-resolved` (gh#1660 step 7, ADR-0076, ADIA2-9123 S4-ii).** A lightweight `ResizeObserver` classifies the toolbar's own live inline-size against the same three `--table-toolbar-bp-*` breakpoints its CSS `@container` rules use (read live via `getComputedStyle`, falling back to each breakpoint's documented default only when the custom property can't be read at all), reflecting the result onto the host — mirrors `chart-ui`'s `data-ratio-resolved` convention, including its is-different guard. Purely informational: never drives table-toolbar's own rendering, which stays 100% CSS-driven (REQ-M-002). An explicit `stage` pin reports itself; the reflection updates on both a live resize and a `stage` attribute change alone.
+
+### Maintenance
+- **`dist/` bundles rebuilt** in this cut's window (6 file(s)) — regenerated from the source changes described above, not independent edits.
+- **`test/` touched in this release window** (1 file(s), e.g. `test/ssr-linkedom-smoke.test.js`) — carried by the entries above.
+
+## [0.8.43] — 2026-08-18
+
+### Removed
+- **BREAKING — ADR-0063 attribute-grammar addendum cuts: `chart-ui[hide-average|hide-grid|hide-values]`, `chart-legend-ui[static]`, `pane-ui[side]`, `menu-item-ui[subtitle]` prop, and the `color-picker-ui` tag (gh#1617, gh#1377/gh#1563).** Each 0.8.42 dual-read compat shim is removed outright — the deprecated old spellings are now inert (no property, no mirroring, no console warning): `chart-ui` keeps only `no-average`/`no-grid`/`no-values`; `chart-legend-ui` keeps only `interactive` (default still `true` — the ADR's own default-inversion consumer-scan remains a separate follow-up); `pane-ui` keeps only `edge`; `menu-item-ui` keeps only the `description` prop (its `subtitle` SLOT is unchanged); `color-picker-ui`/`ColorPicker`/`UIColorPicker` no longer resolve at all — `color-area-ui`/`ColorArea`/`UIColorArea` is the sole tag/component/class. Operator ruling on gh#1562 (IDR-0004 deviation) lifted all 0.9.0-parked breaking cuts onto this 0.8.43 wave. See `.claude/docs/MIGRATION GUIDE.md` § Shipped in `0.8.43` — ADR-0063 attribute-grammar addendum.
+- **BREAKING — `action-item-ui[subtitle]` prop cut (gh#1617, gh#1571).** `[description]` is the sole prop now; the `subtitle` SLOT is unchanged. Closes the gap PR #1569 flagged once `menu-item-ui` converged onto `description`. See `.claude/docs/MIGRATION GUIDE.md` § Shipped in `0.8.43` — `action-item-ui[description]` ADR-0063 convergence.
+- **BREAKING — three 0.8.41-era deprecated components removed outright: `toggle-group-ui`/`toggle-option-ui`, `progress-row-ui`, `datetime-picker-ui` (gh#1617).** Each shipped its `status: deprecated` soft-deprecation additively in 0.8.41 with a one-time `console.warn`, behavior unchanged; all three are now removed — none of the three tags register as custom elements anymore. Migrate `<toggle-group-ui value>` + `<toggle-option-ui>` children → `<segmented-ui multiple value>` + `<segment-ui>` children (`<toggle-group-ui single>` → plain `<segmented-ui>`); `<progress-row-ui label value meta>` → `<progress-ui label value meta>` (mechanical tag rename); `<datetime-picker-ui>` → `<calendar-picker-ui precision="minute">`. Each alias's successor shipped in 0.8.41, one full release (0.8.42) before this cut — the maturity guard the ticket required. See `.claude/docs/MIGRATION GUIDE.md` § Shipped in `0.8.43` — three 0.8.41-era deprecated components removed.
+
+### Maintenance
+- **`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 (6 file(s)) — regenerated from the source changes described above, not independent edits.
+- **`patterns/` touched in this release window** (3 file(s), e.g. `chart-in-card/chart-in-card.examples.html`) — carried by the entries above.
+- **`styles/` touched in this release window** (2 file(s), e.g. `semantics/features.css`) — carried by the entries above.
+- **`traits/` touched in this release window** (2 file(s), e.g. `arrow-grid-nav/arrow-grid-nav.js`) — carried by the entries above.
+
 ## [0.8.42] — 2026-08-17
 
 ### Added

package/MIGRATION.md

@@ -64,7 +64,7 @@ Version cuts and migration scope:
 
 - **Shipped in `0.8.41` (`progress-ui` retires `variant`, gh#1370)** — **BREAKING, no deprecation alias:** `<progress-ui>`'s `variant` prop (`bar` | `spinner`) is removed — progress is bar-only now. The former `variant="spinner"` render mode (a Sanctioned Mode Attribute per the component-token-contract) is gone; `<spinner-ui>` owns circular loading indicators (`arc`/`ring`/`dots`/`knight`). Migration: `<progress-ui variant="spinner">` → `<spinner-ui>` (pick the closest `variant`; `arc` is the nearest visual match to the old spinner render). `<progress-ui variant="bar">` → drop the attribute (bar was already the default). Filed from the catalog-regularity audit's C2 finding (gh#1363) — a 2026-06 merge folded a standalone spinner into progress as `variant="spinner"`, then a richer standalone `spinner-ui` was re-added later, leaving two circular-loading answers in the catalog; this rider un-forks them. See [§ Shipped in `0.8.41` — `progress-ui` retires `variant`](#upcoming--progress-ui-retires-variant-090-gh1370).
 
-- **Shipped in `0.8.41` (`input-ui` trims `type` enum, gh#1381)** — **BREAKING, no deprecation alias:** `<input-ui>`'s `type` enum drops `search`/`date`/`datetime-local`/`time`/`month`/`week`/`color` — none ever rendered a native affordance (all seven fell back to a plain contenteditable surface), so the enum was first-pass-VALID but functionally broken generation output. The implemented set is now exactly `text`/`email`/`password`/`number`/`tel`/`url`. Migration: `type="search"` → `<search-ui>`; `type="date"`/`"month"`/`"week"` → `<calendar-picker-ui>` (day granularity only — no dedicated month/week primitive exists); `type="datetime-local"` → `<datetime-picker-ui>`; `type="time"` → `<time-picker-ui>`; `type="color"` → `<color-input-ui>` (or `<color-picker-ui>` directly for a full-surface editor). Filed from the catalog-regularity audit's B10 finding (gh#1363). See [§ Shipped in `0.8.41` — `input-ui` trims `type` enum](#upcoming--input-ui-trims-type-enum-090-gh1381).
+- **Shipped in `0.8.41` (`input-ui` trims `type` enum, gh#1381)** — **BREAKING, no deprecation alias:** `<input-ui>`'s `type` enum drops `search`/`date`/`datetime-local`/`time`/`month`/`week`/`color` — none ever rendered a native affordance (all seven fell back to a plain contenteditable surface), so the enum was first-pass-VALID but functionally broken generation output. The implemented set is now exactly `text`/`email`/`password`/`number`/`tel`/`url`. Migration: `type="search"` → `<search-ui>`; `type="date"`/`"month"`/`"week"` → `<calendar-picker-ui>` (day granularity only — no dedicated month/week primitive exists); `type="datetime-local"` → `<calendar-picker-ui precision="minute">` (`<datetime-picker-ui>` was cut in 0.8.43, gh#1617); `type="time"` → `<time-picker-ui>`; `type="color"` → `<color-input-ui>` (or `<color-area-ui>` directly for a full-surface editor — `<color-picker-ui>` was likewise cut in 0.8.43, gh#1617). Filed from the catalog-regularity audit's B10 finding (gh#1363). See [§ Shipped in `0.8.41` — `input-ui` trims `type` enum](#upcoming--input-ui-trims-type-enum-090-gh1381).
 
 - **Shipped in `0.8.41` (web-modules `data-*` state converges to bare attributes, gh#1332)** — **BREAKING, no deprecation alias:** two web-modules' declared `states:` entries drop a private `data-*` stamp for a bare state attribute, per the data-* usage sweep's Category A disposition (ADR-0056's rule generalized past `toggle-option-ui`). `<integrations-page-ui>`'s `empty-search`/`empty-data` states (was `data-empty-search`/`data-empty-data`) and `<onboarding-checklist-ui>`'s `complete` state (was `data-complete`) now match their own sibling states' existing bare-attribute convention (`loading`, `collapsed`). Migration: any `[data-empty-search]`/`[data-empty-data]`/`[data-complete]` CSS or script targeting these two modules moves to `[empty-search]`/`[empty-data]`/`[complete]`. See [§ Shipped in `0.8.41` — web-modules data-* state converges to bare attributes](#upcoming--web-modules-data--state-converges-to-bare-attributes-090-gh1332).
 
@@ -82,11 +82,13 @@ Version cuts and migration scope:
 
 - **Shipped in `0.8.41` (`image-ui` load/error states declared + converge to bare attributes, gh#1464)** — **BREAKING, no deprecation alias.** The final residue of the [data-* usage sweep](https://github.com/adiahealth/gen-ui-kit/issues/1332), deferred out of the residual round above because it needed a new `states:` declaration rather than a bare mapping change: `<image-ui>`'s `[data-loaded]`/`[data-error]` were genuine undeclared host-level state (never yaml-declared at all) — now declared as `loaded`/`error` in `image.yaml`'s `states:` list with bare `attribute:` mappings, matching qr-code-ui's own converged `error` state. Migration: any `[data-loaded]`/`[data-error]` CSS or script targeting `image-ui` moves to `[loaded]`/`[error]`; `image-ui`'s unrelated `[data-overlay]` skeleton-proximity marker (gh#1362) is untouched. A repo-wide consumer sweep (`rg -nU 'data-loaded|data-error'`) found zero external consumers of image-ui's forms specifically, so no deprecation alias was kept. The same ticket also dispositioned the `data-msg-*` validation-message config family (`data-msg-required`/`pattern`/`minlength`/`maxlength`/`min`/`max`/`bad-input`) as **exempt, non-breaking, no migration** — it stays `data-*` by design (component-side config read by `core/form.js`'s shared mixin across 7+ components, not host-reflected state; see `primitive-authoring/references/yaml-contract.md`'s new `data-msg-*` section for the full rationale). See [§ Shipped in `0.8.41` — image-ui load/error states declared + converge to bare attributes](#upcoming--image-ui-loaderror-states-declared--converge-to-bare-attributes-090-gh1464).
 
-- **Upcoming `0.9.0` (rename wave — `data-grid` / `data-resize`, docs/ops/plan/plan-090-rename-wave.md)** — **BREAKING at the 0.9.0 cut; a 0.8.x patch ships additive dual-read compat shims first (this entry), per the 2026-08-14 standing ruling that breaking renames never ship in a patch.** `admin-shell`'s consumer-authored 2/3-column content-layout helper `[data-grid]` / `[data-grid="3"]` renames to `[data-layout-grid]` / `[data-layout-grid="3"]` (sits with the `data-col`/`data-row`/`data-actions`/`data-spacer` form-layout-helper family it belongs to, outside every trait-owned root). The author-supplied drag-handle child of `<admin-sidebar>`/`<chat-sidebar>`/`<editor-sidebar>` `[data-resize]` renames to `[data-sidebar-resize]` (owner-scoped to the `*-sidebar` composite family, outside resize-observer's grandfathered `resize` root). Both attributes decorate plain light-DOM children the shells don't own (not a trait/component API), so only the name changes. **Now (0.8.x, additive):** both old and new names work — JS reads dual-query (new name first, falling back to old with a one-time `console.warn`), CSS selectors dual-select via `:is()`, and `adia-lint`'s SHELL-RESIZE rule accepts either name (advisory `DEPRECATED-LAYOUT-NAME` flags the old ones). **At the `0.9.0` cut:** the old names stop resolving — `[data-resize]` reverts to `<admin-sidebar>`'s existing "no handle found" author warning (the correct post-cut behavior, no new code needed) and `[data-grid]` simply no longer matches any CSS rule. Migration (published again, final, at the cut): `git grep -l 'data-resize' | xargs perl -pi -e 's/\bdata-resize\b(?!-)/data-sidebar-resize/g'` and `git grep -l 'data-grid' | xargs perl -pi -e 's/\bdata-grid\b(?!-)/data-layout-grid/g'` (negative lookahead protects trait-owned `data-resize-*`/`data-grid-*` names — unrelated grandfathered attributes, e.g. resize-observer's `data-resize-width`/`data-resize-observer-observed` and arrow-grid-nav's `data-grid-columns`/`mode`/`active-row`/`active-col`, which this wave never touches). Tracked: gh#1560 (this shim) → gh#1561 (in-repo consumer + docs migration) → gh#1562 (the 0.9.0 cut). Disjoint from, and coordinated with, gh#1377/gh#1563's ADR-0063 rename set (chart `hide-*`, `pane[side]`, `color-picker-ui` → `color-area-ui`, `menu-item-ui[subtitle]`) — same 0.9.0 cycle, separate PRs, no file overlap.
+- **Shipped in `0.8.43` (rename wave — `data-grid` / `data-resize`, docs/ops/plan/plan-090-rename-wave.md)** — **BREAKING, no deprecation alias — the 0.8.x dual-read compat shim (gh#1560/gh#1561) is removed.** `admin-shell`'s consumer-authored 2/3-column content-layout helper `[data-grid]` / `[data-grid="3"]` is renamed to `[data-layout-grid]` / `[data-layout-grid="3"]` (sits with the `data-col`/`data-row`/`data-actions`/`data-spacer` form-layout-helper family it belongs to, outside every trait-owned root). The author-supplied drag-handle child of `<admin-sidebar>`/`<chat-sidebar>`/`<editor-sidebar>` `[data-resize]` is renamed to `[data-sidebar-resize]` (owner-scoped to the `*-sidebar` composite family, outside resize-observer's grandfathered `resize` root). Both attributes decorate plain light-DOM children the shells don't own (not a trait/component API), so only the name changed. **The old names no longer resolve:** `[data-resize]` now falls through to `<admin-sidebar>`'s existing "no handle found" author warning (the correct post-cut behavior, no new code needed — `<chat-sidebar>` has no such warning and is silently unhandled) and `[data-grid]` simply no longer matches any CSS rule. `adia-lint`'s SHELL-RESIZE rule now requires `[data-sidebar-resize]` only; its transition-window `DEPRECATED-LAYOUT-NAME` advisory is retired with the window it existed for. `KNOWN_GRAZING_PAIRS` (`scripts/build/traits-catalog.mjs`) drops both entries — 2 → 0, and `verify:traits` now fails hard on any NEW overlap with either old name. Migration (mechanical): `git grep -l 'data-resize' | xargs perl -pi -e 's/\bdata-resize\b(?!-)/data-sidebar-resize/g'` and `git grep -l 'data-grid' | xargs perl -pi -e 's/\bdata-grid\b(?!-)/data-layout-grid/g'` (negative lookahead protects trait-owned `data-resize-*`/`data-grid-*` names — unrelated grandfathered attributes, e.g. resize-observer's `data-resize-width`/`data-resize-observer-observed` and arrow-grid-nav's `data-grid-columns`/`mode`/`active-row`/`active-col`, which this wave never touches). Shipped: gh#1560 (W1 shim) → gh#1561 (W2 in-repo consumer + docs migration) → gh#1562 (W3, this cut). **Deviates from release invariant 7 / IDR-0004** (breaking removals never ship in a patch) — operator ruling 2026-08-18 on gh#1562 moved this 0.9.0-parked cut into the `0.8.43` window ("whatever items are waiting for 0.9.0 should use 0.8.43"), the same recorded-deviation pattern as the `0.8.41` cut. Disjoint from, and coordinated with, gh#1377/gh#1563's ADR-0063 rename set (chart `hide-*`, `pane[side]`, `color-picker-ui` → `color-area-ui`, `menu-item-ui[subtitle]`) and gh#1617's own 0.8.43 breaking-wave build — separate PRs, no file overlap.
 
-- **Upcoming `0.9.0` (ADR-0063 attribute-grammar addendum — chart `no-*`, `chart-legend[interactive]`, `pane[edge]`, `color-area-ui`, `menu-item[description]`, gh#1377/gh#1563)** — **BREAKING at the 0.9.0 cut; a 0.8.42 patch ships additive dual-read compat shims first (this entry), per the same 2026-08-14 standing ruling gh#1560's rename wave follows: breaking renames never ship in a patch.** Five identifiers converge onto ADR-0063's ratified spellings: `chart-ui[hideAverage|hideGrid|hideValues]` → `[noAverage|noGrid|noValues]` (same polarity, straight rename — `no-*` has 8-component/12-attribute plurality over `hide-*`'s 2/4); `chart-legend-ui[static]` (opt-out) → `[interactive]` (opt-in) — **the default itself is NOT flipped in 0.8.42**, `[interactive]` defaults `true` so omitting both attributes keeps today's behavior unchanged, the real default-inversion to `false` is deferred to the 0.9.0 cut per the ADR's own consumer-scan requirement (every `<chart-legend-ui>` tag needs review first); `pane-ui[side]` → `[edge]` (pane-only — `drawer-ui[side]` keeps its own name/vocabulary unchanged); `menu-item-ui[subtitle]` → `[description]` (prop only — the `subtitle` SLOT is a separate, deliberately unrenamed surface); and the tag/component rename `color-picker-ui`/`ColorPicker`/`UIColorPicker` → `color-area-ui`/`ColorArea`/`UIColorArea` (B11 — `-picker` is reserved for the outer trigger+popover composite shape; `color-picker-ui` was the sole violator, playing `calendar-grid-ui`'s inline-substrate role — mirrors the `datetime-picker-ui` → `calendar-picker-ui` alias shape from gh#1372). **Now (0.8.42, additive):** every old name/tag keeps working — each renamed attribute dual-reads (new name wins when both are present, the old name resolves with a one-time `console.warn` when it's the only one set, no warn either way otherwise) and `<color-picker-ui>` is a thin `UIColorArea` subclass (`status: deprecated`) rather than a removed tag. `<color-input-ui>`'s own `composes:` and internal substrate references move to `<color-area-ui>` (its own tag/name is unaffected — it was already correctly *not* named `-picker` despite playing the composite role). **At the `0.9.0` cut:** the old names/tag stop resolving and `chart-legend-ui[interactive]`'s default flips to `false`. Migration (mechanical, at the cut): `git grep -l 'hide-average\|hide-grid\|hide-values' | xargs perl -pi -e 's/\bhide-average\b/no-average/g; s/\bhide-grid\b/no-grid/g; s/\bhide-values\b/no-values/g'`; `git grep -l 'pane-ui' | xargs perl -pi -e 's/(<pane-ui\b[^>]*\b)side=/\1edge=/g'`; `git grep -l 'menu-item-ui' | xargs perl -pi -e 's/(<menu-item-ui\b[^>]*\b)subtitle=/\1description=/g'`; `git grep -rl 'color-picker-ui\|UIColorPicker' | xargs perl -pi -e 's/color-picker-ui/color-area-ui/g; s/UIColorPicker/UIColorArea/g'`; every `<chart-legend-ui>` tag (with or without `[static]`/`[interactive]`) needs a manual pass adding `[interactive]` where the old default was relied on. Filed from the catalog-regularity audit's B2/B3(noodles-only, non-breaking)/B5/B11 findings (gh#1363) via [ADR-0063](../../docs/ops/adr/adr-0063-attribute-grammar-addendum.md). **Rejected/deferred, not part of this dispatch's five items:** `action-item-ui[subtitle]` (a newly-surfaced sole outlier once menu-item converges — flagged for a human decision, not fixed here); `segmented-ui[multiple]`'s comma-separated value encoding (operator-sanctioned as-is); `toggle-group-ui[value]`'s comma-string violation (tracked by gh#1363's own toggle-group/segmented consolidation candidate); `drilldown-ui[static]`→`[no-slide-transition]`, `alert-ui[dismissible]`, `card-ui[outline]`, `agent-reasoning-ui[status="done"]`→`"completed"`, and `noodles-ui[port-size]`/`[show-ports]` duplicate-entry cleanup (all ADR-0063 decisions, but each is its own separately-scoped follow-up build, not gh#1563's five-item scope). Disjoint from, and coordinated with, gh#1560/gh#1561/gh#1562's `data-grid`/`data-resize` rename wave — same 0.9.0 cycle, separate PRs, no file overlap. See [§ Upcoming — ADR-0063 attribute-grammar addendum](#upcoming--adr-0063-attribute-grammar-addendum-chart-no--chart-legendinteractive-paneedge-color-area-ui-menu-itemdescription-090-gh1377gh1563).
+- **Shipped in `0.8.43` (ADR-0063 attribute-grammar addendum — chart `no-*`, `chart-legend[interactive]`, `pane[edge]`, `color-area-ui`, `menu-item[description]`, gh#1377/gh#1563/gh#1617)** — **BREAKING.** The 0.8.42 additive dual-read compat shims are removed per the operator ruling on gh#1562 (IDR-0004 deviation) lifting all 0.9.0-parked breaking cuts onto 0.8.43. Five identifiers now resolve to ADR-0063's ratified spellings ONLY: `chart-ui[hideAverage|hideGrid|hideValues]` → `[noAverage|noGrid|noValues]`; `chart-legend-ui[static]` → `[interactive]` (default still NOT flipped — that inversion remains its own unscoped follow-up); `pane-ui[side]` → `[edge]`; `menu-item-ui[subtitle]` prop → `[description]` prop (the `subtitle` SLOT is unchanged); and `color-picker-ui`/`ColorPicker`/`UIColorPicker` are removed outright — `color-area-ui`/`ColorArea`/`UIColorArea` is the sole tag/component/class. Every old name/tag is now inert (no property, no dual-read, no warning). Filed from the catalog-regularity audit's B2/B3/B5/B11 findings (gh#1363) via [ADR-0063](../../docs/ops/adr/adr-0063-attribute-grammar-addendum.md). **Rejected/deferred:** `chart-legend-ui[interactive]`'s default-inversion to `false` (its own consumer-scan requirement is unmet); `drilldown-ui[static]`, `alert-ui[dismissible]`, `card-ui[outline]`, `agent-reasoning-ui[status]`, `noodles-ui[port-size]`/`[show-ports]` cleanup (separately-scoped follow-ups). See [§ Shipped in `0.8.43` — ADR-0063 attribute-grammar addendum](#upcoming--adr-0063-attribute-grammar-addendum-chart-no--chart-legendinteractive-paneedge-color-area-ui-menu-itemdescription-090-gh1377gh1563).
 
-- **Upcoming `0.9.0` (ADR-0063 convergence — `action-item-ui[description]`, gh#1571)** — **BREAKING at the 0.9.0 cut; an additive patch ships a dual-read compat shim first (this entry), per the same 2026-08-14 standing ruling gh#1560's rename wave and gh#1563's ADR-0063 addendum both follow: breaking renames never ship in a patch.** `action-item-ui[subtitle]` → `[description]` (prop only — the `subtitle` **slot** is a separate, deliberately unrenamed surface, exactly like `menu-item-ui`'s own gh#1563 shape). This closes the gap PR #1569 itself flagged as a rejected/deferred follow-up once `menu-item-ui` converged onto `description`: `action-item-ui` became the corpus's remaining sole `subtitle` outlier. **Now (additive):** both names work — `[description]` wins outright when present (no warning — this is intentional forward-compatible spelling, not a fallback); `[subtitle]` resolves with a one-time `console.warn` per class when it's the only one set; a post-mount `[subtitle]` update keeps mirroring into `[description]` until `[description]` is authored directly, at which point it wins permanently. **At the `0.9.0` cut:** `[subtitle]` stops resolving. Migration (mechanical, at the cut): `git grep -l '<action-item-ui\b' | xargs perl -pi -e 's/(<action-item-ui\b[^>]*\b)subtitle=/\1description=/g'`. See [§ Upcoming — `action-item-ui[description]` ADR-0063 convergence](#upcoming--action-item-uidescription-adr-0063-convergence-090-gh1571). **Rejected/deferred:** the 0.9.0 breaking removal itself — same "no breaking rename in a patch" standing ruling as every sibling entry above.
+- **Shipped in `0.8.43` (ADR-0063 convergence — `action-item-ui[description]`, gh#1571/gh#1617)** — **BREAKING.** `action-item-ui[subtitle]` prop is removed — `[description]` is the sole prop now (the `subtitle` **slot** is unchanged, exactly like `menu-item-ui`'s own gh#1563 shape). Closes the gap PR #1569 flagged as a follow-up once `menu-item-ui` converged onto `description`. See [§ Shipped in `0.8.43` — `action-item-ui[description]` ADR-0063 convergence](#upcoming--action-item-uidescription-adr-0063-convergence-090-gh1571).
+
+- **Shipped in `0.8.43` (three 0.8.41-era deprecated components removed — `toggle-group-ui`/`toggle-option-ui`, `progress-row-ui`, `datetime-picker-ui`, gh#1617)** — **BREAKING.** Each shipped its `status: deprecated` soft-deprecation additively in `0.8.41` (its own entry below); all three are now removed outright per the same operator ruling (gh#1562, IDR-0004 deviation). None of the three tags register as custom elements anymore. Migrate: `<toggle-group-ui value>` + `<toggle-option-ui>` children → `<segmented-ui multiple value>` + `<segment-ui>` children (`<toggle-group-ui single>` → plain `<segmented-ui>`, no `[multiple]`); `<progress-row-ui label value meta>` → `<progress-ui label value meta>` (mechanical tag rename); `<datetime-picker-ui>` → `<calendar-picker-ui precision="minute">`. See [§ Shipped in `0.8.43` — three 0.8.41-era deprecated components removed](#shipped-in-0843--three-0841-era-deprecated-components-removed-toggle-group-uitoggle-option-ui-progress-row-ui-datetime-picker-ui-gh1617).
 
 Live demos and per-component docs at [ui-kit.exe.xyz/site/](https://ui-kit.exe.xyz/site/). The `adia-ui-migration` skill (in `.agents/skills/`) automates most of the mechanical sweeps in this guide.
 
@@ -751,9 +753,9 @@ finding, [gh#1363](https://github.com/adiahealth/gen-ui-kit/issues/1363).
 | `<input-ui type="search">` | `<search-ui>` (built-in magnifying-glass icon, clear button, debounced `search` event) |
 | `<input-ui type="date">` | `<calendar-picker-ui>` (single-date, day granularity) |
 | `<input-ui type="month">` / `type="week"` | `<calendar-picker-ui>` — no dedicated month/week-granularity primitive exists in the catalog; day granularity is the closest routed primitive |
-| `<input-ui type="datetime-local">` | `<datetime-picker-ui>` |
+| `<input-ui type="datetime-local">` | `<calendar-picker-ui precision="minute">` (`<datetime-picker-ui>` was a thin compat alias, cut in 0.8.43, gh#1617) |
 | `<input-ui type="time">` | `<time-picker-ui>` |
-| `<input-ui type="color">` | `<color-input-ui>` (compact form-row swatch + popover) — or `<color-picker-ui>` directly for a full-surface editor (Tokens-Studio-style canvas) |
+| `<input-ui type="color">` | `<color-input-ui>` (compact form-row swatch + popover) — or `<color-area-ui>` directly for a full-surface editor (Tokens-Studio-style canvas; `<color-picker-ui>` was likewise cut in 0.8.43, gh#1617) |
 | `<input-ui>` (no type, or `text`/`email`/`password`/`number`/`tel`/`url`) | unchanged |
 
 The routed primitives are NOT drop-in attribute-compatible with
@@ -1656,12 +1658,13 @@ npm run check
 
 ---
 
-## Upcoming — ADR-0063 attribute-grammar addendum (chart no-*, chart-legend[interactive], pane[edge], color-area-ui, menu-item[description], 0.9.0, gh#1377/gh#1563)
+## Shipped in `0.8.43` — ADR-0063 attribute-grammar addendum (chart no-*, chart-legend[interactive], pane[edge], color-area-ui, menu-item[description], gh#1377/gh#1563/gh#1617)
 
-**Shipped additively in `0.8.42`; BREAKING removal deferred to the `0.9.0`
-cut** — per the same 2026-08-14 standing ruling gh#1560's `data-grid`/
-`data-resize` rename wave follows: a breaking rename never ships in a
-patch. [ADR-0063](../../docs/ops/adr/adr-0063-attribute-grammar-addendum.md)
+**BREAKING.** The additive dual-read compat shims shipped in `0.8.42`
+(previous entry below); this cut removes the deprecated old spellings per
+the operator ruling recorded on gh#1562 (IDR-0004 deviation) that lifted
+all 0.9.0-parked breaking cuts onto `0.8.43`.
+[ADR-0063](../../docs/ops/adr/adr-0063-attribute-grammar-addendum.md)
 ratified six decisions from the catalog-regularity audit
 ([gh#1363](https://github.com/adiahealth/gen-ui-kit/issues/1363)); this
 entry covers the five identifiers gh#1563's own build scope named. (The
@@ -1670,42 +1673,36 @@ convergence — and the `alert`/`card`/`drilldown`/`noodles` decision-2
 items ship under their own separately-scoped follow-up tickets, not
 this one.)
 
-### What changed (additive, 0.8.42)
+### What changed (BREAKING, 0.8.43)
 
-| Component | Old (deprecated, still works) | New (canonical) | Shape |
+| Component | Old (removed) | New (sole spelling) | Shape |
 |---|---|---|---|
 | `<chart-ui>` | `[hide-average]` | `[no-average]` | straight rename, same polarity |
 | `<chart-ui>` | `[hide-grid]` | `[no-grid]` | straight rename, same polarity |
 | `<chart-ui>` | `[hide-values]` | `[no-values]` | straight rename, same polarity |
-| `<chart-legend-ui>` | `[static]` (opt-out) | `[interactive]` (opt-in) | polarity flip — **default NOT yet flipped**, see below |
+| `<chart-legend-ui>` | `[static]` (opt-out) | `[interactive]` (opt-in) | polarity flip — **default still NOT flipped**, see below |
 | `<pane-ui>` | `[side]` | `[edge]` | straight rename, same type/default/enum (`drawer-ui[side]` is untouched — different component, different vocabulary) |
 | `<menu-item-ui>` | `[subtitle]` prop | `[description]` prop | straight rename — the `subtitle` **slot** is a separate surface, deliberately left unrenamed |
-| `<color-picker-ui>` (tag) | `color-picker-ui` / `ColorPicker` / `UIColorPicker` | `color-area-ui` / `ColorArea` / `UIColorArea` | tag/component/class rename (B11, picker-naming convention) — old tag is now a thin `UIColorArea` subclass, `status: deprecated` |
-
-Every renamed attribute dual-reads: **new name wins** when both are
-present (no warning — this is intentional forward-compatible spelling,
-not a fallback); the **old name resolves** with a one-time
-`console.warn` per class when it's the only one set; neither present
-keeps today's default. `<color-picker-ui>` keeps rendering/behaving
-identically — it inherits every prop, event, and token from
-`<color-area-ui>` verbatim (mirrors the `<datetime-picker-ui>` →
-`<calendar-picker-ui>` alias shape from
-[gh#1372](https://github.com/adiahealth/gen-ui-kit/issues/1372)).
-`<color-input-ui>`'s own `composes:` list and internal substrate
-references move to `<color-area-ui>`; `<color-input-ui>`'s own tag/name
-is unaffected (it was already correctly *not* named `-picker` despite
-playing the outer trigger+popover composite role).
-
-**`chart-legend-ui[interactive]`'s default is deliberately NOT flipped
-in this release.** `[interactive]` defaults `true` — a `<chart-legend-ui>`
-naming neither `[static]` nor `[interactive]` renders exactly as it
-does today (interactive `<button>`-role rows). The ADR's own
-"default-inversion" consumer-scan requirement — every `<chart-legend-ui>`
-tag, with or without either attribute, reviewed for whether omission
-was relying on the old default — is the 0.9.0 cut's own prerequisite,
-not this one's.
-
-### Migration (mechanical, recommended now / required at the 0.9.0 cut)
+| `<color-picker-ui>` (tag) | `color-picker-ui` / `ColorPicker` / `UIColorPicker` | `color-area-ui` / `ColorArea` / `UIColorArea` | tag/component/class removed outright (B11, picker-naming convention) — `color-area-ui` is the sole tag now |
+
+The old names/tag no longer resolve: `[hide-average]`/`[hide-grid]`/
+`[hide-values]` are inert attributes on `<chart-ui>` (no property, no
+dual-read); `<chart-legend-ui>`'s `[static]` is likewise inert;
+`<pane-ui>`'s `[side]` is inert; `<menu-item-ui>`'s `[subtitle]` PROP is
+inert (the `subtitle` **slot** is unchanged); and `<color-picker-ui>` no
+longer registers as a custom element at all — `<color-area-ui>` is the
+sole tag, class, and catalog identity.
+
+**`chart-legend-ui[interactive]`'s default is still NOT flipped in this
+release.** `[interactive]` defaults `true` — a `<chart-legend-ui>` naming
+neither attribute renders exactly as it does today (interactive
+`<button>`-role rows). The ADR's own "default-inversion" consumer-scan
+requirement — every `<chart-legend-ui>` tag, with or without the
+attribute, reviewed for whether omission was relying on the old default —
+remains open and is out of this ticket's scope (gh#1617); it ships under
+its own separately-scoped follow-up.
+
+### Migration (mechanical — already applied repo-wide in gh#1617)
 
 ```bash
 git grep -l 'hide-average\|hide-grid\|hide-values' -- packages apps playgrounds site site-a2ui \
@@ -1721,12 +1718,13 @@ git grep -rl 'color-picker-ui\|UIColorPicker' -- packages apps playgrounds site
   | xargs perl -pi -e 's/color-picker-ui/color-area-ui/g; s/UIColorPicker/UIColorArea/g'
 ```
 
-Every `<chart-legend-ui>` tag additionally needs a manual (not
-mechanical) review pass: add `[interactive]` explicitly wherever the
-page relied on the current "interactive by default" behavior, ahead of
-the 0.9.0 default-inversion.
+Every `<chart-legend-ui>` tag still needs a manual (not mechanical)
+review pass: add `[interactive]` explicitly wherever the page relied on
+the current "interactive by default" behavior, ahead of the still-open
+default-inversion follow-up.
 
-**Find every affected consumer site:**
+**Find every remaining consumer site (external consumers upgrading from
+pre-0.8.42):**
 
 ```bash
 npm run qa:contract-migration-scan -- --roots packages,apps,playgrounds,site,site-a2ui \
@@ -1740,24 +1738,19 @@ scanner's own default) — `site-a2ui/` is a separate top-level directory
 the default roots miss entirely (ADR-0063's own consumer-scan
 mechanism section explains why).
 
-### Rejected / deferred (explicitly out of gh#1563's scope)
+### Rejected / deferred (explicitly out of gh#1617's scope)
 
-- `action-item-ui[subtitle]` — once `menu-item-ui` converges onto
-  `description`, `action-item-ui` becomes the corpus's new sole
-  `subtitle` outlier (the same shape of defect ADR-0063 just fixed for
-  menu-item). Flagged as a discovered follow-up candidate for a human
-  ticketing decision — not fixed in this dispatch.
 - `segmented-ui[multiple]`'s comma-separated value encoding — sanctioned
   as-is (operator ruling, gh#1563, 2026-08-17).
-- `toggle-group-ui[value]`'s comma-string violation — tracked by
-  gh#1363's own `toggle-group`/`segmented` consolidation candidate, not
-  duplicated here.
+- `chart-legend-ui[interactive]`'s default-inversion to `false` — the
+  ADR's own consumer-scan requirement is still unmet; ships under its own
+  separately-scoped follow-up, not this ticket.
 - `drilldown-ui[static]` → `[no-slide-transition]`, `alert-ui[dismissible]`
   retirement, `card-ui[outline]` retirement,
   `agent-reasoning-ui[status="done"]` → `"completed"`, and
   `noodles-ui[port-size]`/`[show-ports]` duplicate-entry cleanup — all
   real ADR-0063 decisions, each its own separately-scoped follow-up
-  build, not part of gh#1563's five-item scope.
+  build, not part of this ticket's scope.
 - `menu-item-ui`'s `subtitle` **slot** (distinct from the prop) — left
   unrenamed by design; renaming a slot is a different, unscoped surface.
 
@@ -1772,43 +1765,38 @@ npm run check
 
 ---
 
-## Upcoming — `action-item-ui[description]` ADR-0063 convergence (0.9.0, gh#1571)
+## Shipped in `0.8.43` — `action-item-ui[description]` ADR-0063 convergence (gh#1571/gh#1617)
 
-**Shipped additively; BREAKING removal deferred to the `0.9.0` cut** — per
-the same 2026-08-14 standing ruling gh#1560's `data-grid`/`data-resize`
-rename wave and gh#1563's ADR-0063 addendum both follow: a breaking rename
-never ships in a patch. This closes the gap [PR
-#1569](https://github.com/adiahealth/gen-ui-kit/pull/1569) itself flagged
-under its own "Rejected/deferred" section: once `<menu-item-ui>` converged
-its `subtitle` prop onto `description` ([ADR-0063](../../docs/ops/adr/adr-0063-attribute-grammar-addendum.md),
+**BREAKING.** The additive dual-read compat shim shipped ahead of this cut
+(previous entry below); this cut removes the deprecated `[subtitle]` prop
+per the operator ruling recorded on gh#1562 (IDR-0004 deviation) that
+lifted all 0.9.0-parked breaking cuts onto `0.8.43`. This closes the gap
+[PR #1569](https://github.com/adiahealth/gen-ui-kit/pull/1569) itself
+flagged under its own "Rejected/deferred" section: once `<menu-item-ui>`
+converged its `subtitle` prop onto `description`
+([ADR-0063](../../docs/ops/adr/adr-0063-attribute-grammar-addendum.md),
 gh#1563), `<action-item-ui>` became the corpus's remaining sole `subtitle`
 outlier — the same shape of defect ADR-0063 fixed for menu-item.
 
-### What changed (additive)
+### What changed (BREAKING, 0.8.43)
 
-| Component | Old (deprecated, still works) | New (canonical) | Shape |
+| Component | Old (removed) | New (sole spelling) | Shape |
 |---|---|---|---|
 | `<action-item-ui>` | `[subtitle]` prop | `[description]` prop | straight rename — the `subtitle` **slot** is a separate surface, deliberately left unrenamed |
 
-`[description]` wins outright when present (no warning — this is
-intentional forward-compatible spelling, not a fallback); `[subtitle]`
-resolves with a one-time `console.warn` per class when it's the only one
-set; neither present keeps today's default (empty string, no rendered
-subtitle row). Unlike `menu-item-ui`'s own gh#1563 shim (which only
-resolves once, at `connected()`), `action-item-ui`'s shim re-resolves on
-every render until `[description]` is authored directly, so a post-mount
-`[subtitle]` attribute update keeps propagating exactly as it did before
-this shim existed — once `[description]` is set directly (by attribute or
-property), it wins permanently and further `[subtitle]` churn is ignored.
+`[description]` is now the only prop — `[subtitle]` no longer resolves,
+mirrors, or warns (it is an inert attribute; the `subtitle` **slot** is
+unaffected and still renders custom content the same way it always did).
 
-### Migration (mechanical, recommended now / required at the 0.9.0 cut)
+### Migration (mechanical — already applied repo-wide in gh#1617)
 
 ```bash
 git grep -l '<action-item-ui\b' -- packages apps playgrounds site site-a2ui \
   | xargs perl -pi -e 's/(<action-item-ui\b[^>]*\b)subtitle=/\1description=/g'
 ```
 
-**Find every affected consumer site:**
+**Find every remaining consumer site (external consumers upgrading from
+pre-0.8.43):**
 
 ```bash
 npm run qa:contract-migration-scan -- --roots packages,apps,playgrounds,site,site-a2ui \
@@ -1819,9 +1807,6 @@ rg -nU '<action-item-ui\b[^>]*\bsubtitle=' \
 
 ### Rejected / deferred
 
-- The 0.9.0 breaking removal itself — deferred under the same "no breaking
-  rename in a patch" 2026-08-14 standing ruling every sibling rename-wave
-  entry in this guide follows.
 - `action-item-ui`'s `subtitle` **slot** (distinct from the prop) — left
   unrenamed by design, same as `menu-item-ui`'s own gh#1563 shape;
   renaming a slot is a different, unscoped surface.
@@ -1837,6 +1822,71 @@ npm run check
 
 ---
 
+## Shipped in `0.8.43` — three 0.8.41-era deprecated components removed (toggle-group-ui/toggle-option-ui, progress-row-ui, datetime-picker-ui, gh#1617)
+
+**BREAKING.** These three components shipped their `status: deprecated`
+soft-deprecation additively in `0.8.41` (each entry above) — behavior
+unchanged, a one-time `console.warn`, kept fully working. This cut removes
+them outright, per the operator ruling recorded on gh#1562 (IDR-0004
+deviation) that lifted all 0.9.0-parked breaking cuts onto `0.8.43`. Each
+alias's successor shipped ≥1 release before `0.8.43` (`0.8.41`, with
+`0.8.42` released in between) — the maturity guard gh#1617 verified
+against CHANGELOG/git history before cutting.
+
+### What changed (BREAKING, 0.8.43)
+
+| Removed component | Successor | Migration |
+|---|---|---|
+| `<toggle-group-ui>` + `<toggle-option-ui>` | `<segmented-ui multiple>` + `<segment-ui>` | `<toggle-group-ui value="…">` + `<toggle-option-ui>` children → `<segmented-ui multiple value="…">` + `<segment-ui>` children (identical comma-separated `value` encoding; `text`/`icon`/`disabled` map directly). `<toggle-group-ui single value="…">` → `<segmented-ui value="…">` (no `[multiple]`) |
+| `<progress-row-ui>` | `<progress-ui label meta>` | `<progress-row-ui label="…" value="…" meta="…">` → `<progress-ui label="…" value="…" meta="…">` (mechanical tag rename, identical attribute names). `variant` (color-family prop) has no successor — recolor via `--progress-fill` |
+| `<datetime-picker-ui>` | `<calendar-picker-ui precision="minute">` | `<datetime-picker-ui>` → `<calendar-picker-ui precision="minute">` (or `precision="second"`) |
+
+None of the three tags register as custom elements anymore — mounting
+one is inert markup (no upgrade, no shadow/light DOM stamped). The A2UI
+catalog identities `ToggleGroup`, `ToggleOption`, `ProgressRow`, and
+`DatetimePicker` are removed from `registry.js`; generation should never
+emit them.
+
+**Behavioral gap carried over from the `0.8.41` entry:** `<toggle-group-ui
+single>`'s clear-on-reclick has no `<segmented-ui>` equivalent — see the
+`0.8.41` entry above for the capture-phase workaround if a migrated
+consumer relied on it.
+
+### Migration (mechanical)
+
+```bash
+git grep -l '<toggle-group-ui\|<toggle-option-ui' -- packages apps playgrounds site site-a2ui \
+  -g '!*CHANGELOG*.md' -g '!**/dist/**' -g '!*.examples.md' -g '!*MIGRATION*' -g '!.claude/docs/**'
+# Rewrite by hand — this is a tag + structural rename, not an attribute
+# rename: parent AND child tags change, and `single` mode maps to
+# segmented-ui's OWN single-select (absence of [multiple]), not a prop.
+
+git grep -l '<progress-row-ui\b' -- packages apps playgrounds site site-a2ui \
+  | xargs perl -pi -e 's/<progress-row-ui\b/<progress-ui/g; s/<\/progress-row-ui>/<\/progress-ui>/g'
+
+git grep -l '<datetime-picker-ui\b' -- packages apps playgrounds site site-a2ui \
+  | xargs perl -pi -e 's/<datetime-picker-ui(\s|>)/<calendar-picker-ui precision="minute"\1/g; s/<\/datetime-picker-ui>/<\/calendar-picker-ui>/g'
+```
+
+**Find every remaining consumer site (external consumers upgrading from
+pre-0.8.43):**
+
+```bash
+rg -nU '<toggle-group-ui[^>]*>|<toggle-option-ui[^>]*>|<progress-row-ui[^>]*>|<datetime-picker-ui[^>]*>' \
+  -g '!*CHANGELOG*.md' -g '!**/dist/**' -g '!*.examples.md' -g '!*MIGRATION*' -g '!.claude/docs/**'
+```
+
+A hit means a broken page — none of these three tags register anymore.
+
+### Verify
+
+```bash
+node scripts/build/components.mjs --verify
+npm run check
+```
+
+---
+
 ## Migrating to `@adia-ai/*@v0.8.23` (2026-07-30)
 
 - **Removed: the `--a-font` alias** (pre-ADR-0035 name, DEPRECATED since the 0.8.x line). Any surviving `font-family: var(--a-font)` goes invalid-at-computed-value-time → `inherit` → UA **serif** — the visible symptom is Times-faced labels on an otherwise-correct page.

package/USAGE.md

@@ -1219,7 +1219,7 @@ For a compact swatch-and-popover authoring shape:
 </popover-ui>
 ```
 
-The popover handles focus management + click-outside dismiss; the button-ui exposes the right ARIA semantics. `<color-area-ui>` fires `change` events that bubble through the popover — listen on the popover host. (`<color-area-ui>` is the ADR-0063/gh#1563 rename of `<color-picker-ui>`, which still works as a deprecated alias — this recipe is exactly what `<color-input-ui>` canonicalizes.)
+The popover handles focus management + click-outside dismiss; the button-ui exposes the right ARIA semantics. `<color-area-ui>` fires `change` events that bubble through the popover — listen on the popover host. (`<color-area-ui>` is the ADR-0063/gh#1563 rename of `<color-picker-ui>`; the old tag was cut in 0.8.43, gh#1617 — this recipe is exactly what `<color-input-ui>` canonicalizes.)
 
 ### §221g — `[data-scheme]` ancestor opt-in for color scheme
 

package/color/index.js

@@ -1,6 +1,6 @@
 /**
  * @adia-ai/web-components/color — color-space conversion + gamut utilities
- * shared between primitives (color-picker, swatch, contrast-badge) and
+ * shared between primitives (color-area, swatch, contrast-badge) and
  * available to consumers as a standalone subpath.
  *
  * §301 (v0.5.12, FEEDBACK-29 re-bucket from v0.6.0). Pure functions; no

package/components/action-list/action-item.a2ui.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://adiaui.dev/a2ui/v0_9/components/ActionItem.json",
   "title": "ActionItem",
-  "description": "Child of <action-list-ui>. One actionable row — icon + label + optional\ndescription, forwards activation to the parent action-list. Row contract\nconverges on <menu-item-ui>: icon/text/description/value/variant/disabled\nprops and icon/text/subtitle/trailing slot overrides (#1363 C5).\n(`subtitle` is a deprecated alias for `description` — ADR-0063, gh#1571.)",
+  "description": "Child of <action-list-ui>. One actionable row — icon + label + optional\ndescription, forwards activation to the parent action-list. Row contract\nconverges on <menu-item-ui>: icon/text/description/value/variant/disabled\nprops and icon/text/subtitle/trailing slot overrides (#1363 C5). (The\ndeprecated `subtitle` prop alias for `description` was cut in 0.8.43 —\nADR-0063, gh#1571/gh#1617.)",
   "type": "object",
   "allOf": [
     {
@@ -14,7 +14,7 @@
   ],
   "properties": {
     "description": {
-      "description": "Optional secondary description line rendered under the label. Canonical spelling (ADR-0063, gh#1571) replacing `subtitle` — converges action-item onto the same spelling <menu-item-ui> adopted under gh#1563.",
+      "description": "Optional secondary description line rendered under the label. Canonical spelling (ADR-0063, gh#1571) replacing `subtitle` — converges action-item onto the same spelling <menu-item-ui> adopted under gh#1563. The deprecated `subtitle` prop alias was cut in 0.8.43 (gh#1617).",
       "type": "string",
       "default": ""
     },
@@ -30,11 +30,6 @@
       "description": "Leading icon name (Phosphor).",
       "type": "string"
     },
-    "subtitle": {
-      "description": "DEPRECATED (ADR-0063, gh#1571) — use `description` instead. Same type/default/rendered position; kept working as a dual-read compat shim (one-time console.warn when it's the name that resolves). Removed in 0.9.0. (The `subtitle` SLOT below is a separate surface, deliberately left unrenamed in this pass — see its own description.)",
-      "type": "string",
-      "default": ""
-    },
     "text": {
       "description": "Action label.",
       "type": "string"
@@ -85,7 +80,7 @@
         "description": "Override the [icon] glyph with a custom slotted element (custom icon-ui, image, avatar). Mutually exclusive with the [icon] attribute — slot child wins."
       },
       "subtitle": {
-        "description": "Custom secondary-line content override; falls through to the [description] prop (or its deprecated [subtitle] alias — ADR-0063, gh#1571) if not slotted. The slot's own name is unchanged by that rename — this is a distinct, deliberately-unrenamed surface."
+        "description": "Custom secondary-line content override; falls through to the [description] prop if not slotted (ADR-0063, gh#1571 — the deprecated [subtitle] prop alias was cut in 0.8.43, gh#1617). The slot's own name is unchanged by that rename — this is a distinct, deliberately-unrenamed surface."
       },
       "text": {
         "description": "Custom label content; falls through to [text] prop if not slotted."

package/components/action-list/action-item.yaml

@@ -19,8 +19,9 @@ description: |-
   Child of <action-list-ui>. One actionable row — icon + label + optional
   description, forwards activation to the parent action-list. Row contract
   converges on <menu-item-ui>: icon/text/description/value/variant/disabled
-  props and icon/text/subtitle/trailing slot overrides (#1363 C5).
-  (`subtitle` is a deprecated alias for `description` — ADR-0063, gh#1571.)
+  props and icon/text/subtitle/trailing slot overrides (#1363 C5). (The
+  deprecated `subtitle` prop alias for `description` was cut in 0.8.43 —
+  ADR-0063, gh#1571/gh#1617.)
 
 props:
   icon:
@@ -29,21 +30,13 @@ props:
   text:
     description: Action label.
     type: string
-  subtitle:
-    description: >-
-      DEPRECATED (ADR-0063, gh#1571) — use `description` instead. Same
-      type/default/rendered position; kept working as a dual-read compat
-      shim (one-time console.warn when it's the name that resolves).
-      Removed in 0.9.0. (The `subtitle` SLOT below is a separate surface,
-      deliberately left unrenamed in this pass — see its own description.)
-    type: string
-    default: ''
   description:
     description: >-
       Optional secondary description line rendered under the label.
       Canonical spelling (ADR-0063, gh#1571) replacing `subtitle` —
       converges action-item onto the same spelling <menu-item-ui> adopted
-      under gh#1563.
+      under gh#1563. The deprecated `subtitle` prop alias was cut in
+      0.8.43 (gh#1617).
     type: string
     default: ''
   value:
@@ -70,9 +63,10 @@ slots:
   subtitle:
     description: >-
       Custom secondary-line content override; falls through to the
-      [description] prop (or its deprecated [subtitle] alias — ADR-0063,
-      gh#1571) if not slotted. The slot's own name is unchanged by that
-      rename — this is a distinct, deliberately-unrenamed surface.
+      [description] prop if not slotted (ADR-0063, gh#1571 — the
+      deprecated [subtitle] prop alias was cut in 0.8.43, gh#1617). The
+      slot's own name is unchanged by that rename — this is a distinct,
+      deliberately-unrenamed surface.
   trailing:
     description: >-
       Trailing element pinned to the far edge (shortcut hint, badge, caret).
@@ -108,5 +102,5 @@ a2ui:
       reason: 'Converged with <menu-item-ui>''s danger-variant guidance (#1363 C5).'
     - rule: 'Prefer [icon]/[text]/[description] props over slotted markup; use slot="icon"/"text"/"subtitle"/"trailing" only for custom markup (e.g. a slotted <kbd> shortcut hint).'
       reason: 'Row-contract convergence with <menu-item-ui> (#1363 C5).'
-    - rule: 'NOTE (ADR-0063, gh#1571): [subtitle] is now a deprecated alias for [description] — kept as a dual-read compat shim (new-name precedence, one-time console.warn), removed at the 0.9.0 cut.'
+    - rule: 'NOTE (ADR-0063, gh#1571): the deprecated [subtitle] prop alias for [description] was cut in 0.8.43 (gh#1617) — [description] is the sole prop now.'
       reason: 'Convergence with <menu-item-ui>''s own subtitle -> description rename (gh#1563).'