An open source design system that's fully customizable and agent ready
TypeScript
chore: merge v0.7.5 release outputs to main (#9086)
Cindy Zhang3ec1c8beba48
diff --git a/.changeset/action-group-tracker.md b/.changeset/action-group-tracker.mddeleted file mode 100644index a3f9633a00..0000000000--- a/.changeset/action-group-tracker.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[internal] One tracker for a held finger across a group of targets (an alert's or an action sheet's actions, a menu's rows, a segmented control's segments, a page control's dots): it reads the targets' rects once, resolves the finger against them (or by the owner's rule), paints or reports the highlight, and runs the target through its own click at the lift. Nothing a consumer sees changes.--@vjeuxdiff --git a/.changeset/animated-layout-adopters.md b/.changeset/animated-layout-adopters.mddeleted file mode 100644index 86d0e6ac1b..0000000000--- a/.changeset/animated-layout-adopters.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feature] `useAnimatedLayout({containerRef})` returns a handle that Collapsible and TreeList take as their new `animatedLayout` prop (`spec:AST-105`). When one of them opens or closes, the content around it inside that container (after it, and before it where the layout centers or end-aligns it) glides to its new place instead of jumping, the revealed content reveals, closing content conceals before it hides, and the chevron turns, all on one shared motion, under every pointer, a mouse included. Fixed and stuck sticky elements stay put, the glide never scrolls the container, and under Reduce Motion the change cross-fades on touch and happens at once with a mouse. A single-mode CollapsibleGroup glides every item it changes. Without the prop, nothing changes.--@cixzhangdiff --git a/.changeset/animated-layout-earlier-siblings.md b/.changeset/animated-layout-earlier-siblings.mddeleted file mode 100644index a16e6bca2b..0000000000--- a/.changeset/animated-layout-earlier-siblings.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] With an `animatedLayout` handle, content before a Collapsible or TreeList change glides too where the layout moves it: an item before the change in a centered, end-aligned or space-between row, a sibling `order` places after it, and the card around a change in a centered column. Inside a positioned, stuck sticky or top-layer ancestor of the change, only the content after the change moves: that ancestor, the wrappers inside it and the content before the change take their final place at once.--@cixzhangdiff --git a/.changeset/animated-layout-exit-reads.md b/.changeset/animated-layout-exit-reads.mddeleted file mode 100644index e46c2fc95f..0000000000--- a/.changeset/animated-layout-exit-reads.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[perf] With an `animatedLayout` handle, a Collapsible or TreeList change in a long list reads every row's place before any glide starts, so the page is laid out once rather than once per gliding row.--@cixzhangdiff --git a/.changeset/animated-layout-identity-transform.md b/.changeset/animated-layout-identity-transform.mddeleted file mode 100644index 15c624215a..0000000000--- a/.changeset/animated-layout-identity-transform.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] With an `animatedLayout` handle, content after a change now glides even when it keeps a transform that leaves it in place. A resting Button (`scale(1)`, computed as `matrix(1, 0, 0, 1, 0, 0)`), a pressed one (`scale(0.98)`) and a row with swipe actions at rest (`translate3d(0, 0, 0)`) used to jump to their new place as if the app were moving them, and a pressed button jumped onto the button gliding beside it. A row a swipe holds open, or anything the app translates or rotates, is still left to the app.--@vjeuxdiff --git a/.changeset/animated-layout-swap.md b/.changeset/animated-layout-swap.mddeleted file mode 100644index 4d1d513b9d..0000000000--- a/.changeset/animated-layout-swap.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] The animated-layout module gains its internal in-place swap: old content held as one inert, transient copy while new content enters in its place, on the shared motion. Nothing uses it yet and nothing public changes. In right-to-left containers, content after a Collapsible or TreeList size change (with an `animatedLayout` handle) now glides by its inline-start edge instead of jumping.--@cixzhangdiff --git a/.changeset/animated-layout.md b/.changeset/animated-layout.mddeleted file mode 100644index 68b665f8f7..0000000000--- a/.changeset/animated-layout.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the one module for size-change glides (`spec:AST-105`, `architecture:react-component-runtime` INV12). After a reported size change, the content after it inside a container glides to its new place on one shared internal motion role, and the changed element enters or exits on the same motion. Not exported; no component uses it yet. The public `useAnimatedLayout` hook and Collapsible's and TreeList's `animatedLayout` prop arrive together in a later release.--@cixzhangdiff --git a/.changeset/announce-inside-modals.md b/.changeset/announce-inside-modals.mddeleted file mode 100644index 94dcc23d58..0000000000--- a/.changeset/announce-inside-modals.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `useAnnounce` now delivers a message by where its caller is. Inside an open Astryx modal — a Dialog, a modal BottomSheet (standalone or a switcher step), a modal Drawer, a Lightbox, MobileNav, or CommandPalette's dialog — the message reaches a persistent live region inside that dialog, which assistive technology hears while the modal is open, instead of the page-body region the modal hides; outside a modal nothing changes. Component and app code rendered inside a modal that calls `useAnnounce` is heard without any change to it. Delivery follows exposure, in top-layer order: a message sent as a switcher step hands over reaches the entering step, forward or back; a message sent as a modal BottomSheet closes, or just before an open Dialog is unmounted, waits while the leaving modal still covers the page and is delivered at its real close to whatever is exposed then — the Dialog it was opened over, or the page body — instead of being lost; a message a modal receives while a later modal covers it is not written and its region is clear before it is on top again. Busy controls inside a modal announce their busy start through the same region, including inside a native modal an app renders without Astryx; messages written to one region before the first is exposed are joined, and an identical repeat in the same frame is said once. The region's internal marker is `data-astryx-modal-live-region="polite"` or `"assertive"` (the busy region's former `data-astryx-modal-busy-region` is gone). Not in this change: CommandPalette's own result-count messages, Lightbox's own position and zoom messages, and Selector's and MultiSelector's selection and result-count messages in their `bottom-sheet` presentation are sent from the component that renders each dialog, above it, and still use the page-body channel while that dialog is open; each component's own change follows. This meets the in-modal delivery requirement in spec:AST-086 (FR14).--@imdreamrunnerdiff --git a/.changeset/announce-same-frame-join.md b/.changeset/announce-same-frame-join.mddeleted file mode 100644index 4ea6084237..0000000000--- a/.changeset/announce-same-frame-join.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] useAnnounce: messages announced in the same frame are now joined, in order, into one announcement instead of the last one replacing the others, and an identical repeat is spoken once, so a screen reader no longer misses an earlier status such as a result count announced alongside a confirmation. An empty message still clears the region, including joined messages not yet spoken. This meets the shared-channel requirement in spec:AST-086 (FR9). Introduced in #8244; final-state evidence (#8294).--@cixzhangdiff --git a/.changeset/announcer-role-query.md b/.changeset/announcer-role-query.mddeleted file mode 100644index 2837147a96..0000000000--- a/.changeset/announcer-role-query.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] EmptyState now announces through the page's shared announcer regions, a visually hidden `role="status"` (polite) and `role="alert"` (assertive) pair that Astryx mounts once on `document.body`. In tests, a query such as `getByRole('status')` or `getByRole('alert')` can therefore match one of these regions rather than your component. Scope the query to your component with `within(container)`.--@cixzhangdiff --git a/.changeset/ast-085-chat-composer-input.md b/.changeset/ast-085-chat-composer-input.mddeleted file mode 100644index a0b9c9f5ac..0000000000--- a/.changeset/ast-085-chat-composer-input.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] ChatComposerInput keeps focus and its Tab stop when disabled instead of moving focus to the page. Disabled editors block editing, paste/drop, trigger selection, imperative mutations, and submission while retaining their draft and accessible description.-@korkt-kimdiff --git a/.changeset/ast-085-complexselector.md b/.changeset/ast-085-complexselector.mddeleted file mode 100644index 5239ed008b..0000000000--- a/.changeset/ast-085-complexselector.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] ComplexSelector ignores value commits from an already-open popup while disabled, without changing focus or caller-owned content.-@korkt-kimdiff --git a/.changeset/ast-085-inputgroup.md b/.changeset/ast-085-inputgroup.mddeleted file mode 100644index c4f4e46780..0000000000--- a/.changeset/ast-085-inputgroup.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Propagate InputGroup disablement to compatible inputs and Button addons so child editing, opening, and form participation use their disabled behavior. Preserve nested group disablement and explicitly disabled children without modifying caller-rendered controls.-@korkt-kimdiff --git a/.changeset/ast-085-tokenizer.md b/.changeset/ast-085-tokenizer.mddeleted file mode 100644index 554fe9eb38..0000000000--- a/.changeset/ast-085-tokenizer.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Tokenizer blocks token additions, creation, removal, and supplied removal callbacks while disabled, preserving enabled removal and focus behavior. Disabled form values are omitted instead of rendering native-disabled hidden inputs.-@korkt-kimdiff --git a/.changeset/ast-087-built-icon-functions.md b/.changeset/ast-087-built-icon-functions.mddeleted file mode 100644index 46517e7324..0000000000--- a/.changeset/ast-087-built-icon-functions.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch-'@astryxdesign/core': patch------[feat] `astryx theme build` keeps function icon entries, so a built theme answers each `<Icon>` request with the size and variant it renders, exactly as the runtime theme does. This includes entries inherited from a built or package theme, and family builds. A built theme's `icons` field and the registry its module re-exports are React nodes, each function read at `{size: 'md'}`. A theme that lists `iconVariants` writes an `IconVariantMap` augmentation into `<theme>.variants.d.ts`, and its declaration carries the list, so a theme that extends the built theme types `variant` by those names. A function written in the theme file itself fails the build, as an inline registry always has. Themes without function entries or an icon variant list build the same output as before.-@imdreamrunnerdiff --git a/.changeset/ast-087-icon-function-entries.md b/.changeset/ast-087-icon-function-entries.mddeleted file mode 100644index b369b7d56d..0000000000--- a/.changeset/ast-087-icon-function-entries.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch------[feat] A theme icon entry in `defineTheme({icons})` or `registerIcons()` can be a pure, synchronous function of `{size, variant}`; `Icon` calls it with the size it renders at, so a theme can match its icon library's artwork or props to each Icon size. A selected function's result is final: `null` draws no glyph instead of falling back. `getIcon`, `getExtendedIcon`, `getIconRegistry`, `useIcon`, and a theme's `icons` field stay node-valued and read a function entry at `{size: 'md'}`. Existing node entries are unchanged.-@imdreamrunnerdiff --git a/.changeset/ast-087-icon-variant-list.md b/.changeset/ast-087-icon-variant-list.mddeleted file mode 100644index 0453b9b5e8..0000000000--- a/.changeset/ast-087-icon-variant-list.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch------[feat] A theme lists the icon variant names it supports once with `defineTheme({iconVariants})`, and reads them back from `theme.iconVariants`. A child theme that sets the list replaces the inherited one; a child that omits it inherits it. `astryx theme build` keeps the list in the built theme, so a theme extending a built theme inherits it too. Inside `defineTheme`, icon entry functions receive `variant` typed as the theme's listed names. `@astryxdesign/core/Icon` exports the augmentable `IconVariantMap` and its `IconVariant` names, which type `variant` in `registerIcons()` entries. Themes without `iconVariants` are unchanged.-@imdreamrunnerdiff --git a/.changeset/ast-087-icon-variant-prop.md b/.changeset/ast-087-icon-variant-prop.mddeleted file mode 100644index 24fe0aa051..0000000000--- a/.changeset/ast-087-icon-variant-prop.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch------[feat] `Icon` takes an optional `variant` (an `IconVariant` name) that requests the active theme's alternate artwork for a semantic icon: `<Icon icon="info" variant="filled" />`. The theme's icon entry receives the variant only when the active theme lists it in `iconVariants` and, for an inherited entry, the theme that defined the entry lists it too; otherwise it receives `undefined` and draws its normal artwork. `astryx theme build` keeps each inherited entry's defining list, so a built theme passes the same variants as its runtime theme. A `registerIcons()` entry receives the variants the active theme lists, and a node entry ignores `variant`. An icon component passed directly never receives `variant`, and `variant` is never written to the DOM or reflected on the `icon` theming target. Icons without `variant` render as before.-@imdreamrunnerdiff --git a/.changeset/badge-label-required-doc.md b/.changeset/badge-label-required-doc.mddeleted file mode 100644index e69923735b..0000000000--- a/.changeset/badge-label-required-doc.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] Badge's documentation marks `label` as required, as its props type already does. `astryx component Badge` and the docsite no longer list it as optional.--@cixzhangdiff --git a/.changeset/banner-end-content-foreground.md b/.changeset/banner-end-content-foreground.mddeleted file mode 100644index e6505f1ca0..0000000000--- a/.changeset/banner-end-content-foreground.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Keep `Banner` status foreground colors scoped to Banner-owned content so consumer `endContent`, including nested dialogs, retains its own text color.--@rubyycheungdiff --git a/.changeset/bottom-sheet-fewer-elements.md b/.changeset/bottom-sheet-fewer-elements.mddeleted file mode 100644index 7c2ec8f309..0000000000--- a/.changeset/bottom-sheet-fewer-elements.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] BottomSheet renders fewer elements, with no visual change: an open sheet's dialog positions the panel itself, the grab bar draws its pill, and a closed sheet renders no edge tint. A switcher's sheets keep their positioner.--@vjeuxdiff --git a/.changeset/bottom-sheet-open-order-stacking.md b/.changeset/bottom-sheet-open-order-stacking.mddeleted file mode 100644index 169d5b3748..0000000000--- a/.changeset/bottom-sheet-open-order-stacking.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `BottomSheet` stacks by open order. A modal sheet opened while another modal sheet is open now stacks on top of it instead of presenting as a second, unrelated dialog: the covered sheet stays mounted with its state, recedes behind the top sheet (0.96 / −8px at depth 1, 0.92 / −16px from depth 2), and is blocked from pointer, keyboard, and assistive technology; only the bottom sheet's backdrop dims the page, so a stack no longer darkens per level; and Escape, a scrim tap, a swipe, and a platform close request pop only the top sheet, through that sheet's own `onOpenChange` and honouring its `purpose`. The top sheet is the most recently opened one still open, wherever the sheets are written — siblings, separate components, inside another sheet's content, or inside a `BottomSheetSwitcher` step; a whole switcher is one level, and switching its step keeps its place. When several sheets open in one update (a deep link), tree order decides and the first painted frame is already right: a sheet nested in another sheet's content no longer opens beneath its parent. Closing the top sheet returns focus into the sheet it reveals; closing every sheet of a stack in one update returns focus once, to the bottom sheet's `finalFocusRef` or opener, after the last dialog has closed (each sheet's own return used to be refused while the others were still modal). A sheet rendered inside a closing sheet's content now leaves with it instead of staying open invisibly, and comes back with the host if its own `isOpen` is still true (its state is never written for it); sheets above it that are not in its content stay open. Sheets with `hasScrim={false}` never stack and are never stacked on. No prop, type, or export changes; a modal sheet on its own behaves exactly as before (apart from the reduced-motion fix released alongside).--@imdreamrunnerdiff --git a/.changeset/bottom-sheet-reduced-motion-cross-fade.md b/.changeset/bottom-sheet-reduced-motion-cross-fade.mddeleted file mode 100644index 5b6396e136..0000000000--- a/.changeset/bottom-sheet-reduced-motion-cross-fade.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] BottomSheet follows the reduced-motion design rule. With `prefers-reduced-motion: reduce`, a sheet's entrance, exit, recede and replace handoff — a `BottomSheetSwitcher` step's too — no longer travel or scale: on a touch screen (`pointer: coarse`) the entering sheet fades in at its resting place and the leaving or retained sheet fades out where it is, opacity only, within 200 ms; with a mouse, trackpad or keyboard the change is immediate, except that a swipe dismissal — a transition a touch drag's release started — fades out in place on every pointer. Before, the motions ran shortened transforms on every pointer and nothing cross-faded.--@imdreamrunnerdiff --git a/.changeset/bottom-sheet-replace-aligns.md b/.changeset/bottom-sheet-replace-aligns.mddeleted file mode 100644index 161323f07f..0000000000--- a/.changeset/bottom-sheet-replace-aligns.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] When one standalone `BottomSheet` replaces another and the entering sheet is shorter, the sheet being replaced moves down to the entering sheet's top edge while the entering sheet rises, and only then fades, so the switch reads as one sheet changing height, as a `BottomSheetSwitcher` step change does. It had stayed at its own height and faded out above the entering sheet. Under reduced motion the replaced sheet still does not move.--@imdreamrunnerdiff --git a/.changeset/bottom-sheet-replace-handoff.md b/.changeset/bottom-sheet-replace-handoff.mddeleted file mode 100644index f16448f347..0000000000--- a/.changeset/bottom-sheet-replace-handoff.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `BottomSheet` replaces a sheet that closes in the same update another opens. When the top sheet of a stack closes and exactly one other sheet opens in the same update (one state value naming the open step does this), the new sheet replaces it instead of stacking on it: it rises above the replaced sheet, a taller replaced sheet moves down to meet its top edge at the same time, the replaced sheet fades only after both motions finish and is inert and hidden from assistive technology from the start, the scrim holds steady with no dip, focus moves into the new sheet, and closing the flow later returns focus to the element that opened its first sheet. This is the handoff `BottomSheetSwitcher` runs between its steps, now available to standalone sheets; a multi-step flow can be written as one `BottomSheet` per step with no switcher. A covered sheet closing while a sheet opens, several sheets changing at once, or a close and an open in different updates keep the ordinary push and pop motion, and existing stacking behaviour is unchanged. A replace is recognised only when the move was made from inside the closing sheet: the control last pressed (or, with no recent press, the focused element) was in it, as a step's own Continue or Back button is; a close and an open driven from a control outside it, by two unrelated owners, stay a pop and a push with their own focus return. Non-modal sheets (`hasScrim={false}`) replace each other the same way: they are now hosted in the browser top layer as manual popovers, with no scrim, focus trap or scroll lock as before, so a non-modal step orders above the one it replaces, and the toast viewport re-enters the top layer above a non-modal sheet as it does above a modal. The non-modal sheet's page-level `z-index` is gone with the move (AST-027); below the Popover API support floor the sheet falls back to `show()` in page stacking order, usable but with no promise over later page content (the reduced fallback AST-003 describes). They still never stack. A non-modal sheet now also returns focus to its opener when it closes while the person is still in it (a modal sheet always did); focus the person took elsewhere on the live page stays there. The private stack registry now keeps one state per page shared by every copy of the package on it that speaks the same stack protocol version (a copy on another version keeps its own stack), and one stack per document. No prop, type, or export changes; a modal sheet on its own behaves exactly as before (apart from the reduced-motion fix released alongside). A non-modal sheet on its own changes in three ways with its new host: it is in the top layer (a manual popover) instead of page stacking order, its page-level `z-index` is gone, and it returns focus to its opener on close while focus is still inside it; its scrim-less, scroll-free, page-interactive contract is unchanged.--@imdreamrunnerdiff --git a/.changeset/bottom-sheet-switcher-deprecated.md b/.changeset/bottom-sheet-switcher-deprecated.mddeleted file mode 100644index fbb0963baa..0000000000--- a/.changeset/bottom-sheet-switcher-deprecated.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `BottomSheetSwitcher` and the `sheetId` prop of `BottomSheet` are deprecated. The replacement is already in this release: write each step of a multi-step flow as its own standalone `BottomSheet` with `isOpen`, driven by one state value that names the open step; closing the top sheet and opening the next in the same update runs the same replace handoff the switcher ran (entering step above, a taller retained step aligns down and fades after both motions, one steady scrim, focus into the new step and back to the flow's opener on close). Migration, per flow: (1) replace the `activeSheet` / `onActiveSheetChange` pair with one `step` state value; (2) give each step `isOpen={step === 'id'}` and `onOpenChange={isOpen => !isOpen && setStep(current => (current === 'id' ? null : current))}` in place of `sheetId="id"` (the guard keeps a step that is being replaced from clearing the step the person just chose); (3) remove the `BottomSheetSwitcher` wrapper, moving its `hasScrim` onto every step; (4) keep the step buttons as they were (`setStep('next')`). The handoff runs when the move is made from inside the open step (a step's own Continue or Back, or code while focus is in it); a step changed from a control outside the flow's sheets — a page control beside a `hasScrim={false}` flow, or code after focus has left the step — closes and opens with the sheets' own push and pop motion, where the switcher handed off on any `activeSheet` change. The switcher's other props map as follows: `onCancel` becomes a guarded `onOpenChange` on each step (one that ignores `false` while the flow must stay open), which keeps the step's dialog role — a standalone sheet reports Escape, the platform close, the scrim tap and the swipe all as `onOpenChange(false)` with no reason, so the guard holds the step open against all of them while it applies, where `onCancel` vetoed only the cancel request; a veto of Escape alone has no equivalent, and the only per-path lever is `purpose` (`form` keeps Escape and blocks the scrim tap and the swipe; `required` blocks all three and exposes the step as an `alertdialog`). A consumer `aria-label` / `aria-labelledby` becomes each step's `label`, which names its dialog. `ref`, `id`, `data-testid`, `className`, `style`, `xstyle` and the other dialog props have no dialog-level equivalent — a standalone sheet's `ref` and base props reach its panel `<div>` and its dialog is implementation — so a test or an anchor that needs the dialog queries the panel's `closest('dialog')`, and dialog-level styling is dropped. Flows that keep using the switcher keep working: a switcher flow used on its own behaves as released — with two fixes released alongside: a toast raised from a step now renders above the flow and can be pressed, and under reduced motion its steps' entrance, exit and handoff follow the reduced-motion rule (no travel; a cross-fade on touch, immediate otherwise) — and when it is stacked with other sheets the stacking behaviour of this release applies to it as one level (it recedes and is blocked when covered, shares the one scrim, stands down from dismissal while covered, and returns focus by the stacking rules). Its declarations and docs are marked `@deprecated` and its docs, templates and stories show only the replacement, until a future minor release removes it. Non-modal flows (`hasScrim={false}`) migrate the same way: non-modal sheets replace each other too.--@imdreamrunnerdiff --git a/.changeset/bottom-sheet-switcher-toast-outlet.md b/.changeset/bottom-sheet-switcher-toast-outlet.mddeleted file mode 100644index 6092074d8e..0000000000--- a/.changeset/bottom-sheet-switcher-toast-outlet.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Toasts raised from a `BottomSheetSwitcher` step stay visible and clickable above the flow. A modal switcher flow now supplies its active step's dialog as the toast viewport's host, as a standalone scrim `BottomSheet` and a `Dialog` do; the host follows each handoff to the entering step, and the flow hands the viewport back when it closes. Before, the viewport stayed behind the flow's dialogs, so a toast raised from a step was covered by the step and a press on it landed on the step. A `hasScrim={false}` flow is not modal and leaves the viewport in place.--@imdreamrunnerdiff --git a/.changeset/bottom-sheet-toast-outlet.md b/.changeset/bottom-sheet-toast-outlet.mddeleted file mode 100644index f6d7fe0ba4..0000000000--- a/.changeset/bottom-sheet-toast-outlet.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Toasts stay visible and clickable above an open BottomSheet. The `ToastViewport` from `LayerProvider` (or the one `useToast` mounts on its own) now moves into a standalone BottomSheet while it is open, as it already does into an open Dialog, and back as soon as the sheet starts closing. Before, the sheet covered the viewport and made it inert, so a click on a toast's action landed on the sheet instead and could dismiss it. A sheet with `hasScrim={false}` is not modal and leaves the viewport in place. Sheets inside a `BottomSheetSwitcher` are unchanged.--@vjeuxdiff --git a/.changeset/busy-start-not-after-outcome.md b/.changeset/busy-start-not-after-outcome.mddeleted file mode 100644index ffdad2d744..0000000000--- a/.changeset/busy-start-not-after-outcome.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] BaseTypeahead and CommandPalette: when a typed search finishes before its "Loading" announcement is made, the pending "Loading" is dropped, so a screen reader no longer hears "Loading" after the result count or has it replace the count. This meets the busy-announcement requirement in spec:AST-086 (FR8).--@cixzhangdiff --git a/.changeset/card-press-overlay-touch.md b/.changeset/card-press-overlay-touch.mddeleted file mode 100644index e91846e8c2..0000000000--- a/.changeset/card-press-overlay-touch.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] ClickableCard, SelectableCard and an interactive Thumbnail now show the pressed overlay under a finger in apps that compile Astryx from source with cascade layers (the Vite and PostCSS integrations, and Storybook). The touch press was written as an arm of a custom property whose own default sits outside the cascade layer the arm lands in, so the default always won and a touch press painted nothing. The press now paints as the overlay's own image, at the press's strength, and fades at the lift; mouse hover and press are unchanged, and the precompiled stylesheet keeps the same pixels.--@vjeuxdiff --git a/.changeset/chatcomposer-status-own-content.md b/.changeset/chatcomposer-status-own-content.mddeleted file mode 100644index 94615f84fb..0000000000--- a/.changeset/chatcomposer-status-own-content.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `ChatComposer`'s status bar announces through the shared own-content announcement module (`spec:AST-086` FR11–FR13). It still announces errors assertively and warnings politely, once per occasion, but a status that is already showing while the page loads is no longer announced, and it speaks the bar's rendered text without the decorative icon.--@cixzhangdiff --git a/.changeset/clear-button-keeps-the-keyboard.md b/.changeset/clear-button-keeps-the-keyboard.mddeleted file mode 100644index b45411f0cd..0000000000--- a/.changeset/clear-button-keeps-the-keyboard.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Tapping the clear button of a TextInput or NumberInput that is not focused now brings up the iOS keyboard. The field took focus a frame after the tap, and iOS Safari only raises its keyboard for a focus made while handling the touch, so the field ended up focused with no keyboard. The focus now happens inside the tap, still with `preventScroll`, so a scrolled page stays put.--@vjeuxdiff --git a/.changeset/cli-bottom-sheet-templates-standalone-steps.md b/.changeset/cli-bottom-sheet-templates-standalone-steps.mddeleted file mode 100644index f14e3f3727..0000000000--- a/.changeset/cli-bottom-sheet-templates-standalone-steps.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[feat] The two Bottom Sheet flow block templates (`BottomSheetSwitcherShowcase`, `BottomSheetSwitcherReviewFlow`) now teach the replacement for the deprecated `BottomSheetSwitcher`: each step is a standalone `BottomSheet` driven by one state value, and moving on replaces the open step in place. Both stay examples of `BottomSheetSwitcher` (the showcase remains that page's hero) and are now also listed under `BottomSheet`. Template ids, files and their published registry identities keep their names, so `template <name>`, the released JSON ids and the ShadCN routes are unchanged.--@imdreamrunnerdiff --git a/.changeset/cli-detect-stylex-unplugin.md b/.changeset/cli-detect-stylex-unplugin.mddeleted file mode 100644index 233be65e40..0000000000--- a/.changeset/cli-detect-stylex-unplugin.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `detectStylingSystem` recognizes `@stylexjs/unplugin` as a StyleX compiler, so projects compiling StyleX through the standard Vite path are detected as `stylex` instead of falling through to the `css` guidance.--@nbozidarevicdiff --git a/.changeset/cli-experimental-render.md b/.changeset/cli-experimental-render.mddeleted file mode 100644index b4a99e4ebe..0000000000--- a/.changeset/cli-experimental-render.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[experimental] New command `astryx experimental render <page>`: renders a page with your installed Astryx components to ONE self-contained HTML file. The file inlines only the Core CSS rules the page uses plus the page's own StyleX styles and local images, runs no script, loads nothing from the network, follows light and dark mode, and carries the page's source. `astryx experimental render --reverse <file.html>` writes that source back byte for byte, rebuilds a page from Astryx markup when the source was removed, and refuses other HTML. Warnings flag what may not look as meant, such as a `ListItem` given children instead of `label`. Experimental commands live under `astryx experimental`, are marked `[experimental]` in help and the manifest, and may change or be removed in any patch release. Guide: `astryx docs cli/experimental/render-pages`.--@josephfarinadiff --git a/.changeset/cli-icon-sets-authoring.md b/.changeset/cli-icon-sets-authoring.mddeleted file mode 100644index 936848d6b6..0000000000--- a/.changeset/cli-icon-sets-authoring.md+++ /dev/null@@ -1,17 +0,0 @@-----'@astryxdesign/cli': patch------[experimental] Icon sets: authoring a set from a library takes fewer steps and fewer guesses. Only the experimental icon commands, the icon-set guide, and `astryx template` in a project that sets `experimental.iconSet` change; without the opt-in, every stable command reads as before except the `experimental` group's summary in `astryx help` and `astryx manifest`, which now names icon sets: "Try features that may change in a patch release: icon sets (find icons, build an icon-set package)" (it read "Try features that may change or be removed in a patch release").--- **`experimental icon new-set`.** `--from` maps a definition only when an icon has its exact name and lists those entries for review; other likely icons come back as at most three suggestions per definition, never written. It records the library and version as `source`, copies the library's license notices and takes its license, keeps `--exclude` in the data file's `exclude` for every refresh, and names the exports it left out as not icons. It writes only the set's own files: its receipt names, as text to copy, the entry change that makes the set's icons import from the package by name (never editing a built or CommonJS entry), the `react` and optional `@types/react` and `@astryxdesign/cli` peers, and the `typecheck` script the package is missing, and `integration check` names the same entry change, once, until it is made. `--variants` and `--default-variant` declare variants; `--display-name` and `--description` fill the descriptor, on a refresh too; a refresh that first records the library also copies its license notices and takes its license, and a refresh changes only the icons the refreshed library supplies (your own `./` artwork and other libraries' icons keep their map entries and variants, and `add --all` leaves them alone), knows an existing icon by the library export it re-exports, so the icon keeps its export name exactly, its map entries, variants, and words when its id changes, and the change is listed under `renamed`. Ids keep a dimension as one word (`squares-2x2`), a library's other names for an icon become its words, and `…Provider` and `…Context` exports are never icons. A library of 1,600 icons is read in about two seconds.-- **`experimental icon add` and `map`.** `add --variant <name> --from <module> --all` adds a variant for every icon at once; a `./` file is named as written, and the receipt names the package.json `files` that publishes it. `map --pairs a=b,c=d` writes many entries in one checked write, and both accept a definition's kebab id; `map` names an icon by its id, its export name in any case, or another name its library exports it as, never by one word of its id.-- **Options decided in pairs.** Every icon command refuses two options it would not both honor, with `ERR_INVALID_OPTION` (such as `--list --definitions`, `--definitions --limit 3`, `--all-icons` with a query, `add --all --id`, or `new-set --exclude` without `--from`), instead of ignoring one.-- **All or nothing.** When `new-set`, `add`, `map`, or `new-definition` fails partway, every file is as it was and the error is `ERR_WRITE_FAILED`.-- **Sets named consistently.** Every icon command that names a set (`--set` with a query or `--all-icons`, `<set>/<id>`, `use`, and `add`, `map`, `new-definition` in the package) reports a set that is not there as missing and an invalid one as withdrawn, with why, both `ERR_NOT_FOUND`.-- **Listing.** `experimental icon --set <set> --all-icons` lists every icon of a set (`icon.setIcons`) and `--definitions` lists every Astryx definition, built in or optional (`icon.definitions`). Search shows partial matches only when nothing better matches.-- **Templates.** A mapped icon drops the library's sizing props (`size`, `strokeWidth`, `absoluteStrokeWidth`), reported as `dropped`, and comments on a rewritten import line are kept.-- **Definitions.** Thirteen new icon definitions (`rotate`, `flipHorizontal`, `flipVertical`, `alignStart`, `alignCenter`, `alignEnd`, `panelLeft`, `panelRight`, `gitBranch`, `gitFork`, `scale`, `cpu`, `textCase`), declared by the templates that draw them. Built-in and optional definitions gain common glyph names as words; seven optional definitions lose a word that named a different thing, so a search for that word no longer finds a set's icon through them: `star` (`bookmark`), `database` (`table`), `raiseHand` (`stop`), `redo` (`forward`), `activity` (`monitor`), `archive` (`store`), `mobile` (`device`).-- **Checks.** `integration check` suggests icons by the same rule and lists each optional definition with its description and words; the version-drift warning gives the refresh command.--@josephfarinadiff --git a/.changeset/cli-tokenizer-blocks-mobile-width.md b/.changeset/cli-tokenizer-blocks-mobile-width.mddeleted file mode 100644index b14da5963a..0000000000--- a/.changeset/cli-tokenizer-blocks-mobile-width.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[docs] The Tokenizer block templates (`Tokenizer`, `Clear`, `Creatable`, `End Content`, `Icon`, `Max Entries`, `Overflow`, `States`) size their field through a column that is 400px wide where there is room and shrinks with its container, instead of a fixed 400px width, so the live examples fit a phone-sized screen without clipping.--@imdreamrunnerdiff --git a/.changeset/cli-tokenizer-showcase-search.md b/.changeset/cli-tokenizer-showcase-search.mddeleted file mode 100644index 23aacd0062..0000000000--- a/.changeset/cli-tokenizer-showcase-search.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] The `Tokenizer` showcase block template searches its tags: typing lists the tags that match. Its search source returned nothing for every query, so the live example on the Tokenizer docs page answered all typing with "No results found".--@imdreamrunnerdiff --git a/.changeset/cli-verify-npm-command.md b/.changeset/cli-verify-npm-command.mddeleted file mode 100644index 76b5843060..0000000000--- a/.changeset/cli-verify-npm-command.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx integration verify` starts npm the way the rest of the CLI does: npm's own entry file, run with the Node that runs the CLI, when one is found. An `npm` earlier on the PATH that is not npm itself, such as a wrapper that refuses npm commands, no longer fails the check with "npm pack failed".--@josephfarinadiff --git a/.changeset/codeblock-copy-never-covers-code.md b/.changeset/codeblock-copy-never-covers-code.mddeleted file mode 100644index 58b19d9912..0000000000--- a/.changeset/codeblock-copy-never-covers-code.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A CodeBlock with no title or language label no longer lets its Copy button cover code. The button sits in its own column beside the code instead of over it, so a long first line ends before the button, whether the code is scrolled sideways, wrapped, or right-to-left. The button is centred on the first line, so a one-line block reads as one row with even space above and below, and a block that grows line by line keeps the button where it was. Blocks with a header are unchanged.--@cixzhangdiff --git a/.changeset/codeblock-end-content.md b/.changeset/codeblock-end-content.mddeleted file mode 100644index 469884271b..0000000000--- a/.changeset/codeblock-end-content.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `CodeBlock` takes `endContent`, a slot for your own controls, such as a "Run in terminal" button. They appear just before Copy: in the header when the block has one, otherwise beside the code in the top inline-end corner, never over it. The slot never creates a header, and clicking or pressing keys in it never collapses the block. For single-line mode, leave out the title and pass `hasLanguageLabel={false}`: a one-line command then reads as one row with its controls beside it.--@cixzhangdiff --git a/.changeset/codeblock-languages.md b/.changeset/codeblock-languages.mddeleted file mode 100644index d30525ec1e..0000000000--- a/.changeset/codeblock-languages.md+++ /dev/null@@ -1,17 +0,0 @@-----'@astryxdesign/core': patch------[feat] `CodeBlock` highlights C, C++, SQL, Rust, Kotlin, Swift, and Go with no setup.--Every other language is opt in, one at a time:--- Import that language on its own and pass it as `language`, for example `graphql` from `@astryxdesign/core/CodeBlock/languages/graphql`.-- Modules ship for `graphql`, `java`, `thrift`, `objectiveC` (path `languages/objective-c`), `toml`, `powershell`, `ruby`, `lua`, and `dockerfile`.-- A string such as `language="graphql"` still selects only a built-in language.--Your own languages work the same way. `createCodeLanguage({name, identifiers, fileExtensions, fileNames, tokenize})` makes a language value from your own tokenize function.--The built-in tokenizer stays within 4,608 bytes gzipped. Each module adds at most 512 bytes, and only when you import it.--@cixzhangdiff --git a/.changeset/codeblock-snippet-example-headerless.md b/.changeset/codeblock-snippet-example-headerless.mddeleted file mode 100644index 6d475ffbc0..0000000000--- a/.changeset/codeblock-snippet-example-headerless.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[docs] The CodeBlock "Code — Snippet" example shows one-line commands with no header. Copy sits beside the code in its own column, so each command reads as a single row. A third block shows a long first line that ends before the button.--@cixzhangdiff --git a/.changeset/codeblock-tokenizer-codemod.md b/.changeset/codeblock-tokenizer-codemod.mddeleted file mode 100644index 5e35aa96e8..0000000000--- a/.changeset/codeblock-tokenizer-codemod.md+++ /dev/null@@ -1,8 +0,0 @@-----'@astryxdesign/cli': patch-'@astryxdesign/core': patch------[feat] CodeBlock's `tokenizer` prop is deprecated in favour of a custom language value: pass `language={createCodeLanguage({name, identifiers, tokenize})}` with the same function. The prop still works exactly as released. `astryx upgrade` rewrites it when it sits beside a static `language`. A function literal becomes `language={createCodeLanguage({name: 'zig', identifiers: ['zig'], tokenize: (code) => …})}`. A name or call-free property becomes `language={fn ? createCodeLanguage({…, tokenize: fn}) : 'zig'}`, since it may be undefined. Uses it cannot prove are left unchanged, with a TODO comment: a computed, missing, or `plaintext` language, any other tokenizer value, or a block that spreads props.--@cixzhangdiff --git a/.changeset/codemod-skip-unparseable-protected.md b/.changeset/codemod-skip-unparseable-protected.mddeleted file mode 100644index 1130454116..0000000000--- a/.changeset/codemod-skip-unparseable-protected.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx upgrade` no longer fails when a protected file (vendored, generated, or ignored) does not parse, such as a vendored bundle written for another toolchain. It skips the file, lists it under `declinedCandidates` with the parse error's location, and completes the rest of the upgrade. A file upgrade owns that does not parse still fails the run, and protected files that parse are still checked and reported.--@ejhammonddiff --git a/.changeset/codemod-walk-skip-symlinked-dependencies.md b/.changeset/codemod-walk-skip-symlinked-dependencies.mddeleted file mode 100644index 8bea5797c0..0000000000--- a/.changeset/codemod-walk-skip-symlinked-dependencies.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx upgrade` no longer scans through a symbolic link into installed dependencies or version-control metadata, such as a symlinked `node_modules` or a link into a package store. Those trees were already never written; skipping them stops a run from the project root spending minutes reading them. Other symbolically linked folders are still scanned so their required changes are reported.--@ejhammonddiff --git a/.changeset/command-palette-empty-long-text.md b/.changeset/command-palette-empty-long-text.mddeleted file mode 100644index 52328c9286..0000000000--- a/.changeset/command-palette-empty-long-text.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] CommandPaletteEmpty wraps a long unbroken word, such as a file path or URL in an empty-search message, inside the palette instead of spilling it past both edges where its start and end could not be read.--@cixzhangdiff --git a/.changeset/complex-selector-combobox-trigger.md b/.changeset/complex-selector-combobox-trigger.mddeleted file mode 100644index cb04c13945..0000000000--- a/.changeset/complex-selector-combobox-trigger.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] ComplexSelector: the trigger is now a combobox whose popup is a dialog, so a screen reader hears when the field is required (`aria-required` was ignored on the old button role). With `renderTrigger`, the caller's control receives the same `role`, `aria-required`, and `aria-disabled`, is named by `label` unless the selector is given `aria-label` or `aria-labelledby`, and a disabled control keeps its tab stop but does not open. Button keeps a caller-supplied `aria-disabled` and `aria-busy`, so a Button used as that control carries the selector's state. Tests that find the trigger with `getByRole('button')` should use `getByRole('combobox')`.--@cixzhangdiff --git a/.changeset/complexselector-trigger-caller-name.md b/.changeset/complexselector-trigger-caller-name.mddeleted file mode 100644index e533ebf0bc..0000000000--- a/.changeset/complexselector-trigger-caller-name.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] ComplexSelector: a caller's `aria-label` or `aria-labelledby` now names the built-in trigger, replacing the field label, as it already did for a `renderTrigger` control. Before, the built-in trigger always took its name from the label, so a name passed to the selector was never announced.--@cixzhangdiff --git a/.changeset/context-menu-long-press-lift.md b/.changeset/context-menu-long-press-lift.mddeleted file mode 100644index fe735d81eb..0000000000--- a/.changeset/context-menu-long-press-lift.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A ContextMenu opened by a finger's long press stays open as the finger lifts: the compatibility `mousedown` the browser sends for that press as it lifts no longer reads as a press outside. Every other press outside the menu closes it, or leaves it open, as before.--@vjeuxdiff --git a/.changeset/core-hit-area.md b/.changeset/core-hit-area.mddeleted file mode 100644index b320921ddb..0000000000--- a/.changeset/core-hit-area.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: a shared touch hit-area utility (utils/hitArea.ts) that grows a target toward 44 px under a coarse pointer and stops at half the gap to each neighbour, so a tap goes to the nearer target. Not exported.--@cixzhangdiff --git a/.changeset/data-token-upgrade-no-fallbacks.md b/.changeset/data-token-upgrade-no-fallbacks.mddeleted file mode 100644index 54e77160bf..0000000000--- a/.changeset/data-token-upgrade-no-fallbacks.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx upgrade --from` a version before 0.7.0 no longer fails on `var(--color-data-*)` uses without a fallback. Prebuilt `@astryxdesign/core/astryx.css` defines all 56 data-color defaults, and source builds read data colors through `dataVars`, so the upgrade no longer asks for fallbacks. A graph-based source build, such as `@astryxdesign/build/vite`, that reads raw `var(--color-data-*)` strings without a `dataVars` import should import `dataVars` from `@astryxdesign/core/theme/dataTokens.stylex`; the upgrade no longer reports those uses. Stale generated theme CSS that still emits the defaults at `:root` still fails the upgrade.--@ejhammonddiff --git a/.changeset/dialog-reduced-motion-touch-fade.md b/.changeset/dialog-reduced-motion-touch-fade.mddeleted file mode 100644index a4c7a92d6a..0000000000--- a/.changeset/dialog-reduced-motion-touch-fade.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Dialog: with reduced motion on a touch screen, the dialog fades in where it lands, in 200 ms or less, instead of appearing with no transition. With a mouse it still appears at once, and it never slides or scales in under reduced motion (design:reduced-motion).--@vjeuxdiff --git a/.changeset/doc-edits-seen-in-process.md b/.changeset/doc-edits-seen-in-process.mddeleted file mode 100644index 2df373957f..0000000000--- a/.changeset/doc-edits-seen-in-process.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] A process that calls the CLI API more than once, such as a docs site's search or an agent harness, now sees an edit to a doc file it already read: `search()`, `docs()` and `component()` read the edited file's new content on their next call, instead of what the process first imported. An unchanged doc file is still imported once and shared, so readers keep getting the module's own doc.--@josephfarinadiff --git a/.changeset/dropdown-menu-radio-item-caller-handlers.md b/.changeset/dropdown-menu-radio-item-caller-handlers.mddeleted file mode 100644index 131e47dfb6..0000000000--- a/.changeset/dropdown-menu-radio-item-caller-handlers.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `DropdownMenuRadioItem` now runs a caller's `onClick` and `onPointerMove`. Before, the row's own selection and hover-focus handlers replaced them, so they never ran. They now run after the row selects its value and takes hover focus, as they already do on `DropdownMenuItem` and `DropdownMenuCheckboxItem`; a disabled row still selects nothing and does not call `onClick`. The documentation also marks `value` and `label` as required and no longer says disabled radio items stay reachable with the arrow keys, which DropdownMenu currently skips.--@cixzhangdiff --git a/.changeset/dropdown-menu-submenu-docs.md b/.changeset/dropdown-menu-submenu-docs.mddeleted file mode 100644index 22854c11e3..0000000000--- a/.changeset/dropdown-menu-submenu-docs.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] `DropdownMenuSubMenu`'s documentation marks `label` and `children` as required, as its props type already does, and documents `menuDataTestId`, the test id for the sub-menu's own menu (the flyout, or the drilled-in list on a phone). The `presentation` prop's JSDoc now declares its `'adaptive'` default.--@cixzhangdiff --git a/.changeset/dropdownmenu-submenu-host-selector.md b/.changeset/dropdownmenu-submenu-host-selector.mddeleted file mode 100644index 3e5aff59b3..0000000000--- a/.changeset/dropdownmenu-submenu-host-selector.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: DropdownMenu's rule that steps the root menu aside while a sub-menu's drilled-in view shows names its surface host by an internal marker instead of a universal selector. No visible or behavior change.--@cixzhangdiff --git a/.changeset/ease-exit-token.md b/.changeset/ease-exit-token.mddeleted file mode 100644index 114250b7b0..0000000000--- a/.changeset/ease-exit-token.md+++ /dev/null@@ -1,8 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch------[feat] New `--ease-exit` token, `cubic-bezier(0.3, 0, 0.6, 0.6)`: an accelerating curve for things leaving the screen, beside `--ease-standard` for things arriving. `BottomSheet` closes on it at the value it already used, so nothing looks different; a theme can now retune that exit through the token. On a touch screen the sheet keeps its own closing curve. `astryx docs motion`, the easing token table, and the theme template list it. (#8004)--@kentonquatmandiff --git a/.changeset/edge-autoscroll.md b/.changeset/edge-autoscroll.mddeleted file mode 100644index 8b092e9eab..0000000000--- a/.changeset/edge-autoscroll.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: a menu's edge autoscroll runs on a shared edge-autoscroll timer (utils/edgeAutoscroll.ts), with the same zone, step and interval as before. No behavior change.--@vjeuxdiff --git a/.changeset/empty-state-no-live-role.md b/.changeset/empty-state-no-live-role.mddeleted file mode 100644index e91057e0df..0000000000--- a/.changeset/empty-state-no-live-role.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] EmptyState's root no longer carries `role="status"`, so it is not a live region that mounts already holding its text, which screen readers announce unreliably (`spec:AST-086` FR2). Apps need no code change. An EmptyState rendered or changed while the page loads announces nothing; one that appears later, or whose title or description changes later, announces its title and description once through the shared polite live region; inside a live container such as `ChatMessageList`'s log, the container announces it (`spec:AST-086` FR4). A `role` you pass now reaches the root instead of being replaced; tests that found EmptyState with `getByRole('status')` need another selector.--@harjothkharadiff --git a/.changeset/family-members-from-source.md b/.changeset/family-members-from-source.mddeleted file mode 100644index 877f540d6f..0000000000--- a/.changeset/family-members-from-source.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] A component family lists the same members whether or not its package has been built. When the package's `exports` give a `source` condition and that file is in the package, the CLI reads the family's members from it instead of from the built output. Before, a member that only the package's entry exports, such as Lab's `TourStep`, was listed only after a local build. The official package list now includes `TourStep`.--@josephfarinadiff --git a/.changeset/fileinput-clear-focus-trigger.md b/.changeset/fileinput-clear-focus-trigger.mddeleted file mode 100644index 2218b1d896..0000000000--- a/.changeset/fileinput-clear-focus-trigger.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] FileInput: clearing the selection returns focus to the file-selection trigger. Before, both keyboard and pointer activation of the clear button focused the visually hidden native `<input type="file">`, which is `aria-hidden` and out of the tab order, so a screen reader announced nothing after the clear. Now focus lands on the trigger, which announces the field label. No API changes.--@kyu-rongdiff --git a/.changeset/gesture-pan.md b/.changeset/gesture-pan.mddeleted file mode 100644index 12eb02fc42..0000000000--- a/.changeset/gesture-pan.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the pan gesture recognizer, with UIKit's measured hysteresis and velocity filter. Not exported from the package entry point; no component uses it yet.--@vjeuxdiff --git a/.changeset/gesture-recognizer-core.md b/.changeset/gesture-recognizer-core.mddeleted file mode 100644index 0b0bfc3892..0000000000--- a/.changeset/gesture-recognizer-core.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the gesture recognizer core for touch presentations: UIKit's recognizer state machine and the arena that settles which recognizer owns a touch. Not exported from the package entry point; no component uses it yet.--@vjeuxdiff --git a/.changeset/gesture-tap-long-press.md b/.changeset/gesture-tap-long-press.mddeleted file mode 100644index 9ef786da65..0000000000--- a/.changeset/gesture-tap-long-press.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: tap and long-press gesture recognizers with UIKit's measured thresholds. Not exported from the package entry point; no component uses them yet.--@vjeuxdiff --git a/.changeset/hover-layers-open-on-tap.md b/.changeset/hover-layers-open-on-tap.mddeleted file mode 100644index f147ebbe3b..0000000000--- a/.changeset/hover-layers-open-on-tap.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Tooltip and HoverCard answer a touch only once it is a tap. On a touch screen they used to open as soon as a finger landed on a trigger that performs no action, so a scroll that started on an info icon or an abbreviation opened its tooltip and left it open, and a finger resting on the trigger opened it too. Now the tap opens the layer when the finger lifts, and a touch that turns into a scroll never opens it, the way a tap on iOS behaves. A tap-opened tooltip or card closes when a tap outside lifts, or as soon as a scroll that starts outside takes the touch, which is when iOS dismisses a popover; before, it closed the moment a finger landed anywhere else. Triggers that perform an action keep their tap, and `touchTrigger` keeps its meaning.--@vjeuxdiff --git a/.changeset/icon-theme-size-dimensions.md b/.changeset/icon-theme-size-dimensions.mddeleted file mode 100644index ee28a1bf48..0000000000--- a/.changeset/icon-theme-size-dimensions.md+++ /dev/null@@ -1,8 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch------[feat] A theme sets the dimension of each Icon size: `width` and `height` in `px` or `rem` on `components.icon['size:sm']` (or `xsm`, `md`, `lg`) resize that size's glyph, for semantic icon names and for SVG components passed to `Icon`, in runtime and built themes alike. Before, those properties sized the box around a semantic icon but not its 1em artwork, and an app that compiles StyleX without CSS layers let the icon's own size win over the theme. A size the theme does not style still renders at 12, 16, 20, or 24px at a 16px root and scales with the root font size. `astryx docs theme` gains an Icon sizes section.--@imdreamrunnerdiff --git a/.changeset/input-group-member-selector.md b/.changeset/input-group-member-selector.mddeleted file mode 100644index 21c95769eb..0000000000--- a/.changeset/input-group-member-selector.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: InputGroup's edge rules name group members by an internal marker instead of a universal selector. No visible or behavior change.--@cixzhangdiff --git a/.changeset/item-swipe-pinch-zoom.md b/.changeset/item-swipe-pinch-zoom.mddeleted file mode 100644index e0ee7772be..0000000000--- a/.changeset/item-swipe-pinch-zoom.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A row with `swipeActions` no longer blocks pinch-zoom. A pinch that started on a swipeable `Item` or `ListItem` did nothing, because the row declared `touch-action: pan-y`, and a sideways pinch could also be taken as a swipe. The row now leaves pinch to the browser (`pan-y pinch-zoom`), and a second finger that lands before the swipe has begun, on the row or anywhere else, hands the touch to the browser, so the page zooms and the row stays where it is. One-finger swipes and vertical scrolling are unchanged.--@vjeuxdiff --git a/.changeset/layer-closed-mount-no-style-read.md b/.changeset/layer-closed-mount-no-style-read.mddeleted file mode 100644index 56091064a7..0000000000--- a/.changeset/layer-closed-mount-no-style-read.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[perf] Pages with many closed popovers, tooltips and menus mount faster. A layer that renders closed outside an inline or interactive parent no longer reads computed style when it mounts; it reads its writing direction when it first opens, before its first frame. On a page with hundreds of closed layers, each of those mount-time reads forced its own style recalculation. Open layers look and behave as before, in right-to-left and vertical text too.--@cixzhangdiff --git a/.changeset/layer-slot-second-render.md b/.changeset/layer-slot-second-render.mddeleted file mode 100644index 043c32ecea..0000000000--- a/.changeset/layer-slot-second-render.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[perf] useLayer: placing a context layer no longer re-renders its host. The hook still resolves where the layer goes from its inert marker once the marker is in the DOM, but it now hands that mount to an internal slot that renders the marker and the layer, so the render that places the layer is the slot's alone. A Tooltip, Selector or ComplexSelector that mounts closed renders once; a Popover or DropdownMenu keeps only the renders its own state costs. The host still renders when a resolved mount is replaced by a render call that moved to another host. The DOM, server markup, hydration and `lazyMount` are unchanged.--@vjeuxdiff --git a/.changeset/layer-touch-reduced-motion-fade.md b/.changeset/layer-touch-reduced-motion-fade.mddeleted file mode 100644index 8284f4b7a3..0000000000--- a/.changeset/layer-touch-reduced-motion-fade.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] With Reduce Motion on, a Tooltip, HoverCard, Popover, menu or other layer that opens under a finger now fades in, with no slide and no scale, in 200 ms or less, instead of appearing at once. Under a mouse it still appears at once, and without Reduce Motion the entrance is unchanged.--@vjeuxdiff --git a/.changeset/layout-codemod-const-config.md b/.changeset/layout-codemod-const-config.mddeleted file mode 100644index 10593fa458..0000000000--- a/.changeset/layout-codemod-const-config.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx upgrade` no longer reports an error on an `astryx.config` written as `const config = {...}; export default config;`, the shape generated configs use. The `migrate-layout-components-to-experimental` codemod now follows a default-exported identifier to its top-level `const` binding when the binding is not exported any other way and nothing else references it, so a config without `layout` is left unchanged and one with `layout.components` is migrated.--@ejhammonddiff --git a/.changeset/layout-edge-padding-no-has-universal.md b/.changeset/layout-edge-padding-no-has-universal.mddeleted file mode 100644index 6b22d28fc0..0000000000--- a/.changeset/layout-edge-padding-no-has-universal.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `Layout` no longer ships a `:has()` on the layout followed by a universal `*` selector for the padding that collapses next to a `LayoutHeader` or `LayoutFooter` without a divider. That selector shape can make a browser restyle everything inside the layout on each change within it, which costs the most in long documents. `LayoutHeader` and `LayoutFooter` now carry internal markers, and Layout's middle row reads them with sibling selectors. Rendering is unchanged for a Layout's own content, and a Layout nested in another Layout's content or panels still inherits the outer collapse. One case changes: a Layout nested inside a `LayoutHeader` or `LayoutFooter` that has no divider no longer takes that outer collapse, so its content keeps its own inner padding beside its own divider (16px at the default spacing) instead of 0px.--@cixzhangdiff --git a/.changeset/lightbox-dynamic-viewport.md b/.changeset/lightbox-dynamic-viewport.mddeleted file mode 100644index e26638b23d..0000000000--- a/.changeset/lightbox-dynamic-viewport.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Lightbox: the viewer is as tall as the visible viewport (`100dvh`), so on an iPhone Safari's bottom toolbar no longer covers its bottom, where a gallery's caption sits.--@vjeuxdiff --git a/.changeset/lightbox-open-before-items.md b/.changeset/lightbox-open-before-items.mddeleted file mode 100644index 3fe7f1725e..0000000000--- a/.changeset/lightbox-open-before-items.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Lightbox: a viewer opened before its first item arrives now opens when that item does. It used to stay closed, its dialog never shown.--@vjeuxdiff --git a/.changeset/lightbox-rtl-arrow-keys.md b/.changeset/lightbox-rtl-arrow-keys.mddeleted file mode 100644index dd2c1c2237..0000000000--- a/.changeset/lightbox-rtl-arrow-keys.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Lightbox's Left and Right arrow keys now follow the writing direction. In a right-to-left page the gallery's Next button sits on the left, and ArrowLeft now moves to the next item and ArrowRight to the previous one, matching the buttons. Before, ArrowLeft always went to the previous item, so in RTL the keys moved against their buttons. Panning a zoomed image with the arrow keys is unchanged in both directions: the image is not mirrored, so ArrowRight still reveals what is to its right.--@vjeuxdiff --git a/.changeset/list-item-aria-current-doc.md b/.changeset/list-item-aria-current-doc.mddeleted file mode 100644index f655556c3b..0000000000--- a/.changeset/list-item-aria-current-doc.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] `ListItem`'s documentation says what `isSelected` does: it marks the row as the current item with `aria-current="true"`. It used to say `aria-selected`, which a list item cannot carry and which the component has not set since 0.1.9.--@vjeuxdiff --git a/.changeset/list-number-markers-right-aligned.md b/.changeset/list-number-markers-right-aligned.mddeleted file mode 100644index 8f96e1180c..0000000000--- a/.changeset/list-number-markers-right-aligned.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Numbered List and Markdown markers end on one edge, with tabular figures, so every period in a list lines up as native list markers do. In List, a counter wider than its marker hangs toward the start before it widens the shared column. Markdown's non-swipe document lists instead keep the ordinary text inset and let whole counters paint outside it, matching RichText's native outside markers even beyond the marker gutter. Single-digit numbers, now right-aligned in their marker, sit a few pixels closer to their text.-@ernesttdiff --git a/.changeset/list-number-markers.md b/.changeset/list-number-markers.mddeleted file mode 100644index 9d08f73d3b..0000000000--- a/.changeset/list-number-markers.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Keep multi-digit List and Markdown counters on one line in a shared number column, so sibling text and nested lists stay aligned. Bullets and the text inset of short-only lists without task items retain their existing spacing; numbered rows beside task items move to share the checkbox's text start. Short numbers are right-aligned in their marker, moving the digits a few pixels closer to their text. Markdown task lists with nested or other block content place each checkbox on its item's first line and name it by that item's own text, instead of centering it against the whole body and naming it by all nested content inside a “Task list” group; those lists retain list semantics without that extra group. Paragraph-only pure task lists are unchanged. Browsers without CSS subgrid keep readable, unbroken counters in the existing flex layout, without the shared-column alignment enhancement.-@imdreamrunnerdiff --git a/.changeset/localize-pasted-text-counts-file-size-limits-and-r40m.md b/.changeset/localize-pasted-text-counts-file-size-limits-and-r40m.mddeleted file mode 100644index 484bd7cb78..0000000000--- a/.changeset/localize-pasted-text-counts-file-size-limits-and-r40m.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Localize pasted-text counts, spoken shortcut names and Ctrl/Esc keycaps; format file-size limits with provider-locale digits and translatable units-@nynexman4464diff --git a/.changeset/lookup-suggestion-recall.md b/.changeset/lookup-suggestion-recall.mddeleted file mode 100644index 4fcb8ba61d..0000000000--- a/.changeset/lookup-suggestion-recall.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx component <name>` now suggests a component whose whole name is part of the typed name (a wrapper or prefixed name) when nothing else matches, instead of no suggestions.--@josephfarinadiff --git a/.changeset/lookup-suggestions-stop-at-weaker.md b/.changeset/lookup-suggestions-stop-at-weaker.mddeleted file mode 100644index 1e7d86fdad..0000000000--- a/.changeset/lookup-suggestions-stop-at-weaker.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] When `astryx component`, `astryx template` or `astryx docs` names nothing, the suggestions now stop where the matches get weaker, so a strong first suggestion is no longer followed by unrelated entries. A component list keeps its first two suggestions and, after them, only suggestions about as close as the first or a close spelling of the whole typed name. In a template list, and in the docs list for an unknown topic that is not a route, when the closest entry carries every typed word, only entries that carry every typed word stay; when it carries some of them, entries that carry none are left out. One-letter words do not count. A name that shares no word with any entry still gets the full list, and an unknown route still suggests every child of its namespace. Lists only get shorter, and every suggestion still names a real entry.--@josephfarinadiff --git a/.changeset/markdown-code-languages.md b/.changeset/markdown-code-languages.mddeleted file mode 100644index dcdea03db9..0000000000--- a/.changeset/markdown-code-languages.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `Markdown` takes `codeLanguages`, a list of CodeBlock language values, each imported on its own or made with `createCodeLanguage`. A fence whose language word names a listed value renders with that value, ahead of a built-in language with the same name. A `diff-<name>` fence gets the diff layer over that value.--@cixzhangdiff --git a/.changeset/markdown-fr23-thread-clock.md b/.changeset/markdown-fr23-thread-clock.mddeleted file mode 100644index a120341931..0000000000--- a/.changeset/markdown-fr23-thread-clock.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Markdown's FR23 performance bench times each sampling window on the calling thread's CPU clock instead of the whole process's, so CPU spent by V8's background threads or a worker no longer counts toward either side. Test-only; `Markdown`'s behavior does not change.--@vjeuxdiff --git a/.changeset/menu-hover-focus-not-visible.md b/.changeset/menu-hover-focus-not-visible.mddeleted file mode 100644index 78c81c5363..0000000000--- a/.changeset/menu-hover-focus-not-visible.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] DropdownMenu, ContextMenu: after a pointer press, a row the mouse rests on, or a held press is dragged over, takes focus without matching `:focus-visible`. A plain focus inherited the state from the focus before it (the menu after a pointer open), so any keyboard-only focus style, a theme's or an app's, painted on the row under the mouse. That focus now follows the last input, as other programmatic focus in Astryx does: after a keyboard open, or a key press, the indicator stays. Checkbox, radio and sub-menu rows, and the ContextMenu and Breadcrumbs menus built on them, follow. Browsers without the focus option (Chrome and Edge before 145, Safari before 18.4) keep the earlier behavior.--@vjeuxdiff --git a/.changeset/menu-sheet-nothing-at-rest.md b/.changeset/menu-sheet-nothing-at-rest.mddeleted file mode 100644index 54d32c6ada..0000000000--- a/.changeset/menu-sheet-nothing-at-rest.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] DropdownMenu, MoreMenu and ContextMenu: a menu presented as a bottom sheet (`presentation="bottom-sheet"`, or `"adaptive"` on a phone) no longer keeps its closed sheet and every item mounted while the menu is closed. The sheet mounts as it opens and unmounts after its exit, with focus still returning to the trigger. The open sheet also renders two fewer wrapper elements, with the same layout.--@cixzhangdiff --git a/.changeset/meta-astryx-repository-links.md b/.changeset/meta-astryx-repository-links.mddeleted file mode 100644index 4353d54d38..0000000000--- a/.changeset/meta-astryx-repository-links.md+++ /dev/null@@ -1,16 +0,0 @@-----'@astryxdesign/build': patch-'@astryxdesign/cli': patch-'@astryxdesign/core': patch-'@astryxdesign/richtext': patch-'@astryxdesign/theme-butter': patch-'@astryxdesign/theme-chocolate': patch-'@astryxdesign/theme-gothic': patch-'@astryxdesign/theme-matcha': patch-'@astryxdesign/theme-neutral': patch-'@astryxdesign/theme-stone': patch-'@astryxdesign/theme-y2k': patch------[docs] Point package metadata and project links at the `meta/astryx` repository.-@cixzhangdiff --git a/.changeset/metadata-list-columns-selector.md b/.changeset/metadata-list-columns-selector.mddeleted file mode 100644index 66794b83ea..0000000000--- a/.changeset/metadata-list-columns-selector.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx upgrade` to 0.7 no longer rewrites an app's own class on MetadataList, such as `.astryx-metadata-list.app-compact-list`, into a `[data-columns="app-compact-list"]` selector that never matches. Only the column values MetadataList emitted (`single`, `multi`, and `columns-<n>`) become `data-columns` selectors. (#7982)--@ejhammonddiff --git a/.changeset/mobile-nav-width-cap.md b/.changeset/mobile-nav-width-cap.mddeleted file mode 100644index 5cf0b5d556..0000000000--- a/.changeset/mobile-nav-width-cap.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `MobileNav` is never wider than 85% of the viewport, as its `width` documentation says. A 320 px drawer on a 320 px phone used to cover the whole screen and leave no backdrop to tap; it is now 272 px wide and leaves a 48 px strip of the page beside it, and a tap on that strip closes it. On wider screens the drawer keeps its `width`.--@vjeuxdiff --git a/.changeset/mobile-power-search-discovery.md b/.changeset/mobile-power-search-discovery.mddeleted file mode 100644index 92135d6c88..0000000000--- a/.changeset/mobile-power-search-discovery.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx discover` lists the experimental MobilePowerSearch component from `@astryxdesign/lab`. (#7983)--@imdreamrunnerdiff --git a/.changeset/multi-selector-caller-labelledby.md b/.changeset/multi-selector-caller-labelledby.mddeleted file mode 100644index db87bf149d..0000000000--- a/.changeset/multi-selector-caller-labelledby.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] MultiSelector: a caller's `aria-labelledby` now reaches the built-in trigger. Before, MultiSelector replaced it with its own value, so the trigger lost the extra name (standalone it had no `aria-labelledby` at all). Now the caller's ids follow the field's own label: `label="Fruits" aria-labelledby="lunch-heading"` names the trigger "Fruits Lunch", and inside an InputGroup the group label comes first. With `renderTrigger`, the caller's control still receives the caller's `aria-labelledby` as given. Triggers without a caller `aria-labelledby` are unchanged. No API changes.--@kyu-rongdiff --git a/.changeset/nav-heading-menu-item-disabled-link.md b/.changeset/nav-heading-menu-item-disabled-link.mddeleted file mode 100644index 5a99a918a3..0000000000--- a/.changeset/nav-heading-menu-item-disabled-link.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A disabled `NavHeadingMenuItem` with `href` no longer navigates (`spec:AST-085` FR2). Before, it kept its link destination and only skipped `onClick`, so a click, a middle-click, or assistive-technology activation still followed the link. It now renders a plain `<a>` with no `href`, still reports `aria-disabled`, and does not use a custom `LinkProvider` component. The disabled link row now carries `tabIndex={-1}`: it stays focusable but is no longer a Tab stop (before, it was a page Tab stop only because it kept its `href`; `spec:AST-085` FR1). A link row that becomes disabled or enabled while focused keeps focus (`spec:AST-085` FR4). Apps need no code change; an enabled item is unchanged.--@parinith-webdiff --git a/.changeset/nav-menus-no-text-selection.md b/.changeset/nav-menus-no-text-selection.mddeleted file mode 100644index 371641f02a..0000000000--- a/.changeset/nav-menus-no-text-selection.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A mouse slide across the items of NavHeadingMenu or TabMenu no longer selects their text. In an expanded SideNavHeading, which stays open after a pick, the selection used to stay on the item the press began on. Caller content beside NavHeadingMenu's items stays selectable.--@cixzhangdiff --git a/.changeset/nav-menus-track-held-pointer.md b/.changeset/nav-menus-track-held-pointer.mddeleted file mode 100644index a4f6c20941..0000000000--- a/.changeset/nav-menus-track-held-pointer.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feature] NavHeadingMenu, TopNavMenu, SideNavHeading's menu, TopNavHeading's product menu, BreadcrumbItem's menu and TabMenu track a held pointer across their items, as DropdownMenu does: a press (finger, pen or mouse) that slides across the items acts on the one it lifts on, once, with the highlight following the pointer, and a mouse released outside closes the menu. A link item is no longer draggable, so a mouse press that slides to another item is not a drag. Keyboard and assistive-technology behavior is unchanged. No API changes.--@cixzhangdiff --git a/.changeset/number-input-caller-labelledby.md b/.changeset/number-input-caller-labelledby.mddeleted file mode 100644index fd76a60ab2..0000000000--- a/.changeset/number-input-caller-labelledby.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] NumberInput: a caller's `aria-labelledby` now reaches the input. Before, NumberInput replaced it with its own value, so the input lost the extra name (standalone it had no `aria-labelledby` at all). Now the caller's ids follow the field's own label: `label="Amount" aria-labelledby="shipping-heading"` names the input "Amount Shipping", and inside an InputGroup the group label comes first. Inputs without a caller `aria-labelledby` are unchanged. No API changes.--@kyu-rongdiff --git a/.changeset/number-input-focusable-disabled.md b/.changeset/number-input-focusable-disabled.mddeleted file mode 100644index 63b2d6745f..0000000000--- a/.changeset/number-input-focusable-disabled.md+++ /dev/null@@ -1,9 +0,0 @@-----'@astryxdesign/core': patch------[fix] NumberInput: a disabled field now keeps its place in the tab order, so keyboard and screen-reader users can reach it and hear that it is unavailable (WCAG 2.2 SC 2.1.1 Keyboard, 4.1.2 Name, Role, Value and 2.4.7 Focus Visible; `spec:AST-085` FR1–FR3 and FR6). It exposes `aria-disabled="true"` and is read-only instead of carrying the native `disabled` attribute, as it already did with a `disabledMessage`; it is still dimmed, cannot be edited or stepped, and is left out of form submission. Like a natively disabled field, it runs no caller event handler other than focus and blur, and Enter does not submit its form. Its number steppers expose `aria-disabled` too, and under keyboard focus the field shows its focus ring, dimmed with the rest of the field. The Pagination page box follows.--Part of #7814.--@cixzhangdiff --git a/.changeset/overlay-dropdown-menu-group-host-props.md b/.changeset/overlay-dropdown-menu-group-host-props.mddeleted file mode 100644index b88802b506..0000000000--- a/.changeset/overlay-dropdown-menu-group-host-props.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `Overlay`, `DropdownMenuGroup` and `MobileNavToggle` now forward host attributes and DOM handlers (`id`, `data-*`, `aria-*`, event handlers) to the element each one owns, as other DOM-owning components do. Before, `Overlay` and `DropdownMenuGroup` accepted only `xstyle`, `className`, `style` and `ref` and dropped everything else, so a test id or analytics attribute on either never reached the page; `MobileNavToggle` also forwarded `data-testid`, but no other `data-*`, `id`, `aria-*` or handler. Built-in behavior stays component-owned: `Overlay`'s touch toggle and `MobileNavToggle`'s drawer toggle run on every press, before a caller handler; `DropdownMenuGroup` keeps its `role="group"` and, while it has a `title`, keeps that title as its name; `MobileNavToggle` keeps its `aria-expanded` and `aria-controls`.--@kentonquatmandiff --git a/.changeset/popover-cancel-stale-autofocus.md b/.changeset/popover-cancel-stale-autofocus.mddeleted file mode 100644index 04ac4434bf..0000000000--- a/.changeset/popover-cancel-stale-autofocus.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] usePopover: a popover that closes or unmounts before its first frame no longer moves focus into its hidden content. Auto-focus waits a frame for the content to mount, and that frame is now cancelled with the open, so pressing Escape right after opening a Popover or a collapsed SideNav submenu leaves focus on the trigger.--@vjeuxdiff --git a/.changeset/popover-focus-region-outside-tab.md b/.changeset/popover-focus-region-outside-tab.mddeleted file mode 100644index 853cde19a1..0000000000--- a/.changeset/popover-focus-region-outside-tab.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Popover: an open popover no longer pulls in a Tab pressed elsewhere on the page. Keyboard users can move through the rest of the page in order while a popover is open, for example a list next to a non-modal comment popover. Focus inside the popover still cycles with Tab and Shift+Tab, and Escape still closes it and returns focus to its trigger. `useFocusTrap` applies the same rule: it holds focus that is inside its container and leaves Tabs that start outside to the page. This meets `component:Popover` DEC-9. Fixes #7687.--@cixzhangdiff --git a/.changeset/popover-presentation.md b/.changeset/popover-presentation.mddeleted file mode 100644index 196ebd9268..0000000000--- a/.changeset/popover-presentation.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feature] Popover takes `presentation`, with the values DropdownMenu and Selector use: `'popover'` (the default, unchanged) anchors it to its trigger, `'bottom-sheet'` presents its content in a modal BottomSheet labeled by `label`, and `'adaptive'` uses the BottomSheet on a compact touch screen (a phone) and the anchored popover elsewhere, the way iOS presents a popover on an iPhone. Compact is the theme's compact definition: narrower than its `md` width point or shorter than 500 px. In a sheet, `placement`, `alignment`, `width`, `role`, `isModal` and `hasAutoFocus` do not apply, and `xstyle`, `className` and `style` style the sheet's panel. The sheet loads only when a popover can present one.--@vjeuxdiff --git a/.changeset/popover-second-document.md b/.changeset/popover-second-document.mddeleted file mode 100644index a28dc85681..0000000000--- a/.changeset/popover-second-document.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A `Popover` rendered into a second document through a portal, such as a same-origin iframe or a Document Picture-in-Picture window, now focuses its first control on open, keeps Tab inside, closes on Escape, and returns focus to its trigger, as it does in the page. Its trigger there stays the popover's invoker `source`.--@vjeuxdiff --git a/.changeset/powersearch-result-count-strictmode.md b/.changeset/powersearch-result-count-strictmode.mddeleted file mode 100644index dbdc94490c..0000000000--- a/.changeset/powersearch-result-count-strictmode.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] PowerSearch no longer announces its initial `resultCount` on mount under React StrictMode. The result-count live-region effect guarded its first run with a mounted flag that StrictMode's effect replay reset, so the count present on mount was spoken unprompted; the guard now compares against the last announced text, so only a change after mount is announced in every render mode.--@imdreamrunnerdiff --git a/.changeset/press-coarse-device-mouse-keyboard.md b/.changeset/press-coarse-device-mouse-keyboard.mddeleted file mode 100644index 0c640fa632..0000000000--- a/.changeset/press-coarse-device-mouse-keyboard.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] On a phone or tablet, a press made with a mouse, a trackpad or the Space key now shows the pressed state. Touch devices drop the CSS `:active` press so a finger only sees the touch press model, but that rule keys on the device's primary pointer, so a tablet with a trackpad and keyboard (or a phone with a mouse) lost the pressed state for every press that was not a finger. The touch press controller now paints those presses on such devices with the same pixels a desktop press has: at once, held while the button or key is down, faded at the release. As on a desktop, Space paints only a focused button that is itself the pressed surface (a checkbox's or radio's row stays at rest), and a menu row keeps the menu's own highlight. Desktop presses and finger presses are unchanged.--@vjeuxdiff --git a/.changeset/published-type-declarations-use-fully-specified--rphc.md b/.changeset/published-type-declarations-use-fully-specified--rphc.mddeleted file mode 100644index d74f6c0192..0000000000--- a/.changeset/published-type-declarations-use-fully-specified--rphc.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/richtext': patch------[fix] Published type declarations use fully specified relative imports, so projects compiled with `moduleResolution: NodeNext` resolve them (#7702)-@harjothkharadiff --git a/.changeset/radio-list-press-no-descendant-has.md b/.changeset/radio-list-press-no-descendant-has.mddeleted file mode 100644index b82842f46f..0000000000--- a/.changeset/radio-list-press-no-descendant-has.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `RadioList`'s pressed circle no longer comes from a `:has()` check that reached every element under the row, so a large page no longer restyles everything under each row whenever anything inside it changes. The row is pressed and the circle shows it exactly as before, and a link or button inside the row still keeps its own press.--@cixzhangdiff --git a/.changeset/resolve-snap-point.md b/.changeset/resolve-snap-point.mddeleted file mode 100644index c051e8fb34..0000000000--- a/.changeset/resolve-snap-point.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the motion foundation has one release policy, `motion/resolveSnapPoint.ts` (where a release lands: a flick goes at least to the next snap point, a release moving back toward its start cancels to it), on the `selectSnapPoint` primitive; paging moves to `motion/selectPage.ts` on top of it. No behavior change.--@cixzhangdiff --git a/.changeset/richtext-code-corner-column.md b/.changeset/richtext-code-corner-column.mddeleted file mode 100644index 1c27f26ff5..0000000000--- a/.changeset/richtext-code-corner-column.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/richtext': patch------[fix] In `RichTextEditor` and `RichTextView`, a code block that names no language now leaves room for its corner Copy button. A long line wraps before the button instead of running under it. The block is as tall as the same fence in `Markdown`, so switching between reading and editing no longer moves the content below it.--@cixzhangdiff --git a/.changeset/richtext-code-languages.md b/.changeset/richtext-code-languages.mddeleted file mode 100644index c26460fb6a..0000000000--- a/.changeset/richtext-code-languages.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/richtext': patch------[feat] `RichTextEditor` and `RichTextView` take `codeLanguages`, the same list of CodeBlock language values that `Markdown` takes. A fence named by a listed value is coloured with that value and labelled with its name, so reading and editing match.--@cixzhangdiff --git a/.changeset/scroll-edges-without-style-reads.md b/.changeset/scroll-edges-without-style-reads.mddeleted file mode 100644index be07c46378..0000000000--- a/.changeset/scroll-edges-without-style-reads.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[perf] Scrolling a `ScrollableArea`, or any viewport that uses `useScrollableArea` (Table, CodeBlock, BottomSheet's body), no longer reads computed style on each frame. Before, every scroll event triggered a full measurement in the next animation frame: four computed-style reads plus geometry. When something else on the page had changed style earlier in that frame, this forced a style recalculation from script. Now the scroll event works out the logical edges from box geometry alone, with no computed style and no frame request. Size, style and writing-mode changes still trigger a full measurement, at most once per frame, and so does a scroll whose offset the measured writing direction rules out (a direction changed by a stylesheet alone).--@vjeuxdiff --git a/.changeset/scroll-to-top-reduced-motion-note.md b/.changeset/scroll-to-top-reduced-motion-note.mddeleted file mode 100644index f8fb37fba3..0000000000--- a/.changeset/scroll-to-top-reduced-motion-note.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the UIKit scroll table's scroll-to-top note says that under Reduce Motion a tap-started scroll to the top cross-fades on a coarse pointer and jumps otherwise, since only momentum after a throw keeps decaying. No behavior change.--@cixzhangdiff --git a/.changeset/scrollable-area-first-frame-tab-stop.md b/.changeset/scrollable-area-first-frame-tab-stop.mddeleted file mode 100644index e7e91345cf..0000000000--- a/.changeset/scrollable-area-first-frame-tab-stop.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A scroll viewport that owns keyboard access (`ScrollableArea`, and the Table, CodeBlock, BottomSheet and Schedule viewports built on the same hook) is a tab stop from the first frame its content overflows. Content that arrived already overflowing, such as loaded data replacing a loading state, used to scroll for at least one animation frame, and longer on a busy page, before the viewport joined the tab order. During that time a keyboard user could not reach it and an accessibility audit reported `scrollable-region-focusable`.--@cixzhangdiff --git a/.changeset/scrollable-area-touch-indicator.md b/.changeset/scrollable-area-touch-indicator.mddeleted file mode 100644index 8dc91d2444..0000000000--- a/.changeset/scrollable-area-touch-indicator.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] On touch screens, `ScrollableArea` keeps the platform's own scroll indicator. Its neutral `scrollbar-color` replaced iOS Safari's indicator with a faint bar that was hard to see while scrolling and also showed in the gap a pull opens; iOS now draws its own indicator, only while scrolling. Mouse and trackpad scrollbars keep the neutral colour. To keep the neutral colour on touch screens too, set `scrollbarColor` through the `xstyle` prop.--@vjeuxdiff --git a/.changeset/segmentedcontrol-caller-describedby.md b/.changeset/segmentedcontrol-caller-describedby.mddeleted file mode 100644index 5b2d213231..0000000000--- a/.changeset/segmentedcontrol-caller-describedby.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] SegmentedControl keeps a caller's `aria-describedby`. The radiogroup always replaced it with the disabled-reason tooltip id, or removed it when no reason showed, so the caller's ids never reached the accessible description. The group is now described by the caller's ids and then the disabled reason, the same order RadioList uses.--@kyu-rongdiff --git a/.changeset/selectablecard-not-single-select-docs.md b/.changeset/selectablecard-not-single-select-docs.mddeleted file mode 100644index 7ee27dd3ce..0000000000--- a/.changeset/selectablecard-not-single-select-docs.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[docs] SelectableCard's guidance no longer recommends it for single-select groups. Each card is a checkbox, so a single-select set built from it is announced as multi-select, with one tab stop per card and no arrow-key navigation between them. Its guidance now covers multi-select groups only.--@cixzhangdiff --git a/.changeset/selector-caller-labelledby.md b/.changeset/selector-caller-labelledby.mddeleted file mode 100644index b2ef9d5ac4..0000000000--- a/.changeset/selector-caller-labelledby.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Selector: a caller's `aria-labelledby` now reaches the trigger. Before, Selector replaced it with its own value, so the trigger lost the extra name (standalone it had no `aria-labelledby` at all). Now the caller's ids follow the field's own label: `label="Fruit" aria-labelledby="lunch-heading"` names the trigger "Fruit Lunch", and inside an InputGroup the group label comes first. Triggers without a caller `aria-labelledby` are unchanged. No API changes.--@kyu-rongdiff --git a/.changeset/selector-sheet-active-option-mounted.md b/.changeset/selector-sheet-active-option-mounted.mddeleted file mode 100644index 1ca9262df2..0000000000--- a/.changeset/selector-sheet-active-option-mounted.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Selector's touch sheet no longer points screen readers at an option that isn't there yet. On the first open in the bottom-sheet presentation, the trigger used to report the active option (`aria-activedescendant`) while the sheet was still loading and none of its options existed. The trigger now names the active option only once the sheet has rendered it.--@cixzhangdiff --git a/.changeset/side-nav-initial-collapsed-tooltip.md b/.changeset/side-nav-initial-collapsed-tooltip.mddeleted file mode 100644index 30f1648807..0000000000--- a/.changeset/side-nav-initial-collapsed-tooltip.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] SideNav: a collapsed rail item's tooltip now binds to the link or button itself rather than the row around it, so the focusable control is the WAI-ARIA tooltip pattern's trigger and is described by the tooltip (`aria-describedby`) from its first render. Keyboard focus on it now shows the label. As with other link and button tooltips, a touch tap activates the control without opening the tooltip. A disabled item still shows its label on hover.--@ernestt @thewebartisan7diff --git a/.changeset/sidenav-heading-end-content-beside-link.md b/.changeset/sidenav-heading-end-content-beside-link.mddeleted file mode 100644index 5d0be2bbbd..0000000000--- a/.changeset/sidenav-heading-end-content-beside-link.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] SideNavHeading: with `headingHref` as its only link, `headerEndContent` now renders beside the heading link instead of inside it. A button placed there was nested in the link, so pressing it also followed the link. The link's accessible name no longer includes the end content.--@cixzhangdiff --git a/.changeset/sidenav-rail-motion.md b/.changeset/sidenav-rail-motion.mddeleted file mode 100644index 2819db30cd..0000000000--- a/.changeset/sidenav-rail-motion.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] SideNav's rail no longer snaps when it collapses or expands. Layout snaps to the new width at once, the rail covers or reveals its labels with a clip and ends in its real collapsed state, and inside AppShell the content slides with it, its old line wrapping fading out over the new one, all on one motion (`springs.settle`). Under Reduce Motion it cross-fades with a finger and changes at once otherwise. Nothing animates a width, and no new props.--@cixzhangdiff --git a/.changeset/skeleton-pulse-compositor.md b/.changeset/skeleton-pulse-compositor.mddeleted file mode 100644index 3ca533de8b..0000000000--- a/.changeset/skeleton-pulse-compositor.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Skeleton keeps pulsing in Safari while a script runs. Its stepped pulse used a `steps()` timing function, which Safari never animates off the main thread, so the placeholders froze for as long as the page ran JavaScript; Chromium and Firefox were unaffected. The same ten steps are now written as keyframes with a linear timing function, which every engine animates on its compositor. The pulse looks and times exactly as before, including its stagger and reduced-motion behavior.--@vjeuxdiff --git a/.changeset/slider-caller-labelledby.md b/.changeset/slider-caller-labelledby.mddeleted file mode 100644index d23c6ea090..0000000000--- a/.changeset/slider-caller-labelledby.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Slider keeps a caller's `aria-labelledby`. The thumb of a single slider and the group of a range slider always replaced it with the label id, so the caller's ids never reached the accessible name. The control is now named by its label and then the caller's ids, the same order RadioList and TimeInput use.--@kyu-rongdiff --git a/.changeset/slider-lost-capture-drag-scope.md b/.changeset/slider-lost-capture-drag-scope.mddeleted file mode 100644index e54a1dc64d..0000000000--- a/.changeset/slider-lost-capture-drag-scope.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Slider: the document listener that ends a drag when its pointer capture is lost now exists only while a drag is in progress, so an idle slider no longer holds a document-level listener for its whole lifetime. A drag still ends when the control is replaced mid-drag (a FormLayout direction change).--@cixzhangdiff --git a/.changeset/slider-one-pointer-per-drag.md b/.changeset/slider-one-pointer-per-drag.mddeleted file mode 100644index 32ad1c3f14..0000000000--- a/.changeset/slider-one-pointer-per-drag.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Slider: a drag belongs to the pointer that started it. A second finger that lands on the slider, moves or lifts during a drag no longer moves the value, takes over the drag or ends it, and two fingers can still drag two sliders at once. A drag whose pointer capture is lost without a pointer up also ends, with one `onChangeEnd`, so the slider keeps answering new presses. Introduced in #8152; final-state evidence (#8284).--@vjeuxdiff --git a/.changeset/status-color-roles.md b/.changeset/status-color-roles.mddeleted file mode 100644index 0d51439653..0000000000--- a/.changeset/status-color-roles.md+++ /dev/null@@ -1,32 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch-'@astryxdesign/richtext': patch-'@astryxdesign/theme-neutral': patch-'@astryxdesign/theme-butter': patch-'@astryxdesign/theme-chocolate': patch-'@astryxdesign/theme-gothic': patch-'@astryxdesign/theme-matcha': patch-'@astryxdesign/theme-stone': patch-'@astryxdesign/theme-y2k': patch------[feat] Status colours now have a role for each surface, and Info is a new status. For each of info, success, warning, and error: `--color-<status>` is the strong fill and `--color-on-<status>` is content on it, at 4.5:1 or more; `--color-<status>-muted` is the pale fill, with `--color-on-<status>-muted` content; and `--color-text-<status>` is readable status text on the page and cards, with `--color-icon-<status>` and `--color-border-<status>` (status icons and borders) defaulting to it. `--color-info`, `--color-on-info`, `--color-info-muted`, and the other Info roles are new and independent of the accent. Tailwind gains `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` (the status text role). Introduced in #7657; final-state evidence (#8729).--`--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. Tailwind now projects each status by paint property: `text-`, `decoration-`, `placeholder-`, and `caret-<status>` read the status text role, and `border-`, `divide-`, `outline-`, and `ring-<status>` read the status border role, so status text and lines are readable on the page; `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadow colours, and gradients keep the strong fill. for example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`, and `text-success` is `#09441F` instead of `#0D8626`. To keep the fill colour on text, use `text-[var(--color-warning)]`.--What changes on screen:--- Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `--color-info` (`#0064E0`) instead of the accent; in dark mode the accent was `#2694FE`.-- Icon `color="info|success|warning|error"`, Stepper status glyphs, and Chat tool-call status icons use the icon roles, which are the readable text colours. For example, Core's success icon is now `#09441F` (light) instead of `#0D8626`.-- Input and FileInput status borders use the border roles. Core's light warning border is now `#753F07` instead of `#E9AF08`. Butter's light success and warning input rims are now mid-ramp stops that reach 3:1.-- Banner paints its built-in title, description, icon, and controls with the on-muted roles, and fills Info with `--color-info-muted`.-- Status fills keep a visible boundary in forced-colors mode.-- Chocolate and Matcha's `--color-on-success` and `--color-on-error` are now a dark ink instead of white, and Stone's `--color-on-success`, `--color-on-warning` and `--color-on-error` are white in light mode and near-black in dark mode instead of the status hue, so content on those fills reaches 4.5:1.-- Neutral's `--color-success`, `--color-warning`, and `--color-error` are now its status fills, the colours its Badges already showed: success `#00490B` to `#198100` (dark `#A4D6A3` to `#64AF4C`), warning `#4B3900` to `#FFCE2F` (dark `#F8D36A` to `#FFCE2F`), and error `#76000C` to `#C9303A` (dark `#FFC4BE` to `#FF705D`); `--color-info` is `#0074E2` (dark `#6D9CFE`). Its Badges, StatusDots, progress fills, and Stepper badges look the same, and its `text-<status>` utilities read its status text roles.-- Neutral drops its own status overrides and uses the standard roles: the accent variants of ProgressBar, StatusDot, and Stepper now paint Neutral's accent instead of blue, and Banner and the pale destructive Button use the standard overlays. Neutral no longer defines its proposed and undocumented local tokens; use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; `-on-tint-overlay-hover`, `-on-tint-overlay-pressed`, `-destructive-overlay-hover`, and `-destructive-overlay-pressed` → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value for Neutral extensions but is deprecated and no longer used by Neutral.-- Every first-party theme sets a blue `--color-info`; Chocolate and Matcha Info Badges move from the accent to that blue (Butter keeps its own Info Badge colours).--Custom themes get the content and text roles they don't set: theme generation derives `--color-on-<status>` (light or dark content, whichever contrasts more), readable status text, and on-muted content from the theme's status fills. To keep a component's previous colour, set the matching role in your theme; for example, set `--color-icon-success` to your old `--color-success` value.--@rubyycheungdiff --git a/.changeset/step-indicator-label-gap.md b/.changeset/step-indicator-label-gap.mddeleted file mode 100644index fd4d312232..0000000000--- a/.changeset/step-indicator-label-gap.md+++ /dev/null@@ -1,9 +0,0 @@-----'@astryxdesign/core': patch------[fix] Step: a clickable step's number badge and label are no longer adjacent text, so a text reading of the button no longer joins them as "1Account" (axe-core 4.14's Label in Name rule reported every clickable numbered step). A whitespace node now separates them in all four layouts; the rows are flex containers, so nothing changes on screen. A step's `description` inside the button is a separate Label in Name case and is unchanged.--Fixes #7966.--@HelloOjasMutrejadiff --git a/.changeset/switch-focus-ring-sibling.md b/.changeset/switch-focus-ring-sibling.mddeleted file mode 100644index 9a2607db8d..0000000000--- a/.changeset/switch-focus-ring-sibling.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `Switch`'s focus ring now follows the switch's own input through a sibling selector instead of a `:has()` check on the whole row, so a switch whose row holds large content (a long description, for example) no longer restyles everything in that row whenever something inside it changes. The ring looks and behaves the same. One edge changes: a focusable link inside the switch's label or description keeps its own focus ring and no longer also rings the switch.--@cixzhangdiff --git a/.changeset/tab-and-drawer-doc-claims.md b/.changeset/tab-and-drawer-doc-claims.mddeleted file mode 100644index 25ac4846de..0000000000--- a/.changeset/tab-and-drawer-doc-claims.md+++ /dev/null@@ -1,8 +0,0 @@-----'@astryxdesign/core': patch-'@astryxdesign/cli': patch------[docs] TabList's description no longer promises a built-in "more" menu: a strip narrower than its tabs scrolls horizontally and keeps the selected tab in view (`TabMenu` stays the way to group extra options). The library page template describes `MobileNav` as the slide-out navigation drawer it is, not as a bottom tab bar.--@vjeuxdiff --git a/.changeset/tab-keeps-its-width.md b/.changeset/tab-keeps-its-width.mddeleted file mode 100644index 31d78d1ff3..0000000000--- a/.changeset/tab-keeps-its-width.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] In TabList's default `hug` layout, a `Tab` and a `TabMenu` trigger no longer shrink below their labels. On a page whose CSS lets flex items shrink below their content (a `min-width: 0` reset), a narrow strip squeezed its stops until the labels drew over one another, before overflow could scroll. Each hugging stop now keeps its width and the strip scrolls, as its overflow handling intends; `fill` tabs still share the strip.--@light-merlin-darkdiff --git a/.changeset/table-pinned-dividers.md b/.changeset/table-pinned-dividers.mddeleted file mode 100644index 58e75b133f..0000000000--- a/.changeset/table-pinned-dividers.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Table: a pinned column (`useTableStickyColumns`) now draws its own row dividers, so the line under it no longer goes missing while the table scrolls horizontally. A theme's border color and an app's own borders on a row or cell carry onto the pinned cells, and an open detail panel (`useTableRowExpansion`) carries its row's divider the same way.--@cixzhangdiff --git a/.changeset/table-row-expansion-glide.md b/.changeset/table-row-expansion-glide.mddeleted file mode 100644index a602be810a..0000000000--- a/.changeset/table-row-expansion-glide.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] Table: `useTableRowExpansion` takes an `animatedLayout` handle from `useAnimatedLayout`. With it, opening or closing a row's panel glides the rows after it to their new places instead of jumping, and each row's divider moves with its row. Under Reduce Motion the rows fade in place on a touch screen and change at once with a mouse; in a table with column lines (`dividers="columns"` or `"grid"`) they change at once.--@cixzhangdiff --git a/.changeset/text-fields-focusable-disabled.md b/.changeset/text-fields-focusable-disabled.mddeleted file mode 100644index f7b93c9907..0000000000--- a/.changeset/text-fields-focusable-disabled.md+++ /dev/null@@ -1,9 +0,0 @@-----'@astryxdesign/core': patch------[fix] TextInput, TextArea: a disabled field now keeps its place in the tab order, so keyboard and screen-reader users can reach it and hear that it is unavailable (WCAG 2.2 SC 2.1.1 Keyboard, 4.1.2 Name, Role, Value and 2.4.7 Focus Visible; `spec:AST-085` FR1–FR3 and FR6). It exposes `aria-disabled="true"` and is read-only instead of carrying the native `disabled` attribute, as the field already did when a `disabledMessage` was set. It is still dimmed, cannot be edited, and is left out of form submission. Like a natively disabled field, it runs no caller event handler other than focus and blur, and Enter in a disabled TextInput does not submit its form. Under keyboard focus it shows the field's focus ring, dimmed with the rest of the field.--Part of #7814.--@HelloOjasMutrejadiff --git a/.changeset/text-input-caller-labelledby.md b/.changeset/text-input-caller-labelledby.mddeleted file mode 100644index 4164bbcdf9..0000000000--- a/.changeset/text-input-caller-labelledby.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] TextInput: a caller's `aria-labelledby` now reaches the input. Before, TextInput replaced it with its own value, so the input lost the extra name (standalone it had no `aria-labelledby` at all). Now the caller's ids follow the field's own label: `label="Email" aria-labelledby="billing-heading"` names the input "Email Billing", and inside an InputGroup the group label comes first. Inputs without a caller `aria-labelledby` are unchanged. No API changes.--@kyu-rongdiff --git a/.changeset/theme-build-no-text-fallback.md b/.changeset/theme-build-no-text-fallback.mddeleted file mode 100644index f88a18f1b2..0000000000--- a/.changeset/theme-build-no-text-fallback.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx theme build` reports a theme module that fails to load (an import it cannot resolve, or an error it throws) instead of building the theme from the text of its `defineTheme()` or default-export object; a theme module whose default export is a plain object builds as before, and a theme outside a project that imports Core builds with the Core the CLI answers with.--@vjeuxdiff --git a/.changeset/theme-build-project-core-load-error.md b/.changeset/theme-build-project-core-load-error.mddeleted file mode 100644index 563f202f9a..0000000000--- a/.changeset/theme-build-project-core-load-error.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx theme build` fails, naming it and its import error, when the project's installed `@astryxdesign/core` (or, outside a project, the Core the CLI release carries) does not load or lacks `defineTheme` or `generateThemeRulesSplit`, instead of building with the CLI's own Core. A project with no Core installed still builds with the CLI's.--@vjeuxdiff --git a/.changeset/theme-compact-definition.md b/.changeset/theme-compact-definition.mddeleted file mode 100644index 0a1aa071b0..0000000000--- a/.changeset/theme-compact-definition.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `@astryxdesign/core/theme` exports the compact definition: `compactDefinition(widthBreakpoints?)` and `DEFAULT_COMPACT_DEFINITION`. A screen is compact while its viewport is narrower than the theme's `md` point (768 by default) or shorter than 500. The definition carries both edges and ready-made media queries, with and without a coarse pointer, so every component that picks a presentation by screen size reads one shared definition. Nothing changes behavior yet.--@cixzhangdiff --git a/.changeset/theme-motion-inherits-field-by-field.md b/.changeset/theme-motion-inherits-field-by-field.mddeleted file mode 100644index 55020f125d..0000000000--- a/.changeset/theme-motion-inherits-field-by-field.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[docs] The theme authoring guide, and the comment in the theme file `astryx init` and `astryx theme template` write, say an extending theme's `motion` inherits field by field: the child's `fast`, `medium` and `ratio` regenerate the fast and medium duration tokens, and `slow` or `easing` left unset keep the base theme's tokens (an inherited slow band stays at the base's ratio). It used to say the child's motion config replaced the base's entirely.--@cixzhangdiff --git a/.changeset/theme-surface-codemod-look-alikes.md b/.changeset/theme-surface-codemod-look-alikes.mddeleted file mode 100644index 256438fe56..0000000000--- a/.changeset/theme-surface-codemod-look-alikes.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] `astryx upgrade` to 0.7 no longer renames component keys in a look-alike theme object that is not an Astryx theme, such as another library's `{name, components: {checkbox, radio, textarea}}` theme. A theme object with no `defineTheme()` call or Astryx theme type is migrated only when it is the binding a same-stem theme descriptor declares (`brandTheme` exported from `brandTheme.ts` beside `brandTheme.doc.mjs`). (#7980)--@ejhammonddiff --git a/.changeset/thumbnail-actions-stay-mounted.md b/.changeset/thumbnail-actions-stay-mounted.mddeleted file mode 100644index c9c38bab9b..0000000000--- a/.changeset/thumbnail-actions-stay-mounted.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Thumbnail: Open and Remove stay mounted while they cannot act. A loading or disabled thumbnail keeps Open, and a disabled one keeps Remove, focusable and announced as disabled instead of removing them, so keyboard focus on an action no longer falls to the page body when the thumbnail starts loading or becomes disabled.--@cixzhangdiff --git a/.changeset/thumbnail-disabled-block-doc.md b/.changeset/thumbnail-disabled-block-doc.mddeleted file mode 100644index 7255c7d69c..0000000000--- a/.changeset/thumbnail-disabled-block-doc.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[docs] Thumbnail — Disabled block: its description no longer says the remove button and click handler are suppressed; a disabled thumbnail's open and remove buttons stay focusable and announced as disabled, and call nothing.--@cixzhangdiff --git a/.changeset/toast-dismiss-without-row.md b/.changeset/toast-dismiss-without-row.mddeleted file mode 100644index abd1ab1124..0000000000--- a/.changeset/toast-dismiss-without-row.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A toast dismissed while it had no row on screen — hidden past `maxVisible`, or dismissed before it first rendered — now leaves the stack. Before, it stayed as an empty, invisible row that took a visible slot when it came back into view and kept the "Notifications" landmark (and its F6 stop) present after every real toast was gone.--@vjeuxdiff --git a/.changeset/tokenizer-caret-after-last-token.md b/.changeset/tokenizer-caret-after-last-token.mddeleted file mode 100644index a86461c99f..0000000000--- a/.changeset/tokenizer-caret-after-last-token.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Tokenizer: once a field has tokens, its text cursor sits right after the last token, on the last row, instead of at the end of the first row. PowerSearch gets the same fix. When the last row is too full for the cursor, focusing starts a new row for it; when it fits the cursor but not the typing area, the first keystroke moves to a new row. At rest the field keeps its height.-@kentonquatmandiff --git a/.changeset/tokenizer-sheet-presentation-held-back.md b/.changeset/tokenizer-sheet-presentation-held-back.mddeleted file mode 100644index 734ed7f3cc..0000000000--- a/.changeset/tokenizer-sheet-presentation-held-back.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: Tokenizer's touch sheet presentation is held back until its user experience is finished. The implementation stays in the package, reachable only through an internal entry reserved for Astryx's own packages; `TokenizerProps` offers no `experimental.presentation`, every Tokenizer renders the inline combobox, and nothing a consumer sees changes.--@imdreamrunnerdiff --git a/.changeset/tokenizer-tokens-wrap-before-the-clear-all-butto-a99p.md b/.changeset/tokenizer-tokens-wrap-before-the-clear-all-butto-a99p.mddeleted file mode 100644index cf353bd282..0000000000--- a/.changeset/tokenizer-tokens-wrap-before-the-clear-all-butto-a99p.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Tokenizer: tokens wrap before the clear-all button and busy indicator instead of running under them, including PowerSearch filters. While the field has tokens and can search, the busy indicator's space stays reserved, so a search starting or settling does not move token rows-@harjothkharadiff --git a/.changeset/tooltip-tall-content-follows-trigger.md b/.changeset/tooltip-tall-content-follows-trigger.mddeleted file mode 100644index f8c87d90c4..0000000000--- a/.changeset/tooltip-tall-content-follows-trigger.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `Tooltip`: an open tooltip that has moved clear of its trigger now also stays clear when the trigger moves on screen without resizing, in layout or because the page scrolled, at most one painted frame later. Moving it keeps every animation in its content where it was.--@ejhammonddiff --git a/.changeset/tooltip-tall-content-keeps-trigger-clear.md b/.changeset/tooltip-tall-content-keeps-trigger-clear.mddeleted file mode 100644index 0206b291d1..0000000000--- a/.changeset/tooltip-tall-content-keeps-trigger-clear.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] `Tooltip`: a tooltip taller than the room above and below its trigger no longer opens over the trigger. It opens beside the trigger when there is room there, otherwise on the other side if it fits there, and otherwise on the side with more room, sized to that room, scrolling content it cannot show. It also moves clear when its content grows, or its trigger or the viewport resizes, while it is open. Before, it slid over its own trigger, where a resting pointer could lose it, and content past the viewport could not be read. Tooltips that fit are placed exactly as before.--@ejhammonddiff --git a/.changeset/topnav-mega-menu-reduced-motion.md b/.changeset/topnav-mega-menu-reduced-motion.mddeleted file mode 100644index 14b150be51..0000000000--- a/.changeset/topnav-mega-menu-reduced-motion.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] TopNav: with reduced motion on, the mega-menu panel no longer rises as it opens and closes. On a touch screen it fades, in 200 ms or less; with a mouse it opens and closes at once (design:reduced-motion).--@cixzhangdiff --git a/.changeset/topnavmenu-action-rows-no-selection.md b/.changeset/topnavmenu-action-rows-no-selection.mddeleted file mode 100644index 9ad44bec4c..0000000000--- a/.changeset/topnavmenu-action-rows-no-selection.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A mouse slide across TopNavMenu's action items (items with an `onClick` and no `href`) no longer selects their text.--@cixzhangdiff --git a/.changeset/touch-motion-theme-roles.md b/.changeset/touch-motion-theme-roles.mddeleted file mode 100644index 02eb1ec171..0000000000--- a/.changeset/touch-motion-theme-roles.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the touch motion tables register their springs, durations and curves as internal motion roles, each read once when a motion starts, so every component keeps its measured value. Nothing public changes: themes do not set motion roles, and no shipped component reads the roles yet.--@vjeuxdiff --git a/.changeset/touch-presentation.md b/.changeset/touch-presentation.mddeleted file mode 100644index ad0ae3ff44..0000000000--- a/.changeset/touch-presentation.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `presentation="adaptive"` on DropdownMenu, ContextMenu, MoreMenu, Selector and MultiSelector, and a DropdownMenu's or ContextMenu's default sub-menu drill-in, now use the theme's compact definition with a coarse primary pointer: a viewport narrower than the theme's `md` point (768px by default) or shorter than 500px. This is a behavior change. The old default was a bottom sheet at 768px wide and below on a coarse pointer. Now a coarse-pointer screen exactly 768px wide keeps the anchored popover, and a phone in landscape (wider than 768px but shorter than 500px) gets the bottom sheet and the drilled-in sub-menu. A theme that moves `md` moves the edge with it. To pin a component's presentation regardless of the rule, pass `presentation="popover"` or `presentation="bottom-sheet"`; to keep a sub-menu's flyout, pass `presentation="flyout"` on `DropdownMenuSubMenu`. Mouse and keyboard users on desktop see no change, because every case requires a coarse pointer.--@vjeuxdiff --git a/.changeset/touch-support.md b/.changeset/touch-support.mddeleted file mode 100644index 1eb09b40ec..0000000000--- a/.changeset/touch-support.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Adds an internal entry, reserved for Astryx's own packages, through which Lab components reach the gesture core that Core components import directly. No component uses it yet, and apps import nothing new.--@vjeuxdiff --git a/.changeset/tree-list-guide-alignment.md b/.changeset/tree-list-guide-alignment.mddeleted file mode 100644index d367eb4053..0000000000--- a/.changeset/tree-list-guide-alignment.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] TreeList chevrons and hierarchy guides sit 4px closer to the row's inline start, and the chevron-to-label gap widens from 4px to 8px; labels keep their position.--@rubyycheungdiff --git a/.changeset/typeahead-and-tokenizer-show-loading-feedback-in-f8g1.md b/.changeset/typeahead-and-tokenizer-show-loading-feedback-in-f8g1.mddeleted file mode 100644index 8b45a1f3f4..0000000000--- a/.changeset/typeahead-and-tokenizer-show-loading-feedback-in-f8g1.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[fix] Typeahead and Tokenizer hide the previous empty-result row while the next query debounces or waits for its answer. The existing input spinner provides loading feedback; no replacement Loading row is added. Settled empty results and their announcements remain unchanged. Fixes #8903.-@nynexman4464diff --git a/.changeset/typeahead-edit-focus-in-tap.md b/.changeset/typeahead-edit-focus-in-tap.mddeleted file mode 100644index d1ea5950e2..0000000000--- a/.changeset/typeahead-edit-focus-in-tap.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] Taps that start typing in a search field raise the touch keyboard. A tap on a Typeahead's selected value (edit mode) and a tap on the clear button of a Selector or MultiSelector search row now focus the input inside the tap itself instead of one frame later; iOS raises its keyboard only for a focus made while the browser is still handling the tap, so the deferred focus left a caret with no keyboard until a second tap. A clear tapped while the keyboard is already up keeps it up, as before. Introduced in #8158; final-state evidence (#8247).--@vjeuxdiff --git a/.changeset/typeahead-highlight-follows-pointer-movement.md b/.changeset/typeahead-highlight-follows-pointer-movement.mddeleted file mode 100644index 58128b3a67..0000000000--- a/.changeset/typeahead-highlight-follows-pointer-movement.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] BaseTypeahead, and the Typeahead, Tokenizer and PowerSearch menus built on it: an option now takes the highlight when the pointer moves over it, not when it merely appears under a resting pointer. A menu opened from the keyboard, or one that scrolls during arrow-key navigation, used to hand its highlight to whichever option slid under the cursor, so Enter could pick an option the user never pointed at and arrow keys appeared to jump back. The keyboard highlight now stays put until the pointer actually moves.--@ejhammonddiff --git a/.changeset/uikit-constants-table.md b/.changeset/uikit-constants-table.mddeleted file mode 100644index 01fd41a182..0000000000--- a/.changeset/uikit-constants-table.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the UIKit constants table for touch presentations (springs, scroll physics, timing curves and navigation values), each value with its source and a checked list of the simulator measurements still owed. Not exported from the package entry point; no component reads it yet.--@vjeuxdiff --git a/.changeset/uikit-gestures-named-groups.md b/.changeset/uikit-gestures-named-groups.mddeleted file mode 100644index 1a0476203a..0000000000--- a/.changeset/uikit-gestures-named-groups.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the UIKit gesture thresholds are one export per recognizer (`UIKIT_TAP`, `UIKIT_PAN`, `UIKIT_PRESS`, …), so a touch component bundles only the group it reads. The table's notes say that the status-bar scroll-to-top does not coast under Reduce Motion and that UIKit's Reduce Motion menu spring is never played. No behavior change.--@cixzhangdiff --git a/.changeset/uikit-motion-animator-curves.md b/.changeset/uikit-motion-animator-curves.mddeleted file mode 100644index 86bc609560..0000000000--- a/.changeset/uikit-motion-animator-curves.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the touch presentations' animator plays any closed-form curve (such as a spring chasing a moving target) through `play`, with the same presentation values, velocities, stop and shared clock as a spring, and the Reduce Motion policy. Not exported from the package entry point.--@vjeuxdiff --git a/.changeset/uikit-motion-animator-reduced-motion.md b/.changeset/uikit-motion-animator-reduced-motion.mddeleted file mode 100644index 4dc42ecde1..0000000000--- a/.changeset/uikit-motion-animator-reduced-motion.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the touch presentations' animator follows design:reduced-motion (under Reduce Motion, an opacity-only cross-fade of 200 ms on a coarse pointer or after a touch release and an immediate change on any other pointer, with no option or theme value that keeps travel or lengthens the fade; an entrance or exit role orients a slide that changes no opacity), decided by its own planner module, and starts a call from rest when the browser commits it, as Core Animation does. Not exported from the package entry point.--@vjeuxdiff --git a/.changeset/uikit-motion-animator.md b/.changeset/uikit-motion-animator.mddeleted file mode 100644index d489e3022e..0000000000--- a/.changeset/uikit-motion-animator.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: a compositor animator for touch presentations. It plays UIKit's springs, and scroll coasts (built by a separate coast module, so a surface that never coasts does not carry them; `decay` plays momentum, and sends a spring back from past an edge through the Reduce Motion policy: a cross-fade on a coarse pointer or after a touch release, at once elsewhere) as Web Animations on translate, rotate, scale and opacity, so they keep running while JavaScript is busy, and reads values and velocities back from the curves for interruption, retargeting and Reduce Motion cross-fades. Not exported from the package entry point; no component uses it yet.--@vjeuxdiff --git a/.changeset/uikit-motion-math.md b/.changeset/uikit-motion-math.mddeleted file mode 100644index 7af3d73a92..0000000000--- a/.changeset/uikit-motion-math.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[chore] Internal: the spring, decay, rubber-band and projection math of UIKit for touch presentations, as pure functions checked against an independent integration and against values read from UIKit. Not exported from the package entry point; no component uses it yet.--@vjeuxdiff --git a/.changeset/upgrade-manual-and-regenerate-outcomes.md b/.changeset/upgrade-manual-and-regenerate-outcomes.mddeleted file mode 100644index 63dd9fa492..0000000000--- a/.changeset/upgrade-manual-and-regenerate-outcomes.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[feat] `astryx upgrade` now reports stale generated files in a new `regenerate` receipt field, and reports code a codemod can identify but not migrate safely in the existing `declinedCandidates` list instead of failing. A manual migration is a `declinedCandidates` row with the file, its line as `location` when known, and a `reason` that starts with `manual migration needed (<codemod>):` followed by what to change (a file with several declined findings keeps one row listing each, with its own prefix, joined by `; `); it is printed after the run, does not fail the upgrade, and the run completes and exits 0. A generated file that must be rebuilt, such as stale theme CSS that `validate-data-token-ownership` reports and `astryx theme build` regenerates, is listed in `regenerate` with its rebuild command until it is rebuilt; a `hooks.postCodemod` command that rebuilds it clears it. When the project protects the file (for example an `@generated` header), the run is incomplete exactly as for a protected file (`complete: false`, `errorCode: "ERR_CODEMOD_PROTECTED"`, exit 1); when nothing protects it, it stays a codemod error (`ERR_CODEMOD_FAILED`, as before), now with the rebuild command in `regenerate`. Protected generated files also appear in `regenerate` with their header's `Command:`, and a reported file the project marks generated also appears in `protectedFiles` with the rule that protects it. A real codemod failure keeps its `ERR_CODEMOD_FAILED` error, and the `receipt` it carries lists both too.--@ejhammonddiff --git a/.changeset/upgrade-receipt-on-failure.md b/.changeset/upgrade-receipt-on-failure.mddeleted file mode 100644index 71e9491d48..0000000000--- a/.changeset/upgrade-receipt-on-failure.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/cli': patch------[fix] A failed `astryx upgrade` now says which files it already changed. When a codemod or post-codemod hook fails, the upgrade still writes every other change; the `--json` error (`{"error", "code": "ERR_CODEMOD_FAILED"}`) now adds a `receipt` with the same fields a finished run returns (`modifiedFiles`, `errors`, `protectedFiles`, `complete: false`, `errorCode`), and the error `upgrade()` rejects with carries it as `receipt`. The change is additive: the error code, the error shape, `isError()`, the rejection and exit code 1 are unchanged. An error that stops the run after codemods have written files, such as an astryx.config that fails validation, carries a `receipt` too.--@ejhammonddiff --git a/.changeset/use-combobox-caller-field.md b/.changeset/use-combobox-caller-field.mddeleted file mode 100644index 1126db7fe3..0000000000--- a/.changeset/use-combobox-caller-field.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] `useCombobox` (from `@astryxdesign/core/Selector`) now builds a combobox over a single-line text field you render yourself, such as a search field whose results replace a page section or an “add people” field in a dialog. Spread `getFieldProps` on your `input`, `getListboxProps` on your listbox wherever it renders, and `getOptionProps` on each option. Focus stays in the field; the field and the list carry the combobox roles and relationships; while the list shows, the arrows move the active option, Enter picks it and Escape hides the list without closing a surrounding dialog; while it is hidden, ArrowDown reopens it; while an input method is composing, keys reach the field untouched; a pointer picks without taking focus. Announce each new result count yourself through `useAnnounce`, with the words the field shows when nothing matches. Options may be any type with a string `value`. Existing options, return fields and `onKeyDown` behave as before.--@vjeuxdiff --git a/.changeset/visuallyhidden-keeps-its-clip-block-and-its-dom-a3k7.md b/.changeset/visuallyhidden-keeps-its-clip-block-and-its-dom-a3k7.mddeleted file mode 100644index 402b54eb54..0000000000--- a/.changeset/visuallyhidden-keeps-its-clip-block-and-its-dom-a3k7.md+++ /dev/null@@ -1,17 +0,0 @@-----'@astryxdesign/core': patch------[fix] VisuallyHidden keeps its clip block and its DOM clean: `xstyle`, `className` and `style` no longer reach the element. The component's contract is that content in the accessibility tree stays invisible, so its clip block is meant to be non-overridable — but the implementation spread leftover props onto the element, which wrote the literal attribute `xstyle="[object Object]"` into the DOM, and let the same props arriving through a cast or a `{...consumerProps}` object take the last word on `position` and un-hide the node while assistive technology kept announcing it.--Measured prop by prop against `main`'s implementation, before and after this change:--- `xstyle` arrived as the attribute only — the `style` attribute stayed `null` and the clip classes were the same set in both arms — so a consumer passing it loses a stray attribute and no pixel.-- `className` was already displaced by the clip block's own class list; it reaches the element in neither arm.-- `style` did reach the element (`style="position: static;"`), and an inline declaration outranks a class rule, so the node was un-hidden. It stops reaching the element. That is the one rendering change here, and it moves the node back to the hidden state the contract calls non-overridable.--None of the three is styling surface on `VisuallyHiddenProps` — `className` and `style` are behind its `Omit`, reaching the element only through a cast or an untyped spread, and `xstyle` is documented as ignored — so no typed call site loses an effect it was promised.--`xstyle` stays declared on `VisuallyHiddenProps`, documented as ignored, because released 0.7.2 accepted it through `BaseProps`: removing it from the interface makes `<VisuallyHidden xstyle={…}>` stop compiling, and AST-017 FR31 and FR53 admit that narrowing only as a `[breaking]` change in a planned minor. It is deliberately not marked `@deprecated`: under FR28 a patch that deprecates a surface has to ship the exact migration or a codemod with it, and this fix ships neither. The removal and its migration belong to a planned minor, and the migration is to delete the prop — it applies nothing to the element.--@aashish254diff --git a/.changeset/wheel-pinch-zoom.md b/.changeset/wheel-pinch-zoom.mddeleted file mode 100644index 459f1380e2..0000000000--- a/.changeset/wheel-pinch-zoom.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] A two-finger pinch over an open picker wheel zooms the page again. The wheels in the TimeInput, DateTimeInput and DateInput bottom sheets accepted vertical pans only, which also refused the browser's pinch-zoom, so the page could not be zoomed over an open picker. They now leave the pinch to the page, as the menus and listboxes already do. Scrolling a wheel is unchanged.--@vjeuxdiff --git a/packages/build/CHANGELOG.md b/packages/build/CHANGELOG.mdindex 1e2666d364..2fbb489872 100644--- a/packages/build/CHANGELOG.md+++ b/packages/build/CHANGELOG.md@@ -1,5 +1,19 @@# @astryxdesign/build+# 0.7.5++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang++---+# 0.7.4---diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.mdindex e27717bccc..8083a261b2 100644--- a/packages/cli/CHANGELOG.md+++ b/packages/cli/CHANGELOG.md@@ -1,5 +1,93 @@# @xds/cli+# 0.7.5++#### Experimental APIs++- New command `astryx experimental render <page>` turns a page built with your installed Astryx components into one self-contained HTML file. The file needs no network and no scripts, follows light and dark mode, and carries the page's source; `astryx experimental render --reverse <file.html>` writes that source back. Warnings point out anything that may not look as intended. Experimental commands may change or be removed in any patch release. Guide: `astryx docs cli/experimental/render-pages`.+- Building an icon-set package from an icon library takes fewer steps and fewer guesses. Only the experimental icon commands, the icon-set guide, and `astryx template` in a project that sets `experimental.iconSet` change; without that opt-in, stable commands behave as before, and only the `experimental` group's summary in `astryx help` and `astryx manifest` now mentions icon sets.+ - **`experimental icon new-set`.** `--from` maps a definition only when an icon has its exact name and lists those for review; likely matches come back as at most three suggestions each, never written. It saves the library and version, copies the library's license notices, keeps your `--exclude` list across refreshes, and its receipt names the package entry, peer dependencies, and `typecheck` script to add. `--variants`, `--default-variant`, `--display-name`, and `--description` fill in the set. A refresh changes only the icons that library supplies, keeps each icon's export name, and lists renamed icons. A 1,600-icon library is read in about two seconds.+ - **`experimental icon add` and `map`.** `add --variant <name> --from <module> --all` adds a variant for every icon at once, and `map --pairs a=b,c=d` writes many entries in one checked step.+ - Icon commands now refuse options that conflict instead of silently ignoring one (`ERR_INVALID_OPTION`), leave every file as it was when they fail partway (`ERR_WRITE_FAILED`), and report a missing or withdrawn set the same way everywhere (`ERR_NOT_FOUND`).+ - `experimental icon --set <set> --all-icons` lists every icon in a set, and `--definitions` lists every Astryx icon definition.+ - Templates drop a mapped icon library's sizing props (`size`, `strokeWidth`, `absoluteStrokeWidth`) and keep comments on rewritten imports.+ - Thirteen new icon definitions: `rotate`, `flipHorizontal`, `flipVertical`, `alignStart`, `alignCenter`, `alignEnd`, `panelLeft`, `panelRight`, `gitBranch`, `gitFork`, `scale`, `cpu`, and `textCase`. Definitions gain common glyph names as search words; seven optional definitions lose a word that named a different thing: `star` (`bookmark`), `database` (`table`), `raiseHand` (`stop`), `redo` (`forward`), `activity` (`monitor`), `archive` (`store`), `mobile` (`device`).+ - `integration check` suggests icons by the same rule, describes each optional definition, and its version-drift warning gives the refresh command.++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++- CodeBlock's `tokenizer` prop is deprecated in favor of a custom language: pass `language={createCodeLanguage({name, identifiers, tokenize})}` with the same function. The prop still works. `astryx upgrade` rewrites it when the block has a fixed `language`, and leaves a TODO comment where it can't safely rewrite it.+- `Icon` takes an optional `variant` to ask the active theme for alternate artwork, for example `<Icon icon="info" variant="filled" />`. The theme's icon receives the variant only when the theme lists it in `iconVariants`; otherwise it draws its normal artwork. Icons you pass as components never receive `variant`, and it is never written to the page. Icons without `variant` render as before.+- A theme icon can now pick its artwork by size: an entry in `defineTheme({icons})` or `registerIcons()` can be a function of `{size, variant}`, and `Icon` calls it with the size it renders at. Returning `null` draws no icon. `getIcon`, `getExtendedIcon`, `getIconRegistry`, `useIcon`, and a theme's `icons` field still return nodes, reading a function at `{size: 'md'}`. Existing icon entries are unchanged.+- A theme can list the icon variants it supports, such as `filled`, with `defineTheme({iconVariants})`, and read them back from `theme.iconVariants`. Child themes inherit the list unless they set their own. `@astryxdesign/core/Icon` exports `IconVariantMap` and `IconVariant` for typing variants. Themes without `iconVariants` are unchanged.+- `astryx theme build` keeps function icons and icon variant lists, so a built theme draws each icon at the same size and variant as the live theme, including icons inherited from another theme. A theme that lists `iconVariants` gets matching types in `<theme>.variants.d.ts`. Themes without these features build exactly as before.+- Themes can set the real size of each Icon size: `width` and `height` in `px` or `rem` on `components.icon['size:sm']` (or `xsm`, `md`, `lg`) now resize the glyph itself, for named icons and SVG components, in live and built themes. Before, they sized only the box around the icon. Sizes a theme does not style still render at 12, 16, 20, or 24px at a 16px root. `astryx docs theme` gains an Icon sizes section.+- New `--ease-exit` motion token for things leaving the screen, beside `--ease-standard` for things arriving. BottomSheet already closes on it, so nothing looks different, but a theme can now tune the exit. `astryx docs motion` and the theme template list it.+- `astryx upgrade` finishes instead of failing when it finds code it can't migrate safely: each spot is listed in `declinedCandidates` with its file, line, and a reason starting `manual migration needed (<codemod>):`, and the run exits 0. Generated files that need rebuilding, such as stale theme CSS, are listed in a new `regenerate` field with their rebuild command until they are rebuilt; a `hooks.postCodemod` that rebuilds them clears the entry. Protected generated files still stop the run as before, now with the rebuild command listed.+- The two Bottom Sheet flow templates (`BottomSheetSwitcherShowcase`, `BottomSheetSwitcherReviewFlow`) now show the standalone-step pattern that replaces `BottomSheetSwitcher`, and are also listed under `BottomSheet`. Template names and ids are unchanged.++#### Fixes++- Projects that compile StyleX with `@stylexjs/unplugin` (the standard Vite setup) are detected as StyleX projects.+- The `Tokenizer` showcase template's search returns matching tags again, so the live example on the Tokenizer docs page works.+- `astryx integration verify` no longer fails with "npm pack failed" when another `npm` wrapper comes first on your PATH.+- `astryx upgrade` skips vendored, generated, or ignored files it can't parse, lists them in `declinedCandidates`, and finishes the rest of the upgrade.+- `astryx upgrade` no longer spends minutes reading symlinked `node_modules` folders or package stores.+- `astryx upgrade --from` a version before 0.7.0 no longer fails on `var(--color-data-*)` without a fallback. Source builds that read raw data colors should import `dataVars` from `@astryxdesign/core/theme/dataTokens.stylex`.+- Tools that call the CLI API repeatedly, such as a docs site search, now see doc edits without restarting.+- Component families list the same members whether or not the package has been built, so Lab's `TourStep` now appears in the official package list.+- `astryx upgrade` handles an `astryx.config` written as `const config = {...}; export default config;`.+- `astryx component <name>` suggests the right component when you type a wrapped or prefixed name.+- When `astryx component`, `astryx template`, or `astryx docs` finds nothing, its suggestions stop where the matches get weak instead of listing unrelated entries.+- `astryx upgrade` to 0.7 no longer turns your own MetadataList class into a `data-columns` selector that never matches.+- `astryx discover` lists the experimental MobilePowerSearch component from `@astryxdesign/lab`.+- `astryx theme build` reports a theme file that fails to load instead of guessing the theme from its text.+- `astryx theme build` fails with a clear error when your project's `@astryxdesign/core` can't load, instead of silently building with the CLI's own copy.+- `astryx upgrade` to 0.7 leaves other libraries' theme objects alone.+- A failed `astryx upgrade` now lists the files it already changed: its `--json` error includes a `receipt` with `modifiedFiles`, `errors`, `protectedFiles`, `complete: false`, and `errorCode`. The error code and exit code are unchanged.++#### Documentation++- The Tokenizer templates size their field to fit phone screens.+- The CodeBlock snippet example shows one-line commands with Copy beside them.+- Package links now point to the project's GitHub home, `meta/astryx`.+- TabList's description no longer promises a built-in "more" menu (a narrow tab strip scrolls), and the library page template describes `MobileNav` as the slide-out drawer it is.+- The theme guide and generated theme files explain that an extending theme's `motion` settings inherit field by field.+- The disabled Thumbnail template now describes its buttons correctly: they stay focusable and are announced as disabled.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @ejhammond+- @imdreamrunner+- @josephfarina+- @kentonquatman+- @nbozidarevic+- @rubyycheung+- @vjeux++---+# 0.7.4#### Experimental APIsdiff --git a/packages/cli/assets/codemods/__tests__/registry.test.mjs b/packages/cli/assets/codemods/__tests__/registry.test.mjsindex 7c03819954..b0717363f9 100644--- a/packages/cli/assets/codemods/__tests__/registry.test.mjs+++ b/packages/cli/assets/codemods/__tests__/registry.test.mjs@@ -32,6 +32,7 @@ describe('registry', () => {'0.6.7','0.7.0','0.7.2',+ '0.7.5',]);});});diff --git a/packages/cli/assets/codemods/registry.mjs b/packages/cli/assets/codemods/registry.mjsindex 2029398955..b2e9da433f 100644--- a/packages/cli/assets/codemods/registry.mjs+++ b/packages/cli/assets/codemods/registry.mjs@@ -33,6 +33,7 @@ const registry = new Map([['0.6.7', () => import('./transforms/v0.6.7/index.mjs')],['0.7.0', () => import('./transforms/v0.7.0/index.mjs')],['0.7.2', () => import('./transforms/v0.7.2/index.mjs')],+ ['0.7.5', () => import('./transforms/v0.7.5/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 45dead1111..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 migrateCodeBlockTokenizerToLanguage, {- meta as migrateCodeBlockTokenizerToLanguageMeta,-} from './migrate-codeblock-tokenizer-to-language.mjs';--export default [- {- name: 'migrate-codeblock-tokenizer-to-language',- transform: migrateCodeBlockTokenizerToLanguage,- meta: migrateCodeBlockTokenizerToLanguageMeta,- },-];+export default [];diff --git a/packages/cli/assets/codemods/transforms/next/__tests__/migrate-codeblock-tokenizer-to-language.test.mjs b/packages/cli/assets/codemods/transforms/v0.7.5/__tests__/migrate-codeblock-tokenizer-to-language.test.mjssimilarity index 100%rename from packages/cli/assets/codemods/transforms/next/__tests__/migrate-codeblock-tokenizer-to-language.test.mjsrename to packages/cli/assets/codemods/transforms/v0.7.5/__tests__/migrate-codeblock-tokenizer-to-language.test.mjsdiff --git a/packages/cli/assets/codemods/transforms/v0.7.5/index.mjs b/packages/cli/assets/codemods/transforms/v0.7.5/index.mjsnew file mode 100644index 0000000000..45dead1111--- /dev/null+++ b/packages/cli/assets/codemods/transforms/v0.7.5/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 migrateCodeBlockTokenizerToLanguage, {+ meta as migrateCodeBlockTokenizerToLanguageMeta,+} from './migrate-codeblock-tokenizer-to-language.mjs';++export default [+ {+ name: 'migrate-codeblock-tokenizer-to-language',+ transform: migrateCodeBlockTokenizerToLanguage,+ meta: migrateCodeBlockTokenizerToLanguageMeta,+ },+];diff --git a/packages/cli/assets/codemods/transforms/next/migrate-codeblock-tokenizer-to-language.mjs b/packages/cli/assets/codemods/transforms/v0.7.5/migrate-codeblock-tokenizer-to-language.mjssimilarity index 100%rename from packages/cli/assets/codemods/transforms/next/migrate-codeblock-tokenizer-to-language.mjsrename to packages/cli/assets/codemods/transforms/v0.7.5/migrate-codeblock-tokenizer-to-language.mjsdiff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.mdindex 51884886ac..71fffb9a17 100644--- a/packages/core/CHANGELOG.md+++ b/packages/core/CHANGELOG.md@@ -1,5 +1,206 @@# @xds/core+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++- BottomSheets stack in the order they open. A modal sheet opened over another now sits on top of it: the sheet underneath keeps its state, moves back slightly, and can't be used until it is on top again; only one backdrop dims the page; and Escape, a backdrop tap, a swipe, or the system close gesture closes only the top sheet. Closing the top sheet returns focus to the sheet below, and closing a whole stack returns focus once, to where the flow started. A sheet inside another sheet's content now closes with it. Non-modal sheets (`hasScrim={false}`) never stack. No props change, and a single sheet behaves as before.+- Multi-step sheet flows no longer need a wrapper. When the top BottomSheet closes and another opens in the same update, for example from one state value that names the open step, the new sheet replaces the old one: it rises into place, the backdrop stays steady, focus moves into the new sheet, and closing the flow later returns focus to whatever opened it. This happens when the step change comes from inside the closing sheet, such as its own Continue or Back button. Non-modal sheets (`hasScrim={false}`) replace each other the same way, and now open above all page content in the browser's top layer instead of relying on a `z-index`.+- `BottomSheetSwitcher` and BottomSheet's `sheetId` prop are deprecated and keep working until a future minor release. Write each step as its own `BottomSheet` instead:+ 1. Replace `activeSheet` / `onActiveSheetChange` with one `step` state value.+ 2. On each step, replace `sheetId="id"` with `isOpen={step === 'id'}` and `onOpenChange={isOpen => !isOpen && setStep(current => (current === 'id' ? null : current))}`.+ 3. Remove the `BottomSheetSwitcher` wrapper and move its `hasScrim` onto every step.+ 4. Keep your step buttons as they are, for example `setStep('next')`.++ To keep a step open, ignore `false` in its `onOpenChange` (this replaces `onCancel`); to keep Escape but block the backdrop tap and swipe, use `purpose="form"`. A consumer `aria-label` becomes each step's `label`. Dialog-level `ref`, `id`, `className`, and styling props have no direct replacement: a standalone sheet's `ref` and props reach its panel. Flows that keep the switcher work as before, now with toasts above the flow and reduced-motion support.++- Popover takes `presentation`, like DropdownMenu and Selector: `'popover'` (the default) anchors it to its trigger, `'bottom-sheet'` shows its content in a modal BottomSheet named by `label`, and `'adaptive'` uses the sheet on phones and the anchored popover elsewhere. In a sheet, positioning props such as `placement` and `width` don't apply, and `xstyle`, `className`, and `style` style the sheet's panel. The sheet code loads only when it can be used.+- Menus and selectors with `presentation="adaptive"` (DropdownMenu, ContextMenu, MoreMenu, Selector, MultiSelector) and sub-menus that drill in on phones now switch to a bottom sheet by the shared phone-size rule on touch screens. A touch screen exactly 768px wide now keeps the anchored popover, and a phone in landscape (wider than 768px but shorter than 500px) now gets the sheet. A theme that moves its `md` breakpoint moves this edge too. To keep a fixed presentation, pass `presentation="popover"` or `"bottom-sheet"`, or `presentation="flyout"` on `DropdownMenuSubMenu`. Desktop mouse and keyboard users see no change.+- `@astryxdesign/core/theme` exports `compactDefinition(widthBreakpoints?)` and `DEFAULT_COMPACT_DEFINITION`: one shared rule for a phone-sized screen, narrower than the theme's `md` breakpoint (768px by default) or shorter than 500px, with ready-made media queries.+- `CodeBlock` highlights C, C++, SQL, Rust, Kotlin, Swift, and Go with no setup, so you only ship the languages you use.++ Every other language is opt in, one at a time:++ - Import that language on its own and pass it as `language`, for example `graphql` from `@astryxdesign/core/CodeBlock/languages/graphql`.+ - Modules ship for `graphql`, `java`, `thrift`, `objectiveC` (path `languages/objective-c`), `toml`, `powershell`, `ruby`, `lua`, and `dockerfile`.+ - A string such as `language="graphql"` still selects only a built-in language.++ Your own languages work the same way. `createCodeLanguage({name, identifiers, fileExtensions, fileNames, tokenize})` makes a language from your own tokenize function.++ The built-in tokenizer stays within 4,608 bytes gzipped. Each module adds at most 512 bytes, and only when you import it.++- `CodeBlock` takes `endContent` for your own controls, such as a "Run in terminal" button. They sit just before Copy, in the header when there is one, otherwise beside the code, never over it. For a one-line command, leave out the title and pass `hasLanguageLabel={false}` to get a single row with its controls beside it.+- CodeBlock's `tokenizer` prop is deprecated in favor of a custom language: pass `language={createCodeLanguage({name, identifiers, tokenize})}` with the same function. The prop still works. `astryx upgrade` rewrites it when the block has a fixed `language`, and leaves a TODO comment where it can't safely rewrite it.+- `Markdown` takes `codeLanguages`, a list of CodeBlock languages, so fenced code in Markdown can use the extra or custom languages too. A listed language wins over a built-in language of the same name, and `diff-<name>` fences get diff coloring on top.+- Expanding and collapsing can glide instead of jump. Create a handle with `useAnimatedLayout({containerRef})` and pass it to Collapsible or TreeList as `animatedLayout`: when one opens or closes, the content around it inside that container glides to its new place, revealed content fades in, and the chevron turns, all as one motion. Fixed and sticky elements stay put and the container never scrolls. Under Reduce Motion the change cross-fades on touch and is immediate with a mouse. Without the prop, nothing changes.+- Table: `useTableRowExpansion` accepts the same `animatedLayout` handle, so opening or closing a row's panel glides the rows after it, dividers included, instead of jumping. Under Reduce Motion rows fade on touch and change at once with a mouse; tables with column lines change at once.+- TreeList chevrons and guide lines sit 4px closer to the start of the row, and the gap between chevron and label widens from 4px to 8px. Labels stay where they were.+- `Icon` takes an optional `variant` to ask the active theme for alternate artwork, for example `<Icon icon="info" variant="filled" />`. The theme's icon receives the variant only when the theme lists it in `iconVariants`; otherwise it draws its normal artwork. Icons you pass as components never receive `variant`, and it is never written to the page. Icons without `variant` render as before.+- A theme icon can now pick its artwork by size: an entry in `defineTheme({icons})` or `registerIcons()` can be a function of `{size, variant}`, and `Icon` calls it with the size it renders at. Returning `null` draws no icon. `getIcon`, `getExtendedIcon`, `getIconRegistry`, `useIcon`, and a theme's `icons` field still return nodes, reading a function at `{size: 'md'}`. Existing icon entries are unchanged.+- A theme can list the icon variants it supports, such as `filled`, with `defineTheme({iconVariants})`, and read them back from `theme.iconVariants`. Child themes inherit the list unless they set their own. `@astryxdesign/core/Icon` exports `IconVariantMap` and `IconVariant` for typing variants. Themes without `iconVariants` are unchanged.+- `astryx theme build` keeps function icons and icon variant lists, so a built theme draws each icon at the same size and variant as the live theme, including icons inherited from another theme. A theme that lists `iconVariants` gets matching types in `<theme>.variants.d.ts`. Themes without these features build exactly as before.+- Themes can set the real size of each Icon size: `width` and `height` in `px` or `rem` on `components.icon['size:sm']` (or `xsm`, `md`, `lg`) now resize the glyph itself, for named icons and SVG components, in live and built themes. Before, they sized only the box around the icon. Sizes a theme does not style still render at 12, 16, 20, or 24px at a 16px root. `astryx docs theme` gains an Icon sizes section.+- `useCombobox` (from `@astryxdesign/core/Selector`) can now build an accessible search-with-results on your own text field, such as a search box whose results replace part of the page, or an "add people" field in a dialog. Spread `getFieldProps` on your input, `getListboxProps` on your list, and `getOptionProps` on each option. Focus stays in the field, arrow keys move through results, Enter picks, and Escape hides the list without closing a surrounding dialog. Announce result counts yourself with `useAnnounce`. Existing uses behave as before.+- Navigation menus support press-and-slide, as DropdownMenu does: in NavHeadingMenu, TopNavMenu, SideNavHeading's menu, TopNavHeading's product menu, BreadcrumbItem's menu, and TabMenu, a press that slides across the items picks the one it lifts on, with the highlight following the pointer. Link items are no longer draggable. Keyboard and screen-reader behavior is unchanged.+- On touch screens, `ScrollableArea` shows the phone's own scroll indicator, which is easier to see than the faint bar it drew before. Mouse and trackpad scrollbars keep the neutral color. To keep the neutral color on touch screens too, set `scrollbarColor` through `xstyle`.+- New `--ease-exit` motion token for things leaving the screen, beside `--ease-standard` for things arriving. BottomSheet already closes on it, so nothing looks different, but a theme can now tune the exit. `astryx docs motion` and the theme template list it.++#### Fixes++- With an `animatedLayout` handle, content before a Collapsible or TreeList change now glides too when the layout moves it, for example items in a centered or end-aligned row.+- With an `animatedLayout` handle, content after a change now glides even when it carries a resting transform, such as a Button or a swipeable row at rest, instead of jumping.+- With an `animatedLayout` handle in a right-to-left container, content after a Collapsible or TreeList change now glides instead of jumping.+- Screen readers now hear announcements made inside an open Dialog, modal BottomSheet, modal Drawer, Lightbox, MobileNav, or CommandPalette. Before, `useAnnounce` messages went to a page region the open dialog hid. Messages sent as a dialog closes are spoken once it has closed. Your code needs no change. Not yet covered: CommandPalette's result counts, Lightbox's position and zoom messages, and Selector's and MultiSelector's sheet messages.+- `useAnnounce`: messages announced at the same moment are now read together, in order, instead of the last one replacing the others, and an identical repeat is read once. A screen reader no longer misses a result count announced next to a confirmation.+- A disabled ChatComposerInput keeps focus and its place in the tab order instead of sending focus to the page, and blocks editing and sending while keeping the draft.+- A disabled ComplexSelector ignores selections from a popup that was already open.+- Disabling an InputGroup now disables the inputs and Button addons inside it, unless a child sets its own state.+- A disabled Tokenizer blocks adding, creating, and removing tokens, and leaves its values out of form submission.+- Banner's status text color no longer leaks into your `endContent`, including dialogs opened from it.+- BottomSheet renders fewer page elements, with no visual change.+- With Reduce Motion on, BottomSheets (including `BottomSheetSwitcher` steps) no longer slide or scale: on touch screens they fade in place within 200 ms, and with a mouse or keyboard they change at once. A swipe-to-dismiss fades out in place.+- When a shorter BottomSheet replaces a taller one, the taller sheet moves down to meet it before fading, so the switch looks like one sheet changing height.+- Toasts shown from a `BottomSheetSwitcher` step appear above the flow and can be pressed. Before, the step covered them.+- Toasts appear above an open BottomSheet and can be pressed. Before, the sheet covered them, and pressing a toast's action could dismiss the sheet instead.+- Typeahead and CommandPalette no longer announce "Loading" after the results have already arrived.+- ClickableCard, SelectableCard, and interactive Thumbnails show their pressed state under a finger in apps that compile Astryx from source (the Vite and PostCSS integrations, and Storybook). Mouse hover and press, and the precompiled stylesheet, are unchanged.+- `ChatComposer`'s status bar announces each error and warning once, without its decorative icon, and no longer announces a status that is already showing when the page loads.+- Tapping the clear button of an unfocused TextInput or NumberInput now brings up the iPhone keyboard, without scrolling the page.+- In a CodeBlock with no title or language label, the Copy button no longer covers code. It sits in its own column beside the first line, so long lines stop before it, whether scrolled, wrapped, or right-to-left. Blocks with a header are unchanged.+- A long unbroken word, such as a URL or file path, in CommandPalette's empty message now wraps instead of spilling past both edges.+- ComplexSelector's trigger is now a combobox, so screen readers hear when the field is required. A custom `renderTrigger` control gets the same role and states, and a disabled one keeps its tab stop without opening. Tests that find the trigger with `getByRole('button')` should use `getByRole('combobox')`.+- ComplexSelector: your `aria-label` or `aria-labelledby` now names the built-in trigger instead of being ignored.+- A ContextMenu opened by a long press stays open when the finger lifts.+- With Reduce Motion on a touch screen, Dialog fades in within 200 ms instead of appearing abruptly. With a mouse it still appears at once.+- `DropdownMenuRadioItem` now runs your `onClick` and `onPointerMove` handlers, after it selects its value. Disabled rows still select nothing and don't call `onClick`. Its docs now mark `value` and `label` as required.+- EmptyState announces reliably: it no longer uses `role="status"`, which screen readers read inconsistently. An EmptyState that appears or changes after the page loads announces its title and description once; one present at load announces nothing. A `role` you pass now reaches it. Your code needs no change.+- Clearing a FileInput returns focus to its visible button, so screen readers announce the field again.+- On touch screens, Tooltip and HoverCard open only on a real tap. Starting a scroll on an info icon no longer pops them open.+- Rows with `swipeActions` no longer block pinch-zoom, and a second finger hands the gesture to the browser.+- With Reduce Motion on, tooltips, popovers, menus, and other layers opened by a finger fade in within 200 ms instead of appearing abruptly. With a mouse they still appear at once.+- `Layout` no longer uses a selector that could make the browser restyle the whole layout on every change, which slowed long documents. It looks the same.+- Lightbox fills the visible screen, so Safari's toolbar on iPhone no longer covers the caption.+- A Lightbox opened before its first item arrives now opens when the item does.+- In right-to-left pages, Lightbox's arrow keys now match its Next and Previous buttons.+- Multi-digit numbers in List and Markdown stay on one line in a shared number column, so text and nested lists stay aligned. Bullet lists keep their spacing.+- Numbered List and Markdown markers end on the same edge with even-width digits, so every period lines up.+- Pasted-text counts, spoken shortcut names, Ctrl and Esc key caps, and file-size limits are now translated and use local number formats.+- DropdownMenu and ContextMenu rows under the mouse no longer show a keyboard focus ring after a click.+- DropdownMenu, MoreMenu, and ContextMenu shown as bottom sheets no longer keep the sheet and every item on the page while closed.+- `MobileNav` is never wider than 85% of the screen, as documented, so even a 320px phone keeps a strip of page to tap to close it.+- MultiSelector keeps your `aria-labelledby`, read after the field's label.+- A disabled `NavHeadingMenuItem` with `href` no longer navigates when clicked or activated.+- Sliding the mouse across NavHeadingMenu or TabMenu items no longer selects their text.+- NumberInput keeps your `aria-labelledby`, read after the field's label.+- A disabled NumberInput stays in the tab order, so keyboard and screen-reader users can reach it and hear that it is unavailable. It is read-only and marked `aria-disabled="true"` instead of using the native `disabled` attribute. Part of #7814.+- `Overlay`, `DropdownMenuGroup`, and `MobileNavToggle` pass `id`, `data-*`, `aria-*`, and event handlers through to the page, so test ids and analytics attributes work on them.+- Pressing Escape right after opening a Popover or a collapsed SideNav submenu leaves focus on the trigger instead of moving it into hidden content.+- An open Popover no longer captures Tab presses made elsewhere on the page. Tab inside the popover still cycles, and Escape still closes it.+- A Popover rendered into an iframe or a picture-in-picture window now focuses, keeps Tab inside, closes on Escape, and returns focus as it does on the page.+- PowerSearch no longer announces its starting result count when it mounts in React StrictMode.+- On phones and tablets, presses made with a mouse, trackpad, or the Space key now show the pressed state.+- Type declarations resolve in projects that use `moduleResolution: NodeNext`.+- `RadioList` no longer makes large pages restyle every row's contents on each change. It looks and behaves the same.+- Scrollable areas (`ScrollableArea`, and Table, CodeBlock, BottomSheet, and Schedule viewports) join the tab order as soon as their content overflows, including content that loads already overflowing.+- SegmentedControl keeps your `aria-describedby`, read before the disabled reason.+- Selector keeps your `aria-labelledby`, read after the field's label.+- Selector's phone sheet no longer points screen readers at an option that hasn't appeared yet.+- A collapsed SideNav item's tooltip now belongs to the link or button itself, so keyboard focus shows the label and screen readers read it.+- SideNavHeading: `headerEndContent` now sits beside the heading link instead of inside it, so pressing a button there no longer also follows the link.+- SideNav's rail collapses and expands smoothly instead of snapping, and the page content inside AppShell moves with it. Under Reduce Motion it cross-fades on touch and changes at once otherwise.+- Skeleton keeps pulsing in Safari while the page runs JavaScript. It looks and times the same.+- Slider keeps your `aria-labelledby`, read after its label.+- An idle Slider no longer keeps a page-wide listener running.+- A Slider drag belongs to the finger that started it: a second finger can't take it over or end it, and two fingers can still drag two sliders at once.+- A clickable Step reads as "1 Account" instead of "1Account". Nothing changes on screen. Fixes #7966.+- A Switch with long content in its row no longer makes the row restyle on every change. Its focus ring looks the same; a link inside the label or description keeps its own focus ring.+- Tabs and TabMenu triggers no longer shrink below their labels on pages that reset `min-width`; the tab strip scrolls instead.+- Pinned Table columns keep their row dividers while the table scrolls sideways, including theme and custom border colors.+- A disabled TextInput or TextArea stays in the tab order, so keyboard and screen-reader users can reach it and hear that it is unavailable. It is read-only and marked `aria-disabled="true"` instead of using the native `disabled` attribute. Part of #7814.+- TextInput keeps your `aria-labelledby`, read after the field's label.+- Thumbnail's Open and Remove buttons stay in place, focusable and announced as disabled, while they can't act, so keyboard focus no longer drops to the page.+- A toast dismissed while hidden, or before it first appeared, now really leaves the stack instead of taking an empty slot later.+- Tokenizer and PowerSearch put the text cursor right after the last token, on the last row.+- Tokenizer and PowerSearch tokens wrap before the clear-all button and loading indicator instead of running under them, and rows don't shift when a search starts or ends.+- A Tooltip that moved clear of its trigger stays clear when the trigger moves or the page scrolls.+- A Tooltip taller than the space above and below its trigger no longer covers the trigger: it opens beside it, or on the side with more room and scrolls.+- With Reduce Motion on, TopNav's mega menu fades on touch screens and opens at once with a mouse, instead of rising.+- Sliding the mouse across TopNavMenu action items no longer selects their text.+- Typeahead and Tokenizer hide an old "no results" row while the next search is running.+- Tapping a Typeahead's selected value to edit it, or the clear button in a Selector or MultiSelector search row, now brings up the phone keyboard on the first tap.+- In Typeahead, Tokenizer, and PowerSearch menus, an option is highlighted only when the pointer moves over it, not when it slides under a resting mouse, so Enter no longer picks an option you didn't point at.+- `VisuallyHidden` content can no longer be made visible by accident: `xstyle`, `className`, and `style` no longer reach the element.++ Measured prop by prop against `main`'s implementation, before and after this change:++ - `xstyle` arrived as the attribute only — the `style` attribute was unaffected — so passing it left a stray attribute on the page and changed nothing you could see.+ - `className` never reached the element, before or after.+ - `style` did reach the element, and an inline style could un-hide the content. It no longer does; this is the one visible change.++ None of the three is styling surface on `VisuallyHiddenProps`: `className` and `style` reach the element only through a cast or an untyped spread, and `xstyle` is documented as ignored, so typed code loses nothing.++ `xstyle` stays declared on `VisuallyHiddenProps`, documented as ignored, so existing code keeps compiling.++- Pinch-zoom works again over the TimeInput, DateTimeInput, and DateInput picker wheels.++#### Performance++- With an `animatedLayout` handle, a change in a long Collapsible or TreeList measures the page once instead of once per row.+- Pages with many closed popovers, tooltips, and menus load faster.+- Closed Tooltips, Selectors, and ComplexSelectors render once when they mount, and Popovers and DropdownMenus render less.+- Scrolling a `ScrollableArea`, Table, CodeBlock, or BottomSheet body does less work on each frame, so scrolling stays smooth on busy pages.++#### Documentation++- EmptyState now announces through the page's shared announcer regions. In tests, `getByRole('status')` or `getByRole('alert')` may match those regions; scope the query with `within(container)`.+- Badge's docs mark `label` as required, matching its types.+- `DropdownMenuSubMenu`'s docs mark `label` and `children` as required, document `menuDataTestId`, and state that `presentation` defaults to `'adaptive'`.+- `ListItem`'s docs now say that `isSelected` marks the row as the current item with `aria-current="true"`.+- Package links now point to the project's GitHub home, `meta/astryx`.+- SelectableCard's guidance no longer recommends it for single-choice groups, since each card is a checkbox.+- TabList's description no longer promises a built-in "more" menu (a narrow tab strip scrolls), and the library page template describes `MobileNav` as the slide-out drawer it is.++#### Contributors++Thanks to everyone who contributed to this release:++- @aashish254+- @cixzhang+- @ejhammond+- @ernestt+- @harjothkhara+- @HelloOjasMutreja+- @imdreamrunner+- @kentonquatman+- @korkt-kim+- @kyu-rong+- @light-merlin-dark+- @nynexman4464+- @parinith-web+- @rubyycheung+- @thewebartisan7+- @vjeux++---+# 0.7.4#### New Featuresdiff --git a/packages/richtext/CHANGELOG.md b/packages/richtext/CHANGELOG.mdindex edc3fdfe35..71ea3e1e82 100644--- a/packages/richtext/CHANGELOG.md+++ b/packages/richtext/CHANGELOG.md@@ -1,5 +1,48 @@# @astryxdesign/richtext+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++- `RichTextEditor` and `RichTextView` take `codeLanguages`, the same list `Markdown` takes, so code looks the same while reading and editing.++#### Fixes++- Type declarations resolve in projects that use `moduleResolution: NodeNext`.+- In `RichTextEditor` and `RichTextView`, a code block with no language leaves room for its Copy button, so long lines wrap before it. The block is as tall as in `Markdown`, so switching between reading and editing no longer shifts the page.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @harjothkhara+- @rubyycheung++---+# 0.7.4---diff --git a/packages/themes/butter/CHANGELOG.md b/packages/themes/butter/CHANGELOG.mdindex 40e1f4d962..7ab5ab2f36 100644--- a/packages/themes/butter/CHANGELOG.md+++ b/packages/themes/butter/CHANGELOG.md@@ -1,5 +1,40 @@# @xds/theme-butter+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @rubyycheung++---+# 0.7.4#### New Featuresdiff --git a/packages/themes/chocolate/CHANGELOG.md b/packages/themes/chocolate/CHANGELOG.mdindex a12ba8e629..1f0d93def3 100644--- a/packages/themes/chocolate/CHANGELOG.md+++ b/packages/themes/chocolate/CHANGELOG.md@@ -1,5 +1,40 @@# @xds/theme-chocolate+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @rubyycheung++---+# 0.7.4---diff --git a/packages/themes/gothic/CHANGELOG.md b/packages/themes/gothic/CHANGELOG.mdindex a67382bc7a..dc72206b5c 100644--- a/packages/themes/gothic/CHANGELOG.md+++ b/packages/themes/gothic/CHANGELOG.md@@ -1,5 +1,40 @@# @xds/theme-gothic+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @rubyycheung++---+# 0.7.4#### New Featuresdiff --git a/packages/themes/matcha/CHANGELOG.md b/packages/themes/matcha/CHANGELOG.mdindex b25e04104d..5c279d11f9 100644--- a/packages/themes/matcha/CHANGELOG.md+++ b/packages/themes/matcha/CHANGELOG.md@@ -1,5 +1,40 @@# @xds/theme-matcha+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @rubyycheung++---+# 0.7.4#### New Featuresdiff --git a/packages/themes/neutral/CHANGELOG.md b/packages/themes/neutral/CHANGELOG.mdindex 4a33c14a3c..3517144243 100644--- a/packages/themes/neutral/CHANGELOG.md+++ b/packages/themes/neutral/CHANGELOG.md@@ -1,5 +1,40 @@# @xds/theme-neutral+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @rubyycheung++---+# 0.7.4---diff --git a/packages/themes/stone/CHANGELOG.md b/packages/themes/stone/CHANGELOG.mdindex 200c6bff2a..62f8e2b06f 100644--- a/packages/themes/stone/CHANGELOG.md+++ b/packages/themes/stone/CHANGELOG.md@@ -1,5 +1,40 @@# @xds/theme-stone+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @rubyycheung++---+# 0.7.4#### New Featuresdiff --git a/packages/themes/y2k/CHANGELOG.md b/packages/themes/y2k/CHANGELOG.mdindex 27980b503f..b206b3433e 100644--- a/packages/themes/y2k/CHANGELOG.md+++ b/packages/themes/y2k/CHANGELOG.md@@ -1,5 +1,40 @@# @xds/theme-y2k+# 0.7.5++#### New Features++- Status colors are readable everywhere they appear, and Info is a status of its own. Each status (info, success, warning, error) now has a strong fill (`--color-<status>`) with content on it (`--color-on-<status>`, at least 4.5:1), a pale fill (`--color-<status>-muted`) with its content (`--color-on-<status>-muted`), and readable text for the page and cards (`--color-text-<status>`). Status icons (`--color-icon-<status>`) and borders (`--color-border-<status>`) default to the readable text color. The Info roles (`--color-info`, `--color-on-info`, `--color-info-muted`, …) are new and no longer borrow your accent color.++ `--color-success`, `--color-warning`, and `--color-error` and `bg-<status>` keep their meaning as the strong fills. In Tailwind, `bg-info`, `bg-info-muted`, `text-on-<status>`, `text-on-<status>-muted`, and `text-status-<status>` are new; `text-`, `decoration-`, `placeholder-`, and `caret-<status>` now use the readable text shade, and `border-`, `divide-`, `outline-`, and `ring-<status>` use the border shade, while `bg-`, `accent-`, `fill-`, `stroke-<status>`, shadows, and gradients keep the strong fill. For example, Core's light `text-warning` is now `#753F07` instead of `#E9AF08`. To keep the fill color on text, write `text-[var(--color-warning)]`.++ What changes on screen:++ - Core's dark Error content (`--color-on-error`) is now `#0A1317` instead of white, so text on dark-mode error fills reaches 4.5:1. Core's Info Badge uses `#0064E0` instead of the accent (`#2694FE` in dark mode).+ - Status icons (Icon `color="info|success|warning|error"`), Stepper status glyphs, and Chat tool-call status icons use the readable shades. Core's light success icon is now `#09441F` instead of `#0D8626`.+ - Input and FileInput status borders use the border shades. Core's light warning border is now `#753F07` instead of `#E9AF08`, and Butter's light success and warning input borders reach 3:1.+ - Banner draws its title, description, icon, and controls in the on-muted colors, and fills Info with `--color-info-muted`.+ - Status fills keep a visible edge in forced-colors mode.+ - Content on Chocolate and Matcha success and error fills, and on Stone success, warning, and error fills, now reaches 4.5:1.+ - Every first-party theme sets a blue Info. Chocolate and Matcha Info Badges move from the accent to that blue; Butter keeps its own Info Badge colors.+ - Neutral's `--color-success`, `--color-warning`, and `--color-error` are now the fills its Badges already showed, and its `--color-info` is `#0074E2` (`#6D9CFE` in dark mode). Its Badges, StatusDots, progress fills, and Stepper badges look the same; its accent ProgressBar, StatusDot, and Stepper now use Neutral's accent instead of blue.+ - Neutral no longer defines its undocumented local status tokens. Use the standard roles instead: `--astryx-theme-neutral-color-status-fill-success`, `-status-fill-warning`, and `-status-fill-error` → `--color-success`, `--color-warning`, `--color-error`; `-status-muted-accent` → `--color-info-muted`; `-on-tint-neutral` → `--color-neutral`; the `-on-tint-overlay-*` and `-destructive-overlay-*` tokens → `--color-overlay-hover` and `--color-overlay-pressed`. `--astryx-theme-neutral-color-status-fill-accent` keeps its value but is deprecated.++ Custom themes get the content and text roles they don't set: they are derived from the theme's status fills. To keep a component's previous color, set the matching role, for example `--color-icon-success` to your old `--color-success`.++#### Documentation++- Package links now point to the project's GitHub home, `meta/astryx`.++#### Contributors++Thanks to everyone who contributed to this release:++- @cixzhang+- @rubyycheung++---+# 0.7.4#### New Features