An open source design system that's fully customizable and agent ready
TypeScript
docs: audit, credit and consolidate changesets for v0.4.0 (#4997)
Cindy Zhanga5356783109a
diff --git a/.changeset/alertdialog-inline-role-and-initial-focus.md b/.changeset/alertdialog-inline-role-and-initial-focus.mdnew file mode 100644index 0000000000..f74fe0f377--- /dev/null+++ b/.changeset/alertdialog-inline-role-and-initial-focus.md@@ -0,0 +1,11 @@+---+'@astryxdesign/core': patch+---++[fix] AlertDialog: correct the inline role and pin initial focus (#4887).++The `isInline` preview path no longer renders `role="alertdialog"`. That role promises a modal interruption — focus trap, inert page, explicit dismissal — and the inline path is an always-present, non-modal preview with none of it. It now renders `role="group"`, keeping the title and description associated through `aria-labelledby`/`aria-describedby`.++The cancel button now carries `data-autofocus`, so the documented "initial focus goes to the cancel button" behavior is pinned instead of depending on cancel happening to be the first focusable node in the footer. Docs now name and link the WAI-ARIA APG Alert Dialog pattern the component implements, and gain an anatomy section.++@cixzhangdiff --git a/.changeset/alertdialog-inline-role.md b/.changeset/alertdialog-inline-role.mddeleted file mode 100644index 004fdd2975..0000000000--- a/.changeset/alertdialog-inline-role.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] AlertDialog: the `isInline` preview path no longer renders `role="alertdialog"`. That role promises a modal interruption — focus trap, inert page, explicit dismissal — and the inline path is an always-present, non-modal preview with none of it. It now renders `role="group"`, keeping the title and description associated through `aria-labelledby`/`aria-describedby`.--@cixzhangdiff --git a/.changeset/alertdialog-pin-initial-focus.md b/.changeset/alertdialog-pin-initial-focus.mddeleted file mode 100644index 298e6b525e..0000000000--- a/.changeset/alertdialog-pin-initial-focus.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] AlertDialog: the cancel button now carries `data-autofocus`, so the documented "initial focus goes to the cancel button" behavior is pinned instead of depending on cancel happening to be the first focusable node in the footer. Docs now name and link the WAI-ARIA APG Alert Dialog pattern the component implements, and gain an anatomy section.--@cixzhangdiff --git a/.changeset/appshell-doc-example-mobilenav-header.md b/.changeset/appshell-doc-example-mobilenav-header.mdindex 083de8eb25..fd54810d59 100644--- a/.changeset/appshell-doc-example-mobilenav-header.md+++ b/.changeset/appshell-doc-example-mobilenav-header.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[docs] AppShell: the two worked examples of the `mobileNav` escape hatch passed `title` to `MobileNav`, which does not accept it: `MobileNavProps` omits the native `title` attribute and the drawer heading prop is `header`. Copying either example produced a type error and a drawer with no heading. Both now say `header`. The doc also gains an anatomy list and accessibility guidance covering the landmark structure AppShell owns.+[docs] AppShell: the two worked examples of the `mobileNav` escape hatch passed `title` to `MobileNav`, which does not accept it: `MobileNavProps` omits the native `title` attribute and the drawer heading prop is `header`. Copying either example produced a type error and a drawer with no heading. Both now say `header`. The doc also gains an anatomy list and accessibility guidance covering the landmark structure AppShell owns. (#4944)@cixzhangdiff --git a/.changeset/appshell-landmark-and-skip-link.md b/.changeset/appshell-landmark-and-skip-link.mdnew file mode 100644index 0000000000..0b5d310459--- /dev/null+++ b/.changeset/appshell-landmark-and-skip-link.md@@ -0,0 +1,11 @@+---+'@astryxdesign/core': patch+---++[fix] AppShell: two a11y fixes to the shell chrome (#4944).++The mobile top bar rendered for a sidenav-only layout is now a `banner` landmark, matching the header region of a layout that has a `topNav`. Previously the page's landmark structure changed depending on which nav slots it filled: a screen-reader user on a small viewport got no banner region at all. When a `banner` slot is present the existing header keeps the role, so there is still exactly one.++The skip link now draws the shared Astryx focus ring instead of the browser default outline, so it follows `--color-accent` and matches every other focusable surface in a custom theme.++@cixzhangdiff --git a/.changeset/appshell-mobile-banner-landmark.md b/.changeset/appshell-mobile-banner-landmark.mddeleted file mode 100644index 59fde20c51..0000000000--- a/.changeset/appshell-mobile-banner-landmark.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] AppShell: the mobile top bar rendered for a sidenav-only layout is now a `banner` landmark, matching the header region of a layout that has a `topNav`. Previously the page's landmark structure changed depending on which nav slots it filled: a screen-reader user on a small viewport got no banner region at all. When a `banner` slot is present the existing header keeps the role, so there is still exactly one.--@cixzhangdiff --git a/.changeset/appshell-skip-link-focus-ring.md b/.changeset/appshell-skip-link-focus-ring.mddeleted file mode 100644index d51ebe248f..0000000000--- a/.changeset/appshell-skip-link-focus-ring.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[fix] AppShell: the skip link now draws the shared Astryx focus ring instead of the browser default outline, so it follows `--color-accent` and matches every other focusable surface in a custom theme.--@cixzhangdiff --git a/.changeset/aspectratio-sizing-contract-docs.md b/.changeset/aspectratio-sizing-contract-docs.mdindex 4ef22dbd1f..92f346f27f 100644--- a/.changeset/aspectratio-sizing-contract-docs.md+++ b/.changeset/aspectratio-sizing-contract-docs.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[docs] AspectRatio: document the sizing contract and add the missing anatomy. The box takes its width from its container and derives its height from the ratio, so constraining only the height clamps it off ratio (pass `width: 'auto'` alongside) and a shrink-to-fit parent collapses it to zero width. Both are now in the component JSDoc and in `bestPractices`, along with the single-child expectation: with `fit` set, every direct child is stretched to fill the box. The image-gallery example block now uses `var(--radius-element)` instead of a raw `8`.+[docs] AspectRatio: document the sizing contract and add the missing anatomy. The box takes its width from its container and derives its height from the ratio, so constraining only the height clamps it off ratio (pass `width: 'auto'` alongside) and a shrink-to-fit parent collapses it to zero width. Both are now in the component JSDoc and in `bestPractices`, along with the single-child expectation: with `fit` set, every direct child is stretched to fill the box. The image-gallery example block now uses `var(--radius-element)` instead of a raw `8`. (#4984)@cixzhangdiff --git a/.changeset/avatar-fallback-theme-target.md b/.changeset/avatar-fallback-theme-target.mdindex 6e4e8872c3..ff811b43a9 100644--- a/.changeset/avatar-fallback-theme-target.md+++ b/.changeset/avatar-fallback-theme-target.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] Avatar: the fallback surface (initials and default icon) is now a direct theme target via the stable `astryx-avatar-fallback` class. Theme its background, text color, font weight, and per-size font size through the `avatar-fallback` component key (e.g. `components: { 'avatar-fallback': { base: { backgroundColor: '...' }, 'size:sm': { fontSize: '...' } } }`), replacing the internal `--_avatar-fallback-*` derived vars.+[feat] Avatar: the fallback surface (initials and default icon) is now a direct theme target via the stable `astryx-avatar-fallback` class. Theme its background, text color, font weight, and per-size font size through the `avatar-fallback` component key (e.g. `components: { 'avatar-fallback': { base: { backgroundColor: '...' }, 'size:sm': { fontSize: '...' } } }`), replacing the internal `--_avatar-fallback-*` derived vars. (#4716)@cixzhangdiff --git a/.changeset/avatar-initials-grapheme-clusters.md b/.changeset/avatar-initials-grapheme-clusters.mdindex ce37a673bd..37ca6a94c9 100644--- a/.changeset/avatar-initials-grapheme-clusters.md+++ b/.changeset/avatar-initials-grapheme-clusters.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Avatar: fallback initials no longer break for names containing emoji or other multi-codepoint characters.+[fix] Avatar: fallback initials no longer break for names containing emoji or other multi-codepoint characters. (#4750)@alex-js-ltddiff --git a/.changeset/build-vite-esm-fs-require.md b/.changeset/build-vite-esm-fs-require.mdindex c975666dc7..e9b5004ac2 100644--- a/.changeset/build-vite-esm-fs-require.md+++ b/.changeset/build-vite-esm-fs-require.md@@ -2,7 +2,7 @@'@astryxdesign/build': patch----[fix] build: import `node:fs` statically so the Vite plugin's package discovery survives the ESM build+[fix] build: import `node:fs` statically so the Vite plugin's package discovery survives the ESM build (#4972)`astryxStylex()`'s config plugin discovered installed `@astryxdesign/*` packages with `require('node:fs')`. The `./vite` export ships only an ESM bundle (`dist/vite.mjs`, esbuild `format: 'esm'`), where esbuild lowers `require` to a shim that throws `Dynamic require of "node:fs" is not supported` — always, since native `require` never exists under ESM. The surrounding `try/catch` swallowed the throw, so `optimizeDeps.exclude` silently fell back to `['@astryxdesign/core']` and every other installed Astryx package stayed eligible for Vite pre-bundling, which strips `stylex.create`/`defineVars` calls and causes runtime errors.diff --git a/.changeset/chat-layout-scroll-button-icon-only.md b/.changeset/chat-layout-scroll-button-icon-only.mdindex fbb9ba8e26..92768d694c 100644--- a/.changeset/chat-layout-scroll-button-icon-only.md+++ b/.changeset/chat-layout-scroll-button-icon-only.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] ChatLayoutScrollButton: the default (label-less) state now renders as icon-only, with the translated "Scroll to bottom" string as the accessible name only. It was previously missing `isIconOnly` on its inner `Button`, so Button's default (visible-text) contract rendered the translation as clipped visible text inside the circular button instead.+[fix] ChatLayoutScrollButton: the default (label-less) state now renders as icon-only, with the translated "Scroll to bottom" string as the accessible name only. It was previously missing `isIconOnly` on its inner `Button`, so Button's default (visible-text) contract rendered the translation as clipped visible text inside the circular button instead. (#4854)@HelloOjasMutrejadiff --git a/.changeset/chat-theme-props-and-classname.md b/.changeset/chat-theme-props-and-classname.mdnew file mode 100644index 0000000000..8d1878327b--- /dev/null+++ b/.changeset/chat-theme-props-and-classname.md@@ -0,0 +1,7 @@+---+'@astryxdesign/core': patch+---++[fix] Chat: the dictation and scroll buttons now carry their `chat-dictation-button` and `chat-layout-scroll-button` theme targets, and ChatSendButton no longer clobbers a consumer's `className` (#4634).++@cixzhangdiff --git a/.changeset/chat-tool-calls-hover-radius-clip.md b/.changeset/chat-tool-calls-hover-radius-clip.mdindex 8ba0be120a..8fa37f9bda 100644--- a/.changeset/chat-tool-calls-hover-radius-clip.md+++ b/.changeset/chat-tool-calls-hover-radius-clip.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] ChatToolCalls: hover backgrounds on grouped call rows (2+ calls) now keep their full `--radius-element` rounding instead of getting clipped flat on the inline edges. `groupContentInner` — the `overflow: hidden` clip boundary the expand/collapse height animation needs — was missing the padding/negative-margin pair that absorbs the row-level hover-background overhang, so the overhang extended past the clip boundary and got cut off. Matches the ungrouped single-call row, which has no such wrapper to clip it.+[fix] ChatToolCalls: hover backgrounds on grouped call rows (2+ calls) now keep their full `--radius-element` rounding instead of getting clipped flat on the inline edges. `groupContentInner` — the `overflow: hidden` clip boundary the expand/collapse height animation needs — was missing the padding/negative-margin pair that absorbs the row-level hover-background overhang, so the overhang extended past the clip boundary and got cut off. Matches the ungrouped single-call row, which has no such wrapper to clip it. (#4858)@HelloOjasMutrejadiff --git a/.changeset/cli-agent-docs-layout-pointer.md b/.changeset/cli-agent-docs-layout-pointer.mdindex 81dd03e9cf..2c1bebb459 100644--- a/.changeset/cli-agent-docs-layout-pointer.md+++ b/.changeset/cli-agent-docs-layout-pointer.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[fix] The generated agent cheat sheet hardcoded a shell recommendation ("Full page → AppShell; sidebar nav → SideNav", "pick the shell (AppShell / Layout+LayoutPanel)"), which answers a question that depends on the app archetype and duplicates guidance `astryx docs layout` already maintains. The two layout rules now send agents to that doc instead, so shell choice, region budgets, and the responsive contract have one source of truth.+[fix] The generated agent cheat sheet hardcoded a shell recommendation ("Full page → AppShell; sidebar nav → SideNav", "pick the shell (AppShell / Layout+LayoutPanel)"), which answers a question that depends on the app archetype and duplicates guidance `astryx docs layout` already maintains. The two layout rules now send agents to that doc instead, so shell choice, region budgets, and the responsive contract have one source of truth. (#4772)The rule cites the command rather than the docsite URL, in the block's established `astryx <cmd>` form that the header maps to the project's real invocation (`pnpm exec astryx`, `npx @astryxdesign/cli`, …). `astryx docs` reads the docs shipped inside the installed version, so an agent can't be shown an API that release doesn't have.@josephfarinadiff --git a/.changeset/cli-fix-grid-minchildwidth-columns-combo.md b/.changeset/cli-fix-grid-minchildwidth-columns-combo.mdindex c20e48dd56..06fa289255 100644--- a/.changeset/cli-fix-grid-minchildwidth-columns-combo.md+++ b/.changeset/cli-fix-grid-minchildwidth-columns-combo.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[fix] The `migrate-grid-minchildwidth-to-columns` codemod bailed without changes when a `<Grid>` had both `columns` and `minChildWidth`, leaving the now-invalid `minChildWidth` prop in place and failing type-checking on 0.3.0.+[fix] The `migrate-grid-minchildwidth-to-columns` codemod bailed without changes when a `<Grid>` had both `columns` and `minChildWidth`, leaving the now-invalid `minChildWidth` prop in place and failing type-checking on 0.3.0. (#4792)When `columns` is a numeric literal, it now migrates losslessly to the 0.3.0 object form. This mirrors the old (0.2.0) Grid runtime, where `minChildWidth` dominated and the numeric `columns` capped the column count under `auto-fit`: `<Grid columns={3} minChildWidth={280}>` becomes `<Grid columns={{minWidth: 280, max: 3, repeat: 'fit'}}>`. Object or dynamic `columns` values remain a deliberate bail.diff --git a/.changeset/cli-fix-hook-example.md b/.changeset/cli-fix-hook-example.mdindex 83e2aa6612..63bd3c5336 100644--- a/.changeset/cli-fix-hook-example.md+++ b/.changeset/cli-fix-hook-example.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[fix] The documented `hook` example referenced `useToggle`, which is not a hook in the design system — running it failed with `ERR_UNKNOWN_HOOK`. It now uses `useFocusTrap`.+[fix] The documented `hook` example referenced `useToggle`, which is not a hook in the design system — running it failed with `ERR_UNKNOWN_HOOK`. It now uses `useFocusTrap`. (#4742)This shipped in two places a consumer sees: `astryx manifest --json`, which agents read to learn the CLI, and the `hook` CommandDoc that feeds `--help`. Replaced in both.@josephfarinadiff --git a/.changeset/cli-foundation-layering-and-authoring-types.md b/.changeset/cli-foundation-layering-and-authoring-types.mdnew file mode 100644index 0000000000..3d812e5d9d--- /dev/null+++ b/.changeset/cli-foundation-layering-and-authoring-types.md@@ -0,0 +1,11 @@+---+'@astryxdesign/cli': patch+---++[fix] CLI internals: a true `foundation/` bottom layer, and generated `./authoring` types (#4736).++`foundation/` no longer imports `api/`, and ESLint now enforces that direction alongside the existing `authoring/` and `api/` rules. Two things were reaching upward: `Project` pulled template discovery out of `api/template`, whose adapter imported `Project` straight back, and both `Project` and `integration-warnings` imported `validateLoadedIntegration` from the `validate-integration` command. Neither was misplaced logic, just misplaced files — the adapter now lives at `foundation/discovery/template-adapter.mjs` and the validators at `foundation/integrations/validate-contributions.mjs`. To be precise: `Project` and the template adapter still import each other, so that module cycle remains, contained within foundation instead of spanning two layers. Behavior-preserving — the CLI's observable surface is byte-identical across 84 invocations.++The published `./authoring` type declarations are now generated from their JSDoc instead of hand-written, the same way `./api` already works. The 13 hand-maintained `.d.mts` files are gone; `scripts/sync-api-types.mjs` emits both trees at `prepack`, stamped `@generated`. A hand-written declaration shadows the JSDoc in its `.mjs`, so it could disagree with the implementation and still compile — and both failure modes had shipped: a missing declaration made a strict consumer resolve that parser as `any`, and a stale `parseDoc` return union silently dropped `SchemaDoc`, `CommandDoc` and `EnumDoc`. Also fixes `parseFunction`, a bare re-export of `parseHook` that published `HookDoc` instead of the general `FunctionDoc`.++@josephfarinadiff --git a/.changeset/cli-foundation-layering.md b/.changeset/cli-foundation-layering.mddeleted file mode 100644index c7b64eee2c..0000000000--- a/.changeset/cli-foundation-layering.md+++ /dev/null@@ -1,14 +0,0 @@-----'@astryxdesign/cli': patch------[fix] Make `foundation/` a true bottom layer: it no longer imports `api/`, and ESLint now enforces that direction alongside the existing `authoring/` and `api/` rules.--Two things were reaching upward. `Project` pulled template discovery out of `api/template`, whose adapter imported `Project` straight back — so the module cycle ran across the layer boundary. And both `Project` and `integration-warnings` imported `validateLoadedIntegration` from the `validate-integration` command.--Neither was really misplaced logic, just misplaced files: the template adapter had no `api/` imports at all, and the contribution validators are shared infra that foundation itself runs. The adapter now lives at `foundation/discovery/template-adapter.mjs` and the validators at `foundation/integrations/validate-contributions.mjs`, so both sit with their callers.--To be precise about what did and did not change: `Project` and the template adapter still import each other, so the module cycle itself remains — it is simply contained within foundation now instead of spanning two layers. The redundant nested `Project.load()` inside integration-template discovery, and `Project.templates()` filtering those integration templates back out, are also untouched. Both are worth cleaning up, but doing so would change behavior, and this change is deliberately behavior-preserving.--Internal only — no public API change, and no behavior change: the CLI's observable surface (help, command output, error paths, exit codes) is byte-identical across 84 invocations.-@josephfarinadiff --git a/.changeset/cli-generated-authoring-types.md b/.changeset/cli-generated-authoring-types.mddeleted file mode 100644index 8a4de37443..0000000000--- a/.changeset/cli-generated-authoring-types.md+++ /dev/null@@ -1,12 +0,0 @@-----'@astryxdesign/cli': patch------[fix] Generate the published `./authoring` type declarations from their JSDoc instead of hand-writing them, the same way `./api` already works. The 13 hand-maintained `.d.mts` files are gone; `scripts/sync-api-types.mjs` now emits both trees at `prepack`, stamped `@generated`.--A hand-written declaration shadows the JSDoc in its `.mjs`, so it could disagree with the implementation and still compile. Both failure modes had shipped: a missing declaration made a strict consumer resolve that parser as `any`, and a stale `parseDoc` return union silently dropped `SchemaDoc`, `CommandDoc`, and `EnumDoc` — so consumers could not narrow a parsed doc to those kinds. Generation makes both impossible: `tsc` now rejects a `@returns` that disagrees with the code before a declaration can even be emitted.--Also fixes `parseFunction`, which was a bare re-export of `parseHook` and therefore published `HookDoc` as its return type instead of the general `FunctionDoc`. It is now a thin typed wrapper; runtime behavior (including error message prefixes) is unchanged.--The published `./authoring` surface is now covered by the same end-to-end pack-and-typecheck CI gate as `./api`.-@josephfarinadiff --git a/.changeset/cli-login-templates-center-padding.md b/.changeset/cli-login-templates-center-padding.mdnew file mode 100644index 0000000000..5a3da9efc1--- /dev/null+++ b/.changeset/cli-login-templates-center-padding.md@@ -0,0 +1,7 @@+---+'@astryxdesign/cli': patch+---++[chore] The scaffolded login pages use `Center`'s `padding` prop instead of a hand-written `var(--spacing-6)` style object (#4764).++@jiunshinndiff --git a/.changeset/cli-migrate-table-rowexpansion-to-tree.md b/.changeset/cli-migrate-table-rowexpansion-to-tree.mdindex 56237424b3..a046031f62 100644--- a/.changeset/cli-migrate-table-rowexpansion-to-tree.md+++ b/.changeset/cli-migrate-table-rowexpansion-to-tree.md@@ -2,6 +2,6 @@'@astryxdesign/cli': patch----[feat] Add the `migrate-table-rowexpansion-to-tree` codemod (runs on `astryx upgrade`): rewrites the removed `useTableRowExpansionState` tree pattern to `useTableTreeState` + `useTableTreeData`. Detail-panel usage (`renderExpanded`) is left untouched.+[feat] Add the `migrate-table-rowexpansion-to-tree` codemod (runs on `astryx upgrade`): rewrites the removed `useTableRowExpansionState` tree pattern to `useTableTreeState` + `useTableTreeData`. Detail-panel usage (`renderExpanded`) is left untouched. (#4884)@humbertovirtudesdiff --git a/.changeset/cli-scaffold-video-placeholder.md b/.changeset/cli-scaffold-video-placeholder.mdindex 6882b3871f..29449ccd55 100644--- a/.changeset/cli-scaffold-video-placeholder.md+++ b/.changeset/cli-scaffold-video-placeholder.md@@ -2,6 +2,6 @@'@astryxdesign/cli': patch----[fix] Scaffolding a template that references demo video (e.g. `LightboxVideo`) no longer replaces the video source with the image placeholder data URI, which the generated `<video>` element couldn't play. `stripTemplateAssetRefs()` treated every demo-media reference as an image regardless of extension; video extensions (`.mp4`, `.webm`, `.mov`, `.ogv`) are now stripped to an empty `src` instead — there's no equivalent self-contained inline placeholder for video, so the scaffolded example is honest about needing the builder to supply their own file rather than pointing at something that can't play.+[fix] Scaffolding a template that references demo video (e.g. `LightboxVideo`) no longer replaces the video source with the image placeholder data URI, which the generated `<video>` element couldn't play. `stripTemplateAssetRefs()` treated every demo-media reference as an image regardless of extension; video extensions (`.mp4`, `.webm`, `.mov`, `.ogv`) are now stripped to an empty `src` instead — there's no equivalent self-contained inline placeholder for video, so the scaffolded example is honest about needing the builder to supply their own file rather than pointing at something that can't play. (#4863)@HelloOjasMutrejadiff --git a/.changeset/cli-self-documenting-docs.md b/.changeset/cli-self-documenting-docs.mdindex eb0f5de20b..4d0e1cdca9 100644--- a/.changeset/cli-self-documenting-docs.md+++ b/.changeset/cli-self-documenting-docs.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[feat] Add a self-documenting layer to the CLI: typed, colocated `.doc.mjs` for every command, every `@astryxdesign/cli/api` function, and every authored schema (config, integration, codemod, the response envelope, and the doc-types themselves). Adds the `FunctionDoc`, `SchemaDoc`, `CommandDoc`, and `EnumDoc` authoring types with sealed parsers.+[feat] Add a self-documenting layer to the CLI: typed, colocated `.doc.mjs` for every command, every `@astryxdesign/cli/api` function, and every authored schema (config, integration, codemod, the response envelope, and the doc-types themselves). Adds the `FunctionDoc`, `SchemaDoc`, `CommandDoc`, and `EnumDoc` authoring types with sealed parsers. (#4714)Every command's `--help` and its `astryx manifest` entry are now built from that command's colocated `CommandDoc` via a `defineCommand` converter, so the docs and the CLI can no longer describe different things. The migration is behavior-preserving: help text, command output, error paths, and exit codes are byte-identical.diff --git a/.changeset/codeblock-copy-button-themeable.md b/.changeset/codeblock-copy-button-themeable.mdindex b3c11a04de..138c0aee5b 100644--- a/.changeset/codeblock-copy-button-themeable.md+++ b/.changeset/codeblock-copy-button-themeable.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[feat] CodeBlock: the built-in copy button is now a themeable ghost `IconButton` with a default "Copy code" tooltip, reachable via the stable `astryx-codeblock-copy-button` class (theme it through the `codeblock-copy-button` component key). Restyle or keep the copy control without turning it off and re-implementing it. The tooltip stays "Copy code" after copying — the copy→check icon flip is the confirmation.+[feat] CodeBlock: the built-in copy button is now a themeable ghost `IconButton` with a default "Copy code" tooltip, reachable via the stable `astryx-codeblock-copy-button` class (theme it through the `codeblock-copy-button` component key). Restyle or keep the copy control without turning it off and re-implementing it. The tooltip stays "Copy code" after copying — the copy→check icon flip is the confirmation. (#4867)[feat] New `useClipboard` hook (`@astryxdesign/core/hooks`): the shared copy-to-clipboard behavior — clipboard write, a transient `isCopied` flag with its reset timer, and an optional polite screen-reader announcement. CodeBlock and Timestamp now build their copy buttons on it; reach for it directly for copy affordances that are not a plain icon button.diff --git a/.changeset/codeblock-header-title-targets.md b/.changeset/codeblock-header-title-targets.mdindex f5bb41af89..3634a26258 100644--- a/.changeset/codeblock-header-title-targets.md+++ b/.changeset/codeblock-header-title-targets.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] CodeBlock: add `codeblock-header` and `codeblock-title` theme targets on the header row and the title/language-label element. A theme can now restyle the header (e.g. padding) and the title (e.g. font size) directly, instead of reaching them through structural `> div:first-child > div > span` selectors that reverse-engineer the header layout. Both reflect the `size`/`language`(`/container`) visual props like the root.+[feat] CodeBlock: add `codeblock-header` and `codeblock-title` theme targets on the header row and the title/language-label element. A theme can now restyle the header (e.g. padding) and the title (e.g. font size) directly, instead of reaching them through structural `> div:first-child > div > span` selectors that reverse-engineer the header layout. Both reflect the `size`/`language`(`/container`) visual props like the root. (#4943)@freddymetadiff --git a/.changeset/complex-selector-popup-above-clearance.md b/.changeset/complex-selector-popup-above-clearance.mdindex f1fb113a82..43375dba85 100644--- a/.changeset/complex-selector-popup-above-clearance.md+++ b/.changeset/complex-selector-popup-above-clearance.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `ComplexSelector`'s popup now keeps its 4px clearance from the trigger when `placement="above"`, matching `placement="below"` and `Popover`. The popup's margin was set on `marginBlockStart` only, which is correct for a popup opening downward but leaves zero clearance on the edge that matters when it opens upward.+[fix] `ComplexSelector`'s popup now keeps its 4px clearance from the trigger when `placement="above"`, matching `placement="below"` and `Popover`. The popup's margin was set on `marginBlockStart` only, which is correct for a popup opening downward but leaves zero clearance on the edge that matters when it opens upward. (#4861)@HelloOjasMutrejadiff --git a/.changeset/complexselector-focus-visible-ring.md b/.changeset/complexselector-focus-visible-ring.mdindex 2889a58c92..0c5877a386 100644--- a/.changeset/complexselector-focus-visible-ring.md+++ b/.changeset/complexselector-focus-visible-ring.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] ComplexSelector: the trigger's focus ring is now keyboard-only. It was drawn from `:focus-within`, which also matches a mouse click — open the popover with the mouse, dismiss it with the mouse, and the restored focus left a pointer user staring at a keyboard affordance. It now uses the shared `:has(:focus-visible)` ring, which also brings the outline to the documented 3px offset.+[fix] ComplexSelector: the trigger's focus ring is now keyboard-only. It was drawn from `:focus-within`, which also matches a mouse click — open the popover with the mouse, dismiss it with the mouse, and the restored focus left a pointer user staring at a keyboard affordance. It now uses the shared `:has(:focus-visible)` ring, which also brings the outline to the documented 3px offset. (#4935)@cixzhangdiff --git a/.changeset/date-week-start.md b/.changeset/date-week-start.mdindex ef3fa0e3ca..b2e302e47f 100644--- a/.changeset/date-week-start.md+++ b/.changeset/date-week-start.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[feat] DateInput, DateRangeInput, and DateTimeInput now accept a `weekStartsOn` prop that sets the first day of the week in the calendar popover (0 = Sunday … 6 = Saturday, or a three-letter day name like `"mon"`). It forwards to the underlying Calendar, whose default stays Sunday, so existing usage is unchanged.+[feat] DateInput, DateRangeInput, and DateTimeInput now accept a `weekStartsOn` prop that sets the first day of the week in the calendar popover (0 = Sunday … 6 = Saturday, or a three-letter day name like `"mon"`). It forwards to the underlying Calendar, whose default stays Sunday, so existing usage is unchanged. (#4745)@freddymetadiff --git a/.changeset/datetime-focus-steal.md b/.changeset/datetime-focus-steal.mdindex 19204c3128..38d084b576 100644--- a/.changeset/datetime-focus-steal.md+++ b/.changeset/datetime-focus-steal.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] DateInput and DateTimeInput no longer steal focus when the open calendar is dismissed by clicking another control. Clicking the field to open the calendar, then clicking the time input (DateTimeInput) or any other element, kept yanking focus back to the date input because the popover's close handler always refocused it. It now restores focus only when the dismiss left focus detached (Escape, or a click on empty space), so a click that lands focus elsewhere is respected.+[fix] DateInput and DateTimeInput no longer steal focus when the open calendar is dismissed by clicking another control. Clicking the field to open the calendar, then clicking the time input (DateTimeInput) or any other element, kept yanking focus back to the date input because the popover's close handler always refocused it. It now restores focus only when the dismiss left focus detached (Escape, or a click on empty space), so a click that lands focus elsewhere is respected. (#4974)@freddymetadiff --git a/.changeset/disabled-inputs-form-data.md b/.changeset/disabled-inputs-form-data.mdindex 781bddb53a..4f46292263 100644--- a/.changeset/disabled-inputs-form-data.md+++ b/.changeset/disabled-inputs-form-data.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] TextInput, TextArea, NumberInput: a disabled field is no longer submitted with the form when `disabledMessage` is set. Showing the reason tooltip requires swapping the native `disabled` attribute for `aria-disabled` + `readOnly`, so the message stays discoverable by pointer and keyboard — but read-only fields still serialize into `FormData`, and these three kept their `name`, so a locked field posted its value. They now withhold the `name` while disabled, matching CheckboxInput and Switch (which forward the name only when enabled) and the hidden-input carriers in Selector, MultiSelector, Slider, and Tokenizer (which mirror `disabled`). Adds form-participation coverage to all three so the guarantee is pinned.+[fix] TextInput, TextArea, NumberInput: a disabled field is no longer submitted with the form when `disabledMessage` is set. Showing the reason tooltip requires swapping the native `disabled` attribute for `aria-disabled` + `readOnly`, so the message stays discoverable by pointer and keyboard — but read-only fields still serialize into `FormData`, and these three kept their `name`, so a locked field posted its value. They now withhold the `name` while disabled, matching CheckboxInput and Switch (which forward the name only when enabled) and the hidden-input carriers in Selector, MultiSelector, Slider, and Tokenizer (which mirror `disabled`). Adds form-participation coverage to all three so the guarantee is pinned. (#4811)@josephfarinadiff --git a/.changeset/empty-state-contract-role.md b/.changeset/empty-state-contract-role.mdnew file mode 100644index 0000000000..2a73a6078e--- /dev/null+++ b/.changeset/empty-state-contract-role.md@@ -0,0 +1,7 @@+---+'@astryxdesign/core': patch+---++[fix] EmptyState: the rest spread sits before the contract `role`, so a consumer can no longer clobber the landmark role the component guarantees (#4826).++@cixzhangdiff --git a/.changeset/empty-state-targets-selector-typeahead.md b/.changeset/empty-state-targets-selector-typeahead.mdnew file mode 100644index 0000000000..4bcff9b24e--- /dev/null+++ b/.changeset/empty-state-targets-selector-typeahead.md@@ -0,0 +1,7 @@+---+'@astryxdesign/core': patch+---++[feat] Selector, MultiSelector and Typeahead expose their empty ("No results found") state as a themeable target (#4756, #4862) — `astryx-selector-empty-state`, `astryx-multi-selector-empty-state` and `astryx-typeahead-empty-state`. Themes can restyle the empty state without the fragile structural selectors consumers previously had to reach for. (The Selector search field is a TextInput, so its placeholder is reachable today via `.astryx-text-input::placeholder`; a Selector-scoped placeholder seam would require a TextInput change and is left as a possible follow-up.)++@freddymetadiff --git a/.changeset/empty-state-title-description-targets.md b/.changeset/empty-state-title-description-targets.mdindex e4c431da8c..c409806fe6 100644--- a/.changeset/empty-state-title-description-targets.md+++ b/.changeset/empty-state-title-description-targets.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] EmptyState: add `empty-state-title` and `empty-state-description` theme targets on the title heading and the description. A theme can now restyle the title and description directly (e.g. font size, color, per `variant`) instead of reaching them through structural `> div:has(> :is(h1..h6))` selectors that reverse-engineer which element is which.+[feat] EmptyState: add `empty-state-title` and `empty-state-description` theme targets on the title heading and the description. A theme can now restyle the title and description directly (e.g. font size, color, per `variant`) instead of reaching them through structural `> div:has(> :is(h1..h6))` selectors that reverse-engineer which element is which. (#4942)@freddymetadiff --git a/.changeset/fix-indicator-falsy-children.md b/.changeset/fix-indicator-falsy-children.mdindex 06762727ce..229489ac5d 100644--- a/.changeset/fix-indicator-falsy-children.md+++ b/.changeset/fix-indicator-falsy-children.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] Indicator: a falsy `children` no longer deletes the state mark. The busy idiom a host actually writes — `children={isBusy && <Spinner/>}` — passes `false` when it is not busy, and `false` is neither `null` nor caught by `??`, so all three indicators took the children path, rendered nothing in it, and dropped the checkmark, the checkbox tick and the radio dot on every selected row. They now use `isRenderable`, so only children that actually render replace the mark. `0` still counts as content, since it renders the character "0".+[fix] Indicator: a falsy `children` no longer deletes the state mark. The busy idiom a host actually writes — `children={isBusy && <Spinner/>}` — passes `false` when it is not busy, and `false` is neither `null` nor caught by `??`, so all three indicators took the children path, rendered nothing in it, and dropped the checkmark, the checkbox tick and the radio dot on every selected row. They now use `isRenderable`, so only children that actually render replace the mark. `0` still counts as content, since it renders the character "0". (#4913)CheckIndicator's children slot also reserves the glyph's box and carries its color, so swapping a Spinner in no longer shifts the row or loses the disabled shade.diff --git a/.changeset/focus-outline-consistency.md b/.changeset/focus-outline-consistency.mdindex 0286a5342c..cd2ef1a18a 100644--- a/.changeset/focus-outline-consistency.md+++ b/.changeset/focus-outline-consistency.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] Consolidate general interactive focus outlines onto one definition — 2px `--color-accent` at 3px offset, matching Design Conventions.+[fix] Consolidate general interactive focus outlines onto one definition — 2px `--color-accent` at 3px offset, matching Design Conventions. (#4654)Most general controls had drifted to a 2px offset; Button, Calendar, Dialog and Pagination were the ones still on spec. Their value wins, so a focus ring on the drifted components (Link, TabList, Token, TreeList, SegmentedControl, TopNav items) now sits 1px further from its control.diff --git a/.changeset/heading-display-type-theme-scale.md b/.changeset/heading-display-type-theme-scale.mdindex 562a485fda..3d8a53fbbf 100644--- a/.changeset/heading-display-type-theme-scale.md+++ b/.changeset/heading-display-type-theme-scale.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `<Heading type="display-N">` now sizes correctly under every theme, matching `Text`'s behavior. `generateTypeScaleComponents()` only emitted `level:N`-keyed CSS rules for `heading`, with no `type:display-N` counterpart — so as soon as a theme supplied `typography.scale`, the generated theme-layer CSS's `level:N` rule was the only one present and silently won regardless of `type`, discarding the prop. A theme with no typography config was unaffected, which made the bug look intermittent.+[fix] `<Heading type="display-N">` now sizes correctly under every theme, matching `Text`'s behavior. `generateTypeScaleComponents()` only emitted `level:N`-keyed CSS rules for `heading`, with no `type:display-N` counterpart — so as soon as a theme supplied `typography.scale`, the generated theme-layer CSS's `level:N` rule was the only one present and silently won regardless of `type`, discarding the prop. A theme with no typography config was unaffected, which made the bug look intermittent. (#4859)@HelloOjasMutrejadiff --git a/.changeset/high-contrast-borders.md b/.changeset/high-contrast-borders.mdindex eb90a3b085..e57ca3f3bb 100644--- a/.changeset/high-contrast-borders.md+++ b/.changeset/high-contrast-borders.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] theme: `color.contrast: 'high'` now strengthens border tokens too — the emphasized border tone is pulled toward mid-scale (stronger against both light and dark surfaces) and the subtle hairline's alpha is doubled, so structural boundaries stay perceivable in high-contrast themes instead of only text/icons changing.+[fix] theme: `color.contrast: 'high'` now strengthens border tokens too — the emphasized border tone is pulled toward mid-scale (stronger against both light and dark surfaces) and the subtle hairline's alpha is doubled, so structural boundaries stay perceivable in high-contrast themes instead of only text/icons changing. (#4529)@ernesttdiff --git a/.changeset/icon-rotation-theme-targets.md b/.changeset/icon-rotation-theme-targets.mddeleted file mode 100644index 203c78cac7..0000000000--- a/.changeset/icon-rotation-theme-targets.md+++ /dev/null@@ -1,13 +0,0 @@-----'@astryxdesign/core': patch------[fix] Remove styling-only wrappers around rotating icons, and put each rotation on the icon element that already carries the component's theme target — so a theme reaches the glyph and its open/closed transform through one selector.--No new theme targets: Selector, MultiSelector and ComplexSelector consolidate onto their existing `*-indicator-icon` targets, and the Table plugins and TreeList simply shed redundant wrapper elements.--Where an RTL mirror sat on a separate parent element, it is folded into each state's transform (`scaleX(-1) rotate(...)`) so one element carries both. In the Table plugins that mirror was inert — `transform` does not apply to a non-replaced inline box — so RTL disclosure chevrons now mirror correctly where they silently did not before.--Also adds the `@astryx/no-wrapper-transform` lint rule (warn) for `<div>`/`<span>` wrappers that exist to transform the icon inside them.--@cixzhangdiff --git a/.changeset/icon-theme-target-consolidation.md b/.changeset/icon-theme-target-consolidation.mdnew file mode 100644index 0000000000..13209cf0cc--- /dev/null+++ b/.changeset/icon-theme-target-consolidation.md@@ -0,0 +1,15 @@+---+'@astryxdesign/core': patch+---++[fix] Icons render through `<Icon>` and carry their component's theme target (#4838).++Styling-only wrappers around rotating icons are gone, and each rotation now sits on the icon element that already carries the component's theme target — so a theme reaches the glyph and its open/closed transform through one selector. No new theme targets: Selector, MultiSelector and ComplexSelector consolidate onto their existing `*-indicator-icon` targets, and the Table plugins and TreeList simply shed redundant wrapper elements.++Where an RTL mirror sat on a separate parent element, it is folded into each state's transform (`scaleX(-1) rotate(...)`) so one element carries both. In the Table plugins that mirror was inert — `transform` does not apply to a non-replaced inline box — so RTL disclosure chevrons now mirror correctly where they silently did not before.++Registry glyphs in SideNav, TopNav, Collapsible, TreeList and Breadcrumbs now render through `<Icon>` instead of `useIcon()` inside a hand-written `<span>`. Those spans were a weaker reimplementation of `<Icon>`, which already resolves the same glyph and renders a span carrying merged `className`/`style`/`xstyle` plus the `astryx-icon` theme target. The converted sites gain that target, and the node count is unchanged. `useIcon()` keeps its place for the cases that resolve a glyph _without_ rendering it: MoreMenu and ChatSendButton pass the node as a default for a consumer-overridable prop, which `<Icon>` cannot express.++Also adds the `@astryx/no-wrapper-transform` lint rule (warn) for `<div>`/`<span>` wrappers that exist to transform the icon inside them.++@cixzhangdiff --git a/.changeset/indicator-decorative-contract.md b/.changeset/indicator-decorative-contract.mdindex 35f6b1c0b4..b136a1393e 100644--- a/.changeset/indicator-decorative-contract.md+++ b/.changeset/indicator-decorative-contract.md@@ -2,9 +2,13 @@'@astryxdesign/core': patch----[fix] Indicator: a caller can no longer un-hide a decorative indicator. `IndicatorProps` now omits `aria-hidden`, `role`, `aria-label` and `aria-labelledby` — passing `role` is a compile error — and each indicator emits its own `aria-hidden` after `{...rest}`, so a forwarded one cannot win. Un-hiding an indicator had it announced next to the control that owns the accessible name, saying the same thing twice.+[fix] Indicator: a caller can no longer un-hide or focus a decorative indicator (#4921, #4947).-Nothing is stripped: every other prop, including a forwarded `aria-label`, still reaches the DOM, where it is inert inside an `aria-hidden` subtree. Note that TypeScript exempts hyphenated JSX attributes from excess-property checking, so the type alone cannot reject `aria-*`; the attribute order is what enforces it.+`IndicatorProps` now omits `aria-hidden`, `role`, `aria-label`, `aria-labelledby` and `tabIndex` — passing `role` or `tabIndex` is a compile error — and each indicator emits its own `aria-hidden` after `{...rest}`, so a forwarded one cannot win. Un-hiding an indicator had it announced next to the control that owns the accessible name, saying the same thing twice; a tab stop on one is a focusable node inside a hidden subtree, an axe `aria-hidden-focus` violation.++Nothing is stripped: every other prop, including a forwarded `aria-label`, still reaches the DOM, where it is inert inside an `aria-hidden` subtree. Note that TypeScript exempts hyphenated JSX attributes from excess-property checking, so the type alone cannot reject `aria-*`; the attribute order is what enforces it. `tabIndex` is a plain identifier, so its omission stands on its own.++Also corrects two doc claims: a replacement must render `children` when they will actually draw something (`isRenderable`, not `children ?? mark`), and "passing `role` is a compile error" holds for a literal attribute — a spread bypasses excess-property checking.Fixes #4918.diff --git a/.changeset/indicator-tabindex.md b/.changeset/indicator-tabindex.mddeleted file mode 100644index bbdc0be120..0000000000--- a/.changeset/indicator-tabindex.md+++ /dev/null@@ -1,9 +0,0 @@-----'@astryxdesign/core': patch------[fix] Indicator: `IndicatorProps` also omits `tabIndex`. An indicator is unconditionally `aria-hidden`, so a tab stop on one is a focusable node inside a hidden subtree — an axe `aria-hidden-focus` violation. `tabIndex` is a plain identifier, so the omission makes it a compile error on its own, the same way `role` already is.--Also corrects two doc claims: a replacement must render `children` when they will actually draw something (`isRenderable`, not `children ?? mark`), and "passing `role` is a compile error" holds for a literal attribute — a spread bypasses excess-property checking.--@cixzhangdiff --git a/.changeset/input-clear-icon-theme-targets.md b/.changeset/input-clear-icon-theme-targets.mdindex cad7c246d6..0b636e4f7b 100644--- a/.changeset/input-clear-icon-theme-targets.md+++ b/.changeset/input-clear-icon-theme-targets.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] Every clearable input now renders its clear (✕) affordance through the shared `InputClearButton`, so the glyph is themeable in one place via the `astryx-input-clear-icon` target instead of a per-component target or a fragile descendant selector. The component-specific `astryx-{date-input,date-range-input,selector,multi-selector}-clear-icon` targets still render for a deprecation window — migrate to `input-clear-icon`. The clear glyph is now a consistent secondary-color icon with a ghost-button hover affordance across the whole family.+[feat] Every clearable input now renders its clear (✕) affordance through the shared `InputClearButton`, so the glyph is themeable in one place via the `astryx-input-clear-icon` target instead of a per-component target or a fragile descendant selector. The component-specific `astryx-{date-input,date-range-input,selector,multi-selector}-clear-icon` targets still render for a deprecation window — migrate to `input-clear-icon`. The clear glyph is now a consistent secondary-color icon with a ghost-button hover affordance across the whole family. (#4876)@freddymetadiff --git a/.changeset/input-disabled-theme-state.md b/.changeset/input-disabled-theme-state.mdindex e660cf7d02..49aba85a59 100644--- a/.changeset/input-disabled-theme-state.md+++ b/.changeset/input-disabled-theme-state.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] The input family (TextInput, NumberInput, DateInput, DateRangeInput, DateTimeInput, TimeInput, TextArea, Tokenizer) now reflects its disabled state on the root theming target as `data-disabled="disabled"` plus a `.disabled` variant (only when disabled), so a theme can gate its own hover/border treatment on the disabled state — mirroring the existing `status`/`size` reflection — instead of relying on structural `:has(input:disabled)` CSS. This closes a documented theming gap for downstream consumers.+[feat] The input family (TextInput, NumberInput, DateInput, DateRangeInput, DateTimeInput, TimeInput, TextArea, Tokenizer) now reflects its disabled state on the root theming target as `data-disabled="disabled"` plus a `.disabled` variant (only when disabled), so a theme can gate its own hover/border treatment on the disabled state — mirroring the existing `status`/`size` reflection — instead of relying on structural `:has(input:disabled)` CSS. This closes a documented theming gap for downstream consumers. (#4794)@freddymetadiff --git a/.changeset/menu-item-activation-fixes.md b/.changeset/menu-item-activation-fixes.mdindex 361a27ccaa..4756325b77 100644--- a/.changeset/menu-item-activation-fixes.md+++ b/.changeset/menu-item-activation-fixes.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] A DropdownMenu item closes the menu on activation even when it carries no `onClick`, and a data-mode row that changes its own label keeps its identity instead of remounting and dropping focus+[fix] A DropdownMenu item closes the menu on activation even when it carries no `onClick`, and a data-mode row that changes its own label keeps its identity instead of remounting and dropping focus (#4953)@cixzhangdiff --git a/.changeset/menu-item-close-on-select.md b/.changeset/menu-item-close-on-select.mddeleted file mode 100644index 952522aaac..0000000000--- a/.changeset/menu-item-close-on-select.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[feat] DropdownMenuItem takes `hasCloseOnSelect`, so a plain action can report its result on the item instead of closing the menu-@cixzhangdiff --git a/.changeset/menu-item-data-additions.md b/.changeset/menu-item-data-additions.mdnew file mode 100644index 0000000000..62de281c80--- /dev/null+++ b/.changeset/menu-item-data-additions.md@@ -0,0 +1,7 @@+---+'@astryxdesign/core': patch+---++[feat] DropdownMenu rows take two new options (#4953). `DropdownMenuItem` takes `hasCloseOnSelect`, so a plain action can report its result on the item instead of closing the menu. `DropdownMenuItemData` and `DropdownMenuSection` take an optional `id`, the row's stable React key for a menu whose items reorder or filter (also reaching MoreMenu, ContextMenu and Breadcrumbs, which share the type).++@cixzhangdiff --git a/.changeset/menu-item-data-from-item-props.md b/.changeset/menu-item-data-from-item-props.mdindex 606c788a70..0774ae7e29 100644--- a/.changeset/menu-item-data-from-item-props.md+++ b/.changeset/menu-item-data-from-item-props.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[chore] `DropdownMenuItemData` — the shape of one entry in a `DropdownMenu` / `ContextMenu` / `MoreMenu` `items` array — is now sourced from `DropdownMenuItemProps` (`Pick`) instead of restating `icon`, `onClick`, `isDisabled`, and `variant` by hand, and `renderDropdownItems` forwards the whole item to `DropdownMenuItem` rather than copying it field by field. The data and compound APIs describe the same item, so they can no longer drift — exposing another item prop to the data API is now one key in the `Pick`. The type is structurally identical to before (`label` is still narrowed to `string`, since the renderer keys rows by it) and rendering is unchanged.+[chore] `DropdownMenuItemData` — the shape of one entry in a `DropdownMenu` / `ContextMenu` / `MoreMenu` `items` array — is now sourced from `DropdownMenuItemProps` (`Pick`) instead of restating `icon`, `onClick`, `isDisabled`, and `variant` by hand, and `renderDropdownItems` forwards the whole item to `DropdownMenuItem` rather than copying it field by field. The data and compound APIs describe the same item, so they can no longer drift — exposing another item prop to the data API is now one key in the `Pick`. The type is structurally identical to before (`label` is still narrowed to `string`, since the renderer keys rows by it) and rendering is unchanged. (#4809)@cixzhangdiff --git a/.changeset/menu-item-destructive-variant.md b/.changeset/menu-item-destructive-variant.mdindex b120d0f54d..8d116b5e35 100644--- a/.changeset/menu-item-destructive-variant.md+++ b/.changeset/menu-item-destructive-variant.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[feat] DropdownMenuItem now accepts a `variant` prop (`'default' | 'destructive'`); `'destructive'` renders the label, description, and icon in the error color for dangerous actions like Delete. The data-driven `items` API accepts the same `variant` field, and because ContextMenu shares the menu-item data shape, context-menu items get it too. Defaults to `'default'`, so existing menus are unchanged.+[feat] DropdownMenuItem now accepts a `variant` prop (`'default' | 'destructive'`); `'destructive'` renders the label, description, and icon in the error color for dangerous actions like Delete. The data-driven `items` API accepts the same `variant` field, and because ContextMenu shares the menu-item data shape, context-menu items get it too. Defaults to `'default'`, so existing menus are unchanged. (#4753)@freddymetadiff --git a/.changeset/menu-item-id.md b/.changeset/menu-item-id.mddeleted file mode 100644index 015b4ab0e0..0000000000--- a/.changeset/menu-item-id.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[feat] `DropdownMenuItemData` and `DropdownMenuSection` take an optional `id`, the row's stable React key for a menu whose items reorder or filter (also reaching MoreMenu, ContextMenu and Breadcrumbs, which share the type)-@cixzhangdiff --git a/.changeset/migrate-style-only-wrappers.md b/.changeset/migrate-style-only-wrappers.mdindex da3771c825..ae72bb9efe 100644--- a/.changeset/migrate-style-only-wrappers.md+++ b/.changeset/migrate-style-only-wrappers.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[chore] Remove 15 `<div>`/`<span>` wrappers that existed only to style the single Astryx component inside them (Carousel, Lightbox, MobileNav, Pagination, Switch, TopNav, TopNavMegaMenu, Table row-expansion menu icon); the styles now sit on that component's own root via `xstyle` — or, for Pagination's page-size Selector, its documented `width` prop. No API change, but the rendered DOM has one fewer node at each site, so anything selecting on that structure is affected: `patch`, not `[breaking]`, because the removed nodes were internal implementation with no documented contract, no theme target, and no stable class. Two rendering defects the wrappers were causing are fixed as a side effect: the Lightbox prev/next chevrons and the Pagination first/last chevrons were 2.5-3px off their button's vertical centre.+[chore] Remove 15 `<div>`/`<span>` wrappers that existed only to style the single Astryx component inside them (Carousel, Lightbox, MobileNav, Pagination, Switch, TopNav, TopNavMegaMenu, Table row-expansion menu icon); the styles now sit on that component's own root via `xstyle` — or, for Pagination's page-size Selector, its documented `width` prop. No API change, but the rendered DOM has one fewer node at each site, so anything selecting on that structure is affected: `patch`, not `[breaking]`, because the removed nodes were internal implementation with no documented contract, no theme target, and no stable class. Two rendering defects the wrappers were causing are fixed as a side effect: the Lightbox prev/next chevrons and the Pagination first/last chevrons were 2.5-3px off their button's vertical centre. (#4775)@cixzhangdiff --git a/.changeset/more-menu-placement-alignment.md b/.changeset/more-menu-placement-alignment.mdindex 30fca2bda4..4ceafdb1db 100644--- a/.changeset/more-menu-placement-alignment.md+++ b/.changeset/more-menu-placement-alignment.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] MoreMenu forwards `placement` and `alignment` to its DropdownMenu. Both were part of the underlying menu's API but were dropped on the floor by the wrapper, so an overflow menu — the one component whose job is a trailing-edge affordance — could not ask to be end-aligned; it only looked right when the layer happened to collision-flip. Defaults are unchanged: MoreMenu passes the props straight through, so DropdownMenu's `'below'` / `'start'` still apply.+[fix] MoreMenu forwards `placement` and `alignment` to its DropdownMenu. Both were part of the underlying menu's API but were dropped on the floor by the wrapper, so an overflow menu — the one component whose job is a trailing-edge affordance — could not ask to be end-aligned; it only looked right when the layer happened to collision-flip. Defaults are unchanged: MoreMenu passes the props straight through, so DropdownMenu's `'below'` / `'start'` still apply. (#4952)@cixzhangdiff --git a/.changeset/multiselector-row-slots.md b/.changeset/multiselector-row-slots.mdindex 3d1d39be8a..55f7a00af6 100644--- a/.changeset/multiselector-row-slots.md+++ b/.changeset/multiselector-row-slots.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[feat] MultiSelector: dropdown option rows are themeable through a single+[feat] MultiSelector: dropdown option rows are themeable through a single (#4628)`multi-selector-option` target, carrying the row's `size` and its `select-all`,`selected` and `disabled` states — so a theme can express "selected option atlarge" or restyle just the Select All row. Row typography moved from the labeldiff --git a/.changeset/pagination-caret-icon-centering.md b/.changeset/pagination-caret-icon-centering.mdindex d9f96f96cf..7645e50ddf 100644--- a/.changeset/pagination-caret-icon-centering.md+++ b/.changeset/pagination-caret-icon-centering.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] Pagination: vertically center the prev/next caret icons. The RTL mirror wrapped each chevron in a `display: contents` span, which dropped the icon out of the button's flex-centering context so the glyph sat a few pixels high. The mirror transform now rides on the `Icon` directly via `xstyle`, so the icon stays a centered flex child and still flips under RTL — no wrapper element.+[fix] Pagination: vertically center the prev/next caret icons. The RTL mirror wrapped each chevron in a `display: contents` span, which dropped the icon out of the button's flex-centering context so the glyph sat a few pixels high. The mirror transform now rides on the `Icon` directly via `xstyle`, so the icon stays a centered flex child and still flips under RTL — no wrapper element. (#4723)@freddymetadiff --git a/.changeset/popup-theme-targets.md b/.changeset/popup-theme-targets.mdindex b801ec0e18..df142c6e4e 100644--- a/.changeset/popup-theme-targets.md+++ b/.changeset/popup-theme-targets.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] ComplexSelector and MultiSelector: add `astryx-complex-selector-popup` and `astryx-multi-selector-popup` theme targets on the popup surface, so a theme can style the popup — background, border, radius, elevation, padding — through `defineTheme` instead of a structural selector or a fork. Both components already targeted their trigger but nothing in the popup, which is the part that has to match the rest of an app's menus. The target sits on the popup's content box rather than the layer element: `useLayer` zeroes the layer's borders, padding and background, so the content box is the surface that actually paints. Purely additive — default rendering is unchanged.+[feat] ComplexSelector and MultiSelector: add `astryx-complex-selector-popup` and `astryx-multi-selector-popup` theme targets on the popup surface, so a theme can style the popup — background, border, radius, elevation, padding — through `defineTheme` instead of a structural selector or a fork. Both components already targeted their trigger but nothing in the popup, which is the part that has to match the rest of an app's menus. The target sits on the popup's content box rather than the layer element: `useLayer` zeroes the layer's borders, padding and background, so the content box is the surface that actually paints. Purely additive — default rendering is unchanged. (#4991)@cixzhangdiff --git a/.changeset/progressbar-mark-size-derived-vars.md b/.changeset/progressbar-mark-size-derived-vars.mdindex 8e64d05719..e2398cc356 100644--- a/.changeset/progressbar-mark-size-derived-vars.md+++ b/.changeset/progressbar-mark-size-derived-vars.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] ProgressBar: a theme can size the target mark again without `!important`. The mark's `width`/`height` were plain StyleX declarations, so a `progressbar-mark` override only landed where `@layer astryx-theme` outranks the component atomics — in a source-build app that compiles StyleX without `useCSSLayers` the atomics are unlayered and beat every theme rule, leaving no way to resize the tick but an unlayered `!important` rule. The dimensions now travel as derived vars with no competing declaration, so the same `defineTheme` entry lands in either build. Theme authoring is unchanged; a mark's color is still a plain declaration and still depends on the layer order.+[fix] ProgressBar: a theme can size the target mark again without `!important`. The mark's `width`/`height` were plain StyleX declarations, so a `progressbar-mark` override only landed where `@layer astryx-theme` outranks the component atomics — in a source-build app that compiles StyleX without `useCSSLayers` the atomics are unlayered and beat every theme rule, leaving no way to resize the tick but an unlayered `!important` rule. The dimensions now travel as derived vars with no competing declaration, so the same `defineTheme` entry lands in either build. Theme authoring is unchanged; a mark's color is still a plain declaration and still depends on the layer order. (#4970)@cixzhangdiff --git a/.changeset/prop-forwarding-precedence.md b/.changeset/prop-forwarding-precedence.mdnew file mode 100644index 0000000000..e01666c9ab--- /dev/null+++ b/.changeset/prop-forwarding-precedence.md@@ -0,0 +1,7 @@+---+'@astryxdesign/core': patch+---++[fix] CommandPalette, ComplexSelector and ContextMenu: a consumer's `onClick`/`onMouseEnter` is composed with the component's own handler instead of being overwritten by it, and `{...props}` no longer lands after the props the component must control (#4725).++@cixzhangdiff --git a/.changeset/readonly-text-inputs.md b/.changeset/readonly-text-inputs.mdindex 5a8e7bbfd6..479e53efee 100644--- a/.changeset/readonly-text-inputs.md+++ b/.changeset/readonly-text-inputs.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[feat] TextInput, TextArea, NumberInput: add `isReadOnly`. The value is shown at full opacity and still submits with the form, but cannot be edited — the "visible, locked, still sent" case that `isDisabled` deliberately does not cover, since disabled controls are excluded from submission. Read-only fields are not dimmed and stay in the tab order, matching the native `readonly` semantics they compile to; `isDisabled` takes precedence when both are set, and the clear button is hidden while read-only. The state is reflected on the root theming target as `data-readonly="readonly"`, alongside the existing `data-disabled`, so a theme can paint it without structural `:has(input:read-only)` CSS. `isReadOnly` already existed on CheckboxInput, CheckboxList, and PowerSearch; the remaining text-ish inputs (DateInput, DateRangeInput, DateTimeInput, TimeInput, Tokenizer) do not have it yet.+[feat] TextInput, TextArea, NumberInput: add `isReadOnly`. The value is shown at full opacity and still submits with the form, but cannot be edited — the "visible, locked, still sent" case that `isDisabled` deliberately does not cover, since disabled controls are excluded from submission. Read-only fields are not dimmed and stay in the tab order, matching the native `readonly` semantics they compile to; `isDisabled` takes precedence when both are set, and the clear button is hidden while read-only. The state is reflected on the root theming target as `data-readonly="readonly"`, alongside the existing `data-disabled`, so a theme can paint it without structural `:has(input:read-only)` CSS. `isReadOnly` already existed on CheckboxInput, CheckboxList, and PowerSearch; the remaining text-ish inputs (DateInput, DateRangeInput, DateTimeInput, TimeInput, Tokenizer) do not have it yet. (#4816)@josephfarinadiff --git a/.changeset/remove-dropdown-menu-radio-dot-target.md b/.changeset/remove-dropdown-menu-radio-dot-target.mdindex bb389fa9d4..72c202ca16 100644--- a/.changeset/remove-dropdown-menu-radio-dot-target.md+++ b/.changeset/remove-dropdown-menu-radio-dot-target.md@@ -2,7 +2,7 @@'@astryxdesign/core': minor----[breaking] Remove the `dropdown-menu-radio-dot` theme target. Menu radio rows draw the shared radio indicator now, so the dot is the indicator's dot: target `radio-indicator-dot` (the legacy `radio-dot` name still matches it too). The row's circle keeps its `dropdown-menu-radio` target, so only the dot moved.+[breaking] Remove the `dropdown-menu-radio-dot` theme target. Menu radio rows draw the shared radio indicator now, so the dot is the indicator's dot: target `radio-indicator-dot` (the legacy `radio-dot` name still matches it too). The row's circle keeps its `dropdown-menu-radio` target, so only the dot moved. (#4890)Runtime themes are not validated — a theme keyed on the removed target keeps compiling and silently stops matching — so `astryx upgrade` now carries `rename-dropdown-menu-radio-dot-target`, which rewrites the key and the `astryx-dropdown-menu-radio-dot` class. The new target is app-wide rather than menu-only (there is no menu-only dot element left to address), so the codemod leaves a TODO at each site it rewrites.diff --git a/.changeset/required-disabled-blocks-submit.md b/.changeset/required-disabled-blocks-submit.mdindex afadb06691..4e6b36ef36 100644--- a/.changeset/required-disabled-blocks-submit.md+++ b/.changeset/required-disabled-blocks-submit.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] CheckboxInput, Switch: a `required` control that is disabled with a `disabledMessage` no longer blocks the whole form from submitting. Showing the reason tooltip swaps the native `disabled` attribute for `aria-disabled`, which leaves the control subject to constraint validation — so an unchecked required checkbox (or an off required switch) the user has been told they cannot touch made the form permanently unsubmittable, with the browser reporting a validation error against a control they had no way to satisfy. Both now detach from the form via `form=""` while focusable-disabled, matching a natively disabled control and the treatment RadioListItem already applied. Enabled controls are unaffected — a required, unchecked checkbox still blocks submission as it should.+[fix] CheckboxInput, Switch: a `required` control that is disabled with a `disabledMessage` no longer blocks the whole form from submitting. Showing the reason tooltip swaps the native `disabled` attribute for `aria-disabled`, which leaves the control subject to constraint validation — so an unchecked required checkbox (or an off required switch) the user has been told they cannot touch made the form permanently unsubmittable, with the browser reporting a validation error against a control they had no way to satisfy. Both now detach from the form via `form=""` while focusable-disabled, matching a natively disabled control and the treatment RadioListItem already applied. Enabled controls are unaffected — a required, unchecked checkbox still blocks submission as it should. (#4815)@josephfarinadiff --git a/.changeset/row-expansion-detail-panel.md b/.changeset/row-expansion-detail-panel.mdindex 953367fd31..6042a52fd5 100644--- a/.changeset/row-expansion-detail-panel.md+++ b/.changeset/row-expansion-detail-panel.md@@ -2,6 +2,8 @@'@astryxdesign/core': minor----[breaking] useTableRowExpansion is now a detail-panel plugin: it expands a full-width panel below a row via renderExpanded(item), and useTableRowExpansionState is removed. For hierarchical/tree tables (child rows that reuse the parent columns), migrate to useTableTreeData + useTableTreeState. See the migration example on the useTableRowExpansion docs.+[breaking] useTableRowExpansion is now a detail-panel plugin: it expands a full-width panel below a row via renderExpanded(item), and useTableRowExpansionState is removed. For hierarchical/tree tables (child rows that reuse the parent columns), migrate to useTableTreeData + useTableTreeState. See the migration example on the useTableRowExpansion docs. (#4609)++**Codemod:** `npx astryx upgrade --apply` runs `migrate-table-rowexpansion-to-tree`, which rewrites tree-mode `useTableRowExpansion` call sites onto `useTableTreeData` + `useTableTreeState`.@humbertovirtudesdiff --git a/.changeset/scroll-lock-out-of-order-cleanup.md b/.changeset/scroll-lock-out-of-order-cleanup.mdindex 46c1bef329..91cebc8554 100644--- a/.changeset/scroll-lock-out-of-order-cleanup.md+++ b/.changeset/scroll-lock-out-of-order-cleanup.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `useScrollLock`: coordinate concurrent locks with a shared counter, so overlays closing out of order no longer unlock the body early or leave it stuck locked.+[fix] `useScrollLock`: coordinate concurrent locks with a shared counter, so overlays closing out of order no longer unlock the body early or leave it stuck locked. (#4788)@alex-js-ltddiff --git a/.changeset/selector-check-and-disabled-targets.md b/.changeset/selector-check-and-disabled-targets.mdnew file mode 100644index 0000000000..2f3c88e184--- /dev/null+++ b/.changeset/selector-check-and-disabled-targets.md@@ -0,0 +1,7 @@+---+'@astryxdesign/core': patch+---++[feat] Selector/MultiSelector: two additive theming seams (#4626, #4627). A `selector-check` theme target on the selected-row checkmark lets themes restyle or hide it (e.g. to compose their own selected indicator via `renderOption`) instead of relying on a structural sibling selector, and `data-disabled` now reflects on the trigger for theme-driven disabled styling. Rotation styles remain on the indicator-icon target. Default appearance is unchanged.++@athzdiff --git a/.changeset/selector-check-target.md b/.changeset/selector-check-target.mddeleted file mode 100644index b7643ce03f..0000000000--- a/.changeset/selector-check-target.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[feat] Selector: expose a `selector-check` theme target on the selected-row checkmark so themes can restyle or hide it (e.g. to compose their own selected indicator via `renderOption`) instead of relying on a structural sibling selector. Purely additive — default appearance is unchanged.-@athzdiff --git a/.changeset/selector-disabled-state-target.md b/.changeset/selector-disabled-state-target.mddeleted file mode 100644index b46f2e3b14..0000000000--- a/.changeset/selector-disabled-state-target.md+++ /dev/null@@ -1,6 +0,0 @@-----'@astryxdesign/core': patch------[feat] Selector/MultiSelector: add `data-disabled` reflection on the trigger for theme-driven disabled styling. Rotation styles remain on the indicator-icon target (no separate wrapper target needed).-@athzdiff --git a/.changeset/selector-empty-state-target.md b/.changeset/selector-empty-state-target.mddeleted file mode 100644index 93cc5687be..0000000000--- a/.changeset/selector-empty-state-target.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] Selector and MultiSelector: expose the empty ("No results found") state as a themeable target (`astryx-selector-empty-state` / `astryx-multi-selector-empty-state`). Lets themes restyle the empty state without structural CSS selectors — consumers previously had to reach it via fragile structural selectors because no stable target existed. (The search field is a TextInput, so its placeholder is reachable today via `.astryx-text-input::placeholder`; a Selector-scoped placeholder seam would require a TextInput change and is left as a possible follow-up.)--@freddymetadiff --git a/.changeset/selector-popover-alignment.md b/.changeset/selector-popover-alignment.mdindex d6d57568a6..2743ac37c5 100644--- a/.changeset/selector-popover-alignment.md+++ b/.changeset/selector-popover-alignment.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] Selector: keep the selected option text aligned with the closed trigger across every menu position by measuring untransformed layout geometry during the popover entry animation.+[fix] Selector: keep the selected option text aligned with the closed trigger across every menu position by measuring untransformed layout geometry during the popover entry animation. (#4802)@ernesttdiff --git a/.changeset/selector-trigger-icon-consolidation.md b/.changeset/selector-trigger-icon-consolidation.mdindex 427030d704..565cffad16 100644--- a/.changeset/selector-trigger-icon-consolidation.md+++ b/.changeset/selector-trigger-icon-consolidation.md@@ -2,7 +2,7 @@'@astryxdesign/core': patch----[fix] Drop the shared trigger-icon wrapper in Selector, MultiSelector and ComplexSelector — each trigger icon is now the element that carries its own box, colour and theme target.+[fix] Drop the shared trigger-icon wrapper in Selector, MultiSelector and ComplexSelector — each trigger icon is now the element that carries its own box, colour and theme target. (#4846)The wrapper set a 16px box and `--color-icon-secondary` on a span with no theme target of its own, shared by two different affordances: the status glyph and the disclosure chevron. `<Icon>` already provides both (`size="sm"` is the same 16px box, `color="secondary"` the same token), so the wrapper only stood between a theme and the icons — and made the two affordances share a node they never should have shared.diff --git a/.changeset/self-host-lookaside-images.md b/.changeset/self-host-lookaside-images.mdindex b6f085b65c..9d78dc8aaf 100644--- a/.changeset/self-host-lookaside-images.md+++ b/.changeset/self-host-lookaside-images.md@@ -2,7 +2,7 @@'@astryxdesign/cli': patch----[chore] Self-host template demo imagery in the repo instead of streaming it+[chore] Self-host template demo imagery in the repo instead of streaming it (#3973)from the internal `lookaside.facebook.com` CDN.- Template demo images are now committed underdiff --git a/.changeset/sidenav-footer-collapsed-centering.md b/.changeset/sidenav-footer-collapsed-centering.mdindex fab93a8f5a..d7c964688c 100644--- a/.changeset/sidenav-footer-collapsed-centering.md+++ b/.changeset/sidenav-footer-collapsed-centering.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] SideNav: `footer` content now centers when the nav is collapsed, matching how `children` already centers. `stickyBottomCollapsed` (the collapsed-rail wrapper for `footer`) was missing `alignItems: 'center'`, which its sibling `scrollableCollapsed` (the collapsed-rail wrapper for `children`) already had — so full-width footer content (e.g. an icon-only button) stretched to the collapsed rail's width instead of centering.+[fix] SideNav: `footer` content now centers when the nav is collapsed, matching how `children` already centers. `stickyBottomCollapsed` (the collapsed-rail wrapper for `footer`) was missing `alignItems: 'center'`, which its sibling `scrollableCollapsed` (the collapsed-rail wrapper for `children`) already had — so full-width footer content (e.g. an icon-only button) stretched to the collapsed rail's width instead of centering. (#4852)@HelloOjasMutrejadiff --git a/.changeset/sidenav-heading-collapsed-popover-anchor.md b/.changeset/sidenav-heading-collapsed-popover-anchor.mdindex cf41ed478b..d344a1e9e9 100644--- a/.changeset/sidenav-heading-collapsed-popover-anchor.md+++ b/.changeset/sidenav-heading-collapsed-popover-anchor.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] SideNav: the collapsed icon-only `SideNavHeading` trigger with a `menu` no longer omits its popover's anchor. The trigger's ref callback wasn't forwarding to `usePopover`'s `triggerRef`, so the menu popover had no CSS anchor to position against and fell back to the viewport corner instead of opening next to the trigger.+[fix] SideNav: the collapsed icon-only `SideNavHeading` trigger with a `menu` no longer omits its popover's anchor. The trigger's ref callback wasn't forwarding to `usePopover`'s `triggerRef`, so the menu popover had no CSS anchor to position against and fell back to the viewport corner instead of opening next to the trigger. (#4850)@HelloOjasMutrejadiff --git a/.changeset/statusdot-a11y-guidance.md b/.changeset/statusdot-a11y-guidance.mdindex c6bc9544c8..32569f5d54 100644--- a/.changeset/statusdot-a11y-guidance.md+++ b/.changeset/statusdot-a11y-guidance.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[docs] StatusDot: document the builder's accessibility responsibilities in the usage dos and don'ts. A color-only dot is not fully accessible in isolation, so the guidance now says to use it as a binary present/absent signal, pair it with a label, carry the status as a shape via an icon, and — if neither fits — convey the status through an accessible alternative.+[docs] StatusDot: document the builder's accessibility responsibilities in the usage dos and don'ts. A color-only dot is not fully accessible in isolation, so the guidance now says to use it as a binary present/absent signal, pair it with a label, carry the status as a shape via an icon, and — if neither fits — convey the status through an accessible alternative. (#4737)@ernesttdiff --git a/.changeset/stepper-nonvisual-hygiene.md b/.changeset/stepper-nonvisual-hygiene.mdindex 3afe79d61e..546ff86d4f 100644--- a/.changeset/stepper-nonvisual-hygiene.md+++ b/.changeset/stepper-nonvisual-hygiene.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] Stepper: localize the "Optional" step affordance via the new `@astryx.step.optional` message key so it translates like the rest of the component. No visual change in English.+[fix] Stepper: localize the "Optional" step affordance via the new `@astryx.step.optional` message key so it translates like the rest of the component. No visual change in English. (#4872)@ernesttdiff --git a/.changeset/stepper-template-hardening.md b/.changeset/stepper-template-hardening.mdnew file mode 100644index 0000000000..2104c42220--- /dev/null+++ b/.changeset/stepper-template-hardening.md@@ -0,0 +1,7 @@+---+'@astryxdesign/cli': patch+---++[fix] Stepper templates: the scaffolded Stepper blocks gain the a11y, theming and responsive-label hardening from the component audit, and their doc blocks match what they render (#4917).++@ernesttdiff --git a/.changeset/streaming-text-grapheme-boundary.md b/.changeset/streaming-text-grapheme-boundary.mdindex 9a254d9936..9aa2c9355b 100644--- a/.changeset/streaming-text-grapheme-boundary.md+++ b/.changeset/streaming-text-grapheme-boundary.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `useStreamingText` no longer renders a broken glyph (a lone surrogate, or a partial ZWJ emoji sequence) for one frame when its fixed-code-unit reveal cadence happens to land inside a surrogate pair or multi-codepoint emoji. The rendered slice now snaps back to the nearest grapheme cluster boundary via `Intl.Segmenter` (with a surrogate-pair-safe fallback where it's unavailable); the reveal cadence itself is unchanged. Also corrected the hook's doc comment, which inaccurately described the cadence as advancing on word/syntax boundaries — it always advanced by fixed code units.+[fix] `useStreamingText` no longer renders a broken glyph (a lone surrogate, or a partial ZWJ emoji sequence) for one frame when its fixed-code-unit reveal cadence happens to land inside a surrogate pair or multi-codepoint emoji. The rendered slice now snaps back to the nearest grapheme cluster boundary via `Intl.Segmenter` (with a surrogate-pair-safe fallback where it's unavailable); the reveal cadence itself is unchanged. Also corrected the hook's doc comment, which inaccurately described the cadence as advancing on word/syntax boundaries — it always advanced by fixed code units. (#4866)@HelloOjasMutrejadiff --git a/.changeset/table-context-action-destructive.md b/.changeset/table-context-action-destructive.mdindex 64cb0217af..790abf978f 100644--- a/.changeset/table-context-action-destructive.md+++ b/.changeset/table-context-action-destructive.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] Table: `contextMenuActions` now accept a `variant: 'destructive'` for dangerous row/column actions (e.g. Delete), rendered in the error color to match ContextMenu.+[feat] Table: `contextMenuActions` now accept a `variant: 'destructive'` for dangerous row/column actions (e.g. Delete), rendered in the error color to match ContextMenu. (#4864)@freddymetadiff --git a/.changeset/textarea-detached-no-icon-reserve.md b/.changeset/textarea-detached-no-icon-reserve.mdindex 5bc275da1e..96e50dd228 100644--- a/.changeset/textarea-detached-no-icon-reserve.md+++ b/.changeset/textarea-detached-no-icon-reserve.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] TextArea: no longer reserves trailing space for the on-field status icon when `statusVariant="detached"`. The detached variant surfaces its status glyph in the message box below the field and renders no on-field icon, so the reserved inset pushed the text in for an icon that never appeared. Trailing space is now reserved only when the spinner or on-field status icon actually renders.+[fix] TextArea: no longer reserves trailing space for the on-field status icon when `statusVariant="detached"`. The detached variant surfaces its status glyph in the message box below the field and renders no on-field icon, so the reserved inset pushed the text in for an icon that never appeared. Trailing space is now reserved only when the spinner or on-field status icon actually renders. (#4940)@freddymetadiff --git a/.changeset/textarea-flush-wrapper-padding.md b/.changeset/textarea-flush-wrapper-padding.mdindex 6564228284..1044dc0011 100644--- a/.changeset/textarea-flush-wrapper-padding.md+++ b/.changeset/textarea-flush-wrapper-padding.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] TextArea: remove the duplicate wrapper padding so the text and native resize grip sit flush to the edge. The wrapper's `padding: 0` shorthand was being overridden by the shared input-wrapper longhands, leaving the inset applied twice; it now zeroes with matching longhands.+[fix] TextArea: remove the duplicate wrapper padding so the text and native resize grip sit flush to the edge. The wrapper's `padding: 0` shorthand was being overridden by the shared input-wrapper longhands, leaving the inset applied twice; it now zeroes with matching longhands. (#4813)@ernesttdiff --git a/.changeset/textarea-padding-inline-theme.md b/.changeset/textarea-padding-inline-theme.mdindex 4712cd9f24..d65742c0b3 100644--- a/.changeset/textarea-padding-inline-theme.md+++ b/.changeset/textarea-padding-inline-theme.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[feat] TextArea: theme the text inset by writing `paddingInline` on the `textarea` component key — it now drives the internal `--_textarea-inline-padding` var instead of landing on the wrapper. The wrapper stays flush (`padding: 0`), so the native resize grip keeps its true-corner position and the start icon, status, and character counter stay aligned to the text. Adds a `replaces` option to derived var entries for the general "map a property onto a var without emitting it on the class element" case.+[feat] TextArea: theme the text inset by writing `paddingInline` on the `textarea` component key — it now drives the internal `--_textarea-inline-padding` var instead of landing on the wrapper. The wrapper stays flush (`padding: 0`), so the native resize grip keeps its true-corner position and the start icon, status, and character counter stay aligned to the text. Adds a `replaces` option to derived var entries for the general "map a property onto a var without emitting it on the class element" case. (#4793)@freddymetadiff --git a/.changeset/theme-neutral-radius-none-fix.md b/.changeset/theme-neutral-radius-none-fix.mdindex 30353c8ec1..d356ccf37f 100644--- a/.changeset/theme-neutral-radius-none-fix.md+++ b/.changeset/theme-neutral-radius-none-fix.md@@ -2,6 +2,6 @@'@astryxdesign/theme-neutral': patch----[fix] `--radius-none` no longer overrides to `0.25rem`. `--radius-none` and `--radius-full` are documented as always fixed (never scaled by a theme), matching `@astryxdesign/core`'s own defaults — this theme's radius group bump swept `--radius-none` along with it by mistake. Anything opting out of rounding via `--radius-none` under this theme now renders with a true `0px` radius again, instead of a silent 4px.+[fix] `--radius-none` no longer overrides to `0.25rem`. `--radius-none` and `--radius-full` are documented as always fixed (never scaled by a theme), matching `@astryxdesign/core`'s own defaults — this theme's radius group bump swept `--radius-none` along with it by mistake. Anything opting out of rounding via `--radius-none` under this theme now renders with a true `0px` radius again, instead of a silent 4px. (#4856)@HelloOjasMutrejadiff --git a/.changeset/themeable-indicators.md b/.changeset/themeable-indicators.mdindex 2a8ac40323..0e71eb1fff 100644--- a/.changeset/themeable-indicators.md+++ b/.changeset/themeable-indicators.md@@ -3,7 +3,7 @@'@astryxdesign/cli': patch----[feature] Add themeable indicators — the componentized check, checkbox, and radio visuals. `defineTheme({indicators: {check: RadioIndicator}})` replaces one by name, and every component drawing it follows.+[feature] Add themeable indicators — the componentized check, checkbox, and radio visuals. `defineTheme({indicators: {check: RadioIndicator}})` replaces one by name, and every component drawing it follows. (#4712)Theme targets now follow the component-name convention: `checkbox-indicator`, `radio-indicator`, `radio-indicator-dot`. The old names (`checkbox`, `radio`, `radio-dot`) are still emitted on the same element, so existing themes keep working — migrate at your convenience; they go away in the next major.diff --git a/.changeset/tree-typeahead-cycling.md b/.changeset/tree-typeahead-cycling.mdindex 63a254c3d0..dd348a85f6 100644--- a/.changeset/tree-typeahead-cycling.md+++ b/.changeset/tree-typeahead-cycling.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] TreeList typeahead now cycles through same-letter matches instead of stalling, and searches from the top when no treeitem is focused.+[fix] TreeList typeahead now cycles through same-letter matches instead of stalling, and searches from the top when no treeitem is focused. (#4844)@alex-js-ltddiff --git a/.changeset/typeahead-empty-state-target.md b/.changeset/typeahead-empty-state-target.mddeleted file mode 100644index 197ef02e3a..0000000000--- a/.changeset/typeahead-empty-state-target.md+++ /dev/null@@ -1,7 +0,0 @@-----'@astryxdesign/core': patch------[feat] Typeahead: expose the empty ("No results found") state as a themeable target (`astryx-typeahead-empty-state`), so themes can restyle it without relying on structural CSS selectors.--@freddymetadiff --git a/.changeset/typeahead-ime-composition-enter.md b/.changeset/typeahead-ime-composition-enter.mdindex 25ff83f2be..c34e34561d 100644--- a/.changeset/typeahead-ime-composition-enter.md+++ b/.changeset/typeahead-ime-composition-enter.md@@ -2,6 +2,6 @@'@astryxdesign/core': patch----[fix] `BaseTypeahead` (and everything built on it — `Typeahead`, `Tokenizer`, `PowerSearch`'s content-search field) no longer misinterprets the Enter keydown that commits an IME composition (Korean/Japanese/Chinese input) as "accept the highlighted suggestion". Previously that keydown both selected the highlighted result and cleared the input, so the still-composing syllable landed in the freshly-cleared field and became its own spurious second selection on the next Enter. Also guarded the Enter-to-save handler in `PowerSearchEditPopover`, which had the same gap when typing a CJK filter value.+[fix] `BaseTypeahead` (and everything built on it — `Typeahead`, `Tokenizer`, `PowerSearch`'s content-search field) no longer misinterprets the Enter keydown that commits an IME composition (Korean/Japanese/Chinese input) as "accept the highlighted suggestion". Previously that keydown both selected the highlighted result and cleared the input, so the still-composing syllable landed in the freshly-cleared field and became its own spurious second selection on the next Enter. Also guarded the Enter-to-save handler in `PowerSearchEditPopover`, which had the same gap when typing a CJK filter value. (#4860)@HelloOjasMutrejadiff --git a/.changeset/use-icon-to-icon.md b/.changeset/use-icon-to-icon.mddeleted file mode 100644index ebf3586400..0000000000--- a/.changeset/use-icon-to-icon.md+++ /dev/null@@ -1,11 +0,0 @@-----'@astryxdesign/core': patch------[fix] Render registry glyphs through `<Icon>` instead of `useIcon()` inside a hand-written `<span>`, in SideNav, TopNav, Collapsible, TreeList and Breadcrumbs.--Those spans were a weaker reimplementation of `<Icon>`, which already resolves the same glyph and renders a span carrying merged `className`/`style`/`xstyle` plus the `astryx-icon` theme target. The converted sites gain that target — no new targets are introduced — and the node count is unchanged.--`useIcon()` keeps its place for the cases that resolve a glyph *without* rendering it: MoreMenu and ChatSendButton pass the node as a default for a consumer-overridable prop, which `<Icon>` cannot express.--@cixzhangdiff --git a/.changeset/use-long-press-multitouch-cancel.md b/.changeset/use-long-press-multitouch-cancel.mdindex 114b2f2ebe..81e8b62d7a 100644--- a/.changeset/use-long-press-multitouch-cancel.md+++ b/.changeset/use-long-press-multitouch-cancel.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] useLongPress: cancel the pending long-press when a second finger joins mid-press. Previously `onTouchStart` and `onTouchMove` only checked `touches.length` on their own event, so a second finger arriving after a single-finger press had already started the timer (e.g. a pinch-to-zoom gesture) fell through the `touches.length !== 1` guard without ever clearing it — `onLongPress` could still fire with the stale first-finger point mid-gesture. No API change.+[fix] useLongPress: cancel the pending long-press when a second finger joins mid-press. Previously `onTouchStart` and `onTouchMove` only checked `touches.length` on their own event, so a second finger arriving after a single-finger press had already started the timer (e.g. a pinch-to-zoom gesture) fell through the `touches.length !== 1` guard without ever clearing it — `onLongPress` could still fire with the stale first-finger point mid-gesture. No API change. (#4735)@alex-js-ltddiff --git a/.changeset/usecontainerreveal-scopes-the-reveal-by-inherita-guca.md b/.changeset/usecontainerreveal-scopes-the-reveal-by-inherita-guca.mdindex 26c9b2d68b..446a69addb 100644--- a/.changeset/usecontainerreveal-scopes-the-reveal-by-inherita-guca.md+++ b/.changeset/usecontainerreveal-scopes-the-reveal-by-inherita-guca.md@@ -2,5 +2,5 @@'@astryxdesign/core': patch----[fix] useContainerReveal scopes the reveal by inheritance instead of a marker pool: no dev warnings on lists longer than six rows, and isEnabled now takes effect after mount+[fix] useContainerReveal scopes the reveal by inheritance instead of a marker pool: no dev warnings on lists longer than six rows, and isEnabled now takes effect after mount (#4955)@cixzhang