@fusion.dev/helix-headless 0.26.0 → 0.30.0

package/types/vue.d.ts

@@ -478,6 +478,15 @@ Used for the label and the initials. */
 
 Falls back to the slot, or to initials, if it fails. */
   src?: (HelixHeadlessAvatar["src"]) | undefined;
+  /** Where the image stands: still on its way, arrived, or failed and replaced
+by the initials.
+
+Read-only to a consumer: it is a report rather than a setting, and the same
+report `Image` gives, for the same reason. `load` and `error` fire once, so
+a listener bound after the picture settled hears neither, which is the
+platform on an `<img>` too, and this is what that listener asks instead.
+Mirrored to `data-status` rather than reflected, as `Image` explains. */
+  status?: (HelixHeadlessAvatar["status"]) | undefined;
 };
 
 export type HelixHeadlessAvatarVueEvents = {
@@ -928,7 +937,7 @@ way to stop it, so an autoplaying carousel keeps its pause control on a
 touch device exactly as it does on a desktop. */
   controls?: (HelixHeadlessCarousel["controls"]) | undefined;
   /** Slide to start on, where nothing declared one. */
-  "default-index"?: (HelixHeadlessCarousel["defaultIndex"]) | undefined;
+  "default-index"?: (HelixHeadlessCarousel["defaultIndex"] | `${number}`) | undefined;
   /** Slide to start on, where nothing declared one. */
   defaultIndex?: (HelixHeadlessCarousel["defaultIndex"]) | undefined;
   /** How long each slide is held, in milliseconds. */
@@ -965,7 +974,7 @@ 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
 case is the absent attribute, and the styles read it that way. */
-  "per-view"?: (HelixHeadlessCarousel["perView"]) | undefined;
+  "per-view"?: (HelixHeadlessCarousel["perView"] | `${number}`) | undefined;
   /** How many slides are shown across the track at once. Absent shows one.
 
 **Here rather than on the styled tier, because it decides how many places
@@ -1758,7 +1767,7 @@ the resolved state for stylesheets, which is what the mirror is for. */
   /** What the collapsed count is called, since `+3` names nothing. */
   expandLabel?: (HelixHeadlessCombobox["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
-  "max-tags"?: (HelixHeadlessCombobox["maxTags"]) | undefined;
+  "max-tags"?: (HelixHeadlessCombobox["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixHeadlessCombobox["maxTags"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
@@ -2105,11 +2114,11 @@ export type HelixHeadlessDataTableVueProps = {
   /** Column order to open with, where nothing declared one. */
   defaultOrder?: (HelixHeadlessDataTable["defaultOrder"]) | undefined;
   /** Page to open on, where nothing declared one. */
-  "default-page"?: (HelixHeadlessDataTable["defaultPage"]) | undefined;
+  "default-page"?: (HelixHeadlessDataTable["defaultPage"] | `${number}`) | undefined;
   /** Page to open on, where nothing declared one. */
   defaultPage?: (HelixHeadlessDataTable["defaultPage"]) | undefined;
   /** Page size to open with, where nothing declared one. */
-  "default-page-size"?: (HelixHeadlessDataTable["defaultPageSize"]) | undefined;
+  "default-page-size"?: (HelixHeadlessDataTable["defaultPageSize"] | `${number}`) | undefined;
   /** Page size to open with, where nothing declared one. */
   defaultPageSize?: (HelixHeadlessDataTable["defaultPageSize"]) | undefined;
   /** Keys to open with selected, comma separated, where nothing declared any. */
@@ -2216,7 +2225,7 @@ element ever asks for a different page size: a size selector is
 `helix-pagination-size`, which a consumer puts in the `footer` slot and
 answers themselves. Routing this through `requestChange` would announce an
 event the element never has cause to fire. */
-  "page-size"?: (HelixHeadlessDataTable["pageSize"]) | undefined;
+  "page-size"?: (HelixHeadlessDataTable["pageSize"] | `${number}`) | undefined;
   /** How many rows a page holds. Zero is every row, which is what "no paging" means.
 
 **It announces nothing, and that is not an omission.** Nothing in this
@@ -2373,7 +2382,7 @@ submits and what `min` and `max` compare against. */
   /** Days of the week that cannot be chosen, `0` for Sunday through `6`. */
   disableDays?: (HelixHeadlessDateInput["disableDays"]) | undefined;
   /** First column of the week in the calendar, `0` for Sunday through `6`. */
-  "first-day-of-week"?: (HelixHeadlessDateInput["firstDayOfWeek"]) | undefined;
+  "first-day-of-week"?: (HelixHeadlessDateInput["firstDayOfWeek"] | `${number}`) | undefined;
   /** First column of the week in the calendar, `0` for Sunday through `6`. */
   firstDayOfWeek?: (HelixHeadlessDateInput["firstDayOfWeek"]) | undefined;
   /** Language tag the calendar names its months and days in. */
@@ -2396,6 +2405,17 @@ first. The panel is sized by its content, so this widens it. */
   months?: (HelixHeadlessDateInput["months"]) | undefined;
   /** What the field says before a date is in it. */
   placeholder?: (HelixHeadlessDateInput["placeholder"]) | undefined;
+  /** How far apart the selectable dates are, in days.
+
+`<input type="date" step>`'s own unit, handed to the calendar this renders
+so the field and the grid agree about which dates exist. Counted from `min`
+where there is one and from 1 January 1970 where there is not, which is the
+platform's base. */
+  step?: (HelixHeadlessDateInput["step"]) | undefined;
+  /** Accessible name for the control that opens the calendar. */
+  "trigger-label"?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
+  /** Accessible name for the control that opens the calendar. */
+  triggerLabel?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
   /** Whether the control refuses changes while still submitting its value.
 
 **Enforced by refusing every request in one place**, which is the seam this
@@ -2420,17 +2440,6 @@ submits nothing and leaves the tab order, and a read-only one submits its
 value and stays reachable, which is what a form showing a value somebody
 else set needs. */
   readOnly?: (HelixHeadlessDateInput["readOnly"]) | undefined;
-  /** How far apart the selectable dates are, in days.
-
-`<input type="date" step>`'s own unit, handed to the calendar this renders
-so the field and the grid agree about which dates exist. Counted from `min`
-where there is one and from 1 January 1970 where there is not, which is the
-platform's base. */
-  step?: (HelixHeadlessDateInput["step"]) | undefined;
-  /** Accessible name for the control that opens the calendar. */
-  "trigger-label"?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
-  /** Accessible name for the control that opens the calendar. */
-  triggerLabel?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
   /** Whether the element is open.
 
 One property, not two, so `dialog.open` answers the question anyone
@@ -2459,7 +2468,7 @@ the resolved state for stylesheets, which is what the mirror is for. */
   /** What the collapsed count is called, since `+3` names nothing. */
   expandLabel?: (HelixHeadlessDateInput["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
-  "max-tags"?: (HelixHeadlessDateInput["maxTags"]) | undefined;
+  "max-tags"?: (HelixHeadlessDateInput["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixHeadlessDateInput["maxTags"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
@@ -2564,7 +2573,7 @@ export type HelixHeadlessDatePickerVueProps = {
   /** Days of the week that cannot be chosen, comma separated, `0` to `6`. */
   disableDays?: (HelixHeadlessDatePicker["disableDays"]) | undefined;
   /** First column of the week, `0` for Sunday through `6` for Saturday. */
-  "first-day-of-week"?: (HelixHeadlessDatePicker["firstDayOfWeek"]) | undefined;
+  "first-day-of-week"?: (HelixHeadlessDatePicker["firstDayOfWeek"] | `${number}`) | undefined;
   /** First column of the week, `0` for Sunday through `6` for Saturday. */
   firstDayOfWeek?: (HelixHeadlessDatePicker["firstDayOfWeek"]) | undefined;
   /** Whether the current selection fails validation. */
@@ -3166,12 +3175,12 @@ Here rather than on each control. */
 };
 
 export type HelixHeadlessFileInputVueEvents = {
-  /** Announced once the value has moved. */
-  input: HelixHeadlessFileInputElementEvent;
   /** Announced once the value has moved. */
   change: HelixHeadlessFileInputElementEvent;
   /** Fired before the chosen files change, with their names. Cancelable: refusing it takes the decision and nothing moves. */
   "helix-before-change": HelixHeadlessFileInputHelixBeforeChangeElementEvent;
+  /** Announced once the value has moved. */
+  input: HelixHeadlessFileInputElementEvent;
 };
 
 /** `HelixHeadlessFilterChip` component event */
@@ -3407,7 +3416,7 @@ the resolved state for stylesheets, which is what the mirror is for. */
   /** What the collapsed count is called, since `+3` names nothing. */
   expandLabel?: (HelixHeadlessFilterInput["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
-  "max-tags"?: (HelixHeadlessFilterInput["maxTags"]) | undefined;
+  "max-tags"?: (HelixHeadlessFilterInput["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixHeadlessFilterInput["maxTags"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
@@ -3568,7 +3577,7 @@ arithmetic should plan around.
 
 Zero turns the dropping off altogether, which is right for a strip in a
 container that cannot get narrow. */
-  "min-cell"?: (HelixHeadlessHeatmap["minCell"]) | undefined;
+  "min-cell"?: (HelixHeadlessHeatmap["minCell"] | `${number}`) | undefined;
   /** The smallest a cell may get before the strip draws fewer of them, in CSS pixels.
 
 **Set this only to overrule what the strip actually draws.** The arithmetic
@@ -3916,11 +3925,11 @@ is broken. */
   /** What the clear button is called, since an icon has no name of its own. */
   clearLabel?: (HelixHeadlessInput["clearLabel"]) | undefined;
   /** Most characters the value may have. */
-  maxlength?: (HelixHeadlessInput["maxLength"]) | undefined;
+  maxlength?: (HelixHeadlessInput["maxLength"] | `${number}`) | undefined;
   /** Most characters the value may have. */
   maxLength?: (HelixHeadlessInput["maxLength"]) | undefined;
   /** Fewest characters the value may have. */
-  minlength?: (HelixHeadlessInput["minLength"]) | undefined;
+  minlength?: (HelixHeadlessInput["minLength"] | `${number}`) | undefined;
   /** Fewest characters the value may have. */
   minLength?: (HelixHeadlessInput["minLength"]) | undefined;
   /** A regular expression the value has to match, as the platform reads it.
@@ -4440,7 +4449,7 @@ so the controller has to be told not to measure, and that decision is here
 whatever the stylesheet says. Writing the width in both places would be one
 number in two languages, drifting the first time either moved. This sets
 `data-narrow` on the host and the stylesheet arranges itself off that. */
-  "full-below"?: (HelixHeadlessMegamenu["fullBelow"]) | undefined;
+  "full-below"?: (HelixHeadlessMegamenu["fullBelow"] | `${number}`) | undefined;
   /** The width, in pixels, under which a card becomes a band. Zero never does.
 
 A card is a panel hung off one word, and there is no room to hang anything
@@ -4965,7 +4974,7 @@ consumer to ask for it. */
 Ten steps, which is the convention every spinner on the platform follows,
 and a property because ten of a step of `0.01` is a hundredth and rarely
 what a reader wants from a whole key. */
-  "large-step"?: (HelixHeadlessNumberInput["largeStep"]) | undefined;
+  "large-step"?: (HelixHeadlessNumberInput["largeStep"] | `${number}`) | undefined;
   /** How far `PageUp` and `PageDown` move.
 
 Ten steps, which is the convention every spinner on the platform follows,
@@ -5077,7 +5086,7 @@ One by default: the root is open and everything under it closed, so a
 reader sees the shape of the value before its contents. `0` starts with the
 root closed; a large number opens everything, which on a big value is the
 wall of text this exists to avoid. */
-  "default-depth"?: (HelixHeadlessObjectInspector["defaultDepth"]) | undefined;
+  "default-depth"?: (HelixHeadlessObjectInspector["defaultDepth"] | `${number}`) | undefined;
   /** How many levels start open.
 
 One by default: the root is open and everything under it closed, so a
@@ -5302,7 +5311,7 @@ Not reflected, for the reason `ends` is not: it decides what renders, so
 nothing has to select on it. */
   compact?: (HelixHeadlessPagination["compact"]) | undefined;
   /** Page to open on, where nothing declared one. */
-  "default-page"?: (HelixHeadlessPagination["defaultPage"]) | undefined;
+  "default-page"?: (HelixHeadlessPagination["defaultPage"] | `${number}`) | undefined;
   /** Page to open on, where nothing declared one. */
   defaultPage?: (HelixHeadlessPagination["defaultPage"]) | undefined;
   /** Whether to offer a jump to the first and last pages.
@@ -5388,7 +5397,7 @@ so there is never a question of which of two sources is current. */
 Only arithmetic: this does not slice anything, because the component never
 sees the items. It is what turns `total` into a page count, and nothing
 else. */
-  "page-size"?: (HelixHeadlessPagination["pageSize"]) | undefined;
+  "page-size"?: (HelixHeadlessPagination["pageSize"] | `${number}`) | undefined;
   /** How many items are on a page.
 
 Only arithmetic: this does not slice anything, because the component never
@@ -5441,7 +5450,7 @@ export type HelixHeadlessPaginationSizeHelixBeforeChangeElementEvent =
 
 export type HelixHeadlessPaginationSizeVueProps = {
   /** Size to start on, where nothing declared one. */
-  "default-value"?: (HelixHeadlessPaginationSize["defaultValue"]) | undefined;
+  "default-value"?: (HelixHeadlessPaginationSize["defaultValue"] | `${number}`) | undefined;
   /** Size to start on, where nothing declared one. */
   defaultValue?: (HelixHeadlessPaginationSize["defaultValue"]) | undefined;
   /** The size in force.
@@ -5491,7 +5500,7 @@ Absent uses the runtime's own. */
   /** The page on show, one-based. */
   page?: (HelixHeadlessPaginationSummary["page"]) | undefined;
   /** How many items are on a page. */
-  "page-size"?: (HelixHeadlessPaginationSummary["pageSize"]) | undefined;
+  "page-size"?: (HelixHeadlessPaginationSummary["pageSize"] | `${number}`) | undefined;
   /** How many items are on a page. */
   pageSize?: (HelixHeadlessPaginationSummary["pageSize"]) | undefined;
   /** How many items there are across every page. */
@@ -6505,7 +6514,7 @@ Zero by default, which is a pane fully gone. A tab strip or a title bar
 that should survive its own collapse says how much of itself to keep, and
 only whoever put it there knows that, which is the same reason `min` is a
 consumer's to set. */
-  "collapsed-size"?: (HelixHeadlessSplitter["collapsedSize"]) | undefined;
+  "collapsed-size"?: (HelixHeadlessSplitter["collapsedSize"] | `${number}`) | undefined;
   /** How much of a shut pane is still shown, as a percentage.
 
 Zero by default, which is a pane fully gone. A tab strip or a title bar
@@ -6540,7 +6549,7 @@ of a pane during a drag; this is the thing that says the sliver can go. */
   /** Which pane starts shut, where nothing declared it. */
   defaultCollapsed?: (HelixHeadlessSplitter["defaultCollapsed"]) | undefined;
   /** Where the divider starts, where nothing declared it. */
-  "default-position"?: (HelixHeadlessSplitter["defaultPosition"]) | undefined;
+  "default-position"?: (HelixHeadlessSplitter["defaultPosition"] | `${number}`) | undefined;
   /** Where the divider starts, where nothing declared it. */
   defaultPosition?: (HelixHeadlessSplitter["defaultPosition"]) | undefined;
   /** Accessible name for the divider. */
@@ -7121,7 +7130,7 @@ submitted nothing. `ElementInternals` takes a `FormData`, which is how one
 element sends two entries, and that is what this does. */
   dirName?: (HelixHeadlessTextarea["dirName"]) | undefined;
   /** Most characters the value may have. */
-  maxlength?: (HelixHeadlessTextarea["maxLength"]) | undefined;
+  maxlength?: (HelixHeadlessTextarea["maxLength"] | `${number}`) | undefined;
   /** Most characters the value may have. */
   maxLength?: (HelixHeadlessTextarea["maxLength"]) | undefined;
   /** Fewest characters the value may have.
@@ -7130,7 +7139,7 @@ Forwarded to the real `<textarea>` rather than checked here, which is what
 makes the message the browser's and therefore the reader's own language.
 No `pattern`: the platform does not give a textarea one, and inventing it
 would be this library guessing where the point is to stop guessing. */
-  minlength?: (HelixHeadlessTextarea["minLength"]) | undefined;
+  minlength?: (HelixHeadlessTextarea["minLength"] | `${number}`) | undefined;
   /** Fewest characters the value may have.
 
 Forwarded to the real `<textarea>` rather than checked here, which is what
@@ -7261,30 +7270,6 @@ why a wheel cannot do either. */
   mode?: (HelixHeadlessTimeInput["mode"]) | undefined;
   /** What the field says before a time is in it. */
   placeholder?: (HelixHeadlessTimeInput["placeholder"]) | undefined;
-  /** Whether the control refuses changes while still submitting its value.
-
-**Enforced by refusing every request in one place**, which is the seam this
-component already has: `requestValue` is what every path here comes through,
-and gating it once is what stops the next call site from being written
-without the check.
-
-Not `disabled`, which is the confusion worth naming: a disabled control
-submits nothing and leaves the tab order, and a read-only one submits its
-value and stays reachable, which is what a form showing a value somebody
-else set needs. */
-  readonly?: (HelixHeadlessTimeInput["readOnly"]) | undefined;
-  /** Whether the control refuses changes while still submitting its value.
-
-**Enforced by refusing every request in one place**, which is the seam this
-component already has: `requestValue` is what every path here comes through,
-and gating it once is what stops the next call site from being written
-without the check.
-
-Not `disabled`, which is the confusion worth naming: a disabled control
-submits nothing and leaves the tab order, and a read-only one submits its
-value and stays reachable, which is what a form showing a value somebody
-else set needs. */
-  readOnly?: (HelixHeadlessTimeInput["readOnly"]) | undefined;
   /** How far apart the offered times are, in minutes. */
   step?: (HelixHeadlessTimeInput["step"]) | undefined;
   /** Whether the field writes the time out, or holds the value as it is.
@@ -7319,6 +7304,30 @@ not touch, and React reads that as a hydration mismatch. The absent
 attribute *is* the list, which the stylesheet reads as the base rule, so
 only the departure has to be named. */
   variant?: (HelixHeadlessTimeInput["variant"]) | undefined;
+  /** Whether the control refuses changes while still submitting its value.
+
+**Enforced by refusing every request in one place**, which is the seam this
+component already has: `requestValue` is what every path here comes through,
+and gating it once is what stops the next call site from being written
+without the check.
+
+Not `disabled`, which is the confusion worth naming: a disabled control
+submits nothing and leaves the tab order, and a read-only one submits its
+value and stays reachable, which is what a form showing a value somebody
+else set needs. */
+  readonly?: (HelixHeadlessTimeInput["readOnly"]) | undefined;
+  /** Whether the control refuses changes while still submitting its value.
+
+**Enforced by refusing every request in one place**, which is the seam this
+component already has: `requestValue` is what every path here comes through,
+and gating it once is what stops the next call site from being written
+without the check.
+
+Not `disabled`, which is the confusion worth naming: a disabled control
+submits nothing and leaves the tab order, and a read-only one submits its
+value and stays reachable, which is what a form showing a value somebody
+else set needs. */
+  readOnly?: (HelixHeadlessTimeInput["readOnly"]) | undefined;
   /** Whether the element is open.
 
 One property, not two, so `dialog.open` answers the question anyone
@@ -7347,7 +7356,7 @@ the resolved state for stylesheets, which is what the mirror is for. */
   /** What the collapsed count is called, since `+3` names nothing. */
   expandLabel?: (HelixHeadlessTimeInput["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
-  "max-tags"?: (HelixHeadlessTimeInput["maxTags"]) | undefined;
+  "max-tags"?: (HelixHeadlessTimeInput["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixHeadlessTimeInput["maxTags"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
@@ -7891,7 +7900,7 @@ of them, which is noise rather than help. Focus opens with no delay: a
 keyboard reader arriving on a control has already committed to it. */
   delay?: (HelixHeadlessTooltip["delay"]) | undefined;
   /** How long the bubble stays after the pointer leaves, in milliseconds. */
-  "delay-out"?: (HelixHeadlessTooltip["delayOut"]) | undefined;
+  "delay-out"?: (HelixHeadlessTooltip["delayOut"] | `${number}`) | undefined;
   /** How long the bubble stays after the pointer leaves, in milliseconds. */
   delayOut?: (HelixHeadlessTooltip["delayOut"]) | undefined;
   /** Whether the tooltip never shows. */
@@ -8018,7 +8027,7 @@ The shape is `Carousel`'s, which is the nearest thing in the library: a
 `undefined` until somebody sets one. */
   index?: (HelixHeadlessTour["index"]) | undefined;
   /** Stop to start on, where nothing declared one. */
-  "default-index"?: (HelixHeadlessTour["defaultIndex"]) | undefined;
+  "default-index"?: (HelixHeadlessTour["defaultIndex"] | `${number}`) | undefined;
   /** Stop to start on, where nothing declared one. */
   defaultIndex?: (HelixHeadlessTour["defaultIndex"]) | undefined;
   /** Label for the control that goes on from the last stop. */
@@ -8038,7 +8047,7 @@ The shape is `Carousel`'s, which is the nearest thing in the library: a
   /** Label for the control that leaves the tour. */
   skipLabel?: (HelixHeadlessTour["skipLabel"]) | undefined;
   /** Space left around the target when it is lit, in pixels. */
-  "spotlight-padding"?: (HelixHeadlessTour["spotlightPadding"]) | undefined;
+  "spotlight-padding"?: (HelixHeadlessTour["spotlightPadding"] | `${number}`) | undefined;
   /** Space left around the target when it is lit, in pixels. */
   spotlightPadding?: (HelixHeadlessTour["spotlightPadding"]) | undefined;
 };
@@ -8503,7 +8512,7 @@ as long as anyone is likely to look.
 
 The wait is only ever about *idling*. A video that is paused keeps its bar
 regardless, because a reader who stopped it is deciding what to do next. */
-  "idle-delay"?: (HelixHeadlessVideo["idleDelay"]) | undefined;
+  "idle-delay"?: (HelixHeadlessVideo["idleDelay"] | `${number}`) | undefined;
   /** How long the bar waits after the pointer stops before it goes, in ms.
 
 A wait rather than leaving with the pointer, or a reader moving across the
@@ -8787,7 +8796,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessAccordionItemVueProps,
     HelixHeadlessAccordionItemVueEvents
   >;
-  /** Holds the mode and nothing else. The item that was clicked is what coordinates: it walks up to the nearest accordion, reads the mode off it, and closes its peers itself.  Coordination is structural, not a subscription. 'helix-before-open' does not bubble and is not composed, because overlays nest and an inner one's lifecycle must never read as the outer one's, so an accordion cannot learn that a child opened by listening for it.  Membership resolves on demand, so there is no registry to keep in step: an item added a second after render coordinates on its first click.  Items are matched with 'instanceof HelixHeadlessAccordionItem', never by tag name. Matching 'helix-accordion-item' would tie this tier to the styled one.  Every listener is attached on connect, so none of it runs on the server, where there is no tree to walk and no events to hear. */
+  /** Holds the mode and nothing else. The item that was clicked is what coordinates: it walks up to the nearest accordion, reads the mode off it, and closes its peers itself.  Coordination is structural, not a subscription. 'helix-before-open' does not bubble and is not composed, because overlays nest and an inner one's lifecycle must never read as the outer one's, so an accordion cannot learn that a child opened by listening for it.  Membership resolves on demand, so there is no registry to keep in step: an item added a second after render coordinates on its first click.  Items are matched with 'instanceof HelixHeadlessAccordionItem', never by tag name. Matching 'helix-accordion-item' would tie this tier to the styled one.  The keyboard listener is the controller's and is attached on connect, so none of it runs on the server, where there is no tree to walk and no events to hear. */
   "helix-headless-accordion": DefineCustomElement<
     HelixHeadlessAccordion,
     HelixHeadlessAccordionVueProps,
@@ -9039,7 +9048,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessFilterChipVueProps,
     HelixHeadlessFilterChipVueEvents
   >;
-  /** **A declaration, not a control.** It renders nothing and is never seen. A consumer writes one per field, with the comparisons that field supports and the values it supports them on, and the filter input reads them to build its menu:  '''html <helix-headless-filter-field name="disposition" label="Disposition">   <helix-headless-filter-operator name="any" label="is any of" default>   </helix-headless-filter-operator>   <helix-headless-filter-operator name="none" label="is none of">   </helix-headless-filter-operator>   <helix-headless-option value="refunded">Refunded</helix-headless-option> </helix-headless-filter-field> '''  **Operators are per field and never global.** 'is after' belongs to a date and 'has all of' to a set, and a field that supports one comparison shows no chooser at all. A global list would offer every field every word and leave the component deciding which of them made sense, which is the domain question it declines to answer.  **A field that declares none gets two, and they are the ones the punctuation can say.** 'is any of' and 'is none of' are what 'field:a,b' and '-field:a,b' mean, so declaring them was ceremony for the case every product has; the example above is what a consumer writes when the words matter, not the price of admission. Declaring one comparison replaces both rather than joining them — see 'vocabulary', which is where that is decided once for the menu and the grammar together.  **Values are 'Option's, which is the element a consumer already has.** They carry a value, a label and a disabled state, and a picker built on 'Menu' or 'Listbox' can render them without this element inventing a second way to say the same thing. A field whose values cannot be enumerated declares none, and what fills a chip then is whatever the consumer types. */
+  /** **A declaration, not a control.** It renders nothing and is never seen. A consumer writes one per field, with the comparisons that field supports and the values it supports them on, and the filter input reads them to build its menu:  '''html <helix-headless-filter-field name="disposition" label="Disposition">   <helix-headless-filter-operator name="any" label="is any of" default>   </helix-headless-filter-operator>   <helix-headless-filter-operator name="none" label="is none of">   </helix-headless-filter-operator>   <helix-headless-option value="refunded">Refunded</helix-headless-option> </helix-headless-filter-field> '''  **Operators are per field and never global.** 'is after' belongs to a date and 'has all of' to a set, and a field that supports one comparison shows no chooser at all. A global list would offer every field every word and leave the component deciding which of them made sense, which is the domain question it declines to answer.  **A field that declares none gets two, and they are the ones the punctuation can say.** 'is any of' and 'is none of' are what 'field:a,b' and '-field:a,b' mean, so declaring them was ceremony for the case every product has; the example above is what a consumer writes when the words matter, not the price of admission. Declaring one comparison replaces both rather than joining them: see 'vocabulary', which is where that is decided once for the menu and the grammar together.  **Values are 'Option's, which is the element a consumer already has.** They carry a value, a label and a disabled state, and a picker built on 'Menu' or 'Listbox' can render them without this element inventing a second way to say the same thing. A field whose values cannot be enumerated declares none, and what fills a chip then is whatever the consumer types. */
   "helix-headless-filter-field": DefineCustomElement<
     HelixHeadlessFilterField,
     HelixHeadlessFilterFieldVueProps,
@@ -9057,7 +9066,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessFilterOperatorVueProps,
     HelixHeadlessFilterOperatorVueEvents
   >;
-  /** **The tokens are the consumer's own elements, slotted.** What a filter narrows by belongs to the consumer's model rather than to this element: a facet with a prefix, a saved query, a range. So they are slotted rather than rendered from a list of strings, and removing one is a request this element makes rather than a change it applies. Combobox is the other way round, and that is the difference between the two: its tokens are a view of a selection it owns, drawn from options it was handed.  **'value' is the text being typed, not the tokens**, which is what makes this a field a consumer can listen to. Every keystroke announces 'input' with the text on the element, so a table narrows as the reader types. The tokens need no reporting back, being markup the consumer already holds.  Backspace on an empty field asks the last token to go, through the same 'helix-dismiss' its own remove control fires, so a consumer who handled the pointer has already handled the keyboard.  **It reads what was declared, and nothing that was not.** Write 'FilterField's — usually inside the 'FilterMenu' slotted into 'start', so the picker and the text work off one set — and Enter reads the box against them: 'disposition:refunded,settled' and '-disposition:refunded' announce 'helix-facet', exactly as ticking those values in the picker would, and the text they were read from goes. Everything else stays where it was typed, so 'refund tuesday disposition:settled' is a filter and a search at once. 'grammar.ts' carries the whole rule and is worth reading before relying on it; the short version is that Helix owns the punctuation and the consumer owns every word in it. A field with no 'FilterField' in it parses nothing, which is the behavior this had before it could.  **A field whose values cannot be listed belongs here rather than in the picker.** 'assignee:ada' is a filter and nobody wants to enumerate every name in the company, but a menu page for it would have nothing on it to press. Written directly inside this element it is read by the grammar and never offered as a page: unslotted, so nothing draws it, which is the same trick 'FilterField' already plays on its own children.  **It can suggest what to type next, and deciding what to suggest is still the consumer's.** Slot 'helix-option' elements into 'suggestions' and the field shows them, moves through them with the arrows, and lets Enter press one; the option fires its own 'helix-select' and the consumer decides what choosing meant. Keys before a colon and values after it are the same panel with different contents, and 'readFilterText' is exported for a consumer narrowing that panel against what a reader has half typed.  **The panel opens when there is something in it and closes when there is not**, rather than on a choice. A reader who picks a key wants its values next, and closing on the choice would shut the panel between two renders. Use 'selectionStart' and 'setSelectionRange' to write a completion back and put the caret after it, or the next parse reads the wrong term.  **Three things here have three different owners, and only one of them is a controlled property.**  'value' is the text, and it is uncontrolled by default: the reader types, the element applies it, and 'input' says so. **Writing 'value' does not take that over.** It is a seed and a correction, so a consumer who sets it and then expects the field to hold still will watch the next keystroke overwrite them. Ownership is taken by refusing 'helix-before-change' and writing the value you want, which is the same shape every field in this library uses and is worth saying out loud here because the property looks like React's. 'default-value' seeds the field without claiming anything.  'open' is the suggestions panel, and it is the ordinary controlled pair: refuse 'helix-before-open' or 'helix-before-close' to take the decision, and 'default-open' to seed it.  The tokens are neither, because they are not state. They are the consumer's own elements in a slot, so there is nothing for this to own and nothing to report back: a token goes when the consumer removes it from their markup, having been asked by 'helix-dismiss'. **A 'FilterChip' naming a declared field is asked differently**, and it has to be: the picker holds what is ticked, so a chip that removed itself without telling it left the value ticked in a list nobody could see was wrong. That dismissal is answered as the field being filtered by nothing, so it arrives as 'helix-facet' like every other change and the chip goes because the filter went. */
+  /** **The tokens are the consumer's own elements, slotted.** What a filter narrows by belongs to the consumer's model rather than to this element: a facet with a prefix, a saved query, a range. So they are slotted rather than rendered from a list of strings, and removing one is a request this element makes rather than a change it applies. Combobox is the other way round, and that is the difference between the two: its tokens are a view of a selection it owns, drawn from options it was handed.  **'value' is the text being typed, not the tokens**, which is what makes this a field a consumer can listen to. Every keystroke announces 'input' with the text on the element, so a table narrows as the reader types. The tokens need no reporting back, being markup the consumer already holds.  Backspace on an empty field asks the last token to go, through the same 'helix-dismiss' its own remove control fires, so a consumer who handled the pointer has already handled the keyboard.  **It reads what was declared, and nothing that was not.** Write 'FilterField's (usually inside the 'FilterMenu' slotted into 'start', so the picker and the text work off one set), and Enter reads the box against them: 'disposition:refunded,settled' and '-disposition:refunded' announce 'helix-facet', exactly as ticking those values in the picker would, and the text they were read from goes. Everything else stays where it was typed, so 'refund tuesday disposition:settled' is a filter and a search at once. 'grammar.ts' carries the whole rule and is worth reading before relying on it; the short version is that Helix owns the punctuation and the consumer owns every word in it. A field with no 'FilterField' in it parses nothing, which is the behavior this had before it could.  **A field whose values cannot be listed belongs here rather than in the picker.** 'assignee:ada' is a filter and nobody wants to enumerate every name in the company, but a menu page for it would have nothing on it to press. Written directly inside this element it is read by the grammar and never offered as a page: unslotted, so nothing draws it, which is the same trick 'FilterField' already plays on its own children.  **It can suggest what to type next, and deciding what to suggest is still the consumer's.** Slot 'helix-option' elements into 'suggestions' and the field shows them, moves through them with the arrows, and lets Enter press one; the option fires its own 'helix-select' and the consumer decides what choosing meant. Keys before a colon and values after it are the same panel with different contents, and 'readFilterText' is exported for a consumer narrowing that panel against what a reader has half typed.  **The panel opens when there is something in it and closes when there is not**, rather than on a choice. A reader who picks a key wants its values next, and closing on the choice would shut the panel between two renders. Use 'selectionStart' and 'setSelectionRange' to write a completion back and put the caret after it, or the next parse reads the wrong term.  **Three things here have three different owners, and only one of them is a controlled property.**  'value' is the text, and it is uncontrolled by default: the reader types, the element applies it, and 'input' says so. **Writing 'value' does not take that over.** It is a seed and a correction, so a consumer who sets it and then expects the field to hold still will watch the next keystroke overwrite them. Ownership is taken by refusing 'helix-before-change' and writing the value you want, which is the same shape every field in this library uses and is worth saying out loud here because the property looks like React's. 'default-value' seeds the field without claiming anything.  'open' is the suggestions panel, and it is the ordinary controlled pair: refuse 'helix-before-open' or 'helix-before-close' to take the decision, and 'default-open' to seed it.  The tokens are neither, because they are not state. They are the consumer's own elements in a slot, so there is nothing for this to own and nothing to report back: a token goes when the consumer removes it from their markup, having been asked by 'helix-dismiss'. **A 'FilterChip' naming a declared field is asked differently**, and it has to be: the picker holds what is ticked, so a chip that removed itself without telling it left the value ticked in a list nobody could see was wrong. That dismissal is answered as the field being filtered by nothing, so it arrives as 'helix-facet' like every other change and the chip goes because the filter went. */
   "helix-headless-filter-input": DefineCustomElement<
     HelixHeadlessFilterInput,
     HelixHeadlessFilterInputVueProps,