@adia-ai/web-components 0.8.38 → 0.8.40

package/CHANGELOG.md

@@ -1,11 +1,41 @@
 # Changelog — @adia-ai/web-components
 
+## [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).
+- **`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).
+
+### Maintenance
+- **`dist/` bundles rebuilt** in this cut's window (6 file(s)) — regenerated from the source changes described above, not independent edits.
+
+## [0.8.39] — 2026-08-15
+
+### Changed
+- **`toggle-option-ui` converges onto `segment-ui`'s declared, parent-managed, reflected `[selected]` prop (ADR-0056, gh#1303).** Found by `framework-alignment-agent`'s corpus-wide component-state-naming sweep: the two same-role selection-item primitives named their "currently selected" state differently — `segment-ui` declared a reflected `selected: Boolean` prop (yaml → catalog → generative grammar), while `toggle-option-ui` had no declared state at all; the parent (`toggle-group-ui`) instead stamped a private `data-selected` attribute invisible to the yaml SoT, catalog, and A2UI grammar. `toggle-option-ui` gains `selected` (`Boolean`, default `false`, reflected) in `toggle-option.yaml` + `toggle-group.class.js`; `toggle-group-ui` now sets `selected` on its children (the `UIToggleOption` render pass stamps `aria-pressed` from it, mirroring `segment-ui`'s `aria-checked`-from-`selected` pattern); `toggle-group.css`'s `:scope[data-selected]` style rule becomes `toggle-option-ui[selected]` (moved outside `@scope`, same Safari-17.x attribute-restyle workaround `segment.css` already uses). Behavior, keyboard model, and the group's `value` as the single source of truth are unchanged. **SCOPING RULING (additive only, not the full ADR):** `toggle-group-ui` keeps stamping the legacy `data-selected` attribute on options in parallel, alongside the new `selected` prop — marked **DEPRECATED** in `toggle-option.yaml`/`toggle-group.yaml` — because it was an undocumented hook external CSS may already target; removing it is the breaking half of ADR-0056 and rides the ratified **0.9.0** breaking wave (alongside ADR-0052/0053/0054) rather than landing in this patch. `toggle-group.test.js` (new) covers the reflected `[selected]` + `aria-pressed` pairing, group-managed single-selection, multi-select, and the `data-selected` parallel-stamp deprecation case (named so it's obvious which test flips at 0.9.0 removal); `segmented.test.js` gains a regression check that `segment-ui`'s reference `[selected]`/`aria-checked` pairing is unchanged.
+### Fixed
+- **Trigger-caret sizing — the universal caret-size ruling (`--a-icon-size: var(--a-caret-size)`, encoded on `select-ui`'s trigger caret) is now applied consistently across the input/picker family (gh#1314).** `date-range-picker-ui`'s trigger caret never applied the rule at all, so it rode the ambient icon size and rendered visibly larger than `select-ui`'s caret in mixed control rows (e.g. the admin Finance Batches filter bar; consumer defect ADIA2-8729). Sweeping the rest of the trigger-caret family for the same class of miss found three more members: `datetime-picker-ui`'s trigger caret was missing the rule the same way; `combobox-ui`'s default caret-down suffix icon was sized off `--combobox-font-size` (the same value its leading/prefix icon correctly uses) instead of `--a-caret-size`; `calendar-picker-ui`'s `[slot="caret"]` was likewise sized off its own `--calendar-picker-font-size`. All four now resolve `--a-icon-size` to `--a-caret-size` on the caret glyph specifically (name-guarded on `combobox-ui`/date-picker family so a consumer-slotted non-caret glyph is unaffected), so every trigger caret in the family reads as one size. `time-picker-ui` was audited and excluded — it has no chevron/trigger caret (segmented inline input only). New/updated regression coverage in `date-range-picker.test.js`, `datetime-picker.test.js`, `combobox.test.js`, and a new `calendar-picker.test.js` asserts each caret rule's declared `--a-icon-size` computed value (CSS-source assertion — happy-dom doesn't evaluate `@scope` via `getComputedStyle`, same documented limitation as `badge.test.js`/`tag.test.js`).
+- **ADR-0055 — `command-ui`, `select-ui`'s searchable trigger, and `drilldown-ui`'s filter row no longer stamp a native `<input>` with no recorded ADR-0025 exception (gh#1302).** A corpus sweep (gh#1302) found three uncatalogued native `<input>` stamps: `command-ui`'s palette search field, `select-ui`'s searchable-trigger branch (ADR-0025's own compliant-list entry predated/overlooked this branch), and `drilldown-ui`'s filter row (found while decomposing the issue, not in the original report). ADR-0055 rules no new exceptions get added — all three are replaced with patterns already in-tree: `command-ui` and `select-ui`'s searchable branch now use a `contenteditable="plaintext-only"` span carrying `role="combobox"` (the `combobox-ui` pattern — placeholder via the `[data-empty]::before` pseudo, same mechanism as `input-ui`/`combobox-ui`); `drilldown-ui`'s filter row now composes `<input-ui raw>` (the `search-ui` precedent). Behavior parity verified by a per-surface browser probe (typing, filtering, Escape-clears-query, Backspace-doesn't-navigate-back for drilldown) — not tests alone. `agent-trace`'s native `<details>`/`<summary>` disclosure toggle is ruled explicitly out of ADR-0025's scope by the same ADR (carries no submittable value). `command.yaml` gains the `input` slot entry the CSS rewrite now positions (`audit-slot-vocab-vs-css`). `drilldown.yaml`'s `composes:` list gains `input-ui` (+ `button-ui`, previously undeclared for the back affordance).
+- **`scripts/dev/audit-stamped-native-buttons.mjs` extended to cover native `<input>` stamps, not just `<button>` (ADR-0055 follow-up, gh#1302).** Mirrors the existing button gate: no `createElement('input')` / `<input` in component source outside a `SANCTIONED_INPUT` map with a per-file reason. `input.class.js`'s `type="password"` branch is the one ADR-0025-named exception. Widening the scan surfaced pre-existing native `<input>` stamps outside gh#1302's audited scope — three `type="file"` OS-file-picker triggers (`chat-input.js`, `upload.class.js`, `admin-roster.js`) and two text-gathering surfaces (`otp-input.class.js`'s digit boxes, `table.class.js`'s filter-popover inputs) — all recorded as `PENDING` findings for a follow-up maintainer call, not fixed here (outside this issue's named scope).
+- **`modal-ui` — `close` now fires reliably on every programmatic dismissal, including a parent-driven teardown race that was the actual root cause (gh#1295, adiav2 ADIA2-8581).** `close` previously depended entirely on the native `<dialog>` element's own queued `close` task re-dispatching it, which a consumer's own re-render could tear down before it ran. Real-browser reproduction (a vitest/happy-dom harness alone can't see this) traced the true root cause further: EVERY internal close path only ever runs from `<modal-ui>`'s own render effect, which reacts to the `open` property write via a microtask (signals.js) — `disconnectedCallback()` disposes that effect unconditionally. A consumer whose Confirm/Cancel handler flips `open = false` and, on the SAME tick, unmounts the modal (an ordinary framework re-render shape) tears the effect down before `#animateClose`'s exit-animation timer is ever even created, so `close` never fires and any caller awaiting it (`showConfirmDialog`-style APIs) hangs forever — confirmed reproducing, and NOT fixed, against PR #1296's authoritative-timer-dispatch approach, since that timer is one of the things the teardown race skips creating. `disconnected()` now emits `close` as a last-resort teardown fallback whenever the modal was open or mid-close at disconnect time, guarded by a once-only dispatch flag shared with the two other paths (the native `<dialog>` `close` listener, kept as a redundant net; `#animateClose`'s own timer, now also an authoritative direct dispatch — both absorbed from PR #1296, which correctly diagnosed the duration/unit bug below but couldn't reproduce this teardown race). `#getDuration()` also no longer silently drops a `s` vs `ms` unit on `--modal-duration` (`parseFloat('.25s')` read as `0.25`, a 0.25ms timer instead of 250ms — PR #1296's fix, kept as-is). `modal.test.js` gains per-dismissal-path close-emission coverage (button, Escape, backdrop, direct `.open=false`, raw `dialog.close()`, no-double-fire, re-open reset) plus the teardown-race repro itself.
+
+### Added
+- **`nav-ui` — selecting a page now collapses every expanded group except the one containing the newly selected item (gh#1306).** Previously, `select()` only moved `[selected]` between items and never touched group `[open]` state, so any group a consumer or the collapsed-rail popover had expanded stayed expanded indefinitely, even after navigating elsewhere. Default-on: `select()` now closes every top-level `<nav-group-ui>` except the selected item's ancestor group (all groups, when the selection is ungrouped) — manual multi-expansion is still allowed right up until the next selection. New `[multi-expand]` attribute opts a consumer out, keeping every manually expanded group open across selections. Applies to every `select()` entrypoint: click, keyboard, programmatic, and the collapsed-rail popover option click (`nav-group.class.js`'s `showPopover()`, which itself calls `nav.select()`).
+
+### Maintenance
+- **`components/` touched in this release window** (39 file(s), e.g. `calendar-picker/calendar-picker.css`) — 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.
+
 ## [0.8.38] — 2026-08-15
 
 ### Added
 - **`drilldown-ui` — a new single-panel, multi-level drill-in menu primitive (gh#1285).** Replaces the hand-rolled miller-columns shape (two stacked list columns) that adiav2's Schema Manager had to build because the kit had no drill-down primitive — cleared the pre-build audit against `tree-ui` (inline expand/collapse, wrong for wide/deep >2-level data), `segmented-ui` (no overflow behavior for 18 namespaces), `tag-ui`-as-menu (no keyboard path), `list-ui`/`nav-ui`/`menu-ui`/`context-menu`/`breadcrumb-ui` (flat, not hierarchical drill-in) — none provide single-panel level-swap navigation with back/focus-restoration. Data-driven (`.items` tree of `{value, label, meta?, dot?, counts?, children?}` nodes; `children` may be sync or an async `(item) => array | Promise<array>` lazy loader, rendering a `<skeleton-ui>` loading level while pending). Full keyboard path (roving-tabindex listbox per level; ArrowRight/Enter drills in, ArrowLeft/Backspace goes back with focus restored to the item drilled from), `select` + `navigate` events, a `path` property that reflects to a JSON-encoded attribute both ways (hand-managed, not the generic `reflect:` mechanism — array values don't round-trip through `String(v)`) for deep-link/URL restore, `[filterable]` filter input, `[select-on-drill]` mode flag, a `breadcrumb` slot, row-native trailing count chips (not full `<badge-ui>`, which reads oversized at row density), and a horizontal slide transition that honors `prefers-reduced-motion: reduce` automatically (also suppressible via `[static]`).
 
 ### Fixed
+- **`swatch-ui` — auto-contrast label/detail colors no longer fall back to raw hex, and detail-line dimming no longer uses `color-mix()`.** Found by a new `framework-alignment-agent` cohesion sweep: `--a-chrome-light`/`--a-chrome-dark` are always-defined foundational tokens (`styles/colors/semantics/features.css:124-125`), so the `var(--a-chrome-light, #fafafa)` / `var(--a-chrome-dark, #111)` fallbacks on the `[auto-contrast]` label rules were dead weight and a raw-CSS-color violation. The detail-line dimming also swapped `color-mix(in oklab, …, transparent)` for the plain token color plus `opacity` — not a browser-support fix (`color-mix()` is this repo's documented, Baseline-supported convention per `ADR-0007`/`BROWSER-COMPAT.md`), but a deliberate preference for a literal token over a computed color derivation.
 - **`page-ui` header now ships the slot-gated grid its docs promised (gh#1253).** ADR-0009 recorded the named-slot vocabulary (`slot="icon"` / `slot="heading"` / `slot="action"`) as wired into four containers — Card, Drawer, Modal, and Page — but `page.css` never shipped its half; the slot attributes on a page header's children were dead metadata, so a block-level action child (e.g. `<toggle-scheme-ui>`) dropped to its own row instead of clustering. `page.css` gains the same `:has(> [slot])`-gated header grid as `card.css` (icon/heading/action columns, direct-child guard against nested false-positives), plus the `--page-header-gap` / `--page-heading-*` tokens `card-ui`'s pair already had. `page.yaml`'s `slots.default` and `page.examples.html` (new "Header slot-gated grid" demo) now describe the contract that's actually implemented.
 - **`nav-ui` / `nav-item-ui` — `nav-select` now fires exactly once per click, and zero times re-clicking the already-selected item (gh#1254).** Root cause: two layered click handlers both drove selection for the same physical click — `nav-item-ui`'s own click handler called `nav.select(this)` *and* dispatched its own `nav-select`, while `nav-ui`'s click-delegation listener matched the same item on bubble and called `select()` again — three dispatches per click. `nav.select()` is now the single source of the event (idempotent: a no-op, including no hover-flush, when the item is already selected); `nav-item-ui` no longer dispatches its own copy, and `nav-ui`'s click listener no longer delegates item selection (it now only handles group expand/popover).
 - **`view-transition` trait — no longer leaks unhandled `AbortError` rejections when a transition is superseded (gh#1255).** Only `transition.finished` had a `.catch()`; `ready` and `updateCallbackDone` are distinct promises that also reject (with `AbortError`) when a newer transition supersedes this one, and were previously uncaught. All three are now swallowed on abort — expected behavior for rapid navigation, not an error — with `fireEnd()` still driven solely by `finished`.

package/MIGRATION.md

@@ -54,6 +54,14 @@ Version cuts and migration scope:
 
 - **`0.8.37`** — PATCH lockstep cut. **BREAKING: the a2ui / gen-ui estate split (ADR-0048).** Six published package names (`a2ui-runtime`, `a2ui-compose`, `a2ui-corpus`, `a2ui-retrieval`, `a2ui-validator`, `a2ui-mcp`) are replaced by four (`a2ui`, `gen-ui`, `gen-ui-mcp`, `a2ui-protocol-mcp`). **A patch-shaped version number does not make this non-breaking** — every old name is renamed. One-cycle re-export shims bridge the gap; the cut AFTER `0.8.37` retires them. See [§ 0.8.37 — the a2ui / gen-ui estate split](#0837--the-a2ui--gen-ui-estate-split-adr-0048).
 
+- **Upcoming (`0.8.40` — attribute-grammar reconciliation, ADR-0054)** — **BREAKING, no deprecation alias:** `table-ui[density]` converges onto the ambient global `[density]` attribute — the component-local `compact`/`standard`/`comfortable` enum is removed. Migration: `density="compact"` stays `density="compact"`; `density="standard"` → drop the attribute (unset is the default); `density="comfortable"` → `density="spacious"`. `chart-ui[radius]` renames to `chart-ui[corner-radius]` (same `Number`/`null` semantics, same `--a-radius` fallback) — a mechanical attribute-name rename, no value-shape change. `swatch-ui[color]` and `noodles-ui[color]` are ratified exceptions and are unaffected. See [§ Upcoming — 0.8.40 attribute-grammar reconciliation](#upcoming-0840-attribute-grammar-reconciliation-adr-0054).
+
+- **Upcoming (`qr-code-ui` quiet-zone rename, `0.8.40`)** — **BREAKING:** `<qr-code-ui>`'s reflected `[margin]` attribute is renamed `[quiet-zone]` (property `quietZone`) — same type, default (`4`), and reflection; only the name changes, per [ADR-0053](../../docs/adr/adr-0053-no-shadowing-global-attributes.md). `margin` on `qr-code-ui` now means the framework's **global** `[margin]` Scale attribute (box-model spacing), not the QR quiet zone — the two grammars silently collided on the same syntax with unrelated meanings. **No deprecation alias** — keeping `margin` as an alias would preserve the collision the rename exists to remove. Audit existing usages: `<qr-code-ui margin="4">` intending a quiet zone must become `<qr-code-ui quiet-zone="4">`. Ships in `0.8.40`. See [§ Upcoming — qr-code-ui quiet-zone rename](#upcoming--qr-code-ui-quiet-zone-rename-adr-0053).
+
+- **Upcoming (leading-scale consolidation, `0.8.40`)** — **BREAKING, no aliases:** the legacy `--a-leading-*` token family is removed per [ADR-0052](../../docs/adr/adr-0052-leading-scale-consolidation.md) — `--a-font-leading-*` (+ new `--a-font-leading-none: 1` step) is now the single canonical leading scale. Value-nearest replacement table: `none→--a-font-leading-none` (1), `tight→--a-font-leading-snug` (1.2), `snug→--a-font-leading-normal` (1.35), `normal→--a-font-leading-relaxed` (1.5). The same gh#1298 sweep also tokenized every hardcoded `line-height`/`letter-spacing`/`font-weight` literal across `packages/web-components/components/*/*.css` (1.3 and 1.4 both → `--a-font-leading-normal`; 0.05em → `--a-font-tracking-wide`) and added a mechanized `npm run check:typography-tokens` gate. See [§ Upcoming — leading-scale consolidation](#upcoming--leading-scale-consolidation-adr-0052).
+
+- **Upcoming (`toggle-option-ui` drops `data-selected`, `0.8.40`)** — **BREAKING, no deprecation alias:** `<toggle-group-ui>`'s legacy `data-selected` parallel stamp on its `<toggle-option-ui>` children is removed per [ADR-0056](../../docs/adr/adr-0056-selection-item-selected-convention.md) — the declared, reflected `selected` prop (shipped additively in `0.8.39`) is now the only current-state surface, matching `<segment-ui>`'s convention. Migration: any `[data-selected]` CSS or script targeting `toggle-option-ui` moves to `[selected]`. See [§ Upcoming — `toggle-option-ui` drops the legacy `data-selected` stamp](#upcoming--toggle-option-ui-drops-the-legacy-data-selected-stamp-0840-adr-0056).
+
 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.
 
 ---
@@ -79,8 +87,9 @@ The split is by concept, ruled in `docs/adr/adr-0048-a2ui-gen-ui-estate-split.md
   `@adia-ai/a2ui-protocol-mcp`, before either ever published) ships one bin,
   `adia-mcp`, dispatching two subcommands as separate processes:
   `adia-mcp gen-ui` (30 tools — the generation surface, direct successor of
-  `@adia-ai/a2ui-mcp`) and `adia-mcp protocol` (4 tools — `validate_document`,
-  `get_registry_map`, `get_wiring_registry`, `protocol_status`; renamed off
+  `@adia-ai/a2ui-mcp`) and `adia-mcp protocol` (4 tools at the fold — `validate_document`,
+  `get_registry_map`, `get_wiring_registry`, `protocol_status`, joined since by
+  `get_catalog_ladder`; the first four renamed off
   their original same-named-as-`gen-ui`-surface forms by gh#1248 before this
   server ever published). The name `@adia-ai/a2ui-mcp` is **burned, never
   reused**: it means "the generation MCP" to every consumer that has it
@@ -383,6 +392,238 @@ npm run check   # in-repo consumers; downstream: your app's build + a visual pas
 
 ---
 
+## Upcoming — `0.8.40` attribute-grammar reconciliation (ADR-0054)
+
+**BREAKING, no deprecation alias.** [ADR-0054](../../docs/adr/adr-0054-attribute-grammar-reconciliation.md)
+resolves two component-local attributes that shadowed the [global attribute
+grammar](../../.claude/docs/specs/attribute-api-system.md) with divergent vocabularies —
+`table-ui[density]` **converges** onto the global mechanism (it already did
+the job), `chart-ui[radius]` **renames** (a numeric px value is a genuinely
+different shape than the global preset enum). Per [ADR-0053](../../docs/adr/adr-0053-no-shadowing-global-attributes.md),
+neither collision is exempted — `swatch-ui[color]` / `noodles-ui[color]` are
+the only two ratified exceptions (documented in
+[§11 of attribute-api-system.md](../../.claude/docs/specs/attribute-api-system.md#11-global-attribute-exemption-list)),
+and neither is touched by this cut.
+
+### `table-ui[density]` converges onto the global grammar
+
+The component-local `compact | standard | comfortable` enum is removed —
+`table-ui` no longer reflects a `density` prop or JS property at all.
+`[density]` on `table-ui` is now the ordinary ambient global attribute
+(`compact | spacious`, unset = the middle) — `--table-py`/`--table-px`
+already derive from `--a-space-*` steps, which the global `[density]`
+attribute already scales via `--a-density`.
+
+**Value migration** (apply wherever `<table-ui density="…">` appears):
+
+| Old value | New value |
+|---|---|
+| `density="compact"` | `density="compact"` (unchanged) |
+| `density="standard"` | drop the attribute entirely (unset is the default) |
+| `density="comfortable"` | `density="spacious"` |
+
+```bash
+# find every table-ui density usage in your tree
+git grep -nE '<table-ui[^>]*\bdensity='
+
+# comfortable → spacious (mechanical)
+git grep -lz '<table-ui[^>]*density="comfortable"' | while IFS= read -r -d '' f; do
+  perl -i -pe 's/(<table-ui[^>]*density=")comfortable(")/${1}spacious${2}/g' "$f"
+done
+
+# standard → drop the attribute (review each hit; not always a safe blind sed
+# across multi-line tags)
+git grep -nE '<table-ui[^>]*density="standard"'
+```
+
+If you read/write a table's `density` as a JS property (`el.density`) or
+persisted it via `table-ui`'s `getState()`/`setState()`, switch to
+`getAttribute('density')`/`setAttribute('density', …)` — the reflected
+property and the `getState()`/`setState()` `density` key are both gone.
+Composites that forward density to an embedded `table-ui` (own component,
+own vocabulary) must translate through the same table above before setting
+the child's attribute — see `invoice-history.class.js`'s `mapDensity()` for
+the pattern.
+
+### `chart-ui[radius]` renames to `chart-ui[corner-radius]`
+
+Same `Number` type, same `default: null` (falls back to `--a-radius`), same
+behavior — only the attribute name changes.
+
+```bash
+git grep -nE '<chart-ui[^>]*\bradius='
+git grep -lz '<chart-ui[^>]*radius="' | while IFS= read -r -d '' f; do
+  perl -i -pe 's/(<chart-ui[^>]*)\bradius=/${1}corner-radius=/g' "$f"
+done
+```
+
+If you set it via JS, `chart.radius = 8` → `chart.cornerRadius = 8`.
+
+### Verify
+
+```bash
+git grep -nE '<table-ui[^>]*\bdensity="(standard|comfortable)"'  # must be 0
+git grep -nE '<chart-ui[^>]*\bradius='                           # must be 0
+npm run check
+```
+
+---
+
+## Upcoming — qr-code-ui quiet-zone rename (ADR-0053)
+
+**BREAKING, ships in `0.8.40`.** `<qr-code-ui>`'s reflected `[margin]` attribute is
+renamed `[quiet-zone]` (property `quietZone`) — same `number` type, same default (`4`), same
+reflection; only the name changes.
+
+**Why:** the framework's global attribute grammar (`styles/api/*.css`) is a pitch — one
+grammar, inferable: `margin="4"` means the same thing on every element, resolving through one
+Scale mechanism (`--a-margin`). `qr-code-ui` declared its own reflected `margin` meaning the QR
+"quiet zone" in grid cells. Both grammars accepted the identical syntax with no error surfaced,
+so an author reaching for `<qr-code-ui margin="4">` expecting global spacing silently got a
+quiet-zone resize instead, and vice versa. [ADR-0053](../../docs/adr/adr-0053-no-shadowing-global-attributes.md)
+rules that no component-local attribute may shadow a global one; this is the first instance
+resolved under that policy (gh#1299).
+
+**No deprecation alias.** Keeping `margin` as an alias on `qr-code-ui` would preserve the exact
+collision the rename exists to remove — `margin` on `qr-code-ui` reverts to meaning what it
+means everywhere: the global Scale attribute.
+
+### Mechanical sweep
+
+```bash
+git grep -nE '<qr-code-ui[^>]*\smargin='
+```
+
+Every hit intending the QR quiet zone becomes `quiet-zone`:
+
+```html
+<!-- before -->  <qr-code-ui value="…" margin="4"></qr-code-ui>
+<!-- after  -->  <qr-code-ui value="…" quiet-zone="4"></qr-code-ui>
+```
+
+**Programmatic setters** (JS render paths — the grep above misses these):
+
+```bash
+git grep -rnE "setAttribute\('margin', |\.margin\s*="
+```
+
+Filter to `qr-code-ui` hosts only — `margin` is a legitimate global attribute on every other
+element, so only rewrite a hit that is actually a `<qr-code-ui>` reference:
+`setAttribute('margin', …)` → `setAttribute('quiet-zone', …)`; `el.margin = …` → `el.quietZone
+= …`.
+
+### Verify
+
+```bash
+git grep -nE '<qr-code-ui[^>]*\smargin='   # must be 0
+npm run check                              # in-repo consumers; downstream: your app's build
+```
+
+---
+
+## Upcoming — leading-scale consolidation (ADR-0052)
+
+**BREAKING, no aliases, ships in `0.8.40`.** [ADR-0052](../../docs/adr/adr-0052-leading-scale-consolidation.md)
+retires the legacy `--a-leading-*` family. `--a-font-leading-*` is now the
+single canonical line-height scale.
+
+**Why:** two leading-token families coexisted in `scale.css` with the same
+step names resolving to *different* values (`--a-leading-snug` = `1.3` vs.
+`--a-font-leading-snug` = `1.2`). A component author reaching for a leading
+token had no obviously-correct choice — which is why a corpus-wide sweep
+(gh#1298) found 55 component files reaching for a bare numeric literal
+instead of either family. `--a-font-leading-*` is what the L2 role layer
+already consumes and its shape (tightening as size grows) is the design
+intent on record. One step closes its only gap: `--a-font-leading-none: 1`.
+
+**No value-preserving aliases.** `snug`/`normal` name different values
+across the two families — aliasing one name to the other would silently
+restyle every consumer of the alias. Replacement table (value-nearest, not
+name-preserving):
+
+| Removed | Value | Replacement | Value |
+|---|---|---|---|
+| `--a-leading-none` | `1` | `--a-font-leading-none` | `1` |
+| `--a-leading-tight` | `1.2` | `--a-font-leading-snug` | `1.2` |
+| `--a-leading-snug` | `1.3` | `--a-font-leading-normal` | `1.35` |
+| `--a-leading-normal` | `1.5` | `--a-font-leading-relaxed` | `1.5` |
+
+A surviving `var(--a-leading-*)` reference goes invalid-at-computed-value-time
+→ inherit (same failure shape as the `--a-font` alias removal in `0.8.23`).
+
+### The same sweep also tokenized every other hardcoded typography literal
+
+Beyond the legacy family, gh#1298's corpus sweep found — and tokenized —
+every bare numeric `line-height`, `em`-literal `letter-spacing`, and numeric
+`font-weight` in `packages/web-components/components/*/*.css`:
+
+- **`line-height`** — mapped to the nearest `--a-font-leading-*` step. Both
+  `1.3` and `1.4` map to `--a-font-leading-normal` (`1.35`) — no new step was
+  minted (at the 12–14px sizes where these values appeared, ±0.05
+  line-height is below visual significance). A handful of `1.4` hits on
+  genuinely multi-line body/description copy were mapped up to
+  `--a-font-leading-relaxed` (`1.5`) instead, case-by-case — see the sweep
+  PR description for the enumerated list. `line-height: 0` (the
+  icon/line-box-collapse idiom used by `icon.css`, `swatch.css`,
+  `qr-code.css`, etc.) is **not** a typographic leading value and was left
+  untouched.
+- **`letter-spacing`** — mapped to the nearest `--a-font-tracking-*` step;
+  `0.05em` (off-scale) maps to `--a-font-tracking-wide` (`0.04em`), same
+  nearest-step logic as the leading family.
+- **`font-weight`** — all hits were already on-scale and map mechanically to
+  `--a-weight-*` (`500`→medium, `600`→semibold, `700`→bold).
+
+### A mechanized gate follows the sweep
+
+`npm run check:typography-tokens` (wired into the `npm run check` aggregate)
+fails on any bare numeric `line-height`, `em`-literal `letter-spacing`, or
+numeric `font-weight` reappearing in `packages/web-components/components/*/*.css`
+— mirroring the existing brand-chrome/foundation-layer audit gates — so the
+parallel scale (and the literal-reaching it caused) cannot silently
+reaccumulate.
+
+### Mechanical sweep
+
+```bash
+git grep -nE -- '--a-leading-(none|tight|snug|normal)\b'
+```
+
+Apply the replacement table above at each hit — do not blind-`sed`, since
+`snug`/`normal` map to *different* replacement names than their own name
+would suggest.
+
+### Verify
+
+```bash
+git grep -nE -- '--a-leading-(none|tight|snug|normal)\b'   # must be 0
+npm run check:typography-tokens                              # must exit 0
+npm run check
+```
+
+---
+
+## Upcoming — `toggle-option-ui` drops the legacy `data-selected` stamp (`0.8.40`, ADR-0056)
+
+**BREAKING, no deprecation alias.** [ADR-0056](../../docs/adr/adr-0056-selection-item-selected-convention.md)'s
+breaking half removes `<toggle-group-ui>`'s legacy `data-selected` attribute
+stamp on its `<toggle-option-ui>` children. The declared, reflected `selected`
+prop (shipped additively in `0.8.39`) is now the *only* current-state surface
+— matching `<segment-ui>`'s existing convention.
+
+**Migration:** any external CSS or script targeting `[data-selected]` on
+`toggle-option-ui` must move to `[selected]` — same semantics, same timing,
+just the attribute name. `toggle-group.css` itself already styled
+`[selected]`; the removed stamp was a parallel, undocumented hook with no
+declared API surface (invisible to the yaml SoT, the catalog, and the A2UI
+grammar).
+
+```bash
+git grep -n "data-selected" -- '*.css' '*.js' '*.html' | grep -i toggle   # must be 0
+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/components/agent-artifact/agent-artifact.css

@@ -80,7 +80,7 @@
      uppercase kind reads as a tag, not a label. */
   [data-artifact-kind] {
     flex-shrink: 0;
-    letter-spacing: 0.04em;
+    letter-spacing: var(--a-font-tracking-wide);
   }
 
   [data-artifact-actions] {

package/components/agent-reasoning/agent-reasoning.css

@@ -171,7 +171,7 @@
     display: grid;
     grid-template-columns: subgrid;
     align-items: center;
-    line-height: 1.5;
+    line-height: var(--a-font-leading-relaxed);
     color: var(--agent-reasoning-fg-muted);
     animation: _ar-fade var(--agent-reasoning-duration) var(--agent-reasoning-easing);
   }
@@ -199,7 +199,7 @@
     font-size: var(--agent-reasoning-font);
     color: var(--agent-reasoning-fg-subtle);
     text-transform: uppercase;
-    letter-spacing: 0.04em;
+    letter-spacing: var(--a-font-tracking-wide);
     font-weight: var(--agent-reasoning-weight-heading);
   }
 

package/components/agent-trace/agent-trace.css

@@ -167,7 +167,7 @@
   [data-trace-header] {
     font-size: calc(var(--agent-trace-font) * 0.85);
     text-transform: uppercase;
-    letter-spacing: 0.06em;
+    letter-spacing: var(--a-font-tracking-wider);
     font-weight: var(--a-weight-medium);
     color: var(--agent-trace-fg-subtle);
   }
@@ -289,7 +289,7 @@
     font-size: calc(var(--agent-trace-label-font) * 0.85);
     font-weight: var(--a-weight-medium);
     text-transform: uppercase;
-    letter-spacing: 0.06em;
+    letter-spacing: var(--a-font-tracking-wider);
     padding-block-end: var(--a-space-1);
   }
 
@@ -301,7 +301,7 @@
     grid-template-columns: 1em 1fr;
     column-gap: var(--agent-trace-inline-gap);
     align-items: baseline;
-    line-height: 1.5;
+    line-height: var(--a-font-leading-relaxed);
     font-size: var(--agent-trace-font);
     color: var(--agent-trace-fg);
   }

package/components/alert/alert.css

@@ -207,7 +207,7 @@
   :scope[pattern="dunning"] [data-dunning-amount] {
     font-family: var(--alert-amount-font);
     font-variant-numeric: tabular-nums;
-    font-weight: 600;
+    font-weight: var(--a-weight-semibold);
     /* Inherit color from the variant; tabular-nums + monospace make
        the amount the scannable focal datum. */
   }

package/components/avatar/avatar.css

@@ -46,7 +46,7 @@
   [slot="initials"] {
     user-select: none;
     text-transform: uppercase;
-    line-height: 1;
+    line-height: var(--a-font-leading-none);
   }
 
   /* ── Icon (non-person avatar) ──

package/components/badge/badge.css

@@ -89,7 +89,7 @@
     font-family: var(--badge-font-family);
     font-size: var(--badge-font-size);
     font-weight: var(--badge-weight);
-    line-height: 1;
+    line-height: var(--a-font-leading-none);
     /* ── Register (issue 845) — uppercase + tracking + tabular numerals is the
        badge/tag differentiator now that geometry is shared (see the
        --badge-radius note above). Tag stays proportional sentence-case at

package/components/button/button.css

@@ -89,10 +89,11 @@ button-ui[variant="ghost"][color="warning"]:not([disabled]):hover   { --button-f
        blocks), but the label's ::after clips to its own line box, so
        inheriting 1 makes half-leading negative and shears descenders
        (g/j/p/q/y, parentheses) by ~0.93px at the default size — gh#906.
-       Snug (1.3) contains the font's content box at every [size]; the
+       Normal (1.35) contains the font's content box at every [size]; the
        precedent is stat.css:174,198 setting leading on the truncating
-       box rather than on the component root. */
-    --button-label-line-height: var(--a-leading-snug);
+       box rather than on the component root. Value-nearest migration from
+       the retired --a-leading-snug (1.3) — ADR-0052. */
+    --button-label-line-height: var(--a-font-leading-normal);
     --button-gap:              var(--a-space-1);
     --button-bg-hover:         var(--a-bg-strong);   /* neutral fill → neutral -strong surface on hover */
     --button-fg-hover:         var(--a-ui-text-hover);
@@ -160,7 +161,7 @@ button-ui[variant="ghost"][color="warning"]:not([disabled]):hover   { --button-f
     font-family: var(--button-font-family);
     font-size: var(--button-font-size);
     font-weight: var(--button-font-weight);
-    line-height: 1;
+    line-height: var(--a-font-leading-none);
     cursor: pointer;
     user-select: none;
     transition:
@@ -211,7 +212,7 @@ button-ui[variant="ghost"][color="warning"]:not([disabled]):hover   { --button-f
     border: 1px solid var(--button-trailing-border);
     border-radius: var(--button-trailing-radius);
     padding: 0 var(--button-trailing-px);
-    line-height: 1;
+    line-height: var(--a-font-leading-none);
     /* Recolor a <kbd-ui slot="trailing"> pill via kbd's OWN tokens so it tracks
        the button label color on every variant (primary white, ghost subtle,
        colored fills). kbd-ui's `:scope { color: var(--kbd-fg) }` wins over the

package/components/calendar-picker/calendar-picker.css

@@ -141,7 +141,7 @@
     border-radius: var(--calendar-picker-trigger-radius);
     background: var(--calendar-picker-trigger-bg);
     color: var(--calendar-picker-trigger-fg);
-    line-height: 1;
+    line-height: var(--a-font-leading-none);
     cursor: pointer;
     transition:
       border-color var(--calendar-picker-duration) var(--calendar-picker-easing),
@@ -178,7 +178,10 @@
 
   [slot="caret"] {
     flex-shrink: 0;
-    --a-icon-size: var(--calendar-picker-font-size);
+    /* Universal caret size (gh#1314 sweep) — was riding the trigger's
+       font-size instead of the shared --a-caret-size token select-ui's
+       trigger caret already reads. */
+    --a-icon-size: var(--a-caret-size);
   }
 }
 

package/components/card/card.css

@@ -271,7 +271,7 @@
   & > header > :is(text-ui[variant="display"], text-ui[variant="title"], text-ui[variant="heading"], text-ui[variant="subsection"]):not([slot]),
   & > header > [slot="heading"] :is(h1, h2, h3, h4, h5, h6) {
     grid-row: 1;
-    line-height: 1.3;
+    line-height: var(--a-font-leading-normal);
     margin: 0;
   }
   /* Heading slot is a flex container — can hold title + inline badges/metadata.
@@ -304,7 +304,7 @@
   & > header > :is(text-ui[variant="body"], text-ui[variant="caption"]):not([slot]) {
     grid-row: 2;
     grid-column: 1 / -1;
-    line-height: 1.4;
+    line-height: var(--a-font-leading-relaxed);
     margin: 0;
   }
   & > header:has(> [slot="icon"]) > :is([slot="description"], p, small) { grid-column: 2 / -1; }
@@ -489,7 +489,7 @@
     font-size: var(--card-font-size);
     font-weight: var(--a-weight-medium);
     color: var(--card-heading-fg);
-    line-height: 1.3;
+    line-height: var(--a-font-leading-normal);
     margin: 0;
     flex: 0 0 auto;
   }

package/components/chart/chart.a2ui.json

@@ -53,6 +53,11 @@
     "component": {
       "const": "Chart"
     },
+    "cornerRadius": {
+      "description": "Bar corner radius in px (null = let CSS tokens decide)",
+      "type": "number",
+      "default": null
+    },
     "data": {
       "description": "JS property (set programmatically — `el.data = [...]`). An array of plain objects; each object's keys are named by the `x` and `y` attributes — e.g. `<chart-ui x=\"month\" y=\"revenue\">` consumes `[{month:'Jan', revenue:3200}, {month:'Feb', revenue:4100}]`. The Chart.js `{labels, datasets}` envelope is NOT chart-ui's API — passing it (or any non-array value) renders an empty chart. May also be supplied declaratively as a JSON-array `data=\"[…]\"` attribute, hydrated once at connect. Custom accessor on the element class, not a reflected attribute.",
       "$ref": "common_types.json#/$defs/DynamicObjectList"
@@ -99,11 +104,6 @@
       "type": "boolean",
       "default": false
     },
-    "radius": {
-      "description": "Bar corner radius (null = let CSS tokens decide)",
-      "type": "number",
-      "default": null
-    },
     "seriesEmphasis": {
       "description": "Multi-line only. Names one series key (matching a `y` key) to render at full strength — area fill + full-opacity line. Every other series drops its area fill and renders line-only at --chart-deemphasized-opacity. Empty (default) applies full treatment to every series, unchanged from pre-gh#561 behavior.",
       "type": "string",

package/components/chart/chart.class.js

@@ -25,7 +25,7 @@
  *   color        — accent/success/warning/danger/info
  *   hide-grid    — hide gridlines
  *   hide-values  — hide value labels
- *   radius       — bar corner radius (default: 4)
+ *   corner-radius — bar corner radius in px (default: null, falls back to --a-radius)
  *   dots         — line/multi-line marker visibility: all|none|hover|last (default: all)
  *   series-emphasis — multi-line: series key that keeps full area+line treatment; others render line-only, dimmed
  *
@@ -219,7 +219,7 @@ export class UIChart extends UIElement {
     color:       { type: String,  default: '',       reflect: true },
     hideGrid:    { type: Boolean, default: false,    reflect: true, attribute: 'hide-grid' },
     hideValues:  { type: Boolean, default: false,    reflect: true, attribute: 'hide-values' },
-    radius:      { type: Number,  default: null,     reflect: true },
+    cornerRadius: { type: Number, default: null,     reflect: true, attribute: 'corner-radius' },
     smooth:      { type: Number,  default: 0.4,      reflect: true },
     size:        { type: String,  default: '',       reflect: true },
     format:      { type: String,  default: 'abbr',   reflect: true },
@@ -255,11 +255,11 @@ export class UIChart extends UIElement {
      re-render without a full DOM query. */
   #activeDotEl = null;
 
-  /** Resolves the corner radius: the `radius` prop if explicitly set,
+  /** Resolves the corner radius: the `cornerRadius` prop if explicitly set,
    *  otherwise `--a-radius` from the host's computed style. Falls back
    *  to 6 if the token is unset (should not happen in practice). */
   #resolveRadius() {
-    if (this.radius != null) return this.radius;
+    if (this.cornerRadius != null) return this.cornerRadius;
     const val = getComputedStyle(this).getPropertyValue('--a-radius').trim();
     const parsed = parseFloat(val);
     return Number.isFinite(parsed) && parsed > 0 ? parsed : 6;

package/components/chart/chart.css

@@ -176,7 +176,7 @@
 
   [data-value] {
     font-size: var(--chart-font-size);
-    font-weight: 600;
+    font-weight: var(--a-weight-semibold);
     fill: var(--chart-value);
     font-family: var(--chart-font);
   }
@@ -265,7 +265,7 @@
   [data-avg-label] {
     fill: var(--chart-avg);
     font-family: var(--chart-font);
-    font-weight: 600;
+    font-weight: var(--a-weight-semibold);
   }
 
   /* ── Radar ── */
@@ -388,7 +388,7 @@
   /* ── Donut center text ── */
 
   [data-donut-total] {
-    font-weight: 700;
+    font-weight: var(--a-weight-bold);
     fill: var(--chart-fg);
     font-family: var(--chart-font);
     /* font-size set by JS on the element — scales with donut radius */
@@ -719,7 +719,7 @@
   color: var(--chart-tooltip-fg);
   font-family: var(--a-font-family);
   font-size: var(--a-ui-sm);
-  line-height: 1.35;
+  line-height: var(--a-font-leading-normal);
   border: none;
   border-radius: var(--chart-tooltip-radius);
   box-shadow: var(--chart-tooltip-shadow);
@@ -741,11 +741,11 @@
   font-size: var(--a-ui-tiny);
   opacity: 0.75;
   text-transform: uppercase;
-  letter-spacing: 0.04em;
+  letter-spacing: var(--a-font-tracking-wide);
 }
 
 .chart-tooltip-popup [data-tip-role="label"] {
-  font-weight: 500;
+  font-weight: var(--a-weight-medium);
 }
 
 .chart-tooltip-popup [data-tip-role="value"] {

package/components/chart/chart.d.ts

@@ -22,6 +22,8 @@ export class UIChart extends UIElement {
   type: 'bar' | 'line' | 'pie' | 'donut' | 'radar' | 'sparkline' | 'segments' | 'area' | 'scatter' | 'radial-bar' | 'gauge' | 'stacked-bar' | 'grouped-bar' | 'multi-line' | 'funnel' | 'treemap' | 'sankey' | 'composed';
   /** Color scheme */
   color: 'accent' | 'success' | 'warning' | 'danger' | 'info';
+  /** Bar corner radius in px (null = let CSS tokens decide) */
+  cornerRadius: number;
   /** JS property (set programmatically — `el.data = [...]`). An array of plain objects; each object's keys are named by the `x` and `y` attributes — e.g. `<chart-ui x="month" y="revenue">` consumes `[{month:'Jan', revenue:3200}, {month:'Feb', revenue:4100}]`. The Chart.js `{labels, datasets}` envelope is NOT chart-ui's API — passing it (or any non-array value) renders an empty chart. May also be supplied declaratively as a JSON-array `data="[…]"` attribute, hydrated once at connect. Custom accessor on the element class, not a reflected attribute. */
   data: string;
   /** Marker (dot) visibility for line and multi-line series. `all` draws a circle[data-dot] on every datum (default — matches pre-gh#561 behavior). `none` hides all dots so a dense series reads as a clean line. `hover` shows only the currently-hovered datum's dot. `last` shows only the terminal point per series (sparkline convention). Tooltip hit targets ([data-hit]) are a separate always-rendered layer — every mode keeps hover/click working along the whole line. */
@@ -36,8 +38,6 @@ export class UIChart extends UIElement {
   hideValues: boolean;
   /** Show a skeleton placeholder instead of the chart body. Set to true while data is being fetched; clear once data arrives. Preserves the element's aspect-ratio dimensions so the skeleton occupies the same space the chart will fill. Parity with stat-ui[loading] and table-ui[loading] (§FB-12, v0.6.27). */
   loading: boolean;
-  /** Bar corner radius (null = let CSS tokens decide) */
-  radius: number;
   /** Multi-line only. Names one series key (matching a `y` key) to render at full strength — area fill + full-opacity line. Every other series drops its area fill and renders line-only at --chart-deemphasized-opacity. Empty (default) applies full treatment to every series, unchanged from pre-gh#561 behavior. */
   seriesEmphasis: string;
   /** Chart size */