@fusion.dev/helix 0.47.0 → 0.47.1

package/types/jsx.d.ts

@@ -1087,17 +1087,23 @@ are interpolations, so a larger number extrapolates rather than
 exaggerating, and a streak whose length has passed through zero is drawn
 as a bar across the whole frame.
 
-Read by four of the eleven shapes, the ones made of many similar things,
+Read by six of the eleven shapes, the ones made of many similar things,
 whether those are counted or continuous: `streaks`, whose lanes draw a
 speed, a length, a width, a spacing and a weight apiece; `particles`, whose
-motes draw a size, a brightness and a wander; and `rays` and `aurora`, whose
-fan, bundles and folds widen or even out.
-
-Inert on the other seven, for three different reasons. `braid`, `waves` and
-`flow` have a single subject and nothing to vary. `threads` and `lattice`
-are even on purpose, a scatter of strands and a regular structure each being
-what it is because its members do not differ. `caustics` and `fracture` are
-populations this does not reach, which is a gap rather than a refusal. */
+motes draw a size, a brightness and a wander; `rays` and `aurora`, whose
+fan, bundles and folds widen or even out; `caustics`, whose three depths of
+fold close on one scale and one weight while the pool over them flattens to
+an even wash; and `fracture`, whose sites come home to their own cell
+centers, leaving equal territories and no border more contested than
+another.
+
+Inert on the other five, and every one of them a refusal. `braid`, `waves`
+and `flow` have a single subject and nothing to vary. `threads` and
+`lattice` are even on purpose, a scatter of strands and a regular structure
+each being what it is because its members do not differ: `threads` gives
+its seven one amplitude, one thickness, one weight and one frequency on
+the argument that alike is what makes a weave read as woven, and a lattice
+whose cells differed would be a scatter with straight lines in it. */
   variance?: (HelixAura["variance"]) | undefined;
   /** Which form the light takes. Absent is `braid`.
 
@@ -1189,17 +1195,23 @@ are interpolations, so a larger number extrapolates rather than
 exaggerating, and a streak whose length has passed through zero is drawn
 as a bar across the whole frame.
 
-Read by four of the eleven shapes, the ones made of many similar things,
+Read by six of the eleven shapes, the ones made of many similar things,
 whether those are counted or continuous: `streaks`, whose lanes draw a
 speed, a length, a width, a spacing and a weight apiece; `particles`, whose
-motes draw a size, a brightness and a wander; and `rays` and `aurora`, whose
-fan, bundles and folds widen or even out.
-
-Inert on the other seven, for three different reasons. `braid`, `waves` and
-`flow` have a single subject and nothing to vary. `threads` and `lattice`
-are even on purpose, a scatter of strands and a regular structure each being
-what it is because its members do not differ. `caustics` and `fracture` are
-populations this does not reach, which is a gap rather than a refusal. */
+motes draw a size, a brightness and a wander; `rays` and `aurora`, whose
+fan, bundles and folds widen or even out; `caustics`, whose three depths of
+fold close on one scale and one weight while the pool over them flattens to
+an even wash; and `fracture`, whose sites come home to their own cell
+centers, leaving equal territories and no border more contested than
+another.
+
+Inert on the other five, and every one of them a refusal. `braid`, `waves`
+and `flow` have a single subject and nothing to vary. `threads` and
+`lattice` are even on purpose, a scatter of strands and a regular structure
+each being what it is because its members do not differ: `threads` gives
+its seven one amplitude, one thickness, one weight and one frequency on
+the argument that alike is what makes a weave read as woven, and a lattice
+whose cells differed would be a scatter with straight lines in it. */
   "prop:variance"?: (HelixAura["variance"]) | undefined;
   /** Which form the light takes. Absent is `braid`.
 
@@ -2804,6 +2816,27 @@ clamps to the last *slide*, so three of the six indicators point at an
 offset the track has already reached: pressing next walks the dots to the
 end while the slides stop moving a third of the way through.
 
+**The number is published to the styles rather than enumerated by them**,
+as `--carousel-per-view` on the track, which is what keeps a width and a
+count from disagreeing. A sheet can only name a value it wrote a rule for,
+so the styled tier enumerated `per-view="2"` through `5` and called five a
+judgment; above it the pane fell back to one across while this file went on
+counting positions. Measured in Chromium over eight slides, six across gave
+three dots, a pane taking the whole track and five slides reachable only by
+dragging. Written from here there is no ceiling to exceed, and a consumer's
+own sheet reads the same declaration the styled one does. `runEnd` publishes
+its correction the same way and for the same reason.
+
+**On the track and not on the host.** A custom property on the host is a
+reflected attribute by another name: it would arrive on upgrade, and a
+consumer's server markup never had it. Inside the component's own shadow
+root it serializes with the rest of the template on the server, and the
+track's own declaration beats anything a consumer inherits in, so the
+attribute is the one answer to how wide a pane is.
+
+A value the track cannot honor is taken to the nearest one it can, by
+`across`, and both tiers read that rather than this.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -2820,6 +2853,27 @@ clamps to the last *slide*, so three of the six indicators point at an
 offset the track has already reached: pressing next walks the dots to the
 end while the slides stop moving a third of the way through.
 
+**The number is published to the styles rather than enumerated by them**,
+as `--carousel-per-view` on the track, which is what keeps a width and a
+count from disagreeing. A sheet can only name a value it wrote a rule for,
+so the styled tier enumerated `per-view="2"` through `5` and called five a
+judgment; above it the pane fell back to one across while this file went on
+counting positions. Measured in Chromium over eight slides, six across gave
+three dots, a pane taking the whole track and five slides reachable only by
+dragging. Written from here there is no ceiling to exceed, and a consumer's
+own sheet reads the same declaration the styled one does. `runEnd` publishes
+its correction the same way and for the same reason.
+
+**On the track and not on the host.** A custom property on the host is a
+reflected attribute by another name: it would arrive on upgrade, and a
+consumer's server markup never had it. Inside the component's own shadow
+root it serializes with the rest of the template on the server, and the
+track's own declaration beats anything a consumer inherits in, so the
+attribute is the one answer to how wide a pane is.
+
+A value the track cannot honor is taken to the nearest one it can, by
+`across`, and both tiers read that rather than this.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -3035,6 +3089,27 @@ clamps to the last *slide*, so three of the six indicators point at an
 offset the track has already reached: pressing next walks the dots to the
 end while the slides stop moving a third of the way through.
 
+**The number is published to the styles rather than enumerated by them**,
+as `--carousel-per-view` on the track, which is what keeps a width and a
+count from disagreeing. A sheet can only name a value it wrote a rule for,
+so the styled tier enumerated `per-view="2"` through `5` and called five a
+judgment; above it the pane fell back to one across while this file went on
+counting positions. Measured in Chromium over eight slides, six across gave
+three dots, a pane taking the whole track and five slides reachable only by
+dragging. Written from here there is no ceiling to exceed, and a consumer's
+own sheet reads the same declaration the styled one does. `runEnd` publishes
+its correction the same way and for the same reason.
+
+**On the track and not on the host.** A custom property on the host is a
+reflected attribute by another name: it would arrive on upgrade, and a
+consumer's server markup never had it. Inside the component's own shadow
+root it serializes with the rest of the template on the server, and the
+track's own declaration beats anything a consumer inherits in, so the
+attribute is the one answer to how wide a pane is.
+
+A value the track cannot honor is taken to the nearest one it can, by
+`across`, and both tiers read that rather than this.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -3051,6 +3126,27 @@ clamps to the last *slide*, so three of the six indicators point at an
 offset the track has already reached: pressing next walks the dots to the
 end while the slides stop moving a third of the way through.
 
+**The number is published to the styles rather than enumerated by them**,
+as `--carousel-per-view` on the track, which is what keeps a width and a
+count from disagreeing. A sheet can only name a value it wrote a rule for,
+so the styled tier enumerated `per-view="2"` through `5` and called five a
+judgment; above it the pane fell back to one across while this file went on
+counting positions. Measured in Chromium over eight slides, six across gave
+three dots, a pane taking the whole track and five slides reachable only by
+dragging. Written from here there is no ceiling to exceed, and a consumer's
+own sheet reads the same declaration the styled one does. `runEnd` publishes
+its correction the same way and for the same reason.
+
+**On the track and not on the host.** A custom property on the host is a
+reflected attribute by another name: it would arrive on upgrade, and a
+consumer's server markup never had it. Inside the component's own shadow
+root it serializes with the rest of the template on the server, and the
+track's own declaration beats anything a consumer inherits in, so the
+attribute is the one answer to how wide a pane is.
+
+A value the track cannot honor is taken to the nearest one it can, by
+`across`, and both tiers read that rather than this.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -21109,17 +21205,23 @@ export type CustomElements = {
    * exaggerating, and a streak whose length has passed through zero is drawn
    * as a bar across the whole frame.
    *
-   * Read by four of the eleven shapes, the ones made of many similar things,
+   * Read by six of the eleven shapes, the ones made of many similar things,
    * whether those are counted or continuous: `streaks`, whose lanes draw a
    * speed, a length, a width, a spacing and a weight apiece; `particles`, whose
-   * motes draw a size, a brightness and a wander; and `rays` and `aurora`, whose
-   * fan, bundles and folds widen or even out.
-   *
-   * Inert on the other seven, for three different reasons. `braid`, `waves` and
-   * `flow` have a single subject and nothing to vary. `threads` and `lattice`
-   * are even on purpose, a scatter of strands and a regular structure each being
-   * what it is because its members do not differ. `caustics` and `fracture` are
-   * populations this does not reach, which is a gap rather than a refusal.
+   * motes draw a size, a brightness and a wander; `rays` and `aurora`, whose
+   * fan, bundles and folds widen or even out; `caustics`, whose three depths of
+   * fold close on one scale and one weight while the pool over them flattens to
+   * an even wash; and `fracture`, whose sites come home to their own cell
+   * centers, leaving equal territories and no border more contested than
+   * another.
+   *
+   * Inert on the other five, and every one of them a refusal. `braid`, `waves`
+   * and `flow` have a single subject and nothing to vary. `threads` and
+   * `lattice` are even on purpose, a scatter of strands and a regular structure
+   * each being what it is because its members do not differ: `threads` gives
+   * its seven one amplitude, one thickness, one weight and one frequency on
+   * the argument that alike is what makes a weave read as woven, and a lattice
+   * whose cells differed would be a scatter with straight lines in it.
    * - `variant`: Which form the light takes. Absent is `braid`.
    *
    * Reflected because the fallback gradient selects on it, and given no default
@@ -22545,9 +22647,12 @@ export type CustomElements = {
    * browser's own momentum and the controls only have to scroll.
    *
    * Slides take the full track by default. `per-view` fits more than one across,
-   * up to five, and is declared on the tier below because it decides how many
+   * at any count, and is declared on the tier below because it decides how many
    * positions the track has rather than only how wide a slide is,
    * which is what a run of cards wants rather than a run of full-width panels.
+   * This sheet divides the track by the number that tier publishes rather than
+   * enumerating the values it will answer for, so there is no count it silently
+   * draws one across.
    *
    * ## Attributes & Properties
    *
@@ -22678,6 +22783,27 @@ export type CustomElements = {
    * offset the track has already reached: pressing next walks the dots to the
    * end while the slides stop moving a third of the way through.
    *
+   * **The number is published to the styles rather than enumerated by them**,
+   * as `--carousel-per-view` on the track, which is what keeps a width and a
+   * count from disagreeing. A sheet can only name a value it wrote a rule for,
+   * so the styled tier enumerated `per-view="2"` through `5` and called five a
+   * judgment; above it the pane fell back to one across while this file went on
+   * counting positions. Measured in Chromium over eight slides, six across gave
+   * three dots, a pane taking the whole track and five slides reachable only by
+   * dragging. Written from here there is no ceiling to exceed, and a consumer's
+   * own sheet reads the same declaration the styled one does. `runEnd` publishes
+   * its correction the same way and for the same reason.
+   *
+   * **On the track and not on the host.** A custom property on the host is a
+   * reflected attribute by another name: it would arrive on upgrade, and a
+   * consumer's server markup never had it. Inside the component's own shadow
+   * root it serializes with the rest of the template on the server, and the
+   * track's own declaration beats anything a consumer inherits in, so the
+   * attribute is the one answer to how wide a pane is.
+   *
+   * A value the track cannot honor is taken to the nearest one it can, by
+   * `across`, and both tiers read that rather than this.
+   *
    * No default, because it reflects. A reflected property with a value writes
    * its attribute on upgrade, and the host then carries something a consumer's
    * server markup never had, which React reports as a mismatch. The one-across
@@ -22736,6 +22862,7 @@ export type CustomElements = {
    * - `--carousel-block-size`: Height of a vertical track. (default: `undefined`)
    * - `--carousel-gap`: Space between slides. A sheet sets it and the component measures the run with it. (default: `undefined`)
    * - `--carousel-pane`: The size one pane is laid out at. A sheet sets it and the component measures the run with it. (default: `undefined`)
+   * - `--carousel-per-view`: How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`. (default: `undefined`)
    * - `--carousel-run-end`: How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`. (default: `undefined`)
    *
    * ## CSS Parts
@@ -40405,17 +40532,23 @@ export type CustomElementsSolidJs = {
    * exaggerating, and a streak whose length has passed through zero is drawn
    * as a bar across the whole frame.
    *
-   * Read by four of the eleven shapes, the ones made of many similar things,
+   * Read by six of the eleven shapes, the ones made of many similar things,
    * whether those are counted or continuous: `streaks`, whose lanes draw a
    * speed, a length, a width, a spacing and a weight apiece; `particles`, whose
-   * motes draw a size, a brightness and a wander; and `rays` and `aurora`, whose
-   * fan, bundles and folds widen or even out.
-   *
-   * Inert on the other seven, for three different reasons. `braid`, `waves` and
-   * `flow` have a single subject and nothing to vary. `threads` and `lattice`
-   * are even on purpose, a scatter of strands and a regular structure each being
-   * what it is because its members do not differ. `caustics` and `fracture` are
-   * populations this does not reach, which is a gap rather than a refusal.
+   * motes draw a size, a brightness and a wander; `rays` and `aurora`, whose
+   * fan, bundles and folds widen or even out; `caustics`, whose three depths of
+   * fold close on one scale and one weight while the pool over them flattens to
+   * an even wash; and `fracture`, whose sites come home to their own cell
+   * centers, leaving equal territories and no border more contested than
+   * another.
+   *
+   * Inert on the other five, and every one of them a refusal. `braid`, `waves`
+   * and `flow` have a single subject and nothing to vary. `threads` and
+   * `lattice` are even on purpose, a scatter of strands and a regular structure
+   * each being what it is because its members do not differ: `threads` gives
+   * its seven one amplitude, one thickness, one weight and one frequency on
+   * the argument that alike is what makes a weave read as woven, and a lattice
+   * whose cells differed would be a scatter with straight lines in it.
    * - `variant`: Which form the light takes. Absent is `braid`.
    *
    * Reflected because the fallback gradient selects on it, and given no default
@@ -41877,9 +42010,12 @@ export type CustomElementsSolidJs = {
    * browser's own momentum and the controls only have to scroll.
    *
    * Slides take the full track by default. `per-view` fits more than one across,
-   * up to five, and is declared on the tier below because it decides how many
+   * at any count, and is declared on the tier below because it decides how many
    * positions the track has rather than only how wide a slide is,
    * which is what a run of cards wants rather than a run of full-width panels.
+   * This sheet divides the track by the number that tier publishes rather than
+   * enumerating the values it will answer for, so there is no count it silently
+   * draws one across.
    *
    * ## Attributes & Properties
    *
@@ -42010,6 +42146,27 @@ export type CustomElementsSolidJs = {
    * offset the track has already reached: pressing next walks the dots to the
    * end while the slides stop moving a third of the way through.
    *
+   * **The number is published to the styles rather than enumerated by them**,
+   * as `--carousel-per-view` on the track, which is what keeps a width and a
+   * count from disagreeing. A sheet can only name a value it wrote a rule for,
+   * so the styled tier enumerated `per-view="2"` through `5` and called five a
+   * judgment; above it the pane fell back to one across while this file went on
+   * counting positions. Measured in Chromium over eight slides, six across gave
+   * three dots, a pane taking the whole track and five slides reachable only by
+   * dragging. Written from here there is no ceiling to exceed, and a consumer's
+   * own sheet reads the same declaration the styled one does. `runEnd` publishes
+   * its correction the same way and for the same reason.
+   *
+   * **On the track and not on the host.** A custom property on the host is a
+   * reflected attribute by another name: it would arrive on upgrade, and a
+   * consumer's server markup never had it. Inside the component's own shadow
+   * root it serializes with the rest of the template on the server, and the
+   * track's own declaration beats anything a consumer inherits in, so the
+   * attribute is the one answer to how wide a pane is.
+   *
+   * A value the track cannot honor is taken to the nearest one it can, by
+   * `across`, and both tiers read that rather than this.
+   *
    * No default, because it reflects. A reflected property with a value writes
    * its attribute on upgrade, and the host then carries something a consumer's
    * server markup never had, which React reports as a mismatch. The one-across
@@ -42068,6 +42225,7 @@ export type CustomElementsSolidJs = {
    * - `--carousel-block-size`: Height of a vertical track. (default: `undefined`)
    * - `--carousel-gap`: Space between slides. A sheet sets it and the component measures the run with it. (default: `undefined`)
    * - `--carousel-pane`: The size one pane is laid out at. A sheet sets it and the component measures the run with it. (default: `undefined`)
+   * - `--carousel-per-view`: How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`. (default: `undefined`)
    * - `--carousel-run-end`: How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`. (default: `undefined`)
    *
    * ## CSS Parts
@@ -59467,6 +59625,8 @@ export type CustomCssProperties = {
   "--carousel-gap"?: (string) | undefined;
   /** The size one pane is laid out at. A sheet sets it and the component measures the run with it. */
   "--carousel-pane"?: (string) | undefined;
+  /** How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`. */
+  "--carousel-per-view"?: (string) | undefined;
   /** How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`. */
   "--carousel-run-end"?: (string) | undefined;
   /** Fill behind the composer. */

package/types/vue.d.ts

@@ -612,17 +612,23 @@ are interpolations, so a larger number extrapolates rather than
 exaggerating, and a streak whose length has passed through zero is drawn
 as a bar across the whole frame.
 
-Read by four of the eleven shapes, the ones made of many similar things,
+Read by six of the eleven shapes, the ones made of many similar things,
 whether those are counted or continuous: `streaks`, whose lanes draw a
 speed, a length, a width, a spacing and a weight apiece; `particles`, whose
-motes draw a size, a brightness and a wander; and `rays` and `aurora`, whose
-fan, bundles and folds widen or even out.
-
-Inert on the other seven, for three different reasons. `braid`, `waves` and
-`flow` have a single subject and nothing to vary. `threads` and `lattice`
-are even on purpose, a scatter of strands and a regular structure each being
-what it is because its members do not differ. `caustics` and `fracture` are
-populations this does not reach, which is a gap rather than a refusal. */
+motes draw a size, a brightness and a wander; `rays` and `aurora`, whose
+fan, bundles and folds widen or even out; `caustics`, whose three depths of
+fold close on one scale and one weight while the pool over them flattens to
+an even wash; and `fracture`, whose sites come home to their own cell
+centers, leaving equal territories and no border more contested than
+another.
+
+Inert on the other five, and every one of them a refusal. `braid`, `waves`
+and `flow` have a single subject and nothing to vary. `threads` and
+`lattice` are even on purpose, a scatter of strands and a regular structure
+each being what it is because its members do not differ: `threads` gives
+its seven one amplitude, one thickness, one weight and one frequency on
+the argument that alike is what makes a weave read as woven, and a lattice
+whose cells differed would be a scatter with straight lines in it. */
   variance?: (HelixAura["variance"]) | undefined;
   /** Which form the light takes. Absent is `braid`.
 
@@ -1534,6 +1540,27 @@ clamps to the last *slide*, so three of the six indicators point at an
 offset the track has already reached: pressing next walks the dots to the
 end while the slides stop moving a third of the way through.
 
+**The number is published to the styles rather than enumerated by them**,
+as `--carousel-per-view` on the track, which is what keeps a width and a
+count from disagreeing. A sheet can only name a value it wrote a rule for,
+so the styled tier enumerated `per-view="2"` through `5` and called five a
+judgment; above it the pane fell back to one across while this file went on
+counting positions. Measured in Chromium over eight slides, six across gave
+three dots, a pane taking the whole track and five slides reachable only by
+dragging. Written from here there is no ceiling to exceed, and a consumer's
+own sheet reads the same declaration the styled one does. `runEnd` publishes
+its correction the same way and for the same reason.
+
+**On the track and not on the host.** A custom property on the host is a
+reflected attribute by another name: it would arrive on upgrade, and a
+consumer's server markup never had it. Inside the component's own shadow
+root it serializes with the rest of the template on the server, and the
+track's own declaration beats anything a consumer inherits in, so the
+attribute is the one answer to how wide a pane is.
+
+A value the track cannot honor is taken to the nearest one it can, by
+`across`, and both tiers read that rather than this.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -1550,6 +1577,27 @@ clamps to the last *slide*, so three of the six indicators point at an
 offset the track has already reached: pressing next walks the dots to the
 end while the slides stop moving a third of the way through.
 
+**The number is published to the styles rather than enumerated by them**,
+as `--carousel-per-view` on the track, which is what keeps a width and a
+count from disagreeing. A sheet can only name a value it wrote a rule for,
+so the styled tier enumerated `per-view="2"` through `5` and called five a
+judgment; above it the pane fell back to one across while this file went on
+counting positions. Measured in Chromium over eight slides, six across gave
+three dots, a pane taking the whole track and five slides reachable only by
+dragging. Written from here there is no ceiling to exceed, and a consumer's
+own sheet reads the same declaration the styled one does. `runEnd` publishes
+its correction the same way and for the same reason.
+
+**On the track and not on the host.** A custom property on the host is a
+reflected attribute by another name: it would arrive on upgrade, and a
+consumer's server markup never had it. Inside the component's own shadow
+root it serializes with the rest of the template on the server, and the
+track's own declaration beats anything a consumer inherits in, so the
+attribute is the one answer to how wide a pane is.
+
+A value the track cannot honor is taken to the nearest one it can, by
+`across`, and both tiers read that rather than this.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -10577,6 +10625,8 @@ export type CustomCssProperties = {
   "--carousel-gap"?: (string) | undefined;
   /** The size one pane is laid out at. A sheet sets it and the component measures the run with it. */
   "--carousel-pane"?: (string) | undefined;
+  /** How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`. */
+  "--carousel-per-view"?: (string) | undefined;
   /** How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`. */
   "--carousel-run-end"?: (string) | undefined;
   /** Fill behind the composer. */
@@ -11569,7 +11619,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixCardVueProps,
     HelixCardVueEvents
   >;
-  /** The track scroll-snaps, so a drag and a trackpad swipe move it with the browser's own momentum and the controls only have to scroll.  Slides take the full track by default. 'per-view' fits more than one across, up to five, and is declared on the tier below because it decides how many positions the track has rather than only how wide a slide is, which is what a run of cards wants rather than a run of full-width panels. */
+  /** The track scroll-snaps, so a drag and a trackpad swipe move it with the browser's own momentum and the controls only have to scroll.  Slides take the full track by default. 'per-view' fits more than one across, at any count, and is declared on the tier below because it decides how many positions the track has rather than only how wide a slide is, which is what a run of cards wants rather than a run of full-width panels. This sheet divides the track by the number that tier publishes rather than enumerating the values it will answer for, so there is no count it silently draws one across. */
   "helix-carousel": DefineCustomElement<
     HelixCarousel,
     HelixCarouselVueProps,