An open source design system that's fully customizable and agent ready
TypeScript
release: v0.5.0 (#5435)
Cindy Zhangea888ef33283
diff --git a/.changeset/a11y-table-pagination-both-labels.md b/.changeset/a11y-table-pagination-both-labels.mddeleted file mode 100644index 51cb4dd233..0000000000--- a/.changeset/a11y-table-pagination-both-labels.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] useTablePagination: with `position='both'` the two pagination `<nav>` landmarks now get distinct accessible names — "{label} (top)" above the table and "{label} (bottom)" below it (axe landmark-unique). Consumer-supplied `label` values are interpolated into both names; single-position labels are unchanged (#4692).-@AKnassadiff --git a/.changeset/a11y-table-row-expansion-header.md b/.changeset/a11y-table-row-expansion-header.mddeleted file mode 100644index e6cd49eb8f..0000000000--- a/.changeset/a11y-table-row-expansion-header.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Table useTableRowExpansion: the chevron gutter's column header now carries a visually hidden localized name ("Row expansion", key `@astryx.tableRowExpansion.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank (#5383).-@cixzhangdiff --git a/.changeset/a11y-table-row-status-header.md b/.changeset/a11y-table-row-status-header.mddeleted file mode 100644index e79714d2f4..0000000000--- a/.changeset/a11y-table-row-status-header.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Table useTableRowStatus: the status gutter's column header now carries a visually hidden localized name ("Row status", key `@astryx.table.rowStatus.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank (#4693).-@AKnassadiff --git a/.changeset/allow-multiselector-count-labels-to-be-customize-6kj4.md b/.changeset/allow-multiselector-count-labels-to-be-customize-6kj4.mddeleted file mode 100644index 2438b0bda6..0000000000--- a/.changeset/allow-multiselector-count-labels-to-be-customize-6kj4.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[component] Allow MultiSelector count labels to be customized (#4032)-@Kevinjohndiff --git a/.changeset/api-contract-drift-docs-tjsk.md b/.changeset/api-contract-drift-docs-tjsk.mddeleted file mode 100644index e127542ca4..0000000000--- a/.changeset/api-contract-drift-docs-tjsk.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] document missing API contract props across Button, Toast, ContextMenu, MoreMenu, Selector, Link, and Dialog (#4315, part of #4163)--@HelloOjasMutrejadiff --git a/.changeset/aspectratio-responsive-ratio.md b/.changeset/aspectratio-responsive-ratio.mddeleted file mode 100644index c3019b711e..0000000000--- a/.changeset/aspectratio-responsive-ratio.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch------[feat] AspectRatio: emit `ratio` as a class-level declaration instead of a hard inline style, so the ratio can be overridden responsively: StyleX consumers pass an `aspect-ratio` rule via `xstyle` (including under `@media`/`@container` conditions), and plain-CSS/Tailwind consumers override `aspect-ratio` from their own unlayered rules, which beat the `astryx-base` cascade layer regardless of specificity. The mixed-gallery template's hero now switches 3:1 to 3:2 when the grid stacks with a one-line override on a single element, replacing the duplicated hero markup the fixed inline ratio previously forced (#3883, closes #2798)-@jiunshinndiff --git a/.changeset/badge-error-contrast-aa.md b/.changeset/badge-error-contrast-aa.mddeleted file mode 100644index 34b035a687..0000000000--- a/.changeset/badge-error-contrast-aa.md+++ /dev/null@@ -1,8 +0,0 @@-----'@astryxdesign/theme-neutral': patch-'@astryxdesign/cli': patch------[fix] neutral theme: darken the light-mode error red from `#e33f4a` to `#c9303a` so the filled `Badge variant="error"` label clears WCAG 2.1 AA. White on `#e33f4a` is 4.14:1 and the badge label is 12px/weight 500, so the 4.5:1 normal-text threshold applies rather than the 3:1 large-text allowance; `#c9303a` gives 5.29:1 while holding the hue (OKLCH H 21.9 -> 22.8, C 0.200 -> 0.189). StatusDot and the ProgressBar `--color-error` rebinding move with it — both are documented as tracking the badge fill so the dot and its badge read as one status language. Dark mode is untouched (dark text on `#ff705d`, 6.60:1). Adds `scripts/check-badge-contrast.test.mjs`, which resolves every theme's badge label/fill pair through `light-dark()`, `var()` indirection and alpha compositing, and holds all of them to 4.5:1 (#4446).--@AKnassadiff --git a/.changeset/banner-collapsible-content.md b/.changeset/banner-collapsible-content.mddeleted file mode 100644index 5ad6910a2e..0000000000--- a/.changeset/banner-collapsible-content.md+++ /dev/null@@ -1,44 +0,0 @@-----'@astryxdesign/core': minor-'@astryxdesign/cli': minor------[breaking] Banner: the collapse axis moves onto one `collapsible` prop, and content can opt out of collapsing (#5255)--Banner inferred its disclosure from its content: any `children` got a chevron in-the header and were hidden until it was pressed. There was no way to show-content without a toggle — the case a banner most often wants, a list of the-three fields that failed validation — and `defaultIsExpanded` was the only knob,-with no controlled mode.--The whole axis is now one `boolean | CollapsibleConfig` prop, following the-boolean-or-config convention `SideNav.collapsible` set, and backed by the shared-`useCollapsible` hook rather than Banner's own state:--```tsx-<Banner status="error" title="3 fields need attention">…</Banner> // unchanged: collapsible, starts closed-<Banner collapsible={false}>…</Banner> // new: always visible, no toggle-<Banner collapsible={{defaultIsOpen: true}}>…</Banner> // replaces defaultIsExpanded-<Banner collapsible={{isOpen, onOpenChange}}>…</Banner> // new: controlled-```--**The default is unchanged** — a banner that never mentioned `defaultIsExpanded`-behaves exactly as it did. The breaking part is the prop itself:-`defaultIsExpanded` is removed in favour of the config, which is a type error at-every JSX call site that names it.--**Codemod:** `npx astryx upgrade --codemod banner-collapsible-content`--It rewrites `defaultIsExpanded` to `collapsible={{defaultIsOpen: true}}` and-drops `defaultIsExpanded={false}`, which is now the default. Banners that never-set the prop are left alone.--**One case the codemod and the compiler both miss: a spread.**-`defaultIsExpanded` inside a props object is out of the transform's scope. A-props object in a typed position still fails to compile — but an inferred one-that is spread, `<Banner {...args} />`, does not, because TypeScript does not-excess-property-check a spread. The prop then falls through to the DOM and the-banner quietly starts collapsed. **Grep for `defaultIsExpanded` after running-the codemod** and migrate any spread sites by hand.--@freddymetadiff --git a/.changeset/bottom-sheet-ime-escape-guard.md b/.changeset/bottom-sheet-ime-escape-guard.mddeleted file mode 100644index df9daaa071..0000000000--- a/.changeset/bottom-sheet-ime-escape-guard.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] BottomSheet: a standalone sheet no longer dismisses when a CJK user presses Escape to cancel an in-progress IME composition. The browser fires that keydown before `compositionend`, so an Escape handler reading a bare `event.key` misread the composition cancel as a dismissal command and closed the sheet — losing whatever had been typed into a `purpose="form"` field inside it. The handler now early-returns on `isImeKeyEvent`, the same guard `Dialog` and `BottomSheetSwitcher` already carry, and claims the key first so the browser raises no close request of its own (#5322).--@ernesttdiff --git a/.changeset/breadcrumb-current-non-color-indicator.md b/.changeset/breadcrumb-current-non-color-indicator.mddeleted file mode 100644index af0230fd1b..0000000000--- a/.changeset/breadcrumb-current-non-color-indicator.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `Breadcrumbs` marks the current item with semibold weight, not colour alone. The current crumb was distinguished only by `--color-text-primary` against its siblings' `--color-text-secondary`, which fails WCAG 1.4.1 (use of colour) and leaves the current position invisible to anyone who cannot separate the two tones (#4605, closes #4421).--@gonzoblascodiff --git a/.changeset/button-group-layer-arrow-keys.md b/.changeset/button-group-layer-arrow-keys.mddeleted file mode 100644index 931fbeea14..0000000000--- a/.changeset/button-group-layer-arrow-keys.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] ButtonGroup: arrow keys pressed inside a member's open menu stay with that menu. A DropdownMenu renders its menu inline inside the group, so ArrowLeft and ArrowRight used to bubble to the group and move focus onto a sibling button while the menu was still open. The group's `elevation` is also reflected as `data-elevation` now, so a theme can target it (#5355).--@cixzhangdiff --git a/.changeset/button-group-roving-tabindex.md b/.changeset/button-group-roving-tabindex.mddeleted file mode 100644index 630ed307cb..0000000000--- a/.changeset/button-group-roving-tabindex.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] ButtonGroup is a single tab stop. Its members now share one roving tab stop instead of taking one each, so a three-button group costs one Tab press rather than three. Arrow keys move between members along the orientation (flipped in RTL), Home/End jump to the ends, focus wraps, and disabled members are skipped. Two consequences worth knowing: a keyboard script or test that tabbed through a group member by member must use arrow keys now, and a member rendered as a link (`href`) joins the arrow order for the first time. (#5389)--@cixzhangdiff --git a/.changeset/calendar-initial-month-clamp.md b/.changeset/calendar-initial-month-clamp.mddeleted file mode 100644index c843bf435b..0000000000--- a/.changeset/calendar-initial-month-clamp.md+++ /dev/null@@ -1,18 +0,0 @@-----'@astryxdesign/core': patch------[fix] Calendar (and DateInput, DateRangeInput, DateTimeInput) now opens on a month inside the min/max window instead of on today--@imdreamrunner--With no `focusDate` and no selected value, the calendar opened on today's month-even when `min`/`max` excluded it — a 2019 audit window or a booking window that-opens next spring rendered a grid where every day was disabled, and the only way-in was clicking the prev/next arrows once per month.--The initial month is now today clamped into the window: today when it is inside,-otherwise whichever bound is nearest. An explicit `focusDate` or a selected value-still wins, so nothing changes for callers that already say where to look. With-`numberOfMonths={2}` a past window lands `max` in the right-hand pane, so neither-pane is entirely out of bounds (#5306).diff --git a/.changeset/chatmessagelist-add-align-prop-for-top-aligned-l-xm43.md b/.changeset/chatmessagelist-add-align-prop-for-top-aligned-l-xm43.mddeleted file mode 100644index a2e2f5ad72..0000000000--- a/.changeset/chatmessagelist-add-align-prop-for-top-aligned-l-xm43.md+++ /dev/null@@ -1,16 +0,0 @@-----'@astryxdesign/core': patch------[feat] ChatMessageList: add an `align` prop for top-aligned message lists-(#3933, closes #2572).--- `align?: 'top' | 'bottom'` (default `'bottom'`). `'bottom'` keeps the- existing behavior: a flex spacer fills free space so a short conversation- sits just above the composer. `'top'` omits the spacer so messages start at- the top and grow downward — better for log-style or document-style lists.-- Only changes the resting position of a non-full list. Once messages overflow- the container the spacer collapses to zero in both modes, so ChatLayout- auto-scroll-to-bottom behavior is unchanged.--@jiunshinndiff --git a/.changeset/cli-integration-components-in-search.md b/.changeset/cli-integration-components-in-search.mddeleted file mode 100644index d787288986..0000000000--- a/.changeset/cli-integration-components-in-search.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] Unified search and build now include components contributed by integrations, so a component registered through an integration is findable and buildable alongside the built-in set instead of silently missing from both (#5259).--@andrskrdiff --git a/.changeset/cli-theme-targets.md b/.changeset/cli-theme-targets.mddeleted file mode 100644index 43dd1a6442..0000000000--- a/.changeset/cli-theme-targets.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/cli': patch------[feat] CLI: `astryx theme targets` lists every component theming target — the `defineTheme` key, the class it paints, and the props and states it accepts — for one component or the whole system, with `--json` for lint and audit scripts. `astryx theme --help` now points at component overrides instead of reading as a build-tool menu. The listing and `theme build`'s override validation share one enumeration of the component docs, so neither can drift from the components (#5115).-@cixzhangdiff --git a/.changeset/complex-component-contract-docs-tjsk.md b/.changeset/complex-component-contract-docs-tjsk.mddeleted file mode 100644index 5ca7eb87c5..0000000000--- a/.changeset/complex-component-contract-docs-tjsk.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] document missing props across complex components (MultiSelector, Tokenizer, PowerSearch, Typeahead, Layout, DropdownMenu, HoverCard, Tooltip, Link, Lightbox) (#4316, part of #4163)--@HelloOjasMutrejadiff --git a/.changeset/content-component-contract-docs-tjsk.md b/.changeset/content-component-contract-docs-tjsk.mddeleted file mode 100644index fc01d6b516..0000000000--- a/.changeset/content-component-contract-docs-tjsk.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] document the missing components prop on Markdown (#4319, part of #4163)--@HelloOjasMutrejadiff --git a/.changeset/date-input-touch-clear-preventscroll.md b/.changeset/date-input-touch-clear-preventscroll.mddeleted file mode 100644index c8377ba9e3..0000000000--- a/.changeset/date-input-touch-clear-preventscroll.md+++ /dev/null@@ -1,19 +0,0 @@-----'@astryxdesign/core': patch------[fix] DateInput: clearing on touch no longer jumps the page to the top--On the touch surface, tapping the clear (✕) threw the user to the top of the-page. Clearing unmounts the clear button, and `handleClear` focused the field-in that same task — on iOS Safari, focusing an element as the focused button is-removed scrolls the whole document to 0. The focus handoff is now deferred past-the unmount, which keeps the page where it was and still returns focus to the-field.--Measured on the iOS 26 simulator against the live docsite (DateInput —-Clearable, page at scrollY 2055): synchronous focus → 0, deferred focus → 2055.-`preventScroll` alone does not fix it; it is kept for the ordinary-scroll-into-view nudge, which is unwanted for the same reason (#5350).--@imdreamrunnerdiff --git a/.changeset/datetimeinput-time-option-dropdown.md b/.changeset/datetimeinput-time-option-dropdown.mddeleted file mode 100644index 41b55cabd2..0000000000--- a/.changeset/datetimeinput-time-option-dropdown.md+++ /dev/null@@ -1,9 +0,0 @@-----'@astryxdesign/core': patch------[feat] DateTimeInput: new `timeOptionInterval` prop adds a dropdown of preset times to the time field, at a cadence of `5 | 10 | 15 | 30 | 60` minutes (`60` gives the 12 AM - 11 PM list). The field becomes an APG combobox over a `listbox`: click or Alt+ArrowDown opens it, ArrowUp/ArrowDown move the active option, Enter picks, Escape closes, and typing moves the highlight to the closest option without filtering the list. `min`/`max` trim the options on the boundary date. Style the popup through the `date-time-input-time-listbox` and `date-time-input-time-option` theme targets.--Opt-in and additive: with `timeOptionInterval` omitted the time field keeps exactly its current behavior and gains no combobox semantics, so existing `getByRole('combobox')` queries still resolve to the date input. With the list closed the arrow keys keep stepping by `timeIncrement` (#4837).--@AKnassadiff --git a/.changeset/dialog-responsive-interaction.md b/.changeset/dialog-responsive-interaction.mddeleted file mode 100644index 62870f0609..0000000000--- a/.changeset/dialog-responsive-interaction.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Clamp standard Dialog width to dynamic viewport space with token gutters, add safe-area/fullscreen sizing and fade-only fullscreen motion updates, add opt-in adaptive Dialog/BottomSheet recipes, and add explicit presentation comparison stories (#5352).--@rubyycheungdiff --git a/.changeset/dropdown-menu-theme-fixes.md b/.changeset/dropdown-menu-theme-fixes.mddeleted file mode 100644index ca6c6b8722..0000000000--- a/.changeset/dropdown-menu-theme-fixes.md+++ /dev/null@@ -1,9 +0,0 @@-----'@astryxdesign/core': patch------[fix] DropdownMenu: move the `dropdown-menu-indicator-icon` theme target onto the Icon element itself so a theme can restyle the submenu chevron's size and color directly.--The loading branch no longer carries the target — its `Spinner` has its own `astryx-spinner` target, matching Selector, MultiSelector and ComplexSelector (#4743).--@athzdiff --git a/.changeset/field-contract-docs-tjsk.md b/.changeset/field-contract-docs-tjsk.mddeleted file mode 100644index b208a320d5..0000000000--- a/.changeset/field-contract-docs-tjsk.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] document labelID and isGroupLabel props in Field (#4320, part of #4163)--@HelloOjasMutrejadiff --git a/.changeset/fix-chat-bubble-token-alignment.md b/.changeset/fix-chat-bubble-token-alignment.mddeleted file mode 100644index 7785dbbe6f..0000000000--- a/.changeset/fix-chat-bubble-token-alignment.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Chat: a token in a message bubble now sits on the line the way it does in the composer. `ChatTokenizedText` wraps each token in the same `inline-flex` / `vertical-align: middle` box `ChatComposerInput` uses, so a chip stops lifting off the text the moment the message is sent. Follows #5324, which fixed the composer half (#5402).--@cixzhangdiff --git a/.changeset/fix-chat-token-alignment.md b/.changeset/fix-chat-token-alignment.mddeleted file mode 100644index eb32cb44d9..0000000000--- a/.changeset/fix-chat-token-alignment.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Chat: composer tokens no longer sit above surrounding text — `vertical-align` changed from `baseline` to `middle`, and `ChatComposerTokenElement` now uses a StyleX class instead of an inline style so consumers can override alignment without `!important` (#5324).--@athzdiff --git a/.changeset/focus-trap-tab-outside.md b/.changeset/focus-trap-tab-outside.mddeleted file mode 100644index 856f08b0e0..0000000000--- a/.changeset/focus-trap-tab-outside.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] useFocusTrap: Tab is only cancelled when focus is actually inside the trapped container. An open layer whose focus legitimately sits outside it — a listbox popup anchored to its own input, as in DateTimeInput, Typeahead, Selector and MultiSelector — no longer swallows Tab for the whole page, so keyboard users move to the next control on the first press. A trapped surface with no tabbable controls and focus on a `tabIndex={-1}` panel still keeps Tab inside it (#5397).-@cixzhangdiff --git a/.changeset/kbd-hotkeys-blank-client-hints-platform.md b/.changeset/kbd-hotkeys-blank-client-hints-platform.mddeleted file mode 100644index 4c3789adc4..0000000000--- a/.changeset/kbd-hotkeys-blank-client-hints-platform.md+++ /dev/null@@ -1,16 +0,0 @@-----'@astryxdesign/core': patch------[fix] `mod` hotkeys and `Kbd` resolve to Cmd on macOS again when client hints report a blank platform--`useHotkeys` and `Kbd` both prefer `navigator.userAgentData.platform` and fall-back to `navigator.platform`, but guarded the preference with-`'platform' in uaData`, which is true whenever the key exists at all. A build-reporting `platform: ''` therefore committed to the client-hints branch and got-`false` without ever reaching the fallback, so on macOS every `mod` combo-listened for Ctrl and every `<Kbd>` drew Ctrl. Electron and other embedders-that rewrite the app's user-agent identity ship exactly that. A blank platform-is now treated as unknown and falls through (#5325).--@Astro-Handiff --git a/.changeset/layer-dismissal-stack.md b/.changeset/layer-dismissal-stack.mddeleted file mode 100644index 0acd725897..0000000000--- a/.changeset/layer-dismissal-stack.md+++ /dev/null@@ -1,8 +0,0 @@-----'@astryxdesign/core': minor------[breaking] Overlays share one dismissal stack, so a single Escape dismisses exactly one layer. Every overlay used to own its own Escape listener, which meant one press could close a popover _and_ the Dialog hosting it, or a modal _and_ the modal it was opened from. `useLayerDismissal` replaces that with a single stack: the stack owns one listener, routes each press to the top-most layer, and suppresses the browser's own close-watcher so nothing dismisses twice. A layer declares what it does with a press via `escapeBehavior` — `close` (default) or `block`, for a `required` Dialog that must swallow the press without closing so nothing behind it dismisses either. Fixes a Tooltip inside a Dialog closing the Dialog rather than the tip, and a HoverCard trigger swallowing Escape whenever it merely had focus. Dismissals the browser starts on its own — the Android back gesture, the platform close watcher — still close a Dialog, and follow the same top-most rule. An Escape that cancels an in-progress IME composition dismisses nothing: the stack claims that press so the browser raises no close request of its own, and a close request that arrives mid-composition anyway is declined, so a CJK user backing out of a half-formed character no longer loses the layer and everything typed into it. One behavior change worth knowing about if you listen for Escape yourself: the stack claims a press with `preventDefault()` but deliberately leaves propagation alone, so a `keydown` listener on `window` now sees an Escape that a focus-trapped layer used to stop — with `defaultPrevented` already `true`, which is how to tell the stack has acted on it. Top-most is resolved from React-tree nesting (which survives portals) rather than DOM containment alone. A layer's place in that order is keyed to the layer's identity rather than to each registration, so a prop change that re-registers it — a Dialog whose `purpose` flips while it is open — never promotes it above the layers opened over it. Controlled layers follow their control state: a controlled `Tooltip` or `HoverCard` stays on the stack and takes the press like any other layer, but answers it by calling `onOpenChange(false)` rather than hiding itself — whether it actually closes is the caller's update to make, exactly as it has always been for `Dialog` (#4881).--@freddymeta-@cixzhangdiff --git a/.changeset/markdown-incremental-cache-holds.md b/.changeset/markdown-incremental-cache-holds.mddeleted file mode 100644index 6f1189256e..0000000000--- a/.changeset/markdown-incremental-cache-holds.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Markdown streaming: `parseMarkdownIncremental` no longer throws away its settled blocks while a code fence is open, or when a chunk happens to end on a newline — both re-parsed the whole document, so a long streamed response got slower the longer it grew. Blocks rebuilt across a streamed 500-paragraph document: 126,756 → 1,869 (#5407).-@cixzhangdiff --git a/.changeset/markdown-source-ranges.md b/.changeset/markdown-source-ranges.mddeleted file mode 100644index 0d53bd0431..0000000000--- a/.changeset/markdown-source-ranges.md+++ /dev/null@@ -1,33 +0,0 @@-----'@astryxdesign/core': patch------[feat] Markdown: opt-in source ranges on parsed blocks--`parseMarkdown(source, {sourceRanges: true})` now gives every top-level block a-`range` — `{start, end}`, the character offsets it occupies in the source that-was passed in, with `end` exclusive — so a consumer holding that source can-`source.slice(range.start, range.end)` for a block instead of reconstructing it-from the node (or from the rendered DOM).-Reconstruction is lossy in ways slicing is not: escapes, the exact emphasis and-fence characters, heading depth beyond the clamp, and alignment all survive a-slice unchanged.--Off by default and absent unless asked for, so no existing node, snapshot or-comparison changes.--Two things the offsets get right that a naive implementation does not: link-reference definitions are stripped before the block loop runs, and the ranges-are reported against the string the caller passed rather than the stripped-text; and `parseMarkdownIncremental` parses slices, so blocks report absolute-offsets into the whole document as it streams — including a list whose halves-arrived in separate chunks and were merged.--A range covers a block's own lines verbatim, so slicing it and parsing the-result gives the same node back.--Blocks nested inside a list item or a blockquote carry no range: their children-are parsed from text the parser reassembled with markers and `>` prefixes-removed, so an offset into it would not address the document (#5290).--@lexsdiff --git a/.changeset/migrate-inline-merge-refs.md b/.changeset/migrate-inline-merge-refs.mddeleted file mode 100644index a12d7a67bb..0000000000--- a/.changeset/migrate-inline-merge-refs.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Migrate core components from inline mergeRefs calls to stable useMergedRefs callbacks (#5267).--@nynexman4464diff --git a/.changeset/multiselector-format-value.md b/.changeset/multiselector-format-value.mddeleted file mode 100644index 3b28fc5f0c..0000000000--- a/.changeset/multiselector-format-value.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[component] MultiSelector: rename the unreleased `formatTriggerCount` prop to `formatValue` and widen it to the whole trigger line. It now receives the selected items (`{value, label}[]`, count available as `.length`) and formats the trigger for `triggerDisplay="count"` and `"labels"`; `"badges"` renders elements, so it is not used there. `formatValue` matches NumberInput and Slider, so the same idea has one name across the system. Defaults are unchanged when the prop is absent (#5377).--@Kevinjohndiff --git a/.changeset/powersearch-applies-menuwidth-to-its-main-field--ffyn.md b/.changeset/powersearch-applies-menuwidth-to-its-main-field--ffyn.mddeleted file mode 100644index 73c5d8fba9..0000000000--- a/.changeset/powersearch-applies-menuwidth-to-its-main-field--ffyn.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] PowerSearch now applies `menuWidth` to the initial field and search menu without letting it shrink below the input width. Value menus shown after selecting a field are unchanged. (#5237)-@nynexman4464diff --git a/.changeset/powersearch-applies-operator-menu-limit.md b/.changeset/powersearch-applies-operator-menu-limit.mddeleted file mode 100644index f818d794c8..0000000000--- a/.changeset/powersearch-applies-operator-menu-limit.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] PowerSearch: `maxOperatorMenuItems` now caps suggestions in string, string-list, and entity-list value typeaheads, including values inside nested filters (#5242).--@nynexman4464diff --git a/.changeset/powersearch-narrow-viewport-fit.md b/.changeset/powersearch-narrow-viewport-fit.mddeleted file mode 100644index 857e3064ad..0000000000--- a/.changeset/powersearch-narrow-viewport-fit.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] PowerSearch: the edit popover now fits narrow viewports — its 400px minimum width yields to the screen width, and the filter row wraps instead of overflowing when long translated operator labels don't fit. An editor anchored near the screen edge now stays on its own side at the width available there, wrapping internally, instead of flipping across the anchor to keep 400px (#4768).--@AKnassadiff --git a/.changeset/powersearch-renders-optional-field-groups-while--a8n4.md b/.changeset/powersearch-renders-optional-field-groups-while--a8n4.mddeleted file mode 100644index 666500dae8..0000000000--- a/.changeset/powersearch-renders-optional-field-groups-while--a8n4.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] PowerSearch now groups fields in the browsing menu using each field's `group` value. Ungrouped fields appear first, while typed search results remain flat. (#5235)-@nynexman4464diff --git a/.changeset/powersearch-shows-the-full-field-list-while-brow-5j66.md b/.changeset/powersearch-shows-the-full-field-list-while-brow-5j66.mddeleted file mode 100644index f83eb3aa31..0000000000--- a/.changeset/powersearch-shows-the-full-field-list-while-brow-5j66.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] PowerSearch now shows up to 1,000 configured fields when the search box is empty, instead of stopping at 10. Typed searches still show 10 ranked results by default; use `maxSearchResults` to change only that limit. (#5233)-@nynexman4464diff --git a/.changeset/promote-stepper-to-core.md b/.changeset/promote-stepper-to-core.mddeleted file mode 100644index 5468e4eda2..0000000000--- a/.changeset/promote-stepper-to-core.md+++ /dev/null@@ -1,12 +0,0 @@-----'@astryxdesign/cli': patch-'@astryxdesign/core': patch------[component] Promote `Stepper` and `Step` from the canary-only Lab package to Core. The stable package now ships their existing horizontal/vertical layouts, separated and on-track indicators, semantic status, density, and non-linear navigation, plus Core documentation and rendered examples. The default `aria-label` is now localized.--Advancing one step now animates the connector. Every connector the four layouts draw — the separated bars and the on-track segments alike — grows its accent fill out of the segment's leading edge instead of swapping a background color, so moving forward reads as progress travelling the track. That one gesture is the only thing that animates: going back, jumping forward by more than one step, and mounting mid-flow all apply at once, as does any change under `prefers-reduced-motion`. Retreats are deliberately instant — run in reverse the same transition ends on a shrinking stub of accent, and a remnant still on the track reads as unfinished where the identical curve growing forward reads as arrived — and multi-step jumps are instant because a jump is a navigation rather than a progression, so sweeping a front across the crossed segments only makes the user sit out a journey they asked to skip. Where one span is drawn by several segments (the on-track layouts split a span between two steps, three when a content slot sits between them) the segments take abutting slices of the span's time and run linearly, so the fill reads as one line growing at a constant speed rather than pieces lighting in turn.--Five visual fixes land with the promotion. Horizontal steps now divide the track evenly instead of sizing to their own labels, so every progress segment is the same width regardless of how long a step is named. Number indicators shrink from 20px to 16px to match the check, ring, and custom-icon indicators, so a step swapping its number for a check as it completes no longer nudges the label beside it. A step description now occupies a 16px box rather than a 24px one — it previously inherited the page's line box instead of applying its own leading, which opened an 8px gap under the label. A step's content slot now starts flush with the label above it at every density: the slot renders outside the density-padded label area, so it was hanging one pad short of it. And a vertical on-track step carrying content keeps its connector unbroken — the content renders below the row that draws the line, so the track used to split open around any step with content (#5201).--@ernesttdiff --git a/.changeset/selector-divider-listbox-violation.md b/.changeset/selector-divider-listbox-violation.mddeleted file mode 100644index 614330a654..0000000000--- a/.changeset/selector-divider-listbox-violation.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `Selector` and `MultiSelector` no longer expose their `{type: 'divider'}` separators to assistive technology. `role="listbox"` only permits `option`/`group` children, but the divider previously rendered `role="separator"` as a direct child of the listbox (axe `aria-required-children`, impact critical). The divider is decorative and carries no information the options don't, so it's now hidden from the accessibility tree via `aria-hidden`, matching the pattern already used for section headings (#5107).--@HelloOjasMutrejadiff --git a/.changeset/spinner-svg-ring.md b/.changeset/spinner-svg-ring.mddeleted file mode 100644index 680b8494f0..0000000000--- a/.changeset/spinner-svg-ring.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[refactor] Spinner: the ring is drawn in SVG instead of `<canvas>`. The arc and track take their colours from the cascade (`currentColor` for `shade="inherit"`), so nothing resolves a colour in JS: a colour change after mount now repaints the ring instead of leaving it stale until it remounts, and mounting spinners no longer costs a `getComputedStyle` each. Rings are pinned to the document timeline's origin, so spinners mounted at different times turn in phase. No API, geometry or theme-target change (#5408).--@cixzhangdiff --git a/.changeset/stabilize-hoisted-merged-refs.md b/.changeset/stabilize-hoisted-merged-refs.mddeleted file mode 100644index e72436a40a..0000000000--- a/.changeset/stabilize-hoisted-merged-refs.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Keep merged refs stable across Avatar, Button, SideNav, TabList, and TopNav (#5429).--@nynexman4464diff --git a/.changeset/stable-text-refs.md b/.changeset/stable-text-refs.mddeleted file mode 100644index d0453f6aa2..0000000000--- a/.changeset/stable-text-refs.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Add useMergedRefs and keep Text and Heading refs stable across rerenders (#5266).--@nynexman4464diff --git a/.changeset/structural-component-contract-docs-tjsk.md b/.changeset/structural-component-contract-docs-tjsk.mddeleted file mode 100644index 11ae150d9f..0000000000--- a/.changeset/structural-component-contract-docs-tjsk.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] document missing props across structural components (CodeBlock, Toolbar) (#4317, part of #4163)--@HelloOjasMutrejadiff --git a/.changeset/table-grouped-template-table-body.md b/.changeset/table-grouped-template-table-body.mddeleted file mode 100644index 5266c720a2..0000000000--- a/.changeset/table-grouped-template-table-body.md+++ /dev/null@@ -1,19 +0,0 @@-----'@astryxdesign/cli': patch------[fix] Table - Grouped page template: wrap the rows in `TableBody`--The template rendered `<TableRow>` straight into `<Table>`, so the emitted DOM-was `<table><tr>`. `<table>` cannot contain a row directly: the HTML parser-inserts an implied `<tbody>` when it parses server-rendered markup and React-does not when it renders on the client, so anyone who copied the template into-an app as a server-rendered page inherited a hydration mismatch in their own-app. Client-only the DOM is still invalid — nothing reparents the rows, so the-table ends up with `<tr>` children and no `<tbody>` at all, and any CSS or-query aimed at `tbody` silently misses.--The rows now sit in `<TableBody>`, the same element the data-driven `data={...}`-path renders, so styling, dividers, and column widths are unchanged (#5278).--@AKnassa @rubyycheungdiff --git a/.changeset/table-section-component-docs.md b/.changeset/table-section-component-docs.mddeleted file mode 100644index 1a36e3f460..0000000000--- a/.changeset/table-section-component-docs.md+++ /dev/null@@ -1,20 +0,0 @@-----'@astryxdesign/core': patch------[docs] Table: document the section components children mode requires--Children mode stopped wrapping children in a `<tbody>` in #2098, but the docs-still described the contract from before it. The `children` prop read "render-TableRow/TableCell directly"; `TableRow`'s own `@example` showed a row sitting-in `<Table>` with no section around it; and `TableHeader`, `TableBody`, and-`TableFooter` — public exports since that change — had no docs at all and were-missing from `Table`'s component list. A reader following the component's own-documentation wrote `<table><tr>`, which is invalid HTML and mismatches on-hydration.--The three section components are now documented, listed on `Table`, and named-in the `children` prop description, in a best practice, and in `TableRow`'s-example (#5278).--@AKnassa @rubyycheungdiff --git a/.changeset/table-selection-row-highlight-opt-out.md b/.changeset/table-selection-row-highlight-opt-out.mddeleted file mode 100644index bde7e63a73..0000000000--- a/.changeset/table-selection-row-highlight-opt-out.md+++ /dev/null@@ -1,21 +0,0 @@-----'@astryxdesign/core': patch------[feat] Table: let `useTableSelection` opt out of the checked-row accent wash--The selection plugin paints checked rows by writing `backgroundColor` straight-onto each `<tr>` from its row ref callback. An inline style outranks anything-StyleX can layer on, so a product that wanted the row background for its own-meaning had no way to reclaim it short of forking the plugin.--`hasRowHighlight` turns the wash off. It defaults to `true`, so existing tables-are untouched. Only the background is dropped — `aria-selected` is still set and-removed exactly as before, since that is the half of the state screen readers-read.--```tsx-useTableSelection({...config, hasRowHighlight: false});-``` (#5310)--@ernesttdiff --git a/.changeset/table-suppress-cell-content.md b/.changeset/table-suppress-cell-content.mddeleted file mode 100644index 2b04dbf936..0000000000--- a/.changeset/table-suppress-cell-content.md+++ /dev/null@@ -1,22 +0,0 @@-----'@astryxdesign/core': patch------[fix] Table: a plugin can suppress a body cell's content, and grouped rows use it to keep synthetic group headers out of your cell renderers (#5363)--`useTableGroupedRows` injects section-header rows into the flattened data, and-`BaseTable` evaluates every column's `renderCell` against every row. A renderer-that keys a lookup off a field — `STATUS_META[item.status].dot` — was therefore-handed a row that is not yours and threw, blanking the page the moment grouping-was switched on. The header Proxy answering unknown fields with `''` only ever-rescued a renderer that _prints_ a field; `''` fails a lookup exactly as-`undefined` does.--`BodyCellRenderProps` gains `isContentSuppressed?: boolean`. A plugin sets it in-`transformBodyCell` for a row whose cells it is about to replace wholesale in-`transformBodyRow`, and the table renders that cell empty without calling the-column's renderer or the default one. It is decided per cell at render time-against the final column list, so it also covers columns other plugins-contributed — whatever order the plugins were listed in.--@ernesttdiff --git a/.changeset/tablist-aria-role.md b/.changeset/tablist-aria-role.mddeleted file mode 100644index b4110172bc..0000000000--- a/.changeset/tablist-aria-role.md+++ /dev/null@@ -1,13 +0,0 @@-----'@astryxdesign/core': patch------[feat] TabList: a strip that switches panels in place can now say so with `role="tablist"`, and it speaks the WAI-ARIA tabs pattern — `role="tablist"` on the strip, `role="tab"` and `aria-selected` on the tabs, and `aria-controls` pointing at the panel each tab opens, from a new `panelId` prop on `Tab`. There is no new prop for the switch: `TabList` declares `role?: AriaRole` and reads it, the way `LayoutHeader`, `LayoutContent` and `LayoutPanel` already declare and document theirs. The keyboard behaviour the pattern asks for was already there: arrows move between tabs, Tab leaves the strip. Under the asserted role the strip takes only the horizontal arrows, leaving ArrowUp and ArrowDown to scroll the page.--`role` already reached the DOM through `{...restProps}`, so a caller could pass `role="tablist"` and get a tablist whose children were still `<button>`s with `aria-current` — invalid markup, no `aria-selected`, and no warning. Reading the role turns that silent breakage into the correct behaviour; declaring it is what puts it in the type, the prop table and the docs.--**Nothing changes for a caller who passes no `role`**: the strip is the `<nav>` landmark with `aria-current` it has always been. Any other role still passes through to the element untouched.--Two development warnings come with the asserted role, and only with it. A tab with an `href` is a false statement inside a tablist, so the `href` is ignored and the warning says so. And a tab that controls nothing gets asked for a `panelId` — either that or an `aria-controls` you wrote yourself satisfies it, and a hand-written one is never overwritten. `aria-controls` is emitted only when you supply the id: pointing at a panel that does not exist is an invalid attribute value, which is worse than saying nothing. A menu or any other non-tab in a tablist strip is invalid markup, and warns too. The mirror case warns as well: a `panelId` on a strip that is not a tablist has no panel relationship to state, and is dropped (#5349).--@cixzhangdiff --git a/.changeset/tablist-scroll-overflow.md b/.changeset/tablist-scroll-overflow.mddeleted file mode 100644index 47d39e2bbf..0000000000--- a/.changeset/tablist-scroll-overflow.md+++ /dev/null@@ -1,9 +0,0 @@-----'@astryxdesign/core': patch------[feat] TabList: a strip narrower than its tabs now scrolls instead of spilling out of its container. Every tab stays a tab — nothing is hidden behind a menu — the edges fade to show there is more, and pointers that can hover get arrow affordances; keyboard and screen-reader users reach every tab with the arrow keys, which scrolls the focused tab into view. The selected tab is scrolled back into view whenever it would be out of sight, including on mount and when the host changes `value` itself. The new `overflow` prop takes `'auto'` (the default, which today always scrolls), `'scroll'`, or `'visible'` to keep the old spill-out layout. Built on the existing `useScrollOverflow` hook, so there is no new measurement machinery and no `Carousel` in the tab strip — the documented Carousel recipe, which announced every tab as "slide N of M", is no longer needed and the stories now use the built-in behaviour.--If you followed that recipe, nothing breaks: a `Carousel` still wrapping the tabs renders and behaves exactly as it did before, because its own scroll container absorbs the strip's, which then never overflows. Removing it is worth doing anyway — it drops the `region`/"slide N of M" wrapping from the accessibility tree, and the strip's own scrolling brings a tab that straddles the edge fully into view on focus, which the carousel does not (#5348).--@cixzhangdiff --git a/.changeset/theming-var-enumeration.md b/.changeset/theming-var-enumeration.mddeleted file mode 100644index 0a77b472db..0000000000--- a/.changeset/theming-var-enumeration.md+++ /dev/null@@ -1,13 +0,0 @@-----'@astryxdesign/cli': patch------[chore] Public component theming vars are enumerable, and guarded against being documented but unsettable-@cixzhang--`collectThemingVars` joins `collectThemingTargets` as part of the one-enumeration the theming surface is read from. Two guards ride on it: a-documented public var no component reads compiles to a declaration that never-applies, and a var the component writes inline outranks every cascade layer, so-no theme can reach it. Both had shipped; neither is visible in the generated-theme CSS the jsdom suites assert on (#5409).diff --git a/.changeset/timeinput-parses-compact-am-pm-values-correctly-oqsg.md b/.changeset/timeinput-parses-compact-am-pm-values-correctly-oqsg.mddeleted file mode 100644index 80fe893b76..0000000000--- a/.changeset/timeinput-parses-compact-am-pm-values-correctly-oqsg.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] TimeInput parses compact AM/PM values correctly (#4026)-@Kevinjohndiff --git a/.changeset/typeahead-tab-dismiss-on-keydown.md b/.changeset/typeahead-tab-dismiss-on-keydown.mddeleted file mode 100644index 0781d1bb29..0000000000--- a/.changeset/typeahead-tab-dismiss-on-keydown.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Typeahead: Tab out of the field now moves focus to the next control. The result list is dismissed on the Tab keydown rather than from the blur that press produces — hiding a top-layer popover during the focusout makes Chrome abandon the in-flight focus move and drop focus to `<body>`, so the press appeared to do nothing. Selector and MultiSelector already dismissed on the keydown (#5400).-@cixzhangdiff --git a/packages/build/CHANGELOG.md b/packages/build/CHANGELOG.mdindex dec7c9ee23..f43f90d0dd 100644--- a/packages/build/CHANGELOG.md+++ b/packages/build/CHANGELOG.md@@ -1,5 +1,9 @@# @xds/build+# 0.5.0++---+# 0.4.7---diff --git a/packages/build/package.json b/packages/build/package.jsonindex e62a0b6c82..f8b7b88343 100644--- a/packages/build/package.json+++ b/packages/build/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/build",- "version": "0.4.7",+ "version": "0.5.0","description": "Build plugins for XDS source builds — babel, PostCSS, and Vite integrations","author": "Meta Open Source","license": "MIT",diff --git a/packages/charts/package.json b/packages/charts/package.jsonindex 05adcd8725..e2e5284d42 100644--- a/packages/charts/package.json+++ b/packages/charts/package.json@@ -58,7 +58,7 @@},"peerDependencies": {"@stylexjs/stylex": ">=0.10.0",- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19.0.0","react-dom": ">=19.0.0"},diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.mdindex 5f10deacd7..992b481f38 100644--- a/packages/cli/CHANGELOG.md+++ b/packages/cli/CHANGELOG.md@@ -1,5 +1,69 @@# @xds/cli+# 0.5.0++#### Breaking Changes++- Banner: the collapse axis moves onto one `collapsible` prop, and content can opt out of collapsing (#5255)+ Banner inferred its disclosure from its content: any `children` got a chevron in the header and were hidden until it was pressed. There was no way to show content without a toggle — the case a banner most often wants, a list of the three fields that failed validation — and `defaultIsExpanded` was the only knob, with no controlled mode.++ The whole axis is now one `boolean | CollapsibleConfig` prop, following the boolean-or-config convention `SideNav.collapsible` set, and backed by the shared `useCollapsible` hook rather than Banner's own state:++ ```tsx+ <Banner status="error" title="3 fields need attention">…</Banner> // unchanged: collapsible, starts closed+ <Banner collapsible={false}>…</Banner> // new: always visible, no toggle+ <Banner collapsible={{defaultIsOpen: true}}>…</Banner> // replaces defaultIsExpanded+ <Banner collapsible={{isOpen, onOpenChange}}>…</Banner> // new: controlled+ ```++ **The default is unchanged** — a banner that never mentioned `defaultIsExpanded` behaves exactly as it did. The breaking part is the prop itself: `defaultIsExpanded` is removed in favour of the config, which is a type error at every JSX call site that names it.++ **Codemod:** `npx astryx upgrade --codemod banner-collapsible-content`++ It rewrites `defaultIsExpanded` to `collapsible={{defaultIsOpen: true}}` and drops `defaultIsExpanded={false}`, which is now the default. Banners that never set the prop are left alone.++ **One case the codemod and the compiler both miss: a spread.** `defaultIsExpanded` inside a props object is out of the transform's scope. A props object in a typed position still fails to compile — but an inferred one that is spread, `<Banner {...args} />`, does not, because TypeScript does not excess-property-check a spread. The prop then falls through to the DOM and the banner quietly starts collapsed. **Grep for `defaultIsExpanded` after running the codemod** and migrate any spread sites by hand.++#### New Components++- Promote `Stepper` and `Step` from the canary-only Lab package to Core. The stable package now ships their existing horizontal/vertical layouts, separated and on-track indicators, semantic status, density, and non-linear navigation, plus Core documentation and rendered examples. The default `aria-label` is now localized.+ Advancing one step now animates the connector. Every connector the four layouts draw — the separated bars and the on-track segments alike — grows its accent fill out of the segment's leading edge instead of swapping a background color, so moving forward reads as progress travelling the track. That one gesture is the only thing that animates: going back, jumping forward by more than one step, and mounting mid-flow all apply at once, as does any change under `prefers-reduced-motion`. Retreats are deliberately instant — run in reverse the same transition ends on a shrinking stub of accent, and a remnant still on the track reads as unfinished where the identical curve growing forward reads as arrived — and multi-step jumps are instant because a jump is a navigation rather than a progression, so sweeping a front across the crossed segments only makes the user sit out a journey they asked to skip. Where one span is drawn by several segments (the on-track layouts split a span between two steps, three when a content slot sits between them) the segments take abutting slices of the span's time and run linearly, so the fill reads as one line growing at a constant speed rather than pieces lighting in turn.++ Five visual fixes land with the promotion. Horizontal steps now divide the track evenly instead of sizing to their own labels, so every progress segment is the same width regardless of how long a step is named. Number indicators shrink from 20px to 16px to match the check, ring, and custom-icon indicators, so a step swapping its number for a check as it completes no longer nudges the label beside it. A step description now occupies a 16px box rather than a 24px one — it previously inherited the page's line box instead of applying its own leading, which opened an 8px gap under the label. A step's content slot now starts flush with the label above it at every density: the slot renders outside the density-padded label area, so it was hanging one pad short of it. And a vertical on-track step carrying content keeps its connector unbroken — the content renders below the row that draws the line, so the track used to split open around any step with content (#5201).++#### New Features++- AspectRatio: emit `ratio` as a class-level declaration instead of a hard inline style, so the ratio can be overridden responsively: StyleX consumers pass an `aspect-ratio` rule via `xstyle` (including under `@media`/`@container` conditions), and plain-CSS/Tailwind consumers override `aspect-ratio` from their own unlayered rules, which beat the `astryx-base` cascade layer regardless of specificity. The mixed-gallery template's hero now switches 3:1 to 3:2 when the grid stacks with a one-line override on a single element, replacing the duplicated hero markup the fixed inline ratio previously forced (#3883, closes #2798)+- CLI: `astryx theme targets` lists every component theming target — the `defineTheme` key, the class it paints, and the props and states it accepts — for one component or the whole system, with `--json` for lint and audit scripts. `astryx theme --help` now points at component overrides instead of reading as a build-tool menu. The listing and `theme build`'s override validation share one enumeration of the component docs, so neither can drift from the components (#5115).++#### Fixes++- neutral theme: darken the light-mode error red from `#e33f4a` to `#c9303a` so the filled `Badge variant="error"` label clears WCAG 2.1 AA. White on `#e33f4a` is 4.14:1 and the badge label is 12px/weight 500, so the 4.5:1 normal-text threshold applies rather than the 3:1 large-text allowance; `#c9303a` gives 5.29:1 while holding the hue (OKLCH H 21.9 -> 22.8, C 0.200 -> 0.189). StatusDot and the ProgressBar `--color-error` rebinding move with it — both are documented as tracking the badge fill so the dot and its badge read as one status language. Dark mode is untouched (dark text on `#ff705d`, 6.60:1). Adds `scripts/check-badge-contrast.test.mjs`, which resolves every theme's badge label/fill pair through `light-dark()`, `var()` indirection and alpha compositing, and holds all of them to 4.5:1 (#4446).+- Unified search and build now include components contributed by integrations, so a component registered through an integration is findable and buildable alongside the built-in set instead of silently missing from both (#5259).+- Table - Grouped page template: wrap the rows in `TableBody`+ The template rendered `<TableRow>` straight into `<Table>`, so the emitted DOM was `<table><tr>`. `<table>` cannot contain a row directly: the HTML parser inserts an implied `<tbody>` when it parses server-rendered markup and React does not when it renders on the client, so anyone who copied the template into an app as a server-rendered page inherited a hydration mismatch in their own app. Client-only the DOM is still invalid — nothing reparents the rows, so the table ends up with `<tr>` children and no `<tbody>` at all, and any CSS or query aimed at `tbody` silently misses.++ The rows now sit in `<TableBody>`, the same element the data-driven `data={...}` path renders, so styling, dividers, and column widths are unchanged (#5278).++#### Other Changes++- Public component theming vars are enumerable, and guarded against being documented but unsettable+ `collectThemingVars` joins `collectThemingTargets` as part of the one enumeration the theming surface is read from. Two guards ride on it: a documented public var no component reads compiles to a declaration that never applies, and a var the component writes inline outranks every cascade layer, so no theme can reach it. Both had shipped; neither is visible in the generated theme CSS the jsdom suites assert on (#5409).++#### Contributors++Thanks to everyone who contributed to this release:++- @AKnassa+- @andrskr+- @cixzhang+- @ernestt+- @freddymeta+- @jiunshinn+- @rubyycheung++---+# 0.4.7---diff --git a/packages/cli/assets/codemods/__tests__/registry.test.mjs b/packages/cli/assets/codemods/__tests__/registry.test.mjsindex c0f6ab9685..a8e233e966 100644--- a/packages/cli/assets/codemods/__tests__/registry.test.mjs+++ b/packages/cli/assets/codemods/__tests__/registry.test.mjs@@ -26,6 +26,7 @@ describe('registry', () => {'0.2.1','0.3.0','0.4.0',+ '0.5.0',]);});});diff --git a/packages/cli/assets/codemods/registry.mjs b/packages/cli/assets/codemods/registry.mjsindex 30df66616c..0609a32e7d 100644--- a/packages/cli/assets/codemods/registry.mjs+++ b/packages/cli/assets/codemods/registry.mjs@@ -27,6 +27,7 @@ const registry = new Map([['0.2.1', () => import('./transforms/v0.2.1/index.mjs')],['0.3.0', () => import('./transforms/v0.3.0/index.mjs')],['0.4.0', () => import('./transforms/v0.4.0/index.mjs')],+ ['0.5.0', () => import('./transforms/v0.5.0/index.mjs')],]);// Re-export from the shared utility so registry callers and other consumersdiff --git a/packages/cli/assets/codemods/transforms/next/index.mjs b/packages/cli/assets/codemods/transforms/next/index.mjsindex 731d127b13..2af3bdfcf0 100644--- a/packages/cli/assets/codemods/transforms/next/index.mjs+++ b/packages/cli/assets/codemods/transforms/next/index.mjs@@ -7,14 +7,4 @@* this file into the resolved version folder.*/-import bannerCollapsibleContent, {- meta as bannerCollapsibleContentMeta,-} from './banner-collapsible-content.mjs';--export default [- {- name: 'banner-collapsible-content',- transform: bannerCollapsibleContent,- meta: bannerCollapsibleContentMeta,- },-];+export default [];diff --git a/packages/cli/assets/codemods/transforms/next/__tests__/next-codemods.test.mjs b/packages/cli/assets/codemods/transforms/v0.5.0/__tests__/next-codemods.test.mjssimilarity index 100%rename from packages/cli/assets/codemods/transforms/next/__tests__/next-codemods.test.mjsrename to packages/cli/assets/codemods/transforms/v0.5.0/__tests__/next-codemods.test.mjsdiff --git a/packages/cli/assets/codemods/transforms/next/banner-collapsible-content.mjs b/packages/cli/assets/codemods/transforms/v0.5.0/banner-collapsible-content.mjssimilarity index 100%rename from packages/cli/assets/codemods/transforms/next/banner-collapsible-content.mjsrename to packages/cli/assets/codemods/transforms/v0.5.0/banner-collapsible-content.mjsdiff --git a/packages/cli/assets/codemods/transforms/v0.5.0/index.mjs b/packages/cli/assets/codemods/transforms/v0.5.0/index.mjsnew file mode 100644index 0000000000..731d127b13--- /dev/null+++ b/packages/cli/assets/codemods/transforms/v0.5.0/index.mjs@@ -0,0 +1,20 @@+// Copyright (c) Meta Platforms, Inc. and affiliates.++/**+ * @file next transform manifest+ *+ * Staged codemods for the next release. The Version Packages PR promotes+ * this file into the resolved version folder.+ */++import bannerCollapsibleContent, {+ meta as bannerCollapsibleContentMeta,+} from './banner-collapsible-content.mjs';++export default [+ {+ name: 'banner-collapsible-content',+ transform: bannerCollapsibleContent,+ meta: bannerCollapsibleContentMeta,+ },+];diff --git a/packages/cli/package.json b/packages/cli/package.jsonindex 84c1d71c18..d8f734be35 100644--- a/packages/cli/package.json+++ b/packages/cli/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/cli",- "version": "0.4.7",+ "version": "0.5.0","displayName": "CLI","description": "Scaffold projects, browse templates, generate themes, and get agent-ready docs from the command line.","author": "Meta Open Source",diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.mdindex a63ac9b6b5..2b093de791 100644--- a/packages/core/CHANGELOG.md+++ b/packages/core/CHANGELOG.md@@ -1,5 +1,164 @@# @xds/core+# 0.5.0++#### Breaking Changes++- Banner: the collapse axis moves onto one `collapsible` prop, and content can opt out of collapsing (#5255)+ Banner inferred its disclosure from its content: any `children` got a chevron in the header and were hidden until it was pressed. There was no way to show content without a toggle — the case a banner most often wants, a list of the three fields that failed validation — and `defaultIsExpanded` was the only knob, with no controlled mode.++ The whole axis is now one `boolean | CollapsibleConfig` prop, following the boolean-or-config convention `SideNav.collapsible` set, and backed by the shared `useCollapsible` hook rather than Banner's own state:++ ```tsx+ <Banner status="error" title="3 fields need attention">…</Banner> // unchanged: collapsible, starts closed+ <Banner collapsible={false}>…</Banner> // new: always visible, no toggle+ <Banner collapsible={{defaultIsOpen: true}}>…</Banner> // replaces defaultIsExpanded+ <Banner collapsible={{isOpen, onOpenChange}}>…</Banner> // new: controlled+ ```++ **The default is unchanged** — a banner that never mentioned `defaultIsExpanded` behaves exactly as it did. The breaking part is the prop itself: `defaultIsExpanded` is removed in favour of the config, which is a type error at every JSX call site that names it.++ **Codemod:** `npx astryx upgrade --codemod banner-collapsible-content`++ It rewrites `defaultIsExpanded` to `collapsible={{defaultIsOpen: true}}` and drops `defaultIsExpanded={false}`, which is now the default. Banners that never set the prop are left alone.++ **One case the codemod and the compiler both miss: a spread.** `defaultIsExpanded` inside a props object is out of the transform's scope. A props object in a typed position still fails to compile — but an inferred one that is spread, `<Banner {...args} />`, does not, because TypeScript does not excess-property-check a spread. The prop then falls through to the DOM and the banner quietly starts collapsed. **Grep for `defaultIsExpanded` after running the codemod** and migrate any spread sites by hand.++- Overlays share one dismissal stack, so a single Escape dismisses exactly one layer. Every overlay used to own its own Escape listener, which meant one press could close a popover _and_ the Dialog hosting it, or a modal _and_ the modal it was opened from. `useLayerDismissal` replaces that with a single stack: the stack owns one listener, routes each press to the top-most layer, and suppresses the browser's own close-watcher so nothing dismisses twice. A layer declares what it does with a press via `escapeBehavior` — `close` (default) or `block`, for a `required` Dialog that must swallow the press without closing so nothing behind it dismisses either. Fixes a Tooltip inside a Dialog closing the Dialog rather than the tip, and a HoverCard trigger swallowing Escape whenever it merely had focus. Dismissals the browser starts on its own — the Android back gesture, the platform close watcher — still close a Dialog, and follow the same top-most rule. An Escape that cancels an in-progress IME composition dismisses nothing: the stack claims that press so the browser raises no close request of its own, and a close request that arrives mid-composition anyway is declined, so a CJK user backing out of a half-formed character no longer loses the layer and everything typed into it. One behavior change worth knowing about if you listen for Escape yourself: the stack claims a press with `preventDefault()` but deliberately leaves propagation alone, so a `keydown` listener on `window` now sees an Escape that a focus-trapped layer used to stop — with `defaultPrevented` already `true`, which is how to tell the stack has acted on it. Top-most is resolved from React-tree nesting (which survives portals) rather than DOM containment alone. A layer's place in that order is keyed to the layer's identity rather than to each registration, so a prop change that re-registers it — a Dialog whose `purpose` flips while it is open — never promotes it above the layers opened over it. Controlled layers follow their control state: a controlled `Tooltip` or `HoverCard` stays on the stack and takes the press like any other layer, but answers it by calling `onOpenChange(false)` rather than hiding itself — whether it actually closes is the caller's update to make, exactly as it has always been for `Dialog` (#4881).++#### New Components++- Allow MultiSelector count labels to be customized (#4032)+- MultiSelector: rename the unreleased `formatTriggerCount` prop to `formatValue` and widen it to the whole trigger line. It now receives the selected items (`{value, label}[]`, count available as `.length`) and formats the trigger for `triggerDisplay="count"` and `"labels"`; `"badges"` renders elements, so it is not used there. `formatValue` matches NumberInput and Slider, so the same idea has one name across the system. Defaults are unchanged when the prop is absent (#5377).+- Promote `Stepper` and `Step` from the canary-only Lab package to Core. The stable package now ships their existing horizontal/vertical layouts, separated and on-track indicators, semantic status, density, and non-linear navigation, plus Core documentation and rendered examples. The default `aria-label` is now localized.+ Advancing one step now animates the connector. Every connector the four layouts draw — the separated bars and the on-track segments alike — grows its accent fill out of the segment's leading edge instead of swapping a background color, so moving forward reads as progress travelling the track. That one gesture is the only thing that animates: going back, jumping forward by more than one step, and mounting mid-flow all apply at once, as does any change under `prefers-reduced-motion`. Retreats are deliberately instant — run in reverse the same transition ends on a shrinking stub of accent, and a remnant still on the track reads as unfinished where the identical curve growing forward reads as arrived — and multi-step jumps are instant because a jump is a navigation rather than a progression, so sweeping a front across the crossed segments only makes the user sit out a journey they asked to skip. Where one span is drawn by several segments (the on-track layouts split a span between two steps, three when a content slot sits between them) the segments take abutting slices of the span's time and run linearly, so the fill reads as one line growing at a constant speed rather than pieces lighting in turn.++ Five visual fixes land with the promotion. Horizontal steps now divide the track evenly instead of sizing to their own labels, so every progress segment is the same width regardless of how long a step is named. Number indicators shrink from 20px to 16px to match the check, ring, and custom-icon indicators, so a step swapping its number for a check as it completes no longer nudges the label beside it. A step description now occupies a 16px box rather than a 24px one — it previously inherited the page's line box instead of applying its own leading, which opened an 8px gap under the label. A step's content slot now starts flush with the label above it at every density: the slot renders outside the density-padded label area, so it was hanging one pad short of it. And a vertical on-track step carrying content keeps its connector unbroken — the content renders below the row that draws the line, so the track used to split open around any step with content (#5201).++#### New Features++- AspectRatio: emit `ratio` as a class-level declaration instead of a hard inline style, so the ratio can be overridden responsively: StyleX consumers pass an `aspect-ratio` rule via `xstyle` (including under `@media`/`@container` conditions), and plain-CSS/Tailwind consumers override `aspect-ratio` from their own unlayered rules, which beat the `astryx-base` cascade layer regardless of specificity. The mixed-gallery template's hero now switches 3:1 to 3:2 when the grid stacks with a one-line override on a single element, replacing the duplicated hero markup the fixed inline ratio previously forced (#3883, closes #2798)+- ChatMessageList: add an `align` prop for top-aligned message lists+ (#3933, closes #2572).+- DateTimeInput: new `timeOptionInterval` prop adds a dropdown of preset times to the time field, at a cadence of `5 | 10 | 15 | 30 | 60` minutes (`60` gives the 12 AM - 11 PM list). The field becomes an APG combobox over a `listbox`: click or Alt+ArrowDown opens it, ArrowUp/ArrowDown move the active option, Enter picks, Escape closes, and typing moves the highlight to the closest option without filtering the list. `min`/`max` trim the options on the boundary date. Style the popup through the `date-time-input-time-listbox` and `date-time-input-time-option` theme targets.+ Opt-in and additive: with `timeOptionInterval` omitted the time field keeps exactly its current behavior and gains no combobox semantics, so existing `getByRole('combobox')` queries still resolve to the date input. With the list closed the arrow keys keep stepping by `timeIncrement` (#4837).+- Markdown: opt-in source ranges on parsed blocks+ `parseMarkdown(source, {sourceRanges: true})` now gives every top-level block a `range` — `{start, end}`, the character offsets it occupies in the source that was passed in, with `end` exclusive — so a consumer holding that source can `source.slice(range.start, range.end)` for a block instead of reconstructing it from the node (or from the rendered DOM). Reconstruction is lossy in ways slicing is not: escapes, the exact emphasis and fence characters, heading depth beyond the clamp, and alignment all survive a slice unchanged.++ Off by default and absent unless asked for, so no existing node, snapshot or comparison changes.++ Two things the offsets get right that a naive implementation does not: link reference definitions are stripped before the block loop runs, and the ranges are reported against the string the caller passed rather than the stripped text; and `parseMarkdownIncremental` parses slices, so blocks report absolute offsets into the whole document as it streams — including a list whose halves arrived in separate chunks and were merged.++ A range covers a block's own lines verbatim, so slicing it and parsing the result gives the same node back.++ Blocks nested inside a list item or a blockquote carry no range: their children are parsed from text the parser reassembled with markers and `>` prefixes removed, so an offset into it would not address the document (#5290).++- Table: let `useTableSelection` opt out of the checked-row accent wash+ The selection plugin paints checked rows by writing `backgroundColor` straight onto each `<tr>` from its row ref callback. An inline style outranks anything StyleX can layer on, so a product that wanted the row background for its own meaning had no way to reclaim it short of forking the plugin.++ `hasRowHighlight` turns the wash off. It defaults to `true`, so existing tables are untouched. Only the background is dropped — `aria-selected` is still set and removed exactly as before, since that is the half of the state screen readers read.++ ````tsx+ useTableSelection({...config, hasRowHighlight: false});+ ``` (#5310)+ ````++- TabList: a strip that switches panels in place can now say so with `role="tablist"`, and it speaks the WAI-ARIA tabs pattern — `role="tablist"` on the strip, `role="tab"` and `aria-selected` on the tabs, and `aria-controls` pointing at the panel each tab opens, from a new `panelId` prop on `Tab`. There is no new prop for the switch: `TabList` declares `role?: AriaRole` and reads it, the way `LayoutHeader`, `LayoutContent` and `LayoutPanel` already declare and document theirs. The keyboard behaviour the pattern asks for was already there: arrows move between tabs, Tab leaves the strip. Under the asserted role the strip takes only the horizontal arrows, leaving ArrowUp and ArrowDown to scroll the page.+ `role` already reached the DOM through `{...restProps}`, so a caller could pass `role="tablist"` and get a tablist whose children were still `<button>`s with `aria-current` — invalid markup, no `aria-selected`, and no warning. Reading the role turns that silent breakage into the correct behaviour; declaring it is what puts it in the type, the prop table and the docs.++ **Nothing changes for a caller who passes no `role`**: the strip is the `<nav>` landmark with `aria-current` it has always been. Any other role still passes through to the element untouched.++ Two development warnings come with the asserted role, and only with it. A tab with an `href` is a false statement inside a tablist, so the `href` is ignored and the warning says so. And a tab that controls nothing gets asked for a `panelId` — either that or an `aria-controls` you wrote yourself satisfies it, and a hand-written one is never overwritten. `aria-controls` is emitted only when you supply the id: pointing at a panel that does not exist is an invalid attribute value, which is worse than saying nothing. A menu or any other non-tab in a tablist strip is invalid markup, and warns too. The mirror case warns as well: a `panelId` on a strip that is not a tablist has no panel relationship to state, and is dropped (#5349).++- TabList: a strip narrower than its tabs now scrolls instead of spilling out of its container. Every tab stays a tab — nothing is hidden behind a menu — the edges fade to show there is more, and pointers that can hover get arrow affordances; keyboard and screen-reader users reach every tab with the arrow keys, which scrolls the focused tab into view. The selected tab is scrolled back into view whenever it would be out of sight, including on mount and when the host changes `value` itself. The new `overflow` prop takes `'auto'` (the default, which today always scrolls), `'scroll'`, or `'visible'` to keep the old spill-out layout. Built on the existing `useScrollOverflow` hook, so there is no new measurement machinery and no `Carousel` in the tab strip — the documented Carousel recipe, which announced every tab as "slide N of M", is no longer needed and the stories now use the built-in behaviour.+ If you followed that recipe, nothing breaks: a `Carousel` still wrapping the tabs renders and behaves exactly as it did before, because its own scroll container absorbs the strip's, which then never overflows. Removing it is worth doing anyway — it drops the `region`/"slide N of M" wrapping from the accessibility tree, and the strip's own scrolling brings a tab that straddles the edge fully into view on focus, which the carousel does not (#5348).++#### Fixes++- useTablePagination: with `position='both'` the two pagination `<nav>` landmarks now get distinct accessible names — "{label} (top)" above the table and "{label} (bottom)" below it (axe landmark-unique). Consumer-supplied `label` values are interpolated into both names; single-position labels are unchanged (#4692).+- Table useTableRowExpansion: the chevron gutter's column header now carries a visually hidden localized name ("Row expansion", key `@astryx.tableRowExpansion.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank (#5383).+- Table useTableRowStatus: the status gutter's column header now carries a visually hidden localized name ("Row status", key `@astryx.table.rowStatus.columnHeader`) instead of an empty `<th>` (axe empty-table-header, WCAG 1.3.1 best practice). The gutter stays visually blank (#4693).+- BottomSheet: a standalone sheet no longer dismisses when a CJK user presses Escape to cancel an in-progress IME composition. The browser fires that keydown before `compositionend`, so an Escape handler reading a bare `event.key` misread the composition cancel as a dismissal command and closed the sheet — losing whatever had been typed into a `purpose="form"` field inside it. The handler now early-returns on `isImeKeyEvent`, the same guard `Dialog` and `BottomSheetSwitcher` already carry, and claims the key first so the browser raises no close request of its own (#5322).+- `Breadcrumbs` marks the current item with semibold weight, not colour alone. The current crumb was distinguished only by `--color-text-primary` against its siblings' `--color-text-secondary`, which fails WCAG 1.4.1 (use of colour) and leaves the current position invisible to anyone who cannot separate the two tones (#4605, closes #4421).+- ButtonGroup: arrow keys pressed inside a member's open menu stay with that menu. A DropdownMenu renders its menu inline inside the group, so ArrowLeft and ArrowRight used to bubble to the group and move focus onto a sibling button while the menu was still open. The group's `elevation` is also reflected as `data-elevation` now, so a theme can target it (#5355).+- ButtonGroup is a single tab stop. Its members now share one roving tab stop instead of taking one each, so a three-button group costs one Tab press rather than three. Arrow keys move between members along the orientation (flipped in RTL), Home/End jump to the ends, focus wraps, and disabled members are skipped. Two consequences worth knowing: a keyboard script or test that tabbed through a group member by member must use arrow keys now, and a member rendered as a link (`href`) joins the arrow order for the first time. (#5389)+- Calendar (and DateInput, DateRangeInput, DateTimeInput) now opens on a month inside the min/max window instead of on today+ With no `focusDate` and no selected value, the calendar opened on today's month even when `min`/`max` excluded it — a 2019 audit window or a booking window that opens next spring rendered a grid where every day was disabled, and the only way in was clicking the prev/next arrows once per month.++ The initial month is now today clamped into the window: today when it is inside, otherwise whichever bound is nearest. An explicit `focusDate` or a selected value still wins, so nothing changes for callers that already say where to look. With `numberOfMonths={2}` a past window lands `max` in the right-hand pane, so neither pane is entirely out of bounds (#5306).++- DateInput: clearing on touch no longer jumps the page to the top+ On the touch surface, tapping the clear (✕) threw the user to the top of the page. Clearing unmounts the clear button, and `handleClear` focused the field in that same task — on iOS Safari, focusing an element as the focused button is removed scrolls the whole document to 0. The focus handoff is now deferred past the unmount, which keeps the page where it was and still returns focus to the field.++ Measured on the iOS 26 simulator against the live docsite (DateInput — Clearable, page at scrollY 2055): synchronous focus → 0, deferred focus → 2055. `preventScroll` alone does not fix it; it is kept for the ordinary scroll-into-view nudge, which is unwanted for the same reason (#5350).++- Clamp standard Dialog width to dynamic viewport space with token gutters, add safe-area/fullscreen sizing and fade-only fullscreen motion updates, add opt-in adaptive Dialog/BottomSheet recipes, and add explicit presentation comparison stories (#5352).+- DropdownMenu: move the `dropdown-menu-indicator-icon` theme target onto the Icon element itself so a theme can restyle the submenu chevron's size and color directly.+ The loading branch no longer carries the target — its `Spinner` has its own `astryx-spinner` target, matching Selector, MultiSelector and ComplexSelector (#4743).+- Chat: a token in a message bubble now sits on the line the way it does in the composer. `ChatTokenizedText` wraps each token in the same `inline-flex` / `vertical-align: middle` box `ChatComposerInput` uses, so a chip stops lifting off the text the moment the message is sent. Follows #5324, which fixed the composer half (#5402).+- Chat: composer tokens no longer sit above surrounding text — `vertical-align` changed from `baseline` to `middle`, and `ChatComposerTokenElement` now uses a StyleX class instead of an inline style so consumers can override alignment without `!important` (#5324).+- useFocusTrap: Tab is only cancelled when focus is actually inside the trapped container. An open layer whose focus legitimately sits outside it — a listbox popup anchored to its own input, as in DateTimeInput, Typeahead, Selector and MultiSelector — no longer swallows Tab for the whole page, so keyboard users move to the next control on the first press. A trapped surface with no tabbable controls and focus on a `tabIndex={-1}` panel still keeps Tab inside it (#5397).+- `mod` hotkeys and `Kbd` resolve to Cmd on macOS again when client hints report a blank platform+ `useHotkeys` and `Kbd` both prefer `navigator.userAgentData.platform` and fall back to `navigator.platform`, but guarded the preference with `'platform' in uaData`, which is true whenever the key exists at all. A build reporting `platform: ''` therefore committed to the client-hints branch and got `false` without ever reaching the fallback, so on macOS every `mod` combo listened for Ctrl and every `<Kbd>` drew Ctrl. Electron and other embedders that rewrite the app's user-agent identity ship exactly that. A blank platform is now treated as unknown and falls through (#5325).+- Markdown streaming: `parseMarkdownIncremental` no longer throws away its settled blocks while a code fence is open, or when a chunk happens to end on a newline — both re-parsed the whole document, so a long streamed response got slower the longer it grew. Blocks rebuilt across a streamed 500-paragraph document: 126,756 → 1,869 (#5407).+- Migrate core components from inline mergeRefs calls to stable useMergedRefs callbacks (#5267).+- PowerSearch now applies `menuWidth` to the initial field and search menu without letting it shrink below the input width. Value menus shown after selecting a field are unchanged. (#5237)+- PowerSearch: `maxOperatorMenuItems` now caps suggestions in string, string-list, and entity-list value typeaheads, including values inside nested filters (#5242).+- PowerSearch: the edit popover now fits narrow viewports — its 400px minimum width yields to the screen width, and the filter row wraps instead of overflowing when long translated operator labels don't fit. An editor anchored near the screen edge now stays on its own side at the width available there, wrapping internally, instead of flipping across the anchor to keep 400px (#4768).+- PowerSearch now groups fields in the browsing menu using each field's `group` value. Ungrouped fields appear first, while typed search results remain flat. (#5235)+- PowerSearch now shows up to 1,000 configured fields when the search box is empty, instead of stopping at 10. Typed searches still show 10 ranked results by default; use `maxSearchResults` to change only that limit. (#5233)+- `Selector` and `MultiSelector` no longer expose their `{type: 'divider'}` separators to assistive technology. `role="listbox"` only permits `option`/`group` children, but the divider previously rendered `role="separator"` as a direct child of the listbox (axe `aria-required-children`, impact critical). The divider is decorative and carries no information the options don't, so it's now hidden from the accessibility tree via `aria-hidden`, matching the pattern already used for section headings (#5107).+- Keep merged refs stable across Avatar, Button, SideNav, TabList, and TopNav (#5429).+- Add useMergedRefs and keep Text and Heading refs stable across rerenders (#5266).+- Table: a plugin can suppress a body cell's content, and grouped rows use it to keep synthetic group headers out of your cell renderers (#5363)+ `useTableGroupedRows` injects section-header rows into the flattened data, and `BaseTable` evaluates every column's `renderCell` against every row. A renderer that keys a lookup off a field — `STATUS_META[item.status].dot` — was therefore handed a row that is not yours and threw, blanking the page the moment grouping was switched on. The header Proxy answering unknown fields with `''` only ever rescued a renderer that _prints_ a field; `''` fails a lookup exactly as `undefined` does.++ `BodyCellRenderProps` gains `isContentSuppressed?: boolean`. A plugin sets it in `transformBodyCell` for a row whose cells it is about to replace wholesale in `transformBodyRow`, and the table renders that cell empty without calling the column's renderer or the default one. It is decided per cell at render time against the final column list, so it also covers columns other plugins contributed — whatever order the plugins were listed in.++- TimeInput parses compact AM/PM values correctly (#4026)+- Typeahead: Tab out of the field now moves focus to the next control. The result list is dismissed on the Tab keydown rather than from the blur that press produces — hiding a top-layer popover during the focusout makes Chrome abandon the in-flight focus move and drop focus to `<body>`, so the press appeared to do nothing. Selector and MultiSelector already dismissed on the keydown (#5400).++#### Documentation++- document missing API contract props across Button, Toast, ContextMenu, MoreMenu, Selector, Link, and Dialog (#4315, part of #4163)+- document missing props across complex components (MultiSelector, Tokenizer, PowerSearch, Typeahead, Layout, DropdownMenu, HoverCard, Tooltip, Link, Lightbox) (#4316, part of #4163)+- document the missing components prop on Markdown (#4319, part of #4163)+- document labelID and isGroupLabel props in Field (#4320, part of #4163)+- document missing props across structural components (CodeBlock, Toolbar) (#4317, part of #4163)+- Table: document the section components children mode requires+ Children mode stopped wrapping children in a `<tbody>` in #2098, but the docs still described the contract from before it. The `children` prop read "render TableRow/TableCell directly"; `TableRow`'s own `@example` showed a row sitting in `<Table>` with no section around it; and `TableHeader`, `TableBody`, and `TableFooter` — public exports since that change — had no docs at all and were missing from `Table`'s component list. A reader following the component's own documentation wrote `<table><tr>`, which is invalid HTML and mismatches on hydration.++ The three section components are now documented, listed on `Table`, and named in the `children` prop description, in a best practice, and in `TableRow`'s example (#5278).++#### Other Changes++- `align?: 'top' | 'bottom'` (default `'bottom'`). `'bottom'` keeps the+ existing behavior: a flex spacer fills free space so a short conversation sits just above the composer. `'top'` omits the spacer so messages start at the top and grow downward — better for log-style or document-style lists.+- Only changes the resting position of a non-full list. Once messages overflow+ the container the spacer collapses to zero in both modes, so ChatLayout auto-scroll-to-bottom behavior is unchanged.+- Spinner: the ring is drawn in SVG instead of `<canvas>`. The arc and track take their colours from the cascade (`currentColor` for `shade="inherit"`), so nothing resolves a colour in JS: a colour change after mount now repaints the ring instead of leaving it stale until it remounts, and mounting spinners no longer costs a `getComputedStyle` each. Rings are pinned to the document timeline's origin, so spinners mounted at different times turn in phase. No API, geometry or theme-target change (#5408).++#### Contributors++Thanks to everyone who contributed to this release:++- @AKnassa+- @Astro-Han+- @athz+- @cixzhang+- @ernestt+- @freddymeta+- @gonzoblasco+- @HelloOjasMutreja+- @imdreamrunner+- @jiunshinn+- @Kevinjohn+- @lexs+- @nynexman4464+- @rubyycheung++---+# 0.4.7#### Fixesdiff --git a/packages/core/package.json b/packages/core/package.jsonindex d565ee1588..8513cafc67 100644--- a/packages/core/package.json+++ b/packages/core/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/core",- "version": "0.4.7",+ "version": "0.5.0","displayName": "Astryx Core","description": "The component library. Accessible, themeable React components with built-in spacing, dark mode, and StyleX styling.","author": "Meta Open Source",diff --git a/packages/lab/package.json b/packages/lab/package.jsonindex 4c3148e82f..3f871389ed 100644--- a/packages/lab/package.json+++ b/packages/lab/package.json@@ -58,7 +58,7 @@},"peerDependencies": {"@stylexjs/stylex": ">=0.10.0",- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19.0.0","react-dom": ">=19.0.0"},diff --git a/packages/richtext/package.json b/packages/richtext/package.jsonindex 0f386420ce..acea8a8e68 100644--- a/packages/richtext/package.json+++ b/packages/richtext/package.json@@ -60,7 +60,7 @@},"peerDependencies": {"@stylexjs/stylex": ">=0.10.0",- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19.0.0","react-dom": ">=19.0.0","lexical": "^0.46.0",diff --git a/packages/themes/butter/CHANGELOG.md b/packages/themes/butter/CHANGELOG.mdindex 5ad624f119..615edebdf5 100644--- a/packages/themes/butter/CHANGELOG.md+++ b/packages/themes/butter/CHANGELOG.md@@ -1,5 +1,9 @@# @xds/theme-butter+# 0.5.0++---+# 0.4.7---diff --git a/packages/themes/butter/package.json b/packages/themes/butter/package.jsonindex 6de325aeca..362957acb5 100644--- a/packages/themes/butter/package.json+++ b/packages/themes/butter/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/theme-butter",- "version": "0.4.7",+ "version": "0.5.0","displayName": "Butter Theme","private": false,"description": "Warm, creamy yellows with a friendly blue accent. Playful enough for consumer surfaces, soft enough to stay readable.",@@ -52,11 +52,11 @@"lucide-react": "^1.18.0"},"peerDependencies": {- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19"},"devDependencies": {- "@astryxdesign/cli": "0.4.7",+ "@astryxdesign/cli": "0.5.0","rimraf": "^6.0.1"},"module": "./dist/source.mjs"diff --git a/packages/themes/chocolate/CHANGELOG.md b/packages/themes/chocolate/CHANGELOG.mdindex d02cfc73c6..08f8b5a2af 100644--- a/packages/themes/chocolate/CHANGELOG.md+++ b/packages/themes/chocolate/CHANGELOG.md@@ -1,5 +1,9 @@# @xds/theme-chocolate+# 0.5.0++---+# 0.4.7---diff --git a/packages/themes/chocolate/package.json b/packages/themes/chocolate/package.jsonindex 2856301e47..1883e30f89 100644--- a/packages/themes/chocolate/package.json+++ b/packages/themes/chocolate/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/theme-chocolate",- "version": "0.4.7",+ "version": "0.5.0","displayName": "Chocolate Theme","private": false,"description": "Warm chocolate theme for Astryx — rich brown palette with Fraunces headings, Albert Sans body, and Lucide icons",@@ -52,11 +52,11 @@"lucide-react": "^1.18.0"},"peerDependencies": {- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19"},"devDependencies": {- "@astryxdesign/cli": "0.4.7",+ "@astryxdesign/cli": "0.5.0","rimraf": "^6.0.1"},"module": "./dist/source.mjs"diff --git a/packages/themes/gothic/CHANGELOG.md b/packages/themes/gothic/CHANGELOG.mdindex 06a166b2bb..a034c3918e 100644--- a/packages/themes/gothic/CHANGELOG.md+++ b/packages/themes/gothic/CHANGELOG.md@@ -1,5 +1,9 @@# @xds/theme-gothic+# 0.5.0++---+# 0.4.7---diff --git a/packages/themes/gothic/package.json b/packages/themes/gothic/package.jsonindex bf1b3f061b..6740907677 100644--- a/packages/themes/gothic/package.json+++ b/packages/themes/gothic/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/theme-gothic",- "version": "0.4.7",+ "version": "0.5.0","displayName": "Gothic Theme","private": false,"description": "Deep blue-grays and a signature display serif. Dramatic and editorial, for surfaces that want to be remembered.",@@ -52,11 +52,11 @@"lucide-react": "^1.18.0"},"peerDependencies": {- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19"},"devDependencies": {- "@astryxdesign/cli": "0.4.7",+ "@astryxdesign/cli": "0.5.0","rimraf": "^6.0.1"},"module": "./dist/source.mjs"diff --git a/packages/themes/matcha/CHANGELOG.md b/packages/themes/matcha/CHANGELOG.mdindex 23fedab993..42647d4a2e 100644--- a/packages/themes/matcha/CHANGELOG.md+++ b/packages/themes/matcha/CHANGELOG.md@@ -1,5 +1,9 @@# @xds/theme-matcha+# 0.5.0++---+# 0.4.7---diff --git a/packages/themes/matcha/package.json b/packages/themes/matcha/package.jsonindex ced2b419ba..f21834bbab 100644--- a/packages/themes/matcha/package.json+++ b/packages/themes/matcha/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/theme-matcha",- "version": "0.4.7",+ "version": "0.5.0","private": false,"description": "Earthy greens with a calm, organic feel. Naturalistic and grounded, great for wellness or content-first apps.","author": "Meta Open Source",@@ -51,11 +51,11 @@"lucide-react": "^1.18.0"},"peerDependencies": {- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19"},"devDependencies": {- "@astryxdesign/cli": "0.4.7",+ "@astryxdesign/cli": "0.5.0","rimraf": "^6.0.1"},"module": "./dist/source.mjs"diff --git a/packages/themes/neutral/CHANGELOG.md b/packages/themes/neutral/CHANGELOG.mdindex 79e4fac34d..94ea930855 100644--- a/packages/themes/neutral/CHANGELOG.md+++ b/packages/themes/neutral/CHANGELOG.md@@ -1,5 +1,19 @@# @xds/theme-neutral+# 0.5.0++#### Fixes++- neutral theme: darken the light-mode error red from `#e33f4a` to `#c9303a` so the filled `Badge variant="error"` label clears WCAG 2.1 AA. White on `#e33f4a` is 4.14:1 and the badge label is 12px/weight 500, so the 4.5:1 normal-text threshold applies rather than the 3:1 large-text allowance; `#c9303a` gives 5.29:1 while holding the hue (OKLCH H 21.9 -> 22.8, C 0.200 -> 0.189). StatusDot and the ProgressBar `--color-error` rebinding move with it — both are documented as tracking the badge fill so the dot and its badge read as one status language. Dark mode is untouched (dark text on `#ff705d`, 6.60:1). Adds `scripts/check-badge-contrast.test.mjs`, which resolves every theme's badge label/fill pair through `light-dark()`, `var()` indirection and alpha compositing, and holds all of them to 4.5:1 (#4446).++#### Contributors++Thanks to everyone who contributed to this release:++- @AKnassa++---+# 0.4.7---diff --git a/packages/themes/neutral/package.json b/packages/themes/neutral/package.jsonindex f04dd45e70..842d83856c 100644--- a/packages/themes/neutral/package.json+++ b/packages/themes/neutral/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/theme-neutral",- "version": "0.4.7",+ "version": "0.5.0","displayName": "Neutral Theme","private": false,"description": "Restrained warm grays. Minimal and quiet, so the content stays the focus.",@@ -52,11 +52,11 @@"lucide-react": "^1.18.0"},"peerDependencies": {- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19"},"devDependencies": {- "@astryxdesign/cli": "0.4.7",+ "@astryxdesign/cli": "0.5.0","rimraf": "^6.0.1"},"module": "./dist/source.mjs"diff --git a/packages/themes/stone/CHANGELOG.md b/packages/themes/stone/CHANGELOG.mdindex 6b0586cd70..5e63548ffa 100644--- a/packages/themes/stone/CHANGELOG.md+++ b/packages/themes/stone/CHANGELOG.md@@ -1,5 +1,9 @@# @xds/theme-stone+# 0.5.0++---+# 0.4.7---diff --git a/packages/themes/stone/package.json b/packages/themes/stone/package.jsonindex 7e9d7b8fad..d2597f041a 100644--- a/packages/themes/stone/package.json+++ b/packages/themes/stone/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/theme-stone",- "version": "0.4.7",+ "version": "0.5.0","displayName": "Stone Theme","private": false,"description": "Warm stone and slate, earthy and understated, with just enough character to feel handcrafted.",@@ -52,11 +52,11 @@"lucide-react": "^1.18.0"},"peerDependencies": {- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19"},"devDependencies": {- "@astryxdesign/cli": "0.4.7",+ "@astryxdesign/cli": "0.5.0","rimraf": "^6.0.1"},"module": "./dist/source.mjs"diff --git a/packages/themes/y2k/CHANGELOG.md b/packages/themes/y2k/CHANGELOG.mdindex db1ed4eff1..ae48d4a226 100644--- a/packages/themes/y2k/CHANGELOG.md+++ b/packages/themes/y2k/CHANGELOG.md@@ -1,5 +1,9 @@# @xds/theme-y2k+# 0.5.0++---+# 0.4.7---diff --git a/packages/themes/y2k/package.json b/packages/themes/y2k/package.jsonindex 2816e0329a..1576e7667f 100644--- a/packages/themes/y2k/package.json+++ b/packages/themes/y2k/package.json@@ -1,6 +1,6 @@{"name": "@astryxdesign/theme-y2k",- "version": "0.4.7",+ "version": "0.5.0","displayName": "Y2K Theme","private": false,"description": "Hot pinks, lime greens, and Poppins. Bubbly, playful, and unmistakably retro.",@@ -52,11 +52,11 @@"lucide-react": "^1.18.0"},"peerDependencies": {- "@astryxdesign/core": "0.4.7",+ "@astryxdesign/core": "0.5.0","react": ">=19"},"devDependencies": {- "@astryxdesign/cli": "0.4.7",+ "@astryxdesign/cli": "0.5.0","rimraf": "^6.0.1"},"module": "./dist/source.mjs"diff --git a/pnpm-lock.yaml b/pnpm-lock.yamlindex 188fdac5c1..0a530b31a4 100644--- a/pnpm-lock.yaml+++ b/pnpm-lock.yaml@@ -587,7 +587,7 @@ importers:packages/charts:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../core'@stylexjs/stylex':specifier: '>=0.10.0'@@ -701,7 +701,7 @@ importers:packages/lab:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../core'@stylexjs/stylex':specifier: '>=0.10.0'@@ -741,7 +741,7 @@ importers:packages/richtext:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../core'@stylexjs/stylex':specifier: '>=0.10.0'@@ -796,7 +796,7 @@ importers:packages/themes/butter:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../corelucide-react:specifier: ^1.18.0@@ -806,7 +806,7 @@ importers:version: 19.2.7devDependencies:'@astryxdesign/cli':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../clirimraf:specifier: ^6.0.1@@ -815,7 +815,7 @@ importers:packages/themes/chocolate:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../corelucide-react:specifier: ^1.18.0@@ -825,7 +825,7 @@ importers:version: 19.2.7devDependencies:'@astryxdesign/cli':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../clirimraf:specifier: ^6.0.1@@ -834,7 +834,7 @@ importers:packages/themes/gothic:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../corelucide-react:specifier: ^1.18.0@@ -844,7 +844,7 @@ importers:version: 19.2.7devDependencies:'@astryxdesign/cli':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../clirimraf:specifier: ^6.0.1@@ -853,7 +853,7 @@ importers:packages/themes/matcha:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../corelucide-react:specifier: ^1.18.0@@ -863,7 +863,7 @@ importers:version: 19.2.7devDependencies:'@astryxdesign/cli':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../clirimraf:specifier: ^6.0.1@@ -872,7 +872,7 @@ importers:packages/themes/neutral:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../corelucide-react:specifier: ^1.18.0@@ -882,7 +882,7 @@ importers:version: 19.2.7devDependencies:'@astryxdesign/cli':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../clirimraf:specifier: ^6.0.1@@ -891,7 +891,7 @@ importers:packages/themes/stone:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../corelucide-react:specifier: ^1.18.0@@ -901,7 +901,7 @@ importers:version: 19.2.7devDependencies:'@astryxdesign/cli':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../clirimraf:specifier: ^6.0.1@@ -910,7 +910,7 @@ importers:packages/themes/y2k:dependencies:'@astryxdesign/core':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../corelucide-react:specifier: ^1.18.0@@ -920,7 +920,7 @@ importers:version: 19.2.7devDependencies:'@astryxdesign/cli':- specifier: 0.4.7+ specifier: 0.5.0version: link:../../clirimraf:specifier: ^6.0.1