What's New

Release notes and changelog for all packages.

0.7.2

New Components
  • Promote Drawer and DrawerHeader from the canary-only Lab package to Core, imported from @astryxdesign/core/Drawer or the package root. The stable package now ships the full-height side panel with modal and non-modal presentation, the shared dismissal stack, Dialog's purpose dismissal policy, a DrawerHeader whose close button appears when given onOpenChange, and Dialog-style container padding (--spacing-4 by default, padding prop, or a theme's drawer padding), plus Core documentation and runnable examples. Canary users importing from @astryxdesign/lab switch to @astryxdesign/core/Drawer.
New Features
  • An integration component doc can name a differently named export of the file beside it: when Slides.tsx exports AcmeCarousel and nothing named Slides, Slides.doc.mjs can set name: 'AcmeCarousel', and a kebab-case acme-widget.doc.mjs can name AcmeWidget. component --list, component <Name>, search, swizzle, the doctor integration checks and integration verify know the component by that name, and its file name still opens it. A name that Core or another doc's file already has stays theirs on every surface unless --package names the integration. Docs and sources are read without running them; a doc named after its file, or beside a file that exports its own name, reads exactly as before.
  • Each full entry an integration's family doc lists in components, such as AcmeSlide in an AcmeCarousel doc, is a component under its own name when the module the doc's import names exports it. Its source is the .tsx file in the family's folder that declares it; a member that only built output or a file outside that folder declares has no source to show or copy. component --list, component <Name>, search, swizzle, the doctor integration checks, integration verify and integration add know these members. A member's detail is scoped to its own entry, as a Core sub-component's is, and it never carries the family's replaces. A member named like a Core component or another doc's file opens with --package.
  • The CLI installed for the computer keeps one short Astryx skill for every agent on the computer: ~/.agents/skills/astryx/SKILL.md, which most coding agents read, linked into the skill folder of each agent that reads only its own (~/.claude/skills always; Kiro, Windsurf, Letta, Xcode's coding assistant, and ~/.config/agents/skills when that folder exists) with a folder link and a relative target, a junction on Windows, or a copy where no link can be made. Continue, whose scanner skips links, gets a managed copy. The text tells agents that Astryx is on the computer, when it is relevant (building or changing UI), to start with astryx search, and to read docs with astryx docs; it names no version and only commands every release keeps. It is written on the global copy's first run and after each upgrade, in the background; package install scripts never write it. astryx init --user writes it now, in any folder, and astryx init --user --remove-agents removes the file, every link Astryx made, and the copy, and turns it off. The setting and the links Astryx made are kept in astryx/settings.json in the per-user configuration folder. The file records a hash of its text, so a file a person edited is never overwritten or removed, and nothing Astryx did not create at a link folder is replaced. init --user warns, while still writing, when no astryx command on the computer runs the Astryx CLI, and its init.user receipt lists each path and what happened to it. Outside a project, astryx doctor adds a computer-agent-text check (info only) that says whether the text is present, current, edited, or turned off, where it is linked, and any link folder it skipped or whose skill folder is missing. A cache or configuration folder set through XDG_CACHE_HOME, XDG_CONFIG_HOME, LOCALAPPDATA, or APPDATA is used only when it is an absolute path.
  • Integrations installed for the computer. An integration package installed in the same place as the CLI installed for the computer (npm i -g, pnpm add -g, yarn global add, or bun add -g beside @astryxdesign/cli), or installed with the CLI in one package set by a tool that runs it, is a computer-level integration. Outside a project, it loads the way a project's integrations do: its components, templates, docs, themes, discover source, and cliCommand apply, with the same validation, and one whose @astryxdesign/core or @astryxdesign/cli peer range excludes the CLI's release is skipped. pnpm 11 and later, which give each global package a folder of its own, count every one of those folders. Inside a project, only the project's own integrations load: a computer-level one adds nothing there, and astryx discover lists it under meta.available with source installed for this computer and the project's install command in install, when its peer range admits the project's release and it loads. A project that installs the same integration uses only its own copy. astryx doctor adds a computer-integrations check: outside a project, each one it uses, each the folder replaces with its own copy, and a warning for each it skips or cannot load; inside one, the ones the project could add.
  • astryx gap-report --to <package> sends a report to the issues URL of the loaded integration the person chose, under the same --confirm-public rule, instead of the default handlers. When loaded integrations name their own issues URLs, --list-categories and the receipt list every destination and tell the agent to ask the person where to file. The default route is unchanged.
  • Install the CLI once for your computer (npm i -g @astryxdesign/cli) and run astryx in any folder. In a project, the project's own CLI answers, whatever its version, as before: a copy started anywhere else (the global install, npx, a typed version) hands the run to it. A project with no CLI of its own (only @astryxdesign/core, or a fresh clone) is answered by the copy you started, as before; when that copy is not the Core's release, one hint after the command, at most once a day per project, names the command that adds the CLI at Core's version, and JSON reports meta.answeredBy.copy: "starting". Only a project whose own CLI cannot start is answered by the CLI release equal to its Core, installed once into a per-user cache (from the installed Core, else the lockfile, else the declared range). astryx doctor warns when a project's CLI and Core are different releases, or when a project has no CLI and the copy that answered differs from its Core, and prints the command that aligns them. astryx --help and the manifest's new globalMode field point to astryx docs global. The hand-off keeps the arguments, folder, standard streams, and exit status. Outside a project, the copy installed for your computer answers with its own release; commands that read Core use the Core of that release there: the global copy downloads it into the cache in a background step it starts as a run ends (never in CI, and not on Windows, where a background process would hold the caller's pipes and the first component command downloads it instead), so component reads work offline after one online run. Nothing that worked before breaks: when that release cannot be obtained (offline, a registry without it, an unwritable cache), the copy you started answers, as before global mode, with one warning line on standard error (astryx: could not get Astryx <version> to match this project's Core (<reason>); answering with CLI <version> instead) and meta.answeredBy.copy: "fallback" in JSON. A copy counts as installed for the computer only in npm's global folder or in a global folder a package manager's own settings name (Bun's BUN_INSTALL or globalDir, Yarn's global-folder, pnpm's PNPM_HOME or global-dir, or their defaults), never by a folder's layout alone, so an app made with yarn add is never mistaken for one; a moved Bun or Yarn global folder counts, and its notice reinstalls there. A failed install is remembered in the cache, so offline runs do not start npm again each time: it is retried after 2 minutes, then after 10 once it fails again, and a success forgets it. A stale install lock ends the process it records only when that process is exactly this CLI's install of that release (npm, or node running npm-cli.js, installing @astryxdesign/cli@<version>, started after the lock); otherwise the lock is simply taken over. The new ERR_VERSIONS_UNAVAILABLE is kept for runs nothing can answer, such as a command that needs Core outside a project that cannot install it. The CLI starts npm from npm's own entry file with the running Node, never through a shell, and reads a project's declared Core range only when it is a plain version range. Every successful --json result now carries meta.answeredBy (cli, core, copy: project, starting, matched, carried, or fallback), typed in CLIResponse and described in the output envelope docs. In text mode, a run answered by anything other than the project's own CLI prints one astryx: answered by … line on standard error. Printed commands start with a name that reaches the same release: the project's runner when its own CLI answers, astryx outside a project for the copy installed for the computer, and otherwise the CLI package pinned to the answering version (npx @astryxdesign/cli@0.7.2). The new ERR_PROJECT_REQUIRED code names a command that needs a project. See astryx docs global/install-once.
  • astryx doctor integration and astryx integration check catch more doc mistakes, and stop flagging one pattern Core itself uses.
  • An integration can set the command its users run the CLI with: a new cliCommand field in astryx.integration.*, such as cliCommand: 'acme astryx'. In a project that loads that integration, every command the CLI prints starts with it instead of the package-manager prefix (npx astryx, pnpm exec astryx): next-step hints, errors, suggestions, Doctor fixes, --help, the setup reminder, the agent-docs block, and doc text. If two loaded integrations set different commands, neither is used, and the new cli-command check in astryx doctor warns. An invalid cliCommand is ignored with an invalid_cli_command warning; the rest of the manifest still loads. Docs, including an integration's, are now written with bare astryx ... commands, and astryx docs prefixes them for the project when it prints them. JSON output keeps every command bare, as before. The install-time setup reminder from @astryxdesign/core and @astryxdesign/cli names the command the project's package manager runs, instead of always npx @astryxdesign/cli.
  • The integration manifest accepts an optional docsiteUrl, a link to the integration's docs site, as a known field, so setting it no longer raises an unknown-key warning.
  • Update notices, the way gh and the Vercel CLI do them. Once a day, never in the first day after its first run, the CLI installed for the computer checks the registry's latest release in the background without delaying the command; it never installs a release by itself. When a newer release exists, a command that finishes successfully prints two lines on standard error, at most once a day: A new release of Astryx is available: <current> → <newest> and To upgrade, run: <command>, with the command of the package manager that installed the CLI (npm i -g, pnpm add -g, yarn global add, bun add -g, or volta install), after the Node the release needs when the computer runs an older one. Inside a project the notice names the project's install and upgrade commands instead, and an astryx first on the search path from before the hand-off gets a notice naming its upgrade. No notice prints with --json, after a failed command, or when CI or NO_UPDATE_NOTIFIER is set, and neither variable lets the check run; unlike gh, a notice prints when standard error is not a terminal, because agents run the CLI without one. What the check found lives in astryx/state.json in the per-user configuration folder. astryx doctor reports the same: the newest-release check names the upgrade commands, and a new cli-on-path check lists every astryx command on the search path.
  • A {@link <target>} in a component doc's text now reads as the command that opens its doc, in astryx component <Name>, its --props view, and component lists, in text and JSON: the description, usage, best practices, anatomy and accessibility notes, and each prop's and example's description. A topic's description reads the same way in astryx docs, its list, and the docs tree. Code fields and code ticks show the link as written. A Core component's links resolve against the CLI's docs; an integration's against its own. astryx doctor integration components warns on a link in an integration's component docs that names no doc, and doctor integration docs does the same for a topic's description. The written-pointer warning also reads component docs and topic descriptions, and each finding now names its kind and field.
  • Component prop docs accept stability: 'experimental', the machine-readable marker for a prop outside the stable compatibility promise, such as a component's experimental prop object.
  • doctor integration docs (and so integration check) lists each pair of topics that repeat 10 or more words of prose word for word: two of the package's own topics, or one of them and a Core topic other than the one it replaces. Each entry names the topic that keeps the text (a Core topic, or of two package topics the one the passage fits), the line to change in the other, and the exact link to put there, and is in the new copiedPassages field. A run with fewer than 4 distinct content words (words other than function words such as "the", "in" or "it"), or one that three or more topics share, is not listed. Each pair is also a copied_passage warning, so integration check --strict (new in this release) fails until it is fixed; doctor integration docs still exits 0. The CLI's own guides no longer repeat 18 passages that another guide owns; each copy is now a link to the guide that owns the fact.
  • astryx discover lists the official Astryx packages, first, from a list each CLI release carries, so a project with no discover source sees the official themes, even offline. Each entry in meta.available carries the command that adds it (install), so a project that loads no integration and has no discover source of its own, where every query still answers with the list, can add a package straight from it. An official entry's latest is the newest release the CLI knows (its own version on a release CLI, or a newer Core release the project has), and its versions also list the project's Core version, so both can be looked up. Its add command pins the project's Core version (installed, or declared exactly), else the Core range the project declares (quoted), else the latest release; on a canary CLI with no Core it pins none for packages released with Core, and canary-only packages are listed only beside a canary Core or no Core. Official entries name Astryx as their source, and meta.sources reports the list last. A project's or an integration's source keeps its entry for an official package, and for any package of the same integration. A theme package that the project's own package.json declares as a dependency, under an npm alias too, shows as installed from any folder of the project, and a theme's add text ends with astryx theme add <slug>. A version or item that the official list does not show still answers ERR_UNKNOWN_PACKAGE, as before.
  • doctor integration docs (and so integration check) lists fluff in a package's prose, in the new fluff field: each padding phrase such as "in order to", "note that", or "it is worth noting", with its file line and what to write instead, and each topic of 80 or more prose words in which fewer than half the words carry content. Each is also a doc_fluff warning, so integration check --strict (new in this release) fails until it is cut; doctor integration docs still exits 0. The phrase list and the floor are in the check-your-docs guide (astryx docs cli/integrations/building-blocks/docs/check-your-docs). Core's browser-support guide loses its one padding phrase, and three of Core's guides (debug-and-gap-reports, sections-and-placement, publishing) are tightened to meet the density floor.
  • astryx doctor integration validate now checks every doc an integration ships under its roots (components, templates, docs topics, themes, and their translations, served or not) against the published authoring type for its kind, with the project's own TypeScript, the way tsc would. Each unknown field, missing required field, or value outside its field's type is a warning that names the doc, the line, the field, and a fix; the exit code is unchanged. A doc it cannot fully check, or a themes root that does not load, is listed with the reason; test fixtures under __tests__ in the components or docs root are counted, not checked. JSON adds data.docTypes. Without TypeScript the check prints one [skip] line instead of passing silently; with a TypeScript it cannot read types with (one with no JavaScript compiler API, such as TypeScript 7), that line names the installed version. With no doc files, it says there is nothing to check.
  • astryx doctor integration components compares each component doc's props with the component's TypeScript props, read with the project's own typescript. It warns about a documented prop the code does not have, a prop the package declares that the doc leaves out, and a wrong required. Without TypeScript it prints one line saying the comparison was skipped; with a TypeScript it cannot read types with (one with no JavaScript compiler API, such as TypeScript 7), that line names the installed version. The findings are warnings, so the exit code does not change; the JSON response gains data.propDrift, and nothing else in it changes.
  • astryx doctor integration components also judges each documented prop's type against the code, for props the package declares, a documented field such as status.type and a name the package's own index signature takes included, and warns when they differ (type_mismatch). A type is judged only where both sides read exactly, with the project's own typescript: the same text once whitespace, quotes and union order are set aside, or primitives, literals, arrays and unions of those, and names for them. Every other type (a callback, an object, a generic with arguments, an intersection, keyof, a type that does not resolve, a name two index signatures take) is listed as not compared, never reported. The comparison needs TypeScript 4.8 or later: with an older one, no type is judged and the text says so in one [skip] line. JSON adds typesCompared, typesNotCompared and, when the types were not judged, typesSkipped to propDrift. The findings are warnings, so the exit code does not change.
  • New astryx integration check, the CI check for an integration package's own build. It takes no package argument and checks the integration package in the current folder. It runs the four doctor integration checks (validate, components, templates, docs), prints each result, then a summary, and exits 1 when any of them would. --strict also exits 1 on any warning and on any check that did not run, such as a package with no astryx.integration.*: add "typecheck": "tsc --noEmit && astryx integration check --strict" to package.json so every build keeps the package's docs in sync. Its exit codes and JSON are a contract for the builds that run it: from this first release on, a new check, or a new failure code, joins only in a minor release named in the release notes. JSON: a new integration.check envelope carries each check's own envelope unchanged. Its docs say to run it in CI, so astryx search ci finds it. The doctor integration subcommands keep their exit codes; their JSON gains only additions.
  • Three new published types describe an integration package's templates: IntegrationPageTemplateDoc and IntegrationBlockTemplateDoc, each with every field of its TemplateDoc member but category as the package's own string instead of a TemplateCategory value, and their union, IntegrationTemplateDoc. @astryxdesign/cli/authoring exports IntegrationTemplateDoc; @astryxdesign/cli/doc and @astryxdesign/cli/template export all three. TemplateDoc is unchanged.
  • astryx upgrade renames a static edgeCompensation="inline" on List to edge="outset", and drops edgeCompensation beside an edge that is a fixed string. It keeps edgeCompensation with a TODO(astryx upgrade) comment where it can't prove the result: where edge is computed (it may be undefined, and then edgeCompensation still applies), on a dynamic edgeCompensation value, and where the List also spreads props, which may set edge. The deprecated prop keeps working there.
  • astryx doctor integration docs lists each code span in an integration's prose that is exactly astryx docs <name> for a doc that exists, and says which {@link} to write instead: {@link generic:<name>} for the package's own topic, {@link @astryxdesign/cli:generic:<name>} for Core's. The link prints the command that opens the doc, and doctor's link check fails it if the doc goes away. A command with more words, a route, or a code block is not listed. Each is a stray_doc_pointer warning, so astryx integration check --strict fails on it, and is in the new strayPointers field; doctor integration docs keeps exit 0. Core's own guides point with links, and a test keeps them that way.
  • astryx doctor integration validate and astryx integration check now warn source_without_template_doc when a .tsx directly in an integration's templates root has no same-stem template doc, so astryx template would never list it. The warning names the file and the doc to add. Files in subfolders, such as helpers a template imports, and test, spec or story files such as stray.test.tsx are not checked; a dotted template id such as landing.page.tsx is, and integration check --strict fails on the warning.
  • The doc-type and prop checks in integration check and doctor integration validate|components read types with @typescript/typescript6, the TypeScript 6 API package TypeScript publishes for tools, when the project installs it and its own typescript is missing or has no JavaScript compiler API, as TypeScript 7 does. When no usable TypeScript is found, the skip reason now ends with the remedy: add @typescript/typescript6 on TypeScript 7, or install TypeScript 5.0 through 6 (npm install -D typescript@6).
Fixes
  • extractComponents reported phantom components from locally-declared helper functions in template files — e.g. "Timeline", derived from a function TimelineSection() {...} helper declared directly in the detail-page template, which isn't a real component. It now excludes any name bound by a top-level function, class, const, let or var declaration in the same file (read from the parsed source, so comments, strings and type annotations don't count), before suffix-stripping runs, so a locally-declared helper is never mistaken for an imported component. A component whose whole name is a stripped suffix, such as a bare Section, now stays in the list instead of emptying out.
  • Global and project copies of the CLI meet more predictably. A repository that builds the CLI itself, with packages/cli beside packages/core, answers with that CLI instead of failing with ERR_VERSIONS_UNAVAILABLE. On a cache folder shared between computers, a release install renews its lock every 10 seconds, and a lock from another computer that goes a minute without renewal is taken over, instead of blocking runs for 20 minutes. Folder names are compared without letter case on macOS and Windows, a Yarn 1 global install on Windows is recognized as a global install, and the shims npm, pnpm (including pnpm 12's), and PowerShell write are read when doctor and the reminders look for the astryx commands on the search path.
  • The setup reminder, the swizzle StyleX note, and one doctor line say only what is true
  • A CLI installed with npm under a prefix of its own (npm i -g --prefix ~/.local, NPM_CONFIG_PREFIX, or prefix= in an .npmrc) is now upgraded into that same prefix: the update notice and astryx doctor print npm i -g --prefix <prefix> @astryxdesign/cli@latest, with ~ for the home folder. npm's default prefixes (Node's own, /usr/local, /usr, and %APPDATA%\npm on Windows) keep the plain command.
  • The CLI now uses postcss-selector-parser 7.1.6, which parses flat selectors in linear time and closes a CPU-exhaustion vulnerability (#6985).
  • integration verify reads a package's exports with the same reader discovery uses, so the two agree: a component re-exported through a folder's index file passes, and a type-only re-export no longer counts as the component.
  • astryx component --list and astryx search find VStack, HStack and Heading Each has its own import path, but its doc lives in its family's folder: Stack's doc documents HStack and VStack, and Heading's doc sits next to Text's. The list only counted a doc in the component's own folder, so the three were missing from the list and from search, and astryx component VStack found its doc only through fuzzy matching. A component whose doc is elsewhere is now listed and searchable with its own import path, and astryx component VStack opens its doc directly.
  • A doc link to a component, page, or block ({@link component:AcmeButton}, {@link @astryxdesign/core:component:Button}, {@link block:acme-card}) now resolves, and reads as the command that opens it: astryx component <Name> or astryx template <id> --type <page|block>, with --package for anything not from Core. Before, every such link printed as written, and astryx doctor and doctor integration docs warned that it named no doc, for Core's components as for a package's own. A link that names no component or template still warns, and its hint now searches components or templates instead of topics. A resolved link's route is null for these kinds, which no astryx docs route opens.
  • astryx doctor no longer fails "Theme owners and built imports", and astryx component no longer stops with "Could not load the recorded theme", when an added theme's built module imports a stylesheet, as in import './ocean.css'. Node cannot load a stylesheet, so the CLI checks that each imported .css file exists, then treats it as empty. It looks for each stylesheet from the theme module's folder, also when a module that the theme imports from another folder names it. Doctor still fails when an imported stylesheet is missing, and when the module has any other problem, such as a missing dependency, a syntax error, or an error thrown while it loads.
  • astryx search finds more of what a reader means when the words differ from the catalog's.
  • astryx search keeps a guide first when the query is a phrase of two or more words that the guide declares as a keyword. font size and font weight now open the font setup guide before the Text component, and dark mode opens the theme guides before the theme hooks. A component whose name is the whole query still comes first, one-word queries are unchanged, and the code terms and table cells in a reference doc don't count as its keywords.
  • astryx search ranks a match on more of your words above a shorter named entry.
  • astryx integration check --strict prints each finding once. The checks' own output shows its message and fix, and the closing "Failing under --strict" list names each failure by check, code and place only, so a long report is no longer doubled.
  • The table-filter page template's phone-width view-options panel is now labelled by its selected tab (aria-labelledby) instead of a fixed aria-label, so screen readers get the panel's name from the tab that controls it and the tab–panel relationship resolves in both directions.
  • astryx theme build --check and themeBuild({check: true}) keep comparing outputs outside the working directory, as the latest release does, rather than refusing them with ERR_PATH_TRAVERSAL the way a build does. Check mode writes nothing, so the write confinement of architecture:cli-surface/INV10 and INV10a does not apply to it: an absolute --out path outside the working directory, a theme file outside it whose outputs sit beside it, and --family with its root theme file outside it are each checked read-only. A relative --out path that escapes the working directory is still refused, as before. Builds keep refusing every one of these writes, so when such outputs are stale, the report no longer ends with a Rebuild with: command the build refuses. It names the nearest directory that contains the theme files and the outputs, and the build and check commands to run from there: each output's Source: header records the directory its build ran from, so the check passes only from that same directory. Stale outputs inside the working directory keep the Rebuild with: line.
  • astryx theme build and themeBuild() now write only inside the working directory (cwd for the API), as architecture:cli-surface/INV10 requires; under architecture:cli-surface/INV10a the refusal is a compatible fix. Each of these builds now fails with ERR_PATH_TRAVERSAL before anything is written: an absolute --out path outside the working directory, a theme file outside it whose outputs would go beside it, and --family with its root theme file outside it. Paths inside the working directory still build, including through a symlink. To migrate, run the build from a folder that holds the theme file and its outputs, or pass an --out path inside that folder; API callers pass a cwd that holds them.
  • astryx upgrade no longer reports your code as up to date when the CLI is older than the installed @astryxdesign/core. Core codemods ship inside the CLI, so an older CLI has none for the releases after its own version. It used to print "No changes needed" and "No codemods available for this version range" and exit 0 while the code still needed those releases' migrations. It now warns once that it cannot finish, prints the same upgrade pinned to the CLI release that matches your Core (such as cd <project> && npx @astryxdesign/cli@<core-version> upgrade --from <old-version> --path <source-dir> --apply), and ends with "Upgrade incomplete". That command changes to the folder the run used and names the directory it scanned as an absolute path, both with symbolic links resolved, so it upgrades the same code wherever you paste it. It is written for a POSIX shell, or for PowerShell on Windows. upgrade.status (no_codemods and config_fixable) and upgrade.run gain an optional cliBehindCore field with cliVersion and command, present only in that case. The codemods the CLI has still run, and the exit status and every existing field are unchanged.
  • astryx integration verify accepts a theme module that loads the theme's own styles. Such a module imports the theme's exported stylesheet and font stylesheet for their side effects, and re-exports from the module astryx theme build writes either everything or only its theme, under the theme's export name. Verify also finds that built module by the name theme build gives it, the theme's own name, so a theme whose name differs from its slug no longer fails to rebuild. Any other difference from the built module still fails with theme_module_stale, and for a module that re-exports the theme, the message now says what is wrong.
Performance
  • The CLI loads Core's runtime (@astryxdesign/core and @astryxdesign/core/theme) only when it builds or checks a theme (theme build, and the doctor and integration pack theme checks), not on every start. In a project with Core installed, every other command, and an import of @astryxdesign/cli/api, skips loading Core's components and React: astryx --version drops from about 1.3 s to 0.5 s. Output is unchanged.
Documentation
  • Docs and CLI examples import each Core export from the path astryx component <Name> prints.
  • Global mode docs: astryx docs global is a top-level docs section (and one docsite page, under Guide, which Getting Started introduces and links) explaining what global mode is, the one install command, what you get, and which version runs where. Its pages, each answering one question: project, global, or both (both is recommended; global/project-global-or-both), install (global/install-once, with what to do about EACCES), which version runs and why (global/who-answers), updates and notices (global/updates), the agent guide on your computer (global/computer-agent-guide), integrations installed globally (global/computer-integrations), monorepos and nested folders (global/monorepos), CI and containers (global/ci-and-containers), troubleshooting every line global mode prints (global/problems), uninstall and reset (global/uninstall), and a reference of paths, environment variables, JSON fields, and error codes (global/reference). astryx docs global and its pages are answered by the copy you start, even inside a project whose version predates them. Integration authors get a checklist with the commands to try a package globally (cli/integrations/global-integrations). Every command that does something else outside a project says exactly what in its "In global mode" note, checked against the command run in an empty folder, and every terminal line the global-mode pages show is checked against the CLI's own strings. A project's update notice now installs the CLI beside Core, so a project that installed only Core gets its own CLI too.
  • The integration guides make integration check --strict a required step in every integration's build: the quick start installs typescript@6 (the checks need its JavaScript compiler API, which TypeScript 7 does not ship) and adds "Check it in every build (required)", the Build an integration overview says so, and the checks guide's section reads "Run every check in every build (required)".
  • The astryx docs cli/integrations guides and astryx docs authoring now match the current CLI, and the guides point to the matching astryx docs authoring <section> for every field instead of repeating its tables.
  • Fix the MCP setup snippet in working-with-ai — "type": "url" is not a transport type, and Claude Desktop adds remote servers through Connectors
Other Changes
  • VStack and HStack come from @astryxdesign/core/VStack and @astryxdesign/core/HStack, Heading from @astryxdesign/core/Heading, Text from @astryxdesign/core/Text, and Theme and defineTheme from @astryxdesign/core/theme.
  • This covers the guides, the Card docs, the next steps astryx init prints, the install example astryx theme build prints, the wiring example theme add prints, the build rules, the theme-module fix astryx doctor prints, and the annotated theme template.
  • Every path was already exported. Nothing else changes.
  • A docsZh or docsDense overlay may set name and displayName, as Core's own docs do; both are ignored when the doc renders, so --strict no longer fails on them.
  • doctor integration components reports a documented default that differs from the literal default the component writes in its props destructuring (size = 'md') as default_mismatch. Quotes and spacing are ignored; where either side's default is not a literal, the prop is listed as not compared.
  • doctor integration validate warns, each with a fix, on a prop documented twice (duplicate_prop), a propDescriptions key that matches no prop entry's name as written (unknown_translated_prop), a section with no content (empty_section), two sections of one topic with the same key (duplicate_section_key, whose fix names the key the second one is already served at), and a .doc.zh.mjs or .doc.dense.mjs overlay beside no topic file (orphan_doc_overlay).
  • A topic that takes the route of one of Astryx's own docs is named by its topic name, not an internal id, with the rename to make. A link written as a bare name ({@link deploying}) gives the exact link to write, or says no topic has that name.
  • When a doc is missing several required fields, each finding's message names only its own field.
  • doctor integration validate prints each issue's fix and file in text output, as JSON already carries them.
  • The "run init to finish setup" reminder no longer prints where agents already have the Astryx prompt. In a git repository it looks for init's block in the agent docs from the project up to the repository root, because coding agents read every agent doc in between, so a package in a monorepo that ran init at its root stays quiet. This holds for every command and for the reminder printed when @astryxdesign/core or @astryxdesign/cli is installed. Running the CLI from its own source checkout, inside that checkout, prints no reminder. A project with no block in reach still gets it, and --json never prints it.
  • astryx swizzle no longer says StyleX components "render unstyled (no error)" without a StyleX compiler. Importing them throws StyleX's "Unexpected 'stylex.create' call at runtime" error and the page does not render, and the note now says so.
  • In an integration package, where the package's own manifest loads, astryx doctor's implicit-integrations line no longer says that "every loaded integration is named in astryx.config". It names the package's own manifest: as the only loaded integration, or beside the integrations astryx.config names.
    Classification: contract-restoring. Only message text changes: JSON keys, check ids, statuses, and exit codes are unchanged. The doctor line's new text also appears in its --json message.
  • Internal groundwork for astryx doctor integration components: a comparison of the props a component doc documents with the props its TypeScript source declares, read with the project's own typescript. Nothing reaches it yet, so the CLI's behavior and output do not change; the command starts running it in a later change, which describes what users see.
  • Internal groundwork for astryx doctor integration components: reading two written TypeScript types as one type when they differ only in how they are written (whitespace, comments, quotes, member order, Array<T> for T[], parameter names, React. qualifiers), and judging a documented prop type against the type the code declares where both read exactly. Nothing reaches either yet, so the CLI's behavior and output do not change.
  • Internal groundwork for astryx doctor integration components: finding the project's own typescript, and reading a package's TypeScript project the way tsc reads it (its own tsconfig.json or a monorepo root's, a solution-style config's references, and the declaration files the config includes), and finding the references in that project the compiler cannot resolve. Nothing reaches it yet, so the CLI's behavior and output do not change.
  • Old-CLI notes name the published releases that behave that way: template replaces, links, docs sections, section ids and typed theme descriptors work from 0.6.4, and template keywords from 0.6.6. integration verify still names the CLI range to declare.
  • The quick start makes the package an ES module, so a theme it builds can be imported.
  • Samples and output that had drifted are fixed, among them the subcomponent imports, a theme that extends another, and the upgrade output.
  • The Authoring Reference corrects how an invalid astryx.config is handled, the issuesUrl format, where codemod files go, and which fields nothing reads yet. Its examples use the export default {type: ...} form that integration add writes.
  • astryx docs cli/integrations links to the Authoring Reference, and the reference links back to the guides.
  • astryx docs styling-overview and tokens-and-setup give the real symptom of a missing StyleX compiler: importing a swizzled component throws an error that starts Unexpected 'stylex.create' call at runtime.
  • Adjacent query words that join into a component, hook, or template name, or into a one-word keyword, match it: table header cell with sort arrow finds TableHeaderCell, tree view folders the treeview keyword, and a hook answers to its words without use. Most of a name, a name's leading words, or a run of its words also count for components and hooks, a step below the full name.
  • A query that is one camelCase identifier and matches nothing as typed is read as the words it spells, so an unknown API name such as useTablePaginationState reaches useTablePagination. In a query of several words each identifier stays one term.
  • When the whole query is an entry's name, these readings add no near siblings beside it. A match on a joined keyword never ranks above an entry the query names, and a match on part of another name does only when it spans more query words than that entry's name.
  • A gerund matches its verb (spacing and space, dragging and drag), and a plural can start a longer word through its singular (tokens and Tokenizer).
  • Core component docs declare more keywords: other libraries' names (scrollarea, togglegroup, pageheader, splitpane, circularprogress, linearprogress, commandmenu, relativetime, sidesheet, descriptionlist, inlinecode) and common glyph names on Icon, since any icon library's glyph renders through it.
  • The JSON shape is unchanged.
  • A match on part of a longer name that reads more of the query than the entry the query names is no longer held below it: dropdown menu radio options leads with DropdownMenuRadioItem, not DropdownMenu.
  • useResizable drops the splitview keyword, which put it ahead of the side-panels guide.
Contributors
Thanks to everyone who contributed to this release:

0.7.1

Fixes
  • CommandPaletteInput now exposes the semantics and name that its visible state promises. (#7321)
    • A standalone field with no popup attributes was role="combobox" with aria-expanded="true" and aria-autocomplete="list"; it is now role="searchbox" with no popup state. Pass role="combobox", or your popup's own ARIA attributes, to keep the old semantics. A field that already passes popup attributes (aria-expanded, aria-controls, aria-owns, aria-haspopup, and the like) stays a combobox and keeps them, and a field inside CommandPalette is unchanged.
    • The field's default accessible name was its placeholder (Search…, or the caller's placeholder); it is now Search commands, translated. Pass label to keep a specific name, for example label="Search…" for the old default. A caller whose custom placeholder served as the name keeps working code and hears the generic name until it passes label.
    • The CLI's async-search CommandPalette block names its field Search files.
    • endContent={true} no longer renders an empty trailing slot, and endContent={0} renders inside the trailing slot instead of after it.
  • Stone, Y2K, and Gothic set CodeBlock's diff row slots in their own syntax palettes, so a reader of a diff on those themes gets added and removed rows whose code, line numbers, and +/- glyphs stay readable: every syntax token keeps at least 4.5:1 on the tinted rows in Stone (light and dark) and Y2K (light and dark), and in Gothic the rows take a deep green and a deep red at the background's own luminance, so every token keeps the contrast it has on the plain background. Line numbers and glyphs on changed rows use each theme's own green and red. The CLI's bundled copies of the three themes (astryx theme eject) carry the same palettes. (#7428)
  • A secondary Selector, MultiSelector, or ComplexSelector now matches the theme's secondary Button: under butter, chocolate, gothic, stone, and y2k it takes that Button's border, fill, text color, and hover instead of the default borderless neutral fill, so a toolbar mixing secondary buttons and selectors reads as one set of controls. Disabled and read-only triggers keep a still fill on hover, as a disabled Button does, and a Selector or MultiSelector inside an InputGroup keeps the group's neutral fill and edges. The default theme is unchanged, the selector docs now say secondary follows the theme's secondary Button, and themes added with the CLI get the same parity. (#7548)
  • astryx theme build --watch stops as soon as it is interrupted (Ctrl-C or SIGTERM). A change saved while a rebuild was running no longer starts another rebuild after "Stopped watching.", and a rebuild in progress stops with the watcher instead of keeping the process alive. (#7508)
Performance
  • astryx search and astryx build, and the search and build API functions, read each source directory once per call instead of once per candidate. Results are unchanged. A warm search drops from about 1.9 s to 0.4 s on macOS. (#7421)
Documentation
  • The generated token docs list the five diff row slots of the syntax vocabulary — --color-syntax-added, --color-syntax-removed, --color-syntax-diff-header, --color-syntax-added-marker, --color-syntax-removed-marker — with their defaults, so astryx docs tokens describes nineteen syntax slots. (#7389)
  • The Tailwind and migration setup docs now say that globals.css (or a layers.css holding only the @layer line) must be the first import in the root layout or app entry, before the astryx-themes module or any component that imports theme CSS; otherwise Tailwind preflight overrides Astryx base styles and theme overrides lose. The Tailwind v3 coexistence snippet moves its @layer line into a layers.css imported first, because Next.js (webpack or Turbopack) hoists CSS imports above an inline @layer line. (#7534)
  • Grid's columns docs now lead with the shape that reflows: a numeric columns is exactly N columns at every width and never reflows, and columns={{minWidth, max}} is the form for columns that must survive a phone. The astryx docs layout/responsive topic gains a "Columns that reflow" section with a reflowing stat row beside a fixed week row. No behavior changes. (#7340)
  • The styling setup docs now load the prebuilt stylesheets on every path. The "StyleX from source" path becomes "StyleX for your own code": it keeps astryx.css and points the StyleX compiler at your own and swizzled source only. A new "Other Astryx packages" section lists each package's stylesheet (richtext.css, lab.css, charts.css) and where to import it. Getting started no longer lists the two example setups that compile Astryx source; the remaining examples all load astryx.css. (#7587)
Contributors
Thanks to everyone who contributed to this release:

0.7.0

Breaking Changes
  • theme add now imports built themes; use theme eject to copy theme source. (#7138) The old contract copied theme source with theme add <slug> [path] [--overwrite] [--package <package>] and returned theme.add JSON. The ThemeAddResponse type and the theme.add response type are removed, with their ThemeAddResponse.type, ThemeAddResponse.data, and ThemeAddResponse.meta fields. The replacement imports the built theme with theme add <slug> [--package <package>] and returns theme.app; --import remains an accepted no-op. Plain theme add now returns theme.app with the owner package directly after type. Local themes carry no package.
    A path after theme add now exits 1 with ERR_INVALID_ARGUMENT, and --overwrite exits 1 with ERR_INVALID_OPTION; neither writes files. To migrate a script that copied source, run theme eject with the same slug, path, --overwrite, and --package arguments. A script that already runs theme add --import keeps the same meaning and needs no change.
  • init --remove-agents says when there was nothing to remove. (#6623) Migration: a consumer reading data.removed as a boolean keeps working; a consumer that narrowed on the literal true must accept the corrected value.
  • Four commands refuse silently ignored option pairs. (#7132) Migration: remove the option the command was ignoring.
  • Refuse invalid input that used to silently succeed. (#7149) Migration: pass a valid type or package, an integer limit, or the documented arguments, and catch ERR_AMBIGUOUS_COMPONENT for a multi-package name.
  • An empty-string argument no longer discards the rest of the command. (#6620) Migration: remove the empty string from the invocation; omit the argument to list.
  • doctor integration validate exits 1 when there is no package.json. (#7150) A missing package.json now produces a no_package error, so the existing error-severity exit rule applies. A directory with package.json but no integration manifest still exits 0.
    Migration: run the command in a directory that has a package.json, or handle exit 1 for that case.
  • Move canonical data-color defaults from generated theme CSS to the public StyleX dataVars group. (#6834) Import dataVars from @astryxdesign/core/theme/dataTokens.stylex for CSS-capable code. Canvas and other non-CSS APIs continue to use resolveThemeToken() or useTheme().token(). Rebuild committed theme CSS with astryx theme build; concrete themes now emit only explicitly authored data-color overrides.
    Old usage: Generated theme CSS owned the canonical --color-data-* root defaults.
    Replacement: The public StyleX dataVars group in @astryxdesign/core/theme/dataTokens.stylex owns the defaults; concrete themes emit only explicitly authored data-color overrides.
    Migration: Import dataVars from @astryxdesign/core/theme/dataTokens.stylex for CSS-capable code. Canvas and other non-CSS APIs continue to use resolveThemeToken() or useTheme().token(). Rebuild committed theme CSS with astryx theme build.
    Codemod: astryx upgrade runs validate-data-token-ownership, which rewrites nothing and reports fallback-less var(--color-data-*) uses (whole or embedded source strings, and stylesheets) and stale generated theme CSS for manual migration.
  • Doctor fails when the CLI cannot load what astryx.config asks for (#7130) A new configured-integrations check fails when an integration named in astryx.config cannot be loaded: not installed, installed without a manifest, or a manifest that throws or fails its schema. Such an integration is withdrawn whole and contributes nothing. The config check fails, instead of warning, when astryx.config imports but the CLI cannot load the project from it.
    Unchanged: a problem inside one contribution kind (an invalid component doc, a missing or unreadable root, or an unresolved replacement) stays a warning under integration-issues, and an autolinked dependency that cannot be loaded stays informational.
    No codemod applies: nothing in a project's source changes; install the integration, repair its manifest, or edit integrations in astryx.config.
    What counts as configured is every name astryx.config lists, including a package set aside for a provider conflict and the package being authored when its own config names it. Migration: install the integration, fix its manifest, or remove it from integrations; fix the astryx.config field the message names.
  • Typeahead, Tokenizer, CheckboxList, RadioList, and Slider no longer accept root xstyle, className, or style. Style the field with containerXstyle/containerClassName/containerStyle (the Field box; no effect inside InputGroup or a horizontal-labels FormLayout) and the visual control box with controlXstyle/controlClassName/controlStyle. Base props now reach the primary semantic control: the combobox input for Typeahead and Tokenizer, the role="group"/role="radiogroup" element for CheckboxList and RadioList, and the role="slider" thumb for Slider (the role="group" control in range mode). A caller aria-describedby is kept alongside the field's own description and status, on these components and on TextInput, TextArea, and NumberInput, which previously dropped it. CLI templates use the new props. (#7339) Migration: rename root xstyle/className/style to the part they styled before: containerXstyle/containerClassName/containerStyle on all five components, except a Typeahead inside InputGroup, whose root styling painted the control surface and moves to controlXstyle/controlClassName/controlStyle. The release's astryx upgrade codemod, migrate-field-input-styling, performs these renames on JSX usage.
    Not rewritten by the codemod, so update by hand:
    • ref and id, plus data-* (except Typeahead and Tokenizer data-testid, which marked the control surface), aria-*, and DOM event handlers such as onClick, previously landed on the outer Field (or were dropped by RadioList and Slider). They now land on the primary semantic control. Update code that measured, queried, or listened on the outer field, and wrap the component in your own element when you need an outer boundary.
    • Typeahead and Tokenizer refs are now HTMLInputElement.
    • A consumer onKeyDown on Typeahead or Tokenizer still runs after the built-in key handling, cannot cancel it, and still fires for keys on the clear button and tokens; for keys on the input it now runs on the combobox input itself.
    • RadioList and Slider used to drop DOM event handlers; they now run after the component's own handling, so a Slider onPointerDown, onKeyDown, onFocus, or onBlur that never fired before now fires (on the thumb, or on the group in range mode).
    • Tokenizer's onFocus/onBlur keep their meaning: focus entering or leaving the field.
    • Styling passed through a wrapper's own props or a spread is not rewritten and now fails type-checking at that callsite.
    Untyped callers get a development warning and the value is ignored.
    From #5656 by @harjothkhara.
  • Selector, MultiSelector, and ComplexSelector no longer accept root xstyle, className, or style. Style the field with containerXstyle/containerClassName/containerStyle (the Field box; no effect inside InputGroup, a horizontal-labels FormLayout, or with renderTrigger) and the visual control box with controlXstyle/controlClassName/controlStyle. Base props such as ref, id, data-* (including data-testid), aria-*, and DOM handlers reach the trigger button that carries the combobox role (or, with renderTrigger, the caller's control), and a caller aria-describedby is kept alongside the field's own description and status instead of being replaced. Handlers keep their existing order: a ComplexSelector onClick on its own trigger can still cancel opening, and newly forwarded handlers (including those reaching a renderTrigger control) run after the built-in toggle and keyboard handling. CLI templates use the new props. (#7341) Migration: rename root xstyle/className/style on these components to controlXstyle/controlClassName/controlStyle, which style the same element as before. Not a rename: a data-testid or other base prop now lands on the trigger button rather than the bordered box around it (query the box with .closest() if a test measured it), and with renderTrigger base props and ref now reach the caller's control. Rename JSX usage by hand, or run astryx upgrade; it runs migrate-field-input-styling, which does not follow styling passed through a wrapper's own props or a spread, which now fails type-checking at that callsite, so rename it there. Untyped callers get a development warning and the value is ignored.
    From #5656 by @harjothkhara.
  • TextInput, TextArea, NumberInput, and FileInput no longer accept root xstyle, className, or style. Style the field with containerXstyle/containerClassName/containerStyle (the Field box; no effect inside InputGroup or a horizontal-labels FormLayout) and the visual control box with controlXstyle/controlClassName/controlStyle. Base props such as ref, id, data-*, aria-*, and DOM handlers reach the native control, and a caller id is now honored there. CLI templates use the new props. (#7336) Migration: rename root xstyle/className/style on these components to controlXstyle/controlClassName/controlStyle, which style the same element as before. astryx upgrade rewrites JSX usage; styling passed through a wrapper's own props or a spread is not rewritten and now fails type-checking at that callsite, so rename it there. Untyped callers get a development warning and the value is ignored. Not rewritten by the codemod: a caller id used to be replaced by a generated one and now reaches the native control (the label stays associated), so remove an id you passed but relied on being ignored. Other base props already reached the native control and are unchanged.
    From #5656 by @harjothkhara.
  • matcha's and y2k's spacing steps are rem (--spacing-2: 0.75rem), so their gaps and padding follow the reader's root font size like the core scale. Every step is the same pixel value at the default 16px root; a reader with a larger root font size now sees proportionally larger spacing on these themes. The CLI's copies of both theme templates and the annotated theme template's spacing example change the same way. (#7374) Migration: nothing to change to take the new behaviour. To keep fixed pixel spacing on one of these themes, extend it and override the steps in px, which is honoured as written: defineTheme({name: 'app', extends: matchaTheme, tokens: {'--spacing-2': '12px'}}).
  • On touch devices narrower than the lg breakpoint ((width < 1024px) and (pointer: coarse)), the 14px-base first-party themes now floor their type base to 16px and re-derive the ratio so Display 1 keeps its desktop size: neutral and chocolate (base 14, ratio 1.2 → 1.1736) and butter and stone (base 14, ratio 1.25 → 1.2225). On phones, body, label and code text rise from 14px to 16px; supporting text, the headings and Display 2 and 3 grow by 1–2px; only Display 1 holds its desktop size. Desktop sizes are unchanged. gothic, matcha and y2k already use a 16px base and need no rule. The CLI's theme templates carry the same rule, so a newly scaffolded theme gets it too. (#6699) An app theme that extends one of these four themes and sets its own typography.scale or type-size tokens inherits this rule, and on touch + narrow screens the rule replaces those values (a base-18 child drops to a 16px body and a 42px Display 1). Append your own rule for the same condition with the values you want; a later rule for the same condition wins.
    Migration: nothing to change to take the new phone scale. To keep the previous 14px phone scale in an app, extend the theme and append a later rule for the same condition: defineTheme({name: 'app', extends: neutralTheme, adaptations: {rules: [{when: {pointer: 'coarse', width: {below: 'lg'}}, value: {typography: {scale: {base: 14, ratio: 1.2}}}}]}}). For butter and stone use ratio: 1.25 and also set tokens: {'--text-supporting-size': '12px'} in that rule's value, because those themes pin supporting text at 12px rather than the 11px the scale alone gives. This cannot be rewritten by a codemod: whether an app wants the floor is a product choice.
  • Stop reading the Astryx-owned agent variables ASTRYX_AGENT_ID, ASTRYX_AGENT_SESSION_ID, and ASTRYX_AGENT_METADATA (#7127) The theme-import change already stopped reading ASTRYX_THEME; these three were the last Astryx-owned agent variables. A test now fails on any process.env.ASTRYX_* read in the CLI source.
    Migration: set AGENT and AGENT_SESSION_ID, which the CLI already reads, instead of the Astryx-prefixed variants. ASTRYX_AGENT_METADATA has no replacement variable.
  • Remove the deprecated component-theming compatibility surface scheduled for 0.7.0. Components now emit only canonical target classes and reflected data-* prop/state selectors. Theme discovery and build output no longer expose deprecated targets, and ThemePropsOptions plus ComponentThemingTarget.deprecatedFor are removed. The theme targets --json response drops the ThemeTargetEntry.deprecatedFor field, because no target it lists is deprecated. (#7302) Migration: run the required codemod migrate-deprecated-theme-surface with astryx upgrade --from <your 0.6 version> --apply --path . after upgrading.
    The codemod renames removed target keys inside theme components maps (an imported defineTheme() call, an object typed as an Astryx theme, or a theme object with a static name), renames target classes in CSS, and replaces target-qualified bare prop/value/state classes with reflected data-* selectors, using every bare class the final 0.6 release emitted. It leaves dynamic/computed theme keys, unqualified or unknown classes, and CSS embedded in JavaScript/TypeScript strings for manual review. It adds TODO(astryx upgrade) when old and canonical keys coexist, and when a bare class Astryx once emitted has no known meaning on the target it qualifies.
    The four per-component clear-icon aliases all become the shared input-clear-icon, which styles every input's clear icon. In CSS the codemod keeps each rule on its component with :where(.astryx-<component> *), which adds no specificity. Theme keys cannot carry that scope, so the codemod adds a TODO naming the CSS selector to use.
    Code that passed {legacyNames} to themeProps() or set deprecatedFor in a component doc should delete that argument or field; the canonical target is unchanged.
    Rename theme keys and CSS target classes with this complete mapping:
    • base-table → table
    • checkbox → checkbox-indicator
    • codeblock → code-block
    • codeblock-copy-button → code-block-copy-button
    • codeblock-header → code-block-header
    • codeblock-title → code-block-title
    • date-input-clear-icon → input-clear-icon
    • date-range-input-clear-icon → input-clear-icon
    • hovercard → hover-card
    • multi-selector-clear-icon → input-clear-icon
    • navicon → nav-icon
    • popover-surface → popover
    • progressbar → progress-bar
    • progressbar-fill → progress-bar-fill
    • progressbar-mark → progress-bar-mark
    • progressbar-track → progress-bar-track
    • radio → radio-indicator
    • radio-dot → radio-indicator-dot
    • selector-clear-icon → input-clear-icon
    • statusdot → status-dot
    • textarea → text-area
    For custom CSS, replace removed bare selectors with the corresponding reflected attribute on a canonical target—for example, .astryx-button.primary.sm becomes .astryx-button[data-variant="primary"][data-size="sm"], and .astryx-switch.checked becomes .astryx-switch[data-checked="checked"]. Review unqualified classes such as .primary manually because they may be application-owned.
  • Remove the astryx layout command group. (#7137) Removes the deprecated astryx layout command group (expand, check, grammar), its three response types (layout.expand, layout.check, layout.grammar), and the programmatic API exports (layoutExpand, layoutCheck, layoutGrammar).
    Use astryx build to choose the template to start from, astryx template to scaffold it, and astryx docs layout for layout guidance. The layout guide is unaffected. The error codes ERR_LAYOUT_PARSE and ERR_LAYOUT_INVALID are retained.
    Removed JSON ids: LayoutBlockReference.mode LayoutBlockReference.name LayoutCheckOptions.cwd LayoutCheckOptions.form LayoutCheckOptions.loose LayoutCheckResponse.data LayoutCheckResponse.data.compact LayoutCheckResponse.data.errors LayoutCheckResponse.data.form LayoutCheckResponse.data.outline LayoutCheckResponse.data.valid LayoutCheckResponse.data.warnings LayoutCheckResponse.type LayoutExpandOptions.cwd LayoutExpandOptions.form LayoutExpandOptions.loose LayoutExpandOptions.name LayoutExpandOptions.targetPath LayoutExpandResponse.data LayoutExpandResponse.data.blocksReferenced LayoutExpandResponse.data.code LayoutExpandResponse.data.componentsUsed LayoutExpandResponse.data.demoMediaReplaced LayoutExpandResponse.data.form LayoutExpandResponse.data.states LayoutExpandResponse.data.todos LayoutExpandResponse.data.warnings LayoutExpandResponse.data.written LayoutExpandResponse.type LayoutGrammarOptions.cwd LayoutGrammarResponse.data LayoutGrammarResponse.data.aliases LayoutGrammarResponse.data.text LayoutGrammarResponse.type LayoutIssue.col LayoutIssue.formatted LayoutIssue.line LayoutIssue.message LayoutIssue.suggestions
  • Spacing tokens are rem (--spacing-2: 0.5rem), so gaps and padding follow the reader's root font size the way the type scale does. Every token value is unchanged at the default 16px root. (#7359) One change shows at the default root: the useTableRowExpansion chevron now sits centered in its fixed 40px column instead of running past its edge (its button moves from 24–48px to 8–32px of the column). Under a theme with a larger spacing scale, such as matcha, the chevron is visible again and the detail panel lines up with the first column instead of starting 20px past it.
    Old usage: The --spacing-* defaults were fixed px (--spacing-2: 8px), so useTheme().token(), resolveThemeToken(), tokenDefaults and spacingDefaults returned px strings, and spacing stayed the same size when a reader raised the browser font size.
    Replacement: The defaults are rem with the same value at a 16px root (--spacing-2: 0.5rem, --spacing-4: 1rem), and those readers return the rem string.
    Migration: CSS that reads var(--spacing-*) needs no change. Code that parses a spacing token as a px number converts the rem value with the root font size, or reads the element's computed length. A theme that wants fixed px spacing sets the tokens back, for example defineTheme({tokens: {'--spacing-2': '8px'}}).
    Codemod: None. A token read and parsed at runtime cannot be found and rewritten statically, and CSS uses need no rewrite.
  • theme build exits 1 when it reports private --_* variables. (#6872) The old contract reported private-variable errors but exited 0. The corrected contract keeps the same warnings, receipts, generated files, and --check output, but exits 1.
    To migrate, a CI step that relied on exit 0 must fix the theme's private --_* inputs.
New Features
  • astryx upgrade adds padding={0} to BottomSheet elements that do not set padding, keeping their unpadded content box now that BottomSheet pads like Dialog. Sheets whose only child is a Section or a Layout are left unchanged. A sheet with a Layout anywhere in its content also gets a TODO comment, because padding={0} removes the inset between that Layout's regions and the Layout's own padding restores only its outer edges. A shadowed BottomSheet binding is left alone, and a second run changes nothing. (#6884)
  • astryx upgrade runs migrate-field-input-styling, which renames root xstyle/className/style on Field-composed inputs to the part they styled before: controlXstyle/controlClassName/controlStyle on TextInput, TextArea, NumberInput, FileInput, DateInput, DateRangeInput, DateTimeInput, TimeInput, Selector, MultiSelector, and ComplexSelector, and containerXstyle/containerClassName/containerStyle on Typeahead, Tokenizer, CheckboxList, RadioList, and Slider. It rewrites JSX written directly on an Astryx import (named, aliased, or namespace). Spreads and wrappers that forward their own styling props are left for manual migration, and a callsite that already sets the target prop gets a TODO instead of a rename. (#7342)
  • astryx upgrade renames emptySearchResultsText to emptySearchText on Tokenizer, Typeahead, BaseTypeahead, and ChatComposerInput trigger objects, for the release that removes the old name. (#7289)
Fixes
  • template and build follow the project's package manager. The nearest directory from the target up to the workspace root that has a packageManager field or a lockfile decides. With neither, the command uses npm, whatever package manager launched the CLI. When that directory's lockfiles disagree and nothing it commits picks one, installCommand is null and the note names the missing packages, the directory, and the lockfiles that disagree, instead of guessing a command that would write a second lockfile. (#7343)
  • Teach generated palette references in the full custom-theme authoring guide. (#7268)
  • Generate Neutral's runtime palette references from the stops its theme uses, and fail verification when the package or CLI template copy drifts. (#7255)
Documentation
  • Clarify release-branch codemod promotion and version ownership. (#7293)
Contributors
Thanks to everyone who contributed to this release:

0.6.8

Fixes
  • A template that sets replaces needs @astryxdesign/cli 0.6.4, and one that sets keywords needs 0.6.6, not 0.7.0 (#7265). Published 0.6.4 applies a template's replaces, and published 0.6.6 reads its keywords. integration verify asked for ">=0.7.0" for both, a range no released CLI satisfies, and npm leaves the CLI uninstalled in an app that installs a package with that optional peer. integration verify now accepts ">=0.6.4" for replaces and ">=0.6.6" for keywords, and still refuses a range that admits an older CLI. Its messages now say what older CLIs do. Before 0.6.6 a template that sets keywords is dropped, and before 0.6.4 the package's doc topics are hidden too.
Documentation
  • Guide new theme authors to the palette generator and keep the broad color scale opt-in in generated theme templates (#6795).
Contributors
Thanks to everyone who contributed to this release:

0.6.7

New Features
  • Apps can opt into package-managed themes with astryx theme add <slug> --import. The command records the theme in one generated app module with its production CSS, optional font CSS, and default slug. Use theme remove and theme use to manage that record, and pass themes[defaultThemeSlug] to <Theme>. Plain astryx theme add keeps its released source-copy behavior, options, stdout, exit status, and every theme.add data field. It now warns that theme eject is the explicit source-fork command and theme add --import is the way to use the package-managed theme. Its machine result adds the DEP-0005 deprecation entry; the cleanup is CLN-0005 in a later scheduled minor.
    Use defineTheme({extends: importedTheme, ...}) for ordinary customization. theme eject creates an independent local fork with its descriptor. JSON callers receive theme.app from import, remove, and use, or theme.eject from eject.
    Existing bundled source copies stay where they are and keep their bytes. Run astryx upgrade --from 0.6.4 --path . --apply to add the missing unmaintained descriptor beside each bundled copy in src/themes. Until then, theme commands skip those copies and theme list and doctor name them as unmigrated. Package integration themes keep their released complete-directory copy, including the authoring descriptor.
    ASTRYX_THEME is no longer read. In a project with a generated app theme module, component metadata reads that record's default built theme. Without the module, the released package.json#astryx.theme lookup keeps its meaning. Doctor loads every recorded built module through the same theme adapter, so a broken runtime import fails theme-owners instead of passing.
    theme build also writes <out>.css.d.ts so TypeScript accepts generated CSS imports. Check mode stays compatible with released output sets that do not have this new stub yet.
    Integration themes can export built modules and stylesheets. astryx integration add theme creates those exports, and integration verify checks the exported paths against the packed package and source. Missing partner exports alone do not block packing. Every declared export must resolve; staleness is a warning for an incomplete set and an error for the complete importable module and stylesheet pair.
  • Every result now names the package it comes from. A --json result about one artifact (a component and each of its projections, a doc topic, index, section, or docs-tree node, a template, a hook, and swizzle) carries package in its envelope, directly after type. A result that lists artifacts gives each item its own package: every search hit, build's start, alternatives, blocks, and components, a doc's sections, a docs-tree node's children, --blocks entries, and the component --list and upgrade --list entries. Text names the same package; --source, --showcase, and a template's source still print only the source on stdout and name the package on stderr. Existing fields are unchanged.
  • Deprecate the astryx layout command group The astryx layout command group (expand, check, grammar) is deprecated. Use astryx build to choose the template to start from, astryx template to scaffold it, and astryx docs layout for layout guidance.
    In human mode each invocation prints a stderr warning naming the replacement. In JSON mode the response envelope carries machine-readable deprecation metadata in its meta field. Canonical stdout, exit codes, and the layout.expand / layout.check / layout.grammar response schemas are unchanged.
    Deprecation lifecycle (spec:AST-017 FR28, FR31) — removal only in a later minor whose frozen manifest carries both ids of a pair:
  • An integration component can replace a Core component, once its package opts in An @acme/nav component whose doc sets replaces: 'SideNav' takes over SideNav for unqualified component detail, batch selectors, every component --list detail level, search, swizzle, and gap-report routing, when @acme/nav declares "@astryxdesign/cli": ">=0.6.7" in peerDependencies (optional in peerDependenciesMeta). Every result names its package, --package @astryxdesign/core still selects the original Core component, and the replacement keeps answering to its own name. component SideNav --package @acme/nav also selects it.
    Any @astryxdesign/cli range that starts at 0.6.7 or later is the opt-in, including the >=0.7.0 that integration add doc --parent wrote in 0.6.4 and 0.6.5, and integration add theme in 0.6.5. A package whose range admits an earlier CLI keeps its component under its own name and Core stays selected, and an app that loads it sees no new output; its author gets warnings naming the range to add, from astryx doctor integration components and integration verify. For a package that declares the range, astryx doctor integration components reports a missing Core target, an invalid value, a component named after a different Core component, or two replacements for one target in the package as errors and exits 1. When several packages replace one target, an explicitly configured package beats an autolinked one, the later configured package wins, and Doctor warns.
  • Add the model comparison page template with responsive sticky context and accessible interactions. (#6251)
  • New table-collapsible page template: several tables on one page, each in a collapsible card with its own columns, for groups that do not share a schema. Every table sorts on its own, one time range in the page header drives all of them, and rows expand in place into a full-width history chart. Below 720px each table folds to its name and headline figure. (#6065)
Fixes
  • Printed commands name the scoped @astryxdesign/cli package whenever the astryx bin is not installed for the project
  • Compact the generated agent-docs block: fewer lines, same behavioral coverage
  • astryx doctor keeps its themes check, with the same id, label and fields, beside the new theme checks, so scripts that read it by id keep working. Without a generated theme module it reports what it did before: whether an @astryxdesign/theme-* package is installed, and whether the app's package.json names a theme in astryx.theme. Its fix now names theme add --import. With a generated module it reports the overall result of the theme checks. In a workspace, themes reads the app's own package.json, the file the CLI reads when it resolves the theme, rather than the package.json beside the root node_modules. It no longer counts the ASTRYX_THEME variable, which the CLI does not read, as a wired theme.
  • Doctor says why it skipped a check and what it checked, and doctor integration validate no longer crashes on a folder it cannot read
  • upgrade: exclude node_modules from integration codemod discovery When an integration declared its codemods root as the package root (codemods: "./"), the version-folder scan treated node_modules, .git, __tests__, and __fixtures__ as version folders and loaded their files as codemods. The same SKIP_DIRS filter that the recursive file walk already used is now also applied to the top-level version-folder enumeration.
  • Align the layout deprecation (DEP-0006) with the documented envelope and precedent The layout command's JSON envelope now emits meta.deprecations: [{id, replacements}], matching the response schema doc and the DEP-0005 theme add precedent. The deprecated CommandDoc field renders in --help and the manifest. The programmatic API exports (layoutExpand, layoutCheck, layoutGrammar) carry @deprecated in their declarations and generated types. Command and function reference pages name DEP-0006 and the replacement. The DEP-0006 record names its direct authority. All released data fields are unchanged.
  • swizzle: rewrite every .stylex import to a deep path astryx swizzle Button (and any component that imports a .stylex module from outside its own directory) emitted an import that collapsed to the directory barrel — e.g. @astryxdesign/core/utils instead of @astryxdesign/core/utils/interactionOverlay.stylex. The barrel does not re-export those StyleX symbols, so the swizzled file could not compile.
    rewriteImports now gives every *.stylex module the deep subpath. The exports generator (scripts/sync-exports.js) adds 16 specific subpath exports for the .stylex modules swizzled components actually reference across directories:
    DateInput/tokens.stylex, Icon/IconSize.stylex, Indicator/indicator.markers.stylex, Layer/layerAnimations.stylex, Layer/layerTextReset.stylex, Layer/layerViewportInset.stylex, Layout/container.stylex, Layout/edgeCompensation.stylex, Layout/padding.stylex, NavItem/navItemStyles.stylex, Selector/selectorPresentation.stylex, Stack/stack.stylex, Stack/stackItem.stylex, Text/text.stylex, utils/focusOutline.stylex, utils/interactionOverlay.stylex
    These are public API additions. Each module already ships in the npm tarball (in dist/); only the exports map entry is new. No wildcard — a future cross-directory .stylex import needs a deliberate entry in STATIC_EXPORTS. Precedent: ./theme/dataTokens.stylex (AST-066 FR2).
  • template: show a grouped summary by default instead of the full catalog Bare astryx template (no name, no --list) now shows templates grouped by category with counts — about 21 KB instead of the full 149 KB catalog. The full catalog with descriptions is still reachable via astryx template --list.
    JSON output is unchanged — --json template still returns the complete template.list response. This is a text-only rendering change under AST-017 FR11: the machine-readable response schema is the contract; text formatting is not.
    Trade-off: the grouped output still includes every template id (so template <id> works from a copy-paste), at the cost of ~21 KB. An even shorter summary (type + count only, no ids) would be ~500 bytes but would require a second step to discover any id. The current shape serves both human scanning and agent copy-paste without a round-trip.
  • template: bare template --type no longer prints an empty group header
  • A section read on a docs-tree namespace answers from the guide that has the section again, so astryx docs layout side-panels and the other layout section reads released in 0.6.6 work after the layout split. docs(route, section) returns the same docs.detail.section the guide's own section read returns, found by key, then by title, in --dense and --zh too. When no guide or more than one has the section, the read fails with ERR_UNKNOWN_SECTION and names the guides to read it from.
  • astryx search ranks a component, hook, or template that a query word names above a doc that matched only by keyword, heading, or text. font size finds Text first again instead of a typography guide. A doc the query names, such as font setup or migration, or one whose title the query holds, such as resizable side panels, keeps its place. Result scores do not change; only the order between domains moves.
  • astryx search finds a guide when the query is its route or title in the other number: side panel finds the side panels guide first again, and header and footer finds headers and footers. A section's heading still doesn't count as its topic's name, so font size keeps finding Text first.
  • Fix comparison table category from "Table - Frozen Column" to "Table - Comparison" The category described an implementation detail (the frozen label column) instead of what the template is for. Builders searching by layout type now find it under Comparison.
  • Template and build tell you what a scaffolded template needs that your project lacks. When astryx template <name> <path> scaffolds a file that imports packages your project does not have (e.g. @heroicons/react, recharts, lucide-react), the receipt now includes a ready-to-run install command with the project's package manager and version ranges from the CLI workspace. astryx build shows the same note on its start template.
    When a scaffolded template uses StyleX and the project has no compiler plugin configured, the receipt warns and points to astryx docs styling-overview. The agent-docs block no longer says "don't use xstyle" flat-out — it acknowledges that some templates need it and links the setup doc.
    detectStylingSystem now recognizes the official @stylexjs/rollup-plugin, @stylexjs/webpack-plugin, and @stylexjs/nextjs-plugin alongside the existing entries.
  • astryx theme build prints one line per built theme, plus one line naming fonts the themes do not load. Before, every theme printed the same install example and font recipe, so a build of many themes printed the same blocks again and again. --detail full prints the install example and font recipe, once for a batch instead of once per theme; for one theme it prints what the default printed before. Only the text report changes: --json output, --check, exit codes and written files are unchanged.
  • Wherever the CLI shows the <Theme> wrapper, it now also shows where Theme comes from: import {Theme} from '@astryxdesign/core'. This covers the astryx init next steps, theme add and theme build output, the doctor fix for an unimported theme module, build help, and the theme guides.
  • astryx theme add <slug> --import names the npm package that owns the added theme, in its JSON envelope (package, directly after type) and in its text output, the same way other results about one artifact do. A local theme has no package, so its result has no package, and theme remove and theme use are unchanged. astryx theme add --list keeps its JSON. Its text now names theme add <slug> --import to use a theme and theme eject <slug> to fork one, instead of the deprecated copy form.
    astryx doctor adds a theme-management check, and focused theme-* checks once a project has a generated theme module.
  • One-off commands in a classic Yarn (1.x) project use npx @astryxdesign/cli … instead of yarn dlx, which classic Yarn does not have
Documentation
  • astryx docs migration, internationalization, styling, styling-libraries, typography and tokens still work and now list focused guides. Each section is also readable under its guide, for example astryx docs tokens/tokens-spacing or astryx docs styling/tokens-and-setup stylex-setup, and astryx docs <topic> <section> keeps working: every section key these topics had still opens the same section. astryx docs tokens --depth all --detail full prints every token table, and a token-ref to tokens keeps resolving through the guide that holds the table. Integrations: these six names are now docs-tree sections, not topics, so an integration doc that declares extends or replaces with one of them is reported as naming no topic, and its content no longer shows. To keep that content, ship it as your own topic under a new name, or as a guide in your package's own section (astryx integration add doc <name> --parent <your-section>). Topics that are still flat, such as theme or color, can still be extended or replaced.
  • astryx docs layout still works and now lists the focused guides. Each section is also readable under its guide, for example astryx docs layout/side-panels or astryx docs layout/scaffold shell, and astryx docs layout <section> keeps working. (#7125)
  • astryx docs layout opens with its overview again, and astryx docs author-a-theme and use-a-theme restore guidance the theme split dropped: what a bad extends base does, how adaptation rules are validated, what __built means, the icon-registry specifier traps, registerTheme, and wiring built themes in development too. (#7204)
  • Add a choose-a-path styling overview and restore the import-based workflow across the theme guides. (#7134)
  • Split the theme documentation into focused guides for using and authoring themes, with a concise overview that points to both workflows. (#7141)
Other Changes
  • A hint uses npx astryx … (or pnpm exec, yarn, bunx) only when the astryx bin is in node_modules/.bin, in the project or a folder above it. Otherwise it prints npx @astryxdesign/cli … (pnpm dlx, yarn dlx, bunx), as it already did when the CLI ran from an npx or dlx cache.
  • A global install, or a workspace install used in a fresh package, used to print npx astryx …. The npm package named astryx is not this CLI, so following that hint fetched an unrelated package.
  • astryx blog follows the same rule, and the incident console template names the scoped package.
    Classification: contract-restoring. JSON shapes are unchanged; only hint text changes, and projects with the CLI installed keep npx astryx ….
  • deprecation DEP-0006 / cleanup CLN-0006 — astryx layout command group (expand, check, grammar)
  • A check that needs the loaded project quotes the reason the CLI could not load it, instead of only "Skipped".
  • The config check warns when astryx.config imports but the CLI cannot load the project from it. Before, it said the config loaded cleanly.
  • Integration contributions name the integrations they checked; with none loaded, the check reports info and says there is nothing to check.
  • The agent-docs check reads every file init can write (Hermes included) and looks in the project root as well as the working directory, so running doctor from a subfolder no longer reports that there are no agent docs.
  • astryx doctor integration validate names a folder it cannot read and keeps checking. A declared root that is a file or that cannot be read is reported as invalid_root or unreadable_root instead of a raw error or a crash.
    Classification: contract-restoring. No check becomes stricter: every new finding is a warning or info, and the only exit-code change is that an unreadable folder outside every root no longer crashes validation.
  • Whenever the CLI prints its scoped one-off form (it ran from an npx or dlx cache, or the astryx bin is not installed for the project), a Yarn project got yarn dlx @astryxdesign/cli …. On classic Yarn that command fails.
  • Classic Yarn is read from the declared packageManager version, the yarn.lock header (# yarn lockfile v1), a committed .yarnrc (without .yarnrc.yml), or the runner. Yarn 2 and later keep yarn dlx.
    Classification: contract-restoring. JSON shapes are unchanged; only hint text changes.
Contributors
Thanks to everyone who contributed to this release: