@fusion.dev/helix-headless 0.158.0 → 0.160.0

package/types/jsx.d.ts

@@ -936,9 +936,18 @@ export type HelixHeadlessAppHeaderElementEvent<E = Event> = TypedEvent<
   HelixHeadlessAppHeader,
   E
 >;
+/** `helix-before-close` event type */
+export type HelixHeadlessAppHeaderHelixBeforeCloseElementEvent =
+  HelixHeadlessAppHeaderElementEvent<HelixBeforeCloseEvent>;
+/** `helix-before-open` event type */
+export type HelixHeadlessAppHeaderHelixBeforeOpenElementEvent =
+  HelixHeadlessAppHeaderElementEvent<HelixBeforeOpenEvent>;
 /** `helix-scrolled` event type */
 export type HelixHeadlessAppHeaderHelixScrolledElementEvent =
   HelixHeadlessAppHeaderElementEvent<HelixScrolledEvent>;
+/** `toggle` event type */
+export type HelixHeadlessAppHeaderToggleElementEvent =
+  HelixHeadlessAppHeaderElementEvent<ToggleEvent>;
 
 export type HelixHeadlessAppHeaderProps = {
   /** Where the middle region sits in the bar.
@@ -988,11 +997,50 @@ page scrolls up. */
   /** The id of the element whose scrolling lifts the bar, for an app shell that
 scrolls a container instead of the window. Unset is the window. */
   scroller?: (HelixHeadlessAppHeader["scroller"]) | undefined;
+  /** Where the toggle that opens a folded middle region sits: at the end of the
+bar, after the trailing content, or with `start`, before the leading
+content.
+
+Optional, so the resting bar writes no attribute onto the host. */
+  "toggle-placement"?: (HelixHeadlessAppHeader["togglePlacement"]) | undefined;
+  /** Where the toggle that opens a folded middle region sits: at the end of the
+bar, after the trailing content, or with `start`, before the leading
+content.
+
+Optional, so the resting bar writes no attribute onto the host. */
+  togglePlacement?: (HelixHeadlessAppHeader["togglePlacement"]) | undefined;
+  /** Whether the element starts open. Ignored once `open` is written. */
+  "default-open"?: (HelixHeadlessAppHeader["defaultOpen"]) | undefined;
+  /** Whether the element starts open. Ignored once `open` is written. */
+  defaultOpen?: (HelixHeadlessAppHeader["defaultOpen"]) | undefined;
+  /** Whether the element is open.
+
+One property, not two, so `dialog.open` answers the question anyone
+asking it meant. Writing always applies; `<helix-dialog open>` is the
+same statement in markup.
+
+**Not reflected, and that is required rather than tidy.** Reflection
+writes the resolved state back as an attribute, so an element that opened
+itself would put `open` on its own host: cloned, serialized for
+hydration, or diffed by a framework, it comes back holding whatever the
+last reader did rather than what the author wrote. `:state(open)` carries
+the resolved state for stylesheets, which is what the mirror is for. */
+  open?: (HelixHeadlessAppHeader["open"]) | undefined;
 
+  /** The folded region is about to close. Cancelable: cancel it to keep it open. */
+  "onhelix-before-close"?: ((
+    e: HelixHeadlessAppHeaderHelixBeforeCloseElementEvent,
+  ) => void) | undefined;
+  /** The folded region is about to open. Cancelable: cancel it to keep it closed. */
+  "onhelix-before-open"?: ((
+    e: HelixHeadlessAppHeaderHelixBeforeOpenElementEvent,
+  ) => void) | undefined;
   /** Fired when the page crosses the scroll threshold, with the new state. A custom state cannot be observed the way an attribute can, so listen for this event to follow it. The event uses the header's own threshold and hysteresis, so you do not need a second scroll listener. */
   "onhelix-scrolled"?: ((
     e: HelixHeadlessAppHeaderHelixScrolledElementEvent,
   ) => void) | undefined;
+  /** The folded region opened or closed. The event carries `newState` and `oldState`. */
+  ontoggle?: ((e: HelixHeadlessAppHeaderToggleElementEvent) => void) | undefined;
 };
 
 export type HelixHeadlessAppHeaderSolidJsProps = {
@@ -1043,10 +1091,49 @@ page scrolls up. */
   /** The id of the element whose scrolling lifts the bar, for an app shell that
 scrolls a container instead of the window. Unset is the window. */
   "prop:scroller"?: (HelixHeadlessAppHeader["scroller"]) | undefined;
+  /** Where the toggle that opens a folded middle region sits: at the end of the
+bar, after the trailing content, or with `start`, before the leading
+content.
+
+Optional, so the resting bar writes no attribute onto the host. */
+  "attr:toggle-placement"?: (HelixHeadlessAppHeader["togglePlacement"]) | undefined;
+  /** Where the toggle that opens a folded middle region sits: at the end of the
+bar, after the trailing content, or with `start`, before the leading
+content.
+
+Optional, so the resting bar writes no attribute onto the host. */
+  "prop:togglePlacement"?: (HelixHeadlessAppHeader["togglePlacement"]) | undefined;
+  /** Whether the element starts open. Ignored once `open` is written. */
+  "bool:default-open"?: (HelixHeadlessAppHeader["defaultOpen"]) | undefined;
+  /** Whether the element starts open. Ignored once `open` is written. */
+  "prop:defaultOpen"?: (HelixHeadlessAppHeader["defaultOpen"]) | undefined;
+  /** Whether the element is open.
+
+One property, not two, so `dialog.open` answers the question anyone
+asking it meant. Writing always applies; `<helix-dialog open>` is the
+same statement in markup.
+
+**Not reflected, and that is required rather than tidy.** Reflection
+writes the resolved state back as an attribute, so an element that opened
+itself would put `open` on its own host: cloned, serialized for
+hydration, or diffed by a framework, it comes back holding whatever the
+last reader did rather than what the author wrote. `:state(open)` carries
+the resolved state for stylesheets, which is what the mirror is for. */
+  "prop:open"?: (HelixHeadlessAppHeader["open"]) | undefined;
+  /** The folded region is about to close. Cancelable: cancel it to keep it open. */
+  "on:helix-before-close"?: ((
+    e: HelixHeadlessAppHeaderHelixBeforeCloseElementEvent,
+  ) => void) | undefined;
+  /** The folded region is about to open. Cancelable: cancel it to keep it closed. */
+  "on:helix-before-open"?: ((
+    e: HelixHeadlessAppHeaderHelixBeforeOpenElementEvent,
+  ) => void) | undefined;
   /** Fired when the page crosses the scroll threshold, with the new state. A custom state cannot be observed the way an attribute can, so listen for this event to follow it. The event uses the header's own threshold and hysteresis, so you do not need a second scroll listener. */
   "on:helix-scrolled"?: ((
     e: HelixHeadlessAppHeaderHelixScrolledElementEvent,
   ) => void) | undefined;
+  /** The folded region opened or closed. The event carries `newState` and `oldState`. */
+  "on:toggle"?: ((e: HelixHeadlessAppHeaderToggleElementEvent) => void) | undefined;
 
   /** Set the innerHTML of the element */
   innerHTML?: (string) | undefined;
@@ -2317,6 +2404,14 @@ export type HelixHeadlessButtonGroupHelixBeforeChangeElementEvent =
   HelixHeadlessButtonGroupElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixHeadlessButtonGroupProps = {
+  /** Keeps at least one button pressed once one is, as React Aria's
+`disallowEmptySelection`: a press that would leave none pressed is
+refused. */
+  "disallow-empty-selection"?: (HelixHeadlessButtonGroup["disallowEmptySelection"]) | undefined;
+  /** Keeps at least one button pressed once one is, as React Aria's
+`disallowEmptySelection`: a press that would leave none pressed is
+refused. */
+  disallowEmptySelection?: (HelixHeadlessButtonGroup["disallowEmptySelection"]) | undefined;
   /** The group's name, read by screen readers.
 
 On the host through internals, so an author's `aria-label` still overrides
@@ -2368,6 +2463,14 @@ not reflect, as a native control's `value` does not. */
 };
 
 export type HelixHeadlessButtonGroupSolidJsProps = {
+  /** Keeps at least one button pressed once one is, as React Aria's
+`disallowEmptySelection`: a press that would leave none pressed is
+refused. */
+  "bool:disallow-empty-selection"?: (HelixHeadlessButtonGroup["disallowEmptySelection"]) | undefined;
+  /** Keeps at least one button pressed once one is, as React Aria's
+`disallowEmptySelection`: a press that would leave none pressed is
+refused. */
+  "prop:disallowEmptySelection"?: (HelixHeadlessButtonGroup["disallowEmptySelection"]) | undefined;
   /** The group's name, read by screen readers.
 
 On the host through internals, so an author's `aria-label` still overrides
@@ -9774,37 +9877,56 @@ export type HelixHeadlessDateInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixHeadlessDateInputHelixBeforeOpenElementEvent =
   HelixHeadlessDateInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixHeadlessDateInputHelixClearElementEvent =
+  HelixHeadlessDateInputElementEvent<HelixClearEvent>;
 /** `toggle` event type */
 export type HelixHeadlessDateInputToggleElementEvent =
   HelixHeadlessDateInputElementEvent<ToggleEvent>;
 
 export type HelixHeadlessDateInputProps = {
-  /** What the browser may autofill here, as one of the platform's own tokens.
+  /** What the browser may autofill here, as one of the platform's own tokens,
+such as `bday`.
 
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all: hardcoding `off` here means a birthday or a
-postal code can never be filled in for a reader. */
+postal code can never be filled in for a reader. With `segmented`, a
+hidden native date input carries it, since no browser fills the segments. */
   autocomplete?: (HelixHeadlessDateInput["autocomplete"]) | undefined;
-  /** The calendar the written date and the calendar's days are in: `gregory`,
-`buddhist`, `japanese`, `roc`, or `iso8601`.
-
-Absent is the locale's own where it is one of the five, and `gregory` for
-every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-every calendar, and a focused field is ISO in every calendar. In
-`segmented`, the segments are the Gregorian day, month, and year, in the
-order the locale writes them, or ISO order for `iso8601`. */
+  /** The calendar the written date, the segments, and the calendar's days are
+in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+with months of its own that Date Picker's `calendar` names, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+
+Absent is the locale's own where its months are the Gregorian months, and
+`gregory` for every other, as Date Picker's `calendar` is. The value is
+`YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+calendar. In `segmented`, the segments are the day, month, and year as
+the calendar counts them, in the order the locale writes them: Mehr 14,
+1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+Gregorian months they are the Gregorian day, month, and year, or ISO order
+for `iso8601`. */
   calendar?: (HelixHeadlessDateInput["calendar"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "calendar-label"?: (HelixHeadlessDateInput["calendarLabel"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   calendarLabel?: (HelixHeadlessDateInput["calendarLabel"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  clearable?: (HelixHeadlessDateInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixHeadlessDateInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixHeadlessDateInput["clearLabel"]) | undefined;
   /** How a date is written in the field: `short` through `full`, or ISO.
 
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -9826,8 +9948,9 @@ submits and what `min` and `max` compare against. */
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -9965,6 +10088,14 @@ the date.
 **The name goes in**, so a row of them is heard as which one each
 removes rather than as "Remove" said once per date. */
   removeLabel?: (HelixHeadlessDateInput["removeLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  "selection-label"?: (HelixHeadlessDateInput["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  selectionLabel?: (HelixHeadlessDateInput["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -9976,6 +10107,14 @@ platform's base. */
   "step-mismatch-message"?: (HelixHeadlessDateInput["stepMismatchMessage"]) | undefined;
   /** The message shown when a date is not on `step`. */
   stepMismatchMessage?: (HelixHeadlessDateInput["stepMismatchMessage"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  "time-zone"?: (HelixHeadlessDateInput["timeZone"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  timeZone?: (HelixHeadlessDateInput["timeZone"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
   "trigger-label"?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
@@ -9984,6 +10123,12 @@ platform's base. */
   "unavailable-message"?: (HelixHeadlessDateInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-dates` or `disable-days` bars a date. */
   unavailableMessage?: (HelixHeadlessDateInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  "unreadable-message"?: (HelixHeadlessDateInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  unreadableMessage?: (HelixHeadlessDateInput["unreadableMessage"]) | undefined;
   /** The name of the calendar's heading where it shows a page of years, with
 `{heading}` filled in. */
   "year-view-label"?: (HelixHeadlessDateInput["yearViewLabel"]) | undefined;
@@ -10012,6 +10157,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   incompleteMessage?: (HelixHeadlessDateInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "range-end-label"?: (HelixHeadlessDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  rangeEndLabel?: (HelixHeadlessDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "range-start-label"?: (HelixHeadlessDateInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  rangeStartLabel?: (HelixHeadlessDateInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -10239,6 +10396,8 @@ reader makes in one of these. */
   "onhelix-before-open"?: ((
     e: HelixHeadlessDateInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "onhelix-clear"?: ((e: HelixHeadlessDateInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   oninput?: ((e: HelixHeadlessDateInputElementEvent) => void) | undefined;
   /** Fired when the calendar opens or closes, with `newState` and `oldState`. */
@@ -10246,32 +10405,48 @@ reader makes in one of these. */
 };
 
 export type HelixHeadlessDateInputSolidJsProps = {
-  /** What the browser may autofill here, as one of the platform's own tokens.
+  /** What the browser may autofill here, as one of the platform's own tokens,
+such as `bday`.
 
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all: hardcoding `off` here means a birthday or a
-postal code can never be filled in for a reader. */
+postal code can never be filled in for a reader. With `segmented`, a
+hidden native date input carries it, since no browser fills the segments. */
   "prop:autocomplete"?: (HelixHeadlessDateInput["autocomplete"]) | undefined;
-  /** The calendar the written date and the calendar's days are in: `gregory`,
-`buddhist`, `japanese`, `roc`, or `iso8601`.
-
-Absent is the locale's own where it is one of the five, and `gregory` for
-every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-every calendar, and a focused field is ISO in every calendar. In
-`segmented`, the segments are the Gregorian day, month, and year, in the
-order the locale writes them, or ISO order for `iso8601`. */
+  /** The calendar the written date, the segments, and the calendar's days are
+in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+with months of its own that Date Picker's `calendar` names, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+
+Absent is the locale's own where its months are the Gregorian months, and
+`gregory` for every other, as Date Picker's `calendar` is. The value is
+`YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+calendar. In `segmented`, the segments are the day, month, and year as
+the calendar counts them, in the order the locale writes them: Mehr 14,
+1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+Gregorian months they are the Gregorian day, month, and year, or ISO order
+for `iso8601`. */
   "prop:calendar"?: (HelixHeadlessDateInput["calendar"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "attr:calendar-label"?: (HelixHeadlessDateInput["calendarLabel"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "prop:calendarLabel"?: (HelixHeadlessDateInput["calendarLabel"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  "prop:clearable"?: (HelixHeadlessDateInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "attr:clear-label"?: (HelixHeadlessDateInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "prop:clearLabel"?: (HelixHeadlessDateInput["clearLabel"]) | undefined;
   /** How a date is written in the field: `short` through `full`, or ISO.
 
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -10293,8 +10468,9 @@ submits and what `min` and `max` compare against. */
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -10432,6 +10608,14 @@ the date.
 **The name goes in**, so a row of them is heard as which one each
 removes rather than as "Remove" said once per date. */
   "prop:removeLabel"?: (HelixHeadlessDateInput["removeLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  "attr:selection-label"?: (HelixHeadlessDateInput["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  "prop:selectionLabel"?: (HelixHeadlessDateInput["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -10443,6 +10627,14 @@ platform's base. */
   "attr:step-mismatch-message"?: (HelixHeadlessDateInput["stepMismatchMessage"]) | undefined;
   /** The message shown when a date is not on `step`. */
   "prop:stepMismatchMessage"?: (HelixHeadlessDateInput["stepMismatchMessage"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  "attr:time-zone"?: (HelixHeadlessDateInput["timeZone"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  "prop:timeZone"?: (HelixHeadlessDateInput["timeZone"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
   "attr:trigger-label"?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
@@ -10451,6 +10643,12 @@ platform's base. */
   "attr:unavailable-message"?: (HelixHeadlessDateInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-dates` or `disable-days` bars a date. */
   "prop:unavailableMessage"?: (HelixHeadlessDateInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  "attr:unreadable-message"?: (HelixHeadlessDateInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  "prop:unreadableMessage"?: (HelixHeadlessDateInput["unreadableMessage"]) | undefined;
   /** The name of the calendar's heading where it shows a page of years, with
 `{heading}` filled in. */
   "attr:year-view-label"?: (HelixHeadlessDateInput["yearViewLabel"]) | undefined;
@@ -10479,6 +10677,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   "prop:incompleteMessage"?: (HelixHeadlessDateInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "attr:range-end-label"?: (HelixHeadlessDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "prop:rangeEndLabel"?: (HelixHeadlessDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "attr:range-start-label"?: (HelixHeadlessDateInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "prop:rangeStartLabel"?: (HelixHeadlessDateInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -10705,6 +10915,8 @@ reader makes in one of these. */
   "on:helix-before-open"?: ((
     e: HelixHeadlessDateInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "on:helix-clear"?: ((e: HelixHeadlessDateInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   "on:input"?: ((e: HelixHeadlessDateInputElementEvent) => void) | undefined;
   /** Fired when the calendar opens or closes, with `newState` and `oldState`. */
@@ -10753,14 +10965,16 @@ it is one of the five, such as `buddhist` for `th-TH` or `japanese` for
 `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
 for `fa-IR`.
 
-`persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-`coptic`, and `indian` draw a calendar with months of its own, as React
-Aria's calendars do: each grid is one of that calendar's months, the
-Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-Previous, Next and the page keys move by those months. `month` and
+`persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+`islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+`indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+as React Aria's calendars do: each grid is one of that calendar's months,
+the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+month included, and Previous, Next and the page keys move by those
+months. With `max-view`, the months view shows that calendar's year, of
+twelve or thirteen months, and the years view its years. `month` and
 `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-heading stays text, as the months and years views are drawn in Gregorian
-months only. The value is `YYYY-MM-DD` in every calendar. */
+value is `YYYY-MM-DD` in every calendar. */
   calendar?: (HelixHeadlessDatePicker["calendar"]) | undefined;
   /** The month to open on when `month` is not set. */
   "default-month"?: (HelixHeadlessDatePicker["defaultMonth"]) | undefined;
@@ -10907,6 +11121,18 @@ else set needs. */
   readOnly?: (HelixHeadlessDatePicker["readOnly"]) | undefined;
   /** Stops the form from submitting while no date is chosen. */
   required?: (HelixHeadlessDatePicker["required"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  "selection-label"?: (HelixHeadlessDatePicker["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  selectionLabel?: (HelixHeadlessDatePicker["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -11086,14 +11312,16 @@ it is one of the five, such as `buddhist` for `th-TH` or `japanese` for
 `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
 for `fa-IR`.
 
-`persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-`coptic`, and `indian` draw a calendar with months of its own, as React
-Aria's calendars do: each grid is one of that calendar's months, the
-Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-Previous, Next and the page keys move by those months. `month` and
+`persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+`islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+`indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+as React Aria's calendars do: each grid is one of that calendar's months,
+the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+month included, and Previous, Next and the page keys move by those
+months. With `max-view`, the months view shows that calendar's year, of
+twelve or thirteen months, and the years view its years. `month` and
 `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-heading stays text, as the months and years views are drawn in Gregorian
-months only. The value is `YYYY-MM-DD` in every calendar. */
+value is `YYYY-MM-DD` in every calendar. */
   "prop:calendar"?: (HelixHeadlessDatePicker["calendar"]) | undefined;
   /** The month to open on when `month` is not set. */
   "attr:default-month"?: (HelixHeadlessDatePicker["defaultMonth"]) | undefined;
@@ -11240,6 +11468,18 @@ else set needs. */
   "prop:readOnly"?: (HelixHeadlessDatePicker["readOnly"]) | undefined;
   /** Stops the form from submitting while no date is chosen. */
   "prop:required"?: (HelixHeadlessDatePicker["required"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  "attr:selection-label"?: (HelixHeadlessDatePicker["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  "prop:selectionLabel"?: (HelixHeadlessDatePicker["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -13737,12 +13977,14 @@ Here rather than on each control. */
 
 export type HelixHeadlessFormatDateProps = {
   /** The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-`roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-
-Absent is the locale's own where it is one of the five, such as
-`buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-for `fa-IR`, so a date written here reads as the same date a Date Picker
-beside it shows. */
+`roc`, or `iso8601`, or a calendar with months of its own, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+calendar Date Picker and Date Input draw.
+
+Absent is the locale's own where its months are the Gregorian months,
+such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+`persian` for `fa-IR`, so a date written here reads as the same date a
+Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405. */
   calendar?: (HelixHeadlessFormatDate["calendar"]) | undefined;
   /** The timestamp, in any format `Date` can parse.
 
@@ -13768,6 +14010,14 @@ browser may use either. */
   dateStyle?: (HelixHeadlessFormatDate["dateStyle"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
   day?: (HelixHeadlessFormatDate["day"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  "day-period"?: (HelixHeadlessFormatDate["dayPeriod"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  dayPeriod?: (HelixHeadlessFormatDate["dayPeriod"]) | undefined;
   /** Shows how long ago the timestamp was, in a compact form such as "3h", in
 place of the date.
 
@@ -13785,6 +14035,12 @@ Off by default, which draws the date as one run of text, as Shoelace and
 Web Awesome do. An `elapsed` or `relative` reading is one phrase either
 way. */
   fields?: (HelixHeadlessFormatDate["fields"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  "fractional-second-digits"?: (HelixHeadlessFormatDate["fractionalSecondDigits"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  fractionalSecondDigits?: (HelixHeadlessFormatDate["fractionalSecondDigits"]) | undefined;
   /** Draws an `elapsed` or `relative` reading once and leaves it, where it
 would otherwise move on as it goes stale.
 
@@ -13847,9 +14103,13 @@ Empty is the runtime's own. */
 
 Empty is the runtime's own. */
   timeZone?: (HelixHeadlessFormatDate["timeZone"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   "time-zone-name"?: (HelixHeadlessFormatDate["timeZoneName"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   timeZoneName?: (HelixHeadlessFormatDate["timeZoneName"]) | undefined;
   /** How the weekday is written, where one is shown. */
   weekday?: (HelixHeadlessFormatDate["weekday"]) | undefined;
@@ -13859,12 +14119,14 @@ Empty is the runtime's own. */
 
 export type HelixHeadlessFormatDateSolidJsProps = {
   /** The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-`roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-
-Absent is the locale's own where it is one of the five, such as
-`buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-for `fa-IR`, so a date written here reads as the same date a Date Picker
-beside it shows. */
+`roc`, or `iso8601`, or a calendar with months of its own, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+calendar Date Picker and Date Input draw.
+
+Absent is the locale's own where its months are the Gregorian months,
+such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+`persian` for `fa-IR`, so a date written here reads as the same date a
+Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405. */
   "prop:calendar"?: (HelixHeadlessFormatDate["calendar"]) | undefined;
   /** The timestamp, in any format `Date` can parse.
 
@@ -13890,6 +14152,14 @@ browser may use either. */
   "prop:dateStyle"?: (HelixHeadlessFormatDate["dateStyle"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
   "prop:day"?: (HelixHeadlessFormatDate["day"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  "attr:day-period"?: (HelixHeadlessFormatDate["dayPeriod"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  "prop:dayPeriod"?: (HelixHeadlessFormatDate["dayPeriod"]) | undefined;
   /** Shows how long ago the timestamp was, in a compact form such as "3h", in
 place of the date.
 
@@ -13907,6 +14177,12 @@ Off by default, which draws the date as one run of text, as Shoelace and
 Web Awesome do. An `elapsed` or `relative` reading is one phrase either
 way. */
   "prop:fields"?: (HelixHeadlessFormatDate["fields"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  "attr:fractional-second-digits"?: (HelixHeadlessFormatDate["fractionalSecondDigits"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  "prop:fractionalSecondDigits"?: (HelixHeadlessFormatDate["fractionalSecondDigits"]) | undefined;
   /** Draws an `elapsed` or `relative` reading once and leaves it, where it
 would otherwise move on as it goes stale.
 
@@ -13969,9 +14245,13 @@ Empty is the runtime's own. */
 
 Empty is the runtime's own. */
   "prop:timeZone"?: (HelixHeadlessFormatDate["timeZone"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   "attr:time-zone-name"?: (HelixHeadlessFormatDate["timeZoneName"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   "prop:timeZoneName"?: (HelixHeadlessFormatDate["timeZoneName"]) | undefined;
   /** How the weekday is written, where one is shown. */
   "prop:weekday"?: (HelixHeadlessFormatDate["weekday"]) | undefined;
@@ -26252,6 +26532,14 @@ rather than a thumb sitting on nothing. */
 middle of the track, or `end` at `max`. Absent is `start`. A range fills
 between its thumbs and ignores it. */
   origin?: (HelixHeadlessSlider["origin"]) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  "page-step"?: (HelixHeadlessSlider["pageStep"] | `${number}`) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  pageStep?: (HelixHeadlessSlider["pageStep"]) | undefined;
   /** Adds a second thumb, so the value is a pair.
 
 The pair is one string, `"10,50"`, which is what `value` and
@@ -26506,6 +26794,14 @@ rather than a thumb sitting on nothing. */
 middle of the track, or `end` at `max`. Absent is `start`. A range fills
 between its thumbs and ignores it. */
   "prop:origin"?: (HelixHeadlessSlider["origin"]) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  "attr:page-step"?: (HelixHeadlessSlider["pageStep"] | `${number}`) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  "prop:pageStep"?: (HelixHeadlessSlider["pageStep"]) | undefined;
   /** Adds a second thumb, so the value is a pair.
 
 The pair is one string, `"10,50"`, which is what `value` and
@@ -29059,7 +29355,19 @@ known by its place among the rows as written. */
   textContent?: (string | number) | undefined;
 };
 
+/** `HelixHeadlessTabPanel` component event */
+export type HelixHeadlessTabPanelElementEvent<E = Event> = TypedEvent<
+  HelixHeadlessTabPanel,
+  E
+>;
+/** `helix-load` event type */
+export type HelixHeadlessTabPanelHelixLoadElementEvent =
+  HelixHeadlessTabPanelElementEvent<HelixLoadEvent>;
+
 export type HelixHeadlessTabPanelProps = {
+  /** Whether the panel's content waits in a `<template>` until the panel is
+first shown. */
+  lazy?: (HelixHeadlessTabPanel["lazy"]) | undefined;
   /** Whether this panel is the visible one. */
   selected?: (HelixHeadlessTabPanel["selected"]) | undefined;
   /** Pairs the panel with the tab of the same value. */
@@ -29075,9 +29383,15 @@ written in, and the tab's control is inside the tab's shadow root, which no
 reference from the light DOM can reach. `aria-label` on a `tabpanel` is how
 the pattern names one anyway. */
   label?: (HelixHeadlessTabPanel["label"]) | undefined;
+
+  /** Fired the first time a `lazy` panel is shown, once its template's content is in. */
+  "onhelix-load"?: ((e: HelixHeadlessTabPanelHelixLoadElementEvent) => void) | undefined;
 };
 
 export type HelixHeadlessTabPanelSolidJsProps = {
+  /** Whether the panel's content waits in a `<template>` until the panel is
+first shown. */
+  "prop:lazy"?: (HelixHeadlessTabPanel["lazy"]) | undefined;
   /** Whether this panel is the visible one. */
   "prop:selected"?: (HelixHeadlessTabPanel["selected"]) | undefined;
   /** Pairs the panel with the tab of the same value. */
@@ -29093,6 +29407,8 @@ written in, and the tab's control is inside the tab's shadow root, which no
 reference from the light DOM can reach. `aria-label` on a `tabpanel` is how
 the pattern names one anyway. */
   "prop:label"?: (HelixHeadlessTabPanel["label"]) | undefined;
+  /** Fired the first time a `lazy` panel is shown, once its template's content is in. */
+  "on:helix-load"?: ((e: HelixHeadlessTabPanelHelixLoadElementEvent) => void) | undefined;
 
   /** Set the innerHTML of the element */
   innerHTML?: (string) | undefined;
@@ -30070,6 +30386,9 @@ export type HelixHeadlessTimeInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixHeadlessTimeInputHelixBeforeOpenElementEvent =
   HelixHeadlessTimeInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixHeadlessTimeInputHelixClearElementEvent =
+  HelixHeadlessTimeInputElementEvent<HelixClearEvent>;
 /** `toggle` event type */
 export type HelixHeadlessTimeInputToggleElementEvent =
   HelixHeadlessTimeInputElementEvent<ToggleEvent>;
@@ -30080,6 +30399,14 @@ export type HelixHeadlessTimeInputProps = {
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all. */
   autocomplete?: (HelixHeadlessTimeInput["autocomplete"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  clearable?: (HelixHeadlessTimeInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixHeadlessTimeInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixHeadlessTimeInput["clearLabel"]) | undefined;
   /** Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
 
 Handed to the list, which offers them as unavailable, and checked against
@@ -30183,6 +30510,12 @@ never something this element would refuse to read back. */
   "unavailable-message"?: (HelixHeadlessTimeInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-times` bars a time. */
   unavailableMessage?: (HelixHeadlessTimeInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  "unreadable-message"?: (HelixHeadlessTimeInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  unreadableMessage?: (HelixHeadlessTimeInput["unreadableMessage"]) | undefined;
   /** Whether the panel shows one list of times or a column for each part of the
 time.
 
@@ -30220,6 +30553,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   incompleteMessage?: (HelixHeadlessTimeInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "range-end-label"?: (HelixHeadlessTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  rangeEndLabel?: (HelixHeadlessTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "range-start-label"?: (HelixHeadlessTimeInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  rangeStartLabel?: (HelixHeadlessTimeInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -30436,6 +30781,8 @@ a consumer handing over `new Date()` gets the time of day they expected. */
   "onhelix-before-open"?: ((
     e: HelixHeadlessTimeInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "onhelix-clear"?: ((e: HelixHeadlessTimeInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   oninput?: ((e: HelixHeadlessTimeInputElementEvent) => void) | undefined;
   /** Fired after the list opens or closes, with `newState` and `oldState`. */
@@ -30448,6 +30795,14 @@ export type HelixHeadlessTimeInputSolidJsProps = {
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all. */
   "prop:autocomplete"?: (HelixHeadlessTimeInput["autocomplete"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  "prop:clearable"?: (HelixHeadlessTimeInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "attr:clear-label"?: (HelixHeadlessTimeInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "prop:clearLabel"?: (HelixHeadlessTimeInput["clearLabel"]) | undefined;
   /** Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
 
 Handed to the list, which offers them as unavailable, and checked against
@@ -30551,6 +30906,12 @@ never something this element would refuse to read back. */
   "attr:unavailable-message"?: (HelixHeadlessTimeInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-times` bars a time. */
   "prop:unavailableMessage"?: (HelixHeadlessTimeInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  "attr:unreadable-message"?: (HelixHeadlessTimeInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  "prop:unreadableMessage"?: (HelixHeadlessTimeInput["unreadableMessage"]) | undefined;
   /** Whether the panel shows one list of times or a column for each part of the
 time.
 
@@ -30588,6 +30949,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   "prop:incompleteMessage"?: (HelixHeadlessTimeInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "attr:range-end-label"?: (HelixHeadlessTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "prop:rangeEndLabel"?: (HelixHeadlessTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "attr:range-start-label"?: (HelixHeadlessTimeInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "prop:rangeStartLabel"?: (HelixHeadlessTimeInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -30803,6 +31176,8 @@ a consumer handing over `new Date()` gets the time of day they expected. */
   "on:helix-before-open"?: ((
     e: HelixHeadlessTimeInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "on:helix-clear"?: ((e: HelixHeadlessTimeInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   "on:input"?: ((e: HelixHeadlessTimeInputElementEvent) => void) | undefined;
   /** Fired after the list opens or closes, with `newState` and `oldState`. */
@@ -31716,6 +32091,12 @@ consumer's server markup does not have. A sheet carries the resting
 arrangement in its own `:host` rule and the selectors describe only the
 departures, which is what `orientation` does. */
   placement?: (HelixHeadlessToast["placement"]) | undefined;
+  /** The edge a touch or a pen swipes a message toward to dismiss it: `end`,
+the end of the line, or `start`, `top` or `bottom`. Unset is `end`. */
+  "swipe-direction"?: (HelixHeadlessToast["swipeDirection"]) | undefined;
+  /** The edge a touch or a pen swipes a message toward to dismiss it: `end`,
+the end of the line, or `start`, `top` or `bottom`. Unset is `end`. */
+  swipeDirection?: (HelixHeadlessToast["swipeDirection"]) | undefined;
 
   /** A message is being dismissed, by its control or by its timer. The message sends it, and you can listen for it on the region. Cancelable: canceling it keeps the message. */
   "onhelix-dismiss"?: ((e: HelixHeadlessToastHelixDismissElementEvent) => void) | undefined;
@@ -31763,6 +32144,12 @@ consumer's server markup does not have. A sheet carries the resting
 arrangement in its own `:host` rule and the selectors describe only the
 departures, which is what `orientation` does. */
   "prop:placement"?: (HelixHeadlessToast["placement"]) | undefined;
+  /** The edge a touch or a pen swipes a message toward to dismiss it: `end`,
+the end of the line, or `start`, `top` or `bottom`. Unset is `end`. */
+  "attr:swipe-direction"?: (HelixHeadlessToast["swipeDirection"]) | undefined;
+  /** The edge a touch or a pen swipes a message toward to dismiss it: `end`,
+the end of the line, or `start`, `top` or `bottom`. Unset is `end`. */
+  "prop:swipeDirection"?: (HelixHeadlessToast["swipeDirection"]) | undefined;
   /** A message is being dismissed, by its control or by its timer. The message sends it, and you can listen for it on the region. Cancelable: canceling it keeps the message. */
   "on:helix-dismiss"?: ((e: HelixHeadlessToastHelixDismissElementEvent) => void) | undefined;
 
@@ -31785,6 +32172,18 @@ export type HelixHeadlessToggleGroupHelixSelectElementEvent =
   HelixHeadlessToggleGroupElementEvent<HelixSelectEvent>;
 
 export type HelixHeadlessToggleGroupProps = {
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  "allow-empty-selection"?: (HelixHeadlessToggleGroup["allowEmptySelection"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  allowEmptySelection?: (HelixHeadlessToggleGroup["allowEmptySelection"]) | undefined;
   /** Where the group's label sits. `start` puts it on the track's line.
 
 Absent is above, which is what a field looks like and what almost every
@@ -31963,6 +32362,18 @@ Where one item is chosen, it is that one value, or none. */
 };
 
 export type HelixHeadlessToggleGroupSolidJsProps = {
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  "bool:allow-empty-selection"?: (HelixHeadlessToggleGroup["allowEmptySelection"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  "prop:allowEmptySelection"?: (HelixHeadlessToggleGroup["allowEmptySelection"]) | undefined;
   /** Where the group's label sits. `start` puts it on the track's line.
 
 Absent is above, which is what a field looks like and what almost every
@@ -32679,6 +33090,14 @@ The shape is `Carousel`'s, which is the nearest thing in the library: a
   "next-label"?: (HelixHeadlessTour["nextLabel"]) | undefined;
   /** Label for the control that goes on. */
   nextLabel?: (HelixHeadlessTour["nextLabel"]) | undefined;
+  /** What a press outside the current stop and its target does while the tour
+runs. Unset, nothing: the page stays usable. `close` ends the tour, as
+Skip does, and `block` refuses the press. */
+  "outside-press"?: (HelixHeadlessTour["outsidePress"]) | undefined;
+  /** What a press outside the current stop and its target does while the tour
+runs. Unset, nothing: the page stays usable. `close` ends the tour, as
+Skip does, and `block` refuses the press. */
+  outsidePress?: (HelixHeadlessTour["outsidePress"]) | undefined;
   /** Draws each stop's place in the run in its panel, as well as saying it. */
   progress?: (HelixHeadlessTour["progress"]) | undefined;
   /** Each stop's place in the run, with `{index}` and `{count}` filled in and
@@ -32769,6 +33188,14 @@ The shape is `Carousel`'s, which is the nearest thing in the library: a
   "attr:next-label"?: (HelixHeadlessTour["nextLabel"]) | undefined;
   /** Label for the control that goes on. */
   "prop:nextLabel"?: (HelixHeadlessTour["nextLabel"]) | undefined;
+  /** What a press outside the current stop and its target does while the tour
+runs. Unset, nothing: the page stays usable. `close` ends the tour, as
+Skip does, and `block` refuses the press. */
+  "attr:outside-press"?: (HelixHeadlessTour["outsidePress"]) | undefined;
+  /** What a press outside the current stop and its target does while the tour
+runs. Unset, nothing: the page stays usable. `close` ends the tour, as
+Skip does, and `block` refuses the press. */
+  "prop:outsidePress"?: (HelixHeadlessTour["outsidePress"]) | undefined;
   /** Draws each stop's place in the run in its panel, as well as saying it. */
   "prop:progress"?: (HelixHeadlessTour["progress"]) | undefined;
   /** Each stop's place in the run, with `{index}` and `{count}` filled in and
@@ -32887,6 +33314,9 @@ heading. */
 Reflected, because the styled tier places a dialog and a floating panel by
 it, and unset at rest, so no default is written onto the host. */
   type?: (HelixHeadlessTourStop["type"]) | undefined;
+  /** Run as the tour reaches the stop, before it is shown: see the description
+above. A function, so it is set from script and has no attribute. */
+  effect?: (HelixHeadlessTourStop["effect"]) | undefined;
 
   /** Fired when one of the stop's controls is pressed, to move the tour. */
   "onhelix-tour-ask"?: ((
@@ -32939,6 +33369,9 @@ heading. */
 Reflected, because the styled tier places a dialog and a floating panel by
 it, and unset at rest, so no default is written onto the host. */
   "prop:type"?: (HelixHeadlessTourStop["type"]) | undefined;
+  /** Run as the tour reaches the stop, before it is shown: see the description
+above. A function, so it is set from script and has no attribute. */
+  "prop:effect"?: (HelixHeadlessTourStop["effect"]) | undefined;
   /** Fired when one of the stop's controls is pressed, to move the tour. */
   "on:helix-tour-ask"?: ((
     e: HelixHeadlessTourStopHelixTourAskElementEvent,
@@ -35558,12 +35991,21 @@ export type CustomElements = {
    *
    * **Set `fold-below` to fold the middle region on a narrow screen.** Below that
    * many pixels of the bar's own width, the middle region is hidden behind a
-   * toggle at the end of the bar, named by `menu-label`. The toggle says whether
-   * the region is open with `aria-expanded`, and the region opens below the row.
-   * Escape closes it and puts focus back on the toggle. The custom state
-   * `folded` is on the host while the bar is that narrow, and `open` while the
-   * folded region is open. A server serves the bar unfolded, and the browser
-   * folds it once it has measured it.
+   * toggle at the end of the bar, named by `menu-label`, or at its start with
+   * `toggle-placement="start"`. The toggle says whether the region is open with
+   * `aria-expanded`, and the region opens below the row. The region follows the
+   * toggle's region in focus order, so Tab from the toggle at the end goes into
+   * the open region. The custom state `folded` is on the host while the bar is
+   * that narrow, and `open` while the folded region is open. A server serves the
+   * bar unfolded, and the browser folds it once it has measured it.
+   *
+   * **`open` says whether the folded region is open, and setting it opens or
+   * closes the region.** `requestOpen(true)` and `requestOpen(false)` do the same
+   * and send `helix-before-open` or `helix-before-close` first, which you can
+   * cancel, and `toggleOpen()` asks for the opposite. `toggle` follows every
+   * change. The region closes on Escape, which puts focus back on the toggle,
+   * when focus moves to something outside the header, and on a press outside
+   * it. A bar that widens past `fold-below` closes its region.
    *
    * The host is the page's `banner` landmark. Placed inside `main`, `article`,
    * `aside`, `nav` or `section`, it is a plain box instead, as a native
@@ -35598,6 +36040,24 @@ export type CustomElements = {
    * - `menu-label`/`menuLabel`: The name of the toggle that opens a folded middle region.
    * - `scroller`: The id of the element whose scrolling lifts the bar, for an app shell that
    * scrolls a container instead of the window. Unset is the window.
+   * - `toggle-placement`/`togglePlacement`: Where the toggle that opens a folded middle region sits: at the end of the
+   * bar, after the trailing content, or with `start`, before the leading
+   * content.
+   *
+   * Optional, so the resting bar writes no attribute onto the host.
+   * - `default-open`/`defaultOpen`: Whether the element starts open. Ignored once `open` is written.
+   * - `open`: Whether the element is open.
+   *
+   * One property, not two, so `dialog.open` answers the question anyone
+   * asking it meant. Writing always applies; `<helix-dialog open>` is the
+   * same statement in markup.
+   *
+   * **Not reflected, and that is required rather than tidy.** Reflection
+   * writes the resolved state back as an attribute, so an element that opened
+   * itself would put `open` on its own host: cloned, serialized for
+   * hydration, or diffed by a framework, it comes back holding whatever the
+   * last reader did rather than what the author wrote. `:state(open)` carries
+   * the resolved state for stylesheets, which is what the mirror is for.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -35623,7 +36083,10 @@ export type CustomElements = {
    *
    * Events that will be emitted by the component.
    *
+   * - `helix-before-close`: The folded region is about to close. Cancelable: cancel it to keep it open.
+   * - `helix-before-open`: The folded region is about to open. Cancelable: cancel it to keep it closed.
    * - `helix-scrolled`: Fired when the page crosses the scroll threshold, with the new state. A custom state cannot be observed the way an attribute can, so listen for this event to follow it. The event uses the header's own threshold and hysteresis, so you do not need a second scroll listener.
+   * - `toggle`: The folded region opened or closed. The event carries `newState` and `oldState`.
    *
    * ## Slots
    *
@@ -35634,6 +36097,20 @@ export type CustomElements = {
    * - `menu-icon`: Replaces the glyph inside the toggle that opens a folded middle region.
    * - `start`: Leading content, usually a wordmark.
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `requestOpen(next: boolean) => boolean`: Requests that the element open or close, and returns whether the change
+   * was applied.
+   *
+   * Announces before it acts, so `preventDefault()` on the `helix-before-open` or
+   * `helix-before-close` is a refusal and nothing moves. Nobody refusing means the
+   * element opens or closes itself, whether or not a consumer declared
+   * `open`: a declared property is a seed and a correction, and a consumer
+   * who wants the decision for themselves refuses it and assigns their own.
+   * - `toggleOpen() => boolean`: Requests the opposite of the current state.
+   *
    * ## CSS Parts
    *
    * Custom selectors for styling elements within the component.
@@ -37018,11 +37495,15 @@ export type CustomElements = {
    * appearance and size.
    *
    * **Buttons that stay pressed.** With `selection-mode`, each button with a
-   * `value` is a toggle button: a press presses or releases it, and it says so
-   * with `aria-pressed`. `single` keeps one pressed at a time, and a press on the
-   * pressed one releases it. `multiple` lets any number be pressed. `value` is
-   * the pressed values, comma separated. A press sends a cancelable
-   * `helix-before-change` with the value it would leave, then `change`.
+   * `value` is a toggle button: a press presses or releases it. `multiple` lets
+   * any number be pressed, and each button says so with `aria-pressed`. `single`
+   * keeps one pressed at a time: the group is a `radiogroup` and each button a
+   * `radio` that says so with `aria-checked`, as React Aria's toggle button
+   * group is. A press on the pressed one releases it, unless
+   * `disallow-empty-selection` keeps one pressed. `value` is the pressed values,
+   * comma separated. A press sends a cancelable `helix-before-change` with the
+   * value it would leave, then `change`. A pressed Helix button has
+   * `:state(pressed)` on its own element.
    *
    * The pressed state is written on the control inside each button's shadow
    * root, so the markup you rendered is never changed and a framework hydrating
@@ -37050,15 +37531,18 @@ export type CustomElements = {
    * | Space, Enter | Presses or releases the focused button. |
    *
    * Left and Right swap on a right-to-left page, and a disabled button is
-   * passed over. In a selection mode the group is a `toolbar`, with
+   * passed over. Under `multiple` the group is a `toolbar`, with
    * `aria-orientation` under `orientation="vertical"`. Inside a toolbar it stays
    * a named `group`, and the toolbar's own arrow keys walk its buttons, so a
-   * reader meets one toolbar.
+   * reader meets one toolbar. Under `single` it is a `radiogroup` either way.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `disallow-empty-selection`/`disallowEmptySelection`: Keeps at least one button pressed once one is, as React Aria's
+   * `disallowEmptySelection`: a press that would leave none pressed is
+   * refused.
    * - `label`: The group's name, read by screen readers.
    *
    * On the host through internals, so an author's `aria-label` still overrides
@@ -37426,6 +37910,7 @@ export type CustomElements = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `pending`: The button is pending: `pending` is set.
+   * - `pressed`: A Button Group in a selection mode has this button pressed.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-button": Partial<
@@ -41607,6 +42092,7 @@ export type CustomElements = {
    * - `copied`: The moment after a successful copy, while `copied-label` names the button.
    * - `failed`: The moment after a press that put nothing on the clipboard, while `error-label` names the button.
    * - `pending`: The button is pending: `pending` is set.
+   * - `pressed`: A Button Group in a selection mode has this button pressed.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-copy-button": Partial<
@@ -42109,17 +42595,24 @@ export type CustomElements = {
    * gives a picker and locale formatting but allows almost no styling, so the
    * field is a text field. Typing sends `input` on each keystroke and `change`
    * when you leave the field, as a text field does. A date picked from the
-   * calendar sends both.
+   * calendar sends both. The field reads ISO, `2026-08-04`, and a date written
+   * in the order, the digits, and the month names of `locale`, `8/4/2026` or
+   * `Aug 4, 2026` in `en-US` and `4.8.2026` in `de-DE`, which becomes the value
+   * as you leave the field.
    *
    * The trigger and ArrowDown open the calendar with focus on the selected day,
    * Tab moves between the calendar's controls without leaving it, and Escape
    * closes it and returns focus to the field. A press into the field opens the
    * calendar too. Tab into the field opens nothing, and Tab out of the field
-   * closes the calendar.
+   * closes the calendar. The text field is a `combobox` with
+   * `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, as in the
+   * APG date picker combobox, since Down opens the calendar from it.
    *
    * With `segmented`, the field is a row of segments in place of the text: a
    * month, a day and a year in the order the locale writes them, each set with
-   * digits or the arrow keys. Alt+Down opens the calendar from a segment.
+   * digits or the arrow keys. Alt+Down opens the calendar from a segment. A
+   * `range` is two rows with a dash between them, the start and the end, as
+   * React Aria's DateRangePicker draws them, and `multiple` keeps the text.
    *
    * Text that is not a date gives the form an empty value, as a native date
    * field does, and `value` keeps the text so it can be corrected.
@@ -42149,27 +42642,39 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens.
+   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens,
+   * such as `bday`.
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all: hardcoding `off` here means a birthday or a
-   * postal code can never be filled in for a reader.
-   * - `calendar`: The calendar the written date and the calendar's days are in: `gregory`,
-   * `buddhist`, `japanese`, `roc`, or `iso8601`.
-   *
-   * Absent is the locale's own where it is one of the five, and `gregory` for
-   * every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-   * every calendar, and a focused field is ISO in every calendar. In
-   * `segmented`, the segments are the Gregorian day, month, and year, in the
-   * order the locale writes them, or ISO order for `iso8601`.
+   * postal code can never be filled in for a reader. With `segmented`, a
+   * hidden native date input carries it, since no browser fills the segments.
+   * - `calendar`: The calendar the written date, the segments, and the calendar's days are
+   * in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+   * with months of its own that Date Picker's `calendar` names, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+   *
+   * Absent is the locale's own where its months are the Gregorian months, and
+   * `gregory` for every other, as Date Picker's `calendar` is. The value is
+   * `YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+   * calendar. In `segmented`, the segments are the day, month, and year as
+   * the calendar counts them, in the order the locale writes them: Mehr 14,
+   * 1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+   * Gregorian months they are the Gregorian day, month, and year, or ISO order
+   * for `iso8601`.
    * - `calendar-label`/`calendarLabel`: The name of the calendar's grid of days, read by screen readers.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `date-style`/`dateStyle`: How a date is written in the field: `short` through `full`, or ISO.
    *
    * **The field renders when it is idle and holds the value when it is being
    * edited.** A written date is a rendering, and a document being edited must
    * not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-   * not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-   * locale is how a field ends up rejecting what it just displayed.
+   * not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+   * edit. The field does read a date typed in the locale's order and digits as
+   * you leave it, which covers what a reader types.
    *
    * The way out is not to choose between the two but to separate them in time.
    * Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -42237,6 +42742,9 @@ export type CustomElements = {
    *
    * **The name goes in**, so a row of them is heard as which one each
    * removes rather than as "Remove" said once per date.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the dates chosen in the calendar, with
+   * `{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+   * `selection-label` says.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -42244,8 +42752,13 @@ export type CustomElements = {
    * where there is one and from 1 January 1970 where there is not, which is the
    * platform's base.
    * - `step-mismatch-message`/`stepMismatchMessage`: The message shown when a date is not on `step`.
+   * - `time-zone`/`timeZone`: The time zone today is read in, such as `America/New_York`, handed to the
+   * calendar: the day marked today, and the month an empty field opens on.
+   * Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the calendar, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-dates` or `disable-days` bars a date.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no date, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`.
    * - `year-view-label`/`yearViewLabel`: The name of the calendar's heading where it shows a page of years, with
    * `{heading}` filled in.
    * - `empty-message`/`emptyMessage`: What a row of segments reports when the field is required and every
@@ -42256,6 +42769,10 @@ export type CustomElements = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -42416,6 +42933,7 @@ export type CustomElements = {
    * - `helix-before-change`: Fired before the date changes. Cancelable: call `preventDefault()` to keep the current date.
    * - `helix-before-close`: Fired before the calendar closes. Cancelable: call `preventDefault()` to keep it open.
    * - `helix-before-open`: Fired before the calendar opens. Cancelable: call `preventDefault()` to keep it closed.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    * - `toggle`: Fired when the calendar opens or closes, with `newState` and `oldState`.
    *
@@ -42423,6 +42941,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the date, before the trigger, such as a clear button.
    * - `feedback`: The error message under the field.
    * - `hint`: The help text under the field.
@@ -42498,6 +43017,7 @@ export type CustomElements = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a date.
    * - `control`: The text input.
    * - `date`: One held date, as a tag, in `multiple`.
    * - `date-cell`: The tag's grid cell, which a tag draws only inside a tag group.
@@ -42539,8 +43059,10 @@ export type CustomElements = {
    * - `picker-periods`: The grid of months or years.
    * - `picker-previous`: The control that moves to the previous month.
    * - `picker-previous-mark`: The icon on the previous month control.
+   * - `picker-selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `picker-week`: One row of days.
    * - `picker-weekday`: A column header naming a day of the week.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of dates beyond the ones shown. It is a `<button>` with `expandable` and a `<span>` without it.
    * - `segment`: One part of the date, a year, a month or a day, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -42554,6 +43076,7 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no date.
    * - `invalid`: The field has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: The calendar is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -42573,9 +43096,11 @@ export type CustomElements = {
    * **Dates are `YYYY-MM-DD` strings, and every calculation is in UTC**, because
    * a local-time `Date` shifts across a time zone or daylight-saving boundary.
    *
-   * **The days are the Gregorian calendar's**, written in `calendar`: the
-   * locale's own where its months are the Gregorian months, as `th-TH` writes
-   * 2569 for 2026, and `gregory` where they are not, as for `fa-IR`.
+   * **The months are the ones `calendar` counts**: the Gregorian months for the
+   * locale's own calendar where its months are the Gregorian months, as `th-TH`
+   * writes 2569 for 2026, and `gregory` where they are not, as for `fa-IR`
+   * with no `calendar`. Name a calendar with months of its own, such as
+   * `persian`, and every view counts its days, months, and years from `Intl`.
    *
    * `month` sets which month the grid shows, separately from `value`, so paging
    * selects nothing and you can control the view. When unset, it follows the
@@ -42583,7 +43108,14 @@ export type CustomElements = {
    *
    * `mode` sets how many dates are held. Unset holds one, `range` holds two and
    * marks the dates between them, and `multiple` toggles each date. All three
-   * read and write the same comma-separated `value`.
+   * read and write the same comma-separated `value`. With a `mode`, the grid
+   * carries `aria-multiselectable`. While a range holds one end, the grid draws
+   * the range to the day under the pointer or the focus, marking those cells
+   * `data-range-preview`.
+   *
+   * The chosen date, range, or count of dates is the grid's description, in a
+   * region screen readers announce when it changes, as React Aria's calendars
+   * do. `selection-label` words it.
    *
    * `max-view` makes the heading a button that steps back to the months of the
    * year, and with `year` to a page of years, as Zag's date picker does. The
@@ -42618,14 +43150,16 @@ export type CustomElements = {
    * `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
    * for `fa-IR`.
    *
-   * `persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-   * `coptic`, and `indian` draw a calendar with months of its own, as React
-   * Aria's calendars do: each grid is one of that calendar's months, the
-   * Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-   * Previous, Next and the page keys move by those months. `month` and
+   * `persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+   * `islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+   * `indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+   * as React Aria's calendars do: each grid is one of that calendar's months,
+   * the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+   * month included, and Previous, Next and the page keys move by those
+   * months. With `max-view`, the months view shows that calendar's year, of
+   * twelve or thirteen months, and the years view its years. `month` and
    * `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-   * heading stays text, as the months and years views are drawn in Gregorian
-   * months only. The value is `YYYY-MM-DD` in every calendar.
+   * value is `YYYY-MM-DD` in every calendar.
    * - `default-month`/`defaultMonth`: The month to open on when `month` is not set.
    * - `disable-dates`/`disableDates`: Dates that cannot be chosen, as `YYYY-MM-DD`, separated by commas or
    * spaces.
@@ -42688,6 +43222,11 @@ export type CustomElements = {
    * value and stays reachable, which is what a form showing a value somebody
    * else set needs.
    * - `required`: Stops the form from submitting while no date is chosen.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the chosen dates: the grid's
+   * description, said again whenever the dates change. `{kind}` is `date`,
+   * `start` while a range holds one end, `range`, or `dates` for `multiple`.
+   * `{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+   * many dates are chosen.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -42842,6 +43381,13 @@ export type CustomElements = {
    * Date Input calls this when its trigger opens the calendar, which is where
    * the APG date picker dialog puts focus. The host is not focusable, so a
    * plain `focus()` on it did nothing and focus stayed on the trigger.
+   * - `showChosen() => void`: Shows the days again, on the month of the chosen date, with the tab stop
+   * on that date, forgetting the month and the day the reader browsed to.
+   *
+   * Date Input calls it each time its panel opens, which is where the APG
+   * date picker dialog puts focus. Measured before this: from August 4, two
+   * presses of Page Down, Escape, and Down again opened on October 4.
+   * A `month` you set stays until the reader pages away from it.
    * - `requestValue(next: string) => boolean`: Refuses every change while read-only. See `readOnly`.
    * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
    * where there is no `default-value`.
@@ -42905,7 +43451,7 @@ export type CustomElements = {
    * Custom selectors for styling elements within the component.
    *
    * - `cell`: One column of a week row. A range is painted on the cells.
-   * - `cell-range-end`: The cell of a range's last day, beside `cell`.
+   * - `cell-range-end`: The cell of a range's last day, beside `cell`, or of the day a waiting range is drawn to.
    * - `cell-range-middle`: A cell between a range's ends, beside `cell`.
    * - `cell-range-start`: The cell of a range's first day, beside `cell`.
    * - `day`: The shape inside a cell. A single chosen date is painted on it.
@@ -42931,6 +43477,7 @@ export type CustomElements = {
    * - `periods`: The grid of months or years.
    * - `previous`: The control that moves to the previous month.
    * - `previous-mark`: The glyph on the previous month control, where none is slotted.
+   * - `selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `week`: One row of days.
    * - `weekday`: A column header naming a day of the week. It shows the short name and says the full one.
    *
@@ -42938,7 +43485,11 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `blank`: While no date is chosen.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, the picker holds a date outside `min` and `max` or one it bars, or it is `required`, holds no date, and the reader has answered once or a form has refused it.
+   * - `month-view`: While the months of a year are shown, where `max-view` is set.
+   * - `range-pending`: While a `range` holds its first end and waits for the second.
+   * - `year-view`: While a page of years is shown, where `max-view` is `year`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-date-picker": Partial<
@@ -45552,20 +46103,22 @@ export type CustomElements = {
    *
    * **A date is written in a calendar Date Picker draws**: the locale's own
    * where its months are the Gregorian months, as `th-TH` writes 2569 for 2026,
-   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks one of
-   * the five.
+   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks any of
+   * them, `persian` and `hebrew` included.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
    * - `calendar`: The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-   * `roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-   *
-   * Absent is the locale's own where it is one of the five, such as
-   * `buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-   * for `fa-IR`, so a date written here reads as the same date a Date Picker
-   * beside it shows.
+   * `roc`, or `iso8601`, or a calendar with months of its own, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+   * calendar Date Picker and Date Input draw.
+   *
+   * Absent is the locale's own where its months are the Gregorian months,
+   * such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+   * `persian` for `fa-IR`, so a date written here reads as the same date a
+   * Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405.
    * - `date`: The timestamp, in any format `Date` can parse.
    *
    * An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -45584,6 +46137,9 @@ export type CustomElements = {
    * - `date-style`/`dateStyle`: The locale's own pattern for the date: `full`, `long`, `medium`, or
    * `short`. Set, it stands in for `weekday`, `day`, `month`, `year` and `era`.
    * - `day`: How the day of the month is written, where a date is shown.
+   * - `day-period`/`dayPeriod`: Writes the part of the day in words, such as "in the morning" or "at
+   * night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+   * twelve-hour clock.
    * - `elapsed`: Shows how long ago the timestamp was, in a compact form such as "3h", in
    * place of the date.
    *
@@ -45598,6 +46154,8 @@ export type CustomElements = {
    * Off by default, which draws the date as one run of text, as Shoelace and
    * Web Awesome do. An `elapsed` or `relative` reading is one phrase either
    * way.
+   * - `fractional-second-digits`/`fractionalSecondDigits`: How many digits of a fraction of a second to write after `second`: 1, 2,
+   * or 3, as in 09:41:07.250.
    * - `frozen`: Draws an `elapsed` or `relative` reading once and leaves it, where it
    * would otherwise move on as it goes stale.
    *
@@ -45635,7 +46193,9 @@ export type CustomElements = {
    * - `time-zone`/`timeZone`: The time zone to read the timestamp in.
    *
    * Empty is the runtime's own.
-   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone, in its `long` or `short` form.
+   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+   * Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+   * `longGeneric` or `shortGeneric`, as Pacific Time or PT.
    * - `weekday`: How the weekday is written, where one is shown.
    * - `year`: How the year is written, where a date is shown.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -45666,6 +46226,7 @@ export type CustomElements = {
    * - `day`: The day of the month, with `fields`.
    * - `day-period`: AM or PM, or the locale's word for the part of the day, with `fields`.
    * - `era`: The era, such as AD, with `fields` and `era`.
+   * - `fractional-second`: The fraction of a second, with `fields` and `fractional-second-digits`.
    * - `hour`: The hour, with `fields`.
    * - `minute`: The minute, with `fields`.
    * - `month`: The month, with `fields`.
@@ -46632,6 +47193,7 @@ export type CustomElements = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `pending`: The button is pending: `pending` is set.
+   * - `pressed`: A Button Group in a selection mode has this button pressed.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-icon-button": Partial<
@@ -47518,7 +48080,8 @@ export type CustomElements = {
    * Each item is a `group` with the role description `slide`, named by its
    * `label` or, without one, by its place in the set, such as "2 of 5", as the
    * APG carousel pattern names a slide. The lightbox supplies both words, so they
-   * are translated on the lightbox.
+   * are translated on the lightbox. A `description`, while there is one,
+   * describes the group, so a screen reader says it with the name.
    *
    * An item that is not current is hidden and stays in the DOM, as a `TabPanel`
    * does. Crawlers can read it, it is in the server-rendered markup, and an
@@ -47602,9 +48165,10 @@ export type CustomElements = {
    * buttons that send `--previous`, `--next` and `--close`.
    *
    * **Set `max-zoom` to let a reader zoom into the shown item**, such as `3`.
-   * Two fingers pinch it, a double click or a double tap zooms all the way in
-   * about the point pressed and back out, and once zoomed one pointer drags it
-   * about. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.
+   * Two fingers pinch it, and so does a trackpad pinch or the wheel with Ctrl
+   * held, about the point under the pointer. A double click or a double tap
+   * zooms all the way in about the point pressed and back out, and once zoomed
+   * one pointer drags it about and the wheel moves it. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.
    * The scale and the offset are on the `viewport` part as `--lightbox-zoom`,
    * `--lightbox-pan-x` and `--lightbox-pan-y`, written only while zoomed, and a
    * swipe moves to the next item only while the item is at its own size. With
@@ -47825,6 +48389,8 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `entering`: From the moment the viewer opens until its entrance has finished.
+   * - `exiting`: From the moment the viewer closes until its exit has finished.
    * - `fullscreen`: While the viewer fills the screen.
    * - `idle`: The user has been still long enough for the controls to hide.
    * - `open`: While the viewer is open.
@@ -51418,6 +51984,7 @@ export type CustomElements = {
    * - `time-day`: Format Date's `day`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-day-period`: Format Date's `day-period`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-era`: Format Date's `era`, forwarded for a time drawn as fields. An elapsed time draws none.
+   * - `time-fractional-second`: Format Date's `fractional-second`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-hour`: Format Date's `hour`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-minute`: Format Date's `minute`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-month`: Format Date's `month`, forwarded for a time drawn as fields. An elapsed time draws none.
@@ -55795,6 +56362,10 @@ export type CustomElements = {
    * `min-steps-between-thumbs` keeps them that many steps apart, and the readout
    * joins the two as `range-text` writes them.
    *
+   * A press on a range's track takes the nearest thumb to the point pressed,
+   * and moving the pointer drags it, as React Aria's and Web Awesome's sliders
+   * do. The thumb takes focus, and `change` is sent as the press ends.
+   *
    * `origin` sets where a single thumb's fill starts: at `min`, at the middle of
    * the track, or at `max`. A balance or an offset from zero fills from the
    * middle, as Zag's slider `origin` does. The fill's ends are published as
@@ -55819,7 +56390,7 @@ export type CustomElements = {
    * |---|---|
    * | Right, Up | Moves the thumb up by `step`. |
    * | Left, Down | Moves the thumb down by `step`. |
-   * | Page Up, Page Down | Moves the thumb by a larger step. |
+   * | Page Up, Page Down | Moves the thumb by `page-step`, or by the platform's larger step where it is not set. |
    * | Home, End | Moves the thumb to its lowest or highest value. |
    *
    * Under `readonly` none of these move the thumb, and Tab still reaches it.
@@ -55880,6 +56451,9 @@ export type CustomElements = {
    * - `origin`: Where a single thumb's fill starts: `start` at `min`, `center` at the
    * middle of the track, or `end` at `max`. Absent is `start`. A range fills
    * between its thumbs and ignores it.
+   * - `page-step`/`pageStep`: How far Page Up and Page Down move a thumb, in the slider's own units, as
+   * React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+   * to the platform, which moves a tenth of the track.
    * - `range`: Adds a second thumb, so the value is a pair.
    *
    * The pair is one string, `"10,50"`, which is what `value` and
@@ -56112,6 +56686,8 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `dragging`: A thumb is being dragged, by its thumb or from a press on the track.
+   * - `focus-visible`: A thumb has focus that the keyboard brought, where the browser draws a focus ring.
    * - `invalid`: The slider has an error to show, from the browser's validation or from your `feedback`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -57275,6 +57851,10 @@ export type CustomElements = {
    * region. The current stage's button carries `aria-current="step"`, and only
    * the button, so the state is said once, on the control.
    *
+   * A stage's `content`, while it holds anything, is a group named by the
+   * stage's name, so a screen reader moving into it hears which stage it
+   * belongs to.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
@@ -58321,10 +58901,18 @@ export type CustomElements = {
    * the tab list lands on the panel's first link or control where there is one,
    * and on the panel itself where there is none.
    *
+   * **Set `lazy` for a panel that is expensive to draw.** Its content waits in a
+   * `<template>` inside it, and goes into the panel the first time the panel is
+   * shown, so it costs nothing until a reader opens that tab. Once in, it stays.
+   * The panel sends `helix-load` at the same moment, for content your code
+   * renders itself.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `lazy`: Whether the panel's content waits in a `<template>` until the panel is
+   * first shown.
    * - `selected`: Whether this panel is the visible one.
    * - `value`: Pairs the panel with the tab of the same value.
    * - `label`: The name of the panel, which is the text of the tab that opens it.
@@ -58358,11 +58946,17 @@ export type CustomElements = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Events
+   *
+   * Events that will be emitted by the component.
+   *
+   * - `helix-load`: Fired the first time a `lazy` panel is shown, once its template's content is in.
+   *
    * ## Slots
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The panel's content.
+   * - `(default)`: The panel's content. Under `lazy`, a `<template>` holding it.
    *
    * ## CSS Parts
    *
@@ -58374,6 +58968,7 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `loaded`: Once a `lazy` panel has been shown and its content is in.
    * - `selected`: While its tab is the one selected.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -58423,9 +59018,9 @@ export type CustomElements = {
    * | Enter, Space | Selects the tab with focus, or follows its link. |
    * | Tab | Leaves the list for the selected panel. |
    *
-   * Removing the selected tab selects the first enabled tab that is left, and
-   * `active` says so, with `helix-activate`. Where the removed tab had focus,
-   * focus moves to the tab now selected.
+   * Removing the selected tab selects the enabled tab beside it, the next one
+   * or else the one before, and `active` says so, with `helix-activate`. Where
+   * the removed tab had focus, focus moves to the tab now selected.
    *
    * **More tabs than fit.** With `scroll-controls`, a strip that scrolls shows a
    * button at each end it can scroll toward, as Web Awesome's tab group does,
@@ -58531,6 +59126,8 @@ export type CustomElements = {
    * - `(default)`: The tabs, as direct children of this element.
    * - `indicator`: A mark of your own, drawn inside the `indicator` part, where `--indicator-x`, `--indicator-y`, `--indicator-inline-size` and `--indicator-block-size` reach it.
    * - `panels`: The panels, as direct children of this element. Panels inside a wrapper are not paired with tabs, because pairing reads only the direct children.
+   * - `scroll-end-icon`: Replaces the glyph on the button that scrolls the strip toward its end.
+   * - `scroll-start-icon`: Replaces the glyph on the button that scrolls the strip toward its start.
    *
    * ## Methods
    *
@@ -58552,7 +59149,9 @@ export type CustomElements = {
    * - `indicator`: The marker that moves to the selected tab. It carries the selected tab's place and size as `--indicator-x`, `--indicator-y`, `--indicator-inline-size` and `--indicator-block-size`, and `data-placed` once it has been placed, for a mark you draw and animate yourself.
    * - `panels`: The panel container.
    * - `scroll-end`: The button that scrolls the strip toward its end, shown under `scroll-controls` while there is more that way.
+   * - `scroll-end-mark`: The glyph on that button, where none is slotted.
    * - `scroll-start`: The button that scrolls the strip toward its start, shown under `scroll-controls` while there is more that way.
+   * - `scroll-start-mark`: The glyph on that button, where none is slotted.
    * - `tabs`: The tab list.
    *
    * ## CSS States
@@ -58577,8 +59176,8 @@ export type CustomElements = {
    * can: a press on its `dismiss` mark, or Delete or Backspace while the tab
    * has focus, sends `helix-dismiss`. The tab does not remove itself, because
    * your code owns the set, so remove the tab and its panel in your handler.
-   * Focus moves to the tab beside it, and the tab set selects a tab that is
-   * left.
+   * Focus moves to the tab beside it, and where the tab was selected, the tab
+   * set selects that same tab.
    * The tab says the key through `aria-keyshortcuts`, and the mark is for the
    * pointer, hidden from screen readers.
    *
@@ -58635,6 +59234,7 @@ export type CustomElements = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The tab's label.
+   * - `dismiss-icon`: Replaces the glyph on the mark that closes a `dismissible` tab.
    *
    * ## Methods
    *
@@ -58659,6 +59259,7 @@ export type CustomElements = {
    * Custom selectors for styling elements within the component.
    *
    * - `dismiss`: The mark a pointer presses to close a `dismissible` tab.
+   * - `dismiss-mark`: The glyph on that mark, where none is slotted.
    * - `tab`: The tab itself.
    *
    * ## CSS States
@@ -59211,20 +59812,25 @@ export type CustomElements = {
    * `seconds`, because that is what the form
    * submits, what `min` and `max` compare against, and what sorts correctly as a
    * string. While idle, the field shows the time in the user's locale format.
-   * Once the caret is in the field, it shows the value itself, because a
-   * formatted time such as `2:30 PM` cannot be typed back and `Intl` has no
-   * parser for it.
+   * Once the caret is in the field, it shows the value itself. You can type
+   * `14:30`, or a time as you write one, such as `2:30 PM`, `2.30pm`, or
+   * `14h30`, and the field reads it as you leave it, with AM and PM in the
+   * locale's words.
    *
    * Typing sends `input` on each keystroke and `change` when you leave the
    * field. The trigger and ArrowDown open the list, and so does a press into the
-   * field; Tab into the field opens nothing. In the list, the arrow keys, typed digits and PageUp and PageDown
+   * field; Tab into the field opens nothing. The text field is a `combobox`
+   * with `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, since
+   * Down opens the list from it. In the list, the arrow keys, typed digits and PageUp and PageDown
    * move through the times, and Enter, Space or a click chooses one and closes
    * the panel. With `variant="wheels"` each wheel moves the time as you turn it,
    * the panel stays open, and Enter or Escape closes it.
    *
    * With `segmented`, the field is a row of segments in place of the text: an
    * hour, a minute, and AM or PM where the clock has them, each set with digits
-   * or the arrow keys. Alt+Down opens the list from a segment.
+   * or the arrow keys. Alt+Down opens the list from a segment. A `range` is two
+   * rows with a dash between them, the start and the end, and `multiple` keeps
+   * the text.
    *
    * Text that is not a time gives the form an empty value, as a native time
    * field does, and `value` keeps the text so it can be corrected.
@@ -59256,6 +59862,10 @@ export type CustomElements = {
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `disable-times`/`disableTimes`: Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
    *
    * Handed to the list, which offers them as unavailable, and checked against
@@ -59304,6 +59914,8 @@ export type CustomElements = {
    * never something this element would refuse to read back.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the list, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-times` bars a time.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no time, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`.
    * - `variant`: Whether the panel shows one list of times or a column for each part of the
    * time.
    *
@@ -59326,6 +59938,10 @@ export type CustomElements = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -59477,6 +60093,7 @@ export type CustomElements = {
    * - `helix-before-change`: Fired before the time changes. Cancelable: canceling it stops the change and leaves the decision to you.
    * - `helix-before-close`: Fired before the list closes. Cancelable: canceling it keeps the list open and leaves the decision to you.
    * - `helix-before-open`: Fired before the list opens. Cancelable: canceling it keeps the list closed and leaves the decision to you.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    * - `toggle`: Fired after the list opens or closes, with `newState` and `oldState`.
    *
@@ -59484,6 +60101,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the time, before the trigger, such as a clear button.
    * - `feedback`: The message that says what is wrong with the value.
    * - `hint`: Help under the field.
@@ -59557,6 +60175,7 @@ export type CustomElements = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a time.
    * - `control`: The text input.
    * - `feedback`: The message that says what is wrong with the value.
    * - `field`: The box that holds the text and the trigger.
@@ -59602,6 +60221,7 @@ export type CustomElements = {
    * - `picker-option-item-selected`: The row of a chosen time: the one time, or either end of a range.
    * - `picker-option-label`: The option's label.
    * - `picker-option-text`: The label and the caption, as one column.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of times held beyond the ones shown. A `<button>` with `expandable`, and a `<span>` without it.
    * - `segment`: One part of the time, an hour, a minute, a second or AM and PM, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -59622,6 +60242,7 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no time.
    * - `invalid`: The control has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: While the clock is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -59675,7 +60296,10 @@ export type CustomElements = {
    * host's `aria-label` or its `aria-labelledby`. A development build warns
    * where all four are empty. The list is described by the hint, or by the
    * message in `feedback` in its place, and carries `aria-multiselectable` with
-   * a `mode` and `aria-invalid` while `feedback` says what is wrong. The wheels
+   * a `mode`. It carries `aria-invalid` while `feedback` says what is wrong,
+   * while it holds a time outside `min` and `max` or one the picker does not
+   * offer, and, for a `required` picker with no time, once the reader has
+   * chosen one or a form has refused the picker. The wheels
    * are a `group` with that name, holding one `listbox` per wheel, named "Hour",
    * "Minute", "Second" and "AM/PM" in the page's language, and each described
    * the same way.
@@ -60033,7 +60657,7 @@ export type CustomElements = {
    * - `list-loading`: The text shown while the options load.
    * - `list-search`: The region that holds the filter field.
    * - `list-search-field`: The filter field.
-   * - `option`: One time in the list. It carries `data-between` inside a range.
+   * - `option`: One time in the list. It carries `data-between` inside a range, and inside the run to the time under the pointer while a range waits for its second end.
    * - `option-between`: A time inside a chosen range, excluding its ends, beside `option`.
    * - `option-description`: The caption under the time's label, when there is one.
    * - `option-item`: The row.
@@ -60047,7 +60671,8 @@ export type CustomElements = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `blank`: While no time is chosen.
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, or the list carries `aria-invalid`.
+   * - `range-pending`: While a `range` holds its first time and waits for the second.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-time-picker": Partial<
@@ -60277,8 +60902,9 @@ export type CustomElements = {
    *
    * **Each item runs its own timer.** A timer held by the region would restart
    * with each new message, and the last of three messages would stay for nine
-   * seconds. It pauses while the pointer or focus is on the message, and while
-   * the page is hidden, so a message is not spent in a background tab.
+   * seconds. It pauses while the pointer or focus is on the message or anywhere
+   * in the region's stack, and while the page is hidden, so a message is not
+   * spent in a background tab.
    *
    * **Each message is an `alertdialog` named by its words**, which is how a reader
    * who moves into the stack hears which message they are on. Give it a
@@ -60287,10 +60913,11 @@ export type CustomElements = {
    * says each message once as it arrives, a `danger` one assertively, so a
    * message is never a live region of its own.
    *
-   * A touch or a pen swipes a message toward the end of the line, and past
-   * halfway, or quickly, dismisses it through the same `helix-dismiss` as its
-   * control. While it moves, the distance is on the `item` part as
-   * `--toast-swipe-x`.
+   * A touch or a pen swipes a message toward the end of the line, or toward the
+   * edge the region's `swipe-direction` names, and past halfway, or quickly,
+   * dismisses it through the same `helix-dismiss` as its control. While it
+   * moves, the distance is on the `item` part as `--toast-swipe-x` or
+   * `--toast-swipe-y`.
    *
    * **Escape dismisses the message holding focus**, through the same
    * `helix-dismiss`, and focus moves to the next message.
@@ -60392,6 +61019,7 @@ export type CustomElements = {
    *
    * - `--toast-duration`: How long this message stays, in milliseconds, for a progress hint.
    * - `--toast-swipe-x`: How far a swipe has moved the message across, in pixels, toward the right.
+   * - `--toast-swipe-y`: How far a swipe has moved the message down, in pixels, under a `swipe-direction` of `top` or `bottom`.
    *
    * ## CSS Parts
    *
@@ -60413,7 +61041,7 @@ export type CustomElements = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `closed`: The message has been dismissed and is hidden, or leaving.
-   * - `paused`: The dismiss timer is paused, while a pointer or focus is on the message, or while the page is hidden.
+   * - `paused`: The dismiss timer is paused, while a pointer or focus is on the message or in the stack, or while the page is hidden.
    * - `waiting`: The region holds the message back, past its `max-visible`, until a message before it goes.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -60452,7 +61080,12 @@ export type CustomElements = {
    * to render them from: it appends a message of the region's own tier and
    * removes it once it has been dismissed and has finished leaving. Messages
    * you render yourself stay yours, and the region never removes them. A touch
-   * or a pen swipes a message away toward the end of the line.
+   * or a pen swipes a message away toward the end of the line, or toward the
+   * edge `swipe-direction` names.
+   *
+   * **Every message's timer waits while a pointer or focus is in the stack**, as
+   * React Aria's and Radix's regions do, so a reader moving from one message to
+   * the next does not lose the one behind them.
    *
    * **The stack is in the top layer.** The `region` part is a `popover="manual"`
    * shown while a message is showing, and shown again above a modal dialog that
@@ -60517,6 +61150,8 @@ export type CustomElements = {
    * consumer's server markup does not have. A sheet carries the resting
    * arrangement in its own `:host` rule and the selectors describe only the
    * departures, which is what `orientation` does.
+   * - `swipe-direction`/`swipeDirection`: The edge a touch or a pen swipes a message toward to dismiss it: `end`,
+   * the end of the line, or `start`, `top` or `bottom`. Unset is `end`.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -60621,7 +61256,7 @@ export type CustomElements = {
    * | Right, Down | Moves to the next item, from the last back to the first. In a single group, chooses it. |
    * | Left, Up | Moves to the item before, from the first round to the last. In a single group, chooses it. |
    * | Home, End | Moves to the first or the last item. In a single group, chooses it. |
-   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. |
+   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. With `allow-empty-selection`, takes back the chosen item. |
    *
    * Left and Right swap on a right-to-left page, and a disabled item is passed
    * over. A single group is a `radiogroup` of items with `role="radio"` and
@@ -60633,6 +61268,11 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `allow-empty-selection`/`allowEmptySelection`: Whether a press on the chosen item, or Space or Enter on it, takes it
+   * back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+   * Radix's `ToggleGroup` do in a single group. Absent, a single group always
+   * keeps its choice once it has one, as a radio group does. A multiple group
+   * releases a pressed item either way.
    * - `label-placement`/`labelPlacement`: Where the group's label sits. `start` puts it on the track's line.
    *
    * Absent is above, which is what a field looks like and what almost every
@@ -60977,13 +61617,13 @@ export type CustomElements = {
    *
    * Custom selectors for styling elements within the component.
    *
-   * - `item`: The radio button.
+   * - `item`: The button: a radio in a group where one is chosen, and a button with `aria-pressed` on its own or in a group where several can be.
    *
    * ## CSS States
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `pressed`: The item is pressed, in a group where several can be.
+   * - `pressed`: The item is pressed, on its own or in a group where several can be.
    * - `selected`: The item is chosen.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -61385,6 +62025,17 @@ export type CustomElements = {
    * least distance that brings it on screen, so the stop that points at it is
    * on screen too.
    *
+   * **A stop's `effect` runs as the tour reaches it**, before it is shown, and
+   * the stop waits for a promise it returns, with `:state(preparing)` on the
+   * tour meanwhile. A function it returns runs when the tour leaves the stop.
+   *
+   * **A press outside the current stop and its target does nothing by
+   * default**, so a reader can use the page the tour is describing. Set
+   * `outside-press="close"` to end the tour on one, through `helix-before-close`
+   * as Skip does, or `outside-press="block"` to refuse it, so the stop and its
+   * target are all a pointer can reach while the tour runs, as Zag's
+   * `preventInteraction` does.
+   *
    * **Keyboard.** Focus is on the current stop's panel, which is not in the
    * `Tab` order itself.
    *
@@ -61422,6 +62073,9 @@ export type CustomElements = {
    * `undefined` until somebody sets one.
    * - `label`: The tour's name, read by screen readers, such as "Getting started".
    * - `next-label`/`nextLabel`: Label for the control that goes on.
+   * - `outside-press`/`outsidePress`: What a press outside the current stop and its target does while the tour
+   * runs. Unset, nothing: the page stays usable. `close` ends the tour, as
+   * Skip does, and `block` refuses the press.
    * - `progress`: Draws each stop's place in the run in its panel, as well as saying it.
    * - `progress-label`/`progressLabel`: Each stop's place in the run, with `{index}` and `{count}` filled in and
    * written in the locale. Translate it with the rest of your text.
@@ -61525,6 +62179,7 @@ export type CustomElements = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `open`: While the tour is running.
+   * - `preparing`: While the tour waits for the current stop's `effect` before showing the stop.
    * - `waiting`: While the tour waits at a `wait` stop for its target to be on the page.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -61558,6 +62213,13 @@ export type CustomElements = {
    * get Back, Next, and Skip, already wired. Slot your own `actions` and drive
    * them with `next()`, `back()`, and `skip()` on the root.
    *
+   * **Set `effect` to prepare the page for a stop**, such as opening the menu
+   * it points into or loading what it describes. It is a function, set from
+   * script, that the tour runs as it reaches the stop. Return a promise and the
+   * stop waits for it, and the tour has `:state(preparing)` meanwhile; return a
+   * function, or resolve to one, and the tour runs it when it leaves the stop.
+   * Zag's tour step has the same `effect`.
+   *
    * **`for` is an id, as with `Tooltip`**, so you can point at a target elsewhere
    * on the page from markup. It resolves against the stop's root node, so a stop
    * inside a shadow tree points at a target in that tree.
@@ -61599,6 +62261,8 @@ export type CustomElements = {
    *
    * Reflected, because the styled tier places a dialog and a floating panel by
    * it, and unset at rest, so no default is written onto the host.
+   * - `effect`: Run as the tour reaches the stop, before it is shown: see the description
+   * above. A function, so it is set from script and has no attribute. (property only)
    * - `target`: The element the stop points at, or `null` when no element has the `for` id. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -61681,6 +62345,8 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `entering`: From the moment the stop is shown until its entrance has finished.
+   * - `exiting`: From the moment the stop is left until its exit has finished.
    * - `placed-bottom`: The panel sits below its target.
    * - `placed-left`: The panel sits to the left of its target.
    * - `placed-right`: The panel sits to the right of its target.
@@ -63729,12 +64395,21 @@ export type CustomElementsSolidJs = {
    *
    * **Set `fold-below` to fold the middle region on a narrow screen.** Below that
    * many pixels of the bar's own width, the middle region is hidden behind a
-   * toggle at the end of the bar, named by `menu-label`. The toggle says whether
-   * the region is open with `aria-expanded`, and the region opens below the row.
-   * Escape closes it and puts focus back on the toggle. The custom state
-   * `folded` is on the host while the bar is that narrow, and `open` while the
-   * folded region is open. A server serves the bar unfolded, and the browser
-   * folds it once it has measured it.
+   * toggle at the end of the bar, named by `menu-label`, or at its start with
+   * `toggle-placement="start"`. The toggle says whether the region is open with
+   * `aria-expanded`, and the region opens below the row. The region follows the
+   * toggle's region in focus order, so Tab from the toggle at the end goes into
+   * the open region. The custom state `folded` is on the host while the bar is
+   * that narrow, and `open` while the folded region is open. A server serves the
+   * bar unfolded, and the browser folds it once it has measured it.
+   *
+   * **`open` says whether the folded region is open, and setting it opens or
+   * closes the region.** `requestOpen(true)` and `requestOpen(false)` do the same
+   * and send `helix-before-open` or `helix-before-close` first, which you can
+   * cancel, and `toggleOpen()` asks for the opposite. `toggle` follows every
+   * change. The region closes on Escape, which puts focus back on the toggle,
+   * when focus moves to something outside the header, and on a press outside
+   * it. A bar that widens past `fold-below` closes its region.
    *
    * The host is the page's `banner` landmark. Placed inside `main`, `article`,
    * `aside`, `nav` or `section`, it is a plain box instead, as a native
@@ -63769,6 +64444,24 @@ export type CustomElementsSolidJs = {
    * - `menu-label`/`menuLabel`: The name of the toggle that opens a folded middle region.
    * - `scroller`: The id of the element whose scrolling lifts the bar, for an app shell that
    * scrolls a container instead of the window. Unset is the window.
+   * - `toggle-placement`/`togglePlacement`: Where the toggle that opens a folded middle region sits: at the end of the
+   * bar, after the trailing content, or with `start`, before the leading
+   * content.
+   *
+   * Optional, so the resting bar writes no attribute onto the host.
+   * - `default-open`/`defaultOpen`: Whether the element starts open. Ignored once `open` is written.
+   * - `open`: Whether the element is open.
+   *
+   * One property, not two, so `dialog.open` answers the question anyone
+   * asking it meant. Writing always applies; `<helix-dialog open>` is the
+   * same statement in markup.
+   *
+   * **Not reflected, and that is required rather than tidy.** Reflection
+   * writes the resolved state back as an attribute, so an element that opened
+   * itself would put `open` on its own host: cloned, serialized for
+   * hydration, or diffed by a framework, it comes back holding whatever the
+   * last reader did rather than what the author wrote. `:state(open)` carries
+   * the resolved state for stylesheets, which is what the mirror is for.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -63794,7 +64487,10 @@ export type CustomElementsSolidJs = {
    *
    * Events that will be emitted by the component.
    *
+   * - `helix-before-close`: The folded region is about to close. Cancelable: cancel it to keep it open.
+   * - `helix-before-open`: The folded region is about to open. Cancelable: cancel it to keep it closed.
    * - `helix-scrolled`: Fired when the page crosses the scroll threshold, with the new state. A custom state cannot be observed the way an attribute can, so listen for this event to follow it. The event uses the header's own threshold and hysteresis, so you do not need a second scroll listener.
+   * - `toggle`: The folded region opened or closed. The event carries `newState` and `oldState`.
    *
    * ## Slots
    *
@@ -63805,6 +64501,20 @@ export type CustomElementsSolidJs = {
    * - `menu-icon`: Replaces the glyph inside the toggle that opens a folded middle region.
    * - `start`: Leading content, usually a wordmark.
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `requestOpen(next: boolean) => boolean`: Requests that the element open or close, and returns whether the change
+   * was applied.
+   *
+   * Announces before it acts, so `preventDefault()` on the `helix-before-open` or
+   * `helix-before-close` is a refusal and nothing moves. Nobody refusing means the
+   * element opens or closes itself, whether or not a consumer declared
+   * `open`: a declared property is a seed and a correction, and a consumer
+   * who wants the decision for themselves refuses it and assigns their own.
+   * - `toggleOpen() => boolean`: Requests the opposite of the current state.
+   *
    * ## CSS Parts
    *
    * Custom selectors for styling elements within the component.
@@ -65208,11 +65918,15 @@ export type CustomElementsSolidJs = {
    * appearance and size.
    *
    * **Buttons that stay pressed.** With `selection-mode`, each button with a
-   * `value` is a toggle button: a press presses or releases it, and it says so
-   * with `aria-pressed`. `single` keeps one pressed at a time, and a press on the
-   * pressed one releases it. `multiple` lets any number be pressed. `value` is
-   * the pressed values, comma separated. A press sends a cancelable
-   * `helix-before-change` with the value it would leave, then `change`.
+   * `value` is a toggle button: a press presses or releases it. `multiple` lets
+   * any number be pressed, and each button says so with `aria-pressed`. `single`
+   * keeps one pressed at a time: the group is a `radiogroup` and each button a
+   * `radio` that says so with `aria-checked`, as React Aria's toggle button
+   * group is. A press on the pressed one releases it, unless
+   * `disallow-empty-selection` keeps one pressed. `value` is the pressed values,
+   * comma separated. A press sends a cancelable `helix-before-change` with the
+   * value it would leave, then `change`. A pressed Helix button has
+   * `:state(pressed)` on its own element.
    *
    * The pressed state is written on the control inside each button's shadow
    * root, so the markup you rendered is never changed and a framework hydrating
@@ -65240,15 +65954,18 @@ export type CustomElementsSolidJs = {
    * | Space, Enter | Presses or releases the focused button. |
    *
    * Left and Right swap on a right-to-left page, and a disabled button is
-   * passed over. In a selection mode the group is a `toolbar`, with
+   * passed over. Under `multiple` the group is a `toolbar`, with
    * `aria-orientation` under `orientation="vertical"`. Inside a toolbar it stays
    * a named `group`, and the toolbar's own arrow keys walk its buttons, so a
-   * reader meets one toolbar.
+   * reader meets one toolbar. Under `single` it is a `radiogroup` either way.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `disallow-empty-selection`/`disallowEmptySelection`: Keeps at least one button pressed once one is, as React Aria's
+   * `disallowEmptySelection`: a press that would leave none pressed is
+   * refused.
    * - `label`: The group's name, read by screen readers.
    *
    * On the host through internals, so an author's `aria-label` still overrides
@@ -65617,6 +66334,7 @@ export type CustomElementsSolidJs = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `pending`: The button is pending: `pending` is set.
+   * - `pressed`: A Button Group in a selection mode has this button pressed.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-button": Partial<
@@ -69838,6 +70556,7 @@ export type CustomElementsSolidJs = {
    * - `copied`: The moment after a successful copy, while `copied-label` names the button.
    * - `failed`: The moment after a press that put nothing on the clipboard, while `error-label` names the button.
    * - `pending`: The button is pending: `pending` is set.
+   * - `pressed`: A Button Group in a selection mode has this button pressed.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-copy-button": Partial<
@@ -70344,17 +71063,24 @@ export type CustomElementsSolidJs = {
    * gives a picker and locale formatting but allows almost no styling, so the
    * field is a text field. Typing sends `input` on each keystroke and `change`
    * when you leave the field, as a text field does. A date picked from the
-   * calendar sends both.
+   * calendar sends both. The field reads ISO, `2026-08-04`, and a date written
+   * in the order, the digits, and the month names of `locale`, `8/4/2026` or
+   * `Aug 4, 2026` in `en-US` and `4.8.2026` in `de-DE`, which becomes the value
+   * as you leave the field.
    *
    * The trigger and ArrowDown open the calendar with focus on the selected day,
    * Tab moves between the calendar's controls without leaving it, and Escape
    * closes it and returns focus to the field. A press into the field opens the
    * calendar too. Tab into the field opens nothing, and Tab out of the field
-   * closes the calendar.
+   * closes the calendar. The text field is a `combobox` with
+   * `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, as in the
+   * APG date picker combobox, since Down opens the calendar from it.
    *
    * With `segmented`, the field is a row of segments in place of the text: a
    * month, a day and a year in the order the locale writes them, each set with
-   * digits or the arrow keys. Alt+Down opens the calendar from a segment.
+   * digits or the arrow keys. Alt+Down opens the calendar from a segment. A
+   * `range` is two rows with a dash between them, the start and the end, as
+   * React Aria's DateRangePicker draws them, and `multiple` keeps the text.
    *
    * Text that is not a date gives the form an empty value, as a native date
    * field does, and `value` keeps the text so it can be corrected.
@@ -70384,27 +71110,39 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens.
+   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens,
+   * such as `bday`.
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all: hardcoding `off` here means a birthday or a
-   * postal code can never be filled in for a reader.
-   * - `calendar`: The calendar the written date and the calendar's days are in: `gregory`,
-   * `buddhist`, `japanese`, `roc`, or `iso8601`.
-   *
-   * Absent is the locale's own where it is one of the five, and `gregory` for
-   * every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-   * every calendar, and a focused field is ISO in every calendar. In
-   * `segmented`, the segments are the Gregorian day, month, and year, in the
-   * order the locale writes them, or ISO order for `iso8601`.
+   * postal code can never be filled in for a reader. With `segmented`, a
+   * hidden native date input carries it, since no browser fills the segments.
+   * - `calendar`: The calendar the written date, the segments, and the calendar's days are
+   * in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+   * with months of its own that Date Picker's `calendar` names, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+   *
+   * Absent is the locale's own where its months are the Gregorian months, and
+   * `gregory` for every other, as Date Picker's `calendar` is. The value is
+   * `YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+   * calendar. In `segmented`, the segments are the day, month, and year as
+   * the calendar counts them, in the order the locale writes them: Mehr 14,
+   * 1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+   * Gregorian months they are the Gregorian day, month, and year, or ISO order
+   * for `iso8601`.
    * - `calendar-label`/`calendarLabel`: The name of the calendar's grid of days, read by screen readers.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `date-style`/`dateStyle`: How a date is written in the field: `short` through `full`, or ISO.
    *
    * **The field renders when it is idle and holds the value when it is being
    * edited.** A written date is a rendering, and a document being edited must
    * not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-   * not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-   * locale is how a field ends up rejecting what it just displayed.
+   * not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+   * edit. The field does read a date typed in the locale's order and digits as
+   * you leave it, which covers what a reader types.
    *
    * The way out is not to choose between the two but to separate them in time.
    * Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -70472,6 +71210,9 @@ export type CustomElementsSolidJs = {
    *
    * **The name goes in**, so a row of them is heard as which one each
    * removes rather than as "Remove" said once per date.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the dates chosen in the calendar, with
+   * `{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+   * `selection-label` says.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -70479,8 +71220,13 @@ export type CustomElementsSolidJs = {
    * where there is one and from 1 January 1970 where there is not, which is the
    * platform's base.
    * - `step-mismatch-message`/`stepMismatchMessage`: The message shown when a date is not on `step`.
+   * - `time-zone`/`timeZone`: The time zone today is read in, such as `America/New_York`, handed to the
+   * calendar: the day marked today, and the month an empty field opens on.
+   * Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the calendar, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-dates` or `disable-days` bars a date.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no date, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`.
    * - `year-view-label`/`yearViewLabel`: The name of the calendar's heading where it shows a page of years, with
    * `{heading}` filled in.
    * - `empty-message`/`emptyMessage`: What a row of segments reports when the field is required and every
@@ -70491,6 +71237,10 @@ export type CustomElementsSolidJs = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -70651,6 +71401,7 @@ export type CustomElementsSolidJs = {
    * - `helix-before-change`: Fired before the date changes. Cancelable: call `preventDefault()` to keep the current date.
    * - `helix-before-close`: Fired before the calendar closes. Cancelable: call `preventDefault()` to keep it open.
    * - `helix-before-open`: Fired before the calendar opens. Cancelable: call `preventDefault()` to keep it closed.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    * - `toggle`: Fired when the calendar opens or closes, with `newState` and `oldState`.
    *
@@ -70658,6 +71409,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the date, before the trigger, such as a clear button.
    * - `feedback`: The error message under the field.
    * - `hint`: The help text under the field.
@@ -70733,6 +71485,7 @@ export type CustomElementsSolidJs = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a date.
    * - `control`: The text input.
    * - `date`: One held date, as a tag, in `multiple`.
    * - `date-cell`: The tag's grid cell, which a tag draws only inside a tag group.
@@ -70774,8 +71527,10 @@ export type CustomElementsSolidJs = {
    * - `picker-periods`: The grid of months or years.
    * - `picker-previous`: The control that moves to the previous month.
    * - `picker-previous-mark`: The icon on the previous month control.
+   * - `picker-selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `picker-week`: One row of days.
    * - `picker-weekday`: A column header naming a day of the week.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of dates beyond the ones shown. It is a `<button>` with `expandable` and a `<span>` without it.
    * - `segment`: One part of the date, a year, a month or a day, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -70789,6 +71544,7 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no date.
    * - `invalid`: The field has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: The calendar is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -70811,9 +71567,11 @@ export type CustomElementsSolidJs = {
    * **Dates are `YYYY-MM-DD` strings, and every calculation is in UTC**, because
    * a local-time `Date` shifts across a time zone or daylight-saving boundary.
    *
-   * **The days are the Gregorian calendar's**, written in `calendar`: the
-   * locale's own where its months are the Gregorian months, as `th-TH` writes
-   * 2569 for 2026, and `gregory` where they are not, as for `fa-IR`.
+   * **The months are the ones `calendar` counts**: the Gregorian months for the
+   * locale's own calendar where its months are the Gregorian months, as `th-TH`
+   * writes 2569 for 2026, and `gregory` where they are not, as for `fa-IR`
+   * with no `calendar`. Name a calendar with months of its own, such as
+   * `persian`, and every view counts its days, months, and years from `Intl`.
    *
    * `month` sets which month the grid shows, separately from `value`, so paging
    * selects nothing and you can control the view. When unset, it follows the
@@ -70821,7 +71579,14 @@ export type CustomElementsSolidJs = {
    *
    * `mode` sets how many dates are held. Unset holds one, `range` holds two and
    * marks the dates between them, and `multiple` toggles each date. All three
-   * read and write the same comma-separated `value`.
+   * read and write the same comma-separated `value`. With a `mode`, the grid
+   * carries `aria-multiselectable`. While a range holds one end, the grid draws
+   * the range to the day under the pointer or the focus, marking those cells
+   * `data-range-preview`.
+   *
+   * The chosen date, range, or count of dates is the grid's description, in a
+   * region screen readers announce when it changes, as React Aria's calendars
+   * do. `selection-label` words it.
    *
    * `max-view` makes the heading a button that steps back to the months of the
    * year, and with `year` to a page of years, as Zag's date picker does. The
@@ -70856,14 +71621,16 @@ export type CustomElementsSolidJs = {
    * `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
    * for `fa-IR`.
    *
-   * `persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-   * `coptic`, and `indian` draw a calendar with months of its own, as React
-   * Aria's calendars do: each grid is one of that calendar's months, the
-   * Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-   * Previous, Next and the page keys move by those months. `month` and
+   * `persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+   * `islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+   * `indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+   * as React Aria's calendars do: each grid is one of that calendar's months,
+   * the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+   * month included, and Previous, Next and the page keys move by those
+   * months. With `max-view`, the months view shows that calendar's year, of
+   * twelve or thirteen months, and the years view its years. `month` and
    * `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-   * heading stays text, as the months and years views are drawn in Gregorian
-   * months only. The value is `YYYY-MM-DD` in every calendar.
+   * value is `YYYY-MM-DD` in every calendar.
    * - `default-month`/`defaultMonth`: The month to open on when `month` is not set.
    * - `disable-dates`/`disableDates`: Dates that cannot be chosen, as `YYYY-MM-DD`, separated by commas or
    * spaces.
@@ -70926,6 +71693,11 @@ export type CustomElementsSolidJs = {
    * value and stays reachable, which is what a form showing a value somebody
    * else set needs.
    * - `required`: Stops the form from submitting while no date is chosen.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the chosen dates: the grid's
+   * description, said again whenever the dates change. `{kind}` is `date`,
+   * `start` while a range holds one end, `range`, or `dates` for `multiple`.
+   * `{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+   * many dates are chosen.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -71080,6 +71852,13 @@ export type CustomElementsSolidJs = {
    * Date Input calls this when its trigger opens the calendar, which is where
    * the APG date picker dialog puts focus. The host is not focusable, so a
    * plain `focus()` on it did nothing and focus stayed on the trigger.
+   * - `showChosen() => void`: Shows the days again, on the month of the chosen date, with the tab stop
+   * on that date, forgetting the month and the day the reader browsed to.
+   *
+   * Date Input calls it each time its panel opens, which is where the APG
+   * date picker dialog puts focus. Measured before this: from August 4, two
+   * presses of Page Down, Escape, and Down again opened on October 4.
+   * A `month` you set stays until the reader pages away from it.
    * - `requestValue(next: string) => boolean`: Refuses every change while read-only. See `readOnly`.
    * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
    * where there is no `default-value`.
@@ -71143,7 +71922,7 @@ export type CustomElementsSolidJs = {
    * Custom selectors for styling elements within the component.
    *
    * - `cell`: One column of a week row. A range is painted on the cells.
-   * - `cell-range-end`: The cell of a range's last day, beside `cell`.
+   * - `cell-range-end`: The cell of a range's last day, beside `cell`, or of the day a waiting range is drawn to.
    * - `cell-range-middle`: A cell between a range's ends, beside `cell`.
    * - `cell-range-start`: The cell of a range's first day, beside `cell`.
    * - `day`: The shape inside a cell. A single chosen date is painted on it.
@@ -71169,6 +71948,7 @@ export type CustomElementsSolidJs = {
    * - `periods`: The grid of months or years.
    * - `previous`: The control that moves to the previous month.
    * - `previous-mark`: The glyph on the previous month control, where none is slotted.
+   * - `selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `week`: One row of days.
    * - `weekday`: A column header naming a day of the week. It shows the short name and says the full one.
    *
@@ -71176,7 +71956,11 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `blank`: While no date is chosen.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, the picker holds a date outside `min` and `max` or one it bars, or it is `required`, holds no date, and the reader has answered once or a form has refused it.
+   * - `month-view`: While the months of a year are shown, where `max-view` is set.
+   * - `range-pending`: While a `range` holds its first end and waits for the second.
+   * - `year-view`: While a page of years is shown, where `max-view` is `year`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-date-picker": Partial<
@@ -73818,20 +74602,22 @@ export type CustomElementsSolidJs = {
    *
    * **A date is written in a calendar Date Picker draws**: the locale's own
    * where its months are the Gregorian months, as `th-TH` writes 2569 for 2026,
-   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks one of
-   * the five.
+   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks any of
+   * them, `persian` and `hebrew` included.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
    * - `calendar`: The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-   * `roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-   *
-   * Absent is the locale's own where it is one of the five, such as
-   * `buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-   * for `fa-IR`, so a date written here reads as the same date a Date Picker
-   * beside it shows.
+   * `roc`, or `iso8601`, or a calendar with months of its own, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+   * calendar Date Picker and Date Input draw.
+   *
+   * Absent is the locale's own where its months are the Gregorian months,
+   * such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+   * `persian` for `fa-IR`, so a date written here reads as the same date a
+   * Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405.
    * - `date`: The timestamp, in any format `Date` can parse.
    *
    * An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -73850,6 +74636,9 @@ export type CustomElementsSolidJs = {
    * - `date-style`/`dateStyle`: The locale's own pattern for the date: `full`, `long`, `medium`, or
    * `short`. Set, it stands in for `weekday`, `day`, `month`, `year` and `era`.
    * - `day`: How the day of the month is written, where a date is shown.
+   * - `day-period`/`dayPeriod`: Writes the part of the day in words, such as "in the morning" or "at
+   * night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+   * twelve-hour clock.
    * - `elapsed`: Shows how long ago the timestamp was, in a compact form such as "3h", in
    * place of the date.
    *
@@ -73864,6 +74653,8 @@ export type CustomElementsSolidJs = {
    * Off by default, which draws the date as one run of text, as Shoelace and
    * Web Awesome do. An `elapsed` or `relative` reading is one phrase either
    * way.
+   * - `fractional-second-digits`/`fractionalSecondDigits`: How many digits of a fraction of a second to write after `second`: 1, 2,
+   * or 3, as in 09:41:07.250.
    * - `frozen`: Draws an `elapsed` or `relative` reading once and leaves it, where it
    * would otherwise move on as it goes stale.
    *
@@ -73901,7 +74692,9 @@ export type CustomElementsSolidJs = {
    * - `time-zone`/`timeZone`: The time zone to read the timestamp in.
    *
    * Empty is the runtime's own.
-   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone, in its `long` or `short` form.
+   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+   * Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+   * `longGeneric` or `shortGeneric`, as Pacific Time or PT.
    * - `weekday`: How the weekday is written, where one is shown.
    * - `year`: How the year is written, where a date is shown.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -73932,6 +74725,7 @@ export type CustomElementsSolidJs = {
    * - `day`: The day of the month, with `fields`.
    * - `day-period`: AM or PM, or the locale's word for the part of the day, with `fields`.
    * - `era`: The era, such as AD, with `fields` and `era`.
+   * - `fractional-second`: The fraction of a second, with `fields` and `fractional-second-digits`.
    * - `hour`: The hour, with `fields`.
    * - `minute`: The minute, with `fields`.
    * - `month`: The month, with `fields`.
@@ -74905,6 +75699,7 @@ export type CustomElementsSolidJs = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `pending`: The button is pending: `pending` is set.
+   * - `pressed`: A Button Group in a selection mode has this button pressed.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-icon-button": Partial<
@@ -75807,7 +76602,8 @@ export type CustomElementsSolidJs = {
    * Each item is a `group` with the role description `slide`, named by its
    * `label` or, without one, by its place in the set, such as "2 of 5", as the
    * APG carousel pattern names a slide. The lightbox supplies both words, so they
-   * are translated on the lightbox.
+   * are translated on the lightbox. A `description`, while there is one,
+   * describes the group, so a screen reader says it with the name.
    *
    * An item that is not current is hidden and stays in the DOM, as a `TabPanel`
    * does. Crawlers can read it, it is in the server-rendered markup, and an
@@ -75892,9 +76688,10 @@ export type CustomElementsSolidJs = {
    * buttons that send `--previous`, `--next` and `--close`.
    *
    * **Set `max-zoom` to let a reader zoom into the shown item**, such as `3`.
-   * Two fingers pinch it, a double click or a double tap zooms all the way in
-   * about the point pressed and back out, and once zoomed one pointer drags it
-   * about. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.
+   * Two fingers pinch it, and so does a trackpad pinch or the wheel with Ctrl
+   * held, about the point under the pointer. A double click or a double tap
+   * zooms all the way in about the point pressed and back out, and once zoomed
+   * one pointer drags it about and the wheel moves it. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.
    * The scale and the offset are on the `viewport` part as `--lightbox-zoom`,
    * `--lightbox-pan-x` and `--lightbox-pan-y`, written only while zoomed, and a
    * swipe moves to the next item only while the item is at its own size. With
@@ -76115,6 +76912,8 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `entering`: From the moment the viewer opens until its entrance has finished.
+   * - `exiting`: From the moment the viewer closes until its exit has finished.
    * - `fullscreen`: While the viewer fills the screen.
    * - `idle`: The user has been still long enough for the controls to hide.
    * - `open`: While the viewer is open.
@@ -79764,6 +80563,7 @@ export type CustomElementsSolidJs = {
    * - `time-day`: Format Date's `day`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-day-period`: Format Date's `day-period`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-era`: Format Date's `era`, forwarded for a time drawn as fields. An elapsed time draws none.
+   * - `time-fractional-second`: Format Date's `fractional-second`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-hour`: Format Date's `hour`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-minute`: Format Date's `minute`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-month`: Format Date's `month`, forwarded for a time drawn as fields. An elapsed time draws none.
@@ -84189,6 +84989,10 @@ export type CustomElementsSolidJs = {
    * `min-steps-between-thumbs` keeps them that many steps apart, and the readout
    * joins the two as `range-text` writes them.
    *
+   * A press on a range's track takes the nearest thumb to the point pressed,
+   * and moving the pointer drags it, as React Aria's and Web Awesome's sliders
+   * do. The thumb takes focus, and `change` is sent as the press ends.
+   *
    * `origin` sets where a single thumb's fill starts: at `min`, at the middle of
    * the track, or at `max`. A balance or an offset from zero fills from the
    * middle, as Zag's slider `origin` does. The fill's ends are published as
@@ -84213,7 +85017,7 @@ export type CustomElementsSolidJs = {
    * |---|---|
    * | Right, Up | Moves the thumb up by `step`. |
    * | Left, Down | Moves the thumb down by `step`. |
-   * | Page Up, Page Down | Moves the thumb by a larger step. |
+   * | Page Up, Page Down | Moves the thumb by `page-step`, or by the platform's larger step where it is not set. |
    * | Home, End | Moves the thumb to its lowest or highest value. |
    *
    * Under `readonly` none of these move the thumb, and Tab still reaches it.
@@ -84274,6 +85078,9 @@ export type CustomElementsSolidJs = {
    * - `origin`: Where a single thumb's fill starts: `start` at `min`, `center` at the
    * middle of the track, or `end` at `max`. Absent is `start`. A range fills
    * between its thumbs and ignores it.
+   * - `page-step`/`pageStep`: How far Page Up and Page Down move a thumb, in the slider's own units, as
+   * React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+   * to the platform, which moves a tenth of the track.
    * - `range`: Adds a second thumb, so the value is a pair.
    *
    * The pair is one string, `"10,50"`, which is what `value` and
@@ -84506,6 +85313,8 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `dragging`: A thumb is being dragged, by its thumb or from a press on the track.
+   * - `focus-visible`: A thumb has focus that the keyboard brought, where the browser draws a focus ring.
    * - `invalid`: The slider has an error to show, from the browser's validation or from your `feedback`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -85692,6 +86501,10 @@ export type CustomElementsSolidJs = {
    * region. The current stage's button carries `aria-current="step"`, and only
    * the button, so the state is said once, on the control.
    *
+   * A stage's `content`, while it holds anything, is a group named by the
+   * stage's name, so a screen reader moving into it hears which stage it
+   * belongs to.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
@@ -86754,10 +87567,18 @@ export type CustomElementsSolidJs = {
    * the tab list lands on the panel's first link or control where there is one,
    * and on the panel itself where there is none.
    *
+   * **Set `lazy` for a panel that is expensive to draw.** Its content waits in a
+   * `<template>` inside it, and goes into the panel the first time the panel is
+   * shown, so it costs nothing until a reader opens that tab. Once in, it stays.
+   * The panel sends `helix-load` at the same moment, for content your code
+   * renders itself.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `lazy`: Whether the panel's content waits in a `<template>` until the panel is
+   * first shown.
    * - `selected`: Whether this panel is the visible one.
    * - `value`: Pairs the panel with the tab of the same value.
    * - `label`: The name of the panel, which is the text of the tab that opens it.
@@ -86791,11 +87612,17 @@ export type CustomElementsSolidJs = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Events
+   *
+   * Events that will be emitted by the component.
+   *
+   * - `helix-load`: Fired the first time a `lazy` panel is shown, once its template's content is in.
+   *
    * ## Slots
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The panel's content.
+   * - `(default)`: The panel's content. Under `lazy`, a `<template>` holding it.
    *
    * ## CSS Parts
    *
@@ -86807,6 +87634,7 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `loaded`: Once a `lazy` panel has been shown and its content is in.
    * - `selected`: While its tab is the one selected.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -86859,9 +87687,9 @@ export type CustomElementsSolidJs = {
    * | Enter, Space | Selects the tab with focus, or follows its link. |
    * | Tab | Leaves the list for the selected panel. |
    *
-   * Removing the selected tab selects the first enabled tab that is left, and
-   * `active` says so, with `helix-activate`. Where the removed tab had focus,
-   * focus moves to the tab now selected.
+   * Removing the selected tab selects the enabled tab beside it, the next one
+   * or else the one before, and `active` says so, with `helix-activate`. Where
+   * the removed tab had focus, focus moves to the tab now selected.
    *
    * **More tabs than fit.** With `scroll-controls`, a strip that scrolls shows a
    * button at each end it can scroll toward, as Web Awesome's tab group does,
@@ -86967,6 +87795,8 @@ export type CustomElementsSolidJs = {
    * - `(default)`: The tabs, as direct children of this element.
    * - `indicator`: A mark of your own, drawn inside the `indicator` part, where `--indicator-x`, `--indicator-y`, `--indicator-inline-size` and `--indicator-block-size` reach it.
    * - `panels`: The panels, as direct children of this element. Panels inside a wrapper are not paired with tabs, because pairing reads only the direct children.
+   * - `scroll-end-icon`: Replaces the glyph on the button that scrolls the strip toward its end.
+   * - `scroll-start-icon`: Replaces the glyph on the button that scrolls the strip toward its start.
    *
    * ## Methods
    *
@@ -86988,7 +87818,9 @@ export type CustomElementsSolidJs = {
    * - `indicator`: The marker that moves to the selected tab. It carries the selected tab's place and size as `--indicator-x`, `--indicator-y`, `--indicator-inline-size` and `--indicator-block-size`, and `data-placed` once it has been placed, for a mark you draw and animate yourself.
    * - `panels`: The panel container.
    * - `scroll-end`: The button that scrolls the strip toward its end, shown under `scroll-controls` while there is more that way.
+   * - `scroll-end-mark`: The glyph on that button, where none is slotted.
    * - `scroll-start`: The button that scrolls the strip toward its start, shown under `scroll-controls` while there is more that way.
+   * - `scroll-start-mark`: The glyph on that button, where none is slotted.
    * - `tabs`: The tab list.
    *
    * ## CSS States
@@ -87016,8 +87848,8 @@ export type CustomElementsSolidJs = {
    * can: a press on its `dismiss` mark, or Delete or Backspace while the tab
    * has focus, sends `helix-dismiss`. The tab does not remove itself, because
    * your code owns the set, so remove the tab and its panel in your handler.
-   * Focus moves to the tab beside it, and the tab set selects a tab that is
-   * left.
+   * Focus moves to the tab beside it, and where the tab was selected, the tab
+   * set selects that same tab.
    * The tab says the key through `aria-keyshortcuts`, and the mark is for the
    * pointer, hidden from screen readers.
    *
@@ -87074,6 +87906,7 @@ export type CustomElementsSolidJs = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The tab's label.
+   * - `dismiss-icon`: Replaces the glyph on the mark that closes a `dismissible` tab.
    *
    * ## Methods
    *
@@ -87098,6 +87931,7 @@ export type CustomElementsSolidJs = {
    * Custom selectors for styling elements within the component.
    *
    * - `dismiss`: The mark a pointer presses to close a `dismissible` tab.
+   * - `dismiss-mark`: The glyph on that mark, where none is slotted.
    * - `tab`: The tab itself.
    *
    * ## CSS States
@@ -87662,20 +88496,25 @@ export type CustomElementsSolidJs = {
    * `seconds`, because that is what the form
    * submits, what `min` and `max` compare against, and what sorts correctly as a
    * string. While idle, the field shows the time in the user's locale format.
-   * Once the caret is in the field, it shows the value itself, because a
-   * formatted time such as `2:30 PM` cannot be typed back and `Intl` has no
-   * parser for it.
+   * Once the caret is in the field, it shows the value itself. You can type
+   * `14:30`, or a time as you write one, such as `2:30 PM`, `2.30pm`, or
+   * `14h30`, and the field reads it as you leave it, with AM and PM in the
+   * locale's words.
    *
    * Typing sends `input` on each keystroke and `change` when you leave the
    * field. The trigger and ArrowDown open the list, and so does a press into the
-   * field; Tab into the field opens nothing. In the list, the arrow keys, typed digits and PageUp and PageDown
+   * field; Tab into the field opens nothing. The text field is a `combobox`
+   * with `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, since
+   * Down opens the list from it. In the list, the arrow keys, typed digits and PageUp and PageDown
    * move through the times, and Enter, Space or a click chooses one and closes
    * the panel. With `variant="wheels"` each wheel moves the time as you turn it,
    * the panel stays open, and Enter or Escape closes it.
    *
    * With `segmented`, the field is a row of segments in place of the text: an
    * hour, a minute, and AM or PM where the clock has them, each set with digits
-   * or the arrow keys. Alt+Down opens the list from a segment.
+   * or the arrow keys. Alt+Down opens the list from a segment. A `range` is two
+   * rows with a dash between them, the start and the end, and `multiple` keeps
+   * the text.
    *
    * Text that is not a time gives the form an empty value, as a native time
    * field does, and `value` keeps the text so it can be corrected.
@@ -87707,6 +88546,10 @@ export type CustomElementsSolidJs = {
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `disable-times`/`disableTimes`: Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
    *
    * Handed to the list, which offers them as unavailable, and checked against
@@ -87755,6 +88598,8 @@ export type CustomElementsSolidJs = {
    * never something this element would refuse to read back.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the list, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-times` bars a time.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no time, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`.
    * - `variant`: Whether the panel shows one list of times or a column for each part of the
    * time.
    *
@@ -87777,6 +88622,10 @@ export type CustomElementsSolidJs = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -87928,6 +88777,7 @@ export type CustomElementsSolidJs = {
    * - `helix-before-change`: Fired before the time changes. Cancelable: canceling it stops the change and leaves the decision to you.
    * - `helix-before-close`: Fired before the list closes. Cancelable: canceling it keeps the list open and leaves the decision to you.
    * - `helix-before-open`: Fired before the list opens. Cancelable: canceling it keeps the list closed and leaves the decision to you.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    * - `toggle`: Fired after the list opens or closes, with `newState` and `oldState`.
    *
@@ -87935,6 +88785,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the time, before the trigger, such as a clear button.
    * - `feedback`: The message that says what is wrong with the value.
    * - `hint`: Help under the field.
@@ -88008,6 +88859,7 @@ export type CustomElementsSolidJs = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a time.
    * - `control`: The text input.
    * - `feedback`: The message that says what is wrong with the value.
    * - `field`: The box that holds the text and the trigger.
@@ -88053,6 +88905,7 @@ export type CustomElementsSolidJs = {
    * - `picker-option-item-selected`: The row of a chosen time: the one time, or either end of a range.
    * - `picker-option-label`: The option's label.
    * - `picker-option-text`: The label and the caption, as one column.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of times held beyond the ones shown. A `<button>` with `expandable`, and a `<span>` without it.
    * - `segment`: One part of the time, an hour, a minute, a second or AM and PM, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -88073,6 +88926,7 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no time.
    * - `invalid`: The control has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: While the clock is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -88129,7 +88983,10 @@ export type CustomElementsSolidJs = {
    * host's `aria-label` or its `aria-labelledby`. A development build warns
    * where all four are empty. The list is described by the hint, or by the
    * message in `feedback` in its place, and carries `aria-multiselectable` with
-   * a `mode` and `aria-invalid` while `feedback` says what is wrong. The wheels
+   * a `mode`. It carries `aria-invalid` while `feedback` says what is wrong,
+   * while it holds a time outside `min` and `max` or one the picker does not
+   * offer, and, for a `required` picker with no time, once the reader has
+   * chosen one or a form has refused the picker. The wheels
    * are a `group` with that name, holding one `listbox` per wheel, named "Hour",
    * "Minute", "Second" and "AM/PM" in the page's language, and each described
    * the same way.
@@ -88487,7 +89344,7 @@ export type CustomElementsSolidJs = {
    * - `list-loading`: The text shown while the options load.
    * - `list-search`: The region that holds the filter field.
    * - `list-search-field`: The filter field.
-   * - `option`: One time in the list. It carries `data-between` inside a range.
+   * - `option`: One time in the list. It carries `data-between` inside a range, and inside the run to the time under the pointer while a range waits for its second end.
    * - `option-between`: A time inside a chosen range, excluding its ends, beside `option`.
    * - `option-description`: The caption under the time's label, when there is one.
    * - `option-item`: The row.
@@ -88501,7 +89358,8 @@ export type CustomElementsSolidJs = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `blank`: While no time is chosen.
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, or the list carries `aria-invalid`.
+   * - `range-pending`: While a `range` holds its first time and waits for the second.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-time-picker": Partial<
@@ -88737,8 +89595,9 @@ export type CustomElementsSolidJs = {
    *
    * **Each item runs its own timer.** A timer held by the region would restart
    * with each new message, and the last of three messages would stay for nine
-   * seconds. It pauses while the pointer or focus is on the message, and while
-   * the page is hidden, so a message is not spent in a background tab.
+   * seconds. It pauses while the pointer or focus is on the message or anywhere
+   * in the region's stack, and while the page is hidden, so a message is not
+   * spent in a background tab.
    *
    * **Each message is an `alertdialog` named by its words**, which is how a reader
    * who moves into the stack hears which message they are on. Give it a
@@ -88747,10 +89606,11 @@ export type CustomElementsSolidJs = {
    * says each message once as it arrives, a `danger` one assertively, so a
    * message is never a live region of its own.
    *
-   * A touch or a pen swipes a message toward the end of the line, and past
-   * halfway, or quickly, dismisses it through the same `helix-dismiss` as its
-   * control. While it moves, the distance is on the `item` part as
-   * `--toast-swipe-x`.
+   * A touch or a pen swipes a message toward the end of the line, or toward the
+   * edge the region's `swipe-direction` names, and past halfway, or quickly,
+   * dismisses it through the same `helix-dismiss` as its control. While it
+   * moves, the distance is on the `item` part as `--toast-swipe-x` or
+   * `--toast-swipe-y`.
    *
    * **Escape dismisses the message holding focus**, through the same
    * `helix-dismiss`, and focus moves to the next message.
@@ -88852,6 +89712,7 @@ export type CustomElementsSolidJs = {
    *
    * - `--toast-duration`: How long this message stays, in milliseconds, for a progress hint.
    * - `--toast-swipe-x`: How far a swipe has moved the message across, in pixels, toward the right.
+   * - `--toast-swipe-y`: How far a swipe has moved the message down, in pixels, under a `swipe-direction` of `top` or `bottom`.
    *
    * ## CSS Parts
    *
@@ -88873,7 +89734,7 @@ export type CustomElementsSolidJs = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `closed`: The message has been dismissed and is hidden, or leaving.
-   * - `paused`: The dismiss timer is paused, while a pointer or focus is on the message, or while the page is hidden.
+   * - `paused`: The dismiss timer is paused, while a pointer or focus is on the message or in the stack, or while the page is hidden.
    * - `waiting`: The region holds the message back, past its `max-visible`, until a message before it goes.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -88915,7 +89776,12 @@ export type CustomElementsSolidJs = {
    * to render them from: it appends a message of the region's own tier and
    * removes it once it has been dismissed and has finished leaving. Messages
    * you render yourself stay yours, and the region never removes them. A touch
-   * or a pen swipes a message away toward the end of the line.
+   * or a pen swipes a message away toward the end of the line, or toward the
+   * edge `swipe-direction` names.
+   *
+   * **Every message's timer waits while a pointer or focus is in the stack**, as
+   * React Aria's and Radix's regions do, so a reader moving from one message to
+   * the next does not lose the one behind them.
    *
    * **The stack is in the top layer.** The `region` part is a `popover="manual"`
    * shown while a message is showing, and shown again above a modal dialog that
@@ -88980,6 +89846,8 @@ export type CustomElementsSolidJs = {
    * consumer's server markup does not have. A sheet carries the resting
    * arrangement in its own `:host` rule and the selectors describe only the
    * departures, which is what `orientation` does.
+   * - `swipe-direction`/`swipeDirection`: The edge a touch or a pen swipes a message toward to dismiss it: `end`,
+   * the end of the line, or `start`, `top` or `bottom`. Unset is `end`.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -89087,7 +89955,7 @@ export type CustomElementsSolidJs = {
    * | Right, Down | Moves to the next item, from the last back to the first. In a single group, chooses it. |
    * | Left, Up | Moves to the item before, from the first round to the last. In a single group, chooses it. |
    * | Home, End | Moves to the first or the last item. In a single group, chooses it. |
-   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. |
+   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. With `allow-empty-selection`, takes back the chosen item. |
    *
    * Left and Right swap on a right-to-left page, and a disabled item is passed
    * over. A single group is a `radiogroup` of items with `role="radio"` and
@@ -89099,6 +89967,11 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `allow-empty-selection`/`allowEmptySelection`: Whether a press on the chosen item, or Space or Enter on it, takes it
+   * back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+   * Radix's `ToggleGroup` do in a single group. Absent, a single group always
+   * keeps its choice once it has one, as a radio group does. A multiple group
+   * releases a pressed item either way.
    * - `label-placement`/`labelPlacement`: Where the group's label sits. `start` puts it on the track's line.
    *
    * Absent is above, which is what a field looks like and what almost every
@@ -89444,13 +90317,13 @@ export type CustomElementsSolidJs = {
    *
    * Custom selectors for styling elements within the component.
    *
-   * - `item`: The radio button.
+   * - `item`: The button: a radio in a group where one is chosen, and a button with `aria-pressed` on its own or in a group where several can be.
    *
    * ## CSS States
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `pressed`: The item is pressed, in a group where several can be.
+   * - `pressed`: The item is pressed, on its own or in a group where several can be.
    * - `selected`: The item is chosen.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -89861,6 +90734,17 @@ export type CustomElementsSolidJs = {
    * least distance that brings it on screen, so the stop that points at it is
    * on screen too.
    *
+   * **A stop's `effect` runs as the tour reaches it**, before it is shown, and
+   * the stop waits for a promise it returns, with `:state(preparing)` on the
+   * tour meanwhile. A function it returns runs when the tour leaves the stop.
+   *
+   * **A press outside the current stop and its target does nothing by
+   * default**, so a reader can use the page the tour is describing. Set
+   * `outside-press="close"` to end the tour on one, through `helix-before-close`
+   * as Skip does, or `outside-press="block"` to refuse it, so the stop and its
+   * target are all a pointer can reach while the tour runs, as Zag's
+   * `preventInteraction` does.
+   *
    * **Keyboard.** Focus is on the current stop's panel, which is not in the
    * `Tab` order itself.
    *
@@ -89898,6 +90782,9 @@ export type CustomElementsSolidJs = {
    * `undefined` until somebody sets one.
    * - `label`: The tour's name, read by screen readers, such as "Getting started".
    * - `next-label`/`nextLabel`: Label for the control that goes on.
+   * - `outside-press`/`outsidePress`: What a press outside the current stop and its target does while the tour
+   * runs. Unset, nothing: the page stays usable. `close` ends the tour, as
+   * Skip does, and `block` refuses the press.
    * - `progress`: Draws each stop's place in the run in its panel, as well as saying it.
    * - `progress-label`/`progressLabel`: Each stop's place in the run, with `{index}` and `{count}` filled in and
    * written in the locale. Translate it with the rest of your text.
@@ -90001,6 +90888,7 @@ export type CustomElementsSolidJs = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `open`: While the tour is running.
+   * - `preparing`: While the tour waits for the current stop's `effect` before showing the stop.
    * - `waiting`: While the tour waits at a `wait` stop for its target to be on the page.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -90037,6 +90925,13 @@ export type CustomElementsSolidJs = {
    * get Back, Next, and Skip, already wired. Slot your own `actions` and drive
    * them with `next()`, `back()`, and `skip()` on the root.
    *
+   * **Set `effect` to prepare the page for a stop**, such as opening the menu
+   * it points into or loading what it describes. It is a function, set from
+   * script, that the tour runs as it reaches the stop. Return a promise and the
+   * stop waits for it, and the tour has `:state(preparing)` meanwhile; return a
+   * function, or resolve to one, and the tour runs it when it leaves the stop.
+   * Zag's tour step has the same `effect`.
+   *
    * **`for` is an id, as with `Tooltip`**, so you can point at a target elsewhere
    * on the page from markup. It resolves against the stop's root node, so a stop
    * inside a shadow tree points at a target in that tree.
@@ -90078,6 +90973,8 @@ export type CustomElementsSolidJs = {
    *
    * Reflected, because the styled tier places a dialog and a floating panel by
    * it, and unset at rest, so no default is written onto the host.
+   * - `effect`: Run as the tour reaches the stop, before it is shown: see the description
+   * above. A function, so it is set from script and has no attribute. (property only)
    * - `target`: The element the stop points at, or `null` when no element has the `for` id. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -90160,6 +91057,8 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `entering`: From the moment the stop is shown until its entrance has finished.
+   * - `exiting`: From the moment the stop is left until its exit has finished.
    * - `placed-bottom`: The panel sits below its target.
    * - `placed-left`: The panel sits to the left of its target.
    * - `placed-right`: The panel sits to the right of its target.
@@ -91932,6 +92831,8 @@ export type CustomCssProperties = {
   "--toast-duration"?: (string) | undefined;
   /** How far a swipe has moved the message across, in pixels, toward the right. */
   "--toast-swipe-x"?: (string) | undefined;
+  /** How far a swipe has moved the message down, in pixels, under a `swipe-direction` of `top` or `bottom`. */
+  "--toast-swipe-y"?: (string) | undefined;
   /** The lit box's height, in pixels, padding included. Written on the spotlight while it lights a target. */
   "--tour-spotlight-height"?: (string) | undefined;
   /** The lit box's width, in pixels, padding included. Written on the spotlight while it lights a target. */