Skip to content

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

TypeScript

docs: complete v0.7.6 release metadata (#9580)

Cindy Zhang202a145f9e92
diff --git a/.changeset/a-dropdownmenu-no-longer-rewrites-its-trigger-s--83je.md b/.changeset/a-dropdownmenu-no-longer-rewrites-its-trigger-s--83je.md
index bf2d4867a8..ab62038d2b 100644
--- a/.changeset/a-dropdownmenu-no-longer-rewrites-its-trigger-s--83je.md
+++ b/.changeset/a-dropdownmenu-no-longer-rewrites-its-trigger-s--83je.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] `DropdownMenu` no longer rewrites its trigger's style on every render. Its trigger refs, and the trigger ref `usePopover` returns, now stay the same function when the popover's `onShow` or `onHide` changes, so React stops detaching and reattaching the trigger, and a tooltip anchored to the same trigger keeps its place. Triggers that take `usePopover`'s ref directly (ComplexSelector's built-in trigger, DateTimeInput's date field and Breadcrumbs) get the stable ref too.
+[fix] `DropdownMenu` no longer rewrites its trigger's style on every render. Its trigger refs, and the trigger ref `usePopover` returns, now stay the same function when the popover's `onShow` or `onHide` changes, so React stops detaching and reattaching the trigger, and a tooltip anchored to the same trigger keeps its place. Triggers that take `usePopover`'s ref directly (ComplexSelector's built-in trigger, DateTimeInput's date field and Breadcrumbs) get the stable ref too. (#9130)
@vjeux
diff --git a/.changeset/a-popover-in-a-document-picture-in-picture-windo-9gwo.md b/.changeset/a-popover-in-a-document-picture-in-picture-windo-9gwo.md
index 3b5bb08c9d..47c5d47809 100644
--- a/.changeset/a-popover-in-a-document-picture-in-picture-windo-9gwo.md
+++ b/.changeset/a-popover-in-a-document-picture-in-picture-windo-9gwo.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] A `Popover` in a Document Picture-in-Picture window now scrolls once that window gets too short for it or its content grows past it, instead of being cut off: it measures its overflow from the window it renders in, not the page.
+[fix] A `Popover` in a Document Picture-in-Picture window now scrolls once that window gets too short for it or its content grows past it, instead of being cut off: it measures its overflow from the window it renders in, not the page. (#9098)
@vjeux
diff --git a/.changeset/animated-layout-retarget-drawn-place.md b/.changeset/animated-layout-retarget-drawn-place.md
index 6fa3a737a6..30880b9250 100644
--- a/.changeset/animated-layout-retarget-drawn-place.md
+++ b/.changeset/animated-layout-retarget-drawn-place.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] In Safari, content already gliding after a layout change no longer jumps ahead when a second change retargets it, such as a row that moves again while it is still moving, or a row inside a card that is itself gliding: the new glide started up to about 3 px ahead of where the row was drawn, more the later in its frame the change was made. A gliding element's place before a change is now read on the clock of every glide that carries it, its own and its gliding containers', so the new glide starts where the old one is drawn.
+[fix] In Safari, content already gliding after a layout change no longer jumps ahead when a second change retargets it, such as a row that moves again while it is still moving, or a row inside a card that is itself gliding: the new glide started up to about 3 px ahead of where the row was drawn, more the later in its frame the change was made. A gliding element's place before a change is now read on the clock of every glide that carries it, its own and its gliding containers', so the new glide starts where the old one is drawn. (#9327)
@vjeux
diff --git a/.changeset/animator-retire-at-frame.md b/.changeset/animator-retire-at-frame.md
index 662d20525c..db8e482cf4 100644
--- a/.changeset/animator-retire-at-frame.md
+++ b/.changeset/animator-retire-at-frame.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the touch presentations' animator rechecks a finished animation's end in frame callbacks, starting a frame before it and looking again while up to two frames remain, instead of only on timers that a loaded page can run a frame or two late, so the frame that reaches the curve's end drops the animation before it paints, unless the timer that starts those rechecks itself runs more than a frame late. The timers remain for a page that draws no frames. Not exported from the package entry point.
+[chore] Internal: the touch presentations' animator rechecks a finished animation's end in frame callbacks, starting a frame before it and looking again while up to two frames remain, instead of only on timers that a loaded page can run a frame or two late, so the frame that reaches the curve's end drops the animation before it paints, unless the timer that starts those rechecks itself runs more than a frame late. The timers remain for a page that draws no frames. Not exported from the package entry point. (#9285)
@vjeux
diff --git a/.changeset/animator-retire-look-per-animation.md b/.changeset/animator-retire-look-per-animation.md
index c9b5ca0706..4aa960fcb4 100644
--- a/.changeset/animator-retire-look-per-animation.md
+++ b/.changeset/animator-retire-look-per-animation.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the touch presentations' animator keeps each animation's frame-callback recheck of its curve's end its own, so a recheck still waiting for a replaced animation no longer stands in for the next animation's, which then fell back to its timer. Not exported from the package entry point.
+[chore] Internal: the touch presentations' animator keeps each animation's frame-callback recheck of its curve's end its own, so a recheck still waiting for a replaced animation no longer stands in for the next animation's, which then fell back to its timer. Not exported from the package entry point. (#9325)
@vjeux
diff --git a/.changeset/animator-start-at-commit-frame.md b/.changeset/animator-start-at-commit-frame.md
index 2782464c48..aa4e57d2d4 100644
--- a/.changeset/animator-start-at-commit-frame.md
+++ b/.changeset/animator-start-at-commit-frame.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the touch presentations' animator starts a call from rest, made in a task, at the first frame after it when the browser has not yet told the page that start (Chromium reports a compositor's start a frame or more later), so a retarget or a rebase in that window continues from the value on screen instead of replaying the curve from its start. A call made in a frame callback, or one whose first frame comes after a block, keeps the browser's start. Not exported from the package entry point.
+[chore] Internal: the touch presentations' animator starts a call from rest, made in a task, at the first frame after it when the browser has not yet told the page that start (Chromium reports a compositor's start a frame or more later), so a retarget or a rebase in that window continues from the value on screen instead of replaying the curve from its start. A call made in a frame callback, or one whose first frame comes after a block, keeps the browser's start. Not exported from the package entry point. (#9255)
@vjeux
diff --git a/.changeset/announce-has-replace.md b/.changeset/announce-has-replace.md
index af82854a15..ba56a1d740 100644
--- a/.changeset/announce-has-replace.md
+++ b/.changeset/announce-has-replace.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] useAnnounce takes an optional `{hasReplace: true}`. An instance created with it states one current state, such as a search's result count: each message it writes withdraws that instance's previous message while it has not been spoken yet, whatever their politeness, and is spoken at its own politeness, so input faster than a frame (a barcode scanner, dictation, automation) says only the latest. Messages from other instances, and from instances without it, still join. MultiSelector sends its result count, its create row and its empty-search message through such an instance, so fast typing no longer says `1 result Create "Urg" Create "Urge" …`; its selection changes keep their own instance and still join. This follows spec:AST-086 FR9 and FR13 (#9070).
+[feat] useAnnounce takes an optional `{hasReplace: true}`. An instance created with it states one current state, such as a search's result count: each message it writes withdraws that instance's previous message while it has not been spoken yet, whatever their politeness, and is spoken at its own politeness, so input faster than a frame (a barcode scanner, dictation, automation) says only the latest. Messages from other instances, and from instances without it, still join. MultiSelector sends its result count, its create row and its empty-search message through such an instance, so fast typing no longer says `1 result Create "Urg" Create "Urge" …`; its selection changes keep their own instance and still join. This follows spec:AST-086 FR9 and FR13 (#9070). (#8640)
@vjeux
diff --git a/.changeset/appshell-layout-root.md b/.changeset/appshell-layout-root.md
index ad88b3f7ee..1d63f95a02 100644
--- a/.changeset/appshell-layout-root.md
+++ b/.changeset/appshell-layout-root.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `AppShell` is a layout root: the layout values its ancestors pass down stop at its root, so it lays out the same inside a padded `Card`, a `Section` or a `Layout` as at the page root. Before, its internal Layout escaped a padded host's padding on all four sides, so in a padded `Card` that clips its overflow the shell's logo was cut at the inline start and its navigation and content at the other edges. A caller's own props and styles on `AppShell` still apply; theme, color mode, direction and translations keep inheriting.
+[fix] `AppShell` is a layout root: the layout values its ancestors pass down stop at its root, so it lays out the same inside a padded `Card`, a `Section` or a `Layout` as at the page root. Before, its internal Layout escaped a padded host's padding on all four sides, so in a padded `Card` that clips its overflow the shell's logo was cut at the inline start and its navigation and content at the other edges. A caller's own props and styles on `AppShell` still apply; theme, color mode, direction and translations keep inheriting. (#9418)
@cixzhang @duytbp
diff --git a/.changeset/appshell-main-keyboard-scroll.md b/.changeset/appshell-main-keyboard-scroll.md
index 5e42c2123e..0e77c6174d 100644
--- a/.changeset/appshell-main-keyboard-scroll.md
+++ b/.changeset/appshell-main-keyboard-scroll.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] With `height="fill"`, AppShell's main region can be scrolled from the keyboard when its content overflows and has nothing focusable (WCAG 2.1.1 Keyboard). Before, main was only the skip link's target (`tabIndex={-1}`): Tab passed it by, so long text, a report or a read-only page could not be scrolled without a pointer. Now, while main scrolls overflowing content, it is a stop in the tab order and keyboard focus on it draws the standard focus ring, inset; in an elevated shell with a top nav and an inline side nav, main then takes the surface's rounded top-start corner so the ring follows it. Tab entry moves on when the first focusable element inside main is a plain link or button; otherwise main is one stop before it. A main region that fits, and `height="auto"` (where the page scrolls), are unchanged.
+[fix] With `height="fill"`, AppShell's main region can be scrolled from the keyboard when its content overflows and has nothing focusable (WCAG 2.1.1 Keyboard). Before, main was only the skip link's target (`tabIndex={-1}`): Tab passed it by, so long text, a report or a read-only page could not be scrolled without a pointer. Now, while main scrolls overflowing content, it is a stop in the tab order and keyboard focus on it draws the standard focus ring, inset; in an elevated shell with a top nav and an inline side nav, main then takes the surface's rounded top-start corner so the ring follows it. Tab entry moves on when the first focusable element inside main is a plain link or button; otherwise main is one stop before it. A main region that fits, and `height="auto"` (where the page scrolls), are unchanged. (#8111)
@vjeux
diff --git a/.changeset/appshell-main-release-on-detach.md b/.changeset/appshell-main-release-on-detach.md
index 95ddac03c0..f37bd38829 100644
--- a/.changeset/appshell-main-release-on-detach.md
+++ b/.changeset/appshell-main-release-on-detach.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] AppShell drops an unmount Effect that repeated the release main's ref already performs; main's overflow observation and keyboard delegation are still released on unmount. No behavior changes.
+[chore] AppShell drops an unmount Effect that repeated the release main's ref already performs; main's overflow observation and keyboard delegation are still released on unmount. No behavior changes. (#9262)
@cixzhang
diff --git a/.changeset/ast-085-dateinput.md b/.changeset/ast-085-dateinput.md
index 8de849488b..e16fdebddc 100644
--- a/.changeset/ast-085-dateinput.md
+++ b/.changeset/ast-085-dateinput.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] DateInput ignores selections from an already-open disabled picker and blocks Reset's value change and month navigation while disabled, without dismissing the picker or moving focus.
+[fix] DateInput ignores selections from an already-open disabled picker and blocks Reset's value change and month navigation while disabled, without dismissing the picker or moving focus. (#8813)
@korkt-kim
diff --git a/.changeset/ast-085-daterangeinput.md b/.changeset/ast-085-daterangeinput.md
index 95162cd9ea..5f733e66a2 100644
--- a/.changeset/ast-085-daterangeinput.md
+++ b/.changeset/ast-085-daterangeinput.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] DateRangeInput ignores calendar and preset commits after its open picker becomes disabled, without dismissing the picker or moving focus. Presets reflect the field's disabled state and reason. Enabled selection, clear behavior, and loading-only dismissal remain unchanged.
+[fix] DateRangeInput ignores calendar and preset commits after its open picker becomes disabled, without dismissing the picker or moving focus. Presets reflect the field's disabled state and reason. Enabled selection, clear behavior, and loading-only dismissal remain unchanged. (#9155)
@korkt-kim
diff --git a/.changeset/ast-085-multiselector.md b/.changeset/ast-085-multiselector.md
index c90d60d366..7b6953d6fc 100644
--- a/.changeset/ast-085-multiselector.md
+++ b/.changeset/ast-085-multiselector.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] MultiSelector blocks selection and creation callbacks and Actions when it becomes disabled while its panel is open, without removing the focused control.
+[fix] MultiSelector blocks selection and creation callbacks and Actions when it becomes disabled while its panel is open, without removing the focused control. (#9152)
@korkt-kim
diff --git a/.changeset/ast-085-selector.md b/.changeset/ast-085-selector.md
index 82bff288b5..b64bd06483 100644
--- a/.changeset/ast-085-selector.md
+++ b/.changeset/ast-085-selector.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] Selector ignores option selections after it becomes disabled, including selections from an already-open popup and pointer gestures started while enabled. Its trigger remains focusable and disabled values remain excluded from forms.
+[fix] Selector ignores option selections after it becomes disabled, including selections from an already-open popup and pointer gestures started while enabled. Its trigger remains focusable and disabled values remain excluded from forms. (#9137)
@korkt-kim
diff --git a/.changeset/avatar-initials-forced-colors.md b/.changeset/avatar-initials-forced-colors.md
index 9b18bcbd5c..cb54e716af 100644
--- a/.changeset/avatar-initials-forced-colors.md
+++ b/.changeset/avatar-initials-forced-colors.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] In forced colors (Windows High Contrast), a lone `Avatar`'s initials and default person icon now take the color around them, as the browser forces it, instead of always showing CanvasText: inside a control that paints itself disabled they show GrayText. Faces inside an `AvatarGroup` keep CanvasText on the group's ring. Outside forced colors nothing changes.
+[fix] In forced colors (Windows High Contrast), a lone `Avatar`'s initials and default person icon now take the color around them, as the browser forces it, instead of always showing CanvasText: inside a control that paints itself disabled they show GrayText. Faces inside an `AvatarGroup` keep CanvasText on the group's ring. Outside forced colors nothing changes. (#8819)
@cixzhang
diff --git a/.changeset/badge-grows-with-text.md b/.changeset/badge-grows-with-text.md
index 6bd50e4bc9..f194ee7901 100644
--- a/.changeset/badge-grows-with-text.md
+++ b/.changeset/badge-grows-with-text.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Badge: a badge with a label is now never shorter than one line of that label. With a larger text size, a badge's label grew while the badge kept its fixed height, so the label spilled out of the pill and white text on a colored badge became unreadable. The badge now grows with its label. At the default size nothing changes, a theme that sets the badge's height keeps that height there while its badges still grow with larger text, a color-only badge keeps its size at every text size, and a badge still shrinks and truncates in a container too narrow for it.
+[fix] Badge: a badge with a label is now never shorter than one line of that label. With a larger text size, a badge's label grew while the badge kept its fixed height, so the label spilled out of the pill and white text on a colored badge became unreadable. The badge now grows with its label. At the default size nothing changes, a theme that sets the badge's height keeps that height there while its badges still grow with larger text, a color-only badge keeps its size at every text size, and a badge still shrinks and truncates in a container too narrow for it. (#8236)
@vjeux
diff --git a/.changeset/bottom-sheet-drag-detent-flash.md b/.changeset/bottom-sheet-drag-detent-flash.md
index e3509361e3..83870b7cce 100644
--- a/.changeset/bottom-sheet-drag-detent-flash.md
+++ b/.changeset/bottom-sheet-drag-detent-flash.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Dragging a `BottomSheet` with snap points up from a shorter detent, or back down past it, no longer flashes the sheet away from the finger. For one frame the sheet jumped by the height its scrolling area gives up at that detent (about half the screen at a half-height stop) and then snapped back. The height and position now change in the same frame.
+[fix] Dragging a `BottomSheet` with snap points up from a shorter detent, or back down past it, no longer flashes the sheet away from the finger. For one frame the sheet jumped by the height its scrolling area gives up at that detent (about half the screen at a half-height stop) and then snapped back. The height and position now change in the same frame. (#9193)
@cixzhang
diff --git a/.changeset/bottom-sheet-nested-sheet-drag.md b/.changeset/bottom-sheet-nested-sheet-drag.md
index fe2e95f00b..f0ac29f50c 100644
--- a/.changeset/bottom-sheet-nested-sheet-drag.md
+++ b/.changeset/bottom-sheet-nested-sheet-drag.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A BottomSheet opened from inside another sheet's content drags down to dismiss on its own. The covered sheet underneath no longer takes the gesture, so dragging the top sheet's grabber no longer moves or dismisses the sheet beneath it.
+[fix] A BottomSheet opened from inside another sheet's content drags down to dismiss on its own. The covered sheet underneath no longer takes the gesture, so dragging the top sheet's grabber no longer moves or dismisses the sheet beneath it. (#8820)
@imdreamrunner
diff --git a/.changeset/bottomsheet-checklist-full-row-click.md b/.changeset/bottomsheet-checklist-full-row-click.md
index 7b70db02f0..343b87c140 100644
--- a/.changeset/bottomsheet-checklist-full-row-click.md
+++ b/.changeset/bottomsheet-checklist-full-row-click.md
@@ -2,5 +2,5 @@
'@astryxdesign/cli': patch
---
-[fix] BottomSheet checklist examples use CheckboxList so the whole row toggles, not just the label
+[fix] BottomSheet checklist examples use CheckboxList so the whole row toggles, not just the label (#9533)
@divyanshudhruv
diff --git a/.changeset/bottomsheet-comment-cleanup-2.md b/.changeset/bottomsheet-comment-cleanup-2.md
index 03453ddf35..bf170c06eb 100644
--- a/.changeset/bottomsheet-comment-cleanup-2.md
+++ b/.changeset/bottomsheet-comment-cleanup-2.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Source comments in the BottomSheet gesture and mobile keyboard code are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes.
+[docs] Source comments in the BottomSheet gesture and mobile keyboard code are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9524)
@cixzhang
diff --git a/.changeset/bottomsheet-comment-cleanup.md b/.changeset/bottomsheet-comment-cleanup.md
index 6cea1a82a2..5837a9f7cc 100644
--- a/.changeset/bottomsheet-comment-cleanup.md
+++ b/.changeset/bottomsheet-comment-cleanup.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Source comments in BottomSheet and BottomSheetSwitcher are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes.
+[docs] Source comments in BottomSheet and BottomSheetSwitcher are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9523)
@cixzhang
diff --git a/.changeset/build-readme-next-font-babel.md b/.changeset/build-readme-next-font-babel.md
index 9ebdb878cf..7ab1edf914 100644
--- a/.changeset/build-readme-next-font-babel.md
+++ b/.changeset/build-readme-next-font-babel.md
@@ -2,6 +2,6 @@
'@astryxdesign/build': patch
---
-[docs] The Next.js setup in the README says that its Babel config turns off SWC, which `next/font` needs, so a fresh `create-next-app` layout must drop its `next/font` import before the webpack source build will compile.
+[docs] The Next.js setup in the README says that its Babel config turns off SWC, which `next/font` needs, so a fresh `create-next-app` layout must drop its `next/font` import before the webpack source build will compile. (#9439)
@cixzhang
diff --git a/.changeset/build-stylex-cross-file-consts.md b/.changeset/build-stylex-cross-file-consts.md
index 736b20da43..3dd3d09748 100644
--- a/.changeset/build-stylex-cross-file-consts.md
+++ b/.changeset/build-stylex-cross-file-consts.md
@@ -2,6 +2,6 @@
'@astryxdesign/build': patch
---
-[fix] `astryxStylex` resolves `defineConsts` values read from another file. With the `{stylexOptions}` form (the one Storybook uses), a file that read only constants from a `.stylex.ts` module lost that import once StyleX compiled it, so the constants never reached the CSS: a constant used as a media-query key failed the build ("Invalid empty selector") and one used as a value shipped as a custom property nothing declares. In either form, a constant defined on the other side of the layer split, or in an Astryx package (compiled with the library class-name prefix) and read from an app file (compiled with its own), stayed unresolved.
+[fix] `astryxStylex` resolves `defineConsts` values read from another file. With the `{stylexOptions}` form (the one Storybook uses), a file that read only constants from a `.stylex.ts` module lost that import once StyleX compiled it, so the constants never reached the CSS: a constant used as a media-query key failed the build ("Invalid empty selector") and one used as a value shipped as a custom property nothing declares. In either form, a constant defined on the other side of the layer split, or in an Astryx package (compiled with the library class-name prefix) and read from an app file (compiled with its own), stayed unresolved. (#8075)
@vjeux
diff --git a/.changeset/build-stylex-undefined-variables.md b/.changeset/build-stylex-undefined-variables.md
index f96458edef..0a3267f9c0 100644
--- a/.changeset/build-stylex-undefined-variables.md
+++ b/.changeset/build-stylex-undefined-variables.md
@@ -2,6 +2,6 @@
'@astryxdesign/build': patch
---
-[feat] A production build with `astryxStylex` warns when its stylesheet reads a StyleX-generated custom property that nothing declares, naming the variable and the rule that reads it. It checks the class-name prefixes the build uses, `stylexOverrides.classNamePrefix` included, and never reports a custom property an app declares in its own CSS.
+[feat] A production build with `astryxStylex` warns when its stylesheet reads a StyleX-generated custom property that nothing declares, naming the variable and the rule that reads it. It checks the class-name prefixes the build uses, `stylexOverrides.classNamePrefix` included, and never reports a custom property an app declares in its own CSS. (#8075)
@vjeux
diff --git a/.changeset/calendar-standalone-month-capital.md b/.changeset/calendar-standalone-month-capital.md
index bb88bd0f0f..241af588a3 100644
--- a/.changeset/calendar-standalone-month-capital.md
+++ b/.changeset/calendar-standalone-month-capital.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Calendar, DateInput, DateTimeInput: a month label that stands alone starts with a capital where the locale capitalizes one. In Spanish, French, Italian, Dutch, Polish, Russian and Ukrainian, Calendar's heading read "octubre de 2026"; it now reads "Octubre de 2026", following CLDR's stand-alone capitalization, as the weekday headers already use CLDR's stand-alone names. A two-month view capitalizes both months, and each month grid's name, the touch date fields' month headings and `useCalendarNavigation`'s `monthYearLabel` do the same. Dates in running text, such as a field's value, are unchanged, and so is every locale CLDR does not capitalize, Vietnamese included.
+[fix] Calendar, DateInput, DateTimeInput: a month label that stands alone starts with a capital where the locale capitalizes one. In Spanish, French, Italian, Dutch, Polish, Russian and Ukrainian, Calendar's heading read "octubre de 2026"; it now reads "Octubre de 2026", following CLDR's stand-alone capitalization, as the weekday headers already use CLDR's stand-alone names. A two-month view capitalizes both months, and each month grid's name, the touch date fields' month headings and `useCalendarNavigation`'s `monthYearLabel` do the same. Dates in running text, such as a field's value, are unchanged, and so is every locale CLDR does not capitalize, Vietnamese included. (#9371)
@cixzhang
diff --git a/.changeset/carousel-scroll-area-name.md b/.changeset/carousel-scroll-area-name.md
index eba964bdd7..6b05b004fc 100644
--- a/.changeset/carousel-scroll-area-name.md
+++ b/.changeset/carousel-scroll-area-name.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Carousel's scroll area is a group named like the carousel, so a screen-reader user who tabs onto it hears where they are. It is a tab stop only while its content overflows; a carousel that fits no longer adds an empty stop.
+[fix] Carousel's scroll area is a group named like the carousel, so a screen-reader user who tabs onto it hears where they are. It is a tab stop only while its content overflows; a carousel that fits no longer adds an empty stop. (#8155)
@vjeux
diff --git a/.changeset/chat-pasted-text-token-tap.md b/.changeset/chat-pasted-text-token-tap.md
index cba19d9aae..66054d15a2 100644
--- a/.changeset/chat-pasted-text-token-tap.md
+++ b/.changeset/chat-pasted-text-token-tap.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] ChatComposerInput: a tap on a pasted-text token opens its preview without raising the keyboard. Before, the tap that opened the preview also focused the composer around the token and placed the caret in it, which on a phone raises the on-screen keyboard over the preview. Now a tap by finger or pen stops at the token, so touch reaches the preview and its Expand action without the keyboard covering them, the operable path `architecture:interaction-modality` INV4 asks of every modality; a mouse click on the token still places the caret in the composer, and hover still opens the preview.
+[fix] ChatComposerInput: a tap on a pasted-text token opens its preview without raising the keyboard. Before, the tap that opened the preview also focused the composer around the token and placed the caret in it, which on a phone raises the on-screen keyboard over the preview. Now a tap by finger or pen stops at the token, so touch reaches the preview and its Expand action without the keyboard covering them, the operable path `architecture:interaction-modality` INV4 asks of every modality; a mouse click on the token still places the caret in the composer, and hover still opens the preview. (#9189)
@vjeux
diff --git a/.changeset/chatcomposer-surface-press.md b/.changeset/chatcomposer-surface-press.md
index 608d7fd0ad..d86063452e 100644
--- a/.changeset/chatcomposer-surface-press.md
+++ b/.changeset/chatcomposer-surface-press.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A click inside an open Tooltip or HoverCard in a ChatComposer's body no longer moves focus to the composer's input. A click on the body's empty space still focuses it.
+[fix] A click inside an open Tooltip or HoverCard in a ChatComposer's body no longer moves focus to the composer's input. A click on the body's empty space still focuses it. (#9375)
@cixzhang
diff --git a/.changeset/chatcomposer-trigger-press-keeps-menu.md b/.changeset/chatcomposer-trigger-press-keeps-menu.md
index c172ebf8fe..ca502751c6 100644
--- a/.changeset/chatcomposer-trigger-press-keeps-menu.md
+++ b/.changeset/chatcomposer-trigger-press-keeps-menu.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A press in a ChatComposerInput's own editor no longer closes its open trigger menu (the `@` mention or `/` command list). Clicking inside the query keeps the menu showing; a click that moves the caret out of the query, a press anywhere else on the page and Escape still close it.
+[fix] A press in a ChatComposerInput's own editor no longer closes its open trigger menu (the `@` mention or `/` command list). Clicking inside the query keeps the menu showing; a click that moves the caret out of the query, a press anywhere else on the page and Escape still close it. (#9503)
@cixzhang
diff --git a/.changeset/chatmessage-avatar-rule-linear.md b/.changeset/chatmessage-avatar-rule-linear.md
index 4b9304f2d7..ed69b6e6f6 100644
--- a/.changeset/chatmessage-avatar-rule-linear.md
+++ b/.changeset/chatmessage-avatar-rule-linear.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Safari no longer slows down as a page fills a container with many children because of ChatMessage's avatar-spacing rule. The avatar's top spacing beside a named bubble is now judged from the message itself instead of from its siblings. It looks exactly as before.
+[fix] Safari no longer slows down as a page fills a container with many children because of ChatMessage's avatar-spacing rule. The avatar's top spacing beside a named bubble is now judged from the message itself instead of from its siblings. It looks exactly as before. (#9438)
@cixzhang
diff --git a/.changeset/checkboxlist-disabled-reason-describes-each-checkbox.md b/.changeset/checkboxlist-disabled-reason-describes-each-checkbox.md
index b78aff00f0..23dfa2fe1a 100644
--- a/.changeset/checkboxlist-disabled-reason-describes-each-checkbox.md
+++ b/.changeset/checkboxlist-disabled-reason-describes-each-checkbox.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] CheckboxList: a group disabled with a `disabledMessage` gives that reason to each checkbox as its description (`aria-describedby`), as well as to the group, so a screen reader announces it on the focused checkbox. A row's own description comes first.
+[fix] CheckboxList: a group disabled with a `disabledMessage` gives that reason to each checkbox as its description (`aria-describedby`), as well as to the group, so a screen reader announces it on the focused checkbox. A row's own description comes first. (#9168)
@vjeux
diff --git a/.changeset/cli-ambient-files-read-once.md b/.changeset/cli-ambient-files-read-once.md
index 678feab05f..5982369832 100644
--- a/.changeset/cli-ambient-files-read-once.md
+++ b/.changeset/cli-ambient-files-read-once.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[perf] Calling `integrationComponentConflicts()` or `integrationCheck()` from `@astryxdesign/cli/api` more than once in one process now reads each TypeScript file a package's `tsconfig.json` includes once while the file is unchanged, instead of on every call. A single `astryx doctor integration components` or `astryx integration check` run is unchanged.
+[perf] Calling `integrationComponentConflicts()` or `integrationCheck()` from `@astryxdesign/cli/api` more than once in one process now reads each TypeScript file a package's `tsconfig.json` includes once while the file is unchanged, instead of on every call. A single `astryx doctor integration components` or `astryx integration check` run is unchanged. (#9422)
@vjeux
diff --git a/.changeset/cli-search-shared-gather.md b/.changeset/cli-search-shared-gather.md
index ad205c3cb1..e9429951b3 100644
--- a/.changeset/cli-search-shared-gather.md
+++ b/.changeset/cli-search-shared-gather.md
@@ -2,5 +2,5 @@
'@astryxdesign/cli': patch
---
-[perf] `search()` shares a catalog gather that is still running: searches that start together in one long-running process, such as a docs site's search right after it starts, now gather once instead of once each
+[perf] `search()` shares a catalog gather that is still running: searches that start together in one long-running process, such as a docs site's search right after it starts, now gather once instead of once each (#9460)
@cixzhang
diff --git a/.changeset/click-guard.md b/.changeset/click-guard.md
index 7376b26fef..007d011a06 100644
--- a/.changeset/click-guard.md
+++ b/.changeset/click-guard.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture recognizers and the menu press model share one guard for the browser's click after a gesture that already acted, swallowing it for 400ms or until the next press. Keyboard and assistive-technology clicks (`detail` 0) always pass.
+[chore] Internal: the gesture recognizers and the menu press model share one guard for the browser's click after a gesture that already acted, swallowing it for 400ms or until the next press. Keyboard and assistive-technology clicks (`detail` 0) always pass. (#8360)
@vjeux
diff --git a/.changeset/clickablecard-disabled-router-link.md b/.changeset/clickablecard-disabled-router-link.md
index 8fd253d708..a107dc8f2f 100644
--- a/.changeset/clickablecard-disabled-router-link.md
+++ b/.changeset/clickablecard-disabled-router-link.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] ClickableCard: a disabled link card no longer passes an undefined `href` to the router link component, and a focused link card keeps focus when its disabled state changes.
+[fix] ClickableCard: a disabled link card no longer passes an undefined `href` to the router link component, and a focused link card keeps focus when its disabled state changes. (#8659)
@divyanshudhruv
diff --git a/.changeset/codeblock-rtl-collapse-chevron.md b/.changeset/codeblock-rtl-collapse-chevron.md
index ea1da415f7..75ff7d4cf9 100644
--- a/.changeset/codeblock-rtl-collapse-chevron.md
+++ b/.changeset/codeblock-rtl-collapse-chevron.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] CodeBlock: in right-to-left layouts the collapsed disclosure chevron now points toward the inline end (left), as other disclosure chevrons do. Expanded, it still points down.
+[fix] CodeBlock: in right-to-left layouts the collapsed disclosure chevron now points toward the inline end (left), as other disclosure chevrons do. Expanded, it still points down. (#9294)
@cixzhang
diff --git a/.changeset/collapsible-close-keeps-focus.md b/.changeset/collapsible-close-keeps-focus.md
index 1ff0a4c541..cc6f64eb60 100644
--- a/.changeset/collapsible-close-keeps-focus.md
+++ b/.changeset/collapsible-close-keeps-focus.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] When a `Collapsible` closes while keyboard focus is inside its content, for example from an owner-set `isOpen` or a group's value, focus moves to its trigger. Before, focus fell to the page, so a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). Focus anywhere else is not moved.
+[fix] When a `Collapsible` closes while keyboard focus is inside its content, for example from an owner-set `isOpen` or a group's value, focus moves to its trigger. Before, focus fell to the page, so a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). Focus anywhere else is not moved. (#9250)
@cixzhang @duytbp
diff --git a/.changeset/combobox-aria-required.md b/.changeset/combobox-aria-required.md
index 456bda4678..fd09fc4774 100644
--- a/.changeset/combobox-aria-required.md
+++ b/.changeset/combobox-aria-required.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `Typeahead` and `Tokenizer` expose their state on the combobox (WCAG 2.2 SC 4.1.2; `component:FormLayout` FR5 and AR2). Before, the combobox had no `aria-required`, so under `FormLayout defaultOptionality="required"`, where the visible "Required" marker is hidden, a screen reader announced a required field as optional; and an error status showed its message with no `aria-invalid`. Now the combobox sets `aria-required` for the resolved required state and `aria-invalid` for an error status. A caller's own `aria-required` or `aria-invalid` still applies when the field's own state is off.
+[fix] `Typeahead` and `Tokenizer` expose their state on the combobox (WCAG 2.2 SC 4.1.2; `component:FormLayout` FR5 and AR2). Before, the combobox had no `aria-required`, so under `FormLayout defaultOptionality="required"`, where the visible "Required" marker is hidden, a screen reader announced a required field as optional; and an error status showed its message with no `aria-invalid`. Now the combobox sets `aria-required` for the resolved required state and `aria-invalid` for an error status. A caller's own `aria-required` or `aria-invalid` still applies when the field's own state is off. (#9034)
@cixzhang @duytbp
diff --git a/.changeset/command-palette-pending-empty.md b/.changeset/command-palette-pending-empty.md
index 0021425693..8933215722 100644
--- a/.changeset/command-palette-pending-empty.md
+++ b/.changeset/command-palette-pending-empty.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] CommandPalette no longer shows its "Type to search" text after you have typed. While the first search is still loading, the list stays empty and the field's loading spinner shows; the no-results text appears once that search finishes with nothing. Clearing the field brings "Type to search" back.
+[fix] CommandPalette no longer shows its "Type to search" text after you have typed. While the first search is still loading, the list stays empty and the field's loading spinner shows; the no-results text appears once that search finishes with nothing. Clearing the field brings "Type to search" back. (#9420)
@cixzhang
diff --git a/.changeset/comments-error-announcement-key.md b/.changeset/comments-error-announcement-key.md
index 1e229c06ff..4536bb0dfb 100644
--- a/.changeset/comments-error-announcement-key.md
+++ b/.changeset/comments-error-announcement-key.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Comments: the failure announcement spoken for a Comments error banner now comes from the `@astryx.comments.errorAnnouncement` locale entry, so it can be translated like the rest of the component's messages.
+[fix] Comments: the failure announcement spoken for a Comments error banner now comes from the `@astryx.comments.errorAnnouncement` locale entry, so it can be translated like the rest of the component's messages. (#7902)
@HelloOjasMutreja
diff --git a/.changeset/complex-selector-popup-cap-and-chevron.md b/.changeset/complex-selector-popup-cap-and-chevron.md
index 2e476d5575..144b357d77 100644
--- a/.changeset/complex-selector-popup-cap-and-chevron.md
+++ b/.changeset/complex-selector-popup-cap-and-chevron.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] ComplexSelector's popup content keeps its last rows clear of a bottom bar the app declares through `LayerProvider`'s `inset`, instead of scrolling them underneath it, and its chevron turns at once when the person prefers reduced motion instead of animating its rotation.
+[fix] ComplexSelector's popup content keeps its last rows clear of a bottom bar the app declares through `LayerProvider`'s `inset`, instead of scrolling them underneath it, and its chevron turns at once when the person prefers reduced motion instead of animating its rotation. (#8551)
@cixzhang
diff --git a/.changeset/complexselector-tooltip-status.md b/.changeset/complexselector-tooltip-status.md
index 3535547356..0013a0711b 100644
--- a/.changeset/complexselector-tooltip-status.md
+++ b/.changeset/complexselector-tooltip-status.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] ComplexSelector: with `statusVariant="tooltip"` the status message is no longer lost. The trigger row now shows the status icon as a focusable info-tip button that reveals the message on hover, keyboard focus, or tap, and the trigger is described by that message instead of pointing at an element that did not exist. Pressing the info-tip does not open the popup.
+[fix] ComplexSelector: with `statusVariant="tooltip"` the status message is no longer lost. The trigger row now shows the status icon as a focusable info-tip button that reveals the message on hover, keyboard focus, or tap, and the trigger is described by that message instead of pointing at an element that did not exist. Pressing the info-tip does not open the popup. (#9026)
@cixzhang
diff --git a/.changeset/component-specs-move-to-docs.md b/.changeset/component-specs-move-to-docs.md
index 1ff3470acd..13f9c27467 100644
--- a/.changeset/component-specs-move-to-docs.md
+++ b/.changeset/component-specs-move-to-docs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Component specs are no longer shipped inside the npm package; they live in the repo at `docs/specs/components/`, one folder per component, beside each platform's spec. `astryx swizzle` no longer copies the component's spec file into your project. Nothing a consumer imports or renders changes.
+[docs] Component specs are no longer shipped inside the npm package; they live in the repo at `docs/specs/components/`, one folder per component, beside each platform's spec. `astryx swizzle` no longer copies the component's spec file into your project. Nothing a consumer imports or renders changes. (#9007)
@cixzhang
diff --git a/.changeset/context-menu-spring-roles.md b/.changeset/context-menu-spring-roles.md
index 228c92fdc1..ee256e1844 100644
--- a/.changeset/context-menu-spring-roles.md
+++ b/.changeset/context-menu-spring-roles.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the touch motion tables register the three context-menu springs spec:AST-094 FR4 names (`springs.contextMenuLift`, `springs.contextMenuDismiss` and `springs.contextMenuMorph`, a new row at response 0.3 s and damping ratio 0.8) as internal motion roles, so the registered roles are FR4's again. Nothing public changes: themes do not set motion roles, and no shipped component reads these springs yet.
+[chore] Internal: the touch motion tables register the three context-menu springs spec:AST-094 FR4 names (`springs.contextMenuLift`, `springs.contextMenuDismiss` and `springs.contextMenuMorph`, a new row at response 0.3 s and damping ratio 0.8) as internal motion roles, so the registered roles are FR4's again. Nothing public changes: themes do not set motion roles, and no shipped component reads these springs yet. (#9432)
@vjeux
diff --git a/.changeset/contextmenu-mounts-at-first-open.md b/.changeset/contextmenu-mounts-at-first-open.md
index db50892a8e..c41b21a368 100644
--- a/.changeset/contextmenu-mounts-at-first-open.md
+++ b/.changeset/contextmenu-mounts-at-first-open.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] A context menu that was never opened no longer mounts its menu surface; it mounts at the first open and shows as it attaches. A Table whose cells carry context menus (row expansion gives every body cell one) showed its first rows after a minute or more at 2,000 rows in Safari; it now shows them in a few seconds.
+[fix] A context menu that was never opened no longer mounts its menu surface; it mounts at the first open and shows as it attaches. A Table whose cells carry context menus (row expansion gives every body cell one) showed its first rows after a minute or more at 2,000 rows in Safari; it now shows them in a few seconds. (#9278)
@vjeux
diff --git a/.changeset/core-single-bundle-init-order.md b/.changeset/core-single-bundle-init-order.md
index 2385a51463..1a571115ee 100644
--- a/.changeset/core-single-bundle-init-order.md
+++ b/.changeset/core-single-bundle-init-order.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] An app bundled into one esbuild file (no code splitting, as no-build pages are) no longer crashes on first render with a TypeError such as "Cannot read properties of undefined (reading 'useId')" or "(reading 'useEffect')", for example when it uses `List` or `Button`. Code-split apps are unchanged and still load Core's lazy modules on demand.
+[fix] An app bundled into one esbuild file (no code splitting, as no-build pages are) no longer crashes on first render with a TypeError such as "Cannot read properties of undefined (reading 'useId')" or "(reading 'useEffect')", for example when it uses `List` or `Button`. Code-split apps are unchanged and still load Core's lazy modules on demand. (#9055)
@cixzhang @duytbp
diff --git a/.changeset/date-input-calendar-mounts-when-open.md b/.changeset/date-input-calendar-mounts-when-open.md
index bfa2989e40..812adf33bd 100644
--- a/.changeset/date-input-calendar-mounts-when-open.md
+++ b/.changeset/date-input-calendar-mounts-when-open.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] DateInput, DateRangeInput and DateTimeInput no longer build their calendar while the popover is closed. Each closed field used to mount a full month grid at page load and keep it updated, so a form with many date fields paid that cost per field. The calendar now mounts when the popover opens and opens on the field's current value. Opening, focus and dismissal are unchanged.
+[fix] DateInput, DateRangeInput and DateTimeInput no longer build their calendar while the popover is closed. Each closed field used to mount a full month grid at page load and keep it updated, so a form with many date fields paid that cost per field. The calendar now mounts when the popover opens and opens on the field's current value. Opening, focus and dismissal are unchanged. (#8902)
@harjothkhara
diff --git a/.changeset/dateinput-input-press-keeps-calendar.md b/.changeset/dateinput-input-press-keeps-calendar.md
index 2a440d04ba..ee40da70d2 100644
--- a/.changeset/dateinput-input-press-keeps-calendar.md
+++ b/.changeset/dateinput-input-press-keeps-calendar.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A press in a DateInput's own text input, on its clear button or on its label no longer closes its open calendar. Clicking into the date text to fix a digit keeps the calendar showing; a press anywhere else on the page and Escape still close it, and moving focus from anywhere in the field (its text, clear button or calendar button) to another field now closes it too.
+[fix] A press in a DateInput's own text input, on its clear button or on its label no longer closes its open calendar. Clicking into the date text to fix a digit keeps the calendar showing; a press anywhere else on the page and Escape still close it, and moving focus from anywhere in the field (its text, clear button or calendar button) to another field now closes it too. (#9433)
@cixzhang
diff --git a/.changeset/datetimeinput-time-press-keeps-list.md b/.changeset/datetimeinput-time-press-keeps-list.md
index e4be642eb2..ea0402b78a 100644
--- a/.changeset/datetimeinput-time-press-keeps-list.md
+++ b/.changeset/datetimeinput-time-press-keeps-list.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A press in a DateTimeInput's own time input no longer closes its open list of preset times. Clicking into the time text to fix a digit keeps the list showing; a press anywhere else on the page, moving focus away and Escape still close it.
+[fix] A press in a DateTimeInput's own time input no longer closes its open list of preset times. Clicking into the time text to fix a digit keeps the list showing; a press anywhere else on the page, moving focus away and Escape still close it. (#9459)
@cixzhang
diff --git a/.changeset/dialog-second-document-focus-return.md b/.changeset/dialog-second-document-focus-return.md
index 7cbe1296c8..02eca39e92 100644
--- a/.changeset/dialog-second-document-focus-return.md
+++ b/.changeset/dialog-second-document-focus-return.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] A `Dialog` rendered into a same-origin iframe through a portal now returns focus, when it closes, to the control in the iframe that opened it, as it does in the page.
+[fix] A `Dialog` rendered into a same-origin iframe through a portal now returns focus, when it closes, to the control in the iframe that opened it, as it does in the page. (#8381)
@vjeux
diff --git a/.changeset/diff-viewer-large-change-keys.md b/.changeset/diff-viewer-large-change-keys.md
index 7d70269468..b9fb3a1e87 100644
--- a/.changeset/diff-viewer-large-change-keys.md
+++ b/.changeset/diff-viewer-large-change-keys.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] Adds three `@astryx.diffViewer.*` keys to the `en` catalog for the lab `DiffViewer`'s large-change fold: its "Large change: N lines" label and its Show full diff / Hide full diff button. No existing string changes; locales without a translation fall back to English.
+[feat] Adds three `@astryx.diffViewer.*` keys to the `en` catalog for the lab `DiffViewer`'s large-change fold: its "Large change: N lines" label and its Show full diff / Hide full diff button. No existing string changes; locales without a translation fall back to English. (#9462)
@cixzhang
diff --git a/.changeset/disabled-field-focus-forced-colors.md b/.changeset/disabled-field-focus-forced-colors.md
index 7360a86084..bf19b96731 100644
--- a/.changeset/disabled-field-focus-forced-colors.md
+++ b/.changeset/disabled-field-focus-forced-colors.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled field that keeps its tab stop (TextInput, TextArea, NumberInput, Typeahead, Tokenizer, Selector, MultiSelector, and DateInput, TimeInput, DateRangeInput and DateTimeInput on every surface: popover, native and bottom sheet) now shows keyboard focus under forced colors, such as Windows High Contrast. Its focus border takes the system Highlight color there, as enabled fields' does. Nothing changes outside forced colors.
+[fix] A disabled field that keeps its tab stop (TextInput, TextArea, NumberInput, Typeahead, Tokenizer, Selector, MultiSelector, and DateInput, TimeInput, DateRangeInput and DateTimeInput on every surface: popover, native and bottom sheet) now shows keyboard focus under forced colors, such as Windows High Contrast. Its focus border takes the system Highlight color there, as enabled fields' does. Nothing changes outside forced colors. (#9410)
@cixzhang
diff --git a/.changeset/disabled-row-link-no-destination.md b/.changeset/disabled-row-link-no-destination.md
index f6a3389f38..79bcb37b5c 100644
--- a/.changeset/disabled-row-link-no-destination.md
+++ b/.changeset/disabled-row-link-no-destination.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled `Item`, `ListItem` or `TreeList` row with an `href` no longer navigates from a screen reader, Enter, or a link menu. Its link now has no `href`, `target` or `rel`, as a disabled `Link` does, and it keeps the link role.
+[fix] A disabled `Item`, `ListItem` or `TreeList` row with an `href` no longer navigates from a screen reader, Enter, or a link menu. Its link now has no `href`, `target` or `rel`, as a disabled `Link` does, and it keeps the link role. (#9056)
@cixzhang @duytbp
diff --git a/.changeset/drawer-non-modal-page-scroll.md b/.changeset/drawer-non-modal-page-scroll.md
index 8420ed1f59..47b1cc4f9b 100644
--- a/.changeset/drawer-non-modal-page-scroll.md
+++ b/.changeset/drawer-non-modal-page-scroll.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Under a finger in Chrome, the page beside an open non-modal `Drawer` (`hasScrim={false}`) scrolls again. The panel clipped its content with `overflow: hidden`, which made it a scroll container, and Chrome held a drag on the page beside it in that container's overscroll containment, so the page did not move. It now clips with `overflow: clip`, which clips the same way without a scroll container. The panel's content area still scrolls on its own, and a modal drawer is unchanged.
+[fix] Under a finger in Chrome, the page beside an open non-modal `Drawer` (`hasScrim={false}`) scrolls again. The panel clipped its content with `overflow: hidden`, which made it a scroll container, and Chrome held a drag on the page beside it in that container's overscroll containment, so the page did not move. It now clips with `overflow: clip`, which clips the same way without a scroll container. The panel's content area still scrolls on its own, and a modal drawer is unchanged. (#8636)
@vjeux
diff --git a/.changeset/dropdown-menu-docs-accuracy.md b/.changeset/dropdown-menu-docs-accuracy.md
index 4889cb0afd..2301b3e331 100644
--- a/.changeset/dropdown-menu-docs-accuracy.md
+++ b/.changeset/dropdown-menu-docs-accuracy.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] The development warning for passing both `button` and `renderTrigger` to `DropdownMenu` now names `renderTrigger`; it named a `trigger` prop that does not exist. The docs match the component too: `button` is mutually exclusive with `renderTrigger`, the private menu radius defaults to `--radius-container`, and a disabled `DropdownMenuCheckboxItem` or `DropdownMenuRadioItem` takes no focus — the arrow keys, typeahead, and the pointer highlight skip it — while it stays in the accessibility tree as disabled.
+[fix] The development warning for passing both `button` and `renderTrigger` to `DropdownMenu` now names `renderTrigger`; it named a `trigger` prop that does not exist. The docs match the component too: `button` is mutually exclusive with `renderTrigger`, the private menu radius defaults to `--radius-container`, and a disabled `DropdownMenuCheckboxItem` or `DropdownMenuRadioItem` takes no focus — the arrow keys, typeahead, and the pointer highlight skip it — while it stays in the accessibility tree as disabled. (#7517)
@cixzhang
diff --git a/.changeset/dropdown-menu-forced-colors-focus.md b/.changeset/dropdown-menu-forced-colors-focus.md
index b5b4b36f06..c9fde41f28 100644
--- a/.changeset/dropdown-menu-forced-colors-focus.md
+++ b/.changeset/dropdown-menu-forced-colors-focus.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A keyboard-focused `DropdownMenu` row now shows the standard focus ring, drawn inside the row, in every color mode. Rows showed focus only with a translucent background, which forced colors (Windows High Contrast and similar modes) replace with the page color, so a keyboard user there could not tell which row Enter would activate. The ring follows the last input: after a key press it marks the focused row, including a row the mouse then moves focus to; after a mouse or touch press it does not show. Action, destructive, checkbox, radio and sub-menu rows all show it, including in `ContextMenu` and breadcrumb menus. A `ContextMenu` opened by right-click or long-press focuses its first row without the ring; one opened from the keyboard shows it.
+[fix] A keyboard-focused `DropdownMenu` row now shows the standard focus ring, drawn inside the row, in every color mode. Rows showed focus only with a translucent background, which forced colors (Windows High Contrast and similar modes) replace with the page color, so a keyboard user there could not tell which row Enter would activate. The ring follows the last input: after a key press it marks the focused row, including a row the mouse then moves focus to; after a mouse or touch press it does not show. Action, destructive, checkbox, radio and sub-menu rows all show it, including in `ContextMenu` and breadcrumb menus. A `ContextMenu` opened by right-click or long-press focuses its first row without the ring; one opened from the keyboard shows it. (#7517)
@cixzhang
diff --git a/.changeset/dropdown-menu-popover-presentation-theming.md b/.changeset/dropdown-menu-popover-presentation-theming.md
index 11e32ab2ce..a9743f9114 100644
--- a/.changeset/dropdown-menu-popover-presentation-theming.md
+++ b/.changeset/dropdown-menu-popover-presentation-theming.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] The anchored `DropdownMenu` now reflects `data-presentation="popover"` on its `dropdown-menu` target, as the bottom sheet already reflected `bottom-sheet`. A theme rule written for `presentation:popover`, which the docs list as a visual prop of that target, now applies.
+[fix] The anchored `DropdownMenu` now reflects `data-presentation="popover"` on its `dropdown-menu` target, as the bottom sheet already reflected `bottom-sheet`. A theme rule written for `presentation:popover`, which the docs list as a visual prop of that target, now applies. (#7517)
@cixzhang
diff --git a/.changeset/dropdown-menu-sheet-trigger-ref.md b/.changeset/dropdown-menu-sheet-trigger-ref.md
index 8dcefe9da9..486dca3555 100644
--- a/.changeset/dropdown-menu-sheet-trigger-ref.md
+++ b/.changeset/dropdown-menu-sheet-trigger-ref.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `DropdownMenu` and `MoreMenu` now forward the caller's ref to the trigger button in the bottom-sheet presentation (`architecture:public-component-api` INV8). Before, `presentation="bottom-sheet"`, or `presentation="adaptive"` on a compact touch screen, replaced the `button.ref` (and the `ref` that `MoreMenu` passes) with an internal ref, so a caller's ref stayed empty. The popover presentation already forwarded it. Apps need no code change.
+[fix] `DropdownMenu` and `MoreMenu` now forward the caller's ref to the trigger button in the bottom-sheet presentation (`architecture:public-component-api` INV8). Before, `presentation="bottom-sheet"`, or `presentation="adaptive"` on a compact touch screen, replaced the `button.ref` (and the `ref` that `MoreMenu` passes) with an internal ref, so a caller's ref stayed empty. The popover presentation already forwarded it. Apps need no code change. (#8898)
@parinith-web
diff --git a/.changeset/dropdown-section-submenu.md b/.changeset/dropdown-section-submenu.md
index 2f8e37b718..b1f14f0861 100644
--- a/.changeset/dropdown-section-submenu.md
+++ b/.changeset/dropdown-section-submenu.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `DropdownMenu`, `MoreMenu` and `ContextMenu` render a submenu for a data item with nested `items` inside a `{type: 'section'}`, as they do at the top level. Before, such an item rendered as a plain row with no flyout and no `aria-haspopup`, although its type allows nested `items` there; the bottom sheet on a phone already showed it as a submenu.
+[fix] `DropdownMenu`, `MoreMenu` and `ContextMenu` render a submenu for a data item with nested `items` inside a `{type: 'section'}`, as they do at the top level. Before, such an item rendered as a plain row with no flyout and no `aria-haspopup`, although its type allows nested `items` there; the bottom sheet on a phone already showed it as a submenu. (#8858)
@cixzhang
diff --git a/.changeset/edge-reveal-reversal.md b/.changeset/edge-reveal-reversal.md
index 0c9e5fe256..8d7b8119b4 100644
--- a/.changeset/edge-reveal-reversal.md
+++ b/.changeset/edge-reveal-reversal.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] With an `animatedLayout` handle, a Collapsible or a TreeList row closed while it opens, or opened again while it closes, continues from what it shows: the content's edge stays on the content after it on every frame, instead of jumping back to fully shown or hidden. Under Reduce Motion with a touch pointer, where the content cross-fades instead, a reversal still starts its fade over.
+[fix] With an `animatedLayout` handle, a Collapsible or a TreeList row closed while it opens, or opened again while it closes, continues from what it shows: the content's edge stays on the content after it on every frame, instead of jumping back to fully shown or hidden. Under Reduce Motion with a touch pointer, where the content cross-fades instead, a reversal still starts its fade over. (#8721)
@vjeux
diff --git a/.changeset/export-field-status-placement.md b/.changeset/export-field-status-placement.md
index 3c906ab109..688ec996dc 100644
--- a/.changeset/export-field-status-placement.md
+++ b/.changeset/export-field-status-placement.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Field: `FieldStatusPlacement`, the type of every field control's `statusVariant` (`'attached' | 'detached' | 'tooltip'`), is exported from `@astryxdesign/core` and `@astryxdesign/core/Field`, so a wrapper component can type a `statusVariant` prop it forwards.
+[fix] Field: `FieldStatusPlacement`, the type of every field control's `statusVariant` (`'attached' | 'detached' | 'tooltip'`), is exported from `@astryxdesign/core` and `@astryxdesign/core/Field`, so a wrapper component can type a `statusVariant` prop it forwards. (#9368)
@cixzhang
diff --git a/.changeset/field-focus-forced-colors.md b/.changeset/field-focus-forced-colors.md
index abd5cd105f..4b7c58863c 100644
--- a/.changeset/field-focus-forced-colors.md
+++ b/.changeset/field-focus-forced-colors.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Enabled Field inputs (TextInput, TextArea, NumberInput, Selector, MultiSelector, Typeahead, Tokenizer, and the date and time inputs) now show keyboard focus under forced colors, such as Windows High Contrast. Forced colors drop the inset focus shadow and repaint every border in one system color, so a focused field looked the same as one at rest. A focused field's border now takes the system Highlight color there, with or without a status. Disabled fields, which stay focusable, don't get it yet. Nothing changes outside forced colors.
+[fix] Enabled Field inputs (TextInput, TextArea, NumberInput, Selector, MultiSelector, Typeahead, Tokenizer, and the date and time inputs) now show keyboard focus under forced colors, such as Windows High Contrast. Forced colors drop the inset focus shadow and repaint every border in one system color, so a focused field looked the same as one at rest. A focused field's border now takes the system Highlight color there, with or without a status. Disabled fields, which stay focusable, don't get it yet. Nothing changes outside forced colors. (#9392)
@cixzhang
diff --git a/.changeset/field-status-long-token-wrap.md b/.changeset/field-status-long-token-wrap.md
index 279af5e550..1301b47355 100644
--- a/.changeset/field-status-long-token-wrap.md
+++ b/.changeset/field-status-long-token-wrap.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] FieldStatus wraps a long unbroken word in a validation message, such as an email address or URL echoed from the field, inside the message box instead of painting it past the field's edge where its end could not be read.
+[fix] FieldStatus wraps a long unbroken word in a validation message, such as an email address or URL echoed from the field, inside the message box instead of painting it past the field's edge where its end could not be read. (#9126)
@cixzhang
diff --git a/.changeset/fieldlabel-info-icon-tap.md b/.changeset/fieldlabel-info-icon-tap.md
index db84de8dbf..c0e1176dde 100644
--- a/.changeset/fieldlabel-info-icon-tap.md
+++ b/.changeset/fieldlabel-info-icon-tap.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] FieldLabel: a tap on the label's info icon (`labelTooltip`) opens its help without also toggling or focusing the control (`component:FieldLabel` FR9). Before, the tap that opened the help also activated the label's control, as a tap anywhere on a native label does: on a touch screen it focused the field, raising the keyboard, or toggled the switch or checkbox the label names, an unintended second action. Now a tap by finger or pen opens the help alone; a mouse click on the icon still activates the control like the rest of the label, and hover still shows the help.
+[feat] FieldLabel: a tap on the label's info icon (`labelTooltip`) opens its help without also toggling or focusing the control (`component:FieldLabel` FR9). Before, the tap that opened the help also activated the label's control, as a tap anywhere on a native label does: on a touch screen it focused the field, raising the keyboard, or toggled the switch or checkbox the label names, an unintended second action. Now a tap by finger or pen opens the help alone; a mouse click on the icon still activates the control like the rest of the label, and hover still shows the help. (#9089)
@vjeux
diff --git a/.changeset/fields-keep-field-label-with-caller-labelledby.md b/.changeset/fields-keep-field-label-with-caller-labelledby.md
index 5b25a28a13..4ba73c7436 100644
--- a/.changeset/fields-keep-field-label-with-caller-labelledby.md
+++ b/.changeset/fields-keep-field-label-with-caller-labelledby.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] TextArea, Typeahead and Tokenizer: a caller's `aria-labelledby` no longer replaces the field's own label. Before, it was the only name the control had, so `label="Notes" aria-labelledby="billing-heading"` named the textarea "Billing". Now the caller's ids follow the field's own label ("Notes Billing"), as TextInput, NumberInput, Selector and MultiSelector already do. A Typeahead inside an InputGroup, which ignored the caller's ids altogether, is now named by the group, its label, then the caller's ids. The visible label stays in the accessible name (WCAG 2.2 SC 2.5.3 Label in Name; `family:input-fields` FR10.1). Fields without a caller `aria-labelledby` are unchanged. No API changes.
+[fix] TextArea, Typeahead and Tokenizer: a caller's `aria-labelledby` no longer replaces the field's own label. Before, it was the only name the control had, so `label="Notes" aria-labelledby="billing-heading"` named the textarea "Billing". Now the caller's ids follow the field's own label ("Notes Billing"), as TextInput, NumberInput, Selector and MultiSelector already do. A Typeahead inside an InputGroup, which ignored the caller's ids altogether, is now named by the group, its label, then the caller's ids. The visible label stays in the accessible name (WCAG 2.2 SC 2.5.3 Label in Name; `family:input-fields` FR10.1). Fields without a caller `aria-labelledby` are unchanged. No API changes. (#8862)
@HelloOjasMutreja
diff --git a/.changeset/fieldstatus-tooltip-deprecated.md b/.changeset/fieldstatus-tooltip-deprecated.md
index ca5dcd9961..e5c03087ee 100644
--- a/.changeset/fieldstatus-tooltip-deprecated.md
+++ b/.changeset/fieldstatus-tooltip-deprecated.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[feat] FieldStatus: the `tooltip` variant is deprecated and is removed in the next minor release. FieldStatus has no tooltip presentation: a direct `<FieldStatus variant="tooltip">` draws a plain message box with no tooltip, and your editor now marks it deprecated. To show a status message from a field's on-field icon, set `statusVariant="tooltip"` on the field control instead; that stays supported.
+[feat] FieldStatus: the `tooltip` variant is deprecated and is removed in the next minor release. FieldStatus has no tooltip presentation: a direct `<FieldStatus variant="tooltip">` draws a plain message box with no tooltip, and your editor now marks it deprecated. To show a status message from a field's on-field icon, set `statusVariant="tooltip"` on the field control instead; that stays supported. (#9196)
Before:
diff --git a/.changeset/file-input-tooltip-status-reachable.md b/.changeset/file-input-tooltip-status-reachable.md
index 552104885f..cf92c0c8f3 100644
--- a/.changeset/file-input-tooltip-status-reachable.md
+++ b/.changeset/file-input-tooltip-status-reachable.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] FileInput with `statusVariant="tooltip"` keeps its status button, and the message it reveals, in dropzone mode and while the field is busy (loading or uploading), instead of dropping it and leaving the field's description pointing at nothing.
+[fix] FileInput with `statusVariant="tooltip"` keeps its status button, and the message it reveals, in dropzone mode and while the field is busy (loading or uploading), instead of dropping it and leaving the field's description pointing at nothing. (#9134)
@cixzhang
diff --git a/.changeset/fileinput-caller-aria-on-trigger.md b/.changeset/fileinput-caller-aria-on-trigger.md
index 5bb8b5269d..3cf1661b52 100644
--- a/.changeset/fileinput-caller-aria-on-trigger.md
+++ b/.changeset/fileinput-caller-aria-on-trigger.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] FileInput: a caller's `aria-describedby` and other `aria-*` props now reach the trigger button, the field's focusable control. Before they were set only on the hidden native input, which is `aria-hidden` and never focused, so `aria-describedby="hint"` was never read ("Report" announced without "PDF only, up to 10 MB"). The caller's ids are now joined to the trigger's own description ids, first. The props the trigger composes itself (`aria-label`, `aria-labelledby`, `aria-invalid`, `aria-busy`, `aria-disabled`, `aria-hidden`) are not copied. See `family:input-fields` FR10.1. No API changes.
+[fix] FileInput: a caller's `aria-describedby` and other `aria-*` props now reach the trigger button, the field's focusable control. Before they were set only on the hidden native input, which is `aria-hidden` and never focused, so `aria-describedby="hint"` was never read ("Report" announced without "PDF only, up to 10 MB"). The caller's ids are now joined to the trigger's own description ids, first. The props the trigger composes itself (`aria-label`, `aria-labelledby`, `aria-invalid`, `aria-busy`, `aria-disabled`, `aria-hidden`) are not copied. See `family:input-fields` FR10.1. No API changes. (#9031)
@HelloOjasMutreja
diff --git a/.changeset/fileinput-dropzone-status-variant-docs.md b/.changeset/fileinput-dropzone-status-variant-docs.md
index c374e9ef22..bf6f5d8363 100644
--- a/.changeset/fileinput-dropzone-status-variant-docs.md
+++ b/.changeset/fileinput-dropzone-status-variant-docs.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[docs] FileInput's `statusVariant` docs say that dropzone mode does not support `attached`; use `detached` or `tooltip` there. Rendering is unchanged in this release. From the next minor release, a dropzone resolves `attached` to `detached` and defaults to it.
+[docs] FileInput's `statusVariant` docs say that dropzone mode does not support `attached`; use `detached` or `tooltip` there. Rendering is unchanged in this release. From the next minor release, a dropzone resolves `attached` to `detached` and defaults to it. (#9258)
@cixzhang
diff --git a/.changeset/fileinput-every-rejection.md b/.changeset/fileinput-every-rejection.md
index bbd5f9bb6b..a4646418de 100644
--- a/.changeset/fileinput-every-rejection.md
+++ b/.changeset/fileinput-every-rejection.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] When several picked or dropped files break `accept` or `maxSize`, `FileInput` names every rejected file and why in its status message, not only the first (WCAG 2.2 SC 3.3.1). The messages are listed in the active locale. Going over `maxFiles` still reports the limit, "Maximum N files allowed".
+[fix] When several picked or dropped files break `accept` or `maxSize`, `FileInput` names every rejected file and why in its status message, not only the first (WCAG 2.2 SC 3.3.1). The messages are listed in the active locale. Going over `maxFiles` still reports the limit, "Maximum N files allowed". (#9043)
@cixzhang @duytbp
diff --git a/.changeset/fileinput-prettier-format.md b/.changeset/fileinput-prettier-format.md
index ac74b4d498..bf5135f373 100644
--- a/.changeset/fileinput-prettier-format.md
+++ b/.changeset/fileinput-prettier-format.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] FileInput's source is formatted with the repository's Prettier settings. No behavior changes.
+[chore] FileInput's source is formatted with the repository's Prettier settings. No behavior changes. (#9263)
@cixzhang
diff --git a/.changeset/fileinput-slider-form-required.md b/.changeset/fileinput-slider-form-required.md
index 7fbd0b9d11..c7cd2cc59a 100644
--- a/.changeset/fileinput-slider-form-required.md
+++ b/.changeset/fileinput-slider-form-required.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Inside `<FormLayout defaultOptionality="required">`, FileInput and Slider now tell screen readers they are required even without their own `isRequired`, like the other fields. `isOptional` still opts a field out.
+[fix] Inside `<FormLayout defaultOptionality="required">`, FileInput and Slider now tell screen readers they are required even without their own `isRequired`, like the other fields. `isOptional` still opts a field out. (#9053)
@cixzhang
diff --git a/.changeset/gesture-arena-moving-cancel.md b/.changeset/gesture-arena-moving-cancel.md
index 5b7e52cad1..1c3cd4400d 100644
--- a/.changeset/gesture-arena-moving-cancel.md
+++ b/.changeset/gesture-arena-moving-cancel.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: a gesture that cancels itself on a finger's move (a long press dragged past its tolerance) keeps that finger claimed until it lifts, so the page never takes the drag over midway; a resting finger is still given back when its gesture is cancelled. Not exported from the package entry point.
+[chore] Internal: a gesture that cancels itself on a finger's move (a long press dragged past its tolerance) keeps that finger claimed until it lifts, so the page never takes the drag over midway; a resting finger is still given back when its gesture is cancelled. Not exported from the package entry point. (#8076)
@vjeux
diff --git a/.changeset/gesture-browser-negotiation.md b/.changeset/gesture-browser-negotiation.md
index 1be0500883..68bcccd3ee 100644
--- a/.changeset/gesture-browser-negotiation.md
+++ b/.changeset/gesture-browser-negotiation.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: touch-action derivation, the native scroll probe and haptics for the gesture system. Not exported from the package entry point; no component uses them yet.
+[chore] Internal: touch-action derivation, the native scroll probe and haptics for the gesture system. Not exported from the package entry point; no component uses them yet. (#8071)
@vjeux
diff --git a/.changeset/gesture-doc-comments-placement.md b/.changeset/gesture-doc-comments-placement.md
index 617529f674..f1fd7ff186 100644
--- a/.changeset/gesture-doc-comments-placement.md
+++ b/.changeset/gesture-doc-comments-placement.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] The gesture arena's and the gesture host's internal doc comments sit on the declarations they describe.
+[docs] The gesture arena's and the gesture host's internal doc comments sit on the declarations they describe. (#9114)
@vjeux
diff --git a/.changeset/gesture-hook-fixes.md b/.changeset/gesture-hook-fixes.md
index 87f08a0948..aa6bf41925 100644
--- a/.changeset/gesture-hook-fixes.md
+++ b/.changeset/gesture-hook-fixes.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture hooks call nothing back after unmount; `usePressTracker` brakes with the host by default and keeps one tracker, so an option change or a new ref never drops a press in progress; the recognizer's arena plumbing is `protected`. Not exported from the package entry point.
+[chore] Internal: the gesture hooks call nothing back after unmount; `usePressTracker` brakes with the host by default and keeps one tracker, so an option change or a new ref never drops a press in progress; the recognizer's arena plumbing is `protected`. Not exported from the package entry point. (#8360)
@vjeux
diff --git a/.changeset/gesture-host-fixes.md b/.changeset/gesture-host-fixes.md
index 3609238c3d..6777f5888d 100644
--- a/.changeset/gesture-host-fixes.md
+++ b/.changeset/gesture-host-fixes.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: gesture host fixes from review. A claimed pen holds only its own stylus touches, and a finger is matched to its scroller, its target and a moving element along the flat tree, through slots and shadow roots. Not exported from the package entry point.
+[chore] Internal: gesture host fixes from review. A claimed pen holds only its own stylus touches, and a finger is matched to its scroller, its target and a moving element along the flat tree, through slots and shadow roots. Not exported from the package entry point. (#8360)
@vjeux
diff --git a/.changeset/gesture-host-owner.md b/.changeset/gesture-host-owner.md
index c4e1adeb8b..60d3c4adbb 100644
--- a/.changeset/gesture-host-owner.md
+++ b/.changeset/gesture-host-owner.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture host becomes the one document-level touch owner: the finger count, touch gates, and a kept press for continuous-tracking controls, whose element gets `touch-action: manipulation`. A scroll lock's page hold and the finger-scroll watch keep their own listeners and ask the host only about the touches it owns. A second finger fails a one-finger pan that has not claimed, so the page can pinch. A scroll-edge pan holds a lone finger from the first move that pulls away from an edge every scroller under it is at, so those moves are cancelled before it begins; with a second finger anywhere on the screen the page keeps its pinch. A press tracker whose hold acts (a stepper's hold-repeat) can bring a selection lock for its presses, as a recognizer can. Internal, for the touch components that adopt them; not exported from the package entry point.
+[chore] Internal: the gesture host becomes the one document-level touch owner: the finger count, touch gates, and a kept press for continuous-tracking controls, whose element gets `touch-action: manipulation`. A scroll lock's page hold and the finger-scroll watch keep their own listeners and ask the host only about the touches it owns. A second finger fails a one-finger pan that has not claimed, so the page can pinch. A scroll-edge pan holds a lone finger from the first move that pulls away from an edge every scroller under it is at, so those moves are cancelled before it begins; with a second finger anywhere on the screen the page keeps its pinch. A press tracker whose hold acts (a stepper's hold-repeat) can bring a selection lock for its presses, as a recognizer can. Internal, for the touch components that adopt them; not exported from the package entry point. (#8360)
@vjeux
diff --git a/.changeset/gesture-host.md b/.changeset/gesture-host.md
index 5b0b9fd7c2..4ea55a3127 100644
--- a/.changeset/gesture-host.md
+++ b/.changeset/gesture-host.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture system's DOM host (claims, click suppression, the browser's takeover, the pointer behind a contact), serving a mouse, a pen and a finger alike, with no page listener while idle where the primary pointer is fine. Not exported from the package entry point; no component uses it yet.
+[chore] Internal: the gesture system's DOM host (claims, click suppression, the browser's takeover, the pointer behind a contact), serving a mouse, a pen and a finger alike, with no page listener while idle where the primary pointer is fine. Not exported from the package entry point; no component uses it yet. (#8071)
@vjeux
diff --git a/.changeset/gesture-press-tracking.md b/.changeset/gesture-press-tracking.md
index e964301a57..4c83c724ea 100644
--- a/.changeset/gesture-press-tracking.md
+++ b/.changeset/gesture-press-tracking.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: UIControl press tracking with control and cell profiles and the gesture hooks. Not exported from the package entry point.
+[chore] Internal: UIControl press tracking with control and cell profiles and the gesture hooks. Not exported from the package entry point. (#8076)
@vjeux
diff --git a/.changeset/gesture-readme.md b/.changeset/gesture-readme.md
index 9a6293b811..8cbcaf8cab 100644
--- a/.changeset/gesture-readme.md
+++ b/.changeset/gesture-readme.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture system's README for component authors, with its browser proof in Chromium and WebKit.
+[chore] Internal: the gesture system's README for component authors, with its browser proof in Chromium and WebKit. (#8076)
@vjeux
diff --git a/.changeset/gesture-recognizer-fixes.md b/.changeset/gesture-recognizer-fixes.md
index 9e6754a78d..dc0e550d68 100644
--- a/.changeset/gesture-recognizer-fixes.md
+++ b/.changeset/gesture-recognizer-fixes.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: gesture recognizer and arena fixes from review; a pan claims nothing before it begins at 10 pt; one velocity tracker for every gesture (`spec:AST-100`: UIKit's measured blend, a scrolling surface's release through the pan's `scrollVelocity()`, and FR2's release rules). Not exported from the package entry point.
+[chore] Internal: gesture recognizer and arena fixes from review; a pan claims nothing before it begins at 10 pt; one velocity tracker for every gesture (`spec:AST-100`: UIKit's measured blend, a scrolling surface's release through the pan's `scrollVelocity()`, and FR2's release rules). Not exported from the package entry point. (#8360)
@vjeux
diff --git a/.changeset/gesture-swipe-pinch-edge.md b/.changeset/gesture-swipe-pinch-edge.md
index 27c89e4323..d51274a1da 100644
--- a/.changeset/gesture-swipe-pinch-edge.md
+++ b/.changeset/gesture-swipe-pinch-edge.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: swipe, pinch and screen-edge pan gesture recognizers. Not exported from the package entry point; no component uses them yet.
+[chore] Internal: swipe, pinch and screen-edge pan gesture recognizers. Not exported from the package entry point; no component uses them yet. (#8061)
@vjeux
diff --git a/.changeset/gesture-watcher.md b/.changeset/gesture-watcher.md
index bec7cd286e..24a12934e7 100644
--- a/.changeset/gesture-watcher.md
+++ b/.changeset/gesture-watcher.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: a recognizer created with `claimsTouches: false` is a watcher: passive listeners only, simultaneous with every recognizer, and it follows a touch the browser takes for a scroll to the lift. Not exported from the package entry point.
+[chore] Internal: a recognizer created with `claimsTouches: false` is a watcher: passive listeners only, simultaneous with every recognizer, and it follows a touch the browser takes for a scroll to the lift. Not exported from the package entry point. (#8360)
@vjeux
diff --git a/.changeset/gestures-every-pointer.md b/.changeset/gestures-every-pointer.md
index bd76644fd6..4bbff436f6 100644
--- a/.changeset/gestures-every-pointer.md
+++ b/.changeset/gestures-every-pointer.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: with the gesture host serving every pointer, a press tracker takes a mouse press as a press, painting at once with no scroll brake (AST-094 FR11); a finger's or a pen's hold that does something keeps text unselected under any primary pointer, a touchscreen laptop's included, while a mouse keeps its released behavior (FR41); a finger is read once where the browser sends Touch Events without exposing `ontouchstart`; and `perEventPointer`, from before FR43, is accepted and does nothing. Not exported from the package entry point.
+[chore] Internal: with the gesture host serving every pointer, a press tracker takes a mouse press as a press, painting at once with no scroll brake (AST-094 FR11); a finger's or a pen's hold that does something keeps text unselected under any primary pointer, a touchscreen laptop's included, while a mouse keeps its released behavior (FR41); a finger is read once where the browser sends Touch Events without exposing `ontouchstart`; and `perEventPointer`, from before FR43, is accepted and does nothing. Not exported from the package entry point. (#8360)
@vjeux
diff --git a/.changeset/grid-align-justify-default-docs.md b/.changeset/grid-align-justify-default-docs.md
index 9d933c6f4c..5167520abf 100644
--- a/.changeset/grid-align-justify-default-docs.md
+++ b/.changeset/grid-align-justify-default-docs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Grid's `align` and `justify` docs no longer claim a `'stretch'` default. Unset, they leave the browser default, `normal`, which stretches items that have no natural size or aspect ratio. Rendering is unchanged.
+[docs] Grid's `align` and `justify` docs no longer claim a `'stretch'` default. Unset, they leave the browser default, `normal`, which stretches items that have no natural size or aspect ratio. Rendering is unchanged. (#9347)
@cixzhang
diff --git a/.changeset/grid-span-audit-docs.md b/.changeset/grid-span-audit-docs.md
index c2f919815e..53adb7348c 100644
--- a/.changeset/grid-span-audit-docs.md
+++ b/.changeset/grid-span-audit-docs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] GridSpan: document the `xstyle`, `className`, `style`, and `ref` props, including that a set `columns` or `rows` replaces the same grid placement in `style`.
+[docs] GridSpan: document the `xstyle`, `className`, `style`, and `ref` props, including that a set `columns` or `rows` replaces the same grid placement in `style`. (#9312)
@cixzhang
diff --git a/.changeset/group-last-member-linear-in-webkit.md b/.changeset/group-last-member-linear-in-webkit.md
index d2e17020ca..2ae3d2214a 100644
--- a/.changeset/group-last-member-linear-in-webkit.md
+++ b/.changeset/group-last-member-linear-in-webkit.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] ButtonGroup and InputGroup: the rule that rounds a group's last member no longer slows down filling a container in WebKit (as measured), on any page, groups or not. In WebKit, inserting 10,000 children into one element took about 1.15 s with the old rule on the page and about 10 ms with the new one. Corners look exactly as before: only the last member, skipping trailing popovers, templates and dialogs, rounds its trailing corners.
+[fix] ButtonGroup and InputGroup: the rule that rounds a group's last member no longer slows down filling a container in WebKit (as measured), on any page, groups or not. In WebKit, inserting 10,000 children into one element took about 1.15 s with the old rule on the page and about 10 ms with the new one. Corners look exactly as before: only the last member, skipping trailing popovers, templates and dialogs, rounds its trailing corners. (#9394)
@cixzhang
diff --git a/.changeset/heading-audit-docs.md b/.changeset/heading-audit-docs.md
index a865ea249a..f8ab60864c 100644
--- a/.changeset/heading-audit-docs.md
+++ b/.changeset/heading-audit-docs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Heading: document the `xstyle`, `className`, `style`, and `ref` props, including that a `maxLines` above 1 replaces any `WebkitLineClamp` passed in `style`.
+[docs] Heading: document the `xstyle`, `className`, `style`, and `ref` props, including that a `maxLines` above 1 replaces any `WebkitLineClamp` passed in `style`. (#9328)
@cixzhang
diff --git a/.changeset/heading-menu-accessible-name.md b/.changeset/heading-menu-accessible-name.md
index 159ef4afcf..ac3e328d02 100644
--- a/.changeset/heading-menu-accessible-name.md
+++ b/.changeset/heading-menu-accessible-name.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] Include the visible heading in SideNavHeading and TopNavHeading menu button names, with or without heading links. Keep the translated generic name when TopNavHeading has no heading.
+[fix] Include the visible heading in SideNavHeading and TopNavHeading menu button names, with or without heading links. Keep the translated generic name when TopNavHeading has no heading. (#9329)
@korkt-kim
diff --git a/.changeset/hide-numberinput-s-compact-stepper-buttons-on-co-6epw.md b/.changeset/hide-numberinput-s-compact-stepper-buttons-on-co-6epw.md
index c10efe60bb..f0e32728af 100644
--- a/.changeset/hide-numberinput-s-compact-stepper-buttons-on-co-6epw.md
+++ b/.changeset/hide-numberinput-s-compact-stepper-buttons-on-co-6epw.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[feat] Adapt NumberInput's compact steppers to primary-pointer precision: hide them on coarse pointers and restore the field's themed end padding. Fine-pointer steppers are unchanged.
+[feat] Adapt NumberInput's compact steppers to primary-pointer precision: hide them on coarse pointers and restore the field's themed end padding. Fine-pointer steppers are unchanged. (#8015)
Compatibility: this is a non-breaking presentation adaptation. The public props and exports, numeric value and callback contracts, validation, direct entry, and keyboard stepping remain unchanged; existing NumberInput calls require no source or configuration migration. Coarse-pointer users enter the value directly instead of using the compact visual stepper aids.
diff --git a/.changeset/hooks-comment-cleanup-2.md b/.changeset/hooks-comment-cleanup-2.md
index b9c9dcf0cc..4c85eac466 100644
--- a/.changeset/hooks-comment-cleanup-2.md
+++ b/.changeset/hooks-comment-cleanup-2.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] More source comments in the core hooks are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes.
+[docs] More source comments in the core hooks are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9520)
@cixzhang
diff --git a/.changeset/hooks-comment-cleanup.md b/.changeset/hooks-comment-cleanup.md
index 6338ca2848..83672ac2e6 100644
--- a/.changeset/hooks-comment-cleanup.md
+++ b/.changeset/hooks-comment-cleanup.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Source comments in the core hooks are shorter and explain only non-obvious reasons. A few hook doc comments are reworded. Nothing a consumer imports or renders changes.
+[docs] Source comments in the core hooks are shorter and explain only non-obvious reasons. A few hook doc comments are reworded. Nothing a consumer imports or renders changes. (#9514)
@cixzhang
diff --git a/.changeset/hover-card-audit-docs.md b/.changeset/hover-card-audit-docs.md
index f93ac664a5..85256a1e8c 100644
--- a/.changeset/hover-card-audit-docs.md
+++ b/.changeset/hover-card-audit-docs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] HoverCard: document the `xstyle`, `className`, `style`, and `isOpen` props in every doc language, say that a text trigger is wrapped for you and an element trigger needs no ref, and say that `hasHoverIndication` applies to text triggers only.
+[docs] HoverCard: document the `xstyle`, `className`, `style`, and `isOpen` props in every doc language, say that a text trigger is wrapped for you and an element trigger needs no ref, and say that `hasHoverIndication` applies to text triggers only. (#9536)
@cixzhang
diff --git a/.changeset/hover-layers-disabled-reason-tap.md b/.changeset/hover-layers-disabled-reason-tap.md
index f1ad87acf8..d29874452a 100644
--- a/.changeset/hover-layers-disabled-reason-tap.md
+++ b/.changeset/hover-layers-disabled-reason-tap.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Tooltip and HoverCard: a tap on a disabled `Button`, `IconButton` or `ToggleButton`, or a disabled menu item, now opens the tooltip that explains why it is disabled, and nothing activates. Before, with `touchTrigger="auto"` (the default), the tap counted as the control's own action, so on a touch screen the disabled reason could not be reached (`spec:AST-085` FR5, `architecture:interaction-modality` INV4). An `aria-disabled` control now performs no action, and a tap on a label for a disabled control opens its reason too. A tap on a disabled control inside another acting trigger, such as an option row or a link-role card, now opens that trigger's tooltip or hover card. Taps on enabled controls, `touchTrigger="tap"` and `"none"`, and mouse hover are unchanged.
+[fix] Tooltip and HoverCard: a tap on a disabled `Button`, `IconButton` or `ToggleButton`, or a disabled menu item, now opens the tooltip that explains why it is disabled, and nothing activates. Before, with `touchTrigger="auto"` (the default), the tap counted as the control's own action, so on a touch screen the disabled reason could not be reached (`spec:AST-085` FR5, `architecture:interaction-modality` INV4). An `aria-disabled` control now performs no action, and a tap on a label for a disabled control opens its reason too. A tap on a disabled control inside another acting trigger, such as an option row or a link-role card, now opens that trigger's tooltip or hover card. Taps on enabled controls, `touchTrigger="tap"` and `"none"`, and mouse hover are unchanged. (#8207)
@vjeux
diff --git a/.changeset/hstack-audit-docs.md b/.changeset/hstack-audit-docs.md
index eb915dc195..94b6dd4a83 100644
--- a/.changeset/hstack-audit-docs.md
+++ b/.changeset/hstack-audit-docs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] HStack: say that items follow the writing direction (right to left in RTL), that an explicit `hAlign` or `vAlign` wins over its `justify` or `align` alias, and document the `className`, `style`, and `ref` props.
+[docs] HStack: say that items follow the writing direction (right to left in RTL), that an explicit `hAlign` or `vAlign` wins over its `justify` or `align` alias, and document the `className`, `style`, and `ref` props. (#9540)
@cixzhang
diff --git a/.changeset/input-stream-recognizers.md b/.changeset/input-stream-recognizers.md
index f836fbddad..79575a3a89 100644
--- a/.changeset/input-stream-recognizers.md
+++ b/.changeset/input-stream-recognizers.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture recognizers hear page-wide input through the same shared stream on the window's capture phase, so an app's window-capture `stopPropagation`, or a document-capture `stopImmediatePropagation` registered before Core, no longer hides a touch from them; a recognizer that must claim a touch mid-gesture still needs the touch to reach its element. Each event type's listener is passive unless a subscriber cancels it (the gesture host's `touchend` and `contextmenu` while a claiming recognizer or press tracker is attached, the page hold's `touchmove` while it holds, and the click guard's `click` while it is armed, and from the menu press model's first arm on), so a page of pressables registers no listener that can hold a scroll.
+[chore] Internal: the gesture recognizers hear page-wide input through the same shared stream on the window's capture phase, so an app's window-capture `stopPropagation`, or a document-capture `stopImmediatePropagation` registered before Core, no longer hides a touch from them; a recognizer that must claim a touch mid-gesture still needs the touch to reach its element. Each event type's listener is passive unless a subscriber cancels it (the gesture host's `touchend` and `contextmenu` while a claiming recognizer or press tracker is attached, the page hold's `touchmove` while it holds, and the click guard's `click` while it is armed, and from the menu press model's first arm on), so a page of pressables registers no listener that can hold a scroll. (#8360)
@vjeux
diff --git a/.changeset/input-stream.md b/.changeset/input-stream.md
index a55f98ee0c..ffb68af856 100644
--- a/.changeset/input-stream.md
+++ b/.changeset/input-stream.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Touch press feedback now hears scrolls and page hides on the window's capture phase, where its pointer listeners already were. Under an app's window-capture `stopPropagation`, or a document-capture `stopImmediatePropagation` registered before Core, a finger's pressed look now ends when the content under it scrolls, and every pressed look ends when the page is hidden.
+[fix] Touch press feedback now hears scrolls and page hides on the window's capture phase, where its pointer listeners already were. Under an app's window-capture `stopPropagation`, or a document-capture `stopImmediatePropagation` registered before Core, a finger's pressed look now ends when the content under it scrolls, and every pressed look ends when the page is hidden. (#8360)
@vjeux
diff --git a/.changeset/interaction-overlay-styles-xstyle-type.md b/.changeset/interaction-overlay-styles-xstyle-type.md
index b1b3e21f29..e380364725 100644
--- a/.changeset/interaction-overlay-styles-xstyle-type.md
+++ b/.changeset/interaction-overlay-styles-xstyle-type.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] TypeScript users applying `interactionOverlayStyles` through an Astryx component's `xstyle` no longer get a type error. The touch-press properties of each variant (`animationName`, `animationDuration`, `animationTimingFunction`, `animationFillMode`, and the colour variants' `backgroundImage`) now carry their CSS value types instead of `unknown`. The generated CSS is unchanged.
+[fix] TypeScript users applying `interactionOverlayStyles` through an Astryx component's `xstyle` no longer get a type error. The touch-press properties of each variant (`animationName`, `animationDuration`, `animationTimingFunction`, `animationFillMode`, and the colour variants' `backgroundImage`) now carry their CSS value types instead of `unknown`. The generated CSS is unchanged. (#9440)
@cixzhang
diff --git a/.changeset/inv23-dead-duplicate-private-selectors.md b/.changeset/inv23-dead-duplicate-private-selectors.md
index 16ebbbbeb3..dcc22f3501 100644
--- a/.changeset/inv23-dead-duplicate-private-selectors.md
+++ b/.changeset/inv23-dead-duplicate-private-selectors.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: ChatLayout drops a scrollbar style rule whose condition nothing ever set, and Popover, Table and the press feedback controller each read an internal marker through one shared name instead of a second hand-typed copy. No visible or behavioral change.
+[chore] Internal: ChatLayout drops a scrollbar style rule whose condition nothing ever set, and Popover, Table and the press feedback controller each read an internal marker through one shared name instead of a second hand-typed copy. No visible or behavioral change. (#9256)
@cixzhang
diff --git a/.changeset/item-swipe-entry-focusable-disabled.md b/.changeset/item-swipe-entry-focusable-disabled.md
index 0b7644404f..7210e62a41 100644
--- a/.changeset/item-swipe-entry-focusable-disabled.md
+++ b/.changeset/item-swipe-entry-focusable-disabled.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled swipe action on an `Item` row now stays focusable while the row is swiped open. Before, it rendered a `<button>` with the native `disabled` attribute, so Tab skipped it and a keyboard or screen-reader user could not reach it to learn it exists. Now it exposes `aria-disabled="true"` and keeps its Tab stop, while a click, Enter or Space still runs no `onActivate`, leaves the row open, and does not reach the row's own `onClick` (`spec:AST-085` FR1, FR2). No API changes.
+[fix] A disabled swipe action on an `Item` row now stays focusable while the row is swiped open. Before, it rendered a `<button>` with the native `disabled` attribute, so Tab skipped it and a keyboard or screen-reader user could not reach it to learn it exists. Now it exposes `aria-disabled="true"` and keeps its Tab stop, while a click, Enter or Space still runs no `onActivate`, leaves the row open, and does not reach the row's own `onClick` (`spec:AST-085` FR1, FR2). No API changes. (#9211)
@parinith-web
diff --git a/.changeset/keyboard-hint-portaled-focus.md b/.changeset/keyboard-hint-portaled-focus.md
index 95f953a23c..41142690b5 100644
--- a/.changeset/keyboard-hint-portaled-focus.md
+++ b/.changeset/keyboard-hint-portaled-focus.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] The arrow-key hint of TabList, Toolbar and SegmentedControl no longer appears, or gets used up, when focus lands in content a tab or toolbar button opens through a portal, such as a sheet, dialog or popover. It still shows the first time keyboard focus enters the row itself.
+[fix] The arrow-key hint of TabList, Toolbar and SegmentedControl no longer appears, or gets used up, when focus lands in content a tab or toolbar button opens through a portal, such as a sheet, dialog or popover. It still shows the first time keyboard focus enters the row itself. (#9362)
@duytbp
diff --git a/.changeset/layer-anchor-move-read-next-frame.md b/.changeset/layer-anchor-move-read-next-frame.md
index 9f8f3f10da..07ae375a7e 100644
--- a/.changeset/layer-anchor-move-read-next-frame.md
+++ b/.changeset/layer-anchor-move-read-next-frame.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A tall tooltip, or any layer that keeps clear of its trigger, no longer covers the trigger for an extra frame when the page scrolls on a busy device. The layer re-checks its place in the frame after the scroll, before that frame paints, so the trigger stays visible from the second frame on.
+[fix] A tall tooltip, or any layer that keeps clear of its trigger, no longer covers the trigger for an extra frame when the page scrolls on a busy device. The layer re-checks its place in the frame after the scroll, before that frame paints, so the trigger stays visible from the second frame on. (#9123)
@cixzhang
diff --git a/.changeset/layer-browser-hide-ledger.md b/.changeset/layer-browser-hide-ledger.md
index 34315ce316..9e0ba813d0 100644
--- a/.changeset/layer-browser-hide-ledger.md
+++ b/.changeset/layer-browser-hide-ledger.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] useLayer: a show that a browser-run popover hide refuses (Chromium 156 throws an `InvalidStateError`) is replayed once that hide has ended, so the layer ends shown. For example, when the browser's own Escape closes a light-dismissible layer, the tooltip on the button that opened it now shows instead of failing.
+[fix] useLayer: a show that a browser-run popover hide refuses (Chromium 156 throws an `InvalidStateError`) is replayed once that hide has ended, so the layer ends shown. For example, when the browser's own Escape closes a light-dismissible layer, the tooltip on the button that opened it now shows instead of failing. (#8543)
@vjeux
diff --git a/.changeset/layer-click-boundary.md b/.changeset/layer-click-boundary.md
index f485d10746..4b537c21c4 100644
--- a/.changeset/layer-click-boundary.md
+++ b/.changeset/layer-click-boundary.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] A press inside an open layer (a popover, tooltip, hover card, menu, dialog, drawer, lightbox, mobile navigation, bottom sheet or toast) no longer runs click, pointer, mouse or touch handlers on the elements around where the layer is written. Before, a click inside a menu written inside a clickable card or row could also activate that card or row. Handlers inside the layer, capture-phase handlers, and document and window listeners still receive the press. A handler that needs presses inside a layer belongs on the layer's content.
+[fix] A press inside an open layer (a popover, tooltip, hover card, menu, dialog, drawer, lightbox, mobile navigation, bottom sheet or toast) no longer runs click, pointer, mouse or touch handlers on the elements around where the layer is written. Before, a click inside a menu written inside a clickable card or row could also activate that card or row. Handlers inside the layer, capture-phase handlers, and document and window listeners still receive the press. A handler that needs presses inside a layer belongs on the layer's content. (#9497)
`SelectableCard`: a click inside an open layer within the card (such as a popover's content) no longer toggles it. Until the next minor, the caller's `onClick` still receives that click, now during the capture phase, so before the layer's own handlers.
diff --git a/.changeset/layer-remove-surface-guards.md b/.changeset/layer-remove-surface-guards.md
index b48db54438..5a2a812f8f 100644
--- a/.changeset/layer-remove-surface-guards.md
+++ b/.changeset/layer-remove-surface-guards.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Item, Token and ChatComposer no longer run their own check for presses inside an open Tooltip or HoverCard; the layer root already keeps those presses from them. No behavior changes.
+[chore] Item, Token and ChatComposer no longer run their own check for presses inside an open Tooltip or HoverCard; the layer root already keeps those presses from them. No behavior changes. (#9531)
@cixzhang
diff --git a/.changeset/link-maxlines-truncates.md b/.changeset/link-maxlines-truncates.md
index 488571ccf7..dbb8ed089c 100644
--- a/.changeset/link-maxlines-truncates.md
+++ b/.changeset/link-maxlines-truncates.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Link: `maxLines` now truncates when the link sits in a line narrower than its text. The link, as an anchor or a button, stops at its container and its label draws an ellipsis, instead of growing to its whole text and being clipped with no ellipsis.
+[fix] Link: `maxLines` now truncates when the link sits in a line narrower than its text. The link, as an anchor or a button, stops at its container and its label draws an ellipsis, instead of growing to its whole text and being clipped with no ellipsis. (#9059)
@cixzhang
diff --git a/.changeset/link-reflected-data-color.md b/.changeset/link-reflected-data-color.md
index 08c509a881..1e24df986a 100644
--- a/.changeset/link-reflected-data-color.md
+++ b/.changeset/link-reflected-data-color.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A caller's `data-color` no longer replaces the one `Link` reflects for theme targeting (`architecture:public-component-api` INV5, `Link` FR11). Before, caller props were spread after the theme attributes, so passing `data-color` changed what theme rules saw on the root even though the real `color` prop was unchanged. This holds for the anchor, button and disabled forms. Other caller `data-*` attributes still reach the root.
+[fix] A caller's `data-color` no longer replaces the one `Link` reflects for theme targeting (`architecture:public-component-api` INV5, `Link` FR11). Before, caller props were spread after the theme attributes, so passing `data-color` changed what theme rules saw on the root even though the real `color` prop was unchanged. This holds for the anchor, button and disabled forms. Other caller `data-*` attributes still reach the root. (#9157)
@parinith-web
diff --git a/.changeset/long-press-one-source.md b/.changeset/long-press-one-source.md
index c32640d83c..d03ce72b9b 100644
--- a/.changeset/long-press-one-source.md
+++ b/.changeset/long-press-one-source.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: `useLongPress` takes its default duration and tolerance, 500ms and 10px on either axis, from the same source as the long-press gesture recognizer, so ContextMenu's long press behaves as before. A finger held on a DropdownMenu trigger passes its own 13px allowance instead (see the trigger drift fix).
+[chore] Internal: `useLongPress` takes its default duration and tolerance, 500ms and 10px on either axis, from the same source as the long-press gesture recognizer, so ContextMenu's long press behaves as before. A finger held on a DropdownMenu trigger passes its own 13px allowance instead (see the trigger drift fix). (#8360)
@vjeux
diff --git a/.changeset/menu-sheet-preload-result.md b/.changeset/menu-sheet-preload-result.md
index 05cd015f6e..278930f7cb 100644
--- a/.changeset/menu-sheet-preload-result.md
+++ b/.changeset/menu-sheet-preload-result.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] A bottom-sheet DropdownMenu's internal sheet preload reports a failed load in its result, with the loader's error, instead of catching it with an empty handler. Nothing changes for callers: a failed preload still raises no unhandled rejection, and the next open loads the sheet's actions.
+[chore] A bottom-sheet DropdownMenu's internal sheet preload reports a failed load in its result, with the loader's error, instead of catching it with an empty handler. Nothing changes for callers: a failed preload still raises no unhandled rejection, and the next open loads the sheet's actions. (#9069)
@vjeux
diff --git a/.changeset/menu-trigger-drift.md b/.changeset/menu-trigger-drift.md
index 98ca1acc90..63cb2d5d36 100644
--- a/.changeset/menu-trigger-drift.md
+++ b/.changeset/menu-trigger-drift.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A finger held on a DropdownMenu trigger may drift up to 13px on each axis and still open the menu under every primary pointer, a phone's, a tablet's and a touchscreen laptop's alike, as AST-094 FR29 allows; it cancelled past 10px. No menu, row or trigger reads the pointer query.
+[fix] A finger held on a DropdownMenu trigger may drift up to 13px on each axis and still open the menu under every primary pointer, a phone's, a tablet's and a touchscreen laptop's alike, as AST-094 FR29 allows; it cancelled past 10px. No menu, row or trigger reads the pointer query. (#8360)
@vjeux
diff --git a/.changeset/mobile-tokenizer-keyboard-recovery.md b/.changeset/mobile-tokenizer-keyboard-recovery.md
index d697f7c1c5..4a9933e8e0 100644
--- a/.changeset/mobile-tokenizer-keyboard-recovery.md
+++ b/.changeset/mobile-tokenizer-keyboard-recovery.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Restore a Tall BottomSheet's internal position after keyboard dismissal.
+[chore] Restore a Tall BottomSheet's internal position after keyboard dismissal. (#8742)
@rubyycheung
diff --git a/.changeset/mobilenav-header-grows.md b/.changeset/mobilenav-header-grows.md
index 5ca28efe63..c07e10475c 100644
--- a/.changeset/mobilenav-header-grows.md
+++ b/.changeset/mobilenav-header-grows.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `MobileNav`'s header row grows with its content. It was a fixed one-bar height, so a header taller than one row (a title with a search field under it, or a title that wraps at a larger text size) overflowed the row: the bottom border ran through it and the content ran into the first navigation item. The row is now at least one bar high, so a one-line header looks as before. `SideNav` in drawer mode, which passes its `header` to `MobileNav`, gets the same fix.
+[fix] `MobileNav`'s header row grows with its content. It was a fixed one-bar height, so a header taller than one row (a title with a search field under it, or a title that wraps at a larger text size) overflowed the row: the bottom border ran through it and the content ran into the first navigation item. The row is now at least one bar high, so a one-line header looks as before. `SideNav` in drawer mode, which passes its `header` to `MobileNav`, gets the same fix. (#8865)
@cixzhang
diff --git a/.changeset/modal-announce-shared-observer.md b/.changeset/modal-announce-shared-observer.md
index 8b2091c5ef..69b8b79418 100644
--- a/.changeset/modal-announce-shared-observer.md
+++ b/.changeset/modal-announce-shared-observer.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the announcement routing inside open modals watches each dialog's `open`, `inert` and `aria-hidden` through Core's shared MutationObserver, so any number of open modals use one observer instead of one each. Routing is unchanged.
+[chore] Internal: the announcement routing inside open modals watches each dialog's `open`, `inert` and `aria-hidden` through Core's shared MutationObserver, so any number of open modals use one observer instead of one each. Routing is unchanged. (#9151)
@imdreamrunner
diff --git a/.changeset/modality-one-call.md b/.changeset/modality-one-call.md
index ac3238ffbb..deb8d83a32 100644
--- a/.changeset/modality-one-call.md
+++ b/.changeset/modality-one-call.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Components rendered into a same-origin iframe or a Document Picture-in-Picture window now read the last input in their own document for their keyboard focus rings and keyboard highlights (Slider, MultiSelector, DropdownMenu, ChatComposer, CommandPalette, panel search fields, menus), and for the ring on focus they move themselves. On the page, behavior is unchanged. Where an overlay returns focus on close is unchanged. vjeux wrote the original per-document fix, for Dialog (#8381); this extends it to every reader.
+[fix] Components rendered into a same-origin iframe or a Document Picture-in-Picture window now read the last input in their own document for their keyboard focus rings and keyboard highlights (Slider, MultiSelector, DropdownMenu, ChatComposer, CommandPalette, panel search fields, menus), and for the ring on focus they move themselves. On the page, behavior is unchanged. Where an overlay returns focus on close is unchanged. vjeux wrote the original per-document fix, for Dialog (#8381); this extends it to every reader. (#9148)
@cixzhang
diff --git a/.changeset/month-scroller-explicit-listeners.md b/.changeset/month-scroller-explicit-listeners.md
index 580c022efe..3bacf16e32 100644
--- a/.changeset/month-scroller-explicit-listeners.md
+++ b/.changeset/month-scroller-explicit-listeners.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] The date picker's month scroller attaches and removes its four input listeners directly, each with one shared options object, instead of looping over an array of event names and creating an options object on every attach. Behavior is unchanged. The scroller and its listeners come from @vjeux's month scroller fix.
+[chore] The date picker's month scroller attaches and removes its four input listeners directly, each with one shared options object, instead of looping over an array of event names and creating an options object on every attach. Behavior is unchanged. The scroller and its listeners come from @vjeux's month scroller fix. (#9146)
@cixzhang @vjeux
diff --git a/.changeset/month-scroller-late-step.md b/.changeset/month-scroller-late-step.md
index 548a4bfa6c..d7365fe450 100644
--- a/.changeset/month-scroller-late-step.md
+++ b/.changeset/month-scroller-late-step.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] In the DateInput and DateTimeInput bottom-sheet calendars, a month arrow clicked or tapped as the previous arrow's scroll is ending now brings the calendar to the month its title names in Safari, instead of back to the previous arrow's month.
+[fix] In the DateInput and DateTimeInput bottom-sheet calendars, a month arrow clicked or tapped as the previous arrow's scroll is ending now brings the calendar to the month its title names in Safari, instead of back to the previous arrow's month. (#8513)
@vjeux
diff --git a/.changeset/month-scroller-stalled-frame.md b/.changeset/month-scroller-stalled-frame.md
index af67c54092..5932f45bd8 100644
--- a/.changeset/month-scroller-stalled-frame.md
+++ b/.changeset/month-scroller-stalled-frame.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] In the DateInput and DateTimeInput bottom-sheet calendars, a month arrow no longer sets the calendar paging on by itself in Safari when the page stalls for a moment right after the tap; the calendar moves one month and stays there.
+[fix] In the DateInput and DateTimeInput bottom-sheet calendars, a month arrow no longer sets the calendar paging on by itself in Safari when the page stalls for a moment right after the tap; the calendar moves one month and stays there. (#8513)
@vjeux
diff --git a/.changeset/motion-doc-reduced-motion-touch.md b/.changeset/motion-doc-reduced-motion-touch.md
index 33fdcd586e..55b7fcfa5c 100644
--- a/.changeset/motion-doc-reduced-motion-touch.md
+++ b/.changeset/motion-doc-reduced-motion-touch.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[fix] The motion guide now says that under Reduce Motion, components cross-fade under a finger and change at once under a mouse, and that a value changing in place, such as a progress fill, takes its new value at once under any pointer (design:reduced-motion DR1–DR3).
+[fix] The motion guide now says that under Reduce Motion, components cross-fade under a finger and change at once under a mouse, and that a value changing in place, such as a progress fill, takes its new value at once under any pointer (design:reduced-motion DR1–DR3). (#8615)
@cixzhang
diff --git a/.changeset/motion-roles-docs-followup.md b/.changeset/motion-roles-docs-followup.md
index d6da78855c..6d4e764fbb 100644
--- a/.changeset/motion-roles-docs-followup.md
+++ b/.changeset/motion-roles-docs-followup.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the motion roles test's header and the motion README's files table name the internal motion roles, exactly the ones `spec:AST-094` FR4 lists. Documentation only; no behavior change.
+[chore] Internal: the motion roles test's header and the motion README's files table name the internal motion roles, exactly the ones `spec:AST-094` FR4 lists. Documentation only; no behavior change. (#8502)
@vjeux
diff --git a/.changeset/multiselector-count-i18n.md b/.changeset/multiselector-count-i18n.md
index 5fe0dcc7a2..e8b2b69811 100644
--- a/.changeset/multiselector-count-i18n.md
+++ b/.changeset/multiselector-count-i18n.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] MultiSelector: the default count text on the trigger (`triggerDisplay="count"`, for example "2 selected") now comes from the message catalog (`@astryx.multiSelector.selectedCount`), so it is translated and can use plural forms under any locale. `formatValue` still replaces it.
+[fix] MultiSelector: the default count text on the trigger (`triggerDisplay="count"`, for example "2 selected") now comes from the message catalog (`@astryx.multiSelector.selectedCount`), so it is translated and can use plural forms under any locale. `formatValue` still replaces it. (#9020)
@cixzhang
diff --git a/.changeset/multiselector-prettier-format.md b/.changeset/multiselector-prettier-format.md
index 4430be1219..8c8e777e22 100644
--- a/.changeset/multiselector-prettier-format.md
+++ b/.changeset/multiselector-prettier-format.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] MultiSelector's source is formatted with the repository's Prettier settings. No behavior changes.
+[chore] MultiSelector's source is formatted with the repository's Prettier settings. No behavior changes. (#9247)
@cixzhang
diff --git a/.changeset/nav-heading-menu-arrow-once.md b/.changeset/nav-heading-menu-arrow-once.md
index 482a11cfa2..39a226c14b 100644
--- a/.changeset/nav-heading-menu-arrow-once.md
+++ b/.changeset/nav-heading-menu-arrow-once.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] In a SideNavHeading or TopNavHeading menu built with NavHeadingMenu, one ArrowDown or ArrowUp now moves focus one item. It used to move two, skipping every other item, and in a two-item menu ArrowDown never moved focus.
+[fix] In a SideNavHeading or TopNavHeading menu built with NavHeadingMenu, one ArrowDown or ArrowUp now moves focus one item. It used to move two, skipping every other item, and in a two-item menu ArrowDown never moved focus. (#9019)
@cixzhang
diff --git a/.changeset/neat-trees-judge.md b/.changeset/neat-trees-judge.md
index 8f351e9c5e..028e54ae7f 100644
--- a/.changeset/neat-trees-judge.md
+++ b/.changeset/neat-trees-judge.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] Fix FileInput to prevent file picker activation and file selection while busy. Clear drag-over highlighting when disabled or busy, and expose the busy trigger as disabled to assistive technologies.
+[fix] Fix FileInput to prevent file picker activation and file selection while busy. Clear drag-over highlighting when disabled or busy, and expose the busy trigger as disabled to assistive technologies. (#9167)
@korkt-kim
diff --git a/.changeset/numberinput-focus-reselect-in-handler.md b/.changeset/numberinput-focus-reselect-in-handler.md
index e3a3672dcd..7575798818 100644
--- a/.changeset/numberinput-focus-reselect-in-handler.md
+++ b/.changeset/numberinput-focus-reselect-in-handler.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: when Tab moves focus into a NumberInput with `formatValue`, the focus handler itself puts the editable text in the input and selects it, instead of a layout effect that waited for the next render. Behavior is unchanged: typing still replaces the whole number.
+[chore] Internal: when Tab moves focus into a NumberInput with `formatValue`, the focus handler itself puts the editable text in the input and selects it, instead of a layout effect that waited for the next render. Behavior is unchanged: typing still replaces the whole number. (#9150)
@HelloOjasMutreja
diff --git a/.changeset/numberinput-tab-keeps-select-all.md b/.changeset/numberinput-tab-keeps-select-all.md
index 88ff33eb57..a6ec51570d 100644
--- a/.changeset/numberinput-tab-keeps-select-all.md
+++ b/.changeset/numberinput-tab-keeps-select-all.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] NumberInput: with `formatValue`, tabbing into the field keeps its text selected, so typing replaces the value. Before, the editable text replaced the formatted text after focus and collapsed Tab's selection to the end, so with `1,500,000` shown, Tab then `7` gave `15000007` and committed it on blur. Now `1,500,000` becomes a fully selected `1500000` and `7` replaces it. A click still places the caret where it landed. Fields without `formatValue` are unchanged. No API changes.
+[fix] NumberInput: with `formatValue`, tabbing into the field keeps its text selected, so typing replaces the value. Before, the editable text replaced the formatted text after focus and collapsed Tab's selection to the end, so with `1,500,000` shown, Tab then `7` gave `15000007` and committed it on blur. Now `1,500,000` becomes a fully selected `1500000` and `7` replaces it. A click still places the caret where it landed. Fields without `formatValue` are unchanged. No API changes. (#9033)
@HelloOjasMutreja
diff --git a/.changeset/outline-focus-follows-link.md b/.changeset/outline-focus-follows-link.md
index 4c4a20dcf5..013ff48b78 100644
--- a/.changeset/outline-focus-follows-link.md
+++ b/.changeset/outline-focus-follows-link.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Following an `Outline` link moves focus to the chosen section, as a native in-page link moves the focus starting point, so the next Tab continues from that section instead of jumping back to the top of the page. The section is focused without scrolling, so Outline's own scroll is unchanged (WCAG 2.2 SC 2.4.3 Focus Order).
+[fix] Following an `Outline` link moves focus to the chosen section, as a native in-page link moves the focus starting point, so the next Tab continues from that section instead of jumping back to the top of the page. The section is focused without scrolling, so Outline's own scroll is unchanged (WCAG 2.2 SC 2.4.3 Focus Order). (#9045)
@cixzhang @duytbp
diff --git a/.changeset/overlay-cancel-target.md b/.changeset/overlay-cancel-target.md
index 6e0bd2203f..ea3c7abb00 100644
--- a/.changeset/overlay-cancel-target.md
+++ b/.changeset/overlay-cancel-target.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Dismissing a file picker (Escape, or Cancel in the chooser) inside a `Drawer`, `MobileNav` or `Lightbox` no longer closes it and loses what was in it. Only a close request fired at the surface itself closes it, as `Dialog` and `BottomSheet` already do.
+[fix] Dismissing a file picker (Escape, or Cancel in the chooser) inside a `Drawer`, `MobileNav` or `Lightbox` no longer closes it and loses what was in it. Only a close request fired at the surface itself closes it, as `Dialog` and `BottomSheet` already do. (#8855)
@cixzhang
diff --git a/.changeset/overlays-open-on-server-render-closed.md b/.changeset/overlays-open-on-server-render-closed.md
index 17a7c81f64..ee9c26fa05 100644
--- a/.changeset/overlays-open-on-server-render-closed.md
+++ b/.changeset/overlays-open-on-server-render-closed.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A `Dialog`, `Drawer` or `BottomSheet` that is open on the server now renders closed until hydration, and opens right after it where it rests, with no entry motion, as anything present on page load does; its later opens and closes animate as before. Before, it painted open over a live page with `aria-modal="true"` but no modal state: the page under it stayed interactive, a sheet's invisible host could swallow clicks, and assistive technology was told a modality that didn't exist (WCAG 2.2 SC 4.1.2). A `BottomSheetSwitcher` whose active sheet is set on the server is covered too. Client-rendered overlays are unchanged.
+[fix] A `Dialog`, `Drawer` or `BottomSheet` that is open on the server now renders closed until hydration, and opens right after it where it rests, with no entry motion, as anything present on page load does; its later opens and closes animate as before. Before, it painted open over a live page with `aria-modal="true"` but no modal state: the page under it stayed interactive, a sheet's invisible host could swallow clicks, and assistive technology was told a modality that didn't exist (WCAG 2.2 SC 4.1.2). A `BottomSheetSwitcher` whose active sheet is set on the server is covered too. Client-rendered overlays are unchanged. (#9360)
@cixzhang @duytbp
diff --git a/.changeset/plain-date-format-reuses-formatters.md b/.changeset/plain-date-format-reuses-formatters.md
index 238d7346d3..acfe21906c 100644
--- a/.changeset/plain-date-format-reuses-formatters.md
+++ b/.changeset/plain-date-format-reuses-formatters.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[perf] Calendar, DateInput and the other date components now reuse one date formatter per locale and format instead of building one for every label they show, so rendering a month (42 day labels) no longer builds 42 formatters.
+[perf] Calendar, DateInput and the other date components now reuse one date formatter per locale and format instead of building one for every label they show, so rendering a month (42 day labels) no longer builds 42 formatters. (#8335)
@vjeux
diff --git a/.changeset/presentation-resolver.md b/.changeset/presentation-resolver.md
index 21e19a3382..46e7d00088 100644
--- a/.changeset/presentation-resolver.md
+++ b/.changeset/presentation-resolver.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] An internal `usePresentation` / `readPresentation` resolves a component's `presentation` prop into the surface to render and whether its touch input modes apply, keeping an omitted value distinct from an explicit `'popover'` so a caller's choice always wins over a touch default. Not exported from the package entry point.
+[chore] An internal `usePresentation` / `readPresentation` resolves a component's `presentation` prop into the surface to render and whether its touch input modes apply, keeping an omitted value distinct from an explicit `'popover'` so a caller's choice always wins over a touch default. Not exported from the package entry point. (#8298)
@vjeux
diff --git a/.changeset/presented-hit-testing.md b/.changeset/presented-hit-testing.md
index e27c857277..bc8561332c 100644
--- a/.changeset/presented-hit-testing.md
+++ b/.changeset/presented-hit-testing.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] On iOS, a touch on an element the compositor animator is moving reaches what is drawn: the animator reports each moving element's offset from its layout box, and the gesture host sends the touch, press bounds and the tap's click there instead of to the layout position iOS WebKit hit-tests.
+[chore] On iOS, a touch on an element the compositor animator is moving reaches what is drawn: the animator reports each moving element's offset from its layout box, and the gesture host sends the touch, press bounds and the tap's click there instead of to the layout position iOS WebKit hit-tests. (#8360)
@vjeux
diff --git a/.changeset/progress-bar-compositor-fill.md b/.changeset/progress-bar-compositor-fill.md
index 9313d2b6d6..ddbc5df754 100644
--- a/.changeset/progress-bar-compositor-fill.md
+++ b/.changeset/progress-bar-compositor-fill.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A determinate ProgressBar keeps moving to its new value while a script runs. The fill animated its `width`, which lays out and repaints on the main thread every frame, so a value change stalled for as long as the page ran JavaScript and then jumped. The fill now spans the track and slides into place with a transform that the browser animates on its compositor, in Chromium and in Safari, laying out and painting nothing per frame. Under reduced motion a new value now lands at once, on every pointer. Otherwise duration, easing, colors, marks and right-to-left drawing are unchanged (the fill mirrors with the bar's own direction, so a bar in a left-to-right region of a right-to-left page still fills from the left); the track now clips its fill to the rounded rail in both modes, so below about one track height of fill the leading end follows the track's curve instead of drawing a narrower full-height capsule, and a runtime change of the bar's direction slides the fill across to the other side instead of jumping there.
+[fix] A determinate ProgressBar keeps moving to its new value while a script runs. The fill animated its `width`, which lays out and repaints on the main thread every frame, so a value change stalled for as long as the page ran JavaScript and then jumped. The fill now spans the track and slides into place with a transform that the browser animates on its compositor, in Chromium and in Safari, laying out and painting nothing per frame. Under reduced motion a new value now lands at once, on every pointer. Otherwise duration, easing, colors, marks and right-to-left drawing are unchanged (the fill mirrors with the bar's own direction, so a bar in a left-to-right region of a right-to-left page still fills from the left); the track now clips its fill to the rounded rail in both modes, so below about one track height of fill the leading end follows the track's curve instead of drawing a narrower full-height capsule, and a runtime change of the bar's direction slides the fill across to the other side instead of jumping there. (#8196)
@vjeux
diff --git a/.changeset/radio-list-item-disabled-onclick.md b/.changeset/radio-list-item-disabled-onclick.md
index 21cad60214..0eef2fde97 100644
--- a/.changeset/radio-list-item-disabled-onclick.md
+++ b/.changeset/radio-list-item-disabled-onclick.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled `RadioListItem` no longer runs a caller's `onClick` (`spec:AST-085` FR2). Before, a radio in a group disabled with a `disabledMessage` stays focusable through `aria-disabled` rather than native `disabled`, so the browser did not silence it and the handler still ran on a click on the radio, on Space, and on an arrow key onto it. It still refused to select. An enabled radio is unchanged: its `onClick` still runs.
+[fix] A disabled `RadioListItem` no longer runs a caller's `onClick` (`spec:AST-085` FR2). Before, a radio in a group disabled with a `disabledMessage` stays focusable through `aria-disabled` rather than native `disabled`, so the browser did not silence it and the handler still ran on a click on the radio, on Space, and on an arrow key onto it. It still refused to select. An enabled radio is unchanged: its `onClick` still runs. (#9120)
@parinith-web
diff --git a/.changeset/radiolist-disabled-reason-describes-each-radio.md b/.changeset/radiolist-disabled-reason-describes-each-radio.md
index 3ce810deed..94dcba7a05 100644
--- a/.changeset/radiolist-disabled-reason-describes-each-radio.md
+++ b/.changeset/radiolist-disabled-reason-describes-each-radio.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] RadioList: a group disabled with a `disabledMessage` gives that reason to each radio as its description (`aria-describedby`), as well as to the radio group, so a screen reader announces it on the focused radio. A radio's own description comes first.
+[fix] RadioList: a group disabled with a `disabledMessage` gives that reason to each radio as its description (`aria-describedby`), as well as to the radio group, so a screen reader announces it on the focused radio. A radio's own description comes first. (#9169)
@vjeux
diff --git a/.changeset/reduced-motion-record.md b/.changeset/reduced-motion-record.md
index bd4884f719..4a3a1cf83c 100644
--- a/.changeset/reduced-motion-record.md
+++ b/.changeset/reduced-motion-record.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: under Reduce Motion, a call that names the opacity a waiting dip returns to, with no travel, joins that dip instead of fading the element out a second time, and `reducedMotionFade()` resolves the cross-fade's curve as a registered motion role where it plays. Not exported from the package entry point.
+[chore] Internal: under Reduce Motion, a call that names the opacity a waiting dip returns to, with no travel, joins that dip instead of fading the element out a second time, and `reducedMotionFade()` resolves the cross-fade's curve as a registered motion role where it plays. Not exported from the package entry point. (#8076)
@vjeux
diff --git a/.changeset/release-v075-codemod-merge-back.md b/.changeset/release-v075-codemod-merge-back.md
new file mode 100644
index 0000000000..640f63243f
--- /dev/null
+++ b/.changeset/release-v075-codemod-merge-back.md
@@ -0,0 +1,7 @@
+---
+'@astryxdesign/cli': patch
+---
+
+[chore] Preserved the v0.7.5 upgrade codemod registry when the release outputs returned to main (#9086), so the v0.7.6 CLI continues to offer that migration.
+
+@cixzhang
diff --git a/.changeset/release-v076-current-contract-records.md b/.changeset/release-v076-current-contract-records.md
new file mode 100644
index 0000000000..c70234b9c5
--- /dev/null
+++ b/.changeset/release-v076-current-contract-records.md
@@ -0,0 +1,9 @@
+---
+'@astryxdesign/core': patch
+---
+
+[docs] Recorded the component contract updates completed in this release.
+
+Covered records: #8783, #8822, #8878, #9050, #9058, #9062, #9081, #9083, #9090, #9096, #9100, #9101, #9103, #9105, #9108, #9111, #9112, #9113, #9117, #9118, #9124, #9125, #9127, #9128, #9129, #9131, #9132, #9133, #9135, #9158, #9175.
+
+@cixzhang
diff --git a/.changeset/required-native-invalid.md b/.changeset/required-native-invalid.md
index bd27777dfc..b2655ee3f3 100644
--- a/.changeset/required-native-invalid.md
+++ b/.changeset/required-native-invalid.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] RadioList and Switch: a required field no longer reads as "invalid entry" to screen readers before the user has answered. Each required radio and a required switch take their invalid state from `status`.
+[fix] RadioList and Switch: a required field no longer reads as "invalid entry" to screen readers before the user has answered. Each required radio and a required switch take their invalid state from `status`. (#9042)
@cixzhang
diff --git a/.changeset/resizable-model-module.md b/.changeset/resizable-model-module.md
index 2a4a3e494c..c5932f99fe 100644
--- a/.changeset/resizable-model-module.md
+++ b/.changeset/resizable-model-module.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] `useResizable`'s size parsing, bound resolution, clamping and snapping, saved-size storage and content-box measurement move unchanged into one internal module, so the factory that follows resolves, clamps, snaps and saves exactly as the hook does. No behavior changes.
+[chore] `useResizable`'s size parsing, bound resolution, clamping and snapping, saved-size storage and content-box measurement move unchanged into one internal module, so the factory that follows resolves, clamps, snaps and saves exactly as the hook does. No behavior changes. (#9197)
@vjeux
diff --git a/.changeset/resizable-save-once-per-drag.md b/.changeset/resizable-save-once-per-drag.md
index 5a3fbdb36b..d1d5f5991a 100644
--- a/.changeset/resizable-save-once-per-drag.md
+++ b/.changeset/resizable-save-once-per-drag.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[perf] `useResizable` with `autoSaveId` (and `SideNav` with `resizable={{autoSaveId}}`) now saves a dragged size to `localStorage` once, when the drag ends, instead of on every pointer move. Every write reached each other open tab of the site as a `storage` event, so one drag sent dozens of them. The storage key, the stored format and the size saved at the end are unchanged, and keyboard steps, `resize()`, `collapse()` and `expand()` still save at once.
+[perf] `useResizable` with `autoSaveId` (and `SideNav` with `resizable={{autoSaveId}}`) now saves a dragged size to `localStorage` once, when the drag ends, instead of on every pointer move. Every write reached each other open tab of the site as a `storage` event, so one drag sent dozens of them. The storage key, the stored format and the size saved at the end are unchanged, and keyboard steps, `resize()`, `collapse()` and `expand()` still save at once. (#7782)
@vjeux
diff --git a/.changeset/resizable-window-reads-once.md b/.changeset/resizable-window-reads-once.md
index 6e0289b4a2..ec5ecb59ab 100644
--- a/.changeset/resizable-window-reads-once.md
+++ b/.changeset/resizable-window-reads-once.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `useResizable` (and every component that uses it, such as `SideNav`) no longer reads the window size again after each render it commits. That read forced a layout of the whole page inside every commit, so a tab switch under an `AppShell` with a `SideNav` paid for it on slow devices. The window is still read during render, and every size, bound and reported maximum is unchanged.
+[fix] `useResizable` (and every component that uses it, such as `SideNav`) no longer reads the window size again after each render it commits. That read forced a layout of the whole page inside every commit, so a tab switch under an `AppShell` with a `SideNav` paid for it on slow devices. The window is still read during render, and every size, bound and reported maximum is unchanged. (#8857)
@cixzhang
diff --git a/.changeset/resize-handle-names-node-header.md b/.changeset/resize-handle-names-node-header.md
index 5a76c48ed3..b75cf3d9e2 100644
--- a/.changeset/resize-handle-names-node-header.md
+++ b/.changeset/resize-handle-names-node-header.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A `Table` column-resize handle is named by its column's visible text when the header is a node, such as `<span>Amount (EUR)</span>`, instead of by the column key. The key remains the fallback only for a header with no text.
+[fix] A `Table` column-resize handle is named by its column's visible text when the header is a node, such as `<span>Amount (EUR)</span>`, instead of by the column key. The key remains the fallback only for a header with no text. (#9057)
@cixzhang @duytbp
diff --git a/.changeset/richtext-slots-render-nothing.md b/.changeset/richtext-slots-render-nothing.md
index 94ea4e636b..66e52a2ec7 100644
--- a/.changeset/richtext-slots-render-nothing.md
+++ b/.changeset/richtext-slots-render-nothing.md
@@ -2,6 +2,6 @@
'@astryxdesign/richtext': patch
---
-[fix] RichTextEditor's `toolbar` now treats `''` as empty, as it already treated `null`, `undefined` and booleans, so `toolbar=""` no longer adds the toolbar's top border to the editing surface. RichTextEditorToolbar's `endContent` treats `''`, `false` and `true` as empty, so it no longer adds a trailing separator. `0` still counts as content and shows "0".
+[fix] RichTextEditor's `toolbar` now treats `''` as empty, as it already treated `null`, `undefined` and booleans, so `toolbar=""` no longer adds the toolbar's top border to the editing surface. RichTextEditorToolbar's `endContent` treats `''`, `false` and `true` as empty, so it no longer adds a trailing separator. `0` still counts as content and shows "0". (#9265)
@ernestt @potatowagon
diff --git a/.changeset/richtext-status-placement-tooltip.md b/.changeset/richtext-status-placement-tooltip.md
index d3d757a647..670b1c8cd6 100644
--- a/.changeset/richtext-status-placement-tooltip.md
+++ b/.changeset/richtext-status-placement-tooltip.md
@@ -2,6 +2,6 @@
'@astryxdesign/richtext': patch
---
-[chore] RichTextEditor: `statusVariant` names `'tooltip'` in its own type, so it keeps accepting `statusVariant="tooltip"` after FieldStatus drops its deprecated `tooltip` variant in the next minor release. No behavior change.
+[chore] RichTextEditor: `statusVariant` names `'tooltip'` in its own type, so it keeps accepting `statusVariant="tooltip"` after FieldStatus drops its deprecated `tooltip` variant in the next minor release. No behavior change. (#9196)
@cixzhang
diff --git a/.changeset/scroll-overflow-follows-content.md b/.changeset/scroll-overflow-follows-content.md
index 7ad175e627..3cdce3765f 100644
--- a/.changeset/scroll-overflow-follows-content.md
+++ b/.changeset/scroll-overflow-follows-content.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `useScrollOverflow` measures again when the container's content changes with the container keeping its size: a child added, removed or resized, or a new gap or padding. Carousel's scroll area, a tab stop only while its content overflows, and its edge buttons and fades follow slides added or removed and a slide that grows; TabList's fades follow its tabs the same way.
+[fix] `useScrollOverflow` measures again when the container's content changes with the container keeping its size: a child added, removed or resized, or a new gap or padding. Carousel's scroll area, a tab stop only while its content overflows, and its edge buttons and fades follow slides added or removed and a slide that grows; TabList's fades follow its tabs the same way. (#8155)
@vjeux
diff --git a/.changeset/segmented-control-disabled-reason-on-segment.md b/.changeset/segmented-control-disabled-reason-on-segment.md
index 8a27f0e46c..4fd130fb78 100644
--- a/.changeset/segmented-control-disabled-reason-on-segment.md
+++ b/.changeset/segmented-control-disabled-reason-on-segment.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] SegmentedControl: a control disabled with a `disabledMessage` gives that reason to each segment as its description (`aria-describedby`), as well as to the group, so a screen reader announces it on the segment that has focus. The control also always keeps one Tab stop: the selected segment, even when it is itself disabled, else the first segment not disabled on its own, else the first.
+[fix] SegmentedControl: a control disabled with a `disabledMessage` gives that reason to each segment as its description (`aria-describedby`), as well as to the group, so a screen reader announces it on the segment that has focus. The control also always keeps one Tab stop: the selected segment, even when it is itself disabled, else the first segment not disabled on its own, else the first. (#9176)
@cixzhang
diff --git a/.changeset/segmented-control-disabled-tab-stop.md b/.changeset/segmented-control-disabled-tab-stop.md
index aa65d81f32..ccf3227898 100644
--- a/.changeset/segmented-control-disabled-tab-stop.md
+++ b/.changeset/segmented-control-disabled-tab-stop.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] SegmentedControl: a disabled control, or a disabled selected segment, keeps the control's Tab stop. Before, a control disabled without a `disabledMessage` had no Tab stop and ignored the pointer. A selected segment that was itself disabled lost the stop to another segment, and once the stop had moved there, selecting a third segment left it behind, so Tab re-entered on an unchecked segment. Now the selected segment always holds the one Tab stop, announced as disabled (`aria-disabled`) when it is, and nothing can be selected while disabled.
+[fix] SegmentedControl: a disabled control, or a disabled selected segment, keeps the control's Tab stop. Before, a control disabled without a `disabledMessage` had no Tab stop and ignored the pointer. A selected segment that was itself disabled lost the stop to another segment, and once the stop had moved there, selecting a third segment left it behind, so Tab re-entered on an unchecked segment. Now the selected segment always holds the one Tab stop, announced as disabled (`aria-disabled`) when it is, and nothing can be selected while disabled. (#9314)
@cixzhang
diff --git a/.changeset/segmented-control-item-disabled-onclick.md b/.changeset/segmented-control-item-disabled-onclick.md
index a70f07cb3d..7d4390bedb 100644
--- a/.changeset/segmented-control-item-disabled-onclick.md
+++ b/.changeset/segmented-control-item-disabled-onclick.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled `SegmentedControlItem` no longer runs a caller's `onClick` (`spec:AST-085` FR2). Before, the segment refused to select but still called the handler on a click, and on Enter or Space for the selected segment of a group disabled with a reason, which stays focusable. This covers a segment disabled by its own `isDisabled` and one disabled by its group. An enabled segment is unchanged: its `onClick` still runs first and can still cancel selection with `preventDefault()`.
+[fix] A disabled `SegmentedControlItem` no longer runs a caller's `onClick` (`spec:AST-085` FR2). Before, the segment refused to select but still called the handler on a click, and on Enter or Space for the selected segment of a group disabled with a reason, which stays focusable. This covers a segment disabled by its own `isDisabled` and one disabled by its group. An enabled segment is unchanged: its `onClick` still runs first and can still cancel selection with `preventDefault()`. (#8989)
@parinith-web
diff --git a/.changeset/selector-light-dismiss-focus.md b/.changeset/selector-light-dismiss-focus.md
index d37bfaa451..56ce697762 100644
--- a/.changeset/selector-light-dismiss-focus.md
+++ b/.changeset/selector-light-dismiss-focus.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Selector, MultiSelector: pressing another field while the list is open now leaves focus in that field. Before, the list's close handler moved focus back to the Selector's trigger, so the next key went to the closed Selector (a letter could change its value through type-to-select). Escape, picking an option, or a press on nothing focusable still return focus to the trigger, and a MultiSelector with `renderTrigger` still returns focus to the caller's control on every close.
+[fix] Selector, MultiSelector: pressing another field while the list is open now leaves focus in that field. Before, the list's close handler moved focus back to the Selector's trigger, so the next key went to the closed Selector (a letter could change its value through type-to-select). Escape, picking an option, or a press on nothing focusable still return focus to the trigger, and a MultiSelector with `renderTrigger` still returns focus to the caller's control on every close. (#9018)
@cixzhang
diff --git a/.changeset/side-nav-item-focusable-disabled.md b/.changeset/side-nav-item-focusable-disabled.md
index 63c1d7e1a4..a5dcde73bc 100644
--- a/.changeset/side-nav-item-focusable-disabled.md
+++ b/.changeset/side-nav-item-focusable-disabled.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled `SideNavItem` stays focusable. Before, it rendered a `<button>` with the native `disabled` attribute, so Tab skipped it and keyboard and screen-reader users could not reach it, and an item that became disabled while focused dropped focus to the page. Now it exposes `aria-disabled="true"` and keeps its Tab stop, while a click, Enter or Space still runs no `onClick`, does not navigate, and does not close the mobile drawer. In a collapsed rail, a disabled item's label tooltip now opens when Tab focuses it and describes the focusable control rather than its row. This meets the focusable-disabled requirement in spec:AST-085 (FR1, FR2, FR4, FR5). No API changes.
+[fix] A disabled `SideNavItem` stays focusable. Before, it rendered a `<button>` with the native `disabled` attribute, so Tab skipped it and keyboard and screen-reader users could not reach it, and an item that became disabled while focused dropped focus to the page. Now it exposes `aria-disabled="true"` and keeps its Tab stop, while a click, Enter or Space still runs no `onClick`, does not navigate, and does not close the mobile drawer. In a collapsed rail, a disabled item's label tooltip now opens when Tab focuses it and describes the focusable control rather than its row. This meets the focusable-disabled requirement in spec:AST-085 (FR1, FR2, FR4, FR5). No API changes. (#9102)
@kyu-rong
diff --git a/.changeset/sidenav-collapse-keeps-focus.md b/.changeset/sidenav-collapse-keeps-focus.md
index 6100689241..dc209a8b0b 100644
--- a/.changeset/sidenav-collapse-keeps-focus.md
+++ b/.changeset/sidenav-collapse-keeps-focus.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] When a collapsible `SideNav` collapses and takes the keyboard focus with it, focus now moves instead of falling to the page, where a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). From a row the collapsed rail does not render, such as an item without an icon, focus moves to the collapse toggle, or, with no toggle in the SideNav, to the nearest row still in the rail. On a row the rail keeps, focus stays on that row, and a header or footer control the collapse keeps or re-renders under the same name keeps it. From a header or footer control the collapse removes or replaces under another name, or the resize handle of a `resizable` SideNav, focus moves to the collapse toggle, or, with none, to the first row. Focus the collapse does not take is not moved.
+[fix] When a collapsible `SideNav` collapses and takes the keyboard focus with it, focus now moves instead of falling to the page, where a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). From a row the collapsed rail does not render, such as an item without an icon, focus moves to the collapse toggle, or, with no toggle in the SideNav, to the nearest row still in the rail. On a row the rail keeps, focus stays on that row, and a header or footer control the collapse keeps or re-renders under the same name keeps it. From a header or footer control the collapse removes or replaces under another name, or the resize handle of a `resizable` SideNav, focus moves to the collapse toggle, or, with none, to the first row. Focus the collapse does not take is not moved. (#9249)
@cixzhang @duytbp
diff --git a/.changeset/sidenav-resizable-keeps-items-mounted.md b/.changeset/sidenav-resizable-keeps-items-mounted.md
index b533bb0d07..fbfc8d7e15 100644
--- a/.changeset/sidenav-resizable-keeps-items-mounted.md
+++ b/.changeset/sidenav-resizable-keeps-items-mounted.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A `resizable` `SideNav` keeps its nav and items mounted when it collapses or expands, as a plain one does. Before, every collapse remounted them, so an open nested group closed and item state reset.
+[fix] A `resizable` `SideNav` keeps its nav and items mounted when it collapses or expands, as a plain one does. Before, every collapse remounted them, so an open nested group closed and item state reset. (#9290)
@cixzhang @duytbp
diff --git a/.changeset/sidenav-slot-presence.md b/.changeset/sidenav-slot-presence.md
index af5f9ebf16..97f87e72cc 100644
--- a/.changeset/sidenav-slot-presence.md
+++ b/.changeset/sidenav-slot-presence.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] SideNav (`footerIcons`, `topContent`), SideNavHeading (`icon`, `headerEndContent`), SideNavItem (`endContent`) and SideNavSection (`endContent`): a slot whose value is `0` showed a stray "0" beside its slot, or nothing at all. Now each slot follows the shared presence check. Empty values (`null`, `false`, `''`) render no slot, as an omitted one does. `0` renders inside its slot as content, including a collapsed rail's icon-only heading and the footer and top areas around it.
+[fix] SideNav (`footerIcons`, `topContent`), SideNavHeading (`icon`, `headerEndContent`), SideNavItem (`endContent`) and SideNavSection (`endContent`): a slot whose value is `0` showed a stray "0" beside its slot, or nothing at all. Now each slot follows the shared presence check. Empty values (`null`, `false`, `''`) render no slot, as an omitted one does. `0` renders inside its slot as content, including a collapsed rail's icon-only heading and the footer and top areas around it. (#9498)
@cixzhang
diff --git a/.changeset/slider-coincident-press-focus.md b/.changeset/slider-coincident-press-focus.md
index 577af5eed0..88448dcf7b 100644
--- a/.changeset/slider-coincident-press-focus.md
+++ b/.changeset/slider-coincident-press-focus.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Slider: a press on the mark label of two coincident thumbs' shared value now goes to the upper thumb, as a press on the thumbs does, so a press that never moves leaves focus on the same thumb wherever it lands. Before, a press on that label went to the lower thumb, which the upper one covers.
+[fix] Slider: a press on the mark label of two coincident thumbs' shared value now goes to the upper thumb, as a press on the thumbs does, so a press that never moves leaves focus on the same thumb wherever it lands. Before, a press on that label went to the lower thumb, which the upper one covers. (#9184)
@vjeux
diff --git a/.changeset/slider-coincident-range-thumbs.md b/.changeset/slider-coincident-range-thumbs.md
index 09177f2242..56e602eba8 100644
--- a/.changeset/slider-coincident-range-thumbs.md
+++ b/.changeset/slider-coincident-range-thumbs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Slider: a range slider whose two thumbs sit on the same value can be dragged apart again. Only one of the two thumbs can travel toward where the pointer goes: a press on the track beside them picks the thumb on its side, and a press on the thumbs themselves waits for the pointer to move, so the direction of that first movement picks the thumb, which takes the drag's focus, pressed paint and value tooltip. Such a drag always follows the pointer: once the pointer passes the other thumb, the dragged thumb stops against it and the other one takes the drag, so a first step that drifts the wrong way never sticks it. Before, two thumbs at the maximum could not be dragged down, and a press on the track above two coincident thumbs moved neither.
+[fix] Slider: a range slider whose two thumbs sit on the same value can be dragged apart again. Only one of the two thumbs can travel toward where the pointer goes: a press on the track beside them picks the thumb on its side, and a press on the thumbs themselves waits for the pointer to move, so the direction of that first movement picks the thumb, which takes the drag's focus, pressed paint and value tooltip. Such a drag always follows the pointer: once the pointer passes the other thumb, the dragged thumb stops against it and the other one takes the drag, so a first step that drifts the wrong way never sticks it. Before, two thumbs at the maximum could not be dragged down, and a press on the track above two coincident thumbs moved neither. (#8151)
@vjeux
diff --git a/.changeset/slider-thumb-names-i18n.md b/.changeset/slider-thumb-names-i18n.md
index 7e1936dfcd..b5044b3424 100644
--- a/.changeset/slider-thumb-names-i18n.md
+++ b/.changeset/slider-thumb-names-i18n.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Slider: a range slider's thumb names ("Minimum value" and "Maximum value", announced to screen readers) now come from the message catalog (`@astryx.slider.minimumThumb`, `@astryx.slider.maximumThumb`), so they follow the app's locale.
+[fix] Slider: a range slider's thumb names ("Minimum value" and "Maximum value", announced to screen readers) now come from the message catalog (`@astryx.slider.minimumThumb`, `@astryx.slider.maximumThumb`), so they follow the app's locale. (#9023)
@cixzhang
diff --git a/.changeset/slim-published-package-artifacts.md b/.changeset/slim-published-package-artifacts.md
index f1c93548dc..7eca58057a 100644
--- a/.changeset/slim-published-package-artifacts.md
+++ b/.changeset/slim-published-package-artifacts.md
@@ -12,6 +12,6 @@
'@astryxdesign/theme-y2k': patch
---
-[fix] Published packages no longer include repository test and benchmark files, reducing install size without changing exports.
+[fix] Published packages no longer include repository test and benchmark files, reducing install size without changing exports. (#9153)
@parinith-web
diff --git a/.changeset/slots-render-nothing-a-m.md b/.changeset/slots-render-nothing-a-m.md
index 5b3d24b5de..6142756c0e 100644
--- a/.changeset/slots-render-nothing-a-m.md
+++ b/.changeset/slots-render-nothing-a-m.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] More slots treat `''`, `false` and `true` as empty, the way React renders them, instead of drawing an empty wrapper: ChatSystemMessage's `icon`, Item's `startContent`, `endContent` and `description` (so a ListItem or menu row gains no blank lane), and MetadataList's `title` and MetadataListItem's `icon`. `0` still counts as content and shows "0".
+[fix] More slots treat `''`, `false` and `true` as empty, the way React renders them, instead of drawing an empty wrapper: ChatSystemMessage's `icon`, Item's `startContent`, `endContent` and `description` (so a ListItem or menu row gains no blank lane), and MetadataList's `title` and MetadataListItem's `icon`. `0` still counts as content and shows "0". (#9204)
@czarandy
diff --git a/.changeset/slots-render-nothing-consistently.md b/.changeset/slots-render-nothing-consistently.md
index 21c5aeacee..58994f1157 100644
--- a/.changeset/slots-render-nothing-consistently.md
+++ b/.changeset/slots-render-nothing-consistently.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `DropdownMenuGroup`'s `title` and `Badge`'s `label` now use the shared `isRenderable` check, so `null`, `undefined`, `true`, `false` and `''` count as rendering nothing, and `0` still counts as content. A `DropdownMenuGroup` with `title={true}` no longer renders an empty heading that names the group. `Badge` is unchanged (thanks @vjeux, #8236). Other slots are unchanged.
+[fix] `DropdownMenuGroup`'s `title` and `Badge`'s `label` now use the shared `isRenderable` check, so `null`, `undefined`, `true`, `false` and `''` count as rendering nothing, and `0` still counts as content. A `DropdownMenuGroup` with `title={true}` no longer renders an empty heading that names the group. `Badge` is unchanged (thanks @vjeux, #8236). Other slots are unchanged. (#9160)
@cixzhang @duytbp
diff --git a/.changeset/slots-render-nothing-n-z.md b/.changeset/slots-render-nothing-n-z.md
index e294451d6b..da8b97939d 100644
--- a/.changeset/slots-render-nothing-n-z.md
+++ b/.changeset/slots-render-nothing-n-z.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] More slots treat `''`, `false` and `true` as empty, the way React renders them, instead of drawing an empty wrapper: TreeList's `header` (a header that renders nothing no longer names the tree, so it keeps its `aria-label`), TreeList items' `startContent` and `endContent`, TopNavMegaMenu's `items` and `featured`, Table header `after` content, and OverflowList's measured overflow indicator. `0` still counts as content and shows "0".
+[fix] More slots treat `''`, `false` and `true` as empty, the way React renders them, instead of drawing an empty wrapper: TreeList's `header` (a header that renders nothing no longer names the tree, so it keeps its `aria-label`), TreeList items' `startContent` and `endContent`, TopNavMegaMenu's `items` and `featured`, Table header `after` content, and OverflowList's measured overflow indicator. `0` still counts as content and shows "0". (#9206)
@czarandy @humbertovirtudes @rubyycheung
diff --git a/.changeset/smaller-component-english-fallback.md b/.changeset/smaller-component-english-fallback.md
index 7d6da72cee..eb324868bd 100644
--- a/.changeset/smaller-component-english-fallback.md
+++ b/.changeset/smaller-component-english-fallback.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Many components that show built-in text are smaller. Each one now carries only the English for its own strings instead of every Core string, so a component such as Button loads about 7 KB less (gzip) and a new string elsewhere in Core no longer makes it bigger. Table (and Markdown, which renders it), Chat, PowerSearch, CommandPalette and the date and time inputs still carry every Core string for now. Nothing you see changes: every built-in string still shows the same English, translations and overrides resolve as before, and `useTranslator`, `InternationalizationContext` and `@astryxdesign/core/locales/en.generated.js` still reach every Astryx string.
+[fix] Many components that show built-in text are smaller. Each one now carries only the English for its own strings instead of every Core string, so a component such as Button loads about 7 KB less (gzip) and a new string elsewhere in Core no longer makes it bigger. Table (and Markdown, which renders it), Chat, PowerSearch, CommandPalette and the date and time inputs still carry every Core string for now. Nothing you see changes: every built-in string still shows the same English, translations and overrides resolve as before, and `useTranslator`, `InternationalizationContext` and `@astryxdesign/core/locales/en.generated.js` still reach every Astryx string. (#9429)
@cixzhang
diff --git a/.changeset/smaller-english-fallback-remaining.md b/.changeset/smaller-english-fallback-remaining.md
index 07d73b1ece..e7a72c0cf5 100644
--- a/.changeset/smaller-english-fallback-remaining.md
+++ b/.changeset/smaller-english-fallback-remaining.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Table, Markdown, Chat, CommandPalette and the date and time inputs are smaller too. Each now carries only the English for its own strings instead of every Core string, about 7 KB less (gzip) each. PowerSearch still carries every Core string, because a custom operator's `i18nKey` can name any Astryx key. Nothing you see changes: every built-in string shows the same English, and translations and overrides resolve as before.
+[fix] Table, Markdown, Chat, CommandPalette and the date and time inputs are smaller too. Each now carries only the English for its own strings instead of every Core string, about 7 KB less (gzip) each. PowerSearch still carries every Core string, because a custom operator's `i18nKey` can name any Astryx key. Nothing you see changes: every built-in string shows the same English, and translations and overrides resolve as before. (#9452)
@cixzhang
diff --git a/.changeset/stack-doc-direction-styling-props.md b/.changeset/stack-doc-direction-styling-props.md
index e10087eec4..737294e59b 100644
--- a/.changeset/stack-doc-direction-styling-props.md
+++ b/.changeset/stack-doc-direction-styling-props.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Stack, VStack, and StackItem: say that a horizontal stack follows the writing direction (right to left in RTL), and document the `className`, `style`, and `ref` props, plus `xstyle` on VStack and StackItem.
+[docs] Stack, VStack, and StackItem: say that a horizontal stack follows the writing direction (right to left in RTL), and document the `className`, `style`, and `ref` props, plus `xstyle` on VStack and StackItem. (#9583)
@cixzhang
diff --git a/.changeset/start-icon-slot-presence.md b/.changeset/start-icon-slot-presence.md
index e810ce3e5a..e1364098b4 100644
--- a/.changeset/start-icon-slot-presence.md
+++ b/.changeset/start-icon-slot-presence.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] TextArea: a `startIcon` of `0` showed a stray "0" beside the start-icon slot, with no padding reserved for it. The slot and its padding now follow one presence check: empty values (`null`, `false`, `''`) render no slot, and `0` renders inside the slot like any other content. TextInput uses the same check, with no visible change.
+[fix] TextArea: a `startIcon` of `0` showed a stray "0" beside the start-icon slot, with no padding reserved for it. The slot and its padding now follow one presence check: empty values (`null`, `false`, `''`) render no slot, and `0` renders inside the slot like any other content. TextInput uses the same check, with no visible change. (#9443)
@cixzhang
diff --git a/.changeset/stepper-disabled-step-focusable.md b/.changeset/stepper-disabled-step-focusable.md
index 29548b6b22..c849e7b311 100644
--- a/.changeset/stepper-disabled-step-focusable.md
+++ b/.changeset/stepper-disabled-step-focusable.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] In a clickable `Stepper`, a disabled `Step` now keeps its button: it stays in the tab order, is announced as unavailable (`aria-disabled`), and keeps focus if it becomes disabled while focused, but still does not activate. Its description (the reason it is unavailable) describes the button (`spec:AST-085` FR1, FR4, FR5). Before, it rendered as plain text, so keyboard and screen-reader users could not find it or tell it was unavailable.
+[fix] In a clickable `Stepper`, a disabled `Step` now keeps its button: it stays in the tab order, is announced as unavailable (`aria-disabled`), and keeps focus if it becomes disabled while focused, but still does not activate. Its description (the reason it is unavailable) describes the button (`spec:AST-085` FR1, FR4, FR5). Before, it rendered as plain text, so keyboard and screen-reader users could not find it or tell it was unavailable. (#8867)
@cixzhang
diff --git a/.changeset/switch-disabled-key-handlers.md b/.changeset/switch-disabled-key-handlers.md
index 19b3e5454f..cd6e3db5fe 100644
--- a/.changeset/switch-disabled-key-handlers.md
+++ b/.changeset/switch-disabled-key-handlers.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled `Switch` no longer runs a caller's `onKeyDown` or `onKeyUp` (`spec:AST-085` FR2). Before, the switch stayed focusable through `aria-disabled` instead of native `disabled`, so a key pressed on it still reached those handlers, while its `onClick` was already withheld. It still refused to toggle. An enabled switch is unchanged: its key handlers still run.
+[fix] A disabled `Switch` no longer runs a caller's `onKeyDown` or `onKeyUp` (`spec:AST-085` FR2). Before, the switch stayed focusable through `aria-disabled` instead of native `disabled`, so a key pressed on it still reached those handlers, while its `onClick` was already withheld. It still refused to toggle. An enabled switch is unchanged: its key handlers still run. (#9122)
@parinith-web
diff --git a/.changeset/table-names-own-text.md b/.changeset/table-names-own-text.md
index 6c8c9c3262..fa9fdc33a7 100644
--- a/.changeset/table-names-own-text.md
+++ b/.changeset/table-names-own-text.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] `Table` names say what they belong to (WCAG 2.2 SC 4.1.2 and 2.4.6; the APG sortable table pattern under `spec:AST-020` FR15; `spec:AST-025` FR12).
+[fix] `Table` names say what they belong to (WCAG 2.2 SC 4.1.2 and 2.4.6; the APG sortable table pattern under `spec:AST-020` FR15; `spec:AST-025` FR12). (#9047)
- A sort button was named "Sort by Name", or "Sort by Name, sorted ascending" with "priority 2 of 3" in multi-sort, and that phrase replaced the column header's name. It is now named by its column's text, so the header keeps that name; the direction comes from the header's `aria-sort`, and while several columns sort, each button is described by its priority ("Priority 2 of 3").
- The scroll region was a group named "Table" on every table. It now takes the table's own name (its `aria-labelledby`, else its `aria-label`), and "Table" only for an unnamed table.
diff --git a/.changeset/table-resort-keeps-rows.md b/.changeset/table-resort-keeps-rows.md
index 6409e05293..40997bf422 100644
--- a/.changeset/table-resort-keeps-rows.md
+++ b/.changeset/table-resort-keeps-rows.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[perf] Table: when nothing in a table depends on a row's position, re-sorting it no longer re-renders every row; the rows only move. On a 1,000-row table this is about a tenth of the work a sort click does. This applies to a table that has an `idKey`, sets neither `rowCount` nor `rowIndexStart`, and uses neither `useTableRowIndex` nor a plugin that transforms body rows (selection, row expansion, grouped rows, tree data). Those tables still re-render their rows on a sort.
+[perf] Table: when nothing in a table depends on a row's position, re-sorting it no longer re-renders every row; the rows only move. On a 1,000-row table this is about a tenth of the work a sort click does. This applies to a table that has an `idKey`, sets neither `rowCount` nor `rowIndexStart`, and uses neither `useTableRowIndex` nor a plugin that transforms body rows (selection, row expansion, grouped rows, tree data). Those tables still re-render their rows on a sort. (#9234)
@cixzhang
diff --git a/.changeset/tablist-press-reveal-next-frame.md b/.changeset/tablist-press-reveal-next-frame.md
index 13e1807054..926c5b6f17 100644
--- a/.changeset/tablist-press-reveal-next-frame.md
+++ b/.changeset/tablist-press-reveal-next-frame.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] TabList: pressing or arrowing to a tab in a scrolling strip no longer measures the strip inside the press. Focusing the tab already scrolls it into view, so the check that keeps the selected tab whole now runs in the next frame instead of forcing the new selection's style and layout before the press can paint.
+[fix] TabList: pressing or arrowing to a tab in a scrolling strip no longer measures the strip inside the press. Focusing the tab already scrolls it into view, so the check that keeps the selected tab whole now runs in the next frame instead of forcing the new selection's style and layout before the press can paint. (#8856)
@cixzhang
diff --git a/.changeset/template-demo-content-placeholder.md b/.changeset/template-demo-content-placeholder.md
index baa0386343..1ccb759fea 100644
--- a/.changeset/template-demo-content-placeholder.md
+++ b/.changeset/template-demo-content-placeholder.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[feat] When a template imports Astryx's docs-only demo content, `astryx template <name> <path>`, `astryx template <name>`, `astryx template <name> --skeleton`, and `astryx component <Name> --showcase` replace each demo-content element with a marked `<Text>Card content</Text>` placeholder and remove the demo-content import, so the code they hand out never imports a module that only Astryx's own previews have. The placeholder uses the file's own Astryx `Text` import when that import is in scope, and otherwise imports `Text`, under an alias when the file already uses that name. `template.copy` and `template.show` gain `demoContentReplaced` (0 when the template carried none), their text output says how many elements became placeholders, and the `components` that `template.show` and `template.skeleton` list are the components of the returned source. No shipped template uses demo content yet, so every current template is copied, shown, and outlined exactly as before. The docsite's shadcn install of a block or page applies the same replacement and also replaces demo media, each with a marked placeholder: a placeholder image for an image and a `data:,placeholder-video-add-your-own` source for a video. The item's description says how many references and elements were replaced. The adjacent `.astryx/<item>.json` receipt keeps its current shape, so every released `astryx upgrade` still reads it.
+[feat] When a template imports Astryx's docs-only demo content, `astryx template <name> <path>`, `astryx template <name>`, `astryx template <name> --skeleton`, and `astryx component <Name> --showcase` replace each demo-content element with a marked `<Text>Card content</Text>` placeholder and remove the demo-content import, so the code they hand out never imports a module that only Astryx's own previews have. The placeholder uses the file's own Astryx `Text` import when that import is in scope, and otherwise imports `Text`, under an alias when the file already uses that name. `template.copy` and `template.show` gain `demoContentReplaced` (0 when the template carried none), their text output says how many elements became placeholders, and the `components` that `template.show` and `template.skeleton` list are the components of the returned source. No shipped template uses demo content yet, so every current template is copied, shown, and outlined exactly as before. The docsite's shadcn install of a block or page applies the same replacement and also replaces demo media, each with a marked placeholder: a placeholder image for an image and a `data:,placeholder-video-add-your-own` source for a video. The item's description says how many references and elements were replaced. The adjacent `.astryx/<item>.json` receipt keeps its current shape, so every released `astryx upgrade` still reads it. (#9430)
@cixzhang
diff --git a/.changeset/text-heading-long-tokens-wrap.md b/.changeset/text-heading-long-tokens-wrap.md
index 0167ca5449..8f52f1434f 100644
--- a/.changeset/text-heading-long-tokens-wrap.md
+++ b/.changeset/text-heading-long-tokens-wrap.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Text and Heading: a long unbroken word, URL or ID in text that isn't truncated now wraps instead of running past its container, so in ordinary flow a phone-width page (320 px) no longer scrolls sideways. Ordinary text lays out exactly as before, and truncation (`maxLines`) is unchanged. Inside a flex row, the flex child still needs `min-width: 0`. Text and Heading now set `overflow-wrap` themselves, so a container you style with `overflow-wrap: anywhere` no longer reaches their text; Astryx's own containers (CommandPaletteEmpty, Toast, FieldStatus, Banner) pass their `anywhere` wrap through.
+[fix] Text and Heading: a long unbroken word, URL or ID in text that isn't truncated now wraps instead of running past its container, so in ordinary flow a phone-width page (320 px) no longer scrolls sideways. Ordinary text lays out exactly as before, and truncation (`maxLines`) is unchanged. Inside a flex row, the flex child still needs `min-width: 0`. Text and Heading now set `overflow-wrap` themselves, so a container you style with `overflow-wrap: anywhere` no longer reaches their text; Astryx's own containers (CommandPaletteEmpty, Toast, FieldStatus, Banner) pass their `anywhere` wrap through. (#9351)
@cixzhang
diff --git a/.changeset/textarea-counter-i18n.md b/.changeset/textarea-counter-i18n.md
index a87875f0fc..996ad9f5b5 100644
--- a/.changeset/textarea-counter-i18n.md
+++ b/.changeset/textarea-counter-i18n.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] TextArea: the `maxLength` character counter now comes from one catalog message (`@astryx.textArea.counter`), so its numbers use the locale's number format and translators can change the order or separator. In English a limit of 1,000 or more now shows grouped digits (`62/2,000` instead of `62/2000`).
+[fix] TextArea: the `maxLength` character counter now comes from one catalog message (`@astryx.textArea.counter`), so its numbers use the locale's number format and translators can change the order or separator. In English a limit of 1,000 or more now shows grouped digits (`62/2,000` instead of `62/2000`). (#9025)
@cixzhang
diff --git a/.changeset/textinput-clear-stays-put.md b/.changeset/textinput-clear-stays-put.md
index 43d59ad54b..7ebf128c9b 100644
--- a/.changeset/textinput-clear-stays-put.md
+++ b/.changeset/textinput-clear-stays-put.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] TextInput: the clear button no longer shifts inward when the field turns busy. The busy Spinner now sits inward of the clear button, as in Typeahead and Tokenizer, so a user reaching for the button while a search runs does not miss it. No API changes.
+[fix] TextInput: the clear button no longer shifts inward when the field turns busy. The busy Spinner now sits inward of the clear button, as in Typeahead and Tokenizer, so a user reaching for the button while a search runs does not miss it. No API changes. (#9027)
@HelloOjasMutreja
diff --git a/.changeset/theme-motion-knobs.md b/.changeset/theme-motion-knobs.md
index bf4202c9f8..a8e2a64228 100644
--- a/.changeset/theme-motion-knobs.md
+++ b/.changeset/theme-motion-knobs.md
@@ -3,6 +3,6 @@
'@astryxdesign/cli': patch
---
-[feat] A theme's `motion` takes two knobs beside the duration scale: `tempo` (0.75–1.5) scales every motion duration, and `character` (`'crisp'`, `'standard'` or `'expressive'`) sets the new `--ease-entrance` and `--ease-move` tokens; `--ease-exit` stays the same at every character. Their types, `ThemeMotionConfig`, `ThemeMotionKnobs` and `MotionCharacter`, are exported. A theme without them renders exactly as before; a duration scale and explicit tokens win over the knobs, Spinner's and Skeleton's loops keep their timing under every tempo, and the press release fade follows tempo up to the 200 ms Reduce Motion cap under the person's setting. Springs don't read the knobs yet. The motion, token and theme-authoring docs and the theme template describe the knobs.
+[feat] A theme's `motion` takes two knobs beside the duration scale: `tempo` (0.75–1.5) scales every motion duration, and `character` (`'crisp'`, `'standard'` or `'expressive'`) sets the new `--ease-entrance` and `--ease-move` tokens; `--ease-exit` stays the same at every character. Their types, `ThemeMotionConfig`, `ThemeMotionKnobs` and `MotionCharacter`, are exported. A theme without them renders exactly as before; a duration scale and explicit tokens win over the knobs, Spinner's and Skeleton's loops keep their timing under every tempo, and the press release fade follows tempo up to the 200 ms Reduce Motion cap under the person's setting. Springs don't read the knobs yet. The motion, token and theme-authoring docs and the theme template describe the knobs. (#8661)
@vjeux
diff --git a/.changeset/tidy-progress-marks.md b/.changeset/tidy-progress-marks.md
index 7f4a87f068..348b29849f 100644
--- a/.changeset/tidy-progress-marks.md
+++ b/.changeset/tidy-progress-marks.md
@@ -2,5 +2,5 @@
'@astryxdesign/core': patch
---
-[fix] ProgressBar target marks expose their label as an accessible name before the tooltip loads, while keeping keyboard focus and hover/focus tooltips.
+[fix] ProgressBar target marks expose their label as an accessible name before the tooltip loads, while keeping keyboard focus and hover/focus tooltips. (#9276)
@korkt-kim
diff --git a/.changeset/time-input-locale-hour-cycle.md b/.changeset/time-input-locale-hour-cycle.md
index 3fa689257f..05ff6d9554 100644
--- a/.changeset/time-input-locale-hour-cycle.md
+++ b/.changeset/time-input-locale-hour-cycle.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] TimeInput, DateTimeInput: the `hourFormat` default follows the locale. This is a default change. The old default was always `'12h'`; the new default, when `hourFormat` is unset, is the `InternationalizationProvider` locale's hour cycle, so a `de-DE`, `en-GB`, or `vi-VN` app shows "14:30" like `Timestamp` beside it, while `en-US` and an app with no provider keep "2:30 PM". To keep the old default, pass `hourFormat="12h"`. To honor a person's own 12/24-hour preference everywhere, put it on the provider locale (`en-US-u-hc-h23`). Twelve-hour text now uses the locale's own day period ("오후 2:30", "午後2:30", "2:30 p. m.") instead of a fixed English AM/PM, along with its digits and separator, and the typed field reads that text back. Fixes #8992.
+[feat] TimeInput, DateTimeInput: the `hourFormat` default follows the locale. This is a default change. The old default was always `'12h'`; the new default, when `hourFormat` is unset, is the `InternationalizationProvider` locale's hour cycle, so a `de-DE`, `en-GB`, or `vi-VN` app shows "14:30" like `Timestamp` beside it, while `en-US` and an app with no provider keep "2:30 PM". To keep the old default, pass `hourFormat="12h"`. To honor a person's own 12/24-hour preference everywhere, put it on the provider locale (`en-US-u-hc-h23`). Twelve-hour text now uses the locale's own day period ("오후 2:30", "午後2:30", "2:30 p. m.") instead of a fixed English AM/PM, along with its digits and separator, and the typed field reads that text back. Fixes #8992. (#9022)
@nynexman4464
diff --git a/.changeset/timestamp-caller-name.md b/.changeset/timestamp-caller-name.md
index fa3d41875d..20d021c03f 100644
--- a/.changeset/timestamp-caller-name.md
+++ b/.changeset/timestamp-caller-name.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Timestamp keeps a caller's `aria-label` on relative output and a caller's `tabIndex` while its hover card is attached. Before, the full-date name and the card's tab stop overwrote them, so a timestamp named for its context (for example "Posted 5 minutes ago") lost that name, and one taken out of the tab order came back into it. Without a caller value, nothing changes.
+[fix] Timestamp keeps a caller's `aria-label` on relative output and a caller's `tabIndex` while its hover card is attached. Before, the full-date name and the card's tab stop overwrote them, so a timestamp named for its context (for example "Posted 5 minutes ago") lost that name, and one taken out of the tab order came back into it. Without a caller value, nothing changes. (#8726)
@cixzhang
diff --git a/.changeset/toast-fallback-viewport-nested-theme.md b/.changeset/toast-fallback-viewport-nested-theme.md
index da61131f85..27a2718357 100644
--- a/.changeset/toast-fallback-viewport-nested-theme.md
+++ b/.changeset/toast-fallback-viewport-nested-theme.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Toast: a `Theme` inside toast content shown by the fallback viewport (no `LayerProvider`) now themes only its own subtree. It no longer rewrites the page's `<html>` theme as if it were the app's root `Theme`. First fixed in #5617.
+[fix] Toast: a `Theme` inside toast content shown by the fallback viewport (no `LayerProvider`) now themes only its own subtree. It no longer rewrites the page's `<html>` theme as if it were the app's root `Theme`. First fixed in #5617. (#9253)
@cixzhang @AKnassa
diff --git a/.changeset/toast-leaving-past-cap.md b/.changeset/toast-leaving-past-cap.md
index 4caacd75f5..ac47d389f4 100644
--- a/.changeset/toast-leaving-past-cap.md
+++ b/.changeset/toast-leaving-past-cap.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A toast that is closing when a new toast takes its visible place under `maxVisible`, or that the same handler pushes out and then dismisses, leaves the stack at once. Before, it came back later as an invisible, empty row that kept the notifications landmark, took one of the visible places, and let F6 move focus to its hidden dismiss button. A second `collisionBehavior: 'ignore'` toast with the same `uniqueID`, raised in the same handler as the first, is now dropped unannounced, as it already was once the first had rendered. When a control inside a toast raises toasts and then dismisses its own toast, focus moves to a toast that shows, the new one included, instead of to the notifications region.
+[fix] A toast that is closing when a new toast takes its visible place under `maxVisible`, or that the same handler pushes out and then dismisses, leaves the stack at once. Before, it came back later as an invisible, empty row that kept the notifications landmark, took one of the visible places, and let F6 move focus to its hidden dismiss button. A second `collisionBehavior: 'ignore'` toast with the same `uniqueID`, raised in the same handler as the first, is now dropped unannounced, as it already was once the first had rendered. When a control inside a toast raises toasts and then dismisses its own toast, focus moves to a toast that shows, the new one included, instead of to the notifications region. (#8051)
@vjeux
diff --git a/.changeset/toast-pause-sources.md b/.changeset/toast-pause-sources.md
index 3ae8588737..ebecba608e 100644
--- a/.changeset/toast-pause-sources.md
+++ b/.changeset/toast-pause-sources.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Toast: a toast's auto-hide timer stays paused while any pause condition still holds. Before, the pointer leaving the card, focus leaving it, or the window regaining focus resumed the timer even if another condition was still active, so a toast could hide while focus was on its action or the pointer was over it. Focus moving between the toast's own controls also keeps it paused.
+[fix] Toast: a toast's auto-hide timer stays paused while any pause condition still holds. Before, the pointer leaving the card, focus leaving it, or the window regaining focus resumed the timer even if another condition was still active, so a toast could hide while focus was on its action or the pointer was over it. Focus moving between the toast's own controls also keeps it paused. (#9016)
@cixzhang
diff --git a/.changeset/toast-tab-focus-return.md b/.changeset/toast-tab-focus-return.md
index 56c7baaed1..e2055773a0 100644
--- a/.changeset/toast-tab-focus-return.md
+++ b/.changeset/toast-tab-focus-return.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Toast: dismissing the last toast after reaching it with Tab or a click returns focus to where it was before, instead of dropping it to the page.
+[fix] Toast: dismissing the last toast after reaching it with Tab or a click returns focus to where it was before, instead of dropping it to the page. (#9039)
@cixzhang
diff --git a/.changeset/toggle-button-reflected-pressed-state.md b/.changeset/toggle-button-reflected-pressed-state.md
index ac1bce26d5..adeb541ff2 100644
--- a/.changeset/toggle-button-reflected-pressed-state.md
+++ b/.changeset/toggle-button-reflected-pressed-state.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A caller's `aria-pressed` or `data-is-pressed` no longer replaces the pressed state `ToggleButton` reflects (`architecture:public-component-api` INV5, `ToggleButton` FR12). Before, caller props were spread last, so passing either attribute made assistive technology and theme rules see a state that did not match `isPressed`. `ToggleButton` now owns `aria-pressed` and the reflected `data-is-pressed` and `data-elevation`. Other caller `data-*` attributes still reach the root.
+[fix] A caller's `aria-pressed` or `data-is-pressed` no longer replaces the pressed state `ToggleButton` reflects (`architecture:public-component-api` INV5, `ToggleButton` FR12). Before, caller props were spread last, so passing either attribute made assistive technology and theme rules see a state that did not match `isPressed`. `ToggleButton` now owns `aria-pressed` and the reflected `data-is-pressed` and `data-elevation`. Other caller `data-*` attributes still reach the root. (#9159)
@parinith-web
diff --git a/.changeset/togglebuttongroup-host-props.md b/.changeset/togglebuttongroup-host-props.md
index 4678ea7134..5804416852 100644
--- a/.changeset/togglebuttongroup-host-props.md
+++ b/.changeset/togglebuttongroup-host-props.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `ToggleButtonGroup` accepts `className`, `style`, `id`, `aria-*`, `data-*` and event handlers, and passes them to its group element. The group keeps its own `role`, `aria-label` and theme target.
+[fix] `ToggleButtonGroup` accepts `className`, `style`, `id`, `aria-*`, `data-*` and event handlers, and passes them to its group element. The group keeps its own `role`, `aria-label` and theme target. (#9040)
@cixzhang @duytbp
diff --git a/.changeset/token-disabled-state.md b/.changeset/token-disabled-state.md
index 78d519e113..ca55f76dcf 100644
--- a/.changeset/token-disabled-state.md
+++ b/.changeset/token-disabled-state.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A disabled `Token` reflects its state on the `token` theme target (`data-disabled`) in every structure, so a theme can style it. A disabled link token keeps a focusable link announced as disabled (`aria-disabled="true"`, no `href`), instead of becoming plain text with no tab stop.
+[fix] A disabled `Token` reflects its state on the `token` theme target (`data-disabled`) in every structure, so a theme can style it. A disabled link token keeps a focusable link announced as disabled (`aria-disabled="true"`, no `href`), instead of becoming plain text with no tab stop. (#9037)
@cixzhang @duytbp
diff --git a/.changeset/token-link-onclick.md b/.changeset/token-link-onclick.md
index 57c5fc6d91..06458bc563 100644
--- a/.changeset/token-link-onclick.md
+++ b/.changeset/token-link-onclick.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A `Token` with an `href` now calls a caller's `onClick` (`architecture:public-component-api` INV5, `Token` FR3). Before, `onClick` was dropped whenever `href` made the token a link, so the handler never ran on a click. This covers the link token and the link token with a remove button, where a plain click on the token surface runs the handler once, a Cmd/Ctrl-click or middle click on the surface opens the link in a new tab without running it, and a click on the Remove button does not run it. Navigation is unchanged, and calling `preventDefault` in the handler still stops it.
+[fix] A `Token` with an `href` now calls a caller's `onClick` (`architecture:public-component-api` INV5, `Token` FR3). Before, `onClick` was dropped whenever `href` made the token a link, so the handler never ran on a click. This covers the link token and the link token with a remove button, where a plain click on the token surface runs the handler once, a Cmd/Ctrl-click or middle click on the surface opens the link in a new tab without running it, and a click on the Remove button does not run it. Navigation is unchanged, and calling `preventDefault` in the handler still stops it. (#9205)
@parinith-web
diff --git a/.changeset/tokenizer-clear-all-announced.md b/.changeset/tokenizer-clear-all-announced.md
index 3a6050a301..75449ed988 100644
--- a/.changeset/tokenizer-clear-all-announced.md
+++ b/.changeset/tokenizer-clear-all-announced.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] The inline `Tokenizer` Clear all button announces "All items removed", once, as the touch sheet does, so a screen reader user learns the selection was emptied. `PowerSearch`'s Clear all announces its own words, "All filters removed".
+[fix] The inline `Tokenizer` Clear all button announces "All items removed", once, as the touch sheet does, so a screen reader user learns the selection was emptied. `PowerSearch`'s Clear all announces its own words, "All filters removed". (#9038)
@cixzhang @duytbp
diff --git a/.changeset/tokenizer-create-row-i18n.md b/.changeset/tokenizer-create-row-i18n.md
index ba4fa29631..2184416409 100644
--- a/.changeset/tokenizer-create-row-i18n.md
+++ b/.changeset/tokenizer-create-row-i18n.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Tokenizer: the inline create row now takes its `Create "…"` label from the `@astryx.tokenizer.create` message, the same one the bottom sheet uses, so it follows the provider's locale instead of always reading in English. Fixes #8931.
+[fix] Tokenizer: the inline create row now takes its `Create "…"` label from the `@astryx.tokenizer.create` message, the same one the bottom sheet uses, so it follows the provider's locale instead of always reading in English. Fixes #8931. (#9029)
@nynexman4464
diff --git a/.changeset/tokenizer-focus-handoffs-in-refs.md b/.changeset/tokenizer-focus-handoffs-in-refs.md
index 72b9474d99..ae6ed6a82b 100644
--- a/.changeset/tokenizer-focus-handoffs-in-refs.md
+++ b/.changeset/tokenizer-focus-handoffs-in-refs.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] `Tokenizer` hands focus between its controls from callback refs and the Clear all confirmation's close handler, not from effects, as `architecture:react-component-runtime` INV2 and INV6 require. Where focus lands is unchanged. The presentation swap and the sheet are internal (not yet public). Thanks @imdreamrunner (#7977).
+[chore] `Tokenizer` hands focus between its controls from callback refs and the Clear all confirmation's close handler, not from effects, as `architecture:react-component-runtime` INV2 and INV6 require. Where focus lands is unchanged. The presentation swap and the sheet are internal (not yet public). Thanks @imdreamrunner (#7977). (#9162)
@cixzhang @duytbp
diff --git a/.changeset/toolbar-link-roving.md b/.changeset/toolbar-link-roving.md
index 2ddd79f896..ded9dd69f0 100644
--- a/.changeset/toolbar-link-roving.md
+++ b/.changeset/toolbar-link-roving.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A link in a Toolbar (such as a Button with `href`) now shares the toolbar's single tab stop. Arrow keys reach it like any other control, and it no longer adds a second Tab stop to the row.
+[fix] A link in a Toolbar (such as a Button with `href`) now shares the toolbar's single tab stop. Arrow keys reach it like any other control, and it no longer adds a second Tab stop to the row. (#8921)
@kyu-rong
diff --git a/.changeset/tooltip-auto-focus-when-focused.md b/.changeset/tooltip-auto-focus-when-focused.md
index 057dee7d10..eb6ae5d255 100644
--- a/.changeset/tooltip-auto-focus-when-focused.md
+++ b/.changeset/tooltip-auto-focus-when-focused.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Tooltip: under the default `focusTrigger="auto"`, keyboard focus opens the tooltip of a trigger that was out of the tab order when the tooltip attached. A Button or IconButton in a Toolbar or ButtonGroup whose `tooltip` was set after mount, or any roving-tabindex member rendered with `tabindex="-1"`, now shows its tooltip when the arrow keys reach it. Whether focus counts is decided when it arrives, so a focusable trigger the old check missed, such as a `<summary>`, opens too. Focus inside a trigger that is not focusable still does not open it.
+[fix] Tooltip: under the default `focusTrigger="auto"`, keyboard focus opens the tooltip of a trigger that was out of the tab order when the tooltip attached. A Button or IconButton in a Toolbar or ButtonGroup whose `tooltip` was set after mount, or any roving-tabindex member rendered with `tabindex="-1"`, now shows its tooltip when the arrow keys reach it. Whether focus counts is decided when it arrives, so a focusable trigger the old check missed, such as a `<summary>`, opens too. Focus inside a trigger that is not focusable still does not open it. (#9366)
@cixzhang
diff --git a/.changeset/tooltip-surface-press-stays.md b/.changeset/tooltip-surface-press-stays.md
index ff6740b93d..78169b10e5 100644
--- a/.changeset/tooltip-surface-press-stays.md
+++ b/.changeset/tooltip-surface-press-stays.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A click inside an open Tooltip or HoverCard no longer activates the card, row or field around its trigger: a FileInput no longer opens its file picker, and a ClickableCard, SelectableCard, Token, or Item, TreeList or Table row no longer activates. Links and buttons inside a HoverCard keep working.
+[fix] A click inside an open Tooltip or HoverCard no longer activates the card, row or field around its trigger: a FileInput no longer opens its file picker, and a ClickableCard, SelectableCard, Token, or Item, TreeList or Table row no longer activates. Links and buttons inside a HoverCard keep working. (#9252)
@cixzhang
diff --git a/.changeset/top-nav-drawer-trigger-ref.md b/.changeset/top-nav-drawer-trigger-ref.md
index 676de889a9..b614ff66c7 100644
--- a/.changeset/top-nav-drawer-trigger-ref.md
+++ b/.changeset/top-nav-drawer-trigger-ref.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `TopNavMenu` and `TopNavMegaMenu` now forward their `ref` to the trigger button in drawer mode (`architecture:public-component-api` INV8). Before, only the desktop popover trigger received the ref, so a caller's ref stayed empty whenever the menu rendered inside the mobile drawer. Apps need no code change; the desktop trigger and every other prop are unchanged.
+[fix] `TopNavMenu` and `TopNavMegaMenu` now forward their `ref` to the trigger button in drawer mode (`architecture:public-component-api` INV8). Before, only the desktop popover trigger received the ref, so a caller's ref stayed empty whenever the menu rendered inside the mobile drawer. Apps need no code change; the desktop trigger and every other prop are unchanged. (#8897)
@parinith-web
diff --git a/.changeset/topnav-featured-card-rtl-arrow.md b/.changeset/topnav-featured-card-rtl-arrow.md
index 0a0e8029ad..34d1335903 100644
--- a/.changeset/topnav-featured-card-rtl-arrow.md
+++ b/.changeset/topnav-featured-card-rtl-arrow.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] TopNavMegaMenuFeaturedCard: in right-to-left layouts the link arrow now points toward the inline end (left) instead of backwards. The link's text and accessible name are unchanged.
+[fix] TopNavMegaMenuFeaturedCard: in right-to-left layouts the link arrow now points toward the inline end (left) instead of backwards. The link's text and accessible name are unchanged. (#9317)
@cixzhang
diff --git a/.changeset/topnav-slot-presence.md b/.changeset/topnav-slot-presence.md
index 56d580603a..8ee20e137a 100644
--- a/.changeset/topnav-slot-presence.md
+++ b/.changeset/topnav-slot-presence.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] TopNav (`heading`, `startContent`, `endContent`), TopNavHeading (`logo`, `headerEndContent`), TopNavMegaMenuItem (`icon`), TopNavMenu drawer items' `icon` and NavHeadingMenuItem's `description`: a slot whose value is `0` showed a stray "0" beside its slot. Now each slot follows the shared presence check. Empty values (`null`, `false`, `''`) render no slot, as an omitted one does: an empty `centerContent` or `startContent` no longer switches the bar to its center layout, shows the mobile-bar menu toggle or opens an empty drawer section. `0` renders inside its slot as content.
+[fix] TopNav (`heading`, `startContent`, `endContent`), TopNavHeading (`logo`, `headerEndContent`), TopNavMegaMenuItem (`icon`), TopNavMenu drawer items' `icon` and NavHeadingMenuItem's `description`: a slot whose value is `0` showed a stray "0" beside its slot. Now each slot follows the shared presence check. Empty values (`null`, `false`, `''`) render no slot, as an omitted one does: an empty `centerContent` or `startContent` no longer switches the bar to its center layout, shows the mobile-bar menu toggle or opens an empty drawer section. `0` renders inside its slot as content. (#9500)
@cixzhang
diff --git a/.changeset/touch-selection-lock-gestures.md b/.changeset/touch-selection-lock-gestures.md
index d1f3ab7c2b..ea79ef78aa 100644
--- a/.changeset/touch-selection-lock-gestures.md
+++ b/.changeset/touch-selection-lock-gestures.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture host applies a recognizer's own `selectionLock` to that recognizer's contact and imports no lock itself; a long press brings one only when it has a hold (a `minimumPressDuration` above 0), and `selectionLock: null` opts out. Not exported from the package entry point.
+[chore] Internal: the gesture host applies a recognizer's own `selectionLock` to that recognizer's contact and imports no lock itself; a long press brings one only when it has a hold (a `minimumPressDuration` above 0), and `selectionLock: null` opts out. Not exported from the package entry point. (#8360)
@vjeux
diff --git a/.changeset/touch-selection-lock.md b/.changeset/touch-selection-lock.md
index e5285afc1f..54e62b5053 100644
--- a/.changeset/touch-selection-lock.md
+++ b/.changeset/touch-selection-lock.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Where the primary pointer is fine (a mouse, a trackpad, a touchscreen laptop, a desktop pen tablet), the press feedback controller no longer registers a touch listener: it reads the primary pointer at the first finger or pen press and keeps its `touchcancel` listener only while that pointer is coarse.
+[fix] Where the primary pointer is fine (a mouse, a trackpad, a touchscreen laptop, a desktop pen tablet), the press feedback controller no longer registers a touch listener: it reads the primary pointer at the first finger or pen press and keeps its `touchcancel` listener only while that pointer is coarse. (#8360)
@vjeux
diff --git a/.changeset/touch-style-keys.md b/.changeset/touch-style-keys.md
index 26e5754d78..ccf1ab52cf 100644
--- a/.changeset/touch-style-keys.md
+++ b/.changeset/touch-style-keys.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: core's touch style keys stay literal, and a test pins every one to the touch presentation resolver's constants (`touchKeys`, internal to core). An imported `defineConsts` key compiles to a different StyleX priority than the same literal. No public export and no style changes.
+[chore] Internal: core's touch style keys stay literal, and a test pins every one to the touch presentation resolver's constants (`touchKeys`, internal to core). An imported `defineConsts` key compiles to a different StyleX priority than the same literal. No public export and no style changes. (#8331)
@vjeux
diff --git a/.changeset/treelist-collapse-keeps-focus.md b/.changeset/treelist-collapse-keeps-focus.md
index 6a9199aa36..57c11346a7 100644
--- a/.changeset/treelist-collapse-keeps-focus.md
+++ b/.changeset/treelist-collapse-keeps-focus.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] When a `TreeList` row collapses while keyboard focus is inside its children, for example from an `items` change, focus moves to that row (the outermost one when nested rows collapse together), which then holds the tree's Tab stop unless it is disabled (a disabled row takes focus, and the stop goes to the tree's first enabled row if the collapse removed the row that held it). Before, the focused row disappeared and nothing held focus, so a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). Focus anywhere else is not moved.
+[fix] When a `TreeList` row collapses while keyboard focus is inside its children, for example from an `items` change, focus moves to that row (the outermost one when nested rows collapse together), which then holds the tree's Tab stop unless it is disabled (a disabled row takes focus, and the stop goes to the tree's first enabled row if the collapse removed the row that held it). Before, the focused row disappeared and nothing held focus, so a keyboard or screen-reader user lost their place (WCAG 2.2 SC 2.4.3). Focus anywhere else is not moved. (#9251)
@cixzhang @duytbp
diff --git a/.changeset/trigger-menu-busy-announcement.md b/.changeset/trigger-menu-busy-announcement.md
index 35a6472b7d..34366a8208 100644
--- a/.changeset/trigger-menu-busy-announcement.md
+++ b/.changeset/trigger-menu-busy-announcement.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] ChatComposerInput's trigger menu announces its "Searching…" row through Core's shared busy announcement, like other busy controls: once per search, not repeated while typing continues, and not at all when results arrive first. Inside a native modal dialog an app renders without Astryx, it is now heard inside that dialog.
+[fix] ChatComposerInput's trigger menu announces its "Searching…" row through Core's shared busy announcement, like other busy controls: once per search, not repeated while typing continues, and not at all when results arrive first. Inside a native modal dialog an app renders without Astryx, it is now heard inside that dialog. (#9154)
@HelloOjasMutreja
diff --git a/.changeset/truncation-measures-after-layout.md b/.changeset/truncation-measures-after-layout.md
index 85a9ea8676..1f97009700 100644
--- a/.changeset/truncation-measures-after-layout.md
+++ b/.changeset/truncation-measures-after-layout.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[perf] Pages that mount many truncated `Text` and `Heading` elements at once mount faster. Each one used to measure whether its text overflows while React was still committing the page, so every measurement forced its own style and layout pass; they now measure right after the commit, all of them together, so the page reads layout once. The ellipsis, the line clamp and the full-text tooltip are unchanged.
+[perf] Pages that mount many truncated `Text` and `Heading` elements at once mount faster. Each one used to measure whether its text overflows while React was still committing the page, so every measurement forced its own style and layout pass; they now measure right after the commit, all of them together, so the page reads layout once. The ellipsis, the line clamp and the full-text tooltip are unchanged. (#9013)
@cixzhang
diff --git a/.changeset/typeahead-arrowdown-replaced-source.md b/.changeset/typeahead-arrowdown-replaced-source.md
index 533674d1ec..a40aa07411 100644
--- a/.changeset/typeahead-arrowdown-replaced-source.md
+++ b/.changeset/typeahead-arrowdown-replaced-source.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `Typeahead` and `Tokenizer`: after the search source is replaced, pressing ArrowDown on the closed field loads the new source (its focus entries, or the typed query against it) instead of opening the old source's list.
+[fix] `Typeahead` and `Tokenizer`: after the search source is replaced, pressing ArrowDown on the closed field loads the new source (its focus entries, or the typed query against it) instead of opening the old source's list. (#9166)
@cixzhang
diff --git a/.changeset/typeahead-disabled-inert.md b/.changeset/typeahead-disabled-inert.md
index 7416665059..380096cd65 100644
--- a/.changeset/typeahead-disabled-inert.md
+++ b/.changeset/typeahead-disabled-inert.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A `Typeahead` or `Tokenizer` disabled with a reason (`isDisabled` with `disabledMessage`) no longer opens its results from ArrowDown or a click. A `Typeahead` disabled this way also no longer accepts a pick by Enter or a press, even from a list that was open before it became disabled (a `Tokenizer` already refused those). Escape or Tab still closes such a list.
+[fix] A `Typeahead` or `Tokenizer` disabled with a reason (`isDisabled` with `disabledMessage`) no longer opens its results from ArrowDown or a click. A `Typeahead` disabled this way also no longer accepts a pick by Enter or a press, even from a list that was open before it became disabled (a `Tokenizer` already refused those). Escape or Tab still closes such a list. (#9036)
@cixzhang @duytbp
diff --git a/.changeset/typeahead-disabled-keeps-tab-stop.md b/.changeset/typeahead-disabled-keeps-tab-stop.md
index a60bdf2cc9..f033051a71 100644
--- a/.changeset/typeahead-disabled-keeps-tab-stop.md
+++ b/.changeset/typeahead-disabled-keeps-tab-stop.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Typeahead, Tokenizer, PowerSearch: a disabled field keeps its tab stop. Before, a field disabled without a `disabledMessage` rendered a natively disabled input, so Tab skipped it and screen-reader users moving by focus never reached it. Now the input is announced as disabled (`aria-disabled`), stays read-only, opens and picks nothing, and shows a focus ring under keyboard focus. A search still in flight when the field becomes disabled is dropped: it opens, announces, and spins nothing. A Tokenizer or PowerSearch with `tokenOverflowBehavior="unfocusedLayer"` and no `disabledMessage` keeps its natively disabled input for now.
+[fix] Typeahead, Tokenizer, PowerSearch: a disabled field keeps its tab stop. Before, a field disabled without a `disabledMessage` rendered a natively disabled input, so Tab skipped it and screen-reader users moving by focus never reached it. Now the input is announced as disabled (`aria-disabled`), stays read-only, opens and picks nothing, and shows a focus ring under keyboard focus. A search still in flight when the field becomes disabled is dropped: it opens, announces, and spins nothing. A Tokenizer or PowerSearch with `tokenOverflowBehavior="unfocusedLayer"` and no `disabledMessage` keeps its natively disabled input for now. (#9275)
@cixzhang
diff --git a/.changeset/typeahead-ignore-accents.md b/.changeset/typeahead-ignore-accents.md
index c55228dd00..7e7969bfeb 100644
--- a/.changeset/typeahead-ignore-accents.md
+++ b/.changeset/typeahead-ignore-accents.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Type-to-select ignores accents in every locale. Pressing `d` now reaches "Đào", `a` reaches "Ánh" and "Åsa", `n` reaches "Ñandú", `l` reaches "Łódź", and `ı` now reaches "Isparta" and "İzmir". This applies to a closed Selector and to open DropdownMenu, ContextMenu, MultiSelector and TreeList lists, and to the public `useTypeahead` and `useTreeFocus` hooks. Before, a key typed without the mark skipped every item that starts with the marked letter. Matching ignores case, the combining accents U+0300–U+036F, the stroked letters đ ł ø ħ ŧ ƀ, and Turkish dotted and dotless i. It works the same way in every locale, because type-to-select is navigation, not sorting. When you type the accented letter itself, an exact match comes first. For Turkish, ı pairs with I and İ with i. A combining mark typed first is ignored; typed after a letter, it is part of that letter. Sorting and search filtering are unchanged. This meets `architecture:internationalization` INV17. No API changes.
+[fix] Type-to-select ignores accents in every locale. Pressing `d` now reaches "Đào", `a` reaches "Ánh" and "Åsa", `n` reaches "Ñandú", `l` reaches "Łódź", and `ı` now reaches "Isparta" and "İzmir". This applies to a closed Selector and to open DropdownMenu, ContextMenu, MultiSelector and TreeList lists, and to the public `useTypeahead` and `useTreeFocus` hooks. Before, a key typed without the mark skipped every item that starts with the marked letter. Matching ignores case, the combining accents U+0300–U+036F, the stroked letters đ ł ø ħ ŧ ƀ, and Turkish dotted and dotless i. It works the same way in every locale, because type-to-select is navigation, not sorting. When you type the accented letter itself, an exact match comes first. For Turkish, ı pairs with I and İ with i. A combining mark typed first is ignored; typed after a letter, it is part of that letter. Sorting and search filtering are unchanged. This meets `architecture:internationalization` INV17. No API changes. (#8864)
@HelloOjasMutreja @cixzhang
diff --git a/.changeset/typeahead-incremental-results.md b/.changeset/typeahead-incremental-results.md
index f21508c007..bca5c7b4c2 100644
--- a/.changeset/typeahead-incremental-results.md
+++ b/.changeset/typeahead-incremental-results.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[feat] A `SearchSource` can show results before its search settles. `search(query, context)` may call `context.update(items)` (new exported type `SearchContext`) to show matches it already has, such as people the page loaded earlier, and then return the server's answer. `BaseTypeahead`, `Typeahead` and `Tokenizer` show each list for the current query, change the list at most once per keystroke, and add later rows only after the ones already shown, so the highlighted row never moves; the field stays busy and the result count is announced once, when the search settles. A later list that moves or removes shown rows is shown as given with a development warning. Sources that never call `update` show one list per query as before, with two changes every field sees: option element ids now follow the item's `id` instead of its row index (tests that select options by an index-based id need updating), and a grouped `Tokenizer` with `hasCreate` shows its Create row after the groups instead of first. To show local matches at once, pass `debounceMs={0}` and delay the server request inside the source (`spec:AST-092`).
+[feat] A `SearchSource` can show results before its search settles. `search(query, context)` may call `context.update(items)` (new exported type `SearchContext`) to show matches it already has, such as people the page loaded earlier, and then return the server's answer. `BaseTypeahead`, `Typeahead` and `Tokenizer` show each list for the current query, change the list at most once per keystroke, and add later rows only after the ones already shown, so the highlighted row never moves; the field stays busy and the result count is announced once, when the search settles. A later list that moves or removes shown rows is shown as given with a development warning. Sources that never call `update` show one list per query as before, with two changes every field sees: option element ids now follow the item's `id` instead of its row index (tests that select options by an index-based id need updating), and a grouped `Tokenizer` with `hasCreate` shows its Create row after the groups instead of first. To show local matches at once, pass `debounceMs={0}` and delay the server request inside the source (`spec:AST-092`). (#7962)
@cixzhang
diff --git a/.changeset/typeahead-input-press-keeps-list.md b/.changeset/typeahead-input-press-keeps-list.md
index 8c0d526be1..9ddb8abddb 100644
--- a/.changeset/typeahead-input-press-keeps-list.md
+++ b/.changeset/typeahead-input-press-keeps-list.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] A press in a Typeahead's or Tokenizer's own text input, or on its buttons, no longer closes its open list. Clicking between two letters to fix a typo moves the caret and keeps the matches showing; a press anywhere else on the page still closes the list, and Escape still does.
+[fix] A press in a Typeahead's or Tokenizer's own text input, or on its buttons, no longer closes its open list. Clicking between two letters to fix a typo moves the caret and keeps the matches showing; a press anywhere else on the page still closes the list, and Escape still does. (#9367)
@duytbp
diff --git a/.changeset/typeahead-open-list-replaced-source.md b/.changeset/typeahead-open-list-replaced-source.md
index c1a9bb918a..b7990cb548 100644
--- a/.changeset/typeahead-open-list-replaced-source.md
+++ b/.changeset/typeahead-open-list-replaced-source.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] `Tokenizer`: an open list reloads when the tokens change, so it shows current choices instead of the old ones — a token removed with its button is offered again, and a value set from outside is no longer listed.
+[fix] `Tokenizer`: an open list reloads when the tokens change, so it shows current choices instead of the old ones — a token removed with its button is offered again, and a value set from outside is no longer listed. (#9416)
@cixzhang
diff --git a/.changeset/typeahead-token-tab-stop-named.md b/.changeset/typeahead-token-tab-stop-named.md
index e1f26221d4..4c7a602bb8 100644
--- a/.changeset/typeahead-token-tab-stop-named.md
+++ b/.changeset/typeahead-token-tab-stop-named.md
@@ -2,7 +2,7 @@
'@astryxdesign/core': patch
---
-[fix] With a value, a `Typeahead`'s Tab stop is the value's token button (WCAG 2.2 SC 2.4.6 and 4.1.2). It was named by the value alone ("Apple"), so screen reader users could not tell which field it belonged to. It is now named by the field label and the value ("Fruit Apple"), and described by the field's description and status.
+[fix] With a value, a `Typeahead`'s Tab stop is the value's token button (WCAG 2.2 SC 2.4.6 and 4.1.2). It was named by the value alone ("Apple"), so screen reader users could not tell which field it belonged to. It is now named by the field label and the value ("Fruit Apple"), and described by the field's description and status. (#9049)
A clickable `Token` passed `aria-labelledby` and `aria-describedby` to its root, a generic element where they named nothing. It now passes them to its inner button, the element that owns its action. Every other structure keeps them on its root.
diff --git a/.changeset/uikit-motion-animator-pseudo-element.md b/.changeset/uikit-motion-animator-pseudo-element.md
index 7ccb10bab3..6142b8f108 100644
--- a/.changeset/uikit-motion-animator-pseudo-element.md
+++ b/.changeset/uikit-motion-animator-pseudo-element.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the touch presentations' animator drives a pseudo-element such as a dialog's ::backdrop: a static filling animation holds its value after a curve ends and after `set`, a custom property on its host promotes it, and a Reduce Motion dip borrows and hands back the pseudo-element's own opacity. Not exported from the package entry point.
+[chore] Internal: the touch presentations' animator drives a pseudo-element such as a dialog's ::backdrop: a static filling animation holds its value after a curve ends and after `set`, a custom property on its host promotes it, and a Reduce Motion dip borrows and hands back the pseudo-element's own opacity. Not exported from the package entry point. (#8522)
@vjeux
diff --git a/.changeset/use-attachment-hooks.md b/.changeset/use-attachment-hooks.md
index 4172186774..3e2a8eb592 100644
--- a/.changeset/use-attachment-hooks.md
+++ b/.changeset/use-attachment-hooks.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: the gesture hooks' attach-and-release lifecycle, `useAttachment`, moves to `hooks/` (not exported), where other hooks can use it, and `useFingerScroll` keeps its finger-scroll watch through it instead of its own copy of that lifecycle. The gesture-sync helpers stay in `gestures/gestureSync.ts`. No behavior changes.
+[chore] Internal: the gesture hooks' attach-and-release lifecycle, `useAttachment`, moves to `hooks/` (not exported), where other hooks can use it, and `useFingerScroll` keeps its finger-scroll watch through it instead of its own copy of that lifecycle. The gesture-sync helpers stay in `gestures/gestureSync.ts`. No behavior changes. (#9414)
@vjeux
diff --git a/.changeset/use-collator-name-sort-example.md b/.changeset/use-collator-name-sort-example.md
index 61a6b7beb5..bb70283226 100644
--- a/.changeset/use-collator-name-sort-example.md
+++ b/.changeset/use-collator-name-sort-example.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[docs] A new `useCollator — Locale-aware Name Sort` example block sorts a list of names with the compare function from `useCollator`: accented and lowercase names land where a reader expects, and switching the provider locale to Swedish moves Å and Ö after Z. Copy it with `astryx template useCollatorHookUsage <path>`.
+[docs] A new `useCollator — Locale-aware Name Sort` example block sorts a list of names with the compare function from `useCollator`: accented and lowercase names land where a reader expects, and switching the provider locale to Swedish moves Å and Ö after Z. Copy it with `astryx template useCollatorHookUsage <path>`. (#9510)
@MannXo
diff --git a/.changeset/use-finger-scroll.md b/.changeset/use-finger-scroll.md
index e48f0b171d..fa8270ca68 100644
--- a/.changeset/use-finger-scroll.md
+++ b/.changeset/use-finger-scroll.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[chore] Internal: `useFingerScroll(scroller)` tells a finger's scroll from the program's, and the gestures README gains a guide to migrating a raw-touch drag onto the recognizers. Internal to the touch components: not exported from the package entry point or the gestures barrel.
+[chore] Internal: `useFingerScroll(scroller)` tells a finger's scroll from the program's, and the gestures README gains a guide to migrating a raw-touch drag onto the recognizers. Internal to the touch components: not exported from the package entry point or the gestures barrel. (#8360)
@vjeux
diff --git a/.changeset/use-theme-mode-out-of-range.md b/.changeset/use-theme-mode-out-of-range.md
index c6372e97d3..f0ede66d8f 100644
--- a/.changeset/use-theme-mode-out-of-range.md
+++ b/.changeset/use-theme-mode-out-of-range.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] useTheme: `mode` is always `'light'` or `'dark'`. A mode outside `light | dark | system`, such as a stale persisted preference, now resolves through the OS preference like `'system'` instead of being returned as is. First fixed in #5617.
+[fix] useTheme: `mode` is always `'light'` or `'dark'`. A mode outside `light | dark | system`, such as a stale persisted preference, now resolves through the OS preference like `'system'` instead of being returned as is. First fixed in #5617. (#9254)
@cixzhang @AKnassa
diff --git a/.changeset/use-toast-settings-saved-example.md b/.changeset/use-toast-settings-saved-example.md
index 78bc3819b2..fb90441533 100644
--- a/.changeset/use-toast-settings-saved-example.md
+++ b/.changeset/use-toast-settings-saved-example.md
@@ -2,6 +2,6 @@
'@astryxdesign/cli': patch
---
-[docs] A new `useToast — Settings Saved` example block calls the function from `useToast` on a settings form: Save shows a "Settings saved" toast with an Undo action, its `uniqueID` makes a second Save replace the toast instead of stacking another, and a failed save shows an error toast instead. Copy it with `astryx template useToastHookUsage <path>`.
+[docs] A new `useToast — Settings Saved` example block calls the function from `useToast` on a settings form: Save shows a "Settings saved" toast with an Undo action, its `uniqueID` makes a second Save replace the toast instead of stacking another, and a failed save shows an error toast instead. Copy it with `astryx template useToastHookUsage <path>`. (#9512)
@MannXo
diff --git a/.changeset/utils-comment-cleanup-2.md b/.changeset/utils-comment-cleanup-2.md
index a1c0f4aec6..d6eb5b2b23 100644
--- a/.changeset/utils-comment-cleanup-2.md
+++ b/.changeset/utils-comment-cleanup-2.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] More source comments in the core utilities are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes.
+[docs] More source comments in the core utilities are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9527)
@cixzhang
diff --git a/.changeset/utils-comment-cleanup.md b/.changeset/utils-comment-cleanup.md
index 9638d58785..8524eb24e0 100644
--- a/.changeset/utils-comment-cleanup.md
+++ b/.changeset/utils-comment-cleanup.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[docs] Source comments in ten core utility files are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes.
+[docs] Source comments in ten core utility files are shorter and explain only non-obvious reasons. Nothing a consumer imports or renders changes. (#9522)
@cixzhang
diff --git a/.changeset/wheel-mouse-drag-commit.md b/.changeset/wheel-mouse-drag-commit.md
index a16b25f506..6ecef9e6ad 100644
--- a/.changeset/wheel-mouse-drag-commit.md
+++ b/.changeset/wheel-mouse-drag-commit.md
@@ -2,6 +2,6 @@
'@astryxdesign/core': patch
---
-[fix] Dragging a picker wheel with a mouse now commits the value when the button is released, as a finger's drag does. Before, the wheel committed every row it passed while the button was still down, so in DateInput the calendar behind the month and year wheels changed under the hand. This applies to the wheels in the TimeInput, DateTimeInput and DateInput bottom sheets. Touch, keys and a click on a row are unchanged.
+[fix] Dragging a picker wheel with a mouse now commits the value when the button is released, as a finger's drag does. Before, the wheel committed every row it passed while the button was still down, so in DateInput the calendar behind the month and year wheels changed under the hand. This applies to the wheels in the TimeInput, DateTimeInput and DateInput bottom sheets. Touch, keys and a click on a row are unchanged. (#8483)
@vjeux