@fusion.dev/helix-headless 0.169.0 → 0.171.0

package/types/jsx.d.ts

@@ -6148,6 +6148,12 @@ export type HelixHeadlessCodeBlockHelixToggleElementEvent =
   HelixHeadlessCodeBlockElementEvent<HelixToggleEvent>;
 
 export type HelixHeadlessCodeBlockProps = {
+  /** The lines to mark as inserted, as numbers and ranges counted from 1, such
+as `3-4`. Drawn as `mark-lines` is, in the added color. Not for a diff. */
+  "added-lines"?: (HelixHeadlessCodeBlock["addedLines"]) | undefined;
+  /** The lines to mark as inserted, as numbers and ranges counted from 1, such
+as `3-4`. Drawn as `mark-lines` is, in the added color. Not for a diff. */
+  addedLines?: (HelixHeadlessCodeBlock["addedLines"]) | undefined;
   /** The name of a block that scrolls, which is a tab stop while it does.
 
 Where the block has a name, the scroller says it too, such as "Code,
@@ -6306,6 +6312,12 @@ A false boolean reflects as the attribute's absence, so this costs no
 reflected property taking no default is satisfied by the default being
 `false`. */
   noCopy?: (HelixHeadlessCodeBlock["noCopy"]) | undefined;
+  /** The lines to mark as deleted, as numbers and ranges counted from 1. Drawn
+as `mark-lines` is, in the removed color. Not for a diff. */
+  "removed-lines"?: (HelixHeadlessCodeBlock["removedLines"]) | undefined;
+  /** The lines to mark as deleted, as numbers and ranges counted from 1. Drawn
+as `mark-lines` is, in the removed color. Not for a diff. */
+  removedLines?: (HelixHeadlessCodeBlock["removedLines"]) | undefined;
   /** The words of a button that shows a folded run of unchanged lines, in a
 diff with `context-lines`. `{count}` is how many. */
   "show-unchanged-label"?: (HelixHeadlessCodeBlock["showUnchangedLabel"]) | undefined;
@@ -6378,6 +6390,12 @@ read, nor for a diff. */
 };
 
 export type HelixHeadlessCodeBlockSolidJsProps = {
+  /** The lines to mark as inserted, as numbers and ranges counted from 1, such
+as `3-4`. Drawn as `mark-lines` is, in the added color. Not for a diff. */
+  "attr:added-lines"?: (HelixHeadlessCodeBlock["addedLines"]) | undefined;
+  /** The lines to mark as inserted, as numbers and ranges counted from 1, such
+as `3-4`. Drawn as `mark-lines` is, in the added color. Not for a diff. */
+  "prop:addedLines"?: (HelixHeadlessCodeBlock["addedLines"]) | undefined;
   /** The name of a block that scrolls, which is a tab stop while it does.
 
 Where the block has a name, the scroller says it too, such as "Code,
@@ -6536,6 +6554,12 @@ A false boolean reflects as the attribute's absence, so this costs no
 reflected property taking no default is satisfied by the default being
 `false`. */
   "prop:noCopy"?: (HelixHeadlessCodeBlock["noCopy"]) | undefined;
+  /** The lines to mark as deleted, as numbers and ranges counted from 1. Drawn
+as `mark-lines` is, in the removed color. Not for a diff. */
+  "attr:removed-lines"?: (HelixHeadlessCodeBlock["removedLines"]) | undefined;
+  /** The lines to mark as deleted, as numbers and ranges counted from 1. Drawn
+as `mark-lines` is, in the removed color. Not for a diff. */
+  "prop:removedLines"?: (HelixHeadlessCodeBlock["removedLines"]) | undefined;
   /** The words of a button that shows a folded run of unchanged lines, in a
 diff with `context-lines`. `{count}` is how many. */
   "attr:show-unchanged-label"?: (HelixHeadlessCodeBlock["showUnchangedLabel"]) | undefined;
@@ -7404,10 +7428,11 @@ would give one control two of each. What is left is the validity call and
 the anchor the browser points its bubble at.
 
 **Text that is not a color is bad input**, so a form does not submit
-`#00` from a half-typed value. The picker draws no message of its own, so
-reporting it as each keystroke arrives shows nothing until the form asks;
-Color Input shows its own message against the field the reader typed
-into. */
+`#00` from a half-typed value. The picker marks it, and says
+`badInputMessage` under itself, once the reader leaves the value field or
+presses Enter, and a missing color once the reader has committed one or a
+form has refused the picker. Color Input shows its own message against the
+field the reader typed into. */
   required?: (HelixHeadlessColorPicker["required"]) | undefined;
   /** What the square's horizontal ramp is called. */
   "saturation-label"?: (HelixHeadlessColorPicker["saturationLabel"]) | undefined;
@@ -7784,10 +7809,11 @@ would give one control two of each. What is left is the validity call and
 the anchor the browser points its bubble at.
 
 **Text that is not a color is bad input**, so a form does not submit
-`#00` from a half-typed value. The picker draws no message of its own, so
-reporting it as each keystroke arrives shows nothing until the form asks;
-Color Input shows its own message against the field the reader typed
-into. */
+`#00` from a half-typed value. The picker marks it, and says
+`badInputMessage` under itself, once the reader leaves the value field or
+presses Enter, and a missing color once the reader has committed one or a
+form has refused the picker. Color Input shows its own message against the
+field the reader typed into. */
   "prop:required"?: (HelixHeadlessColorPicker["required"]) | undefined;
   /** What the square's horizontal ramp is called. */
   "attr:saturation-label"?: (HelixHeadlessColorPicker["saturationLabel"]) | undefined;
@@ -8063,12 +8089,13 @@ language. */
   locale?: (HelixHeadlessCombobox["locale"]) | undefined;
   /** Whether more than one option can be chosen.
 
-The list already does the work: `value` comes apart on commas, a press
-toggles rather than replaces, and the arrows move without choosing. What
-this adds is the tags, and keeping the panel open between picks.
+The list already does the work: `value` is the chosen values joined with
+commas, a press toggles rather than replaces, and the arrows move without
+choosing. What this adds is the tags, and keeping the panel open between
+picks.
 
-A comma is therefore not available inside an option's value, which is the
-listbox's contract and not this element's to change.
+An option's value may hold a comma, and it is read as one value, as
+`Select` and `Listbox` read it. So may an answer the reader created.
 
 **The list is told, and the field is not.** `aria-multiselectable` belongs
 to `listbox`, `grid`, `tree` and `tablist`, and `combobox` dropped it in
@@ -8428,12 +8455,13 @@ language. */
   "prop:locale"?: (HelixHeadlessCombobox["locale"]) | undefined;
   /** Whether more than one option can be chosen.
 
-The list already does the work: `value` comes apart on commas, a press
-toggles rather than replaces, and the arrows move without choosing. What
-this adds is the tags, and keeping the panel open between picks.
+The list already does the work: `value` is the chosen values joined with
+commas, a press toggles rather than replaces, and the arrows move without
+choosing. What this adds is the tags, and keeping the panel open between
+picks.
 
-A comma is therefore not available inside an option's value, which is the
-listbox's contract and not this element's to change.
+An option's value may hold a comma, and it is read as one value, as
+`Select` and `Listbox` read it. So may an answer the reader created.
 
 **The list is told, and the field is not.** `aria-multiselectable` belongs
 to `listbox`, `grid`, `tree` and `tablist`, and `combobox` dropped it in
@@ -8718,6 +8746,18 @@ so a palette filtered on a server sends one `helix-filter` for a word.
 so a palette filtered on a server sends one `helix-filter` for a word.
 `0` filters on every keystroke. See Listbox's `filter-delay`. */
   filterDelay?: (HelixHeadlessCommand["filterDelay"]) | undefined;
+  /** Where Home and End go from the filter field.
+
+Absent, they move the caret, as APG's combobox has them. `list` moves the
+highlight to the first or the last command, as React Aria's Autocomplete
+does, and Shift with either still selects the text. */
+  "home-end"?: (HelixHeadlessCommand["homeEnd"]) | undefined;
+  /** Where Home and End go from the filter field.
+
+Absent, they move the caret, as APG's combobox has them. `list` moves the
+highlight to the first or the last command, as React Aria's Autocomplete
+does, and Shift with either still selects the text. */
+  homeEnd?: (HelixHeadlessCommand["homeEnd"]) | undefined;
   /** The key that opens the palette, written as `mod+k`, `shift+p`, or `k`,
 in Kbd's chord spelling: `mod` is Command or Control, `ctrl`, `cmd`,
 `alt` and `shift` the keys they name.
@@ -8735,6 +8775,10 @@ and `open`, `toggle` and the dialog's parts do nothing. */
   inline?: (HelixHeadlessCommand["inline"]) | undefined;
   /** Accessible name for the overlay, which has no visible heading. */
   label?: (HelixHeadlessCommand["label"]) | undefined;
+  /** How the commands are laid out, as Listbox's `layout`: `grid` draws them in
+rows and columns, for a palette of icons or emoji, and the arrow keys
+follow the rows and the columns. Absent is one command under another. */
+  layout?: (HelixHeadlessCommand["layout"]) | undefined;
   /** What the list says when its commands could not be loaded, such as after a
 request to a server fails. Empty, null or no attribute is no error, so
 removing the attribute clears it. Passed to the list, which shows it
@@ -8854,6 +8898,18 @@ so a palette filtered on a server sends one `helix-filter` for a word.
 so a palette filtered on a server sends one `helix-filter` for a word.
 `0` filters on every keystroke. See Listbox's `filter-delay`. */
   "prop:filterDelay"?: (HelixHeadlessCommand["filterDelay"]) | undefined;
+  /** Where Home and End go from the filter field.
+
+Absent, they move the caret, as APG's combobox has them. `list` moves the
+highlight to the first or the last command, as React Aria's Autocomplete
+does, and Shift with either still selects the text. */
+  "attr:home-end"?: (HelixHeadlessCommand["homeEnd"]) | undefined;
+  /** Where Home and End go from the filter field.
+
+Absent, they move the caret, as APG's combobox has them. `list` moves the
+highlight to the first or the last command, as React Aria's Autocomplete
+does, and Shift with either still selects the text. */
+  "prop:homeEnd"?: (HelixHeadlessCommand["homeEnd"]) | undefined;
   /** The key that opens the palette, written as `mod+k`, `shift+p`, or `k`,
 in Kbd's chord spelling: `mod` is Command or Control, `ctrl`, `cmd`,
 `alt` and `shift` the keys they name.
@@ -8871,6 +8927,10 @@ and `open`, `toggle` and the dialog's parts do nothing. */
   "prop:inline"?: (HelixHeadlessCommand["inline"]) | undefined;
   /** Accessible name for the overlay, which has no visible heading. */
   "prop:label"?: (HelixHeadlessCommand["label"]) | undefined;
+  /** How the commands are laid out, as Listbox's `layout`: `grid` draws them in
+rows and columns, for a palette of icons or emoji, and the arrow keys
+follow the rows and the columns. Absent is one command under another. */
+  "prop:layout"?: (HelixHeadlessCommand["layout"]) | undefined;
   /** What the list says when its commands could not be loaded, such as after a
 request to a server fails. Empty, null or no attribute is no error, so
 removing the attribute clears it. Passed to the list, which shows it
@@ -13542,6 +13602,13 @@ makes an unusual filter look unusual. */
   operatorLabel?: (HelixHeadlessFilterChip["operatorLabel"]) | undefined;
   /** Whether the element shows a control that dismisses it. */
   dismissible?: (HelixHeadlessFilterChip["dismissible"]) | undefined;
+  /** Whether the remove button is a tab stop of its own.
+
+`FilterInput` writes `false` on the chips in its `tags` slot: the field's
+text is its one tab stop, and the arrow keys move from the text to the
+chips, as in a `multiple` Combobox. No attribute: it is coordination
+between elements, as `Tag.dismissTabStop` is. */
+  dismissTabStop?: (HelixHeadlessFilterChip["dismissTabStop"]) | undefined;
 
   /** Fired when the user asks to remove the filter. Cancelable: call `preventDefault()` to keep the chip. */
   "onhelix-dismiss"?: ((
@@ -13612,6 +13679,13 @@ makes an unusual filter look unusual. */
   "prop:operatorLabel"?: (HelixHeadlessFilterChip["operatorLabel"]) | undefined;
   /** Whether the element shows a control that dismisses it. */
   "prop:dismissible"?: (HelixHeadlessFilterChip["dismissible"]) | undefined;
+  /** Whether the remove button is a tab stop of its own.
+
+`FilterInput` writes `false` on the chips in its `tags` slot: the field's
+text is its one tab stop, and the arrow keys move from the text to the
+chips, as in a `multiple` Combobox. No attribute: it is coordination
+between elements, as `Tag.dismissTabStop` is. */
+  "prop:dismissTabStop"?: (HelixHeadlessFilterChip["dismissTabStop"]) | undefined;
   /** Fired when the user asks to remove the filter. Cancelable: call `preventDefault()` to keep the chip. */
   "on:helix-dismiss"?: ((
     e: HelixHeadlessFilterChipHelixDismissElementEvent,
@@ -13822,6 +13896,18 @@ export type HelixHeadlessFilterInputToggleElementEvent =
   HelixHeadlessFilterInputElementEvent<ToggleEvent>;
 
 export type HelixHeadlessFilterInputProps = {
+  /** Whether the field keeps a `FilterChip` for each filter in its `tags` slot,
+from the `helix-facet` events it hears.
+
+Off, you build the chips, which is what you do when your own model holds
+the filters. On, a filter typed, picked, or changed adds or updates the
+chip for its field, one with no values takes it away (unless its
+comparison takes none, such as "is empty"), and removing the chip clears
+the filter. A `helix-facet` you cancel changes no chip.
+
+The chips are elements the field adds to its own children, so leave this
+off where a framework renders those children and would remove them. */
+  chips?: (HelixHeadlessFilterInput["chips"]) | undefined;
   /** Shows a button that empties the field.
 
 The text only. The tokens are the consumer's markup and this element is not
@@ -13843,6 +13929,29 @@ what you slot and you narrow it. */
 being typed, as React Aria's Autocomplete filters. Off, the panel shows
 what you slot and you narrow it. */
   filterSuggestions?: (HelixHeadlessFilterInput["filterSuggestions"]) | undefined;
+  /** Whether the suggestions are still loading, such as while a request for the
+values of a typed key is out.
+
+The panel opens on `loading-text`, or the `loading` slot, while the field
+has focus, and a screen reader hears it. Slot the options and clear this
+when they arrive. */
+  loading?: (HelixHeadlessFilterInput["loading"]) | undefined;
+  /** Text the panel shows while the suggestions load. */
+  "loading-text"?: (HelixHeadlessFilterInput["loadingText"]) | undefined;
+  /** Text the panel shows while the suggestions load. */
+  loadingText?: (HelixHeadlessFilterInput["loadingText"]) | undefined;
+  /** Text the panel shows when `filter-suggestions` hides every suggestion, such
+as "No matching filters".
+
+Empty, or no `no-results` slot, and the panel closes instead, as it does
+when it has nothing to offer. */
+  "no-results-text"?: (HelixHeadlessFilterInput["noResultsText"]) | undefined;
+  /** Text the panel shows when `filter-suggestions` hides every suggestion, such
+as "No matching filters".
+
+Empty, or no `no-results` slot, and the panel closes instead, as it does
+when it has nothing to offer. */
+  noResultsText?: (HelixHeadlessFilterInput["noResultsText"]) | undefined;
   /** The text shown while the field is empty.
 
 Not a label: it goes when typing starts. */
@@ -14037,6 +14146,18 @@ Here rather than on each control. */
 };
 
 export type HelixHeadlessFilterInputSolidJsProps = {
+  /** Whether the field keeps a `FilterChip` for each filter in its `tags` slot,
+from the `helix-facet` events it hears.
+
+Off, you build the chips, which is what you do when your own model holds
+the filters. On, a filter typed, picked, or changed adds or updates the
+chip for its field, one with no values takes it away (unless its
+comparison takes none, such as "is empty"), and removing the chip clears
+the filter. A `helix-facet` you cancel changes no chip.
+
+The chips are elements the field adds to its own children, so leave this
+off where a framework renders those children and would remove them. */
+  "prop:chips"?: (HelixHeadlessFilterInput["chips"]) | undefined;
   /** Shows a button that empties the field.
 
 The text only. The tokens are the consumer's markup and this element is not
@@ -14058,6 +14179,29 @@ what you slot and you narrow it. */
 being typed, as React Aria's Autocomplete filters. Off, the panel shows
 what you slot and you narrow it. */
   "prop:filterSuggestions"?: (HelixHeadlessFilterInput["filterSuggestions"]) | undefined;
+  /** Whether the suggestions are still loading, such as while a request for the
+values of a typed key is out.
+
+The panel opens on `loading-text`, or the `loading` slot, while the field
+has focus, and a screen reader hears it. Slot the options and clear this
+when they arrive. */
+  "prop:loading"?: (HelixHeadlessFilterInput["loading"]) | undefined;
+  /** Text the panel shows while the suggestions load. */
+  "attr:loading-text"?: (HelixHeadlessFilterInput["loadingText"]) | undefined;
+  /** Text the panel shows while the suggestions load. */
+  "prop:loadingText"?: (HelixHeadlessFilterInput["loadingText"]) | undefined;
+  /** Text the panel shows when `filter-suggestions` hides every suggestion, such
+as "No matching filters".
+
+Empty, or no `no-results` slot, and the panel closes instead, as it does
+when it has nothing to offer. */
+  "attr:no-results-text"?: (HelixHeadlessFilterInput["noResultsText"]) | undefined;
+  /** Text the panel shows when `filter-suggestions` hides every suggestion, such
+as "No matching filters".
+
+Empty, or no `no-results` slot, and the panel closes instead, as it does
+when it has nothing to offer. */
+  "prop:noResultsText"?: (HelixHeadlessFilterInput["noResultsText"]) | undefined;
   /** The text shown while the field is empty.
 
 Not a label: it goes when typing starts. */
@@ -22150,9 +22294,13 @@ speaks it: `feedback` replaces the message under the field and does not
 reach the bubble. Unset is the sentence registered for the page's
 language, then the English. */
   badInputMessage?: (HelixHeadlessNumberInput["badInputMessage"]) | undefined;
-  /** The name of the step down button, read by screen readers. */
+  /** The name of the step down button, read by screen readers. The field's
+label follows it, so a reader hears "Decrease Quantity", as React Aria
+names its steppers. */
   "decrement-label"?: (HelixHeadlessNumberInput["decrementLabel"]) | undefined;
-  /** The name of the step down button, read by screen readers. */
+  /** The name of the step down button, read by screen readers. The field's
+label follows it, so a reader hears "Decrease Quantity", as React Aria
+names its steppers. */
   decrementLabel?: (HelixHeadlessNumberInput["decrementLabel"]) | undefined;
   /** `Intl.NumberFormat` options the number is shown with while the field is
 not being edited: a currency, a percent, a unit, or a number of decimals.
@@ -22170,9 +22318,13 @@ Written as JSON in the attribute.
 <helix-number-input format-options='{"style":"currency","currency":"EUR"}'></helix-number-input>
 ``` */
   formatOptions?: (HelixHeadlessNumberInput["formatOptions"]) | undefined;
-  /** The name of the step up button, read by screen readers. */
+  /** The name of the step up button, read by screen readers. The field's
+label follows it, so a reader hears "Increase Quantity", as React Aria
+names its steppers. */
   "increment-label"?: (HelixHeadlessNumberInput["incrementLabel"]) | undefined;
-  /** The name of the step up button, read by screen readers. */
+  /** The name of the step up button, read by screen readers. The field's
+label follows it, so a reader hears "Increase Quantity", as React Aria
+names its steppers. */
   incrementLabel?: (HelixHeadlessNumberInput["incrementLabel"]) | undefined;
   /** How many steps `PageUp` and `PageDown` move.
 
@@ -22429,9 +22581,13 @@ speaks it: `feedback` replaces the message under the field and does not
 reach the bubble. Unset is the sentence registered for the page's
 language, then the English. */
   "prop:badInputMessage"?: (HelixHeadlessNumberInput["badInputMessage"]) | undefined;
-  /** The name of the step down button, read by screen readers. */
+  /** The name of the step down button, read by screen readers. The field's
+label follows it, so a reader hears "Decrease Quantity", as React Aria
+names its steppers. */
   "attr:decrement-label"?: (HelixHeadlessNumberInput["decrementLabel"]) | undefined;
-  /** The name of the step down button, read by screen readers. */
+  /** The name of the step down button, read by screen readers. The field's
+label follows it, so a reader hears "Decrease Quantity", as React Aria
+names its steppers. */
   "prop:decrementLabel"?: (HelixHeadlessNumberInput["decrementLabel"]) | undefined;
   /** `Intl.NumberFormat` options the number is shown with while the field is
 not being edited: a currency, a percent, a unit, or a number of decimals.
@@ -22449,9 +22605,13 @@ Written as JSON in the attribute.
 <helix-number-input format-options='{"style":"currency","currency":"EUR"}'></helix-number-input>
 ``` */
   "prop:formatOptions"?: (HelixHeadlessNumberInput["formatOptions"]) | undefined;
-  /** The name of the step up button, read by screen readers. */
+  /** The name of the step up button, read by screen readers. The field's
+label follows it, so a reader hears "Increase Quantity", as React Aria
+names its steppers. */
   "attr:increment-label"?: (HelixHeadlessNumberInput["incrementLabel"]) | undefined;
-  /** The name of the step up button, read by screen readers. */
+  /** The name of the step up button, read by screen readers. The field's
+label follows it, so a reader hears "Increase Quantity", as React Aria
+names its steppers. */
   "prop:incrementLabel"?: (HelixHeadlessNumberInput["incrementLabel"]) | undefined;
   /** How many steps `PageUp` and `PageDown` move.
 
@@ -28426,7 +28586,8 @@ export type HelixHeadlessStepsHelixSelectElementEvent =
 
 export type HelixHeadlessStepsProps = {
   /** Whether the arrow keys move focus between the stages' names, along the
-way the steps run. Off by default, so the arrows keep scrolling the page. */
+way the steps run, and the names are one tab stop. Off by default, so the
+arrows keep scrolling the page. */
   arrows?: (HelixHeadlessSteps["arrows"]) | undefined;
   /** What marks a stage `complete`.
 
@@ -28510,7 +28671,8 @@ there. Not asked of an `optional` stage, nor for a move back. */
 
 export type HelixHeadlessStepsSolidJsProps = {
   /** Whether the arrow keys move focus between the stages' names, along the
-way the steps run. Off by default, so the arrows keep scrolling the page. */
+way the steps run, and the names are one tab stop. Off by default, so the
+arrows keep scrolling the page. */
   "prop:arrows"?: (HelixHeadlessSteps["arrows"]) | undefined;
   /** What marks a stage `complete`.
 
@@ -28633,7 +28795,9 @@ with the page. */
   /** Whether a reader may pass the stage without finishing it, in a sequence
 with `linear`. Ark UI's skippable step. */
   optional?: (HelixHeadlessStep["optional"]) | undefined;
-  /** The value the step sends in `helix-select`. */
+  /** The value the step sends in `helix-select`, and what names the step in its
+sequence's `active`. Without one, the sequence names the step by its place,
+counted from 1. */
   value?: (HelixHeadlessStep["value"]) | undefined;
 
   /** Fired when the step is pressed. Cancelable: cancel it to keep the current step. */
@@ -28666,7 +28830,9 @@ with the page. */
   /** Whether a reader may pass the stage without finishing it, in a sequence
 with `linear`. Ark UI's skippable step. */
   "prop:optional"?: (HelixHeadlessStep["optional"]) | undefined;
-  /** The value the step sends in `helix-select`. */
+  /** The value the step sends in `helix-select`, and what names the step in its
+sequence's `active`. Without one, the sequence names the step by its place,
+counted from 1. */
   "prop:value"?: (HelixHeadlessStep["value"]) | undefined;
   /** Fired when the step is pressed. Cancelable: cancel it to keep the current step. */
   "on:helix-select"?: ((e: HelixHeadlessStepHelixSelectElementEvent) => void) | undefined;
@@ -40168,7 +40334,8 @@ export type CustomElements = {
    * field taking more. A draft that fails them does not send, and the composer
    * takes `:state(invalid)` and `aria-invalid` once the reader has tried to send
    * it, the form was submitted, or the reader edited the field and left it.
-   * Tabbing past an empty composer marks nothing.
+   * Sending an empty required composer counts as trying. Tabbing past an empty
+   * composer marks nothing.
    *
    * **`typing` says whether the user is writing**, and `helix-typing` is sent
    * each time it changes: when they start, and when they send or stop for
@@ -40477,8 +40644,10 @@ export type CustomElements = {
    * there when the transcript opened. A turn is said with its author first, such
    * as "Ada: It ships today" (`arrival-label`), where its author can be named.
    *
-   * Pass the turns as children or as `turns` data. Do not use both. Children
-   * render from the server and suit most conversations. `turns` draws a long
+   * Pass the turns as children or as `turns` data. Do not use both: a chat given
+   * both draws every turn from `turns` and then the children, and says so once
+   * in the console. Children render from the server and suit most
+   * conversations. `turns` draws a long
    * transcript one window at a time, so the log needs a block size of its own.
    *
    * **A conversation is built from three elements.** The chat holds the
@@ -40494,7 +40663,10 @@ export type CustomElements = {
    * it takes them away. Anything slotted into `status` is drawn first.
    *
    * **Keyboard.** The transcript moves between turns the way a feed does. Each
-   * turn says its place, such as "3 of 40", windowed or not.
+   * turn says its place, such as "3 of 40", windowed or not. The transcript is
+   * a tab stop while it holds a turn, and the turn a reader moved to is one
+   * too. Moving to an older turn unpins a transcript that scrolls and scrolls
+   * the turn into view, and moving to the newest pins it again.
    *
    * | Key | What it does |
    * |---|---|
@@ -40705,6 +40877,10 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `empty`: The conversation has no turns.
+   * - `loading`: Older turns are loading: `history` is `loading`.
+   * - `pinned`: The transcript follows its newest turn.
+   * - `typing`: `typing` names someone on the other side.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-chat": Partial<
@@ -41209,7 +41385,11 @@ export type CustomElements = {
    * from the accessibility tree and left out of a copy. Set `mark-lines` to
    * mark lines a reader should look at, such as `2, 4-6`: the block draws a
    * band behind each run, placed where the lines are laid out, so it follows a
-   * highlighter's markup and lines that wrap. Set `wrap` to wrap long lines
+   * highlighter's markup and lines that wrap. `added-lines` and
+   * `removed-lines` mark lines the same way as inserted and deleted, as
+   * Expressive Code's `ins` and `del` do, in code that is not a diff. The bands
+   * are drawn and hidden from screen readers, so say in the text around the
+   * block what a marked line means. Set `wrap` to wrap long lines
    * rather than scroll them; a gutter then numbers each line where it starts.
    * Set `wrappable` for a button in the header that turns `wrap` on and off,
    * pressed while the lines wrap.
@@ -41278,6 +41458,8 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `added-lines`/`addedLines`: The lines to mark as inserted, as numbers and ranges counted from 1, such
+   * as `3-4`. Drawn as `mark-lines` is, in the added color. Not for a diff.
    * - `code-label`/`codeLabel`: The name of a block that scrolls, which is a tab stop while it does.
    *
    * Where the block has a name, the scroller says it too, such as "Code,
@@ -41354,6 +41536,8 @@ export type CustomElements = {
    * `no-copy=""` on hosts that never asked for one, and the rule about a
    * reflected property taking no default is satisfied by the default being
    * `false`.
+   * - `removed-lines`/`removedLines`: The lines to mark as deleted, as numbers and ranges counted from 1. Drawn
+   * as `mark-lines` is, in the removed color. Not for a diff.
    * - `show-unchanged-label`/`showUnchangedLabel`: The words of a button that shows a folded run of unchanged lines, in a
    * diff with `context-lines`. `{count}` is how many.
    * - `variant`: How a diff's two versions are arranged. It has no effect without `diff`.
@@ -41433,6 +41617,8 @@ export type CustomElements = {
    * - `actions`: Controls for the block, in the header before the copy button.
    * - `copied-icon`: The copy button's icon after a copy. Defaults to a check mark.
    * - `copy-icon`: The copy button's icon before a copy. Defaults to a clipboard.
+   * - `expand-icon`: An icon on the button that shows every line of a capped block, before its words.
+   * - `label`: The block's name in the header, such as a file icon beside the file name. Replaces `label` and `language` there, and draws the header.
    *
    * ## CSS Custom Properties
    *
@@ -41480,7 +41666,9 @@ export type CustomElements = {
    * - `header`: The bar that holds the name and the copy button, shown when there is a name.
    * - `hunk`: In a diff, a `@@` line saying where the lines under it are.
    * - `label`: The block's name: its `label`, or its `language` where it has no label.
-   * - `mark`: The band behind a run of lines `mark-lines` names. The block writes where the run is laid out into `--code-block-mark-start`, `--code-block-mark-size`, and `--code-block-mark-inline-size` on it. Hidden from the accessibility tree.
+   * - `mark`: The band behind a run of lines `mark-lines`, `added-lines` or `removed-lines` names. The block writes where the run is laid out into `--code-block-mark-start`, `--code-block-mark-size`, and `--code-block-mark-inline-size` on it. Hidden from the accessibility tree.
+   * - `mark-added`: The band behind a run of lines `added-lines` names. Applied with `mark`.
+   * - `mark-removed`: The band behind a run of lines `removed-lines` names. Applied with `mark`.
    * - `marker`: In a diff, the `+`, `-`, or space that starts a line.
    * - `new`: In a split diff, the new version's `<pre>`.
    * - `number`: In a diff, a line number. In a `wrap` block with `line-numbers`, one line's number in the gutter, which the block makes as tall as the line it numbers through `--code-block-line-size`.
@@ -42087,10 +42275,11 @@ export type CustomElements = {
    * the anchor the browser points its bubble at.
    *
    * **Text that is not a color is bad input**, so a form does not submit
-   * `#00` from a half-typed value. The picker draws no message of its own, so
-   * reporting it as each keystroke arrives shows nothing until the form asks;
-   * Color Input shows its own message against the field the reader typed
-   * into.
+   * `#00` from a half-typed value. The picker marks it, and says
+   * `badInputMessage` under itself, once the reader leaves the value field or
+   * presses Enter, and a missing color once the reader has committed one or a
+   * form has refused the picker. Color Input shows its own message against the
+   * field the reader typed into.
    * - `saturation-label`/`saturationLabel`: What the square's horizontal ramp is called.
    * - `square-text`/`squareText`: What a screen reader hears for the square's place, the color's two
    * numbers and its name, on whichever of its two inputs it is on.
@@ -42209,14 +42398,10 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: A reset ends any typing and takes back text that was not a color, so the
+   * field shows the color the reset put back.
    * - `requestValue(next: string) => boolean`: Blocks every change while `readOnly` is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the square.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
@@ -42297,7 +42482,7 @@ export type CustomElements = {
    * - `eyedropper-live`: The live region of the button inside `eyedropper`, which says its pending label.
    * - `eyedropper-spinner`: The ring the eyedropper button turns while it is pending.
    * - `eyedropper-text`: The words on the button inside `eyedropper`, trimmed to their capitals and baseline.
-   * - `feedback`: The message under the picker, while `feedback` is set.
+   * - `feedback`: The message under the picker: `feedback`, or what is wrong with the answer once the picker is marked invalid.
    * - `field`: One channel's number field with its label, in `channel-fields`.
    * - `field-input`: The number input in a channel's field.
    * - `field-label`: The name above a channel's number input.
@@ -42455,12 +42640,13 @@ export type CustomElements = {
    * language.
    * - `multiple`: Whether more than one option can be chosen.
    *
-   * The list already does the work: `value` comes apart on commas, a press
-   * toggles rather than replaces, and the arrows move without choosing. What
-   * this adds is the tags, and keeping the panel open between picks.
+   * The list already does the work: `value` is the chosen values joined with
+   * commas, a press toggles rather than replaces, and the arrows move without
+   * choosing. What this adds is the tags, and keeping the panel open between
+   * picks.
    *
-   * A comma is therefore not available inside an option's value, which is the
-   * listbox's contract and not this element's to change.
+   * An option's value may hold a comma, and it is read as one value, as
+   * `Select` and `Listbox` read it. So may an answer the reader created.
    *
    * **The list is told, and the field is not.** `aria-multiselectable` belongs
    * to `listbox`, `grid`, `tree` and `tablist`, and `combobox` dropped it in
@@ -42801,7 +42987,8 @@ export type CustomElements = {
    * | `hotkey`, Command or Control with K by default | Opens the palette from anywhere on the page, or closes it. With `inline`, puts focus in its filter field. |
    * | Down, Up | Moves the highlight to the next or the previous command, round from the last to the first. |
    * | Page Down, Page Up | Moves the highlight by as many commands as the list shows at once. |
-   * | Home, End, Left, Right | Move the caret in the filter field. |
+   * | Home, End | Move the caret in the filter field. With `home-end="list"`, move the highlight to the first or the last command. |
+   * | Left, Right | Move the caret in the filter field. |
    * | Enter | Runs the highlighted command, or follows it where it is a link, and closes the palette. On a command with `opens`, shows its page. |
    * | Command or Control with Enter | Takes the highlighted command's `alternate` destination, where it has one. |
    * | Backspace | In an empty filter on a page, goes back to the page before. |
@@ -42823,6 +43010,11 @@ export type CustomElements = {
    * - `filter-delay`/`filterDelay`: How long typing rests before the commands are filtered, in milliseconds,
    * so a palette filtered on a server sends one `helix-filter` for a word.
    * `0` filters on every keystroke. See Listbox's `filter-delay`.
+   * - `home-end`/`homeEnd`: Where Home and End go from the filter field.
+   *
+   * Absent, they move the caret, as APG's combobox has them. `list` moves the
+   * highlight to the first or the last command, as React Aria's Autocomplete
+   * does, and Shift with either still selects the text.
    * - `hotkey`: The key that opens the palette, written as `mod+k`, `shift+p`, or `k`,
    * in Kbd's chord spelling: `mod` is Command or Control, `ctrl`, `cmd`,
    * `alt` and `shift` the keys they name.
@@ -42837,6 +43029,9 @@ export type CustomElements = {
    * Choosing a command says `helix-select` and leaves the list where it is,
    * and `open`, `toggle` and the dialog's parts do nothing.
    * - `label`: Accessible name for the overlay, which has no visible heading.
+   * - `layout`: How the commands are laid out, as Listbox's `layout`: `grid` draws them in
+   * rows and columns, for a palette of icons or emoji, and the arrow keys
+   * follow the rows and the columns. Absent is one command under another.
    * - `load-error`/`loadError`: What the list says when its commands could not be loaded, such as after a
    * request to a server fails. Empty, null or no attribute is no error, so
    * removing the attribute clears it. Passed to the list, which shows it
@@ -43245,10 +43440,15 @@ export type CustomElements = {
    *
    * Sort and filter apply to the whole set, including the rows on other pages.
    *
-   * **The cell values do not server-render.** The headings and the row elements
-   * do. Reading a cell needs the columns, and Lit SSR does not pass the column
-   * children to this element, so a crawler sees an empty table of the right
-   * shape. Use `Table` when the served HTML has to carry the values.
+   * **Write the first page as rows, so the served HTML carries the values.** The
+   * table reads each cell from its column, and a server does not pass the column
+   * children to this element, so on its own it serves the headings and no values.
+   * Write the first page under the columns as `TableRow` and `TableCell`
+   * elements, in the table's sort and page size and formatted as its columns draw
+   * them. The table shows your rows until `rows` holds a row, then draws its own
+   * in their place and leaves yours in the page, unshown. A development build
+   * warns when the two differ. In React, map the first page of the same array in
+   * the same server component.
    *
    * `selectable` adds a column of checkboxes, keyed on `row-key`:
    *
@@ -43598,7 +43798,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The columns, as `TableColumn` elements.
+   * - `(default)`: The columns, as `TableColumn` elements, and the first page served as `TableRow` elements, which show until `rows` holds a row.
    * - `empty`: Content shown when there are no rows to show and none are loading, such as a picture and a link. Falls back to `empty-text`, which the live region still says.
    * - `error`: Content shown while `error-text` is set, such as a button that tries again. Falls back to `error-text`, which the live region still says.
    * - `footer`: Content below the grid. It replaces the built-in pagination.
@@ -46321,9 +46521,10 @@ export type CustomElements = {
    * press. `requestChange` documents the pattern.
    *
    * **Keyboard.** The remove button is a tab stop of its own, and Enter or Space
-   * on it asks to remove the filter. In a `FilterInput`, Backspace in the empty
-   * field asks to remove the last chip, the arrow keys move between the field
-   * and the chips, and Delete or Backspace on a chip asks to remove it.
+   * on it asks to remove the filter. In a `FilterInput`, the field's text is the
+   * one tab stop: Backspace in the empty field asks to remove the last chip, the
+   * arrow keys move between the field and the chips, and Delete or Backspace on
+   * a chip asks to remove it.
    *
    * The remove button is named `dismiss-label` followed by the chip's words,
    * such as "Remove filter Status is not open", so a row of chips says which
@@ -46379,6 +46580,12 @@ export type CustomElements = {
    * reads. The moment somebody picks a different comparison it appears, which
    * makes an unusual filter look unusual.
    * - `dismissible`: Whether the element shows a control that dismisses it.
+   * - `dismissTabStop`: Whether the remove button is a tab stop of its own.
+   *
+   * `FilterInput` writes `false` on the chips in its `tags` slot: the field's
+   * text is its one tab stop, and the arrow keys move from the text to the
+   * chips, as in a `multiple` Combobox. No attribute: it is coordination
+   * between elements, as `Tag.dismissTabStop` is. (property only)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -46846,8 +47053,9 @@ export type CustomElements = {
    * first colon, reads a leading `-` as the negation, and reads a word in
    * brackets before the colon as the comparison.
    *
-   * **Keyboard.** Focus stays in the text. The text names the highlighted
-   * suggestion as its `aria-activedescendant`.
+   * **Keyboard.** Focus stays in the text, which is the field's one tab stop. The
+   * text names the highlighted suggestion as its `aria-activedescendant`, and the
+   * arrow keys reach the tokens.
    *
    * | Key | What it does |
    * |---|---|
@@ -46905,12 +47113,24 @@ export type CustomElements = {
    *   and removing the chip alone would leave its value ticked in the hidden
    *   menu. Its dismissal is treated as the field being filtered by nothing, so
    *   it fires `helix-facet` like every other change, and the chip goes when the
-   *   filter goes.
+   *   filter goes. Set `chips` and the field adds, updates, and removes those
+   *   chips itself, from every `helix-facet` you do not cancel.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `chips`: Whether the field keeps a `FilterChip` for each filter in its `tags` slot,
+   * from the `helix-facet` events it hears.
+   *
+   * Off, you build the chips, which is what you do when your own model holds
+   * the filters. On, a filter typed, picked, or changed adds or updates the
+   * chip for its field, one with no values takes it away (unless its
+   * comparison takes none, such as "is empty"), and removing the chip clears
+   * the filter. A `helix-facet` you cancel changes no chip.
+   *
+   * The chips are elements the field adds to its own children, so leave this
+   * off where a framework renders those children and would remove them.
    * - `clearable`: Shows a button that empties the field.
    *
    * The text only. The tokens are the consumer's markup and this element is not
@@ -46922,6 +47142,18 @@ export type CustomElements = {
    * - `filter-suggestions`/`filterSuggestions`: Whether the panel narrows itself to the suggestions that hold the term
    * being typed, as React Aria's Autocomplete filters. Off, the panel shows
    * what you slot and you narrow it.
+   * - `loading`: Whether the suggestions are still loading, such as while a request for the
+   * values of a typed key is out.
+   *
+   * The panel opens on `loading-text`, or the `loading` slot, while the field
+   * has focus, and a screen reader hears it. Slot the options and clear this
+   * when they arrive.
+   * - `loading-text`/`loadingText`: Text the panel shows while the suggestions load.
+   * - `no-results-text`/`noResultsText`: Text the panel shows when `filter-suggestions` hides every suggestion, such
+   * as "No matching filters".
+   *
+   * Empty, or no `no-results` slot, and the panel closes instead, as it does
+   * when it has nothing to offer.
    * - `placeholder`: The text shown while the field is empty.
    *
    * Not a label: it goes when typing starts.
@@ -47083,6 +47315,8 @@ export type CustomElements = {
    * - `feedback`: The message that says what is wrong, for content richer than a string. It shows while there is a message.
    * - `hint`: Help under the control, for content richer than the `hint` text.
    * - `label`: The label, for content richer than the `label` text.
+   * - `loading`: What the panel shows while `loading` is set, for content richer than `loading-text`.
+   * - `no-results`: What the panel shows when `filter-suggestions` hides every suggestion, for content richer than `no-results-text`.
    * - `start`: Content before the text, such as a search icon.
    * - `suggestions`: Suggestions for what to type next, as `Option`s and `Option.Group`s.
    * - `tags`: The active filters, as `FilterChip`s or `Tag`s.
@@ -47166,12 +47400,14 @@ export type CustomElements = {
    *
    * - `clear`: The button that empties the field.
    * - `control`: The input itself.
+   * - `empty`: Shown in the panel when `filter-suggestions` hides every suggestion.
    * - `feedback`: The error message under the field.
    * - `field`: The box that holds everything.
    * - `hint`: The help text under the field, shown while there is no error.
    * - `label`: The label above the field.
    * - `lead`: The box before the text that holds the `start` slot.
    * - `live`: The live region that says how many suggestions the open panel offers. It is rendered from the first time the panel opens with suggestions.
+   * - `loading`: Shown in the panel while the suggestions load.
    * - `rest`: The count of tokens that did not fit. It is a `<button>` with `expandable` and a `<span>` without it.
    * - `surface`: The floating panel the suggestions sit in.
    * - `tags`: The row the tokens sit in.
@@ -47181,6 +47417,8 @@ export type CustomElements = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `invalid`: The field has an error to show, from the browser's validation or from your `feedback`.
+   * - `loading`: While `loading` is set.
+   * - `no-results`: `filter-suggestions` hid every suggestion, and `no-results-text` or the `no-results` slot says so.
    * - `open`: The suggestions are open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -47202,7 +47440,9 @@ export type CustomElements = {
    * **`relative` shows the same reading in words**, such as "3 hours ago" at
    * `long`, "3 hr. ago" at `short` and "3h ago" at `narrow`, the styles
    * `sl-relative-time` offers. `numeric="always"` says "1 day ago" where the
-   * default says "yesterday".
+   * default says "yesterday". Both readings round the count, as
+   * `sl-relative-time` does: 100 seconds ago is "2 minutes ago", and 59.6
+   * minutes is "1 hour".
    *
    * **`date-style` and `time-style` take each locale's own pattern**, such as
    * "Tuesday, August 4, 2026" at `full`, and stand in for the separate fields,
@@ -48850,6 +49090,9 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `setRangeText(replacement: string, start?: number, end?: number, selectMode?: SelectionMode) => void`: Replaces a range of the text, as the native method does: the selection
+   * where `start` and `end` are left out, and `selectMode` says what is
+   * selected after. It sends no event, as the native method sends none.
    * - `setSelectionRange(start: number, end: number, direction?: SelectionDirection) => void`: Selects the range from `start` to `end` in one call, which setting
    * `selectionStart` and `selectionEnd` one at a time cannot always do.
    *
@@ -53520,7 +53763,9 @@ export type CustomElements = {
    * speaks it: `feedback` replaces the message under the field and does not
    * reach the bubble. Unset is the sentence registered for the page's
    * language, then the English.
-   * - `decrement-label`/`decrementLabel`: The name of the step down button, read by screen readers.
+   * - `decrement-label`/`decrementLabel`: The name of the step down button, read by screen readers. The field's
+   * label follows it, so a reader hears "Decrease Quantity", as React Aria
+   * names its steppers.
    * - `format-options`/`formatOptions`: `Intl.NumberFormat` options the number is shown with while the field is
    * not being edited: a currency, a percent, a unit, or a number of decimals.
    * Written as JSON in the attribute.
@@ -53528,7 +53773,9 @@ export type CustomElements = {
    * ```html
    * <helix-number-input format-options='{"style":"currency","currency":"EUR"}'></helix-number-input>
    * ```
-   * - `increment-label`/`incrementLabel`: The name of the step up button, read by screen readers.
+   * - `increment-label`/`incrementLabel`: The name of the step up button, read by screen readers. The field's
+   * label follows it, so a reader hears "Increase Quantity", as React Aria
+   * names its steppers.
    * - `large-step`/`largeStep`: How many steps `PageUp` and `PageDown` move.
    *
    * Ten steps, which is the convention every spinner on the platform follows,
@@ -53710,8 +53957,10 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `stepUp(large = false) => void`: Steps the value up, by `largeStep` steps when `large` is set.
-   * - `stepDown(large = false) => void`: Steps the value down, by `largeStep` steps when `large` is set.
+   * - `stepUp(count: number | boolean = 1) => void`: Steps the value up by `step`, `count` times, as the native method and
+   * `Input.stepUp` do. `true` takes `largeStep` steps, as `PageUp` does.
+   * - `stepDown(count: number | boolean = 1) => void`: Steps the value down by `step`, `count` times. `true` takes `largeStep`
+   * steps, as `PageDown` does.
    *
    * The same path a press of the down arrow takes, so a consumer driving this
    * from their own control gets the clamping and the announcement rather than
@@ -58905,12 +59154,21 @@ export type CustomElements = {
    * sequence is correct in the server's markup, where the root cannot count its
    * slotted children.
    *
+   * `active` names a step by its `value`. A step with no `value` is named by its
+   * place, counted from 1, so a sequence written without values moves as one
+   * written with them, and `helix-activate` says `1`, `2` and so on. Give every
+   * step a value or none, because a value of `2` and the second place are one
+   * name.
+   *
    * `linear` keeps a reader from passing a stage they have not finished, as Ark
    * UI's linear steps do: a stage ahead is out of reach, and its button disabled,
    * until every stage before it is `complete` or `optional`. Going back is always
    * allowed. `next()` and `previous()` move one stage either way, under the
    * same rules, for your own buttons. `reset()` goes back to the first stage and
-   * clears every stage's `complete`, as Ark UI's `resetStep` does.
+   * clears every stage's `complete`, as Ark UI's `resetStep` does. A button
+   * anywhere on the page calls them with no script, as Ark UI's previous and
+   * next triggers do: give it `commandfor` with the sequence's `id`, and
+   * `command="--previous"`, `"--next"` or `"--reset"`.
    *
    * `completion="passed"` marks a stage `complete` once a reader moves past it,
    * as Ark UI counts a stage before the current one as completed. Going back
@@ -58937,18 +59195,21 @@ export type CustomElements = {
    * button is described by its `complete-label`.
    *
    * **Keyboard.** Each stage's name is a button and its own tab stop, and Enter
-   * or Space goes to the stage. Set `arrows` and the arrow keys move focus
-   * between the names as well, as Ark UI's steps do: Left and Right along a row,
-   * Up and Down a column, Home and End to the first and the last. The arrows
-   * pass over a disabled stage and one a linear sequence holds out of reach,
-   * and they move focus without going to the stage.
+   * or Space goes to the stage. Set `arrows` and the names are one tab stop, the
+   * current stage's, and the arrow keys move focus between them: Left and Right
+   * along a row, Up and Down a column, Home and End to the first and the last.
+   * The stop follows focus, so Tab leaves the sequence and Shift+Tab comes back
+   * to the name the reader left. The arrows pass over a disabled stage and one a
+   * linear sequence holds out of reach, and they move focus without going to the
+   * stage.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
    * - `arrows`: Whether the arrow keys move focus between the stages' names, along the
-   * way the steps run. Off by default, so the arrows keep scrolling the page.
+   * way the steps run, and the names are one tab stop. Off by default, so the
+   * arrows keep scrolling the page.
    * - `completion`: What marks a stage `complete`.
    *
    * Absent, you do: each step's `complete` is yours, because a reader who
@@ -59119,7 +59380,9 @@ export type CustomElements = {
    * - `disabled`: Whether the stage is disabled, so the user cannot go to it.
    * - `optional`: Whether a reader may pass the stage without finishing it, in a sequence
    * with `linear`. Ark UI's skippable step.
-   * - `value`: The value the step sends in `helix-select`.
+   * - `value`: The value the step sends in `helix-select`, and what names the step in its
+   * sequence's `active`. Without one, the sequence names the step by its place,
+   * counted from 1.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -64510,6 +64773,12 @@ export type CustomElements = {
    * captions, and poster treatment. `Sandbox` takes its preview and `Menu` its
    * trigger the same way.
    *
+   * **The player is a `Video` or a plain `<video>`.** Either takes `src` and
+   * `poster` from the entry, is named by it, plays on, and answers Shift with N
+   * or P while focused. A plain `<video>` has no previous and next controls
+   * that send `helix-previous` or `helix-next`, so its moves are the entries,
+   * the menu, and your own buttons calling `previous()` and `next()`.
+   *
    * **Entries are markup.** React skips properties it would set imperatively
    * during hydration, so an array property on a custom element is missing on the
    * first paint of a server-rendered page. `using-the-elements.mdx` has the
@@ -64542,7 +64811,8 @@ export type CustomElements = {
    *
    * **The player is named by the current entry**, and the device's own media
    * controls show the entry as the title. A player you gave a `label` keeps
-   * your name, and only the title follows the entry.
+   * your name, and only the title follows the entry. A plain `<video>` is
+   * named through `aria-label`, unless you wrote one.
    *
    * **Keyboard.** The entries take one stop in the tab order: the entry you
    * last focused, or the current entry before you have focused one. Enter or
@@ -65233,6 +65503,11 @@ export type CustomElements = {
    * commas. Their rows carry `aria-disabled`, the keys and typing pass over
    * them, and a press, Space, or Control with A does not select them.
    *
+   * **Rows a stylesheet can tell apart.** A chosen row carries `data-selected`,
+   * a disabled one `data-disabled`, as React Aria's rows do, and the row the
+   * keys are on, which holds the tab stop, `data-active`, whether or not the
+   * list has focus.
+   *
    * **Loading more.** `helix-range-change` fires as the items on screen change,
    * and `range` holds them. `helix-load-more` fires once a reader is within one
    * screen of the end, once for each length of the set: add to `items` and it can
@@ -69167,7 +69442,8 @@ export type CustomElementsSolidJs = {
    * field taking more. A draft that fails them does not send, and the composer
    * takes `:state(invalid)` and `aria-invalid` once the reader has tried to send
    * it, the form was submitted, or the reader edited the field and left it.
-   * Tabbing past an empty composer marks nothing.
+   * Sending an empty required composer counts as trying. Tabbing past an empty
+   * composer marks nothing.
    *
    * **`typing` says whether the user is writing**, and `helix-typing` is sent
    * each time it changes: when they start, and when they send or stop for
@@ -69478,8 +69754,10 @@ export type CustomElementsSolidJs = {
    * there when the transcript opened. A turn is said with its author first, such
    * as "Ada: It ships today" (`arrival-label`), where its author can be named.
    *
-   * Pass the turns as children or as `turns` data. Do not use both. Children
-   * render from the server and suit most conversations. `turns` draws a long
+   * Pass the turns as children or as `turns` data. Do not use both: a chat given
+   * both draws every turn from `turns` and then the children, and says so once
+   * in the console. Children render from the server and suit most
+   * conversations. `turns` draws a long
    * transcript one window at a time, so the log needs a block size of its own.
    *
    * **A conversation is built from three elements.** The chat holds the
@@ -69495,7 +69773,10 @@ export type CustomElementsSolidJs = {
    * it takes them away. Anything slotted into `status` is drawn first.
    *
    * **Keyboard.** The transcript moves between turns the way a feed does. Each
-   * turn says its place, such as "3 of 40", windowed or not.
+   * turn says its place, such as "3 of 40", windowed or not. The transcript is
+   * a tab stop while it holds a turn, and the turn a reader moved to is one
+   * too. Moving to an older turn unpins a transcript that scrolls and scrolls
+   * the turn into view, and moving to the newest pins it again.
    *
    * | Key | What it does |
    * |---|---|
@@ -69706,6 +69987,10 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `empty`: The conversation has no turns.
+   * - `loading`: Older turns are loading: `history` is `loading`.
+   * - `pinned`: The transcript follows its newest turn.
+   * - `typing`: `typing` names someone on the other side.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-headless-chat": Partial<
@@ -70217,7 +70502,11 @@ export type CustomElementsSolidJs = {
    * from the accessibility tree and left out of a copy. Set `mark-lines` to
    * mark lines a reader should look at, such as `2, 4-6`: the block draws a
    * band behind each run, placed where the lines are laid out, so it follows a
-   * highlighter's markup and lines that wrap. Set `wrap` to wrap long lines
+   * highlighter's markup and lines that wrap. `added-lines` and
+   * `removed-lines` mark lines the same way as inserted and deleted, as
+   * Expressive Code's `ins` and `del` do, in code that is not a diff. The bands
+   * are drawn and hidden from screen readers, so say in the text around the
+   * block what a marked line means. Set `wrap` to wrap long lines
    * rather than scroll them; a gutter then numbers each line where it starts.
    * Set `wrappable` for a button in the header that turns `wrap` on and off,
    * pressed while the lines wrap.
@@ -70286,6 +70575,8 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `added-lines`/`addedLines`: The lines to mark as inserted, as numbers and ranges counted from 1, such
+   * as `3-4`. Drawn as `mark-lines` is, in the added color. Not for a diff.
    * - `code-label`/`codeLabel`: The name of a block that scrolls, which is a tab stop while it does.
    *
    * Where the block has a name, the scroller says it too, such as "Code,
@@ -70362,6 +70653,8 @@ export type CustomElementsSolidJs = {
    * `no-copy=""` on hosts that never asked for one, and the rule about a
    * reflected property taking no default is satisfied by the default being
    * `false`.
+   * - `removed-lines`/`removedLines`: The lines to mark as deleted, as numbers and ranges counted from 1. Drawn
+   * as `mark-lines` is, in the removed color. Not for a diff.
    * - `show-unchanged-label`/`showUnchangedLabel`: The words of a button that shows a folded run of unchanged lines, in a
    * diff with `context-lines`. `{count}` is how many.
    * - `variant`: How a diff's two versions are arranged. It has no effect without `diff`.
@@ -70441,6 +70734,8 @@ export type CustomElementsSolidJs = {
    * - `actions`: Controls for the block, in the header before the copy button.
    * - `copied-icon`: The copy button's icon after a copy. Defaults to a check mark.
    * - `copy-icon`: The copy button's icon before a copy. Defaults to a clipboard.
+   * - `expand-icon`: An icon on the button that shows every line of a capped block, before its words.
+   * - `label`: The block's name in the header, such as a file icon beside the file name. Replaces `label` and `language` there, and draws the header.
    *
    * ## CSS Custom Properties
    *
@@ -70488,7 +70783,9 @@ export type CustomElementsSolidJs = {
    * - `header`: The bar that holds the name and the copy button, shown when there is a name.
    * - `hunk`: In a diff, a `@@` line saying where the lines under it are.
    * - `label`: The block's name: its `label`, or its `language` where it has no label.
-   * - `mark`: The band behind a run of lines `mark-lines` names. The block writes where the run is laid out into `--code-block-mark-start`, `--code-block-mark-size`, and `--code-block-mark-inline-size` on it. Hidden from the accessibility tree.
+   * - `mark`: The band behind a run of lines `mark-lines`, `added-lines` or `removed-lines` names. The block writes where the run is laid out into `--code-block-mark-start`, `--code-block-mark-size`, and `--code-block-mark-inline-size` on it. Hidden from the accessibility tree.
+   * - `mark-added`: The band behind a run of lines `added-lines` names. Applied with `mark`.
+   * - `mark-removed`: The band behind a run of lines `removed-lines` names. Applied with `mark`.
    * - `marker`: In a diff, the `+`, `-`, or space that starts a line.
    * - `new`: In a split diff, the new version's `<pre>`.
    * - `number`: In a diff, a line number. In a `wrap` block with `line-numbers`, one line's number in the gutter, which the block makes as tall as the line it numbers through `--code-block-line-size`.
@@ -71102,10 +71399,11 @@ export type CustomElementsSolidJs = {
    * the anchor the browser points its bubble at.
    *
    * **Text that is not a color is bad input**, so a form does not submit
-   * `#00` from a half-typed value. The picker draws no message of its own, so
-   * reporting it as each keystroke arrives shows nothing until the form asks;
-   * Color Input shows its own message against the field the reader typed
-   * into.
+   * `#00` from a half-typed value. The picker marks it, and says
+   * `badInputMessage` under itself, once the reader leaves the value field or
+   * presses Enter, and a missing color once the reader has committed one or a
+   * form has refused the picker. Color Input shows its own message against the
+   * field the reader typed into.
    * - `saturation-label`/`saturationLabel`: What the square's horizontal ramp is called.
    * - `square-text`/`squareText`: What a screen reader hears for the square's place, the color's two
    * numbers and its name, on whichever of its two inputs it is on.
@@ -71224,14 +71522,10 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: A reset ends any typing and takes back text that was not a color, so the
+   * field shows the color the reset put back.
    * - `requestValue(next: string) => boolean`: Blocks every change while `readOnly` is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the square.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
@@ -71312,7 +71606,7 @@ export type CustomElementsSolidJs = {
    * - `eyedropper-live`: The live region of the button inside `eyedropper`, which says its pending label.
    * - `eyedropper-spinner`: The ring the eyedropper button turns while it is pending.
    * - `eyedropper-text`: The words on the button inside `eyedropper`, trimmed to their capitals and baseline.
-   * - `feedback`: The message under the picker, while `feedback` is set.
+   * - `feedback`: The message under the picker: `feedback`, or what is wrong with the answer once the picker is marked invalid.
    * - `field`: One channel's number field with its label, in `channel-fields`.
    * - `field-input`: The number input in a channel's field.
    * - `field-label`: The name above a channel's number input.
@@ -71471,12 +71765,13 @@ export type CustomElementsSolidJs = {
    * language.
    * - `multiple`: Whether more than one option can be chosen.
    *
-   * The list already does the work: `value` comes apart on commas, a press
-   * toggles rather than replaces, and the arrows move without choosing. What
-   * this adds is the tags, and keeping the panel open between picks.
+   * The list already does the work: `value` is the chosen values joined with
+   * commas, a press toggles rather than replaces, and the arrows move without
+   * choosing. What this adds is the tags, and keeping the panel open between
+   * picks.
    *
-   * A comma is therefore not available inside an option's value, which is the
-   * listbox's contract and not this element's to change.
+   * An option's value may hold a comma, and it is read as one value, as
+   * `Select` and `Listbox` read it. So may an answer the reader created.
    *
    * **The list is told, and the field is not.** `aria-multiselectable` belongs
    * to `listbox`, `grid`, `tree` and `tablist`, and `combobox` dropped it in
@@ -71820,7 +72115,8 @@ export type CustomElementsSolidJs = {
    * | `hotkey`, Command or Control with K by default | Opens the palette from anywhere on the page, or closes it. With `inline`, puts focus in its filter field. |
    * | Down, Up | Moves the highlight to the next or the previous command, round from the last to the first. |
    * | Page Down, Page Up | Moves the highlight by as many commands as the list shows at once. |
-   * | Home, End, Left, Right | Move the caret in the filter field. |
+   * | Home, End | Move the caret in the filter field. With `home-end="list"`, move the highlight to the first or the last command. |
+   * | Left, Right | Move the caret in the filter field. |
    * | Enter | Runs the highlighted command, or follows it where it is a link, and closes the palette. On a command with `opens`, shows its page. |
    * | Command or Control with Enter | Takes the highlighted command's `alternate` destination, where it has one. |
    * | Backspace | In an empty filter on a page, goes back to the page before. |
@@ -71842,6 +72138,11 @@ export type CustomElementsSolidJs = {
    * - `filter-delay`/`filterDelay`: How long typing rests before the commands are filtered, in milliseconds,
    * so a palette filtered on a server sends one `helix-filter` for a word.
    * `0` filters on every keystroke. See Listbox's `filter-delay`.
+   * - `home-end`/`homeEnd`: Where Home and End go from the filter field.
+   *
+   * Absent, they move the caret, as APG's combobox has them. `list` moves the
+   * highlight to the first or the last command, as React Aria's Autocomplete
+   * does, and Shift with either still selects the text.
    * - `hotkey`: The key that opens the palette, written as `mod+k`, `shift+p`, or `k`,
    * in Kbd's chord spelling: `mod` is Command or Control, `ctrl`, `cmd`,
    * `alt` and `shift` the keys they name.
@@ -71856,6 +72157,9 @@ export type CustomElementsSolidJs = {
    * Choosing a command says `helix-select` and leaves the list where it is,
    * and `open`, `toggle` and the dialog's parts do nothing.
    * - `label`: Accessible name for the overlay, which has no visible heading.
+   * - `layout`: How the commands are laid out, as Listbox's `layout`: `grid` draws them in
+   * rows and columns, for a palette of icons or emoji, and the arrow keys
+   * follow the rows and the columns. Absent is one command under another.
    * - `load-error`/`loadError`: What the list says when its commands could not be loaded, such as after a
    * request to a server fails. Empty, null or no attribute is no error, so
    * removing the attribute clears it. Passed to the list, which shows it
@@ -72268,10 +72572,15 @@ export type CustomElementsSolidJs = {
    *
    * Sort and filter apply to the whole set, including the rows on other pages.
    *
-   * **The cell values do not server-render.** The headings and the row elements
-   * do. Reading a cell needs the columns, and Lit SSR does not pass the column
-   * children to this element, so a crawler sees an empty table of the right
-   * shape. Use `Table` when the served HTML has to carry the values.
+   * **Write the first page as rows, so the served HTML carries the values.** The
+   * table reads each cell from its column, and a server does not pass the column
+   * children to this element, so on its own it serves the headings and no values.
+   * Write the first page under the columns as `TableRow` and `TableCell`
+   * elements, in the table's sort and page size and formatted as its columns draw
+   * them. The table shows your rows until `rows` holds a row, then draws its own
+   * in their place and leaves yours in the page, unshown. A development build
+   * warns when the two differ. In React, map the first page of the same array in
+   * the same server component.
    *
    * `selectable` adds a column of checkboxes, keyed on `row-key`:
    *
@@ -72621,7 +72930,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The columns, as `TableColumn` elements.
+   * - `(default)`: The columns, as `TableColumn` elements, and the first page served as `TableRow` elements, which show until `rows` holds a row.
    * - `empty`: Content shown when there are no rows to show and none are loading, such as a picture and a link. Falls back to `empty-text`, which the live region still says.
    * - `error`: Content shown while `error-text` is set, such as a button that tries again. Falls back to `error-text`, which the live region still says.
    * - `footer`: Content below the grid. It replaces the built-in pagination.
@@ -75373,9 +75682,10 @@ export type CustomElementsSolidJs = {
    * press. `requestChange` documents the pattern.
    *
    * **Keyboard.** The remove button is a tab stop of its own, and Enter or Space
-   * on it asks to remove the filter. In a `FilterInput`, Backspace in the empty
-   * field asks to remove the last chip, the arrow keys move between the field
-   * and the chips, and Delete or Backspace on a chip asks to remove it.
+   * on it asks to remove the filter. In a `FilterInput`, the field's text is the
+   * one tab stop: Backspace in the empty field asks to remove the last chip, the
+   * arrow keys move between the field and the chips, and Delete or Backspace on
+   * a chip asks to remove it.
    *
    * The remove button is named `dismiss-label` followed by the chip's words,
    * such as "Remove filter Status is not open", so a row of chips says which
@@ -75431,6 +75741,12 @@ export type CustomElementsSolidJs = {
    * reads. The moment somebody picks a different comparison it appears, which
    * makes an unusual filter look unusual.
    * - `dismissible`: Whether the element shows a control that dismisses it.
+   * - `dismissTabStop`: Whether the remove button is a tab stop of its own.
+   *
+   * `FilterInput` writes `false` on the chips in its `tags` slot: the field's
+   * text is its one tab stop, and the arrow keys move from the text to the
+   * chips, as in a `multiple` Combobox. No attribute: it is coordination
+   * between elements, as `Tag.dismissTabStop` is. (property only)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -75902,8 +76218,9 @@ export type CustomElementsSolidJs = {
    * first colon, reads a leading `-` as the negation, and reads a word in
    * brackets before the colon as the comparison.
    *
-   * **Keyboard.** Focus stays in the text. The text names the highlighted
-   * suggestion as its `aria-activedescendant`.
+   * **Keyboard.** Focus stays in the text, which is the field's one tab stop. The
+   * text names the highlighted suggestion as its `aria-activedescendant`, and the
+   * arrow keys reach the tokens.
    *
    * | Key | What it does |
    * |---|---|
@@ -75961,12 +76278,24 @@ export type CustomElementsSolidJs = {
    *   and removing the chip alone would leave its value ticked in the hidden
    *   menu. Its dismissal is treated as the field being filtered by nothing, so
    *   it fires `helix-facet` like every other change, and the chip goes when the
-   *   filter goes.
+   *   filter goes. Set `chips` and the field adds, updates, and removes those
+   *   chips itself, from every `helix-facet` you do not cancel.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `chips`: Whether the field keeps a `FilterChip` for each filter in its `tags` slot,
+   * from the `helix-facet` events it hears.
+   *
+   * Off, you build the chips, which is what you do when your own model holds
+   * the filters. On, a filter typed, picked, or changed adds or updates the
+   * chip for its field, one with no values takes it away (unless its
+   * comparison takes none, such as "is empty"), and removing the chip clears
+   * the filter. A `helix-facet` you cancel changes no chip.
+   *
+   * The chips are elements the field adds to its own children, so leave this
+   * off where a framework renders those children and would remove them.
    * - `clearable`: Shows a button that empties the field.
    *
    * The text only. The tokens are the consumer's markup and this element is not
@@ -75978,6 +76307,18 @@ export type CustomElementsSolidJs = {
    * - `filter-suggestions`/`filterSuggestions`: Whether the panel narrows itself to the suggestions that hold the term
    * being typed, as React Aria's Autocomplete filters. Off, the panel shows
    * what you slot and you narrow it.
+   * - `loading`: Whether the suggestions are still loading, such as while a request for the
+   * values of a typed key is out.
+   *
+   * The panel opens on `loading-text`, or the `loading` slot, while the field
+   * has focus, and a screen reader hears it. Slot the options and clear this
+   * when they arrive.
+   * - `loading-text`/`loadingText`: Text the panel shows while the suggestions load.
+   * - `no-results-text`/`noResultsText`: Text the panel shows when `filter-suggestions` hides every suggestion, such
+   * as "No matching filters".
+   *
+   * Empty, or no `no-results` slot, and the panel closes instead, as it does
+   * when it has nothing to offer.
    * - `placeholder`: The text shown while the field is empty.
    *
    * Not a label: it goes when typing starts.
@@ -76139,6 +76480,8 @@ export type CustomElementsSolidJs = {
    * - `feedback`: The message that says what is wrong, for content richer than a string. It shows while there is a message.
    * - `hint`: Help under the control, for content richer than the `hint` text.
    * - `label`: The label, for content richer than the `label` text.
+   * - `loading`: What the panel shows while `loading` is set, for content richer than `loading-text`.
+   * - `no-results`: What the panel shows when `filter-suggestions` hides every suggestion, for content richer than `no-results-text`.
    * - `start`: Content before the text, such as a search icon.
    * - `suggestions`: Suggestions for what to type next, as `Option`s and `Option.Group`s.
    * - `tags`: The active filters, as `FilterChip`s or `Tag`s.
@@ -76222,12 +76565,14 @@ export type CustomElementsSolidJs = {
    *
    * - `clear`: The button that empties the field.
    * - `control`: The input itself.
+   * - `empty`: Shown in the panel when `filter-suggestions` hides every suggestion.
    * - `feedback`: The error message under the field.
    * - `field`: The box that holds everything.
    * - `hint`: The help text under the field, shown while there is no error.
    * - `label`: The label above the field.
    * - `lead`: The box before the text that holds the `start` slot.
    * - `live`: The live region that says how many suggestions the open panel offers. It is rendered from the first time the panel opens with suggestions.
+   * - `loading`: Shown in the panel while the suggestions load.
    * - `rest`: The count of tokens that did not fit. It is a `<button>` with `expandable` and a `<span>` without it.
    * - `surface`: The floating panel the suggestions sit in.
    * - `tags`: The row the tokens sit in.
@@ -76237,6 +76582,8 @@ export type CustomElementsSolidJs = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `invalid`: The field has an error to show, from the browser's validation or from your `feedback`.
+   * - `loading`: While `loading` is set.
+   * - `no-results`: `filter-suggestions` hid every suggestion, and `no-results-text` or the `no-results` slot says so.
    * - `open`: The suggestions are open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -76259,7 +76606,9 @@ export type CustomElementsSolidJs = {
    * **`relative` shows the same reading in words**, such as "3 hours ago" at
    * `long`, "3 hr. ago" at `short` and "3h ago" at `narrow`, the styles
    * `sl-relative-time` offers. `numeric="always"` says "1 day ago" where the
-   * default says "yesterday".
+   * default says "yesterday". Both readings round the count, as
+   * `sl-relative-time` does: 100 seconds ago is "2 minutes ago", and 59.6
+   * minutes is "1 hour".
    *
    * **`date-style` and `time-style` take each locale's own pattern**, such as
    * "Tuesday, August 4, 2026" at `full`, and stand in for the separate fields,
@@ -77921,6 +78270,9 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `setRangeText(replacement: string, start?: number, end?: number, selectMode?: SelectionMode) => void`: Replaces a range of the text, as the native method does: the selection
+   * where `start` and `end` are left out, and `selectMode` says what is
+   * selected after. It sends no event, as the native method sends none.
    * - `setSelectionRange(start: number, end: number, direction?: SelectionDirection) => void`: Selects the range from `start` to `end` in one call, which setting
    * `selectionStart` and `selectionEnd` one at a time cannot always do.
    *
@@ -82659,7 +83011,9 @@ export type CustomElementsSolidJs = {
    * speaks it: `feedback` replaces the message under the field and does not
    * reach the bubble. Unset is the sentence registered for the page's
    * language, then the English.
-   * - `decrement-label`/`decrementLabel`: The name of the step down button, read by screen readers.
+   * - `decrement-label`/`decrementLabel`: The name of the step down button, read by screen readers. The field's
+   * label follows it, so a reader hears "Decrease Quantity", as React Aria
+   * names its steppers.
    * - `format-options`/`formatOptions`: `Intl.NumberFormat` options the number is shown with while the field is
    * not being edited: a currency, a percent, a unit, or a number of decimals.
    * Written as JSON in the attribute.
@@ -82667,7 +83021,9 @@ export type CustomElementsSolidJs = {
    * ```html
    * <helix-number-input format-options='{"style":"currency","currency":"EUR"}'></helix-number-input>
    * ```
-   * - `increment-label`/`incrementLabel`: The name of the step up button, read by screen readers.
+   * - `increment-label`/`incrementLabel`: The name of the step up button, read by screen readers. The field's
+   * label follows it, so a reader hears "Increase Quantity", as React Aria
+   * names its steppers.
    * - `large-step`/`largeStep`: How many steps `PageUp` and `PageDown` move.
    *
    * Ten steps, which is the convention every spinner on the platform follows,
@@ -82849,8 +83205,10 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `stepUp(large = false) => void`: Steps the value up, by `largeStep` steps when `large` is set.
-   * - `stepDown(large = false) => void`: Steps the value down, by `largeStep` steps when `large` is set.
+   * - `stepUp(count: number | boolean = 1) => void`: Steps the value up by `step`, `count` times, as the native method and
+   * `Input.stepUp` do. `true` takes `largeStep` steps, as `PageUp` does.
+   * - `stepDown(count: number | boolean = 1) => void`: Steps the value down by `step`, `count` times. `true` takes `largeStep`
+   * steps, as `PageDown` does.
    *
    * The same path a press of the down arrow takes, so a consumer driving this
    * from their own control gets the clamping and the announcement rather than
@@ -88110,12 +88468,21 @@ export type CustomElementsSolidJs = {
    * sequence is correct in the server's markup, where the root cannot count its
    * slotted children.
    *
+   * `active` names a step by its `value`. A step with no `value` is named by its
+   * place, counted from 1, so a sequence written without values moves as one
+   * written with them, and `helix-activate` says `1`, `2` and so on. Give every
+   * step a value or none, because a value of `2` and the second place are one
+   * name.
+   *
    * `linear` keeps a reader from passing a stage they have not finished, as Ark
    * UI's linear steps do: a stage ahead is out of reach, and its button disabled,
    * until every stage before it is `complete` or `optional`. Going back is always
    * allowed. `next()` and `previous()` move one stage either way, under the
    * same rules, for your own buttons. `reset()` goes back to the first stage and
-   * clears every stage's `complete`, as Ark UI's `resetStep` does.
+   * clears every stage's `complete`, as Ark UI's `resetStep` does. A button
+   * anywhere on the page calls them with no script, as Ark UI's previous and
+   * next triggers do: give it `commandfor` with the sequence's `id`, and
+   * `command="--previous"`, `"--next"` or `"--reset"`.
    *
    * `completion="passed"` marks a stage `complete` once a reader moves past it,
    * as Ark UI counts a stage before the current one as completed. Going back
@@ -88142,18 +88509,21 @@ export type CustomElementsSolidJs = {
    * button is described by its `complete-label`.
    *
    * **Keyboard.** Each stage's name is a button and its own tab stop, and Enter
-   * or Space goes to the stage. Set `arrows` and the arrow keys move focus
-   * between the names as well, as Ark UI's steps do: Left and Right along a row,
-   * Up and Down a column, Home and End to the first and the last. The arrows
-   * pass over a disabled stage and one a linear sequence holds out of reach,
-   * and they move focus without going to the stage.
+   * or Space goes to the stage. Set `arrows` and the names are one tab stop, the
+   * current stage's, and the arrow keys move focus between them: Left and Right
+   * along a row, Up and Down a column, Home and End to the first and the last.
+   * The stop follows focus, so Tab leaves the sequence and Shift+Tab comes back
+   * to the name the reader left. The arrows pass over a disabled stage and one a
+   * linear sequence holds out of reach, and they move focus without going to the
+   * stage.
    *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
    * - `arrows`: Whether the arrow keys move focus between the stages' names, along the
-   * way the steps run. Off by default, so the arrows keep scrolling the page.
+   * way the steps run, and the names are one tab stop. Off by default, so the
+   * arrows keep scrolling the page.
    * - `completion`: What marks a stage `complete`.
    *
    * Absent, you do: each step's `complete` is yours, because a reader who
@@ -88327,7 +88697,9 @@ export type CustomElementsSolidJs = {
    * - `disabled`: Whether the stage is disabled, so the user cannot go to it.
    * - `optional`: Whether a reader may pass the stage without finishing it, in a sequence
    * with `linear`. Ark UI's skippable step.
-   * - `value`: The value the step sends in `helix-select`.
+   * - `value`: The value the step sends in `helix-select`, and what names the step in its
+   * sequence's `active`. Without one, the sequence names the step by its place,
+   * counted from 1.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -93794,6 +94166,12 @@ export type CustomElementsSolidJs = {
    * captions, and poster treatment. `Sandbox` takes its preview and `Menu` its
    * trigger the same way.
    *
+   * **The player is a `Video` or a plain `<video>`.** Either takes `src` and
+   * `poster` from the entry, is named by it, plays on, and answers Shift with N
+   * or P while focused. A plain `<video>` has no previous and next controls
+   * that send `helix-previous` or `helix-next`, so its moves are the entries,
+   * the menu, and your own buttons calling `previous()` and `next()`.
+   *
    * **Entries are markup.** React skips properties it would set imperatively
    * during hydration, so an array property on a custom element is missing on the
    * first paint of a server-rendered page. `using-the-elements.mdx` has the
@@ -93826,7 +94204,8 @@ export type CustomElementsSolidJs = {
    *
    * **The player is named by the current entry**, and the device's own media
    * controls show the entry as the title. A player you gave a `label` keeps
-   * your name, and only the title follows the entry.
+   * your name, and only the title follows the entry. A plain `<video>` is
+   * named through `aria-label`, unless you wrote one.
    *
    * **Keyboard.** The entries take one stop in the tab order: the entry you
    * last focused, or the current entry before you have focused one. Enter or
@@ -94521,6 +94900,11 @@ export type CustomElementsSolidJs = {
    * commas. Their rows carry `aria-disabled`, the keys and typing pass over
    * them, and a press, Space, or Control with A does not select them.
    *
+   * **Rows a stylesheet can tell apart.** A chosen row carries `data-selected`,
+   * a disabled one `data-disabled`, as React Aria's rows do, and the row the
+   * keys are on, which holds the tab stop, `data-active`, whether or not the
+   * list has focus.
+   *
    * **Loading more.** `helix-range-change` fires as the items on screen change,
    * and `range` holds them. `helix-load-more` fires once a reader is within one
    * screen of the end, once for each length of the set: add to `items` and it can