Skip to content

An open source design system that's fully customizable and agent ready

TypeScript

docs: consolidate and credit changesets for v0.5.1 (#5658)

Cindy Zhangb4ffc91e13b9
diff --git a/.changeset/alert-dialog-responsive-actions.md b/.changeset/alert-dialog-responsive-actions.md
index 0f4b678d7c..13c95207dd 100644
--- a/.changeset/alert-dialog-responsive-actions.md
+++ b/.changeset/alert-dialog-responsive-actions.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] AlertDialog lets Dialog preserve and clamp its preferred width, lets whole actions move to another row when needed, and stacks full-width destructive and Cancel actions at 640px and below while preserving standard single-line Button sizing and labels regardless of pointer type.
+[fix] AlertDialog lets Dialog preserve and clamp its preferred width, lets whole actions move to another row when needed, and stacks full-width destructive and Cancel actions at 640px and below while preserving standard single-line Button sizing and labels regardless of pointer type. (#5343)
@rubyycheung
diff --git a/.changeset/avatar-shape-prop-xkvw.md b/.changeset/avatar-shape-prop-xkvw.md
index 4e75287c23..c28414c953 100644
--- a/.changeset/avatar-shape-prop-xkvw.md
+++ b/.changeset/avatar-shape-prop-xkvw.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] add shape prop ('circle' | 'rounded' | 'square') to Avatar for non-circular form factors (#4205)
+[feat] add shape prop ('circle' | 'rounded' | 'square') to Avatar for non-circular form factors (#4205) (#4327)
@HelloOjasMutreja
diff --git a/.changeset/badge-clamp-long-label.md b/.changeset/badge-clamp-long-label.md
index c0d947f7c1..02f96806e9 100644
--- a/.changeset/badge-clamp-long-label.md
+++ b/.changeset/badge-clamp-long-label.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Badge: a long label no longer escapes its container.
+[fix] Badge: a long label no longer escapes its container. (#5558)
`Badge` set `white-space: nowrap` with nothing to clip it — the one pairing
that neither wraps nor truncates. A label wider than the space available
diff --git a/.changeset/banner-dismiss-accessible-name.md b/.changeset/banner-dismiss-accessible-name.md
index 928084ddc5..4200059aeb 100644
--- a/.changeset/banner-dismiss-accessible-name.md
+++ b/.changeset/banner-dismiss-accessible-name.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Banner names each dismiss control after its string title, so stacked banners no longer expose identical "Dismiss" buttons to screen readers. Rich titles retain the generic translated name unless the consumer supplies an already-translated `dismissLabel`; that override also labels the tooltip.
+[fix] Banner names each dismiss control after its string title, so stacked banners no longer expose identical "Dismiss" buttons to screen readers. Rich titles retain the generic translated name unless the consumer supplies an already-translated `dismissLabel`; that override also labels the tooltip. (#5113)
@cixzhang
diff --git a/.changeset/baseprops-passthrough-forwarding.md b/.changeset/baseprops-passthrough-forwarding.md
index 647881ad07..6663b283d7 100644
--- a/.changeset/baseprops-passthrough-forwarding.md
+++ b/.changeset/baseprops-passthrough-forwarding.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Seven components now forward the pass-through props promised by `BaseProps`
+[fix] Seven components now forward the pass-through props promised by `BaseProps` (#5563)
`MetadataListItem`, `NavHeadingMenu`, `Timestamp`, `Token`, `TopNavMegaMenu`, `TopNavMenu`, and `TypeaheadItem` now forward neutral `aria-*`, `id`, `tabIndex`, event-handler, and `data-*` props to their rendered DOM element. Styling still merges through `mergeProps`, contract-owned attributes retain precedence, and owned handlers compose through `composeEventHandlers` with the caller first.
diff --git a/.changeset/build-retrieval-scoring.md b/.changeset/build-retrieval-scoring.md
index 2921c8ec32..69c582f3a5 100644
--- a/.changeset/build-retrieval-scoring.md
+++ b/.changeset/build-retrieval-scoring.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[fix] `build`/`search` no longer rank a partially-matched template above one matching every term, no longer index TypeScript generic arguments as rendered components, and no longer treat breadth of rendered components as full-strength relevance.
+[fix] `build`/`search` no longer rank a partially-matched template above one matching every term, no longer index TypeScript generic arguments as rendered components, and no longer treat breadth of rendered components as full-strength relevance. (#5614)
@ernestt
diff --git a/.changeset/button-elevation-theme-target.md b/.changeset/button-elevation-theme-target.md
index 7c6750b46d..f418b07dc7 100644
--- a/.changeset/button-elevation-theme-target.md
+++ b/.changeset/button-elevation-theme-target.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `Button` now reflects `elevation` as a theme target. The prop selected between four StyleX style objects but was missing from the sibling `themeProps('button')` call, so `data-elevation` never reached the DOM and no theme could style the axis — the same defect fixed on `Card` in #5491, and one `ButtonGroup` already had right. A button inside a `ButtonGroup` reports `none`, because the group owns the surface's elevation and the member paints flat. Every wrapper that forwards `ButtonProps` through to `Button` — `IconButton` — picks the reflection up with it. (`ToggleButton` does not: its props extend `BaseProps`, not `ButtonProps`, so it has no `elevation` to forward and keeps reporting `none`.) Nothing about the rendered button changes: 60 of 64 captured frames are byte-identical, and the four that differ do so only inside the loading spinner's own box.
+[fix] `Button` now reflects `elevation` as a theme target. The prop selected between four StyleX style objects but was missing from the sibling `themeProps('button')` call, so `data-elevation` never reached the DOM and no theme could style the axis — the same defect fixed on `Card` in #5491, and one `ButtonGroup` already had right. A button inside a `ButtonGroup` reports `none`, because the group owns the surface's elevation and the member paints flat. Every wrapper that forwards `ButtonProps` through to `Button` — `IconButton` — picks the reflection up with it. (`ToggleButton` does not: its props extend `BaseProps`, not `ButtonProps`, so it has no `elevation` to forward and keeps reporting `none`.) Nothing about the rendered button changes: 60 of 64 captured frames are byte-identical, and the four that differ do so only inside the loading spinner's own box. (#5552)
@cixzhang
diff --git a/.changeset/calendar-nightly-audit-20260824.md b/.changeset/calendar-nightly-audit-20260824.md
index bf28b18384..7ad8e5f945 100644
--- a/.changeset/calendar-nightly-audit-20260824.md
+++ b/.changeset/calendar-nightly-audit-20260824.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Calendar: announce a cleared range in the provider locale, wrap the two-month layout instead of overflowing a narrow viewport, keep the selected date visible under forced colors
+[fix] Calendar: announce a cleared range in the provider locale, wrap the two-month layout instead of overflowing a narrow viewport, keep the selected date visible under forced colors (#5453)
@cixzhang
diff --git a/.changeset/card-nightly-audit-20260825.md b/.changeset/card-nightly-audit-20260825.md
index 4dd725927d..31e0c90936 100644
--- a/.changeset/card-nightly-audit-20260825.md
+++ b/.changeset/card-nightly-audit-20260825.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Card: reflect `elevation` as a theme target so a theme can reach it, and correct the documented `padding` default
+[fix] Card: reflect `elevation` as a theme target so a theme can reach it, and correct the documented `padding` default (#5491)
`elevation` picked a style object but never reached the DOM, so `astryx-card` exposed `data-variant` and nothing for elevation and a theme could not style the four shadow tiers. It now rides `themeProps` alongside `variant`.
diff --git a/.changeset/card-variant-map.md b/.changeset/card-variant-map.md
index b8a444f75f..53d55ebb8b 100644
--- a/.changeset/card-variant-map.md
+++ b/.changeset/card-variant-map.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[feat] Card: make the `variant` axis theme-extensible through a `CardVariantMap` interface
+[feat] Card: make the `variant` axis theme-extensible through a `CardVariantMap` interface (#5551)
`CardVariant` was a hand-written union backed by a closed style record, so a theme could not add a card variant: an unknown value neither type-checked nor rendered. It is now `keyof CardVariantMap`, an interface exported from `@astryxdesign/core/Card` that a theme build augments — the same shape Button, Badge, Section and the other extensible axes already ship.
diff --git a/.changeset/carousel-edge-focus-and-theme-target.md b/.changeset/carousel-edge-focus-and-theme-target.md
index baade8cd37..da09402833 100644
--- a/.changeset/carousel-edge-focus-and-theme-target.md
+++ b/.changeset/carousel-edge-focus-and-theme-target.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Carousel no longer drops keyboard focus to the document body when reaching a scroll edge disables the nav button in use. Focus moves to the opposite arrow instead, on the state transition that disables the button rather than on a prediction from the press, so it holds under reduced motion, under scroll-snap, and on browsers without `scrollend`. The scroll container is also now a documented theme target, `astryx-carousel-scroller`, carrying the gap, padding, snap and edge-fade props it styles, so a theme can reach the spacing and the fade it could not see before.
+[fix] Carousel no longer drops keyboard focus to the document body when reaching a scroll edge disables the nav button in use. Focus moves to the opposite arrow instead, on the state transition that disables the button rather than on a prediction from the press, so it holds under reduced motion, under scroll-snap, and on browsers without `scrollend`. The scroll container is also now a documented theme target, `astryx-carousel-scroller`, carrying the gap, padding, snap and edge-fade props it styles, so a theme can reach the spacing and the fade it could not see before. (#5601)
@cixzhang
diff --git a/.changeset/checkbox-switch-label-theme-target.md b/.changeset/checkbox-switch-label-theme-target.md
index b8c663be1c..4b94cb39f0 100644
--- a/.changeset/checkbox-switch-label-theme-target.md
+++ b/.changeset/checkbox-switch-label-theme-target.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] CheckboxInput and Switch now name their own label as a theme target: `astryx-checkbox-label` and `astryx-switch-label`, alongside the `astryx-field-label` every label already carries. A theme could previously only reach one `astryx-field-label` target, so styling a checkbox's label — which shares a row with its control — meant styling every form field's label above its input too. The control passes the target down, so the name says what the thing is rather than encoding how it is arranged, and nothing can set it untruthfully.
+[feat] CheckboxInput and Switch now name their own label as a theme target: `astryx-checkbox-label` and `astryx-switch-label`, alongside the `astryx-field-label` every label already carries. A theme could previously only reach one `astryx-field-label` target, so styling a checkbox's label — which shares a row with its control — meant styling every form field's label above its input too. The control passes the target down, so the name says what the thing is rather than encoding how it is arranged, and nothing can set it untruthfully. (#5183)
@freddymeta
diff --git a/.changeset/checkbox-theme-targets.md b/.changeset/checkbox-theme-targets.md
index 1095bb14c4..4c2afb4c33 100644
--- a/.changeset/checkbox-theme-targets.md
+++ b/.changeset/checkbox-theme-targets.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] The checkbox indicator now exposes stable theme targets for its two marks — `astryx-checkbox-indicator-check` (the checkmark) and `astryx-checkbox-indicator-dash` (the indeterminate bar) — mirroring the existing `astryx-radio-indicator-dot`. Both reflect `size`. A theme restyling the mark itself (stroke weight, colour, the dash's proportions) previously had to reach it with `.astryx-checkbox-indicator > svg` and `> span`, which are element-and-order selectors that break silently on any restructure. Purely additive; no visual change.
+[feat] The checkbox indicator now exposes stable theme targets for its two marks — `astryx-checkbox-indicator-check` (the checkmark) and `astryx-checkbox-indicator-dash` (the indeterminate bar) — mirroring the existing `astryx-radio-indicator-dot`. Both reflect `size`. A theme restyling the mark itself (stroke weight, colour, the dash's proportions) previously had to reach it with `.astryx-checkbox-indicator > svg` and `> span`, which are element-and-order selectors that break silently on any restructure. Purely additive; no visual change. (#5426)
@freddymeta
diff --git a/.changeset/cli-case-exact-name-resolution.md b/.changeset/cli-case-exact-name-resolution.md
index b9825a7b48..c1cad2340b 100644
--- a/.changeset/cli-case-exact-name-resolution.md
+++ b/.changeset/cli-case-exact-name-resolution.md
@@ -2,7 +2,7 @@
'@astryxdesign/cli': patch
---
-[fix] Component and hook names resolve case-exactly on macOS and Windows, matching Linux
+[fix] Component and hook names resolve case-exactly on macOS and Windows, matching Linux (#5478)
`findComponentReadme`, `findComponentSource` and `findHookDoc` probed candidate
paths with `fs.existsSync`, which answers through the filesystem's own case
diff --git a/.changeset/complexselector-onopenchange.md b/.changeset/complexselector-onopenchange.md
index 53a62a1aa6..6e5ba4ced4 100644
--- a/.changeset/complexselector-onopenchange.md
+++ b/.changeset/complexselector-onopenchange.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] ComplexSelector: `onOpenChange` reports every open and close of the popup — the trigger, the keyboard, a light dismiss, Escape, content calling `close()`, or the imperative handle. Paired with the existing `handleRef`, a consumer can drive and observe the surface without reading the shell's DOM.
+[feat] ComplexSelector: `onOpenChange` reports every open and close of the popup — the trigger, the keyboard, a light dismiss, Escape, content calling `close()`, or the imperative handle. Paired with the existing `handleRef`, a consumer can drive and observe the surface without reading the shell's DOM. (#5211)
@cixzhang
diff --git a/.changeset/data-token-runtime-build-parity.md b/.changeset/data-token-runtime-build-parity.md
new file mode 100644
index 0000000000..21e4b6a48d
--- /dev/null
+++ b/.changeset/data-token-runtime-build-parity.md
@@ -0,0 +1,12 @@
+---
+'@astryxdesign/core': patch
+'@astryxdesign/cli': patch
+---
+
+[fix] The 56 `--color-data-*` defaults now reach runtime CSS and built themes from the same source, while dashboard template fallbacks match those defaults (#5562, #5566)
+
+The defaults live once at `:root` in `@layer astryx-base`, so nested themes inherit parent overrides and `astryx theme build` matches `<Theme>` while `generateThemeCSS` keeps its existing return shape.
+
+**Visual change.** A chart or template that previously painted nothing or used a mismatched hex fallback now paints the data token's default. Pin an explicit color to preserve a previous fallback.
+
+@cixzhang
diff --git a/.changeset/data-tokens-reach-css.md b/.changeset/data-tokens-reach-css.md
deleted file mode 100644
index d5436d83d6..0000000000
--- a/.changeset/data-tokens-reach-css.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] The 56 `--color-data-*` tokens now reach CSS. They were declared in `domainTokens/dataTokens.ts` and resolvable from JS through `useTheme().token()` and `resolveThemeTokens()`, but nothing emitted them as custom properties, so `var(--color-data-categorical-blue)` resolved to nothing and only a token a theme happened to override by name ever landed. The defaults are now emitted once as a `:root` block in `@layer astryx-base` — the same place and layer StyleX puts the core token defaults — so the palette resolves, a theme's `--color-data-*` override outranks it by layer, and a nested `<Theme>` that names no data token inherits its parent's override instead of shadowing it with the default.
-
-**Visual change.** Anything reading `var(--color-data-*)` without a fallback painted nothing before and now paints the palette value; anything reading it with a hex fallback now takes the token value instead of the fallback. Pin a colour explicitly if you were relying on either.
-
-@cixzhang
diff --git a/.changeset/date-input-native-picker-option.md b/.changeset/date-input-native-picker-option.md
deleted file mode 100644
index 4178179507..0000000000
--- a/.changeset/date-input-native-picker-option.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] DateInput: the platform's own date picker on touch, with
-`nativePicker` to choose otherwise
-
-A touch device now gets the browser/OS picker — the iOS wheel, the Android
-calendar dialog — drawn by the platform, with its own hit areas, momentum
-scrolling, locale and accessibility settings. `nativePicker` picks the
-surface: `'touch'` (the default) uses it on a coarse pointer, `'always'`
-wherever the browser supports `<input type="date">`, and `'never'` keeps
-Astryx's own pickers everywhere — the bottom-sheet picker on a finger, the
-calendar popover on a mouse.
-
-Reach for `'never'` on a field that needs what a native picker cannot
-express: `weekStartsOn`, `numberOfMonths`, or `dateConstraints`.
-
-`format` and `placeholder` still apply in native mode — DateInput paints the
-closed field's text itself, over the control, so a date reads the same on a
-phone as on a desktop. `min` and `max` are forwarded, but a native picker may
-not _show_ them: on iOS they are constraint-validation flags rather than
-clamps, so an out-of-range date can be selected, and it is refused on commit
-and announced rather than greyed out in the picker. Mouse-driven devices are
-unaffected.
-
-@imdreamrunner
diff --git a/.changeset/date-input-native-segments-visible.md b/.changeset/date-input-native-segments-visible.md
deleted file mode 100644
index e6528e50b9..0000000000
--- a/.changeset/date-input-native-segments-visible.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] DateInput's native surface (`nativePicker`) now shows the engine's own date segments while the control has focus, instead of painting over them. On iOS and Android `<input type="date">` is a single untypable run, so DateInput's formatted text can cover it; on desktop engines — and in Chrome's touch simulator — it is a row of editable `mm`/`dd`/`yyyy` fields, and covering those hid the digits being typed. `format` reapplies on blur.
-
-@imdreamrunner
diff --git a/.changeset/date-input-touch-picker.md b/.changeset/date-input-touch-picker.md
new file mode 100644
index 0000000000..4c67cbfcc4
--- /dev/null
+++ b/.changeset/date-input-touch-picker.md
@@ -0,0 +1,9 @@
+---
+'@astryxdesign/core': patch
+---
+
+[feat] DateInput uses the platform date picker on touch, with `nativePicker` to choose the native or Astryx surface; focused desktop-style native fields reveal their editable segments, the Astryx touch sheet keeps Reset in its header and Save alone in its footer, and both closed surfaces match standard input height (#5261, #5456, #5502, #5534)
+
+`nativePicker="touch"` is the default, `"always"` uses `<input type="date">` wherever supported, and `"never"` keeps Astryx's sheet or popover. Formatting still returns on blur, and `min`/`max` continue to validate native selections.
+
+@imdreamrunner
diff --git a/.changeset/date-input-touch-reset-in-header.md b/.changeset/date-input-touch-reset-in-header.md
deleted file mode 100644
index 11fb563890..0000000000
--- a/.changeset/date-input-touch-reset-in-header.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] DateInput: move the mobile picker's Reset into the header's trailing
-corner
-
-On a touch device the picker's footer held Reset and Save side by side, two
-half-width buttons of equal weight — so the row that ends the task also
-offered the one action that throws the work away, a thumb's width from it.
-
-Reset now sits at the top of the sheet, trailing of the month arrows: chrome,
-in the band of controls that move the calendar without finishing anything.
-The footer is Save alone, full width. Nothing about what Reset does changed —
-it still clears the date and returns the calendar to the current month — and
-it still leaves with the arrows when the month and year wheels come up, since
-there is no date to clear on that surface.
-
-@imdreamrunner
diff --git a/.changeset/dateinput-touch-field-height.md b/.changeset/dateinput-touch-field-height.md
deleted file mode 100644
index eb79a10191..0000000000
--- a/.changeset/dateinput-touch-field-height.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] DateInput's sheet-backed field is the same height as every other input on touch
-
-`TouchDateField`'s closed field carried a 44px `minBlockSize` floor on a coarse
-pointer, so on a phone it rendered 12px taller than the TextInput beside it —
-and taller than the same component's own native surface, which is what
-`DateInput` renders by default on touch. Two `DateInput`s in one form could
-therefore differ in height purely by `nativePicker`.
-
-The floor is gone from the closed field; every target inside the open sheet
-keeps its 44px. The field's own floor is core's, 24x24 under WCAG 2.5.8 AA,
-which a 32x180 field clears several times over.
-
-@imdreamrunner
diff --git a/.changeset/daterange-same-day-selection.md b/.changeset/daterange-same-day-selection.md
index fdf8c21720..90b9d18dcc 100644
--- a/.changeset/daterange-same-day-selection.md
+++ b/.changeset/daterange-same-day-selection.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] DateRangeInput: allow a same-day range when `minRangeSpan` is 1
+[fix] DateRangeInput: allow a same-day range when `minRangeSpan` is 1 (#5581)
A repeated click on the range start now commits a one-day range when the
configured minimum permits it, including when a maximum span is also set.
diff --git a/.changeset/dialog-fullscreen-safe-area-padding.md b/.changeset/dialog-fullscreen-safe-area-padding.md
index 49a22d582a..4a0cd7b7ad 100644
--- a/.changeset/dialog-fullscreen-safe-area-padding.md
+++ b/.changeset/dialog-fullscreen-safe-area-padding.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Dialog: fullscreen safe-area padding follows writing direction and defers to explicit padding
+[fix] Dialog: fullscreen safe-area padding follows writing direction and defers to explicit padding (#5367)
Two corrections to the fullscreen safe-area padding that shipped in 0.5.0.
diff --git a/.changeset/document-the-seven-core-hooks-that-were-missing--sr6p.md b/.changeset/document-the-seven-core-hooks-that-were-missing--sr6p.md
index f03369b55f..1ca18d50ae 100644
--- a/.changeset/document-the-seven-core-hooks-that-were-missing--sr6p.md
+++ b/.changeset/document-the-seven-core-hooks-that-were-missing--sr6p.md
@@ -3,6 +3,6 @@
'@astryxdesign/core': patch
---
-[docs] `useAnnounce`, `useTypeahead`, `useInteractiveRole`, `useLongPress`, `useInputStatusIcon`, `useDevWarning` and `useIndicatorFocusRing` are now discoverable. The CLI's hook index is built from the `.doc.mjs` files next to each hook, and these seven shipped without one; so `astryx hook <name>` answered "No hook named", `astryx hook` omitted them and `astryx search` never returned them, while the package exported them with full TSDoc. Agents following the documented discovery workflow concluded the primitives did not exist and hand-rolled replacements; for `useAnnounce` that means a hand-built `aria-live` region, which usually does not announce at all. A test now fails when a hook is exported from the barrel without a doc, so the index cannot silently go stale again.
+[docs] `useAnnounce`, `useTypeahead`, `useInteractiveRole`, `useLongPress`, `useInputStatusIcon`, `useDevWarning` and `useIndicatorFocusRing` are now discoverable. The CLI's hook index is built from the `.doc.mjs` files next to each hook, and these seven shipped without one; so `astryx hook <name>` answered "No hook named", `astryx hook` omitted them and `astryx search` never returned them, while the package exported them with full TSDoc. Agents following the documented discovery workflow concluded the primitives did not exist and hand-rolled replacements; for `useAnnounce` that means a hand-built `aria-live` region, which usually does not announce at all. A test now fails when a hook is exported from the barrel without a doc, so the index cannot silently go stale again. (#5109)
@cixzhang
diff --git a/.changeset/fix-plaindateformat-runtime-locale.md b/.changeset/fix-plaindateformat-runtime-locale.md
index cc4dc4d8ca..a037bbfe0b 100644
--- a/.changeset/fix-plaindateformat-runtime-locale.md
+++ b/.changeset/fix-plaindateformat-runtime-locale.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Date formatting now defaults to Gregorian calendar semantics across core, charts, and Schedule while still following the selected locale for language, numbering, and field order.
+[fix] Date formatting now defaults to Gregorian calendar semantics across core, charts, and Schedule while still following the selected locale for language, numbering, and field order. (#5303)
The low-level public `plainDateFormat` helper continues to honor an explicitly supplied `calendar` option for compatibility; Astryx components do not expose that display-only exception and remain Gregorian. The deterministic English fallback also prevents server and browser locale differences from producing hydration mismatches when no provider locale is available. Locale-aware parsing only selects day-first or month-first order for ambiguous ASCII numeric dates; it does not parse localized month names, non-ASCII digits, or arbitrary locale-specific strings.
diff --git a/.changeset/grouped-rows-pinned-heading.md b/.changeset/grouped-rows-pinned-heading.md
deleted file mode 100644
index 635ee53237..0000000000
--- a/.changeset/grouped-rows-pinned-heading.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] `useTableGroupedRows`: the section heading stays on screen when the table
-scrolls sideways
-
-A group header is one cell spanning every column, so on a table scrolled
-sideways its chevron and label slid out of view while the columns they named
-stayed pinned — leaving unlabelled grey bands and no way to collapse a section
-without scrolling back. The heading now sticks to the table's start edge.
-
-The cell's start gutter moves onto the heading itself so that it travels with
-it; left on the cell, the heading would sit one gutter in at rest and jump
-flush the moment it stuck.
-
-This was previously only patchable halfway from userland: `renderGroupHeader`
-can pin its own content, but the chevron is the plugin's and sits outside it,
-so the two would come apart.
-
-@ernesttien
diff --git a/.changeset/hovercard-aria-expanded-role-gate.md b/.changeset/hovercard-aria-expanded-role-gate.md
deleted file mode 100644
index bcd0a6628a..0000000000
--- a/.changeset/hovercard-aria-expanded-role-gate.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] HoverCard: a labelled card no longer puts `aria-expanded` on a trigger whose role cannot carry it
-
-Since the dialog-popup contract landed, a labelled HoverCard set `aria-haspopup`, `aria-controls` and `aria-expanded` on its trigger whatever that trigger was. The first two are global ARIA attributes and are valid anywhere; `aria-expanded` is supported on a fixed set of roles, and a role-less trigger is not one of them. Every Timestamp with a hover card is a role-less trigger, so nine Timestamp stories reported a critical axe `aria-allowed-attr` violation across twenty-nine nodes.
-
-`aria-expanded` is now emitted only when the trigger's role supports it. A role-less trigger keeps `aria-haspopup="dialog"` and `aria-controls`, so the popup relationship is still advertised — only the state the element could never have expressed is dropped, and if it carried its own `aria-expanded` that value is left alone. On a trigger whose role does support the attribute nothing changes: the card drives it, overwriting the trigger's own value exactly as before.
-
-@cixzhang
diff --git a/.changeset/hovercard-popup-semantics.md b/.changeset/hovercard-popup-semantics.md
new file mode 100644
index 0000000000..af6a31990f
--- /dev/null
+++ b/.changeset/hovercard-popup-semantics.md
@@ -0,0 +1,9 @@
+---
+'@astryxdesign/core': patch
+---
+
+[fix] Labelled HoverCard triggers expose a dialog-popup relationship without flattening rich content into a description, and only roles that support `aria-expanded` receive that state (#5419, #5501)
+
+The trigger now uses `aria-haspopup="dialog"`, `aria-controls`, and a role-gated `aria-expanded`; `useHoverCard` exposes the layer `id` and open state, while `describedBy` remains as a deprecated alias for compatibility. Unlabelled group cards keep their description relationship.
+
+@gonzoblasco @cixzhang
diff --git a/.changeset/icon-extension-keys.md b/.changeset/icon-extension-keys.md
new file mode 100644
index 0000000000..32bab85e6f
--- /dev/null
+++ b/.changeset/icon-extension-keys.md
@@ -0,0 +1,10 @@
+---
+'@astryxdesign/core': patch
+'@astryxdesign/cli': patch
+---
+
+[feat] Icon APIs and themes accept namespaced extension keys, and NumberInput steppers use `numberInput:stepperDown` without widening the required `IconRegistry` keys (#5466)
+
+`<Icon icon>`, `useIcon`, and `defineTheme({icons})` accept keys such as `numberInput:stepperDown` and `richtext:bold`; misspelled built-in names remain type errors. NumberInput keeps a compact centered Core fallback, while themes can override its steppers independently from the shared `chevronDown` semantic.
+
+@cixzhang @rubyycheung
diff --git a/.changeset/icon-namespaced-keys-from-the-icon-prop.md b/.changeset/icon-namespaced-keys-from-the-icon-prop.md
deleted file mode 100644
index fb76322534..0000000000
--- a/.changeset/icon-namespaced-keys-from-the-icon-prop.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-'@astryxdesign/core': patch
-'@astryxdesign/cli': patch
----
-
-[feat] `<Icon icon>`, `useIcon`, and `defineTheme({icons})` accept namespaced extension keys (`'numberInput:stepperDown'`, `'richtext:bold'`) alongside the built-in semantic names. A glyph owned by one component or library can now be themed by key while keeping `size`, `color` and `xstyle`, without widening the shared `IconName` union — and so without adding a required key to every downstream `IconRegistry`. Misspelled built-in names are still rejected, and `getIconRegistry()` still returns built-in names only.
-
-@cixzhang
diff --git a/.changeset/layer-dismiss-gesture.md b/.changeset/layer-dismiss-gesture.md
index 8b4e9d459d..c48b676bb6 100644
--- a/.changeset/layer-dismiss-gesture.md
+++ b/.changeset/layer-dismiss-gesture.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Popup triggers no longer fight the browser's own light dismiss: pressing the button of an open Selector, MultiSelector, ComplexSelector, DropdownMenu, or Popover closes it once instead of closing and reopening. MultiSelector's clear and status buttons also keep its popup open when pressed.
+[fix] Popup triggers no longer fight the browser's own light dismiss: pressing the button of an open Selector, MultiSelector, ComplexSelector, DropdownMenu, or Popover closes it once instead of closing and reopening. MultiSelector's clear and status buttons also keep its popup open when pressed. (#5018)
@cixzhang
diff --git a/.changeset/markdown-image-url-parity.md b/.changeset/markdown-image-url-parity.md
index 4628739643..f1dabd5c58 100644
--- a/.changeset/markdown-image-url-parity.md
+++ b/.changeset/markdown-image-url-parity.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Markdown now applies the same URL safety rule to every image path it parses: reference-style images (`![alt][label]` and the shortcut form) and standalone block images pass through the check inline images and links already used, and the render-side guard normalizes control characters before testing so both layers see a URL the way a browser will.
+[fix] Markdown now applies the same URL safety rule to every image path it parses: reference-style images (`![alt][label]` and the shortcut form) and standalone block images pass through the check inline images and links already used, and the render-side guard normalizes control characters before testing so both layers see a URL the way a browser will. (#5522)
@bhamodi
diff --git a/.changeset/markdown-list-forward-base-props.md b/.changeset/markdown-list-forward-base-props.md
index da13969719..938c7f8617 100644
--- a/.changeset/markdown-list-forward-base-props.md
+++ b/.changeset/markdown-list-forward-base-props.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Markdown and List forward the rest of `BaseProps`
+[fix] Markdown and List forward the rest of `BaseProps` (#5288)
Both declare `BaseProps`, and `BaseProps` documents that `data-*`, `aria-*` and
`role` reach the element — but each destructured a fixed set of props and
diff --git a/.changeset/number-input-bounded-separators.md b/.changeset/number-input-bounded-separators.md
deleted file mode 100644
index ec4f1169ad..0000000000
--- a/.changeset/number-input-bounded-separators.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] NumberInput: `1.5` reads as 1.5 everywhere again, and `123-456-789` is not a number
-
-Two defects in the locale-aware parsing added last release, both from one
-decision: which characters may separate digits was decided per input rather
-than from a bounded set.
-
-**The machine decimal point stopped parsing in comma-decimal locales.** In
-de-DE, typing `1.5` committed 1 with no error shown, and pasting `1.5` or
-`1234.56` was refused outright — all three committed the right number before.
-A full stop the locale cannot read as grouping has exactly one reading left,
-so it is now read, the way Chromium's own `<input type="number">` reads it. A
-full stop that _is_ well-formed grouping still belongs to the locale: `1.234`
-in de-DE is 1234, not 1.234.
-
-**Any repeated character read as a thousands separator.** `123-456-789`
-committed 123456789, and so did `1_234_567`, `1/234/567` and `1:234:567` — a
-hyphenated ID pasted into a quantity field became a number. Only the
-characters some locale actually writes between digits are separators now.
-That bounds the characters, not the shapes: a full stop is a real separator in
-its own right, so `192.168.100.200` still commits 192168100200, exactly as it
-did before.
-
-Also: `(-1,234)` and `(+1,234)` each flipped their own sign and now refuse — an
-accounting paren already says negative, so a sign inside it reads two ways.
-
-Everything the previous release got right is unchanged, `formatValue` is
-untouched, and there is no API change.
-
-@cixzhang
diff --git a/.changeset/number-input-parsing-and-commit.md b/.changeset/number-input-parsing-and-commit.md
new file mode 100644
index 0000000000..85700eba9a
--- /dev/null
+++ b/.changeset/number-input-parsing-and-commit.md
@@ -0,0 +1,9 @@
+---
+'@astryxdesign/core': patch
+---
+
+[fix] NumberInput parses locale-formatted paste safely and commits one complete draft: grouped numbers and machine decimal points work, arbitrary repeated punctuation is refused, out-of-range values clamp to the nearest bound, and fractional stepping cannot cross a rounded bound (#5152, #5450, #5459, #5510, #5546)
+
+Invalid typed or pasted input preserves the prior value instead of committing a valid prefix. Pagination inherits the complete-draft and bound behavior, while inline Table filtering and PowerSearch keep their existing live and Enter-to-save behavior.
+
+@cixzhang @jiunshinn
diff --git a/.changeset/number-input-paste-grouped-numbers.md b/.changeset/number-input-paste-grouped-numbers.md
deleted file mode 100644
index 3835d1031c..0000000000
--- a/.changeset/number-input-paste-grouped-numbers.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] NumberInput: a pasted `1,234,234,234` now commits as 1234234234
-
-Pasting a number out of a spreadsheet used to fail. The field parsed with
-`Number()`, so `1,234,234,234` read as `NaN`, the field went invalid, and the
-paste was lost — the single most common way anyone puts a large number into a
-form.
-
-Typed and pasted text is now read under the field's locale: grouping and
-decimal separators and group sizes come from `Intl` (so `1.234.234.234` in
-de-DE, narrow-no-break-space grouping in fr-FR, and lakh grouping in en-IN all
-work), digits come from `\p{Nd}` (Arabic-Indic, Devanagari, full-width), and
-the shapes a spreadsheet attaches — a currency symbol, an accounting `(1,234)`,
-a `1.23E+09`, a stray BOM — are handled.
-
-A separator that could mean two different numbers still refuses: `1,5` is 1.5
-in de-DE and nothing in en-US, and a `1,234 GB` keeps its unit rather than
-guessing which trailing letters are inert. Refusing leaves the field
-`aria-invalid` with its existing alert, which is the honest outcome — a wrong
-number committed silently is the failure this is designed against.
-
-Typing is never intercepted and nothing is rewritten mid-composition. No API
-change: `formatValue` is untouched.
-
-@cixzhang
diff --git a/.changeset/number-input-stepper-icon-slot.md b/.changeset/number-input-stepper-icon-slot.md
deleted file mode 100644
index d84bc58c0e..0000000000
--- a/.changeset/number-input-stepper-icon-slot.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] NumberInput steppers now resolve through the component-owned `numberInput:stepperDown` icon key, leaving `chevronDown` for shared disclosure and navigation affordances. Core provides a compact centered chevron fallback, and themes can override the stepper independently without adding a required `IconRegistry` key.
-
-@rubyycheung
diff --git a/.changeset/numberinput-clamp-to-bound.md b/.changeset/numberinput-clamp-to-bound.md
deleted file mode 100644
index 397436f720..0000000000
--- a/.changeset/numberinput-clamp-to-bound.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] NumberInput: an entry past `min`/`max` now commits at the nearest bound on blur or Enter instead of falling back to the last in-range prefix — typing 100 into a 1–2 field lands on 2, not 1. Pagination inherits this.
-
-@cixzhang
diff --git a/.changeset/numberinput-invalid-draft-commit.md b/.changeset/numberinput-invalid-draft-commit.md
deleted file mode 100644
index 997cc5d47a..0000000000
--- a/.changeset/numberinput-invalid-draft-commit.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] NumberInput: commit each text edit as one draft on blur or Enter, so invalid typed and pasted input consistently preserves the prior value instead of committing a valid prefix. This also prevents Pagination from navigating to an intermediate prefix while preserving live inline Table filtering and PowerSearch's Enter-to-save behavior.
-
-@cixzhang
diff --git a/.changeset/numberinput-stepping-clamps-the-rounded-result-s-18rm.md b/.changeset/numberinput-stepping-clamps-the-rounded-result-s-18rm.md
deleted file mode 100644
index 59be2acbea..0000000000
--- a/.changeset/numberinput-stepping-clamps-the-rounded-result-s-18rm.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] NumberInput stepping clamps the rounded result so fractional min and max bounds cannot be crossed (#5506)
-@jiunshinn
diff --git a/.changeset/overflowlist-on-overflow-change.md b/.changeset/overflowlist-on-overflow-change.md
index a996deb9e3..16ea8adbf7 100644
--- a/.changeset/overflowlist-on-overflow-change.md
+++ b/.changeset/overflowlist-on-overflow-change.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] `OverflowList` can now hand its collapsed items to a menu you already render, via `onOverflowChange(overflowItems)`. `overflowRenderer` only describes an indicator the list mounts itself, and only while items overflow — so a row that already carries a standing "…" menu had no way to collect the collapsed items into it, and adding an indicator gave the user two menus side by side. Watching from the outside was not reachable either: a reporter component placed inside `overflowRenderer` mounts twice (the hidden measurement copy always receives _every_ item, so it cannot tell you what is actually collapsed), and nothing fires when the row widens back out and the set empties. The new callback reports the collapsed set whenever its membership or order changes, and leaves the anchor entirely to the caller. It fires once measurement has collapsed something, fires again with an empty array once the row widens back out and everything fits, and is silent while nothing overflows — including on mount, so a list that fits from the start never calls it. It never reports the pre-measurement state, which is an empty set whether or not the row actually overflows; hold the collapsed set in state initialised to `[]` and it is correct at every moment. Reports run from a layout effect after measurement, so the menu updates in the same frame as the collapse. The measurement container is now observed for size changes, so child-size changes refresh every OverflowList and direct `useOverflow` consumer even when the available container width does not change. Keyed membership and order changes are re-measured before `onOverflowChange` reports them. Stable React keys distinguish same-count membership and order changes, while unrelated re-renders and callback identity changes do not re-fire it. Both APIs may be used together; using `onOverflowChange` alone adds nothing to the row.
+[feat] `OverflowList` can now hand its collapsed items to a menu you already render, via `onOverflowChange(overflowItems)`. `overflowRenderer` only describes an indicator the list mounts itself, and only while items overflow — so a row that already carries a standing "…" menu had no way to collect the collapsed items into it, and adding an indicator gave the user two menus side by side. Watching from the outside was not reachable either: a reporter component placed inside `overflowRenderer` mounts twice (the hidden measurement copy always receives _every_ item, so it cannot tell you what is actually collapsed), and nothing fires when the row widens back out and the set empties. The new callback reports the collapsed set whenever its membership or order changes, and leaves the anchor entirely to the caller. It fires once measurement has collapsed something, fires again with an empty array once the row widens back out and everything fits, and is silent while nothing overflows — including on mount, so a list that fits from the start never calls it. It never reports the pre-measurement state, which is an empty set whether or not the row actually overflows; hold the collapsed set in state initialised to `[]` and it is correct at every moment. Reports run from a layout effect after measurement, so the menu updates in the same frame as the collapse. The measurement container is now observed for size changes, so child-size changes refresh every OverflowList and direct `useOverflow` consumer even when the available container width does not change. Keyed membership and order changes are re-measured before `onOverflowChange` reports them. Stable React keys distinguish same-count membership and order changes, while unrelated re-renders and callback identity changes do not re-fire it. Both APIs may be used together; using `onOverflowChange` alone adds nothing to the row. (#5199)
@cixzhang
diff --git a/.changeset/popover-radius-reaches-surface.md b/.changeset/popover-radius-reaches-surface.md
index d3e0965e23..15bfe71e91 100644
--- a/.changeset/popover-radius-reaches-surface.md
+++ b/.changeset/popover-radius-reaches-surface.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Popover: theming `popover.borderRadius` now changes the rendered radius. The `astryx-popover` target moves onto the popup surface — the box that paints background, radius and elevation — and `usePopover` reads the registered `--_popover-radius` there instead of hardcoding `--radius-container`. Content padding moves with it, so a themed `padding` still replaces the default instead of nesting inside it.
+[fix] Popover: theming `popover.borderRadius` now changes the rendered radius. The `astryx-popover` target moves onto the popup surface — the box that paints background, radius and elevation — and `usePopover` reads the registered `--_popover-radius` there instead of hardcoding `--radius-container`. Content padding moves with it, so a themed `padding` still replaces the default instead of nesting inside it. (#5162)
@cixzhang
diff --git a/.changeset/pressed-overlay-specificity.md b/.changeset/pressed-overlay-specificity.md
index 5703bfe191..b53ac44570 100644
--- a/.changeset/pressed-overlay-specificity.md
+++ b/.changeset/pressed-overlay-specificity.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Ensure pressed overlays override hover across interactive surfaces (#5451)
+[fix] Ensure pressed overlays override hover across interactive surfaces (#5451) (#5516)
@jiunshinn
diff --git a/.changeset/selector-caller-supplied-trigger-id.md b/.changeset/selector-caller-supplied-trigger-id.md
index 768c284392..0ed5813e46 100644
--- a/.changeset/selector-caller-supplied-trigger-id.md
+++ b/.changeset/selector-caller-supplied-trigger-id.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Selector: a caller-supplied `id` now drives the trigger's whole identity, not just its `id` attribute
+[fix] Selector: a caller-supplied `id` now drives the trigger's whole identity, not just its `id` attribute (#5561)
`Selector` generated its trigger id with `useId()` and set it on the trigger button before spreading `...rest`, so a caller's `id` — accepted through `BaseProps` — replaced it on the button while the generated value stayed behind as the target of the listbox's `aria-labelledby` and of the `Field` label's `htmlFor`. Passing `id` therefore left the listbox with no accessible name and the field label pointing at an element that does not exist, silently and with a clean typecheck, lint and build.
diff --git a/.changeset/selector-configurable-empty-state.md b/.changeset/selector-configurable-empty-state.md
index 8bf2201d5d..d68ae1f1a4 100644
--- a/.changeset/selector-configurable-empty-state.md
+++ b/.changeset/selector-configurable-empty-state.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] Selector and MultiSelector: configurable panel empty states via `emptyText` and `emptySearchText`, announced to screen readers as well as shown; a panel with no options now says so instead of rendering blank, and says nothing while `isLoading`
+[feat] Selector and MultiSelector: configurable panel empty states via `emptyText` and `emptySearchText`, announced to screen readers as well as shown; a panel with no options now says so instead of rendering blank, and says nothing while `isLoading` (#5462)
@cixzhang
diff --git a/.changeset/selector-source-build-compat.md b/.changeset/selector-source-build-compat.md
index acbeaa3bc8..dc4d2ffb19 100644
--- a/.changeset/selector-source-build-compat.md
+++ b/.changeset/selector-source-build-compat.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Selector raw source now compiles when consumer Babel presets lower arrow functions before StyleX extraction
+[fix] Selector raw source now compiles when consumer Babel presets lower arrow functions before StyleX extraction (#5508)
@jiunshinn
diff --git a/.changeset/settings-dialog-responsive-hub.md b/.changeset/settings-dialog-responsive-hub.md
index ec8196dab0..baa816f0f6 100644
--- a/.changeset/settings-dialog-responsive-hub.md
+++ b/.changeset/settings-dialog-responsive-hub.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[feat] Rebuild the `settings-dialog` page template with searchable navigation, responsive grouped controls, live appearance previews, configurable keyboard shortcuts, and docsite gallery visibility.
+[feat] Rebuild the `settings-dialog` page template with searchable navigation, responsive grouped controls, live appearance previews, configurable keyboard shortcuts, and docsite gallery visibility. (#5568)
@ernestt
diff --git a/.changeset/shared-apple-platform-detection.md b/.changeset/shared-apple-platform-detection.md
index 6a5a6d9903..72318ba281 100644
--- a/.changeset/shared-apple-platform-detection.md
+++ b/.changeset/shared-apple-platform-detection.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Platform detection reads the client-hints `Unknown` sentinel as no answer, and lives in one place
+[fix] Platform detection reads the client-hints `Unknown` sentinel as no answer, and lives in one place (#5394)
Follow-up to #5325, which taught `useHotkeys` and `Kbd` to fall through to
`navigator.platform` when `userAgentData.platform` is blank. `Unknown` is the
diff --git a/.changeset/sidenav-row-control-size.md b/.changeset/sidenav-row-control-size.md
index 9d767eb586..a495ed86b8 100644
--- a/.changeset/sidenav-row-control-size.md
+++ b/.changeset/sidenav-row-control-size.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] SideNavItem: the standalone expand/collapse toggle on a `collapsible` item with an `href` or `onClick` now carries the box of a `size="sm"` icon button. It had no box of its own, so it shrank to the 24px chevron inside it and painted a smaller hover pill than any icon button sitting beside it in the same row. (#4988)
+[fix] SideNavItem: the standalone expand/collapse toggle on a `collapsible` item with an `href` or `onClick` now carries the box of a `size="sm"` icon button. It had no box of its own, so it shrank to the 24px chevron inside it and painted a smaller hover pill than any icon button sitting beside it in the same row. (#4988) (#5005)
@AKnassa
diff --git a/.changeset/sidenav-single-collapse-owner.md b/.changeset/sidenav-single-collapse-owner.md
index 6e31f8c638..0357e5f17f 100644
--- a/.changeset/sidenav-single-collapse-owner.md
+++ b/.changeset/sidenav-single-collapse-owner.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] SideNav: `collapsible` and `resizable` no longer keep two independently initialized copies of the collapse state. Both props are normalized into one internal collapse config with a single owner — the resize hook when `resizable` is in play, SideNav's own state otherwise — so the hook can no longer restore itself collapsed while SideNav renders the expanded layout at width 0, which is what made a persisted-collapsed nav come back invisible and unrecoverable (#4790) — that the second independently-initialized boolean is the defect, rather than the restore clamp, is @HelloOjasMutreja's diagnosis from #4853. Passing both props stays supported and every configuration that works today resolves to the same collapse state it does now; when the two props genuinely address the same state (`defaultIsCollapsed` on both, or a controlled `collapsible` alongside collapse state on `resizable`) `resizable` wins and a dev warning names the conflicting keys. `useResizable` gains the standard controlled/uncontrolled pair, `defaultIsCollapsed` and `isCollapsed`, alongside the existing `onCollapseChange`: uncontrolled it owns collapse as before, controlled the prop wins and `collapse()`, `expand()` and a drag past the threshold report through the callback instead of mutating. Persisted entries now store `{size, isCollapsed}` where `size` is the _expanded_ size — the encoding is @AKnassa's from #4824 — so a reload restores the collapsed rail and expanding returns to the width the user had rather than `defaultWidth`; legacy entries still load, with a plain number read as a width whose collapse state is unknown and a plain `0` (written by the old collapse path) read as collapsed, so anyone already stuck with an invisible nav recovers without clearing localStorage. `resizable` can now also carry collapse state on its own. Two notification changes ride along: with a single owner, `collapsible.onCollapsedChange` fires once per toggle on a resizable nav instead of twice; and the hook's collapse callbacks now read the live collapse state rather than the value captured at their last render, so one drag past the threshold reports one collapse instead of one per pointer move, dragging back above the threshold re-expands mid-gesture, and `resize()` out of the collapsed state reports the implicit expand. That last fix is @AKnassa's, from #5118.
+[fix] SideNav: `collapsible` and `resizable` no longer keep two independently initialized copies of the collapse state. Both props are normalized into one internal collapse config with a single owner — the resize hook when `resizable` is in play, SideNav's own state otherwise — so the hook can no longer restore itself collapsed while SideNav renders the expanded layout at width 0, which is what made a persisted-collapsed nav come back invisible and unrecoverable (#4790) — that the second independently-initialized boolean is the defect, rather than the restore clamp, is @HelloOjasMutreja's diagnosis from #4853. Passing both props stays supported and every configuration that works today resolves to the same collapse state it does now; when the two props genuinely address the same state (`defaultIsCollapsed` on both, or a controlled `collapsible` alongside collapse state on `resizable`) `resizable` wins and a dev warning names the conflicting keys. `useResizable` gains the standard controlled/uncontrolled pair, `defaultIsCollapsed` and `isCollapsed`, alongside the existing `onCollapseChange`: uncontrolled it owns collapse as before, controlled the prop wins and `collapse()`, `expand()` and a drag past the threshold report through the callback instead of mutating. Persisted entries now store `{size, isCollapsed}` where `size` is the _expanded_ size — the encoding is @AKnassa's from #4824 — so a reload restores the collapsed rail and expanding returns to the width the user had rather than `defaultWidth`; legacy entries still load, with a plain number read as a width whose collapse state is unknown and a plain `0` (written by the old collapse path) read as collapsed, so anyone already stuck with an invisible nav recovers without clearing localStorage. `resizable` can now also carry collapse state on its own. Two notification changes ride along: with a single owner, `collapsible.onCollapsedChange` fires once per toggle on a resizable nav instead of twice; and the hook's collapse callbacks now read the live collapse state rather than the value captured at their last render, so one drag past the threshold reports one collapse instead of one per pointer move, dragging back above the threshold re-expands mid-gesture, and `resize()` out of the collapsed state reports the implicit expand. That last fix is @AKnassa's, from #5118. (#5075)
@AKnassa
@HelloOjasMutreja
diff --git a/.changeset/sidenavitem-actions-slot.md b/.changeset/sidenavitem-actions-slot.md
index 90095d7f00..4d3f734b24 100644
--- a/.changeset/sidenavitem-actions-slot.md
+++ b/.changeset/sidenavitem-actions-slot.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] SideNavItem: new `actions` slot for row-level secondary controls (icon buttons, menus). Content renders as a sibling of the primary link/button — after the expand/collapse toggle, before nested children in DOM and focus order — so interactive controls never nest inside the primary element and every row control is reachable before focus enters the subtree. Passive content (badges, counts) stays in `endContent`; `actions` is hidden while the rail is collapsed, and stays interactive on disabled items since each supplied control owns its own disabled state. An actions row draws its focus ring as a full-row pill for the primary link or button, while the expand/collapse toggle and each supplied action keep their own — adds `focusOutlineProps.focusWithinFirstChild` and `focusOutlineProps.suppressed` for that pairing. Supplied controls inherit the row's control size through `SizeContext`, the way `SideNav` already cascades one size to its footer icons, so an unsized icon button comes out the same box as the built-in toggle; an explicit `size` still wins. (#4988)
+[feat] SideNavItem: new `actions` slot for row-level secondary controls (icon buttons, menus). Content renders as a sibling of the primary link/button — after the expand/collapse toggle, before nested children in DOM and focus order — so interactive controls never nest inside the primary element and every row control is reachable before focus enters the subtree. Passive content (badges, counts) stays in `endContent`; `actions` is hidden while the rail is collapsed, and stays interactive on disabled items since each supplied control owns its own disabled state. An actions row draws its focus ring as a full-row pill for the primary link or button, while the expand/collapse toggle and each supplied action keep their own — adds `focusOutlineProps.focusWithinFirstChild` and `focusOutlineProps.suppressed` for that pairing. Supplied controls inherit the row's control size through `SizeContext`, the way `SideNav` already cascades one size to its footer icons, so an unsized icon button comes out the same box as the built-in toggle; an explicit `size` still wins. (#4988) (#5005)
@AKnassa
diff --git a/.changeset/slider-keyboard-only-focus-ring.md b/.changeset/slider-keyboard-only-focus-ring.md
index 998007b536..d923350dc9 100644
--- a/.changeset/slider-keyboard-only-focus-ring.md
+++ b/.changeset/slider-keyboard-only-focus-ring.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Slider: dragging the thumb with a mouse no longer draws the keyboard focus ring
+[fix] Slider: dragging the thumb with a mouse no longer draws the keyboard focus ring (#5463)
The thumb is a `div[role="slider"]`, and the track's `pointerdown` handler
calls `preventDefault()` and then focuses the thumb from script. Chromium
diff --git a/.changeset/spinner-themeable-diameter-rail.md b/.changeset/spinner-themeable-diameter-rail.md
index 8296a6bb35..fe012df477 100644
--- a/.changeset/spinner-themeable-diameter-rail.md
+++ b/.changeset/spinner-themeable-diameter-rail.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[feat] Spinner: the ring's geometry and its two colors are now themeable. The `size` and `shade` props keep their fixed enums; what each named value _resolves to_ is now a theme's to set, through four public custom properties on the `spinner` target — `--spinner-diameter` and `--spinner-stroke-width` under a size variant, `--spinner-color` and `--spinner-track-color` under a shade variant (or on the base target for all of them at once):
+[feat] Spinner: the ring's geometry and its two colors are now themeable. The `size` and `shade` props keep their fixed enums; what each named value _resolves to_ is now a theme's to set, through four public custom properties on the `spinner` target — `--spinner-diameter` and `--spinner-stroke-width` under a size variant, `--spinner-color` and `--spinner-track-color` under a shade variant (or on the base target for all of them at once): (#5214)
```ts
spinner: {
diff --git a/.changeset/stable-resizable-snaps.md b/.changeset/stable-resizable-snaps.md
index 31f3b160e5..28458dbfb0 100644
--- a/.changeset/stable-resizable-snaps.md
+++ b/.changeset/stable-resizable-snaps.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Keep useResizable callbacks stable when snap points are omitted.
+[fix] Keep useResizable callbacks stable when snap points are omitted. (#5276)
@nynexman4464
diff --git a/.changeset/stable-use-layer.md b/.changeset/stable-use-layer.md
index 511405c2e9..c48cc5e43b 100644
--- a/.changeset/stable-use-layer.md
+++ b/.changeset/stable-use-layer.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Keep useLayer trigger refs and return objects stable when their inputs are unchanged.
+[fix] Keep useLayer trigger refs and return objects stable when their inputs are unchanged. (#5272)
@nynexman4464
diff --git a/.changeset/stable-use-theme.md b/.changeset/stable-use-theme.md
index c24c356630..f03e81c03c 100644
--- a/.changeset/stable-use-theme.md
+++ b/.changeset/stable-use-theme.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Keep useTheme token resolvers and return values stable when the resolved theme is unchanged.
+[fix] Keep useTheme token resolvers and return values stable when the resolved theme is unchanged. (#5274)
@nynexman4464
diff --git a/.changeset/sticky-column-shadow-theme-token.md b/.changeset/sticky-column-shadow-theme-token.md
index a9ac06cccd..d979333ac6 100644
--- a/.changeset/sticky-column-shadow-theme-token.md
+++ b/.changeset/sticky-column-shadow-theme-token.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Table sticky columns: the pinned-column shadow now reads the theme's `--color-shadow` token instead of a hardcoded `light-dark()` tint, so a theme can retint it.
+[fix] Table sticky columns: the pinned-column shadow now reads the theme's `--color-shadow` token instead of a hardcoded `light-dark()` tint, so a theme can retint it. (#5445)
The tint was `light-dark(rgba(0, 0, 0, 0.12), rgba(0, 0, 0, 0.32))` written in the component, chosen because `--color-shadow` (10%/30% alpha) read as slightly too faint. A literal in a component is the one place a theme cannot reach: every theme got this exact black regardless of its own shadow colour, and the two-point alpha difference bought nothing for it — rendered, the token version differs by at most 5/255 on any channel in light mode and 1/255 in dark, over the ~0.4% of the frame the two shadow strips occupy.
diff --git a/.changeset/stone-secondary-text-aa.md b/.changeset/stone-secondary-text-aa.md
index d8c7fd7515..120e6a8e26 100644
--- a/.changeset/stone-secondary-text-aa.md
+++ b/.changeset/stone-secondary-text-aa.md
@@ -2,5 +2,5 @@
'@astryxdesign/theme-stone': patch
---
-[fix] Stone theme: move `--color-text-secondary` to the canonical T40/T70 pair so normal secondary text meets WCAG AA across the theme's light and dark consumer surfaces (#5505)
+[fix] Stone theme: move `--color-text-secondary` to the canonical T40/T70 pair so normal secondary text meets WCAG AA across the theme's light and dark consumer surfaces (#5505) (#5509)
@jiunshinn
diff --git a/.changeset/syntax-punctuation-contrast.md b/.changeset/syntax-punctuation-contrast.md
index 71020cb01c..957bfe97f6 100644
--- a/.changeset/syntax-punctuation-contrast.md
+++ b/.changeset/syntax-punctuation-contrast.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Syntax-highlighted punctuation (brackets, commas, semicolons, operators) now meets WCAG 2.1 AA contrast (4.5:1) against the code surface in every bundled theme.
+[fix] Syntax-highlighted punctuation (brackets, commas, semicolons, operators) now meets WCAG 2.1 AA contrast (4.5:1) against the code surface in every bundled theme. (#5414)
`--color-syntax-punctuation` borrowed `--color-text-disabled`, a token WCAG deliberately exempts from the normal-text contrast requirement because it marks an inactive control. Punctuation in a code sample is always-active, normal text, and measured well under 4.5:1 in three themes: neutral (2.42:1 light, 2.53:1 dark), chocolate (3.06:1 light, 2.56:1 dark), and matcha (3.83:1 light, 2.73:1 dark). The other four themes (butter, gothic, stone, y2k) already defined their own passing punctuation colour and are untouched.
diff --git a/.changeset/table-filter-template.md b/.changeset/table-filter-template.md
index 134dabaa0a..b97a667676 100644
--- a/.changeset/table-filter-template.md
+++ b/.changeset/table-filter-template.md
@@ -2,7 +2,7 @@
'@astryxdesign/cli': patch
---
-[feat] New `table-filter` page template: a table page built around a filter token list
+[feat] New `table-filter` page template: a table page built around a filter token list (#5448)
Ports the feature set of the internal XDS table page pattern onto Astryx
primitives. The filter row is a token list of quick-filter toggles and field
@@ -27,4 +27,4 @@ leaves it.
Uses the `Table - Filtering` category, already reserved in the
`TemplateCategory` union.
-@ernesttien
+@ernestt
diff --git a/.changeset/table-frozen-grouped-states.md b/.changeset/table-frozen-grouped-states.md
new file mode 100644
index 0000000000..02b031a359
--- /dev/null
+++ b/.changeset/table-frozen-grouped-states.md
@@ -0,0 +1,9 @@
+---
+'@astryxdesign/core': patch
+---
+
+[fix] Table keeps grouped headings and selected-row washes visible across frozen columns while scrolling sideways (#5454)
+
+`useTableGroupedRows` pins its default heading and collapse control to the table's start edge. `useTableSelection` now publishes and withdraws the selected-row overlay with the row background, so the wash continues under sticky cells.
+
+@ernestt
diff --git a/.changeset/table-selection-sticky-overlay.md b/.changeset/table-selection-sticky-overlay.md
deleted file mode 100644
index b14f303fc7..0000000000
--- a/.changeset/table-selection-sticky-overlay.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] `useTableSelection`: the checked-row wash now survives a frozen column
-
-A sticky cell paints an opaque background of its own so scrolled content can't
-show through, then replays the row's fill on a `::before` layer from
-`--table-row-overlay`. `TableRow` publishes that variable alongside every
-background it sets, which is how striping and hover carry across the freeze
-line. Selection did not: it wrote `backgroundColor` on the `<tr>` and stopped
-there, so a checked row lost its accent wash under every pinned column — the
-row read as selected on the scrollable side and unselected on the frozen one.
-
-The wash and the variable are now written together, and withdrawn together
-when a row is unchecked or `hasRowHighlight` is turned off.
-
-@ernesttien
diff --git a/.changeset/template-data-token-fallbacks.md b/.changeset/template-data-token-fallbacks.md
deleted file mode 100644
index 4a5d6285f8..0000000000
--- a/.changeset/template-data-token-fallbacks.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/cli': patch
----
-
-[fix] Eight `var(--color-data-*, <hex>)` fallbacks in the dashboard templates named a colour their own token does not have, so the same chart series painted one colour with a theme and another without one. All eight now match the token default: `#22c55e` → `#0B991F` (categorical-green, portfolio), `#E5484D` → `#F5394F` (categorical-red, portfolio), `#008E80` → `#08A3A3` (categorical-teal, service-monitoring, cohort-funnel and data).
-
-**Visual change.** Those series shift to the token colour in a generated template. Copy the old hex in if you were relying on it.
-
-@cixzhang
diff --git a/.changeset/template-description-rewrite.md b/.changeset/template-description-rewrite.md
index 8d3a2091f0..045cfc72dc 100644
--- a/.changeset/template-description-rewrite.md
+++ b/.changeset/template-description-rewrite.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[docs] rewrite all 46 page template descriptions to describe layout, container, data shape and behaviour — the things that actually differentiate one template from its siblings — instead of the sample data they happen to ship with, so `build` and `search` retrieve them from a description of the problem rather than a guess at the slug.
+[docs] rewrite all 46 page template descriptions to describe layout, container, data shape and behaviour — the things that actually differentiate one template from its siblings — instead of the sample data they happen to ship with, so `build` and `search` retrieve them from a description of the problem rather than a guess at the slug. (#5615)
@ernestt
diff --git a/.changeset/text-single-tooltip.md b/.changeset/text-single-tooltip.md
index d09fab3d61..b617afb8c4 100644
--- a/.changeset/text-single-tooltip.md
+++ b/.changeset/text-single-tooltip.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] Text, Heading: a truncated label shows one tooltip, not two.
+[fix] Text, Heading: a truncated label shows one tooltip, not two. (#5559)
When `maxLines` clipped the text, both components rendered Astryx's `Tooltip`
**and** set the native `title` attribute to the same string. Hovering drew
diff --git a/.changeset/textarea-theme-targets.md b/.changeset/textarea-theme-targets.md
index bbef5a44fa..0986d464e3 100644
--- a/.changeset/textarea-theme-targets.md
+++ b/.changeset/textarea-theme-targets.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[feat] TextArea: the two painted elements inside the wrapper now carry stable theme targets — `astryx-text-area-control` (the `<textarea>` itself) and `astryx-text-area-counter` (the character counter). Only the wrapper was themeable before, so a theme restyling the control's own typography, placeholder or resize affordance, or the counter's supporting text, had to reach in with structural selectors like `.astryx-text-area > textarea`. Purely additive: no existing class, data attribute, or style changes.
+[feat] TextArea: the two painted elements inside the wrapper now carry stable theme targets — `astryx-text-area-control` (the `<textarea>` itself) and `astryx-text-area-counter` (the character counter). Only the wrapper was themeable before, so a theme restyling the control's own typography, placeholder or resize affordance, or the counter's supporting text, had to reach in with structural selectors like `.astryx-text-area > textarea`. Purely additive: no existing class, data attribute, or style changes. (#5418)
Neither carries a `size` axis. `size` moves only the control's block padding (`sm` and `md` are empty; `lg` sets `paddingBlock`), and that is the axis a `padding` translation for this component takes over — so an axis here would be a second way to say the same thing, and the one that stops being true once the translation lands.
diff --git a/.changeset/theme-build-color-scheme-gate.md b/.changeset/theme-build-color-scheme-gate.md
deleted file mode 100644
index b63173d464..0000000000
--- a/.changeset/theme-build-color-scheme-gate.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/cli': patch
----
-
-[fix] `astryx theme build` decides its `color-scheme` block from the theme's own token and component values rather than a substring scan of the generated CSS, and emits the `--color-data-*` defaults in `@layer astryx-base` so a built theme matches what the `<Theme>` runtime injects. Every built theme now carries those defaults, which are `light-dark()` pairs, so the old scan would have fired for every theme. The `color-scheme` output is unchanged.
-
-@cixzhang
diff --git a/.changeset/theme-css-output-no-base-field.md b/.changeset/theme-css-output-no-base-field.md
deleted file mode 100644
index 5ee1aaaf50..0000000000
--- a/.changeset/theme-css-output-no-base-field.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-'@astryxdesign/core': patch
-'@astryxdesign/cli': patch
----
-
-[fix] `generateThemeCSS` returns the two scoped blocks it has always returned — `prose` and `component`. The `--color-data-*` defaults it briefly also returned as a third `base` field are theme-independent, so they are not part of a theme's CSS: the `<Theme>` runtime keeps emitting them at `:root` in `@layer astryx-base`, and `astryx theme build` now formats the same block from the already-public `dataTokenDefaults` export. Output is byte-identical on both paths and no stable release ever carried the field.
-
-@cixzhang
diff --git a/.changeset/theme-icons-esm-only.md b/.changeset/theme-icons-esm-only.md
index 74fe264726..5b3ca6e11d 100644
--- a/.changeset/theme-icons-esm-only.md
+++ b/.changeset/theme-icons-esm-only.md
@@ -8,6 +8,6 @@
'@astryxdesign/theme-y2k': patch
---
-[fix] Theme packages no longer ship an unused CommonJS `icons.js` artifact. Their root entry keeps its advertised CommonJS and ESM outputs, while the standalone icon companion used by `/built` is emitted only as `icons.mjs`.
+[fix] Theme packages no longer ship an unused CommonJS `icons.js` artifact. Their root entry keeps its advertised CommonJS and ESM outputs, while the standalone icon companion used by `/built` is emitted only as `icons.mjs`. (#5512)
@jiunshinn
diff --git a/.changeset/theme-overrides-lost-in-vite-build.md b/.changeset/theme-overrides-lost-in-vite-build.md
index d52d16e7b9..544b8c2739 100644
--- a/.changeset/theme-overrides-lost-in-vite-build.md
+++ b/.changeset/theme-overrides-lost-in-vite-build.md
@@ -2,7 +2,7 @@
'@astryxdesign/build': patch
---
-[fix] Vite build: Astryx and product styles are split into their own cascade layers, so a theme's component overrides apply in a production build
+[fix] Vite build: Astryx and product styles are split into their own cascade layers, so a theme's component overrides apply in a production build (#5410)
@cixzhang
StyleX emits every rule it collects into one top-level `@layer
diff --git a/.changeset/theme-showcase-checkout-clipping.md b/.changeset/theme-showcase-checkout-clipping.md
index b65163c8c2..a2134796cd 100644
--- a/.changeset/theme-showcase-checkout-clipping.md
+++ b/.changeset/theme-showcase-checkout-clipping.md
@@ -2,7 +2,7 @@
'@astryxdesign/cli': patch
---
-[fix] The theme-showcase page no longer clips its own controls. In the store's product cards the quantity field and "Add to cart" button spilled out of both sides of the card; in the checkout card the card number truncated mid-number (`1234 1234 12`), the country selector ellipsized, and the pay button was left with only a few pixels of slack.
+[fix] The theme-showcase page no longer clips its own controls. In the store's product cards the quantity field and "Add to cart" button spilled out of both sides of the card; in the checkout card the card number truncated mid-number (`1234 1234 12`), the country selector ellipsized, and the pay button was left with only a few pixels of slack. (#5539)
@rubyycheung
diff --git a/.changeset/theme-target-kebab-names.md b/.changeset/theme-target-kebab-names.md
index 876ad3a389..9e5f411fee 100644
--- a/.changeset/theme-target-kebab-names.md
+++ b/.changeset/theme-target-kebab-names.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Seven theme target roots that ran a compound component name together are deprecated onto the `<component-kebab>-<part>` spelling the component's name implies: `codeblock` → `code-block` (with `-copy-button`, `-header`, `-title`), `progressbar` → `progress-bar` (with `-fill`, `-mark`, `-track`), `hovercard` → `hover-card`, `statusdot` → `status-dot`, `textarea` → `text-area`, `navicon` → `nav-icon`, and Table's second root `base-table` → `table` (both named the same `<table>` element). A `defineTheme` key that matches no target fails silently — no error, no warning, the rule never emits — so someone who read `ProgressBar` and wrote `'progress-bar'` got nothing and no explanation. Nothing breaks: every component renders both classes and both keys resolve, including the derived vars a renamed key expands into. The old spellings drop in the next major.
+[fix] Seven theme target roots that ran a compound component name together are deprecated onto the `<component-kebab>-<part>` spelling the component's name implies: `codeblock` → `code-block` (with `-copy-button`, `-header`, `-title`), `progressbar` → `progress-bar` (with `-fill`, `-mark`, `-track`), `hovercard` → `hover-card`, `statusdot` → `status-dot`, `textarea` → `text-area`, `navicon` → `nav-icon`, and Table's second root `base-table` → `table` (both named the same `<table>` element). A `defineTheme` key that matches no target fails silently — no error, no warning, the rule never emits — so someone who read `ProgressBar` and wrote `'progress-bar'` got nothing and no explanation. Nothing breaks: every component renders both classes and both keys resolve, including the derived vars a renamed key expands into. The old spellings drop in the next major. (#5449)
@cixzhang
diff --git a/.changeset/toast-render-content.md b/.changeset/toast-render-content.md
index f83daba259..04dd1812d9 100644
--- a/.changeset/toast-render-content.md
+++ b/.changeset/toast-render-content.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[feat] Toast: `renderContent` on the `showToast` options replaces the content of that toast's card with your own layout.
+[feat] Toast: `renderContent` on the `showToast` options replaces the content of that toast's card with your own layout. (#5428)
```tsx
showToast({
diff --git a/.changeset/toast-responsive-interaction.md b/.changeset/toast-responsive-interaction.md
deleted file mode 100644
index aa7b9bd2f7..0000000000
--- a/.changeset/toast-responsive-interaction.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Toast now stays within viewport and safe-area gutters; wraps long messages without clipping; keeps actions and dismissal aligned to the first text line when the message wraps; tightens inter-Toast spacing from 12px to 8px while preserving the viewport-edge gutter; collapses dismissed Toasts smoothly; enters and exits toward its configured top or bottom edge; and exposes the Notifications landmark only while Toasts are present. Placement, visible-stack limits, auto-hide defaults, announcement semantics, dismissal reasons, and browser-chrome behavior remain unchanged.
-
-@rubyycheung
diff --git a/.changeset/toast-responsive-layout-and-motion.md b/.changeset/toast-responsive-layout-and-motion.md
new file mode 100644
index 0000000000..c13b5fd6c0
--- /dev/null
+++ b/.changeset/toast-responsive-layout-and-motion.md
@@ -0,0 +1,9 @@
+---
+'@astryxdesign/core': patch
+---
+
+[fix] Toast fits narrow and safe-area viewports, aligns wrapped actions and dismissal, uses edge-directed entrance and exit motion, exposes the Notifications landmark only while populated, and keeps exactly the viewport gutter below the final toast (#5353, #5460)
+
+Inter-toast spacing is 8px, while the visual bottom no longer adds a trailing toast gap on top of viewport padding. Placement, visible-stack limits, auto-hide defaults, announcement semantics, and dismissal reasons are unchanged.
+
+@rubyycheung @cixzhang
diff --git a/.changeset/toast-viewport-trailing-gap.md b/.changeset/toast-viewport-trailing-gap.md
deleted file mode 100644
index eca63dec46..0000000000
--- a/.changeset/toast-viewport-trailing-gap.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] ToastViewport: the space below the bottom-most toast is the viewport's own padding again, not the viewport's padding plus the toast's. Each toast carries a trailing `--spacing-3` as the inter-toast gap, and the one at the visual bottom of the stack added it on top of the viewport's `--spacing-4` — 28px there against 16px on every other edge. That toast now drops its trailing gap. The flex direction flips with `position`, so it is the last toast for `bottomEnd`/`bottomStart` and the first for `topEnd`/`topStart`; all four are corrected. The gap is still padding, so entry and exit animate as before.
-
-@cixzhang
diff --git a/.changeset/transfer-list-audit-fixes.md b/.changeset/transfer-list-audit-fixes.md
deleted file mode 100644
index 65a4f76bd8..0000000000
--- a/.changeset/transfer-list-audit-fixes.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] `TransferList` clears its three remaining audit BLOCKs: the `Clear` and `Add all` header actions now meet the 24px touch-target minimum (WCAG 2.5.8) while keeping their text-link look, the add/remove/reorder glyphs render through the shared `Icon` primitive (remove reuses the registry `close` icon) instead of inline `<svg>`, and the fallback heading for ungrouped options is localized through the i18n catalog.
-
-@ernestt
diff --git a/.changeset/transfer-list-promotion-prep.md b/.changeset/transfer-list-promotion-prep.md
deleted file mode 100644
index 9125bc119c..0000000000
--- a/.changeset/transfer-list-promotion-prep.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] `TransferList` and `TransferListSelector` now route every user- and screen-reader-facing string through the i18n catalog, and no longer disable themselves while an async change is pending. Previously all 28 strings were hardcoded English literals — panel headings, row action labels, locked-item tooltips, the keyboard reorder instructions, and every live-region announcement — and item counts were pluralized by a `count === 1` ternary rather than an ICU plural, so no locale with different plural rules could ever read correctly. Separately, `TransferListSelector` wrapped its list in `<fieldset disabled={isDisabled || state.isBusy}>`, and because the user is holding focus on the Add or Remove button that started the change, disabling on busy dropped their focus to `<body>`. Busy is now carried by `aria-busy` and the trigger's existing spinner, with transfers ignored until the change settles.
-
-@ernestt
diff --git a/.changeset/treelist-forward-baseprops.md b/.changeset/treelist-forward-baseprops.md
index 514bede33e..e6716f5fcf 100644
--- a/.changeset/treelist-forward-baseprops.md
+++ b/.changeset/treelist-forward-baseprops.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] TreeList: forward `aria-label`/`aria-labelledby` to the `role="tree"` element so a tree can be named
+[fix] TreeList: forward `aria-label`/`aria-labelledby` to the `role="tree"` element so a tree can be named (#5493)
`TreeList` destructured a fixed set of props with no rest spread, so every `BaseProps` attribute (`aria-*`, `role`, `tabIndex`, `id`, event handlers) was dropped and never reached the DOM. A tree without a visible header could not be named at all - a screen reader announced an unnamed tree with no way to know what it was.