@fusion.dev/helix 0.0.0-dev → 0.0.3

package/dist/card/root/card-root.d.ts

@@ -4,9 +4,11 @@ import type { CSSResultGroup } from 'lit';
  * @summary Groups related content and actions into a single surface.
  *
  * @description
- * Regions are slots: `media`, `header`, the default slot for content, and
- * `footer`. An omitted region takes no space, so a card with only content needs
- * no wrapper markup at all.
+ * Regions are bare slots with no wrapper element: `media`, `header`, the default
+ * slot for content, and `footer`. An omitted one occupies no space without the
+ * card having to detect that it is missing, so a card with only content needs no
+ * wrapper markup at all. Style slotted content directly rather than reaching for
+ * a part: a header is whatever element you slotted, not a wrapper around it.
  *
  * `media` runs edge to edge and clips to the card's corners, so an image needs
  * no inset correction. Set `orientation="horizontal"` to move it alongside the
@@ -14,11 +16,6 @@ import type { CSSResultGroup } from 'lit';
  * `media-placement="end"` to put it under the content instead of over it, which
  * is what a chart concluding a card wants.
  *
- * Regions are bare slots with no wrapper element, so an omitted one occupies no
- * space without the card having to detect that it is missing. Style slotted
- * content directly rather than reaching for a part: a header is whatever
- * element you slotted, not a wrapper around it.
- *
  * @since 0.1.0
  * @status stable
  * @category layout
@@ -49,16 +46,40 @@ import type { CSSResultGroup } from 'lit';
  *   `data-card` link raises on hover.
  */
 export declare class HelixCard extends HelixHeadlessCard {
+    /**
+     * What the card is made of.
+     *
+     * **A third axis, and it passes the test the other two answer to.**
+     * `separation` is where the surface ends and `tone` is what it means; both of
+     * those can be true at once with this, an elevated glass card being a
+     * perfectly ordinary thing to want, so it is not a value of either.
+     *
+     * **An attribute rather than a hook, because glass is not one declaration.**
+     * It is a translucent ground *and* a backdrop filter, and either without the
+     * other does nothing: a blur behind an opaque background is invisible, and a
+     * translucent card over an unfiltered page is a smear. `--card-backdrop` on
+     * its own is that trap, a published hook a consumer could set and see nothing
+     * happen. The component owns the pair; a theme owns how strong it is.
+     *
+     * Absent is opaque, per the rule that a reflected property takes no default,
+     * so the stylesheet only describes the departure.
+     *
+     * **The whole axis, not one point of it.** `frosted` is the same pair turned
+     * up, the heavier ground under the heavier blur, for a card that has to stay
+     * readable over a busy page; `transparent` drops both, for one that is
+     * structure and spacing with the page showing through.
+     */
+    material?: 'frosted' | 'glass' | 'transparent';
+    /**
+     * Whether media sits above the content stack or beside it.
+     */
+    orientation?: 'vertical' | 'horizontal';
     /**
      * How the card separates itself from the page.
      *
      * **One value per mechanism, and the theme has the same four.**
      * `ThemeIntent.separation` is `border | fill | shadow | space`, so these are
-     * the component's words for what a theme states as a policy, one to one. It
-     * was `appearance`, which is the library's word for four different questions
-     * and is being retired from all of them: `outlined` on a Card says where the
-     * surface ends and `outlined` on a Button says how much ink, and one word
-     * cannot keep saying both.
+     * the component's words for what a theme states as a policy, one to one.
      *
      * - `outlined` is the default, and a hairline is usually enough. It costs
      *   less attention than a shadow: a screen of shadowed cards reads as a stack
@@ -74,43 +95,12 @@ export declare class HelixCard extends HelixHeadlessCard {
      *   is the surface. For a card inside something already bounded, where a
      *   second box adds a line and no meaning.
      *
-     * **`filled` is new and it closes a hole the engine could already see.**
-     * `plain` clears the ground *and* the edge, so a surface with its own color
-     * and neither edge nor lift was unsayable while being one of the four things
-     * a theme could ask for.
+     * `filled` closes a hole `plain` cannot: `plain` clears the ground *and* the
+     * edge, so a surface with its own color and neither edge nor lift would
+     * otherwise be unsayable while being one of the four things a theme can ask
+     * for.
      */
     separation?: 'elevated' | 'filled' | 'outlined' | 'plain';
-    /**
-     * What the card is made of.
-     *
-     * **A third axis, and it passes the test the other two answer to.**
-     * `separation` is where the surface ends and `tone` is what it means; both of
-     * those can be true at once with this, an elevated glass card being a
-     * perfectly ordinary thing to want, so it is not a value of either.
-     *
-     * **An attribute rather than a hook, because glass is not one declaration.**
-     * It is a translucent ground *and* a backdrop filter, and either without the
-     * other does nothing: a blur behind an opaque background is invisible, and a
-     * translucent card over an unfiltered page is a smear. `--card-backdrop`
-     * shipped on its own for exactly one commit and was that trap, a published
-     * hook a consumer could set and see nothing happen. The component owns the
-     * pair; a theme owns how strong it is.
-     *
-     * Absent is opaque, per the rule that a reflected property takes no default,
-     * so the stylesheet only describes the departure.
-     *
-     * **The whole axis, which it did not used to be.** `glass` shipped alone,
-     * so a card offered one point of a three-point language and said nothing
-     * about the other two. `frosted` is the same pair turned up, the heavier
-     * ground under the heavier blur, for a card that has to stay readable over
-     * a busy page; `transparent` drops both, for one that is structure and
-     * spacing with the page showing through. See 270.
-     */
-    material?: 'frosted' | 'glass' | 'transparent';
-    /**
-     * Whether media sits above the content stack or beside it.
-     */
-    orientation?: 'vertical' | 'horizontal';
     static styles: CSSResultGroup;
 }
 declare global {

package/dist/card/root/card-root.js

@@ -12,9 +12,11 @@ import { styles } from './card-root.css.js';
  * @summary Groups related content and actions into a single surface.
  *
  * @description
- * Regions are slots: `media`, `header`, the default slot for content, and
- * `footer`. An omitted region takes no space, so a card with only content needs
- * no wrapper markup at all.
+ * Regions are bare slots with no wrapper element: `media`, `header`, the default
+ * slot for content, and `footer`. An omitted one occupies no space without the
+ * card having to detect that it is missing, so a card with only content needs no
+ * wrapper markup at all. Style slotted content directly rather than reaching for
+ * a part: a header is whatever element you slotted, not a wrapper around it.
  *
  * `media` runs edge to edge and clips to the card's corners, so an image needs
  * no inset correction. Set `orientation="horizontal"` to move it alongside the
@@ -22,11 +24,6 @@ import { styles } from './card-root.css.js';
  * `media-placement="end"` to put it under the content instead of over it, which
  * is what a chart concluding a card wants.
  *
- * Regions are bare slots with no wrapper element, so an omitted one occupies no
- * space without the card having to detect that it is missing. Style slotted
- * content directly rather than reaching for a part: a header is whatever
- * element you slotted, not a wrapper around it.
- *
  * @since 0.1.0
  * @status stable
  * @category layout
@@ -59,15 +56,15 @@ import { styles } from './card-root.css.js';
 let HelixCard = class HelixCard extends HelixHeadlessCard {
     static { this.styles = styles; }
 };
-__decorate([
-    property({ reflect: true })
-], HelixCard.prototype, "separation", void 0);
 __decorate([
     property({ reflect: true })
 ], HelixCard.prototype, "material", void 0);
 __decorate([
     property({ reflect: true })
 ], HelixCard.prototype, "orientation", void 0);
+__decorate([
+    property({ reflect: true })
+], HelixCard.prototype, "separation", void 0);
 HelixCard = __decorate([
     customElement('helix-card')
 ], HelixCard);

package/dist/carousel/root/carousel-root.css.js

@@ -1,8 +1,6 @@
-// Generated from src/carousel/root/carousel-root.css by `bun run styles`. Do not edit.
+// Generated from src/carousel/root/carousel-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
-display: block;
-
 --_carousel-bleed: var(--carousel-bleed, var(--helix-space-md));
 --_carousel-gap: var(--carousel-gap, var(--helix-space-md));
 --_carousel-per-view: 1;
@@ -314,14 +312,6 @@ margin-inline-start: auto;
 order: 1;
 }
 
-@media (prefers-reduced-motion: reduce) {
-[part="indicator"],
-:host([indicator-placement="inline-start"]) [part="indicator"],
-:host([indicator-placement="inline-end"]) [part="indicator"] {
-transition: none;
-}
-}
-
 :host(:dir(rtl)) [part="previous"] svg,
 :host(:dir(rtl)) [part="next"] svg {
 scale: -1 1;

package/dist/carousel/root/carousel-root.d.ts

@@ -26,25 +26,35 @@ import type { CSSResultGroup } from 'lit';
  */
 export declare class HelixCarousel extends HelixHeadlessCarousel {
     /**
-     * Which side of the slides the dots sit on.
+     * Where along that side the arrows sit. See `indicatorAlign`.
      *
-     * Unset is `block-end`, under them. `block-start` puts them above,
-     * `inline-start` and `inline-end` beside, where a run of dots becomes a
-     * column.
+     * `overlay` answers it too, and the edge there is the whole slide: the bar is
+     * stretched across the picture, so this moves the arrows up and down within
+     * it rather than moving the bar. Centered unless asked otherwise, which is
+     * where an arrow over a photograph belongs.
+     */
+    controlsAlign?: 'center' | 'end' | 'start';
+    /**
+     * Which side of the slides the arrows sit on.
      *
-     * **The sides of the content, not positions along a bar.** This was
-     * `start | center | end`, which answered "where along the row" when the
-     * question is "which edge", and could not say "above" at all. The logical
-     * names rather than `top`/`left`, because the component is already careful
-     * about writing direction everywhere else and an `inline-start` carousel
-     * should put its dots on the right in Arabic without being told.
+     * The same four sides as `indicatorPlacement` and the same default, so a
+     * carousel that moves only one of them keeps the other where it was.
+     * `inline-start` or `inline-end` stacks the arrows into a column, which is
+     * what a vertical track usually wants.
      *
-     * Independent of `controlsPlacement`. Both default to the block end, where
-     * they share the row and split it, dots to the start and arrows to the end.
-     * That is the arrangement the old shared bar gave, arrived at by two defaults
-     * rather than by a rule about the pair, so moving one leaves the other alone.
+     * `overlay` puts them on the slides, at the track's own edges, which is what a
+     * full-bleed carousel wants: the slide is the page and the controls are on it
+     * rather than in a bar beneath it. It carries its own treatment with it, a
+     * surface and a shadow under each arrow, because a glyph drawn straight onto a
+     * photograph is legible against about half of one.
+     *
+     * **It is a value here rather than an axis of its own.** "The controls are
+     * over the content" is the whole of what a `hero` appearance would say, and
+     * the surface, the edge-to-edge arrows and the bar that catches no presses all
+     * follow from it. These two placements are the whole of where a carousel's
+     * chrome can go.
      */
-    indicatorPlacement?: 'block-end' | 'block-start' | 'inline-end' | 'inline-start';
+    controlsPlacement?: 'block-end' | 'block-start' | 'inline-end' | 'inline-start' | 'overlay';
     /**
      * Where along that side the dots sit.
      *
@@ -67,41 +77,27 @@ export declare class HelixCarousel extends HelixHeadlessCarousel {
      * what keeps two items in one grid cell from landing on each other. Beside the
      * slides, and over them, both center instead, because a column there has
      * nothing to split the edge with. Putting both groups on the same edge with
-     * the same alignment does overlap them, and always did: that is what the two
-     * different defaults exist to avoid.
+     * the same alignment overlaps them, which is what the two different defaults
+     * exist to avoid.
      */
     indicatorAlign?: 'center' | 'end' | 'start';
     /**
-     * Which side of the slides the arrows sit on.
-     *
-     * The same four sides as `indicatorPlacement` and the same default, so a
-     * carousel that moves only one of them keeps the other where it was.
-     * `inline-start` or `inline-end` stacks the arrows into a column, which is
-     * what a vertical track usually wants.
+     * Which side of the slides the dots sit on.
      *
-     * `overlay` puts them on the slides, at the track's own edges, which is what a
-     * full-bleed carousel wants: the slide is the page and the controls are on it
-     * rather than in a bar beneath it. It carries its own treatment with it, a
-     * surface and a shadow under each arrow, because a glyph drawn straight onto a
-     * photograph is legible against about half of one.
+     * Unset is `block-end`, under them. `block-start` puts them above,
+     * `inline-start` and `inline-end` beside, where a run of dots becomes a
+     * column.
      *
-     * **That was `appearance="hero"` and did not need to be.** A third axis for
-     * something these two already describe: what `hero` meant was "the controls
-     * are over the content", and the surface, the edge-to-edge arrows and the bar
-     * that catches no presses all followed from it rather than being separate
-     * decisions. One fewer property, and the two axes are now the whole of where
-     * a carousel's chrome can go.
-     */
-    controlsPlacement?: 'block-end' | 'block-start' | 'inline-end' | 'inline-start' | 'overlay';
-    /**
-     * Where along that side the arrows sit. See `indicatorAlign`.
+     * **The sides of the content, not positions along a bar**, and logical names
+     * rather than `top`/`left`: an `inline-start` carousel should put its dots on
+     * the right in Arabic without being told.
      *
-     * `overlay` answers it too, and the edge there is the whole slide: the bar is
-     * stretched across the picture, so this moves the arrows up and down within
-     * it rather than moving the bar. Centered unless asked otherwise, which is
-     * where an arrow over a photograph belongs.
+     * Independent of `controlsPlacement`. Both default to the block end, where
+     * they share the row and split it, dots to the start and arrows to the end,
+     * arrived at by two defaults rather than by a rule about the pair, so moving
+     * one leaves the other alone.
      */
-    controlsAlign?: 'center' | 'end' | 'start';
+    indicatorPlacement?: 'block-end' | 'block-start' | 'inline-end' | 'inline-start';
     static styles: CSSResultGroup;
 }
 declare global {

package/dist/carousel/root/carousel-root.js

@@ -36,17 +36,17 @@ let HelixCarousel = class HelixCarousel extends HelixHeadlessCarousel {
     static { this.styles = styles; }
 };
 __decorate([
-    property({ attribute: 'indicator-placement', reflect: true })
-], HelixCarousel.prototype, "indicatorPlacement", void 0);
-__decorate([
-    property({ attribute: 'indicator-align', reflect: true })
-], HelixCarousel.prototype, "indicatorAlign", void 0);
+    property({ attribute: 'controls-align', reflect: true })
+], HelixCarousel.prototype, "controlsAlign", void 0);
 __decorate([
     property({ attribute: 'controls-placement', reflect: true })
 ], HelixCarousel.prototype, "controlsPlacement", void 0);
 __decorate([
-    property({ attribute: 'controls-align', reflect: true })
-], HelixCarousel.prototype, "controlsAlign", void 0);
+    property({ attribute: 'indicator-align', reflect: true })
+], HelixCarousel.prototype, "indicatorAlign", void 0);
+__decorate([
+    property({ attribute: 'indicator-placement', reflect: true })
+], HelixCarousel.prototype, "indicatorPlacement", void 0);
 HelixCarousel = __decorate([
     customElement('helix-carousel')
 ], HelixCarousel);

package/dist/chat/composer/chat-composer.css.js

@@ -1,4 +1,4 @@
-// Generated from src/chat/composer/chat-composer.css by `bun run styles`. Do not edit.
+// Generated from src/chat/composer/chat-composer.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: block;

package/dist/chat/message/chat-message.css.js

@@ -1,4 +1,4 @@
-// Generated from src/chat/message/chat-message.css by `bun run styles`. Do not edit.
+// Generated from src/chat/message/chat-message.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: block;
@@ -64,12 +64,6 @@ pointer-events: auto;
 }
 }
 
-@media (prefers-reduced-motion: reduce) {
-[part="actions"] {
-transition: none;
-}
-}
-
 [part="actions"] {
 
 --helix-size-control: calc(var(--helix-size-control-sm) - var(--helix-space-2xs));

package/dist/chat/message/chat-message.d.ts

@@ -35,13 +35,10 @@ export declare class HelixChatMessage extends HelixHeadlessChatMessage {
     /**
      * Where the turn's surface ends.
      *
-     * **A bubble is one answer and not the only one, and the category has moved.**
-     * Two people messaging read as two columns of bubbles, which is what the form
-     * has looked like since it existed. An assistant answering does not: the reply
-     * is a paragraph, often a long one with code and lists in it, and every AI
-     * surface worth copying sets it as prose with the reader's own turns in
-     * bubbles beside it. A component that can only draw bubbles cannot render the
-     * conversation most people are now building.
+     * **A bubble is one answer and not the only one.** Two people messaging read
+     * as two columns of bubbles; an assistant answering does not, the reply being
+     * a paragraph with code and lists in it, set as prose with the reader's own
+     * turns in bubbles beside it.
      *
      * - `filled` is the default and is told apart by its own ground, which is the
      *   bubble.
@@ -50,12 +47,10 @@ export declare class HelixChatMessage extends HelixHeadlessChatMessage {
      *   assistant's side of a conversation, and for any turn long enough that a
      *   fill reads as a wall.
      *
-     * **On this tier, because it is where the surface ends and nothing else.**
-     * `check:axes` keeps `separation` off the headless tier for the reason it
-     * keeps every painted axis off it: that tier has no ground to end. The two
-     * values are a subset of the registry's four; `elevated` and `outlined` are
-     * available and neither is a thing a turn should be, a lifted message reading
-     * as a card and an outlined one as an input.
+     * **On this tier**, because `separation` is paint and the headless tier has
+     * no ground to end. The two values are a subset of the registry's four:
+     * `elevated` reads as a card and `outlined` as an input, so neither is a
+     * thing a turn should be.
      */
     separation?: 'filled' | 'plain';
 }

package/dist/chat/root/chat-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/chat/root/chat-root.css by `bun run styles`. Do not edit.
+// Generated from src/chat/root/chat-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: grid;

package/dist/checkbox/root/checkbox-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/checkbox/root/checkbox-root.css by `bun run styles`. Do not edit.
+// Generated from src/checkbox/root/checkbox-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: inline-flex;
@@ -107,13 +107,6 @@ border-color: var(--helix-color-danger);
 background-color: var(--helix-color-danger);
 }
 
-@media (prefers-reduced-motion: reduce) {
-[part="mark"],
-[part="control"] {
-transition: none;
-}
-}
-
 :host(:not(:state(has-label))) [part="label"] {
 display: none;
 }
@@ -163,12 +156,6 @@ margin-block-start: calc(
 );
 }
 
-@media (prefers-reduced-motion: reduce) {
-:host([variant="card"]) [part="field"] {
-transition: none;
-}
-}
-
 @media print {
 :host {
 box-shadow: none;

package/dist/checkbox-group/root/checkbox-group-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/checkbox-group/root/checkbox-group-root.css by `bun run styles`. Do not edit.
+// Generated from src/checkbox-group/root/checkbox-group-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: flex;

package/dist/code/root/code-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/code/root/code-root.css by `bun run styles`. Do not edit.
+// Generated from src/code/root/code-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: inline;
@@ -6,13 +6,15 @@ display: inline;
 
 [part="code"] {
 
-background-color: color-mix(in oklab, var(--helix-color-foreground) 6%, transparent);
+background-color: var(
+--code-background-color,
+color-mix(in oklab, var(--helix-color-foreground) 6%, transparent)
+);
 border-radius: var(--helix-radii-sm);
 
-color: color-mix(
-in oklab,
-var(--helix-color-foreground) 30%,
-var(--helix-color-foreground-muted)
+color: var(
+--code-foreground-color,
+color-mix(in oklab, var(--helix-color-foreground) 30%, var(--helix-color-foreground-muted))
 );
 font-family: var(--helix-font-mono);
 
@@ -23,7 +25,7 @@ padding-inline: var(--code-padding, calc(var(--helix-space-2xs) * 0.5));
 }
 
 @media print {
-:host {
+[part="code"] {
 background-color: transparent;
 box-shadow: none;
 }

package/dist/code/root/code-root.d.ts

@@ -12,6 +12,10 @@ import type { CSSResultGroup } from 'lit';
  * @category typography
  * @documentation https://helix.fusion.dev/components/code
  *
+ * @cssproperty --code-background-color - Fill behind the fragment. Defaults to a 6%
+ * wash of the ink, which composites the same against a light page and a dark one.
+ * @cssproperty --code-foreground-color - The fragment's ink. Defaults to the prose's
+ * own, pulled back towards `foreground-muted`.
  * @cssproperty --code-padding - Space either side of the fragment. Defaults to half
  * of `space-2xs`, which is what keeps a bracket beside the chip rather than a space
  * away from it.

package/dist/code/root/code-root.js

@@ -19,6 +19,10 @@ import { styles } from './code-root.css.js';
  * @category typography
  * @documentation https://helix.fusion.dev/components/code
  *
+ * @cssproperty --code-background-color - Fill behind the fragment. Defaults to a 6%
+ * wash of the ink, which composites the same against a light page and a dark one.
+ * @cssproperty --code-foreground-color - The fragment's ink. Defaults to the prose's
+ * own, pulled back towards `foreground-muted`.
  * @cssproperty --code-padding - Space either side of the fragment. Defaults to half
  * of `space-2xs`, which is what keeps a bracket beside the chip rather than a space
  * away from it.

package/dist/code-block/root/code-block-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/code-block/root/code-block-root.css by `bun run styles`. Do not edit.
+// Generated from src/code-block/root/code-block-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: flex;

package/dist/color-input/root/color-input-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/color-input/root/color-input-root.css by `bun run styles`. Do not edit.
+// Generated from src/color-input/root/color-input-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: block;
@@ -57,7 +57,7 @@ flex: none;
 
 [part="trigger"]:focus-visible {
 outline: var(--helix-size-focus-ring) solid var(--helix-color-focus-ring);
-outline-offset: calc(var(--helix-size-focus-ring) * -1);
+outline-offset: calc(var(--helix-size-focus-offset) * -1);
 }
 
 :host(:disabled) [part="trigger"] {

package/dist/color-input/root/color-input-root.js

@@ -6,10 +6,10 @@ var __decorate = (this && this.__decorate) || function (decorators, target, key,
 };
 import { customElement } from '@fusion.dev/helix-core';
 import { HelixHeadlessColorInput } from '@fusion.dev/helix-headless/color-input';
-/* Side-effect import, because the tier below renders `<helix-slider>` and a
-   custom element registers on import. Inherited from the base along with the
+/* Side-effect import, because the tier below renders `<helix-color-picker>` and
+   a custom element registers on import. Inherited from the base along with the
    template, which is why it has to be restated here: this file has no
-   `<helix-slider>` in it to remind anyone. `check:composed` enforces it. */
+   `<helix-color-picker>` in it to remind anyone. */
 import '../../color-picker/index.js';
 import { styles as fieldStyles } from '../../shared/field/field.css.js';
 import { styles as fieldStackedStyles } from '../../shared/field/field-stacked.css.js';

package/dist/color-picker/root/color-picker-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/color-picker/root/color-picker-root.css by `bun run styles`. Do not edit.
+// Generated from src/color-picker/root/color-picker-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: block;
@@ -250,14 +250,6 @@ inline-size: var(--color-picker-swatch-size, var(--helix-size-icon-loose));
 padding: var(--helix-space-none);
 }
 
-@media (prefers-reduced-motion: reduce) {
-[part="eyedropper"],
-[part="format"],
-[part="value"] {
-transition: none;
-}
-}
-
 @media (prefers-reduced-motion: reduce) {
 
 [part="sample"] {

package/dist/color-picker/root/color-picker-root.js

@@ -6,10 +6,10 @@ var __decorate = (this && this.__decorate) || function (decorators, target, key,
 };
 import { customElement } from '@fusion.dev/helix-core';
 import { HelixHeadlessColorPicker } from '@fusion.dev/helix-headless/color-picker';
-/* Side-effect import, because the tier below renders `<helix-slider>` and a
+/* Side-effect imports, because the tier below renders each of these tags and a
    custom element registers on import. Inherited from the base along with the
-   template, which is why it has to be restated here: this file has no
-   `<helix-slider>` in it to remind anyone. `check:composed` enforces it. */
+   template, which is why they have to be restated here: this file has none of
+   the tags in it to remind anyone. */
 import '../../button/index.js';
 import '../../button-group/index.js';
 import '../../icon/index.js';

package/dist/combobox/root/combobox-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/combobox/root/combobox-root.css by `bun run styles`. Do not edit.
+// Generated from src/combobox/root/combobox-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`:host {
 display: flex;
@@ -121,13 +121,6 @@ inline-size: var(--helix-size-icon);
 scale: 1 -1;
 }
 
-@media (prefers-reduced-motion: reduce) {
-[part="indicator"],
-::slotted([slot="indicator"]) {
-transition: none;
-}
-}
-
 slot[name="start"]::slotted(*),
 slot[name="end"]::slotted(*) {
 --icon-size: var(--helix-size-icon);

package/dist/combobox/root/combobox-root.js

@@ -9,7 +9,7 @@ import { HelixHeadlessCombobox } from '@fusion.dev/helix-headless/combobox';
 /* Side-effect import, because the tier below renders `<helix-listbox>` and a
    custom element registers on import. Inherited from the base along with the
    template, which is why it is restated here: this file has no `<helix-listbox>`
-   in it to remind anyone. `check:composed` enforces it. */
+   in it to remind anyone. */
 import '../../listbox/index.js';
 import '../../tag/index.js';
 import { styles as fieldStyles } from '../../shared/field/field.css.js';

package/dist/command/root/command-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/command/root/command-root.css by `bun run styles`. Do not edit.
+// Generated from src/command/root/command-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`helix-dialog::part(dialog) {
 align-self: start;

package/dist/copy-button/root/copy-button-root.css.js

@@ -1,4 +1,4 @@
-// Generated from src/copy-button/root/copy-button-root.css by `bun run styles`. Do not edit.
+// Generated from src/copy-button/root/copy-button-root.css by `turbo run styles`. Do not edit.
 import { createSheet } from '@fusion.dev/helix-core';
 export const styles = createSheet(`[part="button"] {
 display: inline-grid;