Skip to content

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

TypeScript

chore: version packages for v0.6.3 (#6358)

Cindy Zhang8492ddeee2aa
diff --git a/.changeset/bottom-sheet-keyboard-scroll.md b/.changeset/bottom-sheet-keyboard-scroll.md
deleted file mode 100644
index d1bc90d835..0000000000
--- a/.changeset/bottom-sheet-keyboard-scroll.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Make overflowing BottomSheet text keyboard reachable with a named scroll-body tab stop. Add shared focus-time keyboard delegation to `useScrollableArea`: forward Tab may enter the first native link/button directly, while inputs, composite widgets, and nested scroll owners retain the viewport stop. Reverse traversal skips the delegated viewport; pointer/programmatic focus and content changes never trigger delegation. Sheet scroll containment now applies only while content overflows and uses the shared `contain` policy, which permits native edge feedback. (#6301)
-
-@jiunshinn
diff --git a/.changeset/bright-waves-clear.md b/.changeset/bright-waves-clear.md
deleted file mode 100644
index e7318a427a..0000000000
--- a/.changeset/bright-waves-clear.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Show each shared InputClearButton's contextual action label in a tooltip. Clearable inputs now give sighted users the same specific action name already available to assistive technology. (#6354)
-
-@athz
diff --git a/.changeset/canvas-editor-template.md b/.changeset/canvas-editor-template.md
deleted file mode 100644
index ca79fb2df6..0000000000
--- a/.changeset/canvas-editor-template.md
+++ /dev/null
@@ -1,401 +0,0 @@
----
-'@astryxdesign/cli': patch
----
-
-[feat] Add a Canvas Editor page template (#6237)
-@ernestt
-
-A layered-artboard workspace: a File/Edit/View/Object/Help
-menubar over a layer rail and asset library on the left, the artboard centered
-on a muted backdrop under a floating tool bar that sets zoom, and a property
-inspector on the right whose fields retarget to the selected layer. Both rails
-drag to resize.
-
-The inspector is the substance of it. A text layer gets font, weight, colour,
-size, line height, letter spacing, horizontal and vertical alignment, slant,
-decoration, transform, a text shadow and a stroke; an image layer gets fit and
-the nine CSS filters, each on a number and a rail that move together. Colour
-anywhere in the panel opens a real picker. Everything that can reach the
-artboard does — typing in Transform recases the poster, dragging Sepia tints
-the photograph.
-
-It fills a gap next to `Tools - Page Editor`. That one composes a document — a
-palette of blocks dropped into a flow that reflows around them. This one moves
-objects on a fixed 1080 x 1920 frame, where position and size are coordinates
-rather than an order, so the inspector reads X/Y/W/H and the canvas needs a
-zoom control at all.
-
-Two decisions worth knowing if you copy it:
-
-**The artboard is themed, not styled.** The template's `canvasEditorTheme` is
-pinned to `mode="light"` around the artboard, so the poster keeps its palette
-when the editor around it goes dark. The theme carries what belongs to the
-poster as a whole —
-the display face, the leading, the uppercase treatment, the frame margins —
-and the display face is Anton with a fallback chain through the condensed
-grotesques that ship with macOS and Windows. The chain puts Impact ahead of
-Arial Narrow because every face in it is a single-weight black rendered at
-weight 400, and Arial Narrow at 400 reads thin rather than poster-heavy.
-
-Size and tracking are deliberately not tokens: they belong to a layer rather
-than to the poster, so they live on the layer and the inspector edits them
-live. That split is the line worth copying — theme what the surface owns,
-leave per-object properties to the object.
-
-**Zoom is a transform, not a re-layout.** The artboard always lays out at its
-native size and the frame scales the painted result, which keeps the theme's
-numbers in artboard pixels — the same numbers the inspector shows — and keeps
-the poster from reflowing between zoom steps.
-
-**The menubar is one button, not five.** File/Edit/View/Object/Help became
-submenus of a single `DropdownMenu`. A menubar spends the top-left on five
-words that are only read by someone already hunting for a command, and this
-editor has something better to do with that space: the tabs, which are read
-constantly. The commands keep their grouping — the bar became the first
-level of the menu rather than disappearing. The menu takes a `menuWidth`
-because left to itself it matches its trigger, and the trigger is a 28px
-icon button: five one-word rows in a column barely wider than the words,
-with nowhere for the submenu chevrons to sit.
-
-Five smaller things the template works out, in case you hit the same walls:
-
-**A field names itself from inside.** Every inspector control is one input
-with a glyph in its `startIcon` slot — `X`, `Y`, `W`, `H` — rather than an
-`InputGroup` pairing an addon to a field. It reads as a single control, and
-the accessible name stops stuttering ("Horizontal position", not "Horizontal
-position X"). `startIcon` takes an SVG component, so the letters are drawn on
-the same 24px grid Lucide uses and sit interchangeably beside real icons.
-
-**One left edge across the panel.** The label column is a set width, but a
-flex item shrinks before its siblings do, and the fields beside it carry
-StackItem's min-width reset. Without `flexShrink: 0` on the label column the
-row spends its shrinkage there, and every field lands on a slightly different
-edge — which is the one thing an inspector cannot afford.
-
-**Row actions use the shared reveal primitive.** A layer's lock stays hidden
-until the row is pointed at or receives keyboard focus. `useContainerReveal`
-owns the hover, focus, coarse-pointer, and reduced-motion behavior, while
-`TreeListItemData` forwards the returned row props so every nested row keeps
-its reveal state isolated.
-
-**A fixed-height Card scrolls; the artboard has to clip.** Give `Card` a
-`height` and it becomes a scroll container, which is right for a card holding
-more copy than fits. The artboard is the opposite case: it lays out at its
-native 1080 wide at every zoom step and the frame scales the painted result,
-so its content is deliberately larger than its box and the card would offer
-1080px of sideways scroll inside a 432px frame. `overflow: clip` through
-`xstyle` is the fix, and `clip` over `hidden` because nothing here should
-scroll at all — including the quiet scroll `hidden` still performs when
-something inside it takes focus.
-
-**Concentric corners come out of the padding.** The floating tool bar is a
-card with one spacing step of padding, so the controls inside it round to the
-card's radius _less_ that step — written as
-`calc(var(--radius-container) - var(--spacing-1))` rather than a number, so
-it still holds if either token moves. An inner corner cut at the same radius
-as its container reads as a rounder curve crossing a straighter one; matching
-the difference is what strikes both from the same centre. While you are in
-there: a vertical `Divider` is `height: 100%`, and a flex row that centres
-its items gives a percentage height nothing to resolve against, so the rule
-collapses to zero and the bar silently loses its groups. `alignSelf: stretch`
-is what gives it a height.
-
-**The top bar is a `LayoutHeader`, not a `Toolbar`.** It reads like a
-toolbar and it is not one. A toolbar is a set of peer commands that arrow
-keys walk across, and the document tabs break that twice: arrowing off a tab
-landed on that tab's own close button, and a strip of open documents is not
-a band of tools in the first place. It also fought the padding — a toolbar
-sizes its gutters for a band heading content, and app chrome wants to sit
-tighter, which took a `--astryx-section-padding-inline` override and the
-edge compensation that override republished.
-
-`LayoutHeader` is the component for the slot, and `padding={1}` settles all
-of it: 4px on every edge puts the menu button's box exactly where the ghost
-inset used to pull it, so the glyph lands on the same pixel with nothing
-pulled back out. Same 45px bar, same 18px glyph centre, same divider —
-measured before and after — minus a role that was describing the wrong
-thing. The floating canvas tool bar stays a `Toolbar`, because that one
-really is a row of peer commands, and it still roves left to right.
-
-**One icon on three rows is a list nobody reads.** Border, shadow and fill
-all shipped with the same `Palette` swatch, and the three effect presets in
-the library shared it too — six rows, one mark, so the column read as one
-control repeated rather than six different things. Lucide has no `shadow`,
-`fill` or `padding` icon, so the picks came out of reading the pack rather
-than guessing at names: `PaintBucket` for fill, `SquareStack` for shadow
-(two offset squares is a drop shadow), plain `Square` for border,
-`SquareRoundCorner` for per-corner radius so it stops colliding with the
-per-side padding button that was also `SquareDashed`. Two things worth
-knowing if you go looking yourself. Names in that pack can be aliases —
-`FlipHorizontal` re-exports `square-centerline-dashed-horizontal`, which at
-16px is an unreadable dashed box, and the mirrored triangles you actually
-want are `FlipHorizontal2`. And judge candidates at 16px, not at sketch
-size: `radius` is a legible corner gauge at 48px and mush at 16.
-
-X, Y, W and H stay letterforms. They are names, not pictures — no icon
-distinguishes the horizontal coordinate from the vertical one, and every
-design tool prints the letters for the same reason.
-
-**A shortcut is a hint, not a control.** `Kbd` paints one key cap per key, so
-`⌘N` arrived as two small objects beside the menu item and read as something
-you could press. Desktop menus print shortcuts as quiet secondary text, which
-is what these are now — a `Text type="supporting" color="secondary"`, one
-string, set against the menu's right edge. The cost is platform awareness:
-`Kbd` resolves `mod` to ⌘ or Ctrl, and it does that through
-`isApplePlatform`, which core keeps unexported on purpose, so a template that
-leaves `Kbd` prints macOS glyphs and stops adapting. The `shell-nav` menubar
-already makes that trade. If you need both the quiet treatment and the
-platform switch, that is a gap in `Kbd` rather than something to solve at the
-callsite.
-
-**Rows are `Item`, not `ListItem`.** Both land on the same compact metrics —
-4px/8px padding — but `Item` carries its own `density` instead of taking it
-from `List` context, so a row keeps its spacing wherever it is put and the
-rail does not depend on the list above it to stay dense. The rows still
-render as `<li>` through `as="li"`, so the rail is still a list to a screen
-reader, and `Item` merges `className`, which is what lets the hover-reveal
-marker keep sitting on the row itself.
-
-**One height, two rules: beside a field, or inside a row.** Everything here
-aligns to 28px — the menubar, the tool bar, every inspector field, every row
-of the layer rail. Two different things follow from that, and conflating
-them is what makes a panel look untidy.
-
-An action standing _beside_ a field is `IconButton size="sm"`, and its 28px
-box is the whole point: the clear, the rotate pair, the per-side and
-per-corner toggles all end level with the input's top and bottom, so the row
-reads as one band rather than a field with something small floating next to
-it. The colour swatch and the image thumbnail take the same 28px square for
-the same reason — a chip beside a field is still a thing with edges, and its
-edges should be the field's.
-
-An action _inside_ a row is the exception, and the only place anything
-shrinks. A compact row spends 4px above and below, leaving 20px, and the
-smallest `IconButton` is 28px on its own — so a rail built from them
-measures 36px no matter what density says. There is no smaller size to reach
-for; the floor is the component's. The layer rail's lock is therefore a bare
-`<button>` with a 20px hit area (`styles.itemAction`), and the rail measures
-28px. Note what did _not_ change: it is still a `<button>`, so it stays
-keyboard-reachable and announced. It was `Button`'s minimum that had to go,
-not the element.
-
-**Gutters differ by panel, and the swatch borrows the field's corner.** The
-left rail sits at 8px because its rows are the content — a denser gutter
-lets the list read as a list. The inspector sits at 12px, carried by each
-`InspectorSection` rather than by the panel, which is what keeps the rules
-between sections running edge to edge: pad the panel instead and every
-divider insets by the gutter, turning a full-bleed rule into a floating
-line.
-
-The colour chips round to `--radius-element`, the same token an input
-rounds to, not `--radius-inner`. One step tighter sounds like the safer
-choice for a small square, but at 28px beside a 28px field the two curves
-read as different families; matching them is what makes the chip look like
-another control on the row rather than a tile dropped next to one.
-
-Sliders are the one control that should _not_ match. A filter row pairs a
-28px number field with a 20px rail, centred — a slider is a line to aim at,
-not a box to stack, and stretching it to the field's height would read as a
-second input.
-
-**Border, Shadow and Fill are pickers, not text fields.** Each row is now a
-value, a chip that opens a picker, and a clear that only lights up once the
-slot holds something. Astryx has no colour picker to reach for, so the
-popover is assembled from what it does have: a `Popover`, a `TextInput` for
-hex, and a `Slider` for hue.
-
-The hue rail is worth pausing on, because the obvious move is to paint it and
-that would be wrong. A spectrum rail looks like custom work, but the only
-custom thing about it is the gradient — the dragging, the arrow keys, the
-ARIA and the thumb are all just a slider. So it _is_ a `Slider`, with
-`components['slider-track']` in the template's single `defineTheme` carries
-the spectrum. That same theme is mounted narrowly around the hue Slider so
-the nine filter sliders in the panel keep the plain track they should have.
-Reach for the theming target before reaching for a `<div>`; check a component's
-`theming.targets` in its docs first.
-
-Only the saturation/value plane is painted, and only because it is two axes
-at once and no slider is. It carries `role="slider"`, arrow keys, and pointer
-capture — capture being the part worth copying, since without it a fast drag
-out of the plane stops at the edge instead of following the cursor.
-
-The picker holds HSV while it is open even though the layer stores hex. That
-is not redundancy — hex has no hue left once a colour reaches black or
-white, so a picker that round-trips through it loses your place on the rail
-the moment you drag to the bottom of the plane.
-
-Shadow reuses the same popover and adds X, Y, Blur and Spread inside it,
-because a shadow is one thing to set rather than five rows to find. And
-Shadow appears twice on a text layer on purpose: the one in Styles is the
-box's, the one in Text is the type's, and a layer can carry both.
-
-**Enumerable styling is static; only the open-ended values are dynamic.**
-Text transform, decoration, slant and alignment are closed sets, so they
-compile to real classes picked by key (`typeCase`, `typeLine`, `typeSlant`,
-`typeAlign`) rather than to a custom property written on every keystroke.
-Size, line height, colour, stroke and shadow have no such set, so those stay
-a dynamic `styles.type(…)`. Worth splitting rather than making everything
-dynamic: the static half costs nothing at runtime and shows up in devtools
-as a name instead of a variable.
-
-**Filters emit only what is off its neutral point.** Nine filter functions
-that all happen to be no-ops still force the image onto its own composited
-layer, so `filterCss` drops the ones sitting at 0 or 100 and returns `none`
-when they all are.
-
-**The image row's thumbnail opens a picker.** `FileInput` would be the
-obvious component, but it is fixed at the medium element height and this
-inspector is built on a 28px rhythm, so the picker is driven from the
-thumbnail instead and the file input itself stays hidden in the DOM. Choosing
-a file names it in the adjacent field and stops there: a template has no
-upload endpoint, and repainting the artboard from a local object URL would
-show something the template does not ship.
-
-**The canvas tool bar's end gutters match.** The trailing zoom control is a
-ghost, so edge compensation pulls it out to the card's edge to optically align
-its label — correct when the control is alone in a container, but here it left
-8px on the leading end and nothing on the trailing one. The step goes back via
-a wrapper rather than the control's own `xstyle`, because `Selector` passes
-`xstyle` to an inner node and a margin there does not move the field.
-
-**The layer rail is a `TreeList`, grouped by layer kind.** A poster's layers
-are not a flat list — the two text layers belong together and the images
-belong together — and a tree says so structurally instead of relying on sort
-order and the reader's inference. It also buys collapse for documents whose
-layer count outgrows the rail. The rows are supplied as data rather than
-composed, so `TreeList` keeps the disclosure state, the guide lines and the
-roving focus that a hand-rolled tree would have to reimplement; the lock still
-arrives through `endContent`.
-
-The per-row lock reveal survives the move because `TreeListItemData` forwards
-the `className` and `style` from `useContainerReveal` to each row. Groups take
-the frame mark rather than repeating a child's glyph, since a parent is a
-container and not another layer of that kind.
-
-**A tab's close eats into its label rather than widening the tab.** Fading a
-control that still occupies its box costs the name 20px permanently to hold
-room for something usually invisible. The close now collapses to zero width
-at rest and takes its 20px back on hover, so the space belongs to the name
-until it is needed. That requires a set tab width: with content sizing the
-label has nothing to shrink against, and revealing the close would push every
-tab to its right — the strip would reflow under the pointer and the target
-being reached for would move. The reveal is instant. Easing the width means
-the label reflows for the length of the animation, so the name wobbles every
-time the pointer crosses a tab — motion on an affordance that is only ever
-glanced at. The set width holds the longest seeded name _with_ its close
-showing, since the open document never hides one.
-
-**Tabs separate with a 16px rule, dropped either side of the open one.** A
-vertical `Divider` takes its height from the row unless given one, and the
-strip has no columns to divide — it needs the smallest mark that reads as
-"these are separate tabs". Tabs are all one width, so the rule marks a
-boundary rather than sitting midway between two labels, which is also why it
-is dropped next to the open document: that tab already reads as separate by
-its fill, and a rule running into the fill's rounded edge only crowds it. The
-rule is hidden rather than unmounted, so moving the selection does not add or
-remove a flex item and slide the whole strip sideways under the pointer that
-just clicked it. The strip carries no flex gap, since a gap applies on _both_
-sides of a rule and would leave it floating in a channel of its own instead
-of landing on the seam; the tabs have their own inner padding, so butting
-them up costs the labels nothing.
-
-**Tabs have a ceiling, not a fixed width, and the panels fold by width.** A
-tab now sits at its widest and gives ground as documents are added or the
-window narrows, spending the label's slack before truncating and stopping at
-a floor so a crowded strip scrolls rather than grinding every tab down to a
-sliver. The ceiling has to be `width` and not `flex-basis`: a basis does not
-raise an item's max-content contribution, so the strip sizes itself to the
-tabs' _content_ and then squeezes them back under their own basis, leaving
-every tab short even with the bar half empty.
-
-The strip also caps itself, because it sits in `Toolbar`'s start slot and
-that is not the slot built to give way — only the centre slot carries
-`min-width: 0`, so a start slot grows to its content and pushes the bar wider
-instead of squeezing. Widening the start slot in core would change every
-toolbar to suit one page's tab strip, so the cap is local: bar width less the
-room the menu button and the trailing save/export group need, measured in
-`cqw` against the header so it tracks the bar rather than the window. The
-new-document button moved out of the strip on the way — it is not one of the
-open documents the group is named for, and inside a scrolling strip it would
-be the first thing to scroll out of reach.
-
-The two side panels fold away below a width rather than being switched off:
-the View menu's toggles record what the user asked for, so a panel that
-vanished for room comes back on its own when the window grows. The inspector
-goes first, being the wider of the two and the one you can work without; the
-rail follows later, since knowing what is on the canvas outlasts being able
-to adjust it. Each resize handle folds with its panel, or a grip is left
-behind on a seam with nothing on the other side.
-
-**The header bar sits at 4px, not 8.** Two paddings were stacking: the
-toolbar's own gutter plus the tab strip's, putting 12px above a 28px tab and
-a 53px bar over the canvas. The bar is app chrome, so it takes the tighter
-gutter and the strip keeps its 4px, which lands the header at 45px. Note the
-floor while you are in here — `Toolbar` sets `min-height: --size-element-sm`
-and a tab is that same 28px, so no padding gets the bar below 37px.
-
-**Export is a ghost trigger.** A filled primary put the page's heaviest mark
-on the one control that is not the work — the canvas is, and the bar around
-it should stay chrome. Ghost also lets the toolbar's edge compensation do its
-job: it pulls a ghost trigger out by its own padding, so the icon lands on
-the header's gutter while the hover box still bleeds past it.
-
-**The image row's trigger is a `Thumbnail`, not a button wrapping an `img`.**
-The component already carries what the hand-rolled version was re-deriving:
-button semantics and a hover overlay from `onClick`, an accessible name and
-tooltip from `label`, and the same `--radius-element` the colour swatches
-use. It ships at 64px for media grids, so it takes a width override to join a
-row of 28px controls; the picture stays square on its own aspect ratio, so
-the height needs no help.
-
-**Icons in the rail share one colour, and unselected tabs dim whole.** Every
-rail glyph, and the strip's new-document `+`, now resolves to the secondary
-_icon_ token. That token and its
-text counterpart agree at the theme root but diverge under this editor's
-theme, so a lock keyed to the text ramp came out darker than the layer glyphs
-on its own row. Tabs dim their icon alongside their label; dimming the label
-alone left the icon at full strength and read as half-active.
-
-**An open document tab is an `Item`, and the strip is an `HStack`.** A tab
-was a `div` painting chrome around a `button` and a `span`, with its own
-radius, fill, height, gap, padding and ellipsis. It is the same object as a
-layer row — a name with a mark in front and an action behind — so it is now
-the same component, and all of that comes from `Item`: `density="compact"`
-gives the 28px box, `isSelected` the fill, `startContent` and `endContent`
-the file mark and the close, and a string `label` ellipsizes on its own.
-`Item` also ignores a click that lands on a nested button, which is what
-keeps the close from switching to the document it closes. The strip's flex,
-gap, padding, scroll and cap are all `HStack` props now.
-
-Not `TabList`, which is the component the name suggests: a `Tab` marks the
-open one with an underline rather than a fill, sizes itself to its label with
-no way to cap it from outside, and keeps both of those in spans an `xstyle`
-cannot reach.
-
-Two things stayed local. The width ceiling, because the strip sits in
-`Toolbar`'s start slot and that slot grows to its content. And the selected
-fill, because `Item` marks selection with `--color-accent-muted`, which this
-editor's theme resolves to the exact colour of the header bar in dark — the
-open document would have read as no document at all. `Item` also spaces a
-list row for reading down a column; across a tab those channels cost the name
-six characters, so the measure is tightened back to what the strip had.
-
-**Two wrapper divs went back to the layout components.** The canvas stage is
-an `HStack` — its flex box, its max-content sizing and its 100% floor on the
-block axis are props, leaving only the `min-width` HStack has no prop for.
-The zoom control's wrapper is gone entirely: a div whose only job was one
-margin is a margin the control carries itself.
-
-**A nested row action is a real `IconButton` now.** It was a hand-rolled
-20px `button` because the element scale stops at 28px and a control the
-row's own height would push a 28px row to 36. A `size="sm"` `IconButton`
-pulled in by the row's padding step on every edge lays out as 20px while
-staying 28px to the pointer: the glyph does not move, the row keeps its
-height, and the target grows to what a pointer expects. No tooltip on these
-— a bubble opening off a 28px row covers the row above it, and a padlock and
-an × already say what they do.
-
-A note if you wire the Appearance menu to a Theme of your own: a nested Theme
-recolours text but does not repaint the page behind transparent panels, so an
-explicit mode needs a surface — here a `Section` wrapping the editor — or the
-new mode's text lands on the host's old background.
diff --git a/.changeset/chat-composer-contracts.md b/.changeset/chat-composer-contracts.md
deleted file mode 100644
index 6d25682c3a..0000000000
--- a/.changeset/chat-composer-contracts.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Keep ChatComposer's public composition contracts aligned: custom inputs now submit the value they supply, disabled default editors expose their state to assistive technology, and an explicitly shown Stop action remains pointer-operable while editing is disabled. (#6398)
-
-@cixzhang
diff --git a/.changeset/chat-composer-drawer-badge-placement-8cq6.md b/.changeset/chat-composer-drawer-badge-placement-8cq6.md
deleted file mode 100644
index a5afe9fd2a..0000000000
--- a/.changeset/chat-composer-drawer-badge-placement-8cq6.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] ChatComposerDrawer: add a `collapsedSummary` composition slot that replaces the complete Collapsed summary anatomy part when provided. Omitting it preserves the existing neutral Badge and label. (#5399)
-@aldentan
diff --git a/.changeset/chat-composer-drawer-hidden-focus.md b/.changeset/chat-composer-drawer-hidden-focus.md
deleted file mode 100644
index 329db5b691..0000000000
--- a/.changeset/chat-composer-drawer-hidden-focus.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Keep collapsed `ChatComposerDrawer` content out of keyboard and assistive-technology navigation, and show the shared focus indicator on its disclosure control. (#6416)
-
-@cixzhang
diff --git a/.changeset/chat-composer-input-observable-edits.md b/.changeset/chat-composer-input-observable-edits.md
deleted file mode 100644
index 2860b45b17..0000000000
--- a/.changeset/chat-composer-input-observable-edits.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Keep programmatic ChatComposerInput edits observable, deliver dropped files through `onFiles`, and let `onPaste` intercept text before default token conversion. (#6419)
-
-@cixzhang
diff --git a/.changeset/chat-composer-token-element-contract.md b/.changeset/chat-composer-token-element-contract.md
deleted file mode 100644
index 9b8b8c4ac2..0000000000
--- a/.changeset/chat-composer-token-element-contract.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Export `ChatComposerTokenElementProps` and forward supported span props and refs from `ChatComposerTokenElement` (#6443).
-
-@cixzhang
diff --git a/.changeset/chat-dictation-button-unsupported-state.md b/.changeset/chat-dictation-button-unsupported-state.md
deleted file mode 100644
index 1261d1b678..0000000000
--- a/.changeset/chat-dictation-button-unsupported-state.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Keep the chat dictation control disabled when speech recognition is unavailable, and preserve theme control over its clipping feedback (#6444).
-
-@cixzhang
diff --git a/.changeset/clip-the-resizable-sidenav-handle-within-the-sid-r265.md b/.changeset/clip-the-resizable-sidenav-handle-within-the-sid-r265.md
deleted file mode 100644
index 213f7becf5..0000000000
--- a/.changeset/clip-the-resizable-sidenav-handle-within-the-sid-r265.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Clip the resizable SideNav handle within the sidebar bounds (#6196)
-@harjothkhara
diff --git a/.changeset/dialog-header-end-content-edge-compensation.md b/.changeset/dialog-header-end-content-edge-compensation.md
deleted file mode 100644
index ad04d0795c..0000000000
--- a/.changeset/dialog-header-end-content-edge-compensation.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] DialogHeader: add end-content edge compensation control (#6465)
-
-DialogHeader now accepts `endContentEdgeCompensation="inline" | "block" | "all"` to select which axes of its existing end-content wrapper receive fixed compensation. Omitting the prop preserves the current automatic compensation whenever the close action renders.
-
-@cixzhang
diff --git a/.changeset/input-floor-ios-only.md b/.changeset/input-floor-ios-only.md
deleted file mode 100644
index ad107c714e..0000000000
--- a/.changeset/input-floor-ios-only.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] scope the 16px text-control font-size floor to iOS with `@supports (-webkit-touch-callout: none)` inside the coarse-pointer query, so Android and touch-screen laptops keep the theme's type scale instead of an inflated 16px (#6085; fixes #6015)
-
-@ManoharPaturi
diff --git a/.changeset/kbd-key-aliases.md b/.changeset/kbd-key-aliases.md
deleted file mode 100644
index 075571ff22..0000000000
--- a/.changeset/kbd-key-aliases.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Kbd: render the `esc` and `return` aliases with the same glyphs and accessible names as `escape` and `enter` (#5657)
-
-This partial fix for #5403 normalizes the two unambiguous aliases already accepted by `useHotkeys`. Kbd now renders `esc` as `Esc` with the accessible name `Escape`, and `return` as `↵` with the accessible name `Enter`. Its lookup tables now also avoid prototype-chain collisions when rendering arbitrary key names. The platform-specific rendering contract for `meta` and display choice for `space` remain unresolved in #5403 pending separate API and design decisions.
-
-@harjothkhara
diff --git a/.changeset/layout-footer-playground-wrapper.md b/.changeset/layout-footer-playground-wrapper.md
deleted file mode 100644
index 51e6e64714..0000000000
--- a/.changeset/layout-footer-playground-wrapper.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] LayoutFooter: add playground wrapper and default children for docsite preview (#6341)
-
-Prevents the properties-tab preview on the docsite from rendering an empty stage by wrapping LayoutFooter inside a Layout scaffold with representative footer content in the footer slot.
-
-@rupesh-kumar-sah
diff --git a/.changeset/markdown-frontmatter.md b/.changeset/markdown-frontmatter.md
deleted file mode 100644
index d7524d88c9..0000000000
--- a/.changeset/markdown-frontmatter.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Markdown: add native typed frontmatter metadata (#6381)
-
-Use `createMarkdownFrontmatter()` from `@astryxdesign/core/Markdown/plugins` to decode a document-start key/value block into typed metadata, keep unfinished streaming metadata hidden, and remove completed metadata syntax from rendered Markdown.
-
-@cixzhang
diff --git a/.changeset/markdown-plugin-core.md b/.changeset/markdown-plugin-core.md
deleted file mode 100644
index 7615316e55..0000000000
--- a/.changeset/markdown-plugin-core.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Markdown: add the core plugin protocol (#6340)
-
-Use `createMarkdownPlugin()` and Markdown's `plugins` prop to compose bounded
-source syntax, immutable typed AST transforms, and extension renderers. Import
-`parseMarkdownAst()` or `parseInlineAst()` from
-`@astryxdesign/core/Markdown/parser` when server code needs the canonical tree.
-The same ordered plugins work with parser entry points and Markdown-derived
-Outline items, while omitted or empty plugin lists preserve existing behavior.
-
-@cixzhang
diff --git a/.changeset/markdown-remark-adapter.md b/.changeset/markdown-remark-adapter.md
deleted file mode 100644
index 85bbc8f40c..0000000000
--- a/.changeset/markdown-remark-adapter.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Markdown: add a limited Remark compatibility adapter (#6345)
-
-Import `createMarkdownRemarkTransform()` from `@astryxdesign/core/Markdown/remark` to run one synchronous transform-only Remark plugin over the documented MDAST subset. Every invocation gets a fresh mutable tree and an isolated file, and each plugin's compatibility is proven by fixtures rather than assumed: async work, parser or compiler plugins, processor state, raw HTML, unsupported nodes, forged positions, and metadata Astryx cannot represent keep the last valid readable document and report one diagnostic. The adapter is a separate entry point, so it stays out of every bundle that does not import it.
-
-@cixzhang
diff --git a/.changeset/markdown-semantic-fence.md b/.changeset/markdown-semantic-fence.md
deleted file mode 100644
index 9792a83709..0000000000
--- a/.changeset/markdown-semantic-fence.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Markdown: add a semantic code-fence transform helper (#6343)
-
-Use `createMarkdownFenceTransform()` to annotate declared fenced-code languages with typed extension data while standard plugin `renderers` own presentation and text projection. `components.code` retains precedence, and declined, missing, or failed proposals preserve Markdown's accessible, copyable `CodeBlock` fallback.
-
-@cixzhang
diff --git a/.changeset/markdown-source-decoration.md b/.changeset/markdown-source-decoration.md
deleted file mode 100644
index ae68168b9c..0000000000
--- a/.changeset/markdown-source-decoration.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Markdown: add an immutable source-decoration helper (#6344)
-
-Use `createMarkdownSourceDecoration()` to attach non-visual metadata to every block a validated UTF-16 source range touches, and `getMarkdownSourceDecorations()` to read it back in a later plugin. It works through `<Markdown>` and Outline with no extra parser options, resolves independently of the order earlier transforms left blocks in, and appears on the settled document rather than on partial streaming chunks, so a decoration never appears and then vanishes. Metadata lives in one versioned Astryx-owned envelope that never merges foreign node data. Rendered output, copyable text, accessible names, heading ids, focus order, navigation, and source provenance are unchanged.
-
-Markdown transforms also got faster, and a plugin now always observes a fully immutable tree — including blocks a Core helper carried over untouched. Core-authored helpers now validate the nodes a caller's callback produced and run on a trusted path that skips the whole-tree validation and freezing applied to plugin-authored output, freezing walks only what a transform changed, a plugin list that contributes no inline syntax no longer costs anything per source character, and the helpers' per-match allocations and rebuilds are gone. The representative three-helper set now adds about 20 percent over an empty pipeline, inside its 25 percent budget, down from roughly 3.3x.
-
-@cixzhang
diff --git a/.changeset/markdown-text-transform.md b/.changeset/markdown-text-transform.md
deleted file mode 100644
index b79b5ea82a..0000000000
--- a/.changeset/markdown-text-transform.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Markdown: add an immutable text-transform helper (#6342)
-
-Use `createMarkdownTextTransform()` to replace matching prose with typed Markdown nodes while preserving links, images, code, math, citations, and existing extension syntax as protected contexts.
-
-@cixzhang
diff --git a/.changeset/powersearch-stale-value-menu.md b/.changeset/powersearch-stale-value-menu.md
deleted file mode 100644
index 1e7c684996..0000000000
--- a/.changeset/powersearch-stale-value-menu.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] PowerSearch: switching the field or operator while the value menu is open now shows the new field's options instead of the old ones. (#6357)
-
-@nynexman4464
diff --git a/.changeset/pressed-state-eight-components.md b/.changeset/pressed-state-eight-components.md
deleted file mode 100644
index 30104afbcb..0000000000
--- a/.changeset/pressed-state-eight-components.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Add pressed feedback to CheckboxInput, Collapsible, Link, Slider, Switch, TabList, RadioList, and unselected SegmentedControl items. Enabled controls paint `--color-overlay-pressed` on their interaction surface during pointer hold or drag; disabled controls and selected SegmentedControl items keep their existing surfaces. (#6380)
-
-@vjeux
diff --git a/.changeset/progressbar-mark-accessibility.md b/.changeset/progressbar-mark-accessibility.md
deleted file mode 100644
index 4a69b61ed6..0000000000
--- a/.changeset/progressbar-mark-accessibility.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Move focusable ProgressBar target marks outside the `progressbar` subtree (#6248)
-@korkt-kim
diff --git a/.changeset/selector-empty-mark-column.md b/.changeset/selector-empty-mark-column.md
deleted file mode 100644
index 97cc0d164f..0000000000
--- a/.changeset/selector-empty-mark-column.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Selector: collapse an option's mark column when its resolved selection indicator renders nothing. (#5619)
-
-Unselected rows using the default check indicator no longer lose label width to an empty wrapper. Selected marks and themed indicators that render an unselected state keep their space at the configured logical edge.
-
-@athz
diff --git a/.changeset/slider-marks-fill-color.md b/.changeset/slider-marks-fill-color.md
deleted file mode 100644
index 410a1871fa..0000000000
--- a/.changeset/slider-marks-fill-color.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Slider marks inside the filled region use the fill color: marks at or behind the thumb in single mode, and marks between the thumbs in range mode, now paint with the accent fill color instead of the default mark color. Marks on the unfilled side are unchanged. (#6455)
-
-@kentonquatman
diff --git a/.changeset/slider-uses-the-track-token-for-unfilled-tick-ma-5nd1.md b/.changeset/slider-uses-the-track-token-for-unfilled-tick-ma-5nd1.md
deleted file mode 100644
index ab13cd09aa..0000000000
--- a/.changeset/slider-uses-the-track-token-for-unfilled-tick-ma-5nd1.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Slider uses the track token for unfilled tick marks so marks and rails stay aligned across themes (#6461)
-@kentonquatman
diff --git a/.changeset/spinner-ios-rotation-wobble.md b/.changeset/spinner-ios-rotation-wobble.md
deleted file mode 100644
index 616b2990e3..0000000000
--- a/.changeset/spinner-ios-rotation-wobble.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Spinner: animate the arc's dash offset instead of rotating the ring, fixing residual wobble on iOS Safari (#6311; fixes #6253)
-
-The earlier fix for #3617 added `willChange: 'transform'` to the rotating `<svg>`, which smooths the rotation's motion but does nothing about how WebKit rasterizes a rotating stroked shape's rounded cap on each frame. Rotating the whole ring still visibly wobbled on iOS Safari.
-
-Animates `stroke-dashoffset` on the stationary arc `<circle>` instead of rotating the `<svg>`, so the shape never rotates and WebKit never re-rasterizes the cap at an intermediate angle. Confirmed against a real iOS Safari device by the issue reporter.
-
-@HelloOjasMutreja
diff --git a/.changeset/table-conditional-overscroll.md b/.changeset/table-conditional-overscroll.md
deleted file mode 100644
index 96966547c0..0000000000
--- a/.changeset/table-conditional-overscroll.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Table: contain overscroll only while its inner viewport can scroll, so a fitting table no longer creates a dead scroll zone in its parent. (#6410)
-
-@cixzhang
diff --git a/.changeset/theme-scope-root-base-font.md b/.changeset/theme-scope-root-base-font.md
deleted file mode 100644
index 5a9778c280..0000000000
--- a/.changeset/theme-scope-root-base-font.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Apply the theme's body font to the theme scope root. Generated theme CSS set `font-family` on headings, paragraphs, and code elements but never established a base font on the page, so components styled with `font-family: inherit` (SideNav items, Buttons) fell back to the browser default serif. The generator now emits `font-family: var(--font-family-body)` on `:scope`, which inherits through the tree. (#6450)
-
-@kentonquatman
diff --git a/.changeset/toggle-button-click-action.md b/.changeset/toggle-button-click-action.md
deleted file mode 100644
index 87d578a2a1..0000000000
--- a/.changeset/toggle-button-click-action.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Keep ToggleButton callbacks synchronous and run pressed Actions through Button’s clickAction pathway, preserving callback cancellation and optimistic pending feedback. Omit the Action pathway for callback-only toggles and value-identified ToggleButtonGroup members, whose selection remains group-owned. (#6463)
-
-@cixzhang
diff --git a/.changeset/toggle-button-member-disabled.md b/.changeset/toggle-button-member-disabled.md
deleted file mode 100644
index 9ad3bcf6b8..0000000000
--- a/.changeset/toggle-button-member-disabled.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[fix] Keep a ToggleButton's own `isDisabled` when its ToggleButtonGroup does not disable anything. The group always supplies an `isDisabled` boolean, so the previous `??` fallback never ran and an enabled group re-enabled a member that had disabled itself — the member selected on click, and a member carrying a `tooltip` stayed operable while looking unavailable. A disabled group still disables every member; it just cannot re-enable one. (#6356)
-
-@cixzhang
diff --git a/.changeset/tree-list-item-classname.md b/.changeset/tree-list-item-classname.md
deleted file mode 100644
index c2b43b903a..0000000000
--- a/.changeset/tree-list-item-classname.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-'@astryxdesign/core': patch
----
-
-[feat] Let a TreeList item carry row styles (#6238)
-@ernestt
-
-`TreeListItemData` gains `xstyle`, `className`, and `style`, applied to the
-item's row element, as the TreeList contract's per-item styling seam requires.
-
-`TreeList` takes rows as data, so nothing previously handed back the row's
-element. That prevents row-scoped primitives such as `useContainerReveal` from
-installing the class and inline custom properties that jointly isolate each
-row's hover and focus state; applying the reveal to the whole tree would expose
-every row action at once.
-
-`Item` already accepts the same row styling props, so a list converting to a
-tree keeps its reveal wiring instead of having to mark the whole tree.
diff --git a/packages/build/CHANGELOG.md b/packages/build/CHANGELOG.md
index 5a495a9c2f..703f9c79f5 100644
--- a/packages/build/CHANGELOG.md
+++ b/packages/build/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/build
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/build/package.json b/packages/build/package.json
index d035c96687..6fb9c6edd6 100644
--- a/packages/build/package.json
+++ b/packages/build/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/build",
- "version": "0.6.2",
+ "version": "0.6.3",
"description": "Build plugins for XDS source builds — babel, PostCSS, and Vite integrations",
"author": "Meta Open Source",
"license": "MIT",
diff --git a/packages/charts/package.json b/packages/charts/package.json
index a5bf6956ac..ff5ab923c5 100644
--- a/packages/charts/package.json
+++ b/packages/charts/package.json
@@ -60,7 +60,7 @@
},
"peerDependencies": {
"@stylexjs/stylex": ">=0.10.0",
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19.0.0",
"react-dom": ">=19.0.0"
},
diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
index d166d6613c..8548869add 100644
--- a/packages/cli/CHANGELOG.md
+++ b/packages/cli/CHANGELOG.md
@@ -1,5 +1,122 @@
# @xds/cli
+# 0.6.3
+
+#### New Features
+
+- Add a Canvas Editor page template (#6237)
+ A layered-artboard workspace: a File/Edit/View/Object/Help menubar over a layer rail and asset library on the left, the artboard centered on a muted backdrop under a floating tool bar that sets zoom, and a property inspector on the right whose fields retarget to the selected layer. Both rails drag to resize.
+
+ The inspector is the substance of it. A text layer gets font, weight, colour, size, line height, letter spacing, horizontal and vertical alignment, slant, decoration, transform, a text shadow and a stroke; an image layer gets fit and the nine CSS filters, each on a number and a rail that move together. Colour anywhere in the panel opens a real picker. Everything that can reach the artboard does — typing in Transform recases the poster, dragging Sepia tints the photograph.
+
+ It fills a gap next to `Tools - Page Editor`. That one composes a document — a palette of blocks dropped into a flow that reflows around them. This one moves objects on a fixed 1080 x 1920 frame, where position and size are coordinates rather than an order, so the inspector reads X/Y/W/H and the canvas needs a zoom control at all.
+
+ Two decisions worth knowing if you copy it:
+
+ **The artboard is themed, not styled.** The template's `canvasEditorTheme` is pinned to `mode="light"` around the artboard, so the poster keeps its palette when the editor around it goes dark. The theme carries what belongs to the poster as a whole — the display face, the leading, the uppercase treatment, the frame margins — and the display face is Anton with a fallback chain through the condensed grotesques that ship with macOS and Windows. The chain puts Impact ahead of Arial Narrow because every face in it is a single-weight black rendered at weight 400, and Arial Narrow at 400 reads thin rather than poster-heavy.
+
+ Size and tracking are deliberately not tokens: they belong to a layer rather than to the poster, so they live on the layer and the inspector edits them live. That split is the line worth copying — theme what the surface owns, leave per-object properties to the object.
+
+ **Zoom is a transform, not a re-layout.** The artboard always lays out at its native size and the frame scales the painted result, which keeps the theme's numbers in artboard pixels — the same numbers the inspector shows — and keeps the poster from reflowing between zoom steps.
+
+ **The menubar is one button, not five.** File/Edit/View/Object/Help became submenus of a single `DropdownMenu`. A menubar spends the top-left on five words that are only read by someone already hunting for a command, and this editor has something better to do with that space: the tabs, which are read constantly. The commands keep their grouping — the bar became the first level of the menu rather than disappearing. The menu takes a `menuWidth` because left to itself it matches its trigger, and the trigger is a 28px icon button: five one-word rows in a column barely wider than the words, with nowhere for the submenu chevrons to sit.
+
+ Five smaller things the template works out, in case you hit the same walls:
+
+ **A field names itself from inside.** Every inspector control is one input with a glyph in its `startIcon` slot — `X`, `Y`, `W`, `H` — rather than an `InputGroup` pairing an addon to a field. It reads as a single control, and the accessible name stops stuttering ("Horizontal position", not "Horizontal position X"). `startIcon` takes an SVG component, so the letters are drawn on the same 24px grid Lucide uses and sit interchangeably beside real icons.
+
+ **One left edge across the panel.** The label column is a set width, but a flex item shrinks before its siblings do, and the fields beside it carry StackItem's min-width reset. Without `flexShrink: 0` on the label column the row spends its shrinkage there, and every field lands on a slightly different edge — which is the one thing an inspector cannot afford.
+
+ **Row actions use the shared reveal primitive.** A layer's lock stays hidden until the row is pointed at or receives keyboard focus. `useContainerReveal` owns the hover, focus, coarse-pointer, and reduced-motion behavior, while `TreeListItemData` forwards the returned row props so every nested row keeps its reveal state isolated.
+
+ **A fixed-height Card scrolls; the artboard has to clip.** Give `Card` a `height` and it becomes a scroll container, which is right for a card holding more copy than fits. The artboard is the opposite case: it lays out at its native 1080 wide at every zoom step and the frame scales the painted result, so its content is deliberately larger than its box and the card would offer 1080px of sideways scroll inside a 432px frame. `overflow: clip` through `xstyle` is the fix, and `clip` over `hidden` because nothing here should scroll at all — including the quiet scroll `hidden` still performs when something inside it takes focus.
+
+ **Concentric corners come out of the padding.** The floating tool bar is a card with one spacing step of padding, so the controls inside it round to the card's radius _less_ that step — written as `calc(var(--radius-container) - var(--spacing-1))` rather than a number, so it still holds if either token moves. An inner corner cut at the same radius as its container reads as a rounder curve crossing a straighter one; matching the difference is what strikes both from the same centre. While you are in there: a vertical `Divider` is `height: 100%`, and a flex row that centres its items gives a percentage height nothing to resolve against, so the rule collapses to zero and the bar silently loses its groups. `alignSelf: stretch` is what gives it a height.
+
+ **The top bar is a `LayoutHeader`, not a `Toolbar`.** It reads like a toolbar and it is not one. A toolbar is a set of peer commands that arrow keys walk across, and the document tabs break that twice: arrowing off a tab landed on that tab's own close button, and a strip of open documents is not a band of tools in the first place. It also fought the padding — a toolbar sizes its gutters for a band heading content, and app chrome wants to sit tighter, which took a `--astryx-section-padding-inline` override and the edge compensation that override republished.
+
+ `LayoutHeader` is the component for the slot, and `padding={1}` settles all of it: 4px on every edge puts the menu button's box exactly where the ghost inset used to pull it, so the glyph lands on the same pixel with nothing pulled back out. Same 45px bar, same 18px glyph centre, same divider — measured before and after — minus a role that was describing the wrong thing. The floating canvas tool bar stays a `Toolbar`, because that one really is a row of peer commands, and it still roves left to right.
+
+ **One icon on three rows is a list nobody reads.** Border, shadow and fill all shipped with the same `Palette` swatch, and the three effect presets in the library shared it too — six rows, one mark, so the column read as one control repeated rather than six different things. Lucide has no `shadow`, `fill` or `padding` icon, so the picks came out of reading the pack rather than guessing at names: `PaintBucket` for fill, `SquareStack` for shadow (two offset squares is a drop shadow), plain `Square` for border, `SquareRoundCorner` for per-corner radius so it stops colliding with the per-side padding button that was also `SquareDashed`. Two things worth knowing if you go looking yourself. Names in that pack can be aliases — `FlipHorizontal` re-exports `square-centerline-dashed-horizontal`, which at 16px is an unreadable dashed box, and the mirrored triangles you actually want are `FlipHorizontal2`. And judge candidates at 16px, not at sketch size: `radius` is a legible corner gauge at 48px and mush at 16.
+
+ X, Y, W and H stay letterforms. They are names, not pictures — no icon distinguishes the horizontal coordinate from the vertical one, and every design tool prints the letters for the same reason.
+
+ **A shortcut is a hint, not a control.** `Kbd` paints one key cap per key, so `⌘N` arrived as two small objects beside the menu item and read as something you could press. Desktop menus print shortcuts as quiet secondary text, which is what these are now — a `Text type="supporting" color="secondary"`, one string, set against the menu's right edge. The cost is platform awareness: `Kbd` resolves `mod` to ⌘ or Ctrl, and it does that through `isApplePlatform`, which core keeps unexported on purpose, so a template that leaves `Kbd` prints macOS glyphs and stops adapting. The `shell-nav` menubar already makes that trade. If you need both the quiet treatment and the platform switch, that is a gap in `Kbd` rather than something to solve at the callsite.
+
+ **Rows are `Item`, not `ListItem`.** Both land on the same compact metrics — 4px/8px padding — but `Item` carries its own `density` instead of taking it from `List` context, so a row keeps its spacing wherever it is put and the rail does not depend on the list above it to stay dense. The rows still render as `<li>` through `as="li"`, so the rail is still a list to a screen reader, and `Item` merges `className`, which is what lets the hover-reveal marker keep sitting on the row itself.
+
+ **One height, two rules: beside a field, or inside a row.** Everything here aligns to 28px — the menubar, the tool bar, every inspector field, every row of the layer rail. Two different things follow from that, and conflating them is what makes a panel look untidy.
+
+ An action standing _beside_ a field is `IconButton size="sm"`, and its 28px box is the whole point: the clear, the rotate pair, the per-side and per-corner toggles all end level with the input's top and bottom, so the row reads as one band rather than a field with something small floating next to it. The colour swatch and the image thumbnail take the same 28px square for the same reason — a chip beside a field is still a thing with edges, and its edges should be the field's.
+
+ An action _inside_ a row is the exception, and the only place anything shrinks. A compact row spends 4px above and below, leaving 20px, and the smallest `IconButton` is 28px on its own — so a rail built from them measures 36px no matter what density says. There is no smaller size to reach for; the floor is the component's. The layer rail's lock is therefore a bare `<button>` with a 20px hit area (`styles.itemAction`), and the rail measures 28px. Note what did _not_ change: it is still a `<button>`, so it stays keyboard-reachable and announced. It was `Button`'s minimum that had to go, not the element.
+
+ **Gutters differ by panel, and the swatch borrows the field's corner.** The left rail sits at 8px because its rows are the content — a denser gutter lets the list read as a list. The inspector sits at 12px, carried by each `InspectorSection` rather than by the panel, which is what keeps the rules between sections running edge to edge: pad the panel instead and every divider insets by the gutter, turning a full-bleed rule into a floating line.
+
+ The colour chips round to `--radius-element`, the same token an input rounds to, not `--radius-inner`. One step tighter sounds like the safer choice for a small square, but at 28px beside a 28px field the two curves read as different families; matching them is what makes the chip look like another control on the row rather than a tile dropped next to one.
+
+ Sliders are the one control that should _not_ match. A filter row pairs a 28px number field with a 20px rail, centred — a slider is a line to aim at, not a box to stack, and stretching it to the field's height would read as a second input.
+
+ **Border, Shadow and Fill are pickers, not text fields.** Each row is now a value, a chip that opens a picker, and a clear that only lights up once the slot holds something. Astryx has no colour picker to reach for, so the popover is assembled from what it does have: a `Popover`, a `TextInput` for hex, and a `Slider` for hue.
+
+ The hue rail is worth pausing on, because the obvious move is to paint it and that would be wrong. A spectrum rail looks like custom work, but the only custom thing about it is the gradient — the dragging, the arrow keys, the ARIA and the thumb are all just a slider. So it _is_ a `Slider`, with `components['slider-track']` in the template's single `defineTheme` carries the spectrum. That same theme is mounted narrowly around the hue Slider so the nine filter sliders in the panel keep the plain track they should have. Reach for the theming target before reaching for a `<div>`; check a component's `theming.targets` in its docs first.
+
+ Only the saturation/value plane is painted, and only because it is two axes at once and no slider is. It carries `role="slider"`, arrow keys, and pointer capture — capture being the part worth copying, since without it a fast drag out of the plane stops at the edge instead of following the cursor.
+
+ The picker holds HSV while it is open even though the layer stores hex. That is not redundancy — hex has no hue left once a colour reaches black or white, so a picker that round-trips through it loses your place on the rail the moment you drag to the bottom of the plane.
+
+ Shadow reuses the same popover and adds X, Y, Blur and Spread inside it, because a shadow is one thing to set rather than five rows to find. And Shadow appears twice on a text layer on purpose: the one in Styles is the box's, the one in Text is the type's, and a layer can carry both.
+
+ **Enumerable styling is static; only the open-ended values are dynamic.** Text transform, decoration, slant and alignment are closed sets, so they compile to real classes picked by key (`typeCase`, `typeLine`, `typeSlant`, `typeAlign`) rather than to a custom property written on every keystroke. Size, line height, colour, stroke and shadow have no such set, so those stay a dynamic `styles.type(…)`. Worth splitting rather than making everything dynamic: the static half costs nothing at runtime and shows up in devtools as a name instead of a variable.
+
+ **Filters emit only what is off its neutral point.** Nine filter functions that all happen to be no-ops still force the image onto its own composited layer, so `filterCss` drops the ones sitting at 0 or 100 and returns `none` when they all are.
+
+ **The image row's thumbnail opens a picker.** `FileInput` would be the obvious component, but it is fixed at the medium element height and this inspector is built on a 28px rhythm, so the picker is driven from the thumbnail instead and the file input itself stays hidden in the DOM. Choosing a file names it in the adjacent field and stops there: a template has no upload endpoint, and repainting the artboard from a local object URL would show something the template does not ship.
+
+ **The canvas tool bar's end gutters match.** The trailing zoom control is a ghost, so edge compensation pulls it out to the card's edge to optically align its label — correct when the control is alone in a container, but here it left 8px on the leading end and nothing on the trailing one. The step goes back via a wrapper rather than the control's own `xstyle`, because `Selector` passes `xstyle` to an inner node and a margin there does not move the field.
+
+ **The layer rail is a `TreeList`, grouped by layer kind.** A poster's layers are not a flat list — the two text layers belong together and the images belong together — and a tree says so structurally instead of relying on sort order and the reader's inference. It also buys collapse for documents whose layer count outgrows the rail. The rows are supplied as data rather than composed, so `TreeList` keeps the disclosure state, the guide lines and the roving focus that a hand-rolled tree would have to reimplement; the lock still arrives through `endContent`.
+
+ The per-row lock reveal survives the move because `TreeListItemData` forwards the `className` and `style` from `useContainerReveal` to each row. Groups take the frame mark rather than repeating a child's glyph, since a parent is a container and not another layer of that kind.
+
+ **A tab's close eats into its label rather than widening the tab.** Fading a control that still occupies its box costs the name 20px permanently to hold room for something usually invisible. The close now collapses to zero width at rest and takes its 20px back on hover, so the space belongs to the name until it is needed. That requires a set tab width: with content sizing the label has nothing to shrink against, and revealing the close would push every tab to its right — the strip would reflow under the pointer and the target being reached for would move. The reveal is instant. Easing the width means the label reflows for the length of the animation, so the name wobbles every time the pointer crosses a tab — motion on an affordance that is only ever glanced at. The set width holds the longest seeded name _with_ its close showing, since the open document never hides one.
+
+ **Tabs separate with a 16px rule, dropped either side of the open one.** A vertical `Divider` takes its height from the row unless given one, and the strip has no columns to divide — it needs the smallest mark that reads as "these are separate tabs". Tabs are all one width, so the rule marks a boundary rather than sitting midway between two labels, which is also why it is dropped next to the open document: that tab already reads as separate by its fill, and a rule running into the fill's rounded edge only crowds it. The rule is hidden rather than unmounted, so moving the selection does not add or remove a flex item and slide the whole strip sideways under the pointer that just clicked it. The strip carries no flex gap, since a gap applies on _both_ sides of a rule and would leave it floating in a channel of its own instead of landing on the seam; the tabs have their own inner padding, so butting them up costs the labels nothing.
+
+ **Tabs have a ceiling, not a fixed width, and the panels fold by width.** A tab now sits at its widest and gives ground as documents are added or the window narrows, spending the label's slack before truncating and stopping at a floor so a crowded strip scrolls rather than grinding every tab down to a sliver. The ceiling has to be `width` and not `flex-basis`: a basis does not raise an item's max-content contribution, so the strip sizes itself to the tabs' _content_ and then squeezes them back under their own basis, leaving every tab short even with the bar half empty.
+
+ The strip also caps itself, because it sits in `Toolbar`'s start slot and that is not the slot built to give way — only the centre slot carries `min-width: 0`, so a start slot grows to its content and pushes the bar wider instead of squeezing. Widening the start slot in core would change every toolbar to suit one page's tab strip, so the cap is local: bar width less the room the menu button and the trailing save/export group need, measured in `cqw` against the header so it tracks the bar rather than the window. The new-document button moved out of the strip on the way — it is not one of the open documents the group is named for, and inside a scrolling strip it would be the first thing to scroll out of reach.
+
+ The two side panels fold away below a width rather than being switched off: the View menu's toggles record what the user asked for, so a panel that vanished for room comes back on its own when the window grows. The inspector goes first, being the wider of the two and the one you can work without; the rail follows later, since knowing what is on the canvas outlasts being able to adjust it. Each resize handle folds with its panel, or a grip is left behind on a seam with nothing on the other side.
+
+ **The header bar sits at 4px, not 8.** Two paddings were stacking: the toolbar's own gutter plus the tab strip's, putting 12px above a 28px tab and a 53px bar over the canvas. The bar is app chrome, so it takes the tighter gutter and the strip keeps its 4px, which lands the header at 45px. Note the floor while you are in here — `Toolbar` sets `min-height: --size-element-sm` and a tab is that same 28px, so no padding gets the bar below 37px.
+
+ **Export is a ghost trigger.** A filled primary put the page's heaviest mark on the one control that is not the work — the canvas is, and the bar around it should stay chrome. Ghost also lets the toolbar's edge compensation do its job: it pulls a ghost trigger out by its own padding, so the icon lands on the header's gutter while the hover box still bleeds past it.
+
+ **The image row's trigger is a `Thumbnail`, not a button wrapping an `img`.** The component already carries what the hand-rolled version was re-deriving: button semantics and a hover overlay from `onClick`, an accessible name and tooltip from `label`, and the same `--radius-element` the colour swatches use. It ships at 64px for media grids, so it takes a width override to join a row of 28px controls; the picture stays square on its own aspect ratio, so the height needs no help.
+
+ **Icons in the rail share one colour, and unselected tabs dim whole.** Every rail glyph, and the strip's new-document `+`, now resolves to the secondary _icon_ token. That token and its text counterpart agree at the theme root but diverge under this editor's theme, so a lock keyed to the text ramp came out darker than the layer glyphs on its own row. Tabs dim their icon alongside their label; dimming the label alone left the icon at full strength and read as half-active.
+
+ **An open document tab is an `Item`, and the strip is an `HStack`.** A tab was a `div` painting chrome around a `button` and a `span`, with its own radius, fill, height, gap, padding and ellipsis. It is the same object as a layer row — a name with a mark in front and an action behind — so it is now the same component, and all of that comes from `Item`: `density="compact"` gives the 28px box, `isSelected` the fill, `startContent` and `endContent` the file mark and the close, and a string `label` ellipsizes on its own. `Item` also ignores a click that lands on a nested button, which is what keeps the close from switching to the document it closes. The strip's flex, gap, padding, scroll and cap are all `HStack` props now.
+
+ Not `TabList`, which is the component the name suggests: a `Tab` marks the open one with an underline rather than a fill, sizes itself to its label with no way to cap it from outside, and keeps both of those in spans an `xstyle` cannot reach.
+
+ Two things stayed local. The width ceiling, because the strip sits in `Toolbar`'s start slot and that slot grows to its content. And the selected fill, because `Item` marks selection with `--color-accent-muted`, which this editor's theme resolves to the exact colour of the header bar in dark — the open document would have read as no document at all. `Item` also spaces a list row for reading down a column; across a tab those channels cost the name six characters, so the measure is tightened back to what the strip had.
+
+ **Two wrapper divs went back to the layout components.** The canvas stage is an `HStack` — its flex box, its max-content sizing and its 100% floor on the block axis are props, leaving only the `min-width` HStack has no prop for. The zoom control's wrapper is gone entirely: a div whose only job was one margin is a margin the control carries itself.
+
+ **A nested row action is a real `IconButton` now.** It was a hand-rolled 20px `button` because the element scale stops at 28px and a control the row's own height would push a 28px row to 36. A `size="sm"` `IconButton` pulled in by the row's padding step on every edge lays out as 20px while staying 28px to the pointer: the glyph does not move, the row keeps its height, and the target grows to what a pointer expects. No tooltip on these — a bubble opening off a 28px row covers the row above it, and a padlock and an × already say what they do.
+
+ A note if you wire the Appearance menu to a Theme of your own: a nested Theme recolours text but does not repaint the page behind transparent panels, so an explicit mode needs a surface — here a `Section` wrapping the editor — or the new mode's text lands on the host's old background.
+
+#### Contributors
+
+Thanks to everyone who contributed to this release:
+
+- @ernestt
+
+---
+
# 0.6.2
#### New Features
diff --git a/packages/cli/package.json b/packages/cli/package.json
index 1c3ed037f5..8eeafcfcc6 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/cli",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "CLI",
"description": "Scaffold projects, browse templates, generate themes, and get agent-ready docs from the command line.",
"author": "Meta Open Source",
diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md
index c5576e2aa8..3a69231907 100644
--- a/packages/core/CHANGELOG.md
+++ b/packages/core/CHANGELOG.md
@@ -1,5 +1,86 @@
# @xds/core
+# 0.6.3
+
+#### New Features
+
+- Show each shared InputClearButton's contextual action label in a tooltip. Clearable inputs now give sighted users the same specific action name already available to assistive technology. (#6354)
+- ChatComposerDrawer: add a `collapsedSummary` composition slot that replaces the complete Collapsed summary anatomy part when provided. Omitting it preserves the existing neutral Badge and label. (#5399)
+- DialogHeader: add end-content edge compensation control (#6465)
+ DialogHeader now accepts `endContentEdgeCompensation="inline" | "block" | "all"` to select which axes of its existing end-content wrapper receive fixed compensation. Omitting the prop preserves the current automatic compensation whenever the close action renders.
+- Markdown: add native typed frontmatter metadata (#6381)
+ Use `createMarkdownFrontmatter()` from `@astryxdesign/core/Markdown/plugins` to decode a document-start key/value block into typed metadata, keep unfinished streaming metadata hidden, and remove completed metadata syntax from rendered Markdown.
+- Markdown: add the core plugin protocol (#6340)
+ Use `createMarkdownPlugin()` and Markdown's `plugins` prop to compose bounded source syntax, immutable typed AST transforms, and extension renderers. Import `parseMarkdownAst()` or `parseInlineAst()` from `@astryxdesign/core/Markdown/parser` when server code needs the canonical tree. The same ordered plugins work with parser entry points and Markdown-derived Outline items, while omitted or empty plugin lists preserve existing behavior.
+- Markdown: add a limited Remark compatibility adapter (#6345)
+ Import `createMarkdownRemarkTransform()` from `@astryxdesign/core/Markdown/remark` to run one synchronous transform-only Remark plugin over the documented MDAST subset. Every invocation gets a fresh mutable tree and an isolated file, and each plugin's compatibility is proven by fixtures rather than assumed: async work, parser or compiler plugins, processor state, raw HTML, unsupported nodes, forged positions, and metadata Astryx cannot represent keep the last valid readable document and report one diagnostic. The adapter is a separate entry point, so it stays out of every bundle that does not import it.
+- Markdown: add a semantic code-fence transform helper (#6343)
+ Use `createMarkdownFenceTransform()` to annotate declared fenced-code languages with typed extension data while standard plugin `renderers` own presentation and text projection. `components.code` retains precedence, and declined, missing, or failed proposals preserve Markdown's accessible, copyable `CodeBlock` fallback.
+- Markdown: add an immutable source-decoration helper (#6344)
+ Use `createMarkdownSourceDecoration()` to attach non-visual metadata to every block a validated UTF-16 source range touches, and `getMarkdownSourceDecorations()` to read it back in a later plugin. It works through `<Markdown>` and Outline with no extra parser options, resolves independently of the order earlier transforms left blocks in, and appears on the settled document rather than on partial streaming chunks, so a decoration never appears and then vanishes. Metadata lives in one versioned Astryx-owned envelope that never merges foreign node data. Rendered output, copyable text, accessible names, heading ids, focus order, navigation, and source provenance are unchanged.
+
+ Markdown transforms also got faster, and a plugin now always observes a fully immutable tree — including blocks a Core helper carried over untouched. Core-authored helpers now validate the nodes a caller's callback produced and run on a trusted path that skips the whole-tree validation and freezing applied to plugin-authored output, freezing walks only what a transform changed, a plugin list that contributes no inline syntax no longer costs anything per source character, and the helpers' per-match allocations and rebuilds are gone. The representative three-helper set now adds about 20 percent over an empty pipeline, inside its 25 percent budget, down from roughly 3.3x.
+
+- Markdown: add an immutable text-transform helper (#6342)
+ Use `createMarkdownTextTransform()` to replace matching prose with typed Markdown nodes while preserving links, images, code, math, citations, and existing extension syntax as protected contexts.
+- Add pressed feedback to CheckboxInput, Collapsible, Link, Slider, Switch, TabList, RadioList, and unselected SegmentedControl items. Enabled controls paint `--color-overlay-pressed` on their interaction surface during pointer hold or drag; disabled controls and selected SegmentedControl items keep their existing surfaces. (#6380)
+- Let a TreeList item carry row styles (#6238)
+ `TreeListItemData` gains `xstyle`, `className`, and `style`, applied to the item's row element, as the TreeList contract's per-item styling seam requires.
+
+ `TreeList` takes rows as data, so nothing previously handed back the row's element. That prevents row-scoped primitives such as `useContainerReveal` from installing the class and inline custom properties that jointly isolate each row's hover and focus state; applying the reveal to the whole tree would expose every row action at once.
+
+ `Item` already accepts the same row styling props, so a list converting to a tree keeps its reveal wiring instead of having to mark the whole tree.
+
+#### Fixes
+
+- Make overflowing BottomSheet text keyboard reachable with a named scroll-body tab stop. Add shared focus-time keyboard delegation to `useScrollableArea`: forward Tab may enter the first native link/button directly, while inputs, composite widgets, and nested scroll owners retain the viewport stop. Reverse traversal skips the delegated viewport; pointer/programmatic focus and content changes never trigger delegation. Sheet scroll containment now applies only while content overflows and uses the shared `contain` policy, which permits native edge feedback. (#6301)
+- Keep ChatComposer's public composition contracts aligned: custom inputs now submit the value they supply, disabled default editors expose their state to assistive technology, and an explicitly shown Stop action remains pointer-operable while editing is disabled. (#6398)
+- Keep collapsed `ChatComposerDrawer` content out of keyboard and assistive-technology navigation, and show the shared focus indicator on its disclosure control. (#6416)
+- Keep programmatic ChatComposerInput edits observable, deliver dropped files through `onFiles`, and let `onPaste` intercept text before default token conversion. (#6419)
+- Export `ChatComposerTokenElementProps` and forward supported span props and refs from `ChatComposerTokenElement` (#6443).
+- Keep the chat dictation control disabled when speech recognition is unavailable, and preserve theme control over its clipping feedback (#6444).
+- Clip the resizable SideNav handle within the sidebar bounds (#6196)
+- scope the 16px text-control font-size floor to iOS with `@supports (-webkit-touch-callout: none)` inside the coarse-pointer query, so Android and touch-screen laptops keep the theme's type scale instead of an inflated 16px (#6085; fixes #6015)
+- Kbd: render the `esc` and `return` aliases with the same glyphs and accessible names as `escape` and `enter` (#5657)
+ This partial fix for #5403 normalizes the two unambiguous aliases already accepted by `useHotkeys`. Kbd now renders `esc` as `Esc` with the accessible name `Escape`, and `return` as `↵` with the accessible name `Enter`. Its lookup tables now also avoid prototype-chain collisions when rendering arbitrary key names. The platform-specific rendering contract for `meta` and display choice for `space` remain unresolved in #5403 pending separate API and design decisions.
+- LayoutFooter: add playground wrapper and default children for docsite preview (#6341)
+ Prevents the properties-tab preview on the docsite from rendering an empty stage by wrapping LayoutFooter inside a Layout scaffold with representative footer content in the footer slot.
+- PowerSearch: switching the field or operator while the value menu is open now shows the new field's options instead of the old ones. (#6357)
+- Move focusable ProgressBar target marks outside the `progressbar` subtree (#6248)
+- Selector: collapse an option's mark column when its resolved selection indicator renders nothing. (#5619)
+ Unselected rows using the default check indicator no longer lose label width to an empty wrapper. Selected marks and themed indicators that render an unselected state keep their space at the configured logical edge.
+- Slider marks inside the filled region use the fill color: marks at or behind the thumb in single mode, and marks between the thumbs in range mode, now paint with the accent fill color instead of the default mark color. Marks on the unfilled side are unchanged. (#6455)
+- Slider uses the track token for unfilled tick marks so marks and rails stay aligned across themes (#6461)
+- Spinner: animate the arc's dash offset instead of rotating the ring, fixing residual wobble on iOS Safari (#6311; fixes #6253)
+ The earlier fix for #3617 added `willChange: 'transform'` to the rotating `<svg>`, which smooths the rotation's motion but does nothing about how WebKit rasterizes a rotating stroked shape's rounded cap on each frame. Rotating the whole ring still visibly wobbled on iOS Safari.
+
+ Animates `stroke-dashoffset` on the stationary arc `<circle>` instead of rotating the `<svg>`, so the shape never rotates and WebKit never re-rasterizes the cap at an intermediate angle. Confirmed against a real iOS Safari device by the issue reporter.
+
+- Table: contain overscroll only while its inner viewport can scroll, so a fitting table no longer creates a dead scroll zone in its parent. (#6410)
+- Apply the theme's body font to the theme scope root. Generated theme CSS set `font-family` on headings, paragraphs, and code elements but never established a base font on the page, so components styled with `font-family: inherit` (SideNav items, Buttons) fell back to the browser default serif. The generator now emits `font-family: var(--font-family-body)` on `:scope`, which inherits through the tree. (#6450)
+- Keep ToggleButton callbacks synchronous and run pressed Actions through Button’s clickAction pathway, preserving callback cancellation and optimistic pending feedback. Omit the Action pathway for callback-only toggles and value-identified ToggleButtonGroup members, whose selection remains group-owned. (#6463)
+- Keep a ToggleButton's own `isDisabled` when its ToggleButtonGroup does not disable anything. The group always supplies an `isDisabled` boolean, so the previous `??` fallback never ran and an enabled group re-enabled a member that had disabled itself — the member selected on click, and a member carrying a `tooltip` stayed operable while looking unavailable. A disabled group still disables every member; it just cannot re-enable one. (#6356)
+
+#### Contributors
+
+Thanks to everyone who contributed to this release:
+
+- @aldentan
+- @athz
+- @cixzhang
+- @ernestt
+- @harjothkhara
+- @HelloOjasMutreja
+- @jiunshinn
+- @kentonquatman
+- @korkt-kim
+- @ManoharPaturi
+- @nynexman4464
+- @rupesh-kumar-sah
+- @vjeux
+
+---
+
# 0.6.2
#### New Features
diff --git a/packages/core/package.json b/packages/core/package.json
index 37b58640ac..e4778b3d63 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/core",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "Astryx Core",
"description": "The component library. Accessible, themeable React components with built-in spacing, dark mode, and StyleX styling.",
"author": "Meta Open Source",
diff --git a/packages/lab/package.json b/packages/lab/package.json
index 15ad0dec76..a5e4aec5c9 100644
--- a/packages/lab/package.json
+++ b/packages/lab/package.json
@@ -59,7 +59,7 @@
},
"peerDependencies": {
"@stylexjs/stylex": ">=0.10.0",
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19.0.0",
"react-dom": ">=19.0.0"
},
diff --git a/packages/richtext/package.json b/packages/richtext/package.json
index 2bddcd0244..677786ed9e 100644
--- a/packages/richtext/package.json
+++ b/packages/richtext/package.json
@@ -63,7 +63,7 @@
},
"peerDependencies": {
"@stylexjs/stylex": ">=0.10.0",
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19.0.0",
"react-dom": ">=19.0.0",
"lexical": "^0.46.0",
diff --git a/packages/themes/butter/CHANGELOG.md b/packages/themes/butter/CHANGELOG.md
index 8fd53fee08..7b1c0441ce 100644
--- a/packages/themes/butter/CHANGELOG.md
+++ b/packages/themes/butter/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-butter
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/themes/butter/package.json b/packages/themes/butter/package.json
index 7a0cb034f2..6930292293 100644
--- a/packages/themes/butter/package.json
+++ b/packages/themes/butter/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-butter",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "Butter Theme",
"private": false,
"description": "Warm, creamy yellows with a friendly blue accent. Playful enough for consumer surfaces, soft enough to stay readable.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/packages/themes/chocolate/CHANGELOG.md b/packages/themes/chocolate/CHANGELOG.md
index f1c65e380f..04bef3e271 100644
--- a/packages/themes/chocolate/CHANGELOG.md
+++ b/packages/themes/chocolate/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-chocolate
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/themes/chocolate/package.json b/packages/themes/chocolate/package.json
index aca6581f91..c6e4e8c1c0 100644
--- a/packages/themes/chocolate/package.json
+++ b/packages/themes/chocolate/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-chocolate",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "Chocolate Theme",
"private": false,
"description": "Warm chocolate theme for Astryx — rich brown palette with Fraunces headings, Albert Sans body, and Lucide icons",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/packages/themes/gothic/CHANGELOG.md b/packages/themes/gothic/CHANGELOG.md
index a2dcf53f01..771eaf1aa3 100644
--- a/packages/themes/gothic/CHANGELOG.md
+++ b/packages/themes/gothic/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-gothic
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/themes/gothic/package.json b/packages/themes/gothic/package.json
index 3a5cd1b405..41010e23cb 100644
--- a/packages/themes/gothic/package.json
+++ b/packages/themes/gothic/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-gothic",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "Gothic Theme",
"private": false,
"description": "Deep blue-grays and a signature display serif. Dramatic and editorial, for surfaces that want to be remembered.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/packages/themes/matcha/CHANGELOG.md b/packages/themes/matcha/CHANGELOG.md
index 2c191d8ffb..1921ac8c89 100644
--- a/packages/themes/matcha/CHANGELOG.md
+++ b/packages/themes/matcha/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-matcha
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/themes/matcha/package.json b/packages/themes/matcha/package.json
index 8362bc6c51..96b4b46264 100644
--- a/packages/themes/matcha/package.json
+++ b/packages/themes/matcha/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-matcha",
- "version": "0.6.2",
+ "version": "0.6.3",
"private": false,
"description": "Earthy greens with a calm, organic feel. Naturalistic and grounded, great for wellness or content-first apps.",
"author": "Meta Open Source",
@@ -51,11 +51,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/packages/themes/neutral/CHANGELOG.md b/packages/themes/neutral/CHANGELOG.md
index 147746d967..874cf1f0b4 100644
--- a/packages/themes/neutral/CHANGELOG.md
+++ b/packages/themes/neutral/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-neutral
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/themes/neutral/package.json b/packages/themes/neutral/package.json
index 43ff1019e4..68ef53a085 100644
--- a/packages/themes/neutral/package.json
+++ b/packages/themes/neutral/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-neutral",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "Neutral Theme",
"private": false,
"description": "Restrained warm grays. Minimal and quiet, so the content stays the focus.",
@@ -53,11 +53,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/packages/themes/probe/package.json b/packages/themes/probe/package.json
index 9f09d6a122..f19c27d83d 100644
--- a/packages/themes/probe/package.json
+++ b/packages/themes/probe/package.json
@@ -23,12 +23,12 @@
"build": "node ../../../scripts/clean-dist.mjs && astryx theme build src/probeTheme.ts -o dist/theme.css --icons-specifier ./registries.mjs && tsup && tsc --project tsconfig.build.json && node ../../../scripts/check-fully-specified.mjs"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
"tsup": "^8.3.0",
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/packages/themes/stone/CHANGELOG.md b/packages/themes/stone/CHANGELOG.md
index 8ba6923f5d..f91a42ecce 100644
--- a/packages/themes/stone/CHANGELOG.md
+++ b/packages/themes/stone/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-stone
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/themes/stone/package.json b/packages/themes/stone/package.json
index 66187c20ff..d3bff073e6 100644
--- a/packages/themes/stone/package.json
+++ b/packages/themes/stone/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-stone",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "Stone Theme",
"private": false,
"description": "Warm stone and slate, earthy and understated, with just enough character to feel handcrafted.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/packages/themes/y2k/CHANGELOG.md b/packages/themes/y2k/CHANGELOG.md
index 84edd2d72c..ec0ca3d4da 100644
--- a/packages/themes/y2k/CHANGELOG.md
+++ b/packages/themes/y2k/CHANGELOG.md
@@ -1,5 +1,9 @@
# @xds/theme-y2k
+# 0.6.3
+
+---
+
# 0.6.2
---
diff --git a/packages/themes/y2k/package.json b/packages/themes/y2k/package.json
index 973bf5f881..9bfaddfa27 100644
--- a/packages/themes/y2k/package.json
+++ b/packages/themes/y2k/package.json
@@ -1,6 +1,6 @@
{
"name": "@astryxdesign/theme-y2k",
- "version": "0.6.2",
+ "version": "0.6.3",
"displayName": "Y2K Theme",
"private": false,
"description": "Hot pinks, lime greens, and Poppins. Bubbly, playful, and unmistakably retro.",
@@ -52,11 +52,11 @@
"lucide-react": "^1.18.0"
},
"peerDependencies": {
- "@astryxdesign/core": "0.6.2",
+ "@astryxdesign/core": "0.6.3",
"react": ">=19"
},
"devDependencies": {
- "@astryxdesign/cli": "0.6.2"
+ "@astryxdesign/cli": "0.6.3"
},
"module": "./dist/source.mjs"
}
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index d140f79d43..2111f4eec4 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -694,7 +694,7 @@ importers:
packages/charts:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../core
'@stylexjs/stylex':
specifier: '>=0.10.0'
@@ -871,7 +871,7 @@ importers:
packages/lab:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../core
'@stylexjs/stylex':
specifier: '>=0.10.0'
@@ -929,7 +929,7 @@ importers:
packages/richtext:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../core
'@stylexjs/stylex':
specifier: '>=0.10.0'
@@ -999,7 +999,7 @@ importers:
packages/themes/butter:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -1009,13 +1009,13 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
packages/themes/chocolate:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -1025,13 +1025,13 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
packages/themes/gothic:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -1041,13 +1041,13 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
packages/themes/matcha:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -1057,13 +1057,13 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
packages/themes/neutral:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -1073,20 +1073,20 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
packages/themes/probe:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
react:
specifier: '>=19'
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
tsup:
specifier: ^8.3.0
@@ -1095,7 +1095,7 @@ importers:
packages/themes/stone:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -1105,13 +1105,13 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
packages/themes/y2k:
dependencies:
'@astryxdesign/core':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../core
lucide-react:
specifier: ^1.18.0
@@ -1121,7 +1121,7 @@ importers:
version: 19.2.7
devDependencies:
'@astryxdesign/cli':
- specifier: 0.6.2
+ specifier: 0.6.3
version: link:../../cli
packages/vega: