@fusion.dev/helix-headless 0.144.0 → 0.145.0

package/types/vue.d.ts

@@ -94,6 +94,7 @@ import type {
   HelixHeadlessMegamenu,
   HelixHeadlessMenuItem,
   HelixHeadlessMenu,
+  HelixHeadlessMenuSection,
   HelixHeadlessMeter,
   HelixHeadlessNavigation,
   HelixHeadlessNotificationGroup,
@@ -146,6 +147,7 @@ import type {
   HelixHeadlessTextarea,
   HelixHeadlessTimeInput,
   HelixHeadlessTimePicker,
+  HelixHeadlessTimelineGroup,
   HelixHeadlessTimelineItem,
   HelixHeadlessTimeline,
   HelixHeadlessToastItem,
@@ -184,6 +186,7 @@ import type {
   HelixSelectEvent,
   HelixActivateEvent,
   HelixSendEvent,
+  HelixTypingEvent,
   HelixBeforePinEvent,
   HelixHistoryEvent,
   HelixPinEvent,
@@ -194,7 +197,10 @@ import type {
   HelixSampleStartEvent,
   HelixCreateEvent,
   HelixFilterEvent,
+  HelixCopyErrorEvent,
+  HelixExpandEvent,
   HelixFilteredEvent,
+  HelixLoadMoreEvent,
   HelixNavigateEvent,
   HelixReorderEvent,
   HelixReorderedEvent,
@@ -212,7 +218,9 @@ import type {
   HelixGraphSignalEvent,
   HelixGraphZoomEvent,
   HelixResizeEvent,
+  HelixClearEvent,
   HelixShortcutEvent,
+  HelixActionEvent,
   HelixMapPartChangeEvent,
   HelixMapClusterEvent,
   HelixMapPanEvent,
@@ -220,6 +228,7 @@ import type {
   HelixMapRotateEvent,
   HelixMapTiltEvent,
   HelixMapZoomEvent,
+  HelixToggleEvent,
   HelixReadEvent,
   HelixCompleteEvent,
   HelixBeforeCollapseEvent,
@@ -227,8 +236,11 @@ import type {
   HelixCollapseEvent,
   HelixResizedEvent,
   HelixTourAskEvent,
+  HelixLoadEvent,
+  HelixEndEvent,
   HelixNextEvent,
   HelixPreviousEvent,
+  HelixRangeChangeEvent,
 } from "@fusion.dev/helix-headless";
 import type { HTMLAttributes, PublicProps, EmitFn, EmitsToProps } from "vue";
 
@@ -316,6 +328,22 @@ too. */
 Unset takes the accordion's `heading-level`, and 3 where that is unset
 too. */
   headingLevel?: (HelixHeadlessAccordionItem["headingLevel"]) | undefined;
+  /** Whether find in page searches the section while it is closed, and opens it
+on a match.
+
+Off by default. A closed section is then `hidden="until-found"`, which
+hides through `content-visibility`, so a stylesheet that animates the
+section closed shows an empty box for the length of that animation. The
+accordion's own `hidden-until-found` turns it on for every section. */
+  "hidden-until-found"?: (HelixHeadlessAccordionItem["hiddenUntilFound"]) | undefined;
+  /** Whether find in page searches the section while it is closed, and opens it
+on a match.
+
+Off by default. A closed section is then `hidden="until-found"`, which
+hides through `content-visibility`, so a stylesheet that animates the
+section closed shows an empty box for the length of that animation. The
+accordion's own `hidden-until-found` turns it on for every section. */
+  hiddenUntilFound?: (HelixHeadlessAccordionItem["hiddenUntilFound"]) | undefined;
   /** A group name. Opening an item closes the other items with the same name,
 as `<details name>` does.
 
@@ -372,6 +400,14 @@ Unset is 3. An item's own `heading-level` wins over this. */
 
 Unset is 3. An item's own `heading-level` wins over this. */
   headingLevel?: (HelixHeadlessAccordion["headingLevel"]) | undefined;
+  /** Whether find in page searches every closed section, and opens the one it
+matches in. Each item's own `hidden-until-found` turns it on for that item
+alone. */
+  "hidden-until-found"?: (HelixHeadlessAccordion["hiddenUntilFound"]) | undefined;
+  /** Whether find in page searches every closed section, and opens the one it
+matches in. Each item's own `hidden-until-found` turns it on for that item
+alone. */
+  hiddenUntilFound?: (HelixHeadlessAccordion["hiddenUntilFound"]) | undefined;
   /** How many sections may be open at once.
 
 Absent is `multiple`, so nothing closes unexpectedly and the default costs
@@ -400,6 +436,12 @@ export type HelixHeadlessAnnouncementHelixDismissElementEvent =
   HelixHeadlessAnnouncementElementEvent<HelixDismissEvent>;
 
 export type HelixHeadlessAnnouncementVueProps = {
+  /** How long the announcement stays, in milliseconds, before it sends
+`helix-dismiss`. When it is not set, it stays until it is dismissed.
+
+Read once when the announcement is first rendered, as `Toast` reads its
+own. The clock stops while the pointer or focus is on the announcement. */
+  duration?: (HelixHeadlessAnnouncement["duration"]) | undefined;
   /** The band's color.
 
 Paint only: unlike `Callout`, no value here draws a mark, changes the label,
@@ -440,7 +482,7 @@ would catch. */
 };
 
 export type HelixHeadlessAnnouncementVueEvents = {
-  /** The dismiss button was pressed. The announcement does not remove itself, so remove it in response. Cancelable. */
+  /** The dismiss button was pressed, or `duration` ran out. The announcement does not remove itself, so remove it in response. Cancelable. */
   "helix-dismiss": HelixHeadlessAnnouncementHelixDismissElementEvent;
 };
 
@@ -822,6 +864,12 @@ export type HelixHeadlessBreadcrumbsVueProps = {
   /** The landmark's name, read by screen readers. An `aria-label` on the host
 wins over it. */
   label?: (HelixHeadlessBreadcrumbs["label"]) | undefined;
+  /** The trail as data, drawn as crumbs before any you slot. The last item is the
+current page.
+
+React Aria's `items`. A property only: a trail is built by script, and an
+attribute would put the whole path into the markup twice. */
+  items?: (HelixHeadlessBreadcrumbs["items"]) | undefined;
 };
 
 export type HelixHeadlessBreadcrumbsVueEvents = {};
@@ -1743,6 +1791,18 @@ read out in English. */
   label?: (HelixHeadlessCarousel["label"]) | undefined;
   /** Whether moving past either end wraps to the other. */
   loop?: (HelixHeadlessCarousel["loop"]) | undefined;
+  /** Whether a mouse can drag the track from slide to slide.
+
+Off unless asked for, because a press on a slide is then the start of a
+drag, and text in a slide can no longer be selected with the mouse. A drag
+of a few pixels or less is still a press. */
+  "mouse-drag"?: (HelixHeadlessCarousel["mouseDrag"]) | undefined;
+  /** Whether a mouse can drag the track from slide to slide.
+
+Off unless asked for, because a press on a slide is then the start of a
+drag, and text in a slide can no longer be selected with the mouse. A drag
+of a few pixels or less is still a press. */
+  mouseDrag?: (HelixHeadlessCarousel["mouseDrag"]) | undefined;
   /** The name of the control that moves to the next slide. */
   "next-label"?: (HelixHeadlessCarousel["nextLabel"]) | undefined;
   /** The name of the control that moves to the next slide. */
@@ -1884,6 +1944,14 @@ case is the absent attribute, and the styles read it that way. */
   "previous-label"?: (HelixHeadlessCarousel["previousLabel"]) | undefined;
   /** The name of the control that moves to the previous slide. */
   previousLabel?: (HelixHeadlessCarousel["previousLabel"]) | undefined;
+  /** The word screen readers announce in place of the carousel's role, set as
+`aria-roledescription`. Translate it with the rest of your text, or empty
+it to leave the role as `group`. */
+  "role-label"?: (HelixHeadlessCarousel["roleLabel"]) | undefined;
+  /** The word screen readers announce in place of the carousel's role, set as
+`aria-roledescription`. Translate it with the rest of your text, or empty
+it to leave the role as `group`. */
+  roleLabel?: (HelixHeadlessCarousel["roleLabel"]) | undefined;
   /** The name of each slide, with `{index}` and `{count}` filled in. */
   "slide-label"?: (HelixHeadlessCarousel["slideLabel"]) | undefined;
   /** The name of each slide, with `{index}` and `{count}` filled in. */
@@ -1919,10 +1987,11 @@ export type HelixHeadlessChatComposerElementEvent<E = Event> = TypedEvent<
 /** `helix-send` event type */
 export type HelixHeadlessChatComposerHelixSendElementEvent =
   HelixHeadlessChatComposerElementEvent<HelixSendEvent>;
+/** `helix-typing` event type */
+export type HelixHeadlessChatComposerHelixTypingElementEvent =
+  HelixHeadlessChatComposerElementEvent<HelixTypingEvent>;
 
 export type HelixHeadlessChatComposerVueProps = {
-  /** Whether the composer blocks input, such as while a turn is being sent. */
-  disabled?: (HelixHeadlessChatComposer["disabled"]) | undefined;
   /** The field's name, read by screen readers. */
   label?: (HelixHeadlessChatComposer["label"]) | undefined;
   /** Placeholder text shown in an empty field. */
@@ -1949,16 +2018,50 @@ button only.
 `button` is what a composer holding several paragraphs wants, where Enter
 has to mean a new line and nothing else. */
   submitOn?: (HelixHeadlessChatComposer["submitOn"]) | undefined;
+  /** How long after the last keystroke the user still counts as typing, in
+milliseconds. */
+  "typing-timeout"?: (HelixHeadlessChatComposer["typingTimeout"] | `${number}`) | undefined;
+  /** How long after the last keystroke the user still counts as typing, in
+milliseconds. */
+  typingTimeout?: (HelixHeadlessChatComposer["typingTimeout"]) | undefined;
   /** The text the user has written.
 
 It follows typing, so reading it gives the draft. Set it to seed a draft or
 to replace the one in the field, and set it to `''` to clear it. */
   value?: (HelixHeadlessChatComposer["value"]) | undefined;
+  /** Whether the control is disabled and cannot be used.
+
+Reflected, because the styled tier selects on it, and mirrored to
+`aria-disabled` rather than removing the element from the accessibility
+tree, so a screen reader can still announce that the control exists.
+
+The mirror itself is in `willUpdate` below, here rather than in each
+control, because here is where `disabled` is. */
+  disabled?: (HelixHeadlessChatComposer["disabled"]) | undefined;
+  /** The name the control's value is submitted under.
+
+**Reflected, and it is the exception to "reflect only what CSS selects
+on".** The platform builds a form's entry list from the `name` *content
+attribute*, not from the property, so a control named through the property
+submitted under no name at all and was silently dropped. Measured: two
+inputs in one form, one named by attribute and one by property, and the
+form carried a single entry.
+
+Safe for a React consumer, which is what the rule is protecting: React
+renders a custom element's props as attributes on the server, so the name
+is already in the markup being hydrated and reflecting it writes what is
+there. It is only a change to the markup when a consumer assigns it
+imperatively later, and nothing is hydrating by then.
+
+Here rather than on each control. */
+  name?: (HelixHeadlessChatComposer["name"]) | undefined;
 };
 
 export type HelixHeadlessChatComposerVueEvents = {
   /** Fired when the user sends their turn, and cancelable. */
   "helix-send": HelixHeadlessChatComposerHelixSendElementEvent;
+  /** The user started or stopped writing, with `typing` saying which, as the composer's `typing` does. */
+  "helix-typing": HelixHeadlessChatComposerHelixTypingElementEvent;
   /** The user changed the text. Read it from `value`, for a typing indicator or a saved draft. Sent on the composer and does not bubble. */
   input: HelixHeadlessChatComposerElementEvent;
 };
@@ -1983,6 +2086,18 @@ participants is the ordinary case for anything worth building this for.
 `me` and `them` are the conventional values and the stylesheet knows them;
 anything else is a name the consumer styles. */
   author?: (HelixHeadlessChatMessage["author"]) | undefined;
+  /** The author's name, as a screen reader says it at the start of the turn,
+such as "Support" or "Ada Lovelace".
+
+Empty reads "You" for `me`, the `author` itself where it is a name, and
+nothing for `them`. */
+  "author-label"?: (HelixHeadlessChatMessage["authorLabel"]) | undefined;
+  /** The author's name, as a screen reader says it at the start of the turn,
+such as "Support" or "Ada Lovelace".
+
+Empty reads "You" for `me`, the `author` itself where it is a name, and
+nothing for `them`. */
+  authorLabel?: (HelixHeadlessChatMessage["authorLabel"]) | undefined;
   /** Label for a message that did not send. */
   "failed-label"?: (HelixHeadlessChatMessage["failedLabel"]) | undefined;
   /** Label for a message that did not send. */
@@ -2063,6 +2178,18 @@ only the consumer knows whether the server has anything older. */
   historyText?: (HelixHeadlessChat["historyText"]) | undefined;
   /** The conversation's name, read by screen readers. */
   label?: (HelixHeadlessChat["label"]) | undefined;
+  /** The word a screen reader says for `me` when it names a turn. */
+  "me-label"?: (HelixHeadlessChat["meLabel"]) | undefined;
+  /** The word a screen reader says for `me` when it names a turn. */
+  meLabel?: (HelixHeadlessChat["meLabel"]) | undefined;
+  /** The name a screen reader gives a turn with both an author and a time.
+`{author}` is who wrote it and `{time}` is when, as the turn shows it. A
+turn with only one of the two is named by that one. */
+  "message-label"?: (HelixHeadlessChat["messageLabel"]) | undefined;
+  /** The name a screen reader gives a turn with both an author and a time.
+`{author}` is who wrote it and `{time}` is when, as the turn shows it. A
+turn with only one of the two is named by that one. */
+  messageLabel?: (HelixHeadlessChat["messageLabel"]) | undefined;
   /** Whether the transcript follows new turns to the bottom.
 
 The reader's scrolling asks first: `helix-before-pin` is cancelable, so a
@@ -2347,9 +2474,17 @@ export type HelixHeadlessCodeBlockVueProps = {
   "copied-label"?: (HelixHeadlessCodeBlock["copiedLabel"]) | undefined;
   /** The copy button's name and tooltip text after a copy. */
   copiedLabel?: (HelixHeadlessCodeBlock["copiedLabel"]) | undefined;
-  /** The copy button's name and tooltip text before a copy. */
+  /** The copy button's name and tooltip text before a copy.
+
+Where the block has a name, the button says it too, such as "Copy code,
+app.ts", so each copy button on a page with several blocks is told apart.
+In a diff, that is each file's own name. */
   "copy-label"?: (HelixHeadlessCodeBlock["copyLabel"]) | undefined;
-  /** The copy button's name and tooltip text before a copy. */
+  /** The copy button's name and tooltip text before a copy.
+
+Where the block has a name, the button says it too, such as "Copy code,
+app.ts", so each copy button on a page with several blocks is told apart.
+In a diff, that is each file's own name. */
   copyLabel?: (HelixHeadlessCodeBlock["copyLabel"]) | undefined;
   /** Whether the content is a unified diff, drawn as the lines it changed.
 
@@ -3369,6 +3504,9 @@ export type HelixHeadlessCopyButtonElementEvent<E = Event> = TypedEvent<
 /** `helix-copy` event type */
 export type HelixHeadlessCopyButtonHelixCopyElementEvent =
   HelixHeadlessCopyButtonElementEvent<HelixCopyEvent>;
+/** `helix-copy-error` event type */
+export type HelixHeadlessCopyButtonHelixCopyErrorElementEvent =
+  HelixHeadlessCopyButtonElementEvent<HelixCopyErrorEvent>;
 
 export type HelixHeadlessCopyButtonVueProps = {
   /** The button's name and tooltip text after a copy.
@@ -3405,72 +3543,6 @@ whatever its `type`. Declared here so its own page says what it holds. */
   value?: (HelixHeadlessCopyButton["value"]) | undefined;
   /**  */
   "aria-label"?: unknown;
-  /** What to send when the button is activated, and what to send it to.
-
-The platform's invoker attributes, forwarded onto the inner `<button>`
-rather than left on the host: only a real button is recognized as an
-invoker, so `commandfor` written on a custom element resolves nothing and
-the trigger silently does nothing at all. A wrapper has to hand them down,
-the same way `label` becomes `aria-label` in there.
-
-```html
-<helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
-```
-
-`commandFor` spells its attribute out, because Lit lowercases a property
-name to derive one rather than dash-casing it, and what a consumer writes
-is the platform's `commandfor`. */
-  command?: (HelixHeadlessCopyButton["command"]) | undefined;
-  /** The id of the element the command is sent to. */
-  commandfor?: (HelixHeadlessCopyButton["commandFor"]) | undefined;
-  /** The id of the element the command is sent to. */
-  commandFor?: (HelixHeadlessCopyButton["commandFor"]) | undefined;
-  /** Where this button's submission goes, overriding the form's own.
-
-**The five `form*` overrides work by writing the form and putting it back**,
-which is the only mechanism available and is closer to the platform than it
-sounds. `requestSubmit(submitter)` is how a native submitter carries these,
-and it refuses ours twice over: the inner `<button>` is `type="button"` so
-it is not a submit button, and it sits in this shadow root so its form owner
-is not the consumer's form. Both throw. So the submission is started with no
-submitter and the overrides are applied to the form for the duration of it.
-
-The whole submit algorithm runs synchronously inside `requestSubmit()`, so
-the window is one call and a `finally` closes it whether or not a listener
-refused. What a `submit` handler observes during that window is the form a
-native submitter would have given it, which is the point. */
-  formaction?: (HelixHeadlessCopyButton["formAction"]) | undefined;
-  /** Where this button's submission goes, overriding the form's own.
-
-**The five `form*` overrides work by writing the form and putting it back**,
-which is the only mechanism available and is closer to the platform than it
-sounds. `requestSubmit(submitter)` is how a native submitter carries these,
-and it refuses ours twice over: the inner `<button>` is `type="button"` so
-it is not a submit button, and it sits in this shadow root so its form owner
-is not the consumer's form. Both throw. So the submission is started with no
-submitter and the overrides are applied to the form for the duration of it.
-
-The whole submit algorithm runs synchronously inside `requestSubmit()`, so
-the window is one call and a `finally` closes it whether or not a listener
-refused. What a `submit` handler observes during that window is the form a
-native submitter would have given it, which is the point. */
-  formAction?: (HelixHeadlessCopyButton["formAction"]) | undefined;
-  /** How the submission is encoded, overriding the form's own. */
-  formenctype?: (HelixHeadlessCopyButton["formEnctype"]) | undefined;
-  /** How the submission is encoded, overriding the form's own. */
-  formEnctype?: (HelixHeadlessCopyButton["formEnctype"]) | undefined;
-  /** Which HTTP method the submission uses, overriding the form's own. */
-  formmethod?: (HelixHeadlessCopyButton["formMethod"]) | undefined;
-  /** Which HTTP method the submission uses, overriding the form's own. */
-  formMethod?: (HelixHeadlessCopyButton["formMethod"]) | undefined;
-  /** Whether this submission skips the form's validation. */
-  formnovalidate?: (HelixHeadlessCopyButton["formNoValidate"]) | undefined;
-  /** Whether this submission skips the form's validation. */
-  formNoValidate?: (HelixHeadlessCopyButton["formNoValidate"]) | undefined;
-  /** Which browsing context the response lands in, overriding the form's own. */
-  formtarget?: (HelixHeadlessCopyButton["formTarget"]) | undefined;
-  /** Which browsing context the response lands in, overriding the form's own. */
-  formTarget?: (HelixHeadlessCopyButton["formTarget"]) | undefined;
   /** Whether the action the button started is still running.
 
 A pending button keeps focus and stays in the tab order, and refuses every
@@ -3487,8 +3559,6 @@ a press, so focus stays where the reader left it. */
   "pending-label"?: (HelixHeadlessCopyButton["pendingLabel"]) | undefined;
   /** What a reader hears when the button becomes pending while it has focus. */
   pendingLabel?: (HelixHeadlessCopyButton["pendingLabel"]) | undefined;
-  /** What activating the button does to its form. */
-  type?: (HelixHeadlessCopyButton["type"]) | undefined;
   /** Whether the control is disabled and cannot be used.
 
 Reflected, because the styled tier selects on it, and mirrored to
@@ -3515,31 +3585,6 @@ imperatively later, and nothing is hydrating by then.
 
 Here rather than on each control. */
   name?: (HelixHeadlessCopyButton["name"]) | undefined;
-  /** Whether this button is a disclosure trigger, and whether its panel is open.
-
-**Set by whatever owns the panel, and a property rather than an attribute
-for the reason `Menu` already states about its items**: an attribute
-written onto a consumer's element after it upgrades is a hydration mismatch
-waiting to happen. Measured 28 Aug 2026 against React 19.2.8, server markup
-hydrated with the definitions loaded either side of `hydrateRoot`:
-`Megamenu` and `SpeedDial` wrote `aria-expanded` onto the slotted trigger
-and React reported "some attributes of the server rendered HTML didn't
-match the client properties. This won't be patched up" in both orders;
-`Popover` and `Menu`, which write nothing, were clean in both.
-
-**A property crosses that gap because React never looks at one.** It diffs
-the attributes it rendered, and this one is `attribute: false`, so the state
-travels to the inner `<button>` and lands inside a shadow root React does
-not own and cannot compare. The consumer's own element is left exactly as
-they served it and the reader is still told what the control does.
-
-`undefined` renders nothing at all, so a button that is not a trigger
-carries no `aria-expanded`: the resting state is the attribute's absence,
-which is the rule every reflected property here follows.
-
-A consumer who wants to say this statically writes `aria-expanded` on the
-host instead, which `AriaForwardController` carries to the same place. */
-  expanded?: (HelixHeadlessCopyButton["expanded"]) | undefined;
   /** Whether the button holds its group's tab stop.
 
 A toolbar keeps one tab stop across its children, and the obvious way to do
@@ -3551,14 +3596,6 @@ and the stop lands on the inner control inside the shadow root.
 No attribute, because it is coordination between elements rather than
 anything a consumer sets. */
   focusable?: (HelixHeadlessCopyButton["focusable"]) | undefined;
-  /** What kind of panel this button opens, where it opens one: `menu` for a
-`Menu`.
-
-Set by the component that owns the panel, as a property for the reason
-`expanded` gives above. It is what makes a reader say the button opens a
-menu. Read from Chromium's tree, a Menu's trigger was a plain button that
-reported collapsed and expanded and no popup. */
-  popup?: (HelixHeadlessCopyButton["popup"]) | undefined;
   /** The element this button's command is sent to, resolved.
 
 The platform's own accessor, because the resolution is otherwise kept
@@ -3572,8 +3609,8 @@ invoker without an id in the same tree needs. */
 export type HelixHeadlessCopyButtonVueEvents = {
   /** Fired after the clipboard write succeeds. */
   "helix-copy": HelixHeadlessCopyButtonHelixCopyElementEvent;
-  /** Fired when a press put nothing on the clipboard: the browser refused the write, or there was nothing to copy. */
-  "helix-copy-error": HelixHeadlessCopyButtonElementEvent;
+  /** Fired when a press put nothing on the clipboard: the browser did not allow the write, or there was nothing to copy. */
+  "helix-copy-error": HelixHeadlessCopyButtonHelixCopyErrorElementEvent;
 };
 
 /** `HelixHeadlessDataTable` component event */
@@ -3584,12 +3621,18 @@ export type HelixHeadlessDataTableElementEvent<E = Event> = TypedEvent<
 /** `helix-activate` event type */
 export type HelixHeadlessDataTableHelixActivateElementEvent =
   HelixHeadlessDataTableElementEvent<HelixActivateEvent>;
+/** `helix-expand` event type */
+export type HelixHeadlessDataTableHelixExpandElementEvent =
+  HelixHeadlessDataTableElementEvent<HelixExpandEvent>;
 /** `helix-filter` event type */
 export type HelixHeadlessDataTableHelixFilterElementEvent =
   HelixHeadlessDataTableElementEvent<HelixFilterEvent>;
 /** `helix-filtered` event type */
 export type HelixHeadlessDataTableHelixFilteredElementEvent =
   HelixHeadlessDataTableElementEvent<HelixFilteredEvent>;
+/** `helix-load-more` event type */
+export type HelixHeadlessDataTableHelixLoadMoreElementEvent =
+  HelixHeadlessDataTableElementEvent<HelixLoadMoreEvent>;
 /** `helix-navigate` event type */
 export type HelixHeadlessDataTableHelixNavigateElementEvent =
   HelixHeadlessDataTableElementEvent<HelixNavigateEvent>;
@@ -3617,6 +3660,24 @@ export type HelixHeadlessDataTableVueProps = {
   "ascending-label"?: (HelixHeadlessDataTable["ascendingLabel"]) | undefined;
   /** The word for an ascending sort, in `sorted-label`. */
   ascendingLabel?: (HelixHeadlessDataTable["ascendingLabel"]) | undefined;
+  /** The field that holds a row's child rows, as an array. Set it, and `row-key`,
+and the grid becomes a tree grid.
+
+Reflected, because the styled tier indents a tree grid's row headers by
+it. No default, so a table that sets none writes nothing onto its host. */
+  "child-field"?: (HelixHeadlessDataTable["childField"]) | undefined;
+  /** The field that holds a row's child rows, as an array. Set it, and `row-key`,
+and the grid becomes a tree grid.
+
+Reflected, because the styled tier indents a tree grid's row headers by
+it. No default, so a table that sets none writes nothing onto its host. */
+  childField?: (HelixHeadlessDataTable["childField"]) | undefined;
+  /** The keys of the rows open at the start, separated by commas. Used until
+`expanded` is set. */
+  "default-expanded"?: (HelixHeadlessDataTable["defaultExpanded"]) | undefined;
+  /** The keys of the rows open at the start, separated by commas. Used until
+`expanded` is set. */
+  defaultExpanded?: (HelixHeadlessDataTable["defaultExpanded"]) | undefined;
   /** The starting search query, used until `filter` is set. */
   "default-filter"?: (HelixHeadlessDataTable["defaultFilter"]) | undefined;
   /** The starting search query, used until `filter` is set. */
@@ -3655,6 +3716,9 @@ replaces this with what each row came to as it draws. It still has to be
 close, because it is what the scrollbar is built from before anything has
 been measured. */
   estimate?: (HelixHeadlessDataTable["estimate"]) | undefined;
+  /** The keys of the open rows in a tree grid, separated by commas, the shape of
+`selected`. A reader's press writes it and then sends `helix-expand`. */
+  expanded?: (HelixHeadlessDataTable["expanded"]) | undefined;
   /** The search query. A row is shown when the query matches any of its columns.
 
 One query rather than a predicate per column, which is what a reader means
@@ -3669,6 +3733,22 @@ replaced with the page it jumps to. */
   gapLabel?: (HelixHeadlessDataTable["gapLabel"]) | undefined;
   /** The grid's name, read by screen readers. */
   label?: (HelixHeadlessDataTable["label"]) | undefined;
+  /** Draws a row after the last one with a button that asks for more rows.
+
+The button sends `helix-load-more`, and a `windowed` table sends it by
+itself once a reader scrolls within one screen of the end. Turn it off
+when there are no more rows to load. */
+  "load-more"?: (HelixHeadlessDataTable["loadMore"]) | undefined;
+  /** Draws a row after the last one with a button that asks for more rows.
+
+The button sends `helix-load-more`, and a `windowed` table sends it by
+itself once a reader scrolls within one screen of the end. Turn it off
+when there are no more rows to load. */
+  loadMore?: (HelixHeadlessDataTable["loadMore"]) | undefined;
+  /** The words on the button in the `more` row. */
+  "load-more-label"?: (HelixHeadlessDataTable["loadMoreLabel"]) | undefined;
+  /** The words on the button in the `more` row. */
+  loadMoreLabel?: (HelixHeadlessDataTable["loadMoreLabel"]) | undefined;
   /** Where filtering, sorting, and paging happen. `client` does them in the
 table, and `server` leaves them to your code.
 
@@ -3876,10 +3956,14 @@ holds and reordering it under them is a mutation they did not ask for. */
 export type HelixHeadlessDataTableVueEvents = {
   /** Fired after the page changes, with the new page as a string in `detail.value`. */
   "helix-activate": HelixHeadlessDataTableHelixActivateElementEvent;
+  /** Fired after a row opens or closes, with every open row's key, separated by commas, which `expanded` also holds. */
+  "helix-expand": HelixHeadlessDataTableHelixExpandElementEvent;
   /** The search query is about to change. Cancelable: cancel it to keep the current query. */
   "helix-filter": HelixHeadlessDataTableHelixFilterElementEvent;
   /** Fired after the search query changes, with the new query. */
   "helix-filtered": HelixHeadlessDataTableHelixFilteredElementEvent;
+  /** Fired when a reader asks for more rows, by the `load-more` row's button or by scrolling a `windowed` table near its end. */
+  "helix-load-more": HelixHeadlessDataTableHelixLoadMoreElementEvent;
   /** Another page was requested. Cancelable: cancel it to stay on the current page. */
   "helix-navigate": HelixHeadlessDataTableHelixNavigateElementEvent;
   /** The columns are about to move. The event carries every field in the new order. Cancelable: cancel it to keep the current order. */
@@ -4621,6 +4705,9 @@ labels line up, and lining up is a fact about all of them.
 a reflecting default writes an attribute onto markup the consumer rendered,
 and React reports that as a hydration mismatch. */
   direction?: (HelixHeadlessDescriptionList["direction"]) | undefined;
+  /** The list's name, read by screen readers, such as "Server details". It
+makes the list a named group. */
+  label?: (HelixHeadlessDescriptionList["label"]) | undefined;
 };
 
 export type HelixHeadlessDescriptionListVueEvents = {};
@@ -4980,14 +5067,6 @@ elements, and writing `tabindex` onto a host the consumer rendered is a
 change a React consumer's hydration reports and does not patch up. The stop
 lands inside this shadow root instead. */
   focusable?: (HelixHeadlessDrilldownItem["focusable"]) | undefined;
-  /** Whether the page showing is the one this row is on.
-
-Written by the stack. */
-  onPage?: (HelixHeadlessDrilldownItem["onPage"]) | undefined;
-  /** Whether this row's own page is the one showing.
-
-Written by the stack. */
-  showingPage?: (HelixHeadlessDrilldownItem["showingPage"]) | undefined;
 };
 
 export type HelixHeadlessDrilldownItemVueEvents = {
@@ -6399,6 +6478,9 @@ export type HelixHeadlessInputElementEvent<E = Event> = TypedEvent<
 /** `helix-before-change` event type */
 export type HelixHeadlessInputHelixBeforeChangeElementEvent =
   HelixHeadlessInputElementEvent<HelixBeforeChangeEvent>;
+/** `helix-clear` event type */
+export type HelixHeadlessInputHelixClearElementEvent =
+  HelixHeadlessInputElementEvent<HelixClearEvent>;
 
 export type HelixHeadlessInputVueProps = {
   /** Whether a phone capitalizes as the reader types: `off`, `sentences`,
@@ -6602,7 +6684,7 @@ export type HelixHeadlessInputVueEvents = {
   /** The text is about to change. Cancelable: cancel it to keep the current text. */
   "helix-before-change": HelixHeadlessInputHelixBeforeChangeElementEvent;
   /** Fired after the clear button has emptied the field, after `input` and `change`. */
-  "helix-clear": HelixHeadlessInputElementEvent;
+  "helix-clear": HelixHeadlessInputHelixClearElementEvent;
   /** Fired as the value changes. */
   input: HelixHeadlessInputElementEvent;
 };
@@ -6996,7 +7078,27 @@ writes them, whatever this says. */
 
 export type HelixHeadlessLineChartVueEvents = {};
 
+/** `HelixHeadlessListItem` component event */
+export type HelixHeadlessListItemElementEvent<E = Event> = TypedEvent<
+  HelixHeadlessListItem,
+  E
+>;
+/** `helix-action` event type */
+export type HelixHeadlessListItemHelixActionElementEvent =
+  HelixHeadlessListItemElementEvent<HelixActionEvent>;
+
 export type HelixHeadlessListItemVueProps = {
+  /** Marks the row a reader is on: `page` for the page they are reading, `step`,
+`location`, `date` or `time` for those, and written bare for the current
+one of a set. It is `aria-current` on the row's link, or on the row where
+it has none.
+
+Not reflected, as a state never is. `row-current` is the part a
+stylesheet draws it from. */
+  current?: (HelixHeadlessListItem["current"]) | undefined;
+  /** Takes the row out of reach in a list with `selection-mode`: the arrow keys
+pass over it and it cannot be selected or acted on. */
+  disabled?: (HelixHeadlessListItem["disabled"]) | undefined;
   /** The URL the row links to. Leave it empty for a row that is not a link.
 
 Empty rather than optional, and unset by default: a list is not always a
@@ -7008,9 +7110,39 @@ to the current page on every row a consumer never asked to be one. */
   rel?: (HelixHeadlessListItem["rel"]) | undefined;
   /** Where the link opens. Use it for a row that leaves the site. */
   target?: (HelixHeadlessListItem["target"]) | undefined;
+  /** What the row stands for in its list's `value`.
+
+Absent is the row's own words. */
+  value?: (HelixHeadlessListItem["value"]) | undefined;
+  /** Whether the row holds its list's tab stop.
+
+Written by a list with `selection-mode` on every row it holds, and unset
+otherwise, which is how a row knows it is a row of a grid. No attribute:
+it is coordination between elements, as `Tag.focusable` is. */
+  focusable?: (HelixHeadlessListItem["focusable"]) | undefined;
+  /** Whether the row is selected, in a list that selects.
+
+Written by the list from its own `value`, and unset where nothing can be
+selected, which keeps `aria-selected` off a list that does not select. */
+  selected?: (HelixHeadlessListItem["selected"]) | undefined;
 };
 
-export type HelixHeadlessListItemVueEvents = {};
+export type HelixHeadlessListItemVueEvents = {
+  /** The reader pressed Enter on the row, or pressed the row in a list that selects nothing, in a list with `selection-mode`. Read the row from `target`. A row with `href` follows its link instead. */
+  "helix-action": HelixHeadlessListItemHelixActionElementEvent;
+};
+
+/** `HelixHeadlessList` component event */
+export type HelixHeadlessListElementEvent<E = Event> = TypedEvent<
+  HelixHeadlessList,
+  E
+>;
+/** `helix-action` event type */
+export type HelixHeadlessListHelixActionElementEvent =
+  HelixHeadlessListElementEvent<HelixActionEvent>;
+/** `helix-before-change` event type */
+export type HelixHeadlessListHelixBeforeChangeElementEvent =
+  HelixHeadlessListElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixHeadlessListVueProps = {
   /** The kind of list, which follows from the content.
@@ -7036,6 +7168,20 @@ has to survive with the stylesheet turned off.
   kind?: (HelixHeadlessList["kind"]) | undefined;
   /** The list's name, read by screen readers. */
   label?: (HelixHeadlessList["label"]) | undefined;
+  /** Numbers an ordered list downward, so the count falls row by row and ends at
+its last row, as `<ol reversed>` does. */
+  reversed?: (HelixHeadlessList["reversed"]) | undefined;
+  /** Makes the list interactive: `single` selects one row, `multiple` any
+number, and `none` moves and acts without selecting. Unset is a list a
+reader reads, with no tab stop of its own. */
+  "selection-mode"?: (HelixHeadlessList["selectionMode"]) | undefined;
+  /** Makes the list interactive: `single` selects one row, `multiple` any
+number, and `none` moves and acts without selecting. Unset is a list a
+reader reads, with no tab stop of its own. */
+  selectionMode?: (HelixHeadlessList["selectionMode"]) | undefined;
+  /** The number of an ordered list's first row, as `<ol start>` is. Unset counts
+from one, or down from the number of rows where `reversed`. */
+  start?: (HelixHeadlessList["start"]) | undefined;
   /** The markers an ordered list draws. It takes the five values of `<ol type>`.
 
 Reflected, because this is one of the things a stylesheet selects on, each
@@ -7043,18 +7189,24 @@ value mapping to a `list-style-type`. The platform's spellings rather than
 the CSS ones, so `<helix-headless-list kind="ordered" type="i">` is what a
 consumer would have written on an `<ol>`.
 
-**`start` and `reversed` are both absent and neither can be done here.**
-This renders no `<ol>`: the rows are slotted and numbered by the CSS
-`list-item` counter, and that counter is not author-resettable. Measured in
-Chrome 148, `counter-reset: list-item 4` moves nothing on a `<div>`, on a
-`<ul>`, or even on a real `<ol>`, while `<ol start="5">` does and a *named*
-counter with explicit `::before` content does. So the markers would have to
-be rebuilt out of generated content to gain a start, which is a different
-component. `type` is only `list-style-type` and works. */
+`type` is only `list-style-type`. `start` and `reversed` move the count
+itself. */
   type?: (HelixHeadlessList["type"]) | undefined;
+  /** The selected rows' values, separated by commas, in a list that selects.
+
+Set it to start with rows selected. A row's value is its `value`, or its
+words where it has none. */
+  value?: (HelixHeadlessList["value"]) | undefined;
 };
 
-export type HelixHeadlessListVueEvents = {};
+export type HelixHeadlessListVueEvents = {
+  /** Fired once a press has changed which rows are selected. */
+  change: HelixHeadlessListElementEvent;
+  /** Sent from a row when the reader acts on it: Enter, or a press in a list that selects nothing. Read the row from `target`. A row with `href` follows its link instead. */
+  "helix-action": HelixHeadlessListHelixActionElementEvent;
+  /** Fired before a press changes which rows are selected, with the `value` it would leave. Cancelable. */
+  "helix-before-change": HelixHeadlessListHelixBeforeChangeElementEvent;
+};
 
 /** `HelixHeadlessListbox` component event */
 export type HelixHeadlessListboxElementEvent<E = Event> = TypedEvent<
@@ -7618,6 +7770,9 @@ export type HelixHeadlessMapHelixMapTiltElementEvent =
 /** `helix-map-zoom` event type */
 export type HelixHeadlessMapHelixMapZoomElementEvent =
   HelixHeadlessMapElementEvent<HelixMapZoomEvent>;
+/** `helix-toggle` event type */
+export type HelixHeadlessMapHelixToggleElementEvent =
+  HelixHeadlessMapElementEvent<HelixToggleEvent>;
 
 export type HelixHeadlessMapVueProps = {
   /** The map's rotation, in degrees clockwise from north. `connectMap` keeps it
@@ -7922,6 +8077,8 @@ export type HelixHeadlessMapVueEvents = {
   "helix-map-tilt": HelixHeadlessMapHelixMapTiltElementEvent;
   /** A zoom button or key was pressed, with a direction. Zoom your map in response. */
   "helix-map-zoom": HelixHeadlessMapHelixMapZoomElementEvent;
+  /** A layer's tile in the layers menu showed or hid it. Sent from the layer once its `hidden` attribute holds the choice, with `checked` true when it is shown. */
+  "helix-toggle": HelixHeadlessMapHelixToggleElementEvent;
 };
 
 /** `HelixHeadlessMapRoute` component event */
@@ -8191,37 +8348,24 @@ So the anchor *is* the row, carrying `menuitem` and the `tabindex` the menu
 roves, which is the same maneuver `Tree.Item` makes and the reason `href`
 changes the markup rather than only adding an attribute.
 
-**`Option` cannot have this and the reason is worth knowing**, since a
-command palette is the obvious place to want it. A listbox has to keep
-focus somewhere else, in the text field for a combobox, so it says which
-option is current with `aria-activedescendant`. That reference can only
-point at the option's host, measured: assigning
-`ariaActiveDescendantElement` an element inside a sibling shadow root reads
-back `null`. So `role="option"` is pinned to the host, and an anchor under
-it hits the naming failure above. A menu has no such constraint because
-focus really moves to the row. */
+**`Option` takes an `href` too, and keeps its role a different way.** A
+listbox keeps focus somewhere else, in the text field for a combobox, and
+names the current option with `aria-activedescendant`, which can only point
+at the option's host. So an option stays `role="option"` on its host, draws
+no anchor, and follows its link through an anchor made for the moment. A
+menu has no such constraint, because focus really moves to the row. */
   href?: (HelixHeadlessMenuItem["href"]) | undefined;
   /** The link's `rel`. Set it whenever you set `target="_blank"`. */
   rel?: (HelixHeadlessMenuItem["rel"]) | undefined;
+  /** The row's keyboard shortcut as a chord, such as `mod+s`, shown after the
+label in the platform's glyphs and given to the row as
+`aria-keyshortcuts`. `mod` is Command on an Apple keyboard and Control
+elsewhere. Showing a shortcut does not bind it. */
+  shortcut?: (HelixHeadlessMenuItem["shortcut"]) | undefined;
   /** Where the link opens, for rows that should open outside the current page. */
   target?: (HelixHeadlessMenuItem["target"]) | undefined;
   /** The row's value, sent in `helix-select` when the row is chosen. */
   value?: (HelixHeadlessMenuItem["value"]) | undefined;
-  /** Whether the row is on the menu page that is showing.
-
-Set by the menu, and a property rather than an attribute for that reason.
-Public because the menu has to reach it, and not something a consumer
-writes: which page is open is the menu's business. */
-  onPage?: (HelixHeadlessMenuItem["onPage"]) | undefined;
-  /** Whether the page showing is this row's submenu, or one below it.
-
-Separate from `onPage`, and it has to be. A row that opened a page is not
-itself on that page, so both are false for it, and rendering nothing on
-that basis takes its `slot[name="submenu"]` with it: the rows inside have
-nowhere to be assigned and are never laid out. Every row on the way down to
-the open page has to keep its slot, not only the one directly above it.
-Three levels deep, the topmost row holds the slot the middle one lives in. */
-  showingSubmenu?: (HelixHeadlessMenuItem["showingSubmenu"]) | undefined;
 };
 
 export type HelixHeadlessMenuItemVueEvents = {
@@ -8254,6 +8398,9 @@ export type HelixHeadlessMenuVueProps = {
   "back-label"?: (HelixHeadlessMenu["backLabel"]) | undefined;
   /** The text of the row that returns from a submenu. */
   backLabel?: (HelixHeadlessMenu["backLabel"]) | undefined;
+  /** Whether the menu is the trigger's context menu: it opens where the reader
+asks for one, with a right-click, a long press, Shift+F10 or the menu key. */
+  context?: (HelixHeadlessMenu["context"]) | undefined;
   /** Accessible name for the surface.
 
 Empty by default, which names the surface by its trigger, so a menu opened
@@ -8310,6 +8457,14 @@ export type HelixHeadlessMenuVueEvents = {
   toggle: HelixHeadlessMenuToggleElementEvent;
 };
 
+export type HelixHeadlessMenuSectionVueProps = {
+  /** The heading's words, when they are plain text. Content in the `heading`
+slot replaces it. */
+  label?: (HelixHeadlessMenuSection["label"]) | undefined;
+};
+
+export type HelixHeadlessMenuSectionVueEvents = {};
+
 export type HelixHeadlessMeterVueProps = {
   /** Sets the band directly, for a rule that `low`, `high`, and `optimum` cannot
 express.
@@ -8416,6 +8571,11 @@ fair summary of a task and a poor one of a quantity. */
 export type HelixHeadlessMeterVueEvents = {};
 
 export type HelixHeadlessNavigationVueProps = {
+  /** Whether the arrow keys move focus between the destinations.
+
+Off by default, so a page whose readers scroll with the arrow keys while
+a link has focus keeps doing so. */
+  arrows?: (HelixHeadlessNavigation["arrows"]) | undefined;
   /** The landmark's name, read by screen readers.
 
 An `aria-label` or `aria-labelledby` on the host names the landmark too,
@@ -8577,6 +8737,9 @@ export type HelixHeadlessNotificationsElementEvent<E = Event> = TypedEvent<
 /** `helix-dismiss` event type */
 export type HelixHeadlessNotificationsHelixDismissElementEvent =
   HelixHeadlessNotificationsElementEvent<HelixDismissEvent>;
+/** `helix-load-more` event type */
+export type HelixHeadlessNotificationsHelixLoadMoreElementEvent =
+  HelixHeadlessNotificationsElementEvent<HelixLoadMoreEvent>;
 /** `helix-read` event type */
 export type HelixHeadlessNotificationsHelixReadElementEvent =
   HelixHeadlessNotificationsElementEvent<HelixReadEvent>;
@@ -8584,6 +8747,16 @@ export type HelixHeadlessNotificationsHelixReadElementEvent =
 export type HelixHeadlessNotificationsVueProps = {
   /** The feed's name, read by screen readers. */
   label?: (HelixHeadlessNotifications["label"]) | undefined;
+  /** Whether to draw a button after the list that asks for the next page, by
+sending `helix-load-more`. Take it off once there is nothing more. */
+  "load-more"?: (HelixHeadlessNotifications["loadMore"]) | undefined;
+  /** Whether to draw a button after the list that asks for the next page, by
+sending `helix-load-more`. Take it off once there is nothing more. */
+  loadMore?: (HelixHeadlessNotifications["loadMore"]) | undefined;
+  /** The text of the `load-more` button. */
+  "load-more-label"?: (HelixHeadlessNotifications["loadMoreLabel"]) | undefined;
+  /** The text of the `load-more` button. */
+  loadMoreLabel?: (HelixHeadlessNotifications["loadMoreLabel"]) | undefined;
   /** Whether to draw a control that marks everything read. */
   "mark-all"?: (HelixHeadlessNotifications["markAll"]) | undefined;
   /** Whether to draw a control that marks everything read. */
@@ -8617,6 +8790,8 @@ say that without the component knowing what a row looks like. */
 export type HelixHeadlessNotificationsVueEvents = {
   /** Fired when the user dismisses a row. The row dispatches it, and you can listen for it on the feed. Cancelable: cancel it to keep the row. */
   "helix-dismiss": HelixHeadlessNotificationsHelixDismissElementEvent;
+  /** Fired when a reader presses the `load-more` button, asking for the next page of the feed. */
+  "helix-load-more": HelixHeadlessNotificationsHelixLoadMoreElementEvent;
   /** Fired by an item when it is marked read or unread, and by the feed when everything is marked read. Cancelable. */
   "helix-read": HelixHeadlessNotificationsHelixReadElementEvent;
 };
@@ -8856,11 +9031,31 @@ export type HelixHeadlessObjectInspectorElementEvent<E = Event> = TypedEvent<
   HelixHeadlessObjectInspector,
   E
 >;
+/** `helix-activate` event type */
+export type HelixHeadlessObjectInspectorHelixActivateElementEvent =
+  HelixHeadlessObjectInspectorElementEvent<HelixActivateEvent>;
+/** `helix-before-activate` event type */
+export type HelixHeadlessObjectInspectorHelixBeforeActivateElementEvent =
+  HelixHeadlessObjectInspectorElementEvent<HelixBeforeActivateEvent>;
 /** `helix-copy` event type */
 export type HelixHeadlessObjectInspectorHelixCopyElementEvent =
   HelixHeadlessObjectInspectorElementEvent<HelixCopyEvent>;
+/** `helix-filter` event type */
+export type HelixHeadlessObjectInspectorHelixFilterElementEvent =
+  HelixHeadlessObjectInspectorElementEvent<HelixFilterEvent>;
+/** `helix-filtered` event type */
+export type HelixHeadlessObjectInspectorHelixFilteredElementEvent =
+  HelixHeadlessObjectInspectorElementEvent<HelixFilteredEvent>;
 
 export type HelixHeadlessObjectInspectorVueProps = {
+  /** The active row's path, such as `/meta/tags/0`, and the empty string for the
+root.
+
+Reading gives the row the keys are on. Writing moves there, opening the
+branches around it, and sends no event, the way a script's write to any
+current value sends none. A path the value does not hold moves to the
+nearest branch above it that it does. */
+  active?: (HelixHeadlessObjectInspector["active"]) | undefined;
   /** The copy button's accessible name on a row with a key, with the key filled
 in as `{name}`.
 
@@ -8891,6 +9086,15 @@ reader sees the shape of the value before its contents. `0` starts with the
 root closed; a large number opens everything, which on a big value is the
 wall of text this exists to avoid. */
   defaultDepth?: (HelixHeadlessObjectInspector["defaultDepth"]) | undefined;
+  /** Text the tree is narrowed to: the entries whose key or value holds it,
+ignoring case, and the branches that lead to them. Empty shows everything. */
+  filter?: (HelixHeadlessObjectInspector["filter"]) | undefined;
+  /** Whether to show a field that sets `filter`. */
+  filterable?: (HelixHeadlessObjectInspector["filterable"]) | undefined;
+  /** The filter field's placeholder and accessible name. */
+  "filter-label"?: (HelixHeadlessObjectInspector["filterLabel"]) | undefined;
+  /** The filter field's placeholder and accessible name. */
+  filterLabel?: (HelixHeadlessObjectInspector["filterLabel"]) | undefined;
   /** The id of a `<script type="application/json">` holding the value.
 
 Read once the document exists, and again whenever this changes. Text that
@@ -8939,6 +9143,16 @@ who set the property. This button is positioned out of the flow and takes no
 room, so nothing selects on it, and reflection exists so that a selector can
 reach a value. */
   noCopy?: (HelixHeadlessObjectInspector["noCopy"]) | undefined;
+  /** What a screen reader hears when a filter matches one entry. `{count}` is the count. */
+  "result-label"?: (HelixHeadlessObjectInspector["resultLabel"]) | undefined;
+  /** What a screen reader hears when a filter matches one entry. `{count}` is the count. */
+  resultLabel?: (HelixHeadlessObjectInspector["resultLabel"]) | undefined;
+  /** What a screen reader hears when a filter matches any other number of
+entries. `{count}` is the count. The two are chosen by `Intl.PluralRules`. */
+  "results-label"?: (HelixHeadlessObjectInspector["resultsLabel"]) | undefined;
+  /** What a screen reader hears when a filter matches any other number of
+entries. `{count}` is the count. The two are chosen by `Intl.PluralRules`. */
+  resultsLabel?: (HelixHeadlessObjectInspector["resultsLabel"]) | undefined;
   /** The tree's accessible name when `label` is empty and the host names it
 with neither `aria-label` nor `aria-labelledby`. */
   "tree-label"?: (HelixHeadlessObjectInspector["treeLabel"]) | undefined;
@@ -8950,6 +9164,11 @@ with neither `aria-label` nor `aria-labelledby`. */
 For a value of thousands of entries. Reflected, because the box it scrolls
 needs a height, which is a stylesheet rule reading this attribute. */
   windowed?: (HelixHeadlessObjectInspector["windowed"]) | undefined;
+  /** The open branches, by path, in no set order.
+
+Writing opens exactly these and closes every other, keeping the active row
+where it stays visible. A property, never an attribute. */
+  expanded?: (HelixHeadlessObjectInspector["expanded"]) | undefined;
   /** The value to show, when your code already holds it as an object.
 
 Takes precedence over `for`. Anything JSON can say is drawn; anything else
@@ -8958,8 +9177,16 @@ is shown as its string. */
 };
 
 export type HelixHeadlessObjectInspectorVueEvents = {
+  /** The active row moved, by a key or a click. The detail's `value` is its path. */
+  "helix-activate": HelixHeadlessObjectInspectorHelixActivateElementEvent;
+  /** The active row is about to move, with its new path. Cancelable: cancel it to keep the row where it is. */
+  "helix-before-activate": HelixHeadlessObjectInspectorHelixBeforeActivateElementEvent;
   /** A value was put on the clipboard, from the copy button or the keyboard. */
   "helix-copy": HelixHeadlessObjectInspectorHelixCopyElementEvent;
+  /** Text was typed in the filter field, with what it now holds. Cancelable: cancel it to keep the filter as it was. */
+  "helix-filter": HelixHeadlessObjectInspectorHelixFilterElementEvent;
+  /** The filter field changed `filter`, which now holds the text. */
+  "helix-filtered": HelixHeadlessObjectInspectorHelixFilteredElementEvent;
 };
 
 export type HelixHeadlessOptionGroupVueProps = {
@@ -9163,7 +9390,8 @@ read at the click rather than cached, because a reader can change it while
 the page is open and this is the only motion in the component that
 JavaScript rather than CSS decides. */
   behavior?: (HelixHeadlessOutline["behavior"]) | undefined;
-  /** The navigation's name, read by screen readers. */
+  /** The navigation's name, read by screen readers. A heading in the `heading`
+slot names it in place of this. */
   label?: (HelixHeadlessOutline["label"]) | undefined;
   /** How far below the top of the scroll container a heading counts as reached,
 in pixels. The scroll container is the window or the panel the sections
@@ -9373,6 +9601,32 @@ Reading gives the real one; writing declares it the consumer's, and
 `default-value` seeds one this element owns. Same accessor pair as
 `Pagination.page` and the calendar's `month`. */
   value?: (HelixHeadlessPaginationSize["value"]) | undefined;
+  /** Whether the control is disabled and cannot be used.
+
+Reflected, because the styled tier selects on it, and mirrored to
+`aria-disabled` rather than removing the element from the accessibility
+tree, so a screen reader can still announce that the control exists.
+
+The mirror itself is in `willUpdate` below, here rather than in each
+control, because here is where `disabled` is. */
+  disabled?: (HelixHeadlessPaginationSize["disabled"]) | undefined;
+  /** The name the control's value is submitted under.
+
+**Reflected, and it is the exception to "reflect only what CSS selects
+on".** The platform builds a form's entry list from the `name` *content
+attribute*, not from the property, so a control named through the property
+submitted under no name at all and was silently dropped. Measured: two
+inputs in one form, one named by attribute and one by property, and the
+form carried a single entry.
+
+Safe for a React consumer, which is what the rule is protecting: React
+renders a custom element's props as attributes on the server, so the name
+is already in the markup being hydrated and reflecting it writes what is
+there. It is only a change to the markup when a consumer assigns it
+imperatively later, and nothing is hydrating by then.
+
+Here rather than on each control. */
+  name?: (HelixHeadlessPaginationSize["name"]) | undefined;
 };
 
 export type HelixHeadlessPaginationSizeVueEvents = {
@@ -9799,18 +10053,18 @@ only `horizontal` has to be named. */
   /** Whether a reader can see and focus the answer and cannot change it. A
 read-only group still submits its value.
 
-React Aria's `isReadOnly`. A press on a radio is refused, and the arrow
-keys, Home and End leave focus on the answer, so Tab still reaches it and
-a reader hears it with the group's name. The group says `aria-readonly`.
-A script can still set `value`. */
+React Aria's `isReadOnly`. A press on a radio is refused. The arrow keys,
+Home and End move focus between the radios and choose nothing, so a reader
+can hear every choice, and Tab still reaches the answer. The group says
+`aria-readonly`. A script can still set `value`. */
   readonly?: (HelixHeadlessRadioGroup["readOnly"]) | undefined;
   /** Whether a reader can see and focus the answer and cannot change it. A
 read-only group still submits its value.
 
-React Aria's `isReadOnly`. A press on a radio is refused, and the arrow
-keys, Home and End leave focus on the answer, so Tab still reaches it and
-a reader hears it with the group's name. The group says `aria-readonly`.
-A script can still set `value`. */
+React Aria's `isReadOnly`. A press on a radio is refused. The arrow keys,
+Home and End move focus between the radios and choose nothing, so a reader
+can hear every choice, and Tab still reaches the answer. The group says
+`aria-readonly`. A script can still set `value`. */
   readOnly?: (HelixHeadlessRadioGroup["readOnly"]) | undefined;
   /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixHeadlessRadioGroup["defaultValue"]) | undefined;
@@ -9982,6 +10236,9 @@ export type HelixHeadlessRatingElementEvent<E = Event> = TypedEvent<
 /** `helix-before-change` event type */
 export type HelixHeadlessRatingHelixBeforeChangeElementEvent =
   HelixHeadlessRatingElementEvent<HelixBeforeChangeEvent>;
+/** `helix-clear` event type */
+export type HelixHeadlessRatingHelixClearElementEvent =
+  HelixHeadlessRatingElementEvent<HelixClearEvent>;
 
 export type HelixHeadlessRatingVueProps = {
   /** Whether a reader can take the rating back to unrated: by pressing the
@@ -10175,7 +10432,7 @@ export type HelixHeadlessRatingVueEvents = {
   /** The score is about to change. Cancelable: cancel it to keep the current score. */
   "helix-before-change": HelixHeadlessRatingHelixBeforeChangeElementEvent;
   /** The rating went back to unrated, under `clearable`. Sent after `input` and `change`. */
-  "helix-clear": HelixHeadlessRatingElementEvent;
+  "helix-clear": HelixHeadlessRatingHelixClearElementEvent;
   /** The score changed. */
   input: HelixHeadlessRatingElementEvent;
 };
@@ -10220,14 +10477,44 @@ writes them, whatever this says. */
 
 export type HelixHeadlessScatterChartVueEvents = {};
 
+/** `HelixHeadlessScrollArea` component event */
+export type HelixHeadlessScrollAreaElementEvent<E = Event> = TypedEvent<
+  HelixHeadlessScrollArea,
+  E
+>;
+
 export type HelixHeadlessScrollAreaVueProps = {
+  /** How long the scrollbars stay after the content stops moving, or the pointer
+leaves, in milliseconds. Read under `scrollbars="scroll"` and
+`scrollbars="hover"`. */
+  "hide-delay"?: (HelixHeadlessScrollArea["hideDelay"] | `${number}`) | undefined;
+  /** How long the scrollbars stay after the content stops moving, or the pointer
+leaves, in milliseconds. Read under `scrollbars="scroll"` and
+`scrollbars="hover"`. */
+  hideDelay?: (HelixHeadlessScrollArea["hideDelay"]) | undefined;
   /** The region's name, read by screen readers.
 
 Without one there is no region: see the note on the class. */
   label?: (HelixHeadlessScrollArea["label"]) | undefined;
+  /** Draws scrollbars of the component's own in place of the browser's, and
+says when they show.
+
+- `auto`: on each axis that has content past it.
+- `always`: on each axis that can scroll, whether or not it has anything to
+  scroll, so the scrollbar is there before the content grows.
+- `scroll`: while the content is moving, and for `hide-delay` after.
+- `hover`: as `scroll`, and while the pointer is over the scroll area.
+
+Absent keeps the browser's scrollbars. */
+  scrollbars?: (HelixHeadlessScrollArea["scrollbars"]) | undefined;
 };
 
-export type HelixHeadlessScrollAreaVueEvents = {};
+export type HelixHeadlessScrollAreaVueEvents = {
+  /** The content scrolled. Sent from the host, because the viewport's own does not leave the shadow root. Does not bubble. */
+  scroll: HelixHeadlessScrollAreaElementEvent;
+  /** The content stopped scrolling. Sent from the host, as `scroll` is. Does not bubble. */
+  scrollend: HelixHeadlessScrollAreaElementEvent;
+};
 
 /** `HelixHeadlessSelect` component event */
 export type HelixHeadlessSelectElementEvent<E = Event> = TypedEvent<
@@ -10904,6 +11191,15 @@ Reading gives where it is; writing declares it the consumer's, and
 `default-position` seeds one this element owns. The same accessor pair
 `Pagination.page` and the calendar's `month` carry. */
   position?: (HelixHeadlessSplitter["position"]) | undefined;
+  /** Where a dragged divider snaps, comma separated, as Web Awesome's split
+panel does: a bare number is a percentage and a length such as `240px` is
+measured along the splitter, so `snap="25, 50, 75"` or `snap="240px, 50"`.
+The arrow keys move by `step` and do not snap. */
+  snap?: (HelixHeadlessSplitter["snap"]) | undefined;
+  /** How close a drag has to come to a snap point to land on it, in pixels. */
+  "snap-threshold"?: (HelixHeadlessSplitter["snapThreshold"] | `${number}`) | undefined;
+  /** How close a drag has to come to a snap point to land on it, in pixels. */
+  snapThreshold?: (HelixHeadlessSplitter["snapThreshold"]) | undefined;
   /** How far one arrow key press moves the divider, as a percentage. */
   step?: (HelixHeadlessSplitter["step"]) | undefined;
 };
@@ -10979,6 +11275,9 @@ export type HelixHeadlessStepsVueProps = {
 A list of stages is a landmark a reader arrives at out of order, so it
 needs a name of its own rather than borrowing the heading above it. */
   label?: (HelixHeadlessSteps["label"]) | undefined;
+  /** Whether a reader has to finish each stage, or pass an `optional` one,
+before going on to the next. */
+  linear?: (HelixHeadlessSteps["linear"]) | undefined;
   /** Which way the steps run.
 
 Absent is a row, which is what a form header wants, with each name under
@@ -11042,10 +11341,19 @@ export type HelixHeadlessStepHelixSelectElementEvent =
 export type HelixHeadlessStepVueProps = {
   /** Whether this stage is finished. */
   complete?: (HelixHeadlessStep["complete"]) | undefined;
+  /** The words that tell a screen reader the stage is finished. Translate it
+with the page. */
+  "complete-label"?: (HelixHeadlessStep["completeLabel"]) | undefined;
+  /** The words that tell a screen reader the stage is finished. Translate it
+with the page. */
+  completeLabel?: (HelixHeadlessStep["completeLabel"]) | undefined;
   /** Whether this is the current stage. */
   current?: (HelixHeadlessStep["current"]) | undefined;
   /** Whether the stage is disabled, so the user cannot go to it. */
   disabled?: (HelixHeadlessStep["disabled"]) | undefined;
+  /** 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`. */
   value?: (HelixHeadlessStep["value"]) | undefined;
 };
@@ -11185,6 +11493,9 @@ export type HelixHeadlessTableColumnElementEvent<E = Event> = TypedEvent<
 /** `helix-before-resize` event type */
 export type HelixHeadlessTableColumnHelixBeforeResizeElementEvent =
   HelixHeadlessTableColumnElementEvent<HelixBeforeResizeEvent>;
+/** `helix-resized` event type */
+export type HelixHeadlessTableColumnHelixResizedElementEvent =
+  HelixHeadlessTableColumnElementEvent<HelixResizedEvent>;
 
 export type HelixHeadlessTableColumnVueProps = {
   /** The key this column reads out of a row.
@@ -11226,6 +11537,22 @@ replaced with the heading text. */
   /** The accessible name of the separator that resizes the column. `{name}` is
 replaced with the heading text. */
   resizeLabel?: (HelixHeadlessTableColumn["resizeLabel"]) | undefined;
+  /** Makes this column's cells the headers of their rows, in `DataTable`.
+
+A screen reader moving along a row or down a column names the row by its
+row header, so the cell that identifies a row, a file's name say, is the
+one to mark. Where no column sets it, `DataTable` makes the first column
+with a `field` the row header. A `Table`'s cells are your markup, so there
+a cell is a row header through its own `header` attribute. */
+  "row-header"?: (HelixHeadlessTableColumn["rowHeader"]) | undefined;
+  /** Makes this column's cells the headers of their rows, in `DataTable`.
+
+A screen reader moving along a row or down a column names the row by its
+row header, so the cell that identifies a row, a file's name say, is the
+one to mark. Where no column sets it, `DataTable` makes the first column
+with a `field` the row header. A `Table`'s cells are your markup, so there
+a cell is a row header through its own `header` attribute. */
+  rowHeader?: (HelixHeadlessTableColumn["rowHeader"]) | undefined;
   /** Whether the table can be sorted by this column.
 
 Ignored without a `field`, and silently: a column with nothing to sort by
@@ -11353,6 +11680,8 @@ correct default: the raw value is what an API sorted by. */
 export type HelixHeadlessTableColumnVueEvents = {
   /** The column is about to be resized, with the requested width. Cancelable: cancel it to keep the current width. */
   "helix-before-resize": HelixHeadlessTableColumnHelixBeforeResizeElementEvent;
+  /** Fired after the column is resized, with the new width. */
+  "helix-resized": HelixHeadlessTableColumnHelixResizedElementEvent;
 };
 
 /** `HelixHeadlessTable` component event */
@@ -11360,9 +11689,18 @@ export type HelixHeadlessTableElementEvent<E = Event> = TypedEvent<
   HelixHeadlessTable,
   E
 >;
+/** `helix-select` event type */
+export type HelixHeadlessTableHelixSelectElementEvent =
+  HelixHeadlessTableElementEvent<HelixSelectEvent>;
+/** `helix-selected` event type */
+export type HelixHeadlessTableHelixSelectedElementEvent =
+  HelixHeadlessTableElementEvent<HelixSelectedEvent>;
 /** `helix-sort` event type */
 export type HelixHeadlessTableHelixSortElementEvent =
   HelixHeadlessTableElementEvent<HelixSortEvent>;
+/** `helix-sorted` event type */
+export type HelixHeadlessTableHelixSortedElementEvent =
+  HelixHeadlessTableElementEvent<HelixSortedEvent>;
 
 export type HelixHeadlessTableVueProps = {
   /** The word for an ascending sort, in `sorted-label`. */
@@ -11398,6 +11736,12 @@ and a list here would be a second way to say what that says. This table's
 cells are markup, and a table written as rows of cells with no column
 declared in it has nowhere else to be sized from. */
   columns?: (HelixHeadlessTable["columns"]) | undefined;
+  /** The keys selected at the start, separated by commas. Used until `selected`
+is set. */
+  "default-selected"?: (HelixHeadlessTable["defaultSelected"]) | undefined;
+  /** The keys selected at the start, separated by commas. Used until `selected`
+is set. */
+  defaultSelected?: (HelixHeadlessTable["defaultSelected"]) | undefined;
   /** The starting sort order, used until `sort` is set. */
   "default-sort"?: (HelixHeadlessTable["defaultSort"]) | undefined;
   /** The starting sort order, used until `sort` is set. */
@@ -11411,6 +11755,31 @@ declared in it has nowhere else to be sized from. */
 An `aria-label` or `aria-labelledby` on the host names the table too, and
 wins over this. */
   label?: (HelixHeadlessTable["label"]) | undefined;
+  /** Adds a column of checkboxes for selecting rows. Each row is known by its
+`value`, and by its place among the rows as written where it has none. */
+  selectable?: (HelixHeadlessTable["selectable"]) | undefined;
+  /** The name of the checkbox in the heading that selects every row. */
+  "select-all-label"?: (HelixHeadlessTable["selectAllLabel"]) | undefined;
+  /** The name of the checkbox in the heading that selects every row. */
+  selectAllLabel?: (HelixHeadlessTable["selectAllLabel"]) | undefined;
+  /** The keys of the selected rows, separated by commas.
+
+A reader's press fires `helix-select` first, and refusing it leaves the
+selection as it was. `default-selected` seeds a selection this element
+then owns. */
+  selected?: (HelixHeadlessTable["selected"]) | undefined;
+  /** What screen readers hear when the chosen rows change. `{count}` is how many
+rows are chosen. */
+  "selected-label"?: (HelixHeadlessTable["selectedLabel"]) | undefined;
+  /** What screen readers hear when the chosen rows change. `{count}` is how many
+rows are chosen. */
+  selectedLabel?: (HelixHeadlessTable["selectedLabel"]) | undefined;
+  /** The name of a row's checkbox. `{row}` is replaced with the words of the
+row's first cell. */
+  "select-row-label"?: (HelixHeadlessTable["selectRowLabel"]) | undefined;
+  /** The name of a row's checkbox. `{row}` is replaced with the words of the
+row's first cell. */
+  selectRowLabel?: (HelixHeadlessTable["selectRowLabel"]) | undefined;
   /** The sort order, as `field:direction`, where `field` is a sortable column's
 `field`.
 
@@ -11446,11 +11815,21 @@ say that without the component knowing what a row looks like. */
 };
 
 export type HelixHeadlessTableVueEvents = {
+  /** The selection is about to change. The event carries every selected key, separated by commas. Cancelable: cancel it to keep the current selection. */
+  "helix-select": HelixHeadlessTableHelixSelectElementEvent;
+  /** Fired after the selection changes, with every selected key, separated by commas. */
+  "helix-selected": HelixHeadlessTableHelixSelectedElementEvent;
   /** A different sort order was requested, as `field:direction`, or empty for the order the rows were written in. Cancelable: cancel it to keep the current order. */
   "helix-sort": HelixHeadlessTableHelixSortElementEvent;
+  /** Fired after the sort order changes, with the new order. */
+  "helix-sorted": HelixHeadlessTableHelixSortedElementEvent;
 };
 
-export type HelixHeadlessTableRowVueProps = {};
+export type HelixHeadlessTableRowVueProps = {
+  /** The key the table's `selected` lists this row by. Left empty, the row is
+known by its place among the rows as written. */
+  value?: (HelixHeadlessTableRow["value"]) | undefined;
+};
 
 export type HelixHeadlessTableRowVueEvents = {};
 
@@ -11466,10 +11845,9 @@ because it is coordination between elements rather than anything a consumer
 writes: the tab already says it.
 
 A string and not a reference: an IDREF resolves only in the tree it is
-written in, and an element reference cannot reach a sibling shadow tree
-either, so `aria-labelledby` to the tab's own id leaves the panel with no
-accessible name. `aria-label` on a `tabpanel` is how the pattern names one
-anyway. */
+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;
 };
 
@@ -11503,6 +11881,11 @@ Automatic is the default because showing a panel is usually cheap. Set this
 where it is not, so a reader arrowing past four tabs does not load four
 panels on the way. */
   manual?: (HelixHeadlessTabs["manual"]) | undefined;
+  /** The direction the tabs run. `vertical` sets them in a column beside the
+panels and tells a screen reader the list is vertical.
+
+Optional, so the resting row writes no attribute onto the host. */
+  orientation?: (HelixHeadlessTabs["orientation"]) | undefined;
   /** How the row of tabs is drawn.
 
 Unset is a raised pill on the selected tab with nothing behind the row,
@@ -11564,6 +11947,13 @@ export type HelixHeadlessTabHelixSelectElementEvent =
   HelixHeadlessTabElementEvent<HelixSelectEvent>;
 
 export type HelixHeadlessTabVueProps = {
+  /** The URL the tab links to. Setting it renders the tab as a link, for a set
+of tabs that are pages of a site. */
+  href?: (HelixHeadlessTab["href"]) | undefined;
+  /** The link's `rel`, for a tab with an `href`. */
+  rel?: (HelixHeadlessTab["rel"]) | undefined;
+  /** Where the link opens, such as `_blank`, for a tab with an `href`. */
+  target?: (HelixHeadlessTab["target"]) | undefined;
   /** Whether the item is disabled and cannot be chosen. */
   disabled?: (HelixHeadlessTab["disabled"]) | undefined;
   /** Whether the item is selected.
@@ -12448,6 +12838,19 @@ export type HelixHeadlessTimePickerVueEvents = {
   input: HelixHeadlessTimePickerElementEvent;
 };
 
+export type HelixHeadlessTimelineGroupVueProps = {
+  /** The level of the group's heading, from 1 to 6. */
+  "heading-level"?: (HelixHeadlessTimelineGroup["headingLevel"] | `${number}`) | undefined;
+  /** The level of the group's heading, from 1 to 6. */
+  headingLevel?: (HelixHeadlessTimelineGroup["headingLevel"]) | undefined;
+  /** The heading, when it is plain text, such as "Today".
+
+The fallback of the `heading` slot, so slotted content replaces it. */
+  label?: (HelixHeadlessTimelineGroup["label"]) | undefined;
+};
+
+export type HelixHeadlessTimelineGroupVueEvents = {};
+
 export type HelixHeadlessTimelineItemVueProps = {
   /** When it happened, in machine-readable form. Setting it wraps the time in a
 `<time>` element.
@@ -12801,6 +13204,12 @@ and wins over this. */
   label?: (HelixHeadlessToolbar["label"]) | undefined;
   /** The direction the arrow keys move focus in. */
   orientation?: (HelixHeadlessToolbar["orientation"]) | undefined;
+  /** Whether the arrow keys stop at the first and the last control. Unset, they
+wrap around from one end to the other. */
+  "stop-at-ends"?: (HelixHeadlessToolbar["stopAtEnds"]) | undefined;
+  /** Whether the arrow keys stop at the first and the last control. Unset, they
+wrap around from one end to the other. */
+  stopAtEnds?: (HelixHeadlessToolbar["stopAtEnds"]) | undefined;
 };
 
 export type HelixHeadlessToolbarVueEvents = {};
@@ -13125,6 +13534,9 @@ export type HelixHeadlessTreeItemHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixHeadlessTreeItemHelixBeforeOpenElementEvent =
   HelixHeadlessTreeItemElementEvent<HelixBeforeOpenEvent>;
+/** `helix-load` event type */
+export type HelixHeadlessTreeItemHelixLoadElementEvent =
+  HelixHeadlessTreeItemElementEvent<HelixLoadEvent>;
 /** `helix-select` event type */
 export type HelixHeadlessTreeItemHelixSelectElementEvent =
   HelixHeadlessTreeItemElementEvent<HelixSelectEvent>;
@@ -13133,12 +13545,20 @@ export type HelixHeadlessTreeItemToggleElementEvent =
   HelixHeadlessTreeItemElementEvent<ToggleEvent>;
 
 export type HelixHeadlessTreeItemVueProps = {
+  /** Whether the item cannot be chosen, opened or followed. The arrow keys still
+reach it, so a reader knows it is there. */
+  disabled?: (HelixHeadlessTreeItem["disabled"]) | undefined;
   /** The URL this node links to. Setting it makes the row a link.
 
 Unset by default, and unreflected: a tree of choosable nodes is not a tree
 of links, and an empty `href` written onto every row would be a link to the
 current page on every item a consumer never asked to be one. */
   href?: (HelixHeadlessTreeItem["href"]) | undefined;
+  /** Whether the item is a branch whose children are loaded when it opens.
+
+Opening it sends `helix-load`. Add the children to its `children` slot,
+and remove `lazy` once they are in, as Web Awesome's tree item does. */
+  lazy?: (HelixHeadlessTreeItem["lazy"]) | undefined;
   /** The link's `rel` value, which describes how the linked page relates to this
 one.
 
@@ -13206,6 +13626,8 @@ export type HelixHeadlessTreeItemVueEvents = {
   "helix-before-close": HelixHeadlessTreeItemHelixBeforeCloseElementEvent;
   /** Fired before a branch opens, and cancelable. */
   "helix-before-open": HelixHeadlessTreeItemHelixBeforeOpenElementEvent;
+  /** Fired when a `lazy` item opens, so you can load its children. */
+  "helix-load": HelixHeadlessTreeItemHelixLoadElementEvent;
   /** Fired when the item is chosen, and cancelable. Canceling it changes nothing. */
   "helix-select": HelixHeadlessTreeItemHelixSelectElementEvent;
   /** Sent when the branch opens or closes, with `newState` and `oldState`. */
@@ -13268,6 +13690,16 @@ branch as a label; a headless consumer reads the attribute and the
 written here appears in the served markup of every tree anybody renders.
 The resting state is the absence of the attribute, which is `peer`. */
   nesting?: (HelixHeadlessTree["nesting"]) | undefined;
+  /** Whether a reader can check many items. Unset, one item is chosen at a
+time.
+
+Optional, so a tree of one choice writes no attribute onto the host. */
+  "selection-mode"?: (HelixHeadlessTree["selectionMode"]) | undefined;
+  /** Whether a reader can check many items. Unset, one item is chosen at a
+time.
+
+Optional, so a tree of one choice writes no attribute onto the host. */
+  selectionMode?: (HelixHeadlessTree["selectionMode"]) | undefined;
   /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixHeadlessTree["emptyText"]) | undefined;
   /** The text shown and announced when there are no rows and none are loading. */
@@ -13299,6 +13731,9 @@ Ignored once `active` is written. */
 
 Ignored once `active` is written. */
   defaultActive?: (HelixHeadlessTree["defaultActive"]) | undefined;
+  /** The checked values, as a list, under `selection-mode="multiple"`, and the
+chosen value alone otherwise. Writing it sets `active`. */
+  values?: (HelixHeadlessTree["values"]) | undefined;
 };
 
 export type HelixHeadlessTreeVueEvents = {
@@ -13428,10 +13863,25 @@ export type HelixHeadlessVideoPlaylistHelixActivateElementEvent =
 /** `helix-before-activate` event type */
 export type HelixHeadlessVideoPlaylistHelixBeforeActivateElementEvent =
   HelixHeadlessVideoPlaylistElementEvent<HelixBeforeActivateEvent>;
+/** `helix-end` event type */
+export type HelixHeadlessVideoPlaylistHelixEndElementEvent =
+  HelixHeadlessVideoPlaylistElementEvent<HelixEndEvent>;
 
 export type HelixHeadlessVideoPlaylistVueProps = {
   /** The list's name, read by screen readers. */
   label?: (HelixHeadlessVideoPlaylist["label"]) | undefined;
+  /** What happens when an entry ends with no next one to go to. `one` plays the
+same entry again, and `all` goes from the last entry back to the first.
+Absent, the playlist stops on the last entry and sends `helix-end`.
+
+`all` also lets the next and previous controls go round, so next on the
+last entry is the first. `one` changes only what an ending does: next and
+previous still move, being a reader asking for another entry. */
+  repeat?: (HelixHeadlessVideoPlaylist["repeat"]) | undefined;
+  /** Whether the entries play in a random order. The order starts from the
+entry that is current, and holds until shuffle is turned off or an entry
+arrives or leaves, so previous goes back through what has played. */
+  shuffle?: (HelixHeadlessVideoPlaylist["shuffle"]) | undefined;
   /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
@@ -13456,6 +13906,8 @@ export type HelixHeadlessVideoPlaylistVueEvents = {
   "helix-activate": HelixHeadlessVideoPlaylistHelixActivateElementEvent;
   /** The current entry is about to change. Cancelable: cancel it to keep the current entry. */
   "helix-before-activate": HelixHeadlessVideoPlaylistHelixBeforeActivateElementEvent;
+  /** The last entry finished playing, and the playlist stopped there. Not sent while `repeat` is set. */
+  "helix-end": HelixHeadlessVideoPlaylistHelixEndElementEvent;
 };
 
 /** `HelixHeadlessVideo` component event */
@@ -13474,10 +13926,10 @@ export type HelixHeadlessVideoVueProps = {
   /** Whether the video starts playing on its own. Browsers allow this only while
 it is muted.
 
-Forwarded rather than acted on. Whether an unprompted play is permitted is
-the browser's policy and not this element's, and `play()` already swallows
-the refusal: what follows a refused autoplay is a paused player showing its
-start control, which is the correct thing to be looking at. */
+Forwarded to the video, which decides. Whether an unprompted play is
+permitted is the browser's policy, and what follows a refused autoplay is a
+paused player showing its start control, which is the correct thing to be
+looking at. */
   autoplay?: (HelixHeadlessVideo["autoplay"]) | undefined;
   /** The name of the captions control when the video has one track. The control
 turns that track on and off.
@@ -13711,6 +14163,12 @@ bar: two of the same control is worse than either placement. */
   "pip-label"?: (HelixHeadlessVideo["pipLabel"]) | undefined;
   /** What the control that floats the video over other windows is called. */
   pipLabel?: (HelixHeadlessVideo["pipLabel"]) | undefined;
+  /** The name of the player when `label` is not set. The player is a group, and
+this is what a screen reader calls it on arriving. */
+  "player-label"?: (HelixHeadlessVideo["playerLabel"]) | undefined;
+  /** The name of the player when `label` is not set. The player is a group, and
+this is what a screen reader calls it on arriving. */
+  playerLabel?: (HelixHeadlessVideo["playerLabel"]) | undefined;
   /** The name of the play control while pressing it would start the video. */
   "play-label"?: (HelixHeadlessVideo["playLabel"]) | undefined;
   /** The name of the play control while pressing it would start the video. */
@@ -13760,6 +14218,14 @@ nothing in it says "press to watch".
 behind a hero, a grid of eight thumbnails, anything where the video is
 decoration rather than something to start.
 
+**It is for the pointer, and the bar's Play is for everyone else.** Both
+play the video, so a keyboard met two stops called "Play" one after the
+other and a screen reader read the same button twice. The large one is out
+of the tab order and hidden from assistive technology while the bar is
+drawn, which is whenever it is: it shows only while the video is not
+playing, and the bar does not fade then. A press on it leaves focus on the
+player, so the keys go on working once it has gone.
+
 A value rather than a boolean, so the resting state is the attribute's
 absence: a boolean defaulting to on would have to be spelled as its own
 negation. */
@@ -13777,6 +14243,14 @@ nothing in it says "press to watch".
 behind a hero, a grid of eight thumbnails, anything where the video is
 decoration rather than something to start.
 
+**It is for the pointer, and the bar's Play is for everyone else.** Both
+play the video, so a keyboard met two stops called "Play" one after the
+other and a screen reader read the same button twice. The large one is out
+of the tab order and hidden from assistive technology while the bar is
+drawn, which is whenever it is: it shows only while the video is not
+playing, and the bar does not fade then. A press on it leaves focus on the
+player, so the keys go on working once it has gone.
+
 A value rather than a boolean, so the resting state is the attribute's
 absence: a boolean defaulting to on would have to be spelled as its own
 negation. */
@@ -13811,17 +14285,69 @@ past the end is the one write the platform answers with an exception. */
 };
 
 export type HelixHeadlessVideoVueEvents = {
-  /** The video reached its end. Relayed from the inner video, since the native event does not cross the shadow boundary. */
+  /** The media stopped loading before it finished, without an error. */
+  abort: HelixHeadlessVideoElementEvent;
+  /** Enough has loaded to start playing. */
+  canplay: HelixHeadlessVideoElementEvent;
+  /** Enough has loaded to play to the end without stopping, at the current rate. */
+  canplaythrough: HelixHeadlessVideoElementEvent;
+  /** The duration changed, which it does once the metadata is in. */
+  durationchange: HelixHeadlessVideoElementEvent;
+  /** The media was reset, as when `src` changes. */
+  emptied: HelixHeadlessVideoElementEvent;
+  /** The video reached its end. */
   ended: HelixHeadlessVideoElementEvent;
+  /** The source could not be loaded or played. The player shows `error-label` as well. */
+  error: HelixHeadlessVideoElementEvent;
   /** The next video was requested. Load it in response. */
   "helix-next": HelixHeadlessVideoHelixNextElementEvent;
   /** The previous video was requested. Load it in response. */
   "helix-previous": HelixHeadlessVideoHelixPreviousElementEvent;
-  /** Playback paused. Relayed from the inner video. */
+  /** The frame at the current position has loaded. */
+  loadeddata: HelixHeadlessVideoElementEvent;
+  /** The duration and the size of the video are known. */
+  loadedmetadata: HelixHeadlessVideoElementEvent;
+  /** The video started looking for its media. */
+  loadstart: HelixHeadlessVideoElementEvent;
+  /** Playback paused. */
   pause: HelixHeadlessVideoElementEvent;
-  /** Playback started. Relayed from the inner video. */
+  /** Playback was asked to start. */
   play: HelixHeadlessVideoElementEvent;
-};
+  /** Playback started, or started again after waiting for data. */
+  playing: HelixHeadlessVideoElementEvent;
+  /** More of the media has downloaded. */
+  progress: HelixHeadlessVideoElementEvent;
+  /** The playback rate changed. Read `playbackRate`. */
+  ratechange: HelixHeadlessVideoElementEvent;
+  /** The video's own width or height changed. Read `videoWidth` and `videoHeight`. */
+  resize: HelixHeadlessVideoElementEvent;
+  /** A move to a new position finished. */
+  seeked: HelixHeadlessVideoElementEvent;
+  /** A move to a new position started. */
+  seeking: HelixHeadlessVideoElementEvent;
+  /** The browser is trying to load more data and none is arriving. */
+  stalled: HelixHeadlessVideoElementEvent;
+  /** Loading paused on purpose, as when `preload` asks for no more. */
+  suspend: HelixHeadlessVideoElementEvent;
+  /** The position changed. Read `currentTime`. */
+  timeupdate: HelixHeadlessVideoElementEvent;
+  /** The volume or the mute changed. Read `volume` and `muted`. */
+  volumechange: HelixHeadlessVideoElementEvent;
+  /** Playback stopped to wait for more data. */
+  waiting: HelixHeadlessVideoElementEvent;
+};
+
+/** `HelixHeadlessVirtualList` component event */
+export type HelixHeadlessVirtualListElementEvent<E = Event> = TypedEvent<
+  HelixHeadlessVirtualList,
+  E
+>;
+/** `helix-load-more` event type */
+export type HelixHeadlessVirtualListHelixLoadMoreElementEvent =
+  HelixHeadlessVirtualListElementEvent<HelixLoadMoreEvent>;
+/** `helix-range-change` event type */
+export type HelixHeadlessVirtualListHelixRangeChangeElementEvent =
+  HelixHeadlessVirtualListElementEvent<HelixRangeChangeEvent>;
 
 export type HelixHeadlessVirtualListVueProps = {
   /** The height of one row, in pixels, used to find the row at a scroll offset.
@@ -13829,7 +14355,8 @@ export type HelixHeadlessVirtualListVueProps = {
 An estimate rather than a measurement while `measured` is off, which is
 right whenever the rows really are one height and is the cheaper of the two. */
   estimate?: (HelixHeadlessVirtualList["estimate"]) | undefined;
-  /** The id of the script element that holds the rows as JSON. */
+  /** The id of the script element that holds the items as JSON. `items` wins
+where both are set. */
   for?: (HelixHeadlessVirtualList["for"]) | undefined;
   /** The list's name, read by screen readers, because only some of its rows
 are rendered at a time.
@@ -13846,9 +14373,27 @@ disagree with itself; measuring is what a set of genuinely different
 heights needs and costs a read of each row as it renders. A list of
 one-line rows should leave this alone. */
   measured?: (HelixHeadlessVirtualList["measured"]) | undefined;
+  /** The items, as an array. Set it as a property.
+
+Each item is drawn by `renderItem`, or into the row `<template>` by its
+fields. A new array draws the new rows, so replace the array to change it.
+Left unset, the list reads the script that `for` names. */
+  items?: (HelixHeadlessVirtualList["items"]) | undefined;
+  /** Draws one item into its row, given the item and its index. Set it as a
+property.
+
+It returns what Lit renders: a template from `html`, a string, or a DOM
+node. The list wraps each result in a `<div>` that carries the row's role
+and place in the set. Where it is unset, the row `<template>` is used. */
+  renderItem?: (HelixHeadlessVirtualList["renderItem"]) | undefined;
 };
 
-export type HelixHeadlessVirtualListVueEvents = {};
+export type HelixHeadlessVirtualListVueEvents = {
+  /** Fired when a reader comes within one screen of the last item, once for each length of the set. */
+  "helix-load-more": HelixHeadlessVirtualListHelixLoadMoreElementEvent;
+  /** Fired when the items on screen change, with the new `first` and `last`, which `range` also holds. */
+  "helix-range-change": HelixHeadlessVirtualListHelixRangeChangeElementEvent;
+};
 
 export type CustomCssProperties = {
   /** The width of an axis, in `ch`, set from the widest number on it. The chart sets it on the axis itself, and only when the categories run along the bottom. In a horizontal chart the axis is a row, one line high. */
@@ -13879,6 +14424,8 @@ export type CustomCssProperties = {
   "--color-picker-swatch"?: (string) | undefined;
   /** The alignment of the cell's column: `start`, `center`, or `end`. Unset when the column sets none. The component writes it on each cell it draws, and the stylesheet reads it. `Table` sets `--table-cell-align` for the same purpose. */
   "--data-table-cell-align"?: (string) | undefined;
+  /** How deep a row is in a tree grid, from 1. The component writes it on each row header cell, and the stylesheet indents by it. */
+  "--data-table-level"?: (string) | undefined;
   /** The column track list, worked out from the columns. The component writes it inline on the element that reads it, so setting it has no effect. Set a column's `width` to change it. */
   "--data-table-template"?: (string) | undefined;
   /** How many month columns are drawn, capped at two. `--date-picker-columns` overrides it. */
@@ -13921,6 +14468,10 @@ export type CustomCssProperties = {
   "--chart-terminus-x"?: (string) | undefined;
   /** Where a series' last reading sits vertically, as a percentage. Written by the component. */
   "--chart-terminus-y"?: (string) | undefined;
+  /** The number of the first row, written where `start` or `reversed` moves it. */
+  "--list-first"?: (string) | undefined;
+  /** What each row adds to the number before it: `1`, or `-1` where `reversed`. */
+  "--list-step"?: (string) | undefined;
   /** How far the needle turns to point north, as an angle. The frame writes it from `bearing`. */
   "--map-needle-turn"?: (string) | undefined;
   /** Where the panel starts, measured from the bar above it. */
@@ -13951,6 +14502,10 @@ export type CustomCssProperties = {
   "--chart-point-y"?: (string) | undefined;
   /** A tick's position along its axis, as a percentage. The component writes it. */
   "--chart-tick"?: (string) | undefined;
+  /** How far along its axis the content is scrolled, from 0 at the start to 1 at the end. Written on each `scrollbar` part, so its thumb inherits it. Counted from the right on a right-to-left page. */
+  "--scroll-area-scroll-fraction"?: (string) | undefined;
+  /** The share of the track the thumb covers, from 0 to 1, which is how much of the content is in view. Written on each `scrollbar` part. */
+  "--scroll-area-thumb-fraction"?: (string) | undefined;
   /** The value as a fraction of the range, 0 to 1. */
   "--slider-fraction"?: (string) | undefined;
   /** Where a range's filled span starts, as a fraction of the track, 0 to 1. */
@@ -13985,7 +14540,7 @@ export type CustomCssProperties = {
 // Note: Some tooling expects this augmentation under "@vue/runtime-core", while
 // other docs/examples use "vue". We emit both for compatibility.
 export interface WcToolkitVueGlobalComponents {
-  /** Holds its own open state. Used alone, outside an accordion, it works as a disclosure.  The trigger sits inside a heading, so a screen reader lists the section with the page's headings. The level is the item's 'heading-level', then the accordion's, then 3.  Content stays mounted when the item is closed, so it can animate and its text is present in server-rendered HTML. Closed content has both 'hidden' and 'inert'. 'hidden' collapses it when no stylesheet is loaded. 'inert' keeps it out of the tab order and the accessibility tree after the styled tier's 'display' overrides 'hidden'. */
+  /** Holds its own open state. Used alone, outside an accordion, it works as a disclosure.  The trigger sits inside a heading, so a screen reader lists the section with the page's headings. The level is the item's 'heading-level', then the accordion's, then 3.  Content stays mounted when the item is closed, so it can animate and its text is present in server-rendered HTML. Closed content has both 'hidden' and 'inert'. 'hidden' collapses it when no stylesheet is loaded. 'inert' keeps it out of the tab order and the accessibility tree after the styled tier's 'display' overrides 'hidden'.  Set 'hidden-until-found' and the browser's find in page searches a closed section too: a match opens it, with 'helix-before-open' first, as React Aria's disclosure does. The content is then 'hidden="until-found"' while closed, and not 'inert', since an inert region is never searched. */
   "helix-headless-accordion-item": DefineCustomElement<
     HelixHeadlessAccordionItem,
     HelixHeadlessAccordionItemVueProps,
@@ -13997,13 +14552,13 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessAccordionVueProps,
     HelixHeadlessAccordionVueEvents
   >;
-  /** An announcement is a banner above the page header with news about the whole site or session, such as a trial ending, a degraded service, or a change of terms. For a passage inside a document, use 'Callout', which stays where it is placed and cannot be dismissed.  The announcement is always a polite live region, whatever its 'tone'. 'role="alert"' is assertive and interrupts a screen reader, so an announcement served with the page would interrupt on every page load.  The live region is its own part. When the announcement appears after the page has loaded, the message is written into the region one frame later, so screen readers read it reliably, and the region is emptied seven seconds later, so the message is not in the page twice. When the announcement is in the served HTML, the region stays empty and nothing is read out.  The dismiss button fires 'helix-dismiss', and the announcement stays in the document, so remove it in your listener. The event is cancelable, and 'dismiss()' returns 'false' when a listener calls 'preventDefault()'. When your listener removes an announcement whose dismiss button has focus, focus moves to the dismiss button of the announcement beside it. With no other announcement beside it, move focus yourself, for example to the page's main heading. */
+  /** An announcement is a banner above the page header with news about the whole site or session, such as a trial ending, a degraded service, or a change of terms. For a passage inside a document, use 'Callout', which stays where it is placed and cannot be dismissed.  The announcement is always a polite live region, whatever its 'tone'. 'role="alert"' is assertive and interrupts a screen reader, so an announcement served with the page would interrupt on every page load.  The live region is its own part. When the announcement appears after the page has loaded, the message is written into the region one frame later, so screen readers read it reliably, and the region is emptied seven seconds later, so the message is not in the page twice. When the announcement is in the served HTML, the region stays empty and nothing is read out.  The dismiss button fires 'helix-dismiss', and the announcement stays in the document, so remove it in your listener. The event is cancelable, and 'dismiss()' returns 'false' when a listener calls 'preventDefault()'. When your listener removes an announcement whose dismiss button has focus, focus moves to the dismiss button of the announcement beside it. With no other announcement beside it, move focus yourself, for example to the page's main heading.  Set 'duration' to dismiss it after a time. The clock stops while the pointer or focus is on the announcement, and continues from what was left, so a reader partway through is not cut off. When the time runs out it sends 'helix-dismiss', as the button does. */
   "helix-headless-announcement": DefineCustomElement<
     HelixHeadlessAnnouncement,
     HelixHeadlessAnnouncementVueProps,
     HelixHeadlessAnnouncementVueEvents
   >;
-  /** Tracks whether the page has scrolled and sets the custom state 'scrolled', so the styled tier can lift the bar without a scroll handler of its own. The state is read when the element connects. A fresh load starts at the top, which matches the server markup, and a reload partway down the page is corrected on hydration.  The element uses a custom state because an attribute such as 'data-scrolled', written onto its own host, is one the server did not send. A hydrating framework would report a mismatch whenever the page reloads far enough down. 'ElementInternals.states' is not in the DOM, so hydration has nothing to compare. Select the state with ':state(scrolled)'.  The page is the window unless 'scroller' names the element that scrolls, for an app shell whose content scrolls inside a container. */
+  /** Tracks whether the page has scrolled and sets the custom state 'scrolled', so the styled tier can lift the bar without a scroll handler of its own. The state is read when the element connects. A fresh load starts at the top, which matches the server markup, and a reload partway down the page is corrected on hydration.  The element uses a custom state because an attribute such as 'data-scrolled', written onto its own host, is one the server did not send. A hydrating framework would report a mismatch whenever the page reloads far enough down. 'ElementInternals.states' is not in the DOM, so hydration has nothing to compare. Select the state with ':state(scrolled)'.  The page is the window unless 'scroller' names the element that scrolls, for an app shell whose content scrolls inside a container.  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 '<header>' is there, so a header inside a card or a pane does not add a second banner. A server cannot see the ancestors, so it serves the banner and the browser corrects it when the element connects. */
   "helix-headless-app-header": DefineCustomElement<
     HelixHeadlessAppHeader,
     HelixHeadlessAppHeaderVueProps,
@@ -14051,7 +14606,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessBreadcrumbVueProps,
     HelixHeadlessBreadcrumbVueEvents
   >;
-  /** The host is the navigation landmark, named "Breadcrumb" by default. An 'aria-label' on the host names the trail instead, and so does 'label'. When a page has more than one navigation landmark, screen reader users choose between them by name.  The '<ol>' has an explicit 'role="list"', because Safari removes list semantics from a list with 'list-style: none', and the trail always hides its markers.  The items are slotted directly, so they are '<ol>' children in the flat tree, and each item sets 'role="listitem"' on itself.  The trail does not measure itself, and you write its overflow in markup: put the crumb that holds the folded items where the gap should appear. */
+  /** The host is the navigation landmark, named "Breadcrumb" by default. An 'aria-label' on the host names the trail instead, and so does 'label'. When a page has more than one navigation landmark, screen reader users choose between them by name.  The '<ol>' has an explicit 'role="list"', because Safari removes list semantics from a list with 'list-style: none', and the trail always hides its markers.  The items are slotted directly, so they are '<ol>' children in the flat tree, and each item sets 'role="listitem"' on itself.  The trail does not measure itself, and you write its overflow in markup: put the crumb that holds the folded items where the gap should appear.  A trail built from data, such as a router's matched routes, takes 'items': an array of '{ label, href }', drawn as crumbs in order, the last one as the current page. Slotted crumbs follow them. Use one way or the other in a trail. */
   "helix-headless-breadcrumbs": DefineCustomElement<
     HelixHeadlessBreadcrumbs,
     HelixHeadlessBreadcrumbsVueProps,
@@ -14099,25 +14654,25 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessCardVueProps,
     HelixHeadlessCardVueEvents
   >;
-  /** The track is a scroll container with scroll snapping, so dragging, trackpad swipes, and the browser's momentum scrolling all work. The controls scroll the track.  Slides are your own elements, and the carousel writes nothing onto them. It renders a pane for each slide with 'role="group"', 'aria-roledescription="slide"', and a name that gives the slide's position in the set, and assigns the slide into it. A screen reader announces the position, and a slide that is a link stays a link. See 'assign'.  **Rotation stops on focus and on hover, and stays stopped** until the user starts it again, as the APG requires. The rotation control is labeled with the action it performs and is first in the tab order. Rotation goes on from the last slide to the first, with or without 'loop', which is about the reader's own moves.  A move the reader makes is announced, the slide's position read from a polite live region. While the carousel rotates the region is off, so a screen reader is not interrupted every few seconds.  The indicators are one tab stop. The arrow keys along the track move between them, Up and Down on a vertical carousel, and Home and End go to the first and the last. Without 'loop', Previous on the first slide and Next on the last are marked 'aria-disabled'. */
+  /** The track is a scroll container with scroll snapping, so dragging, trackpad swipes, and the browser's momentum scrolling all work. The controls scroll the track.  Slides are your own elements, and the carousel writes nothing onto them. It renders a pane for each slide with 'role="group"', 'aria-roledescription="slide"', and a name that gives the slide's position in the set, and assigns the slide into it. A screen reader announces the position, and a slide that is a link stays a link. See 'assign'.  **Rotation stops on focus and on hover, and stays stopped** until the user starts it again, as the APG requires. The rotation control is labeled with the action it performs and is first in the tab order. Rotation goes on from the last slide to the first, with or without 'loop', which is about the reader's own moves.  A move the reader makes is announced, the slide's position read from a polite live region. While the carousel rotates the region is off, so a screen reader is not interrupted every few seconds.  The indicators are one tab stop. The arrow keys along the track move between them, Up and Down on a vertical carousel, and Home and End go to the first and the last. Without 'loop', Previous on the first slide and Next on the last are marked 'aria-disabled'.  **'mouse-drag' lets a mouse drag the track**, which otherwise only a touch screen, a trackpad, or the scroll wheel moves. The drag follows the pointer with snapping off and settles on the nearest slide when it is let go, and that move is announced and refusable like a press of Next. A link in a slide is not followed at the end of a drag.  The glyphs on Previous and Next can be replaced by slotting an icon of your own into 'previous-icon' and 'next-icon'. */
   "helix-headless-carousel": DefineCustomElement<
     HelixHeadlessCarousel,
     HelixHeadlessCarouselVueProps,
     HelixHeadlessCarouselVueEvents
   >;
-  /** The composer is a separate element so you can replace it. If you need attachments, slash commands, or a model picker, replace the composer and keep the transcript.  By default, Enter sends and Shift+Enter starts a new line, the convention in messaging apps. Document editors mostly use the opposite, so 'submit-on' takes 'enter' or 'button'. Use 'button' for a long-form composer.  The composer clears only when no listener cancels the send, so the text is kept when you cancel a send that failed. */
+  /** The composer is a separate element so you can replace it. If you need attachments, slash commands, or a model picker, replace the composer and keep the transcript.  By default, Enter sends and Shift+Enter starts a new line, the convention in messaging apps. Document editors mostly use the opposite, so 'submit-on' takes 'enter' or 'button'. Use 'button' for a long-form composer.  The composer clears only when no listener cancels the send, so the text is kept when you cancel a send that failed.  **In a form, the draft is the composer's value**, submitted under 'name'. A form reset puts back the 'value' the markup declared, and a '<fieldset disabled>' turns the composer off. Sending is still 'helix-send', and it does not submit the form.  **'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 'typing-timeout' milliseconds. Pass it on to show "is typing" to the other side. */
   "helix-headless-chat-composer": DefineCustomElement<
     HelixHeadlessChatComposer,
     HelixHeadlessChatComposerVueProps,
     HelixHeadlessChatComposerVueEvents
   >;
-  /** A chat message carries its state: sending, arrived, streaming, or failed. A failed message has a retry control in the message, which fires 'helix-send'.  'streaming' is the state the others are arranged around. A streaming message changes height on every frame, so it is marked 'aria-busy' while it arrives and announced once when it settles. A screen reader cannot follow a stream read out character by character. */
+  /** A chat message carries its state: sending, arrived, streaming, or failed. A failed message has a retry control in the message, which fires 'helix-send'.  'streaming' is the state the others are arranged around. A streaming message changes height on every frame, so it is marked 'aria-busy' while it arrives and announced once when it settles. A screen reader cannot follow a stream read out character by character.  A screen reader names the turn by its author and its time, such as "You, 2 minutes ago". The author is 'author-label', or "You" for 'me', or the 'author' itself where it is a name; give a turn by 'them' an 'author-label' to name it. The chat it sits in holds the sentence and the word for 'me', so a page in another language sets them once there. The time moves on by itself, so "now" becomes "1 minute ago" while the page is open. */
   "helix-headless-chat-message": DefineCustomElement<
     HelixHeadlessChatMessage,
     HelixHeadlessChatMessageVueProps,
     HelixHeadlessChatMessageVueEvents
   >;
-  /** Chat has no positioning, no backdrop, and no trigger, so you can put it in any container, such as a page, a sidebar, a modal, or a floating panel.  The transcript stays pinned to the bottom, including while a streamed answer grows, until the user scrolls more than 'threshold' away from it.  With 'history' set to 'more', reaching the top fires 'helix-history'. Set 'loading' while you fetch, then prepend the older turns. The turn the user was reading stays in place on screen.  The log is 'aria-live="off"'. A separate status region announces each new turn once, when it has finished arriving. It skips the user's own turns unless they failed to send, turns loaded as history, and the turns already there when the transcript opened.  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 transcript one window at a time, so the log needs a block size of its own.  A turn from 'turns' is drawn in the chat's shadow root, so style it through the forwarded 'message-*' parts. A turn by 'me' also gets each part with '-mine' added, and the turn's state adds 'message-meta-failed', 'message-content-sending', and 'message-content-streaming'. To style each participant differently, pass the turns as children. */
+  /** Chat has no positioning, no backdrop, and no trigger, so you can put it in any container, such as a page, a sidebar, a modal, or a floating panel.  The transcript stays pinned to the bottom, including while a streamed answer grows, until the user scrolls more than 'threshold' away from it.  With 'history' set to 'more', reaching the top fires 'helix-history'. Set 'loading' while you fetch, then prepend the older turns. The turn the user was reading stays in place on screen.  The log is 'aria-live="off"'. A separate status region announces each new turn once, when it has finished arriving. It skips the user's own turns unless they failed to send, turns loaded as history, and the turns already there when the transcript opened.  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 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 transcript, a 'Chat.Message' stands for each turn, and a 'Chat.Composer' sits in the 'composer' slot. When the user sends, 'helix-send' reaches the chat: add their turn with 'author="me"' and 'state="sending"', then set 'state' to 'sent' or 'failed' when your server answers. Add the reply as a turn with 'state="streaming"', write its text as it arrives, and set 'state' to 'sent' when it is complete. While the user types, the composer sends 'helix-typing', which you can pass on to the other side. Show the other side's typing in the 'status' slot.  A screen reader names each turn by its author and its time, such as "You, 2 minutes ago". Set 'me-label' and 'message-label' to say it in your language, and give each turn by 'them' an 'author-label'.  A turn from 'turns' is drawn in the chat's shadow root, so style it through the forwarded 'message-*' parts. A turn by 'me' also gets each part with '-mine' added, and the turn's state adds 'message-meta-failed', 'message-content-sending', and 'message-content-streaming'. To style each participant differently, pass the turns as children. */
   "helix-headless-chat": DefineCustomElement<
     HelixHeadlessChat,
     HelixHeadlessChatVueProps,
@@ -14177,7 +14732,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessCopyButtonVueProps,
     HelixHeadlessCopyButtonVueEvents
   >;
-  /** Declare the columns as 'TableColumn' children and pass the rows as an array. The schema stays readable in the HTML, and the rows can be windowed, which ten thousand row elements cannot be.  '''html <helix-headless-data-table .rows=${rows} sort="name:asc" page-size="20">   <helix-headless-table-column field="name" sortable>Name</helix-headless-table-column>   <helix-headless-table-column field="size" text-align="end" sortable .cell=${bytes}>Size</helix-headless-table-column> </helix-headless-data-table> '''  For a short table written out by hand, use 'Table', which takes rows as markup.  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.  'selectable' adds a column of checkboxes, keyed on 'row-key':  - A row is selected by its key, so the selection survives a sort, a filter,   and a page change. - 'selected' holds the chosen keys, comma separated, the same shape 'Listbox'   uses for a multiple choice. As with 'sort', writing it applies the   selection, and 'default-selected' holds what the markup declared. - The checkbox in the heading selects every row in the result, across pages,   and shows a dash while only some are chosen.  To act on a single row, such as opening it, put a link or a button in a cell.  The grid is one tab stop, and the arrow keys move between its cells, the headings included:  - The arrow keys move one cell, and Home and End to the ends of the row. - Control with Home or End moves to the first or the last cell of the grid. - Page Up and Page Down move by the rows that fit in view. - Enter or F2 moves into the cell's controls, and Escape moves back to the   cell. Tab moves between the controls of one cell. - Enter or Space on a sortable heading sorts by it, and Space on a row of a   'selectable' table selects it.  The controls inside the cells leave the tab order, so Tab moves past the whole grid. A windowed table keeps the row holding focus drawn while the rest scroll away.  People can resize and reorder the columns. 'resizable' on a column puts a separator on its edge. 'reorderable' on the table puts a grip on each heading that has a 'field', moved by dragging or with the arrow keys. The new order is written to 'order' as a list of fields. Your markup is not rewritten: the table assigns the headings to its header in that order.  'csv()' returns the result as text: every row that passes the filter, in the order and the columns on screen. Saving the file is up to you.  'DataTable' has no 'columns' attribute. Each 'TableColumn' is part of the schema, so you size a column with its own 'width'. 'Table' has 'columns' because its cells are markup you write and it can have no columns at all. Written on 'DataTable', 'columns' has no effect, so watch for it when you move a table from 'Table' to 'DataTable'. */
+  /** Declare the columns as 'TableColumn' children and pass the rows as an array. The schema stays readable in the HTML, and the rows can be windowed, which ten thousand row elements cannot be.  '''html <helix-headless-data-table .rows=${rows} sort="name:asc" page-size="20">   <helix-headless-table-column field="name" sortable>Name</helix-headless-table-column>   <helix-headless-table-column field="size" text-align="end" sortable .cell=${bytes}>Size</helix-headless-table-column> </helix-headless-data-table> '''  For a short table written out by hand, use 'Table', which takes rows as markup.  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.  'selectable' adds a column of checkboxes, keyed on 'row-key':  - A row is selected by its key, so the selection survives a sort, a filter,   and a page change. - 'selected' holds the chosen keys, comma separated, the same shape 'Listbox'   uses for a multiple choice. As with 'sort', writing it applies the   selection, and 'default-selected' holds what the markup declared. - The checkbox in the heading selects every row in the result, across pages,   and shows a dash while only some are chosen. - Shift with a press on a checkbox selects every row between it and the row   last chosen.  To act on a single row, such as opening it, put a link or a button in a cell.  The grid is one tab stop, and the arrow keys move between its cells, the headings included:  - The arrow keys move one cell, and Home and End to the ends of the row. - Control with Home or End moves to the first or the last cell of the grid. - Page Up and Page Down move by the rows that fit in view. - Enter or F2 moves into the cell's controls, and Escape moves back to the   cell. Tab moves between the controls of one cell. - Enter or Space on a sortable heading sorts by it, and Space on a row of a   'selectable' table selects it. - In a 'selectable' table, Shift with Up or Down selects the rows it moves   across, Shift with Space selects every row from the one last chosen, and   Control or Command with A selects every row. - Typing letters moves to the next row whose row header starts with them.  Each row is named by its row header, the column marked 'row-header', or the first column with a 'field' where none is. A screen reader says it as a reader moves between rows.  **Rows that hold rows.** 'child-field' names the field that holds a row's child rows, and the grid becomes a tree grid. The row header column draws a mark that a press opens and closes a row by, and 'expanded' holds the keys of the open rows, which 'row-key' names. Right on a closed row's header opens it, Left on an open one closes it, and Left on a child moves to its parent. A sort orders the rows under each parent, and a search shows the rows that lead to each match, open.  'load-more' adds a row after the last one with a button that sends 'helix-load-more'. A 'windowed' table also sends it by itself once a reader scrolls within one screen of the end, once for each number of rows. Add the next rows to 'rows', and set 'loading' while they are on their way.  The controls inside the cells leave the tab order, so Tab moves past the whole grid. A windowed table keeps the row holding focus drawn while the rest scroll away.  People can resize and reorder the columns. 'resizable' on a column puts a separator on its edge. 'reorderable' on the table puts a grip on each heading that has a 'field', moved by dragging or with the arrow keys. The new order is written to 'order' as a list of fields. Your markup is not rewritten: the table assigns the headings to its header in that order.  'csv()' returns the result as text: every row that passes the filter, in the order and the columns on screen. Saving the file is up to you.  'DataTable' has no 'columns' attribute. Each 'TableColumn' is part of the schema, so you size a column with its own 'width'. 'Table' has 'columns' because its cells are markup you write and it can have no columns at all. Written on 'DataTable', 'columns' has no effect, so watch for it when you move a table from 'Table' to 'DataTable'. */
   "helix-headless-data-table": DefineCustomElement<
     HelixHeadlessDataTable,
     HelixHeadlessDataTableVueProps,
@@ -14195,13 +14750,13 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessDatePickerVueProps,
     HelixHeadlessDatePickerVueEvents
   >;
-  /** Each pair is its own element: the label is the '<dt>' and the value its '<dd>', and a screen reader hears them together however the list lays them out.  The value is the default slot, because it varies and is often more than text, such as a tag, an avatar, or a link. The label is almost always text, so it is also a property. */
+  /** Each pair is its own element: the label is the '<dt>' and the value its '<dd>', and a screen reader hears them together however the list lays them out.  The value is the default slot, because it varies and is often more than text, such as a tag, an avatar, or a link. The label is almost always text, so it is also a property.  **For a label with several values, write each value as a '<dd>'**, such as the authors of a paper. The item then puts your '<dd>' elements after its '<dt>' in place of its own, so a screen reader hears one term and each of its descriptions, as in a native '<dl>'. A server cannot see your elements, so the served item wraps them in its own '<dd>' until it runs. */
   "helix-headless-description-list-item": DefineCustomElement<
     HelixHeadlessDescriptionListItem,
     HelixHeadlessDescriptionListItemVueProps,
     HelixHeadlessDescriptionListItemVueEvents
   >;
-  /** Renders a '<dl>', with each item's label as a '<dt>' and its value as a '<dd>', for panels such as "Owner: Ada, Region: us-east, Created: 3 days ago". A screen reader announces which label goes with which value and how many pairs there are.  **Each item renders its own term and description**, and the list takes the items through its slot. The accessibility tree is built from the flattened tree, so the pairs appear inside the list. Measured in Chromium, the result matches a plain '<dl>' with the same content node for node, both with a slotted label and with an item set to 'display: contents'. */
+  /** Renders a '<dl>', with each item's label as a '<dt>' and its value as a '<dd>', for panels such as "Owner: Ada, Region: us-east, Created: 3 days ago". A screen reader announces which label goes with which value and how many pairs there are.  **Each item renders its own term and description**, and the list takes the items through its slot. The accessibility tree is built from the flattened tree, so the pairs appear inside the list. Measured in Chromium, the result matches a plain '<dl>' with the same content node for node, both with a slotted label and with an item set to 'display: contents'.  **A named list is a named group.** A '<dl>' takes no name in ARIA 1.2, so the list becomes a group around it when it has 'label', 'aria-label' or 'aria-labelledby', and the name lands on the group. Unnamed, the host adds nothing to the tree. */
   "helix-headless-description-list": DefineCustomElement<
     HelixHeadlessDescriptionList,
     HelixHeadlessDescriptionListVueProps,
@@ -14237,7 +14792,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessDrilldownItemVueProps,
     HelixHeadlessDrilldownItemVueEvents
   >;
-  /** One panel whose content changes as you move between pages. Use it where there is no room for a second column, such as on a phone, or on a touch screen with no hover to open one.  It is a region that stays where you put it, such as inside a drawer, a sidebar, or a settings panel. A 'Menu' opens from a trigger and closes when you are done. 'Menu' can drill into pages too, through the same controller.  Rows are places to go and commands to run. Nothing here is form-associated and nothing is submitted. To choose a value, use a 'Listbox'.  A row that opens a page contains that page, so the stack holds one reference and reads the rest from the DOM. The behavior lives in 'DrilldownController', which 'Menu' shares.  The rows of the page showing are a 'menu', named by 'label' on the top page and by the page's title below it. The back button and the title sit above the menu. Disabled rows stay reachable with the arrow keys, and typing a letter moves to the next row whose name starts with it. */
+  /** One panel whose content changes as you move between pages. Use it where there is no room for a second column, such as on a phone, or on a touch screen with no hover to open one.  It is a region that stays where you put it, such as inside a drawer, a sidebar, or a settings panel. A 'Menu' opens from a trigger and closes when you are done. 'Menu' can drill into pages too, through the same controller.  Rows are places to go and commands to run. Nothing here is form-associated and nothing is submitted. To choose a value, use a 'Listbox'.  A row that opens a page contains that page, so the stack holds one reference and reads the rest from the DOM. The behavior lives in 'DrilldownController', which 'Menu' shares.  After each move the host carries 'data-direction', 'forward' into a page or 'back' out of one, so a stylesheet can slide the new page in from the side the reader is going. The styled tier does, and holds still under reduced motion.  The rows of the page showing are a 'menu', named by 'label' on the top page and by the page's title below it. The back button and the title sit above the menu. Disabled rows stay reachable with the arrow keys, and typing a letter moves to the next row whose name starts with it. */
   "helix-headless-drilldown": DefineCustomElement<
     HelixHeadlessDrilldown,
     HelixHeadlessDrilldownVueProps,
@@ -14357,13 +14912,13 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessLineChartVueProps,
     HelixHeadlessLineChartVueEvents
   >;
-  /** Provides layout and semantics. The row is a target only when you set 'href'.  **'href' makes the row a link.** The component wraps the leading content, the label, and the description in an '<a part="link">' inside the row, as 'Tree.Item' does. An anchor of your own cannot wrap slots it does not own. With the anchor, the row is a target, Enter follows it, middle click opens a new tab, the status bar shows the destination, and all of it works before JavaScript runs.  **The 'end' slot sits beside the link, outside it**, so a button or a menu there is a control of its own: a click on it does not follow the link, and its name is not part of the link's.  Client-side routing needs your own handling. A router cannot render its anchor inside the shadow root, so to navigate without a page load, intercept the click: the anchor is in 'composedPath()'. Handle only a plain primary click, so native gestures keep working.  **For a row that holds controls and is not a destination, use 'data-list-item'.** With 'href' unset, the row is not a link. */
+  /** Provides layout and semantics. The row is a target only when you set 'href'.  **'href' makes the row a link.** The component wraps the leading content, the label, and the description in an '<a part="link">' inside the row, as 'Tree.Item' does. An anchor of your own cannot wrap slots it does not own. With the anchor, the row is a target, Enter follows it, middle click opens a new tab, the status bar shows the destination, and all of it works before JavaScript runs.  **The 'end' slot sits beside the link, outside it**, so a button or a menu there is a control of its own: a click on it does not follow the link, and its name is not part of the link's.  Client-side routing needs your own handling. A router cannot render its anchor inside the shadow root, so to navigate without a page load, intercept the click: the anchor is in 'composedPath()'. Handle only a plain primary click, so native gestures keep working.  **For a row that holds controls and is not a destination, use 'data-list-item'.** With 'href' unset, the row is not a link.  'current' marks the row a reader is on, such as the page in a list of pages, with 'aria-current' on its link, or on the row where it has none.  **In a list with 'selection-mode', the row is a row of a grid.** The list gives it its role, its place in the one tab stop and, where the list selects, whether it is selected. Its link leaves the tab order there, and Enter follows it from the row. */
   "helix-headless-list-item": DefineCustomElement<
     HelixHeadlessListItem,
     HelixHeadlessListItemVueProps,
     HelixHeadlessListItemVueEvents
   >;
-  /** Sets 'role="list"' on the host, so a screen reader counts the rows and announces each one's position, such as "1 of 7". */
+  /** Sets 'role="list"' on the host, so a screen reader counts the rows and announces each one's position, such as "1 of 7".  **'selection-mode' makes the list interactive**, in the way of a grid list: a grid of rows that is one tab stop. Up and Down move between rows, Home and End go to the first and the last, and a typed letter goes to the next row starting with it. Left and Right move between the row and the controls in its 'end' slot. 'single' selects one row at a time and 'multiple' any number, with Space or a press, and 'value' holds the selected rows' values, separated by commas. A change asks with 'helix-before-change' and tells with 'change'. Enter acts on the row: it follows the row's link, or sends 'helix-action' from the row. 'none' selects nothing, so a press acts too. A 'disabled' row is passed over.  **Leave 'selection-mode' unset for a list a reader reads**, and set it for one a reader chooses from or acts on. The rows of an interactive list are grid rows, which hold controls as a list box option cannot. Give a control in 'end' 'tabindex="-1"' to leave it to the arrow keys and out of the tab order.  'start' and 'reversed' number an ordered list as '<ol>' does. The list writes where the numbers start and which way they run as '--list-first' and '--list-step' on its slot, which the styled tier counts from. Reversed with no 'start' counts down from the number of rows, which a server cannot know, so served markup counts from one until the list runs. */
   "helix-headless-list": DefineCustomElement<
     HelixHeadlessList,
     HelixHeadlessListVueProps,
@@ -14429,7 +14984,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessMapRasterVueProps,
     HelixHeadlessMapRasterVueEvents
   >;
-  /** Wraps a map drawn by MapLibre, Leaflet, or another renderer. The frame adds a name for the map, a column of controls, and a strip for the map credit. Helix does not draw the map itself.  The controls are one column, and 'controls' names which ones: 'fullscreen', 'layers', 'tilt', 'zoom', and 'compass', top to bottom. 'zoom compass fullscreen' by default. The compass's needle points north as the map turns, and pressing it turns the map to face north.  Add 'pan' and 'rotate' for buttons around the compass that move and turn the map. Dragging is otherwise the only way a pointer moves the map, so add them where the map has to be usable without dragging, as WCAG 2.2 asks at level AA. The arrow keys pan the map and Shift with Left or Right turns it either way.  The pan and zoom buttons and the arrow keys send 'helix-map-pan' and 'helix-map-zoom'. Move your map in response, or connect it with 'connectMap' from '@fusion.dev/helix-map', which does this for you.  Add 'tilt' to 'controls' for the 3D button, which a map with 3D buildings or terrain needs. It is a toggle. Pressed, it tilts the map 50 degrees, and 'connectMap' raises the buildings and the ground. Pressed again, it makes the map flat, and lays them flat too. Shift with Up or Down tilts the map in steps. Turning and tilting send 'helix-map-rotate' and 'helix-map-tilt', which 'connectMap' answers on MapLibre. Leaflet draws maps flat and does not rotate.  Add 'layers' to 'controls' for a layers button. It opens a menu with a tile for each layer, which sets the layer's 'hidden' attribute. Layers with the same 'group', such as a route and its dotted legs, share one tile. A tile sends 'helix-before-toggle' from the layer first, so you can store the choice or refuse it.  Imagery, a 'helix-map-raster' with 'ground', is a map type and not a tile. The menu opens with a card for each type, Standard, Hybrid, and Satellite, with a picture of the map in it, and 'map-type' says which is chosen. Standard hides the imagery, Hybrid draws it under the roads and names, and Satellite draws it alone. Choosing one sends 'helix-before-change' with its name, and 'change' once 'map-type' holds it. 'connectMap' does not draw a hidden layer, so a layer you write with 'hidden' starts turned off.  Markers, routes, areas, live positions, and points layers go inside the frame as child elements. */
+  /** Wraps a map drawn by MapLibre, Leaflet, or another renderer. The frame adds a name for the map, a column of controls, and a strip for the map credit. Helix does not draw the map itself.  The controls are one column, and 'controls' names which ones: 'fullscreen', 'layers', 'tilt', 'zoom', and 'compass', top to bottom. 'zoom compass fullscreen' by default. The compass's needle points north as the map turns, and pressing it turns the map to face north.  Add 'pan' and 'rotate' for buttons around the compass that move and turn the map. Dragging is otherwise the only way a pointer moves the map, so add them where the map has to be usable without dragging, as WCAG 2.2 asks at level AA. The arrow keys pan the map and Shift with Left or Right turns it either way.  The pan and zoom buttons and the arrow keys send 'helix-map-pan' and 'helix-map-zoom'. Move your map in response, or connect it with 'connectMap' from '@fusion.dev/helix-map', which does this for you.  Add 'tilt' to 'controls' for the 3D button, which a map with 3D buildings or terrain needs. It is a toggle. Pressed, it tilts the map 50 degrees, and 'connectMap' raises the buildings and the ground. Pressed again, it makes the map flat, and lays them flat too. Shift with Up or Down tilts the map in steps. Turning and tilting send 'helix-map-rotate' and 'helix-map-tilt', which 'connectMap' answers on MapLibre. Leaflet draws maps flat and does not rotate.  Add 'layers' to 'controls' for a layers button. It opens a menu with a tile for each layer, which sets the layer's 'hidden' attribute. Layers with the same 'group', such as a route and its dotted legs, share one tile. A tile sends 'helix-before-toggle' from the layer first, so you can store the choice or refuse it, and 'helix-toggle' from it once 'hidden' holds the choice.  Imagery, a 'helix-map-raster' with 'ground', is a map type and not a tile. The menu opens with a card for each type, Standard, Hybrid, and Satellite, with a picture of the map in it, and 'map-type' says which is chosen. Standard hides the imagery, Hybrid draws it under the roads and names, and Satellite draws it alone. Choosing one sends 'helix-before-change' with its name, and 'change' once 'map-type' holds it. 'connectMap' does not draw a hidden layer, so a layer you write with 'hidden' starts turned off.  Markers, routes, areas, live positions, and points layers go inside the frame as child elements. */
   "helix-headless-map": DefineCustomElement<
     HelixHeadlessMap,
     HelixHeadlessMapVueProps,
@@ -14447,31 +15002,37 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessMapTerrainVueProps,
     HelixHeadlessMapTerrainVueEvents
   >;
-  /** A disclosure: a button that shows and hides a region of your own links. It does not use 'role="menu"' or 'menuitem', which are for application commands. Those roles take over the arrow keys, announce "menu" to someone looking for navigation, and put every link inside a role that is not a link. As a disclosure, middle clicks, modified clicks, and the status bar keep working. Use 'Menu' for a row of commands.  It renders no links. A router renders its own anchors and cannot render them inside this shadow root, so the panel is a slot for the lists and headings you write.  It opens on hover by default, and a press always opens it too. 'open-on' sets which. Hover is the default because in a navigation bar people expect to move along the row and see each section. */
+  /** A disclosure: a button that shows and hides a region of your own links. It does not use 'role="menu"' or 'menuitem', which are for application commands. Those roles take over the arrow keys, announce "menu" to someone looking for navigation, and put every link inside a role that is not a link. As a disclosure, middle clicks, modified clicks, and the status bar keep working. Use 'Menu' for a row of commands.  It renders no links. A router renders its own anchors and cannot render them inside this shadow root, so the panel is a slot for the lists and headings you write.  It opens on hover by default, and a press always opens it too. 'open-on' sets which. Hover is the default because in a navigation bar people expect to move along the row and see each section.  When one panel opens in place of another, each says which way the reader moved, as Radix's 'data-motion' does: the one opening is ':state(from-start)' or ':state(from-end)', by where the one closing sits in the bar, and the one closing is ':state(to-start)' or ':state(to-end)'. A stylesheet slides them on that. Put megamenus in a 'Navigation' with 'arrows' and the arrow keys move between their triggers. */
   "helix-headless-megamenu": DefineCustomElement<
     HelixHeadlessMegamenu,
     HelixHeadlessMegamenuVueProps,
     HelixHeadlessMegamenuVueEvents
   >;
-  /** One element covers three kinds of row, and what you give it decides which: - Content in the 'submenu' slot makes the row open a submenu page. - 'checked' makes the row a choice. - With neither, the row is a command.  The role follows the kind. A row with 'checked' is 'menuitemcheckbox' with 'aria-checked', and 'exclusive' makes it 'menuitemradio', for a set where only one can be on. A row that opens a page keeps 'menuitem' and sets 'aria-haspopup'.  Choosing a choice row checks or unchecks it before 'helix-select' is sent, so a listener reads the new 'checked'. An 'exclusive' row turns on and turns off the 'exclusive' rows next to it. Cancel 'helix-before-toggle' to keep a row as it is and set 'checked' yourself.  The menu sets whether the row's page is showing as a property, never as an attribute. An attribute written onto your element after it upgrades causes a hydration mismatch. */
+  /** One element covers three kinds of row, and what you give it decides which: - Content in the 'submenu' slot makes the row open a submenu page. - 'checked' makes the row a choice. - With neither, the row is a command.  The role follows the kind. A row with 'checked' is 'menuitemcheckbox' with 'aria-checked', and 'exclusive' makes it 'menuitemradio', for a set where only one can be on. A row that opens a page keeps 'menuitem' and sets 'aria-haspopup'.  Choosing a choice row checks or unchecks it before 'helix-select' is sent, so a listener reads the new 'checked'. An 'exclusive' row turns on and turns off the 'exclusive' rows next to it. Cancel 'helix-before-toggle' to keep a row as it is and set 'checked' yourself.  The menu sets whether the row's page is showing as a property, never as an attribute. An attribute written onto your element after it upgrades causes a hydration mismatch.  'shortcut' shows a row's keyboard shortcut after its label, drawn by 'Kbd' in the platform's glyphs, and gives the row 'aria-keyshortcuts'. It binds nothing: the shortcut is the page's to bind. Other trailing words, such as a count, go in the 'end' slot. */
   "helix-headless-menu-item": DefineCustomElement<
     HelixHeadlessMenuItem,
     HelixHeadlessMenuItemVueProps,
     HelixHeadlessMenuItemVueEvents
   >;
-  /** The trigger is slotted and stays your own element, as with the tooltip. The menu renders its surface in the top layer with the popover API, so an ancestor with 'overflow: hidden' does not clip it and it needs no 'z-index'.  Slot a 'helix-button' or 'helix-icon-button' as the trigger, and the menu tells it that it opens a menu and whether the menu is open. A plain '<button>' can only be told by writing attributes onto your markup, which the menu does not do, so give it 'aria-haspopup="menu"' and set its 'aria-expanded' from the 'toggle' event.  Submenus drill down. A submenu replaces the panel's content, and a back row returns to the previous page. One panel avoids the diagonal pointer path that side-by-side panels need, stays inside a narrow window, and works on touch screens, which have no hover.  The root holds which page is open, because only one page shows at a time. It sets this on items as a property, never as an attribute. An attribute written onto your element after it upgrades causes a hydration mismatch. */
+  /** The trigger is slotted and stays your own element, as with the tooltip. The menu renders its surface in the top layer with the popover API, so an ancestor with 'overflow: hidden' does not clip it and it needs no 'z-index'.  Slot a 'helix-button' or 'helix-icon-button' as the trigger, and the menu tells it that it opens a menu and whether the menu is open. A plain '<button>' can only be told by writing attributes onto your markup, which the menu does not do, so give it 'aria-haspopup="menu"' and set its 'aria-expanded' from the 'toggle' event.  Submenus drill down. A submenu replaces the panel's content, and a back row returns to the previous page. One panel avoids the diagonal pointer path that side-by-side panels need, stays inside a narrow window, and works on touch screens, which have no hover.  The root holds which page is open, because only one page shows at a time. It sets this on items as a property, never as an attribute. An attribute written onto your element after it upgrades causes a hydration mismatch.  Group rows under a heading with 'Menu.Section', which is a 'group' named by its heading. Between runs of rows, a '<helix-divider announced>' is a separator a screen reader announces.  With 'context', the trigger is an area and the menu is its context menu: a right-click, a long press, Shift+F10 or the menu key over the area opens it at the pointer, or at the area's corner from the keyboard, as Radix's context menu does. A press on the area does not open it, and closing it returns focus to where it was. */
   "helix-headless-menu": DefineCustomElement<
     HelixHeadlessMenu,
     HelixHeadlessMenuVueProps,
     HelixHeadlessMenuVueEvents
   >;
+  /** The rows inside it are the menu's rows: the arrow keys and typed letters move through them with the rest, and a set of 'exclusive' rows is still the run of them next to each other. The section is a 'group' named by its heading, as React Aria's menu section is, so a screen reader says which group a row is in as it arrives.  A section goes on the menu's first page. A submenu's page takes rows and dividers. */
+  "helix-headless-menu-section": DefineCustomElement<
+    HelixHeadlessMenuSection,
+    HelixHeadlessMenuSectionVueProps,
+    HelixHeadlessMenuSectionVueEvents
+  >;
   /** A meter shows a level within a range. Use 'Progress' to show how far along a task is. A progress bar starts empty and ends full, and full is always the good end. For a meter, which end is good depends on what is measured. There is no 'indeterminate', because a meter always has a value.  **Set 'low', 'high', and 'optimum'**, as defined in the HTML specification. 'low' and 'high' divide the range into a low band, a middle band, and a high band. 'optimum' sets the preferred band. The band next to it is fair, and the band two away is poor. */
   "helix-headless-meter": DefineCustomElement<
     HelixHeadlessMeter,
     HelixHeadlessMeterVueProps,
     HelixHeadlessMeterVueEvents
   >;
-  /** Renders a real '<nav>', the landmark that screen reader users jump to. Navigation is its own component, separate from 'AppHeader', so you can use it in a header, a footer, or a sidebar.  **It renders no links.** Bring your own, mark the current one with 'aria-current="page"', and style them with the 'data-navigation-item' recipe. A router renders its own anchors and cannot render them inside the component's shadow root.  The component moves a marker to the current item. It finds the current item by reading 'aria-current', so the attribute that screen readers announce also places the marker. Any value but 'false' counts, so a sidebar of sections on one page can mark the section in view with 'aria-current="location"'. Where several are marked, 'page' wins.  Set 'orientation="vertical"' to stack the destinations in a column, for a sidebar. */
+  /** Renders a real '<nav>', the landmark that screen reader users jump to. Navigation is its own component, separate from 'AppHeader', so you can use it in a header, a footer, or a sidebar.  **It renders no links.** Bring your own, mark the current one with 'aria-current="page"', and style them with the 'data-navigation-item' recipe. A router renders its own anchors and cannot render them inside the component's shadow root.  The component moves a marker to the current item. It finds the current item by reading 'aria-current', so the attribute that screen readers announce also places the marker. Any value but 'false' counts, so a sidebar of sections on one page can mark the section in view with 'aria-current="location"'. Where several are marked, 'page' wins.  Set 'orientation="vertical"' to stack the destinations in a column, for a sidebar.  Set 'arrows' and the arrow keys move focus between the destinations, as Radix's navigation menu does: left and right along a row, up and down a column, Home and End to the ends. A 'Megamenu' among them is reached at its trigger. Tab still stops at every link, since a navigation is a list of links and not a single control, and the keys across the other axis are left to the page and to an open panel. */
   "helix-headless-navigation": DefineCustomElement<
     HelixHeadlessNavigation,
     HelixHeadlessNavigationVueProps,
@@ -14489,7 +15050,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessNotificationVueProps,
     HelixHeadlessNotificationVueEvents
   >;
-  /** Notifications are slotted children. Each one is your own markup, with an avatar, a link, or a button in it. Feeds usually hold tens of items, so writing them out lets an item hold anything.  The list does not virtualize. Windowing needs the list to own the data, and here you own it, so N notifications are N elements. For a feed of thousands, use a data table with a custom cell.  Read state is reported to you. Marking read goes from the root to the item and from the item to you, so a canceled 'helix-read' changes nothing, and if you own 'read', nothing changes until you set it. 'unread' is derived from the items and written to an attribute, so a stylesheet and a badge can both use it without counting.  **The feed is one 'Tab' stop for its rows.** Each row takes focus itself and is read by its label. 'ArrowDown' and 'ArrowUp' move to the next and the previous row, 'Home' and 'End' to the first and the last, and 'PageDown' and 'PageUp' move a row on or back from anywhere inside one, as in the APG feed pattern. The controls inside a row stay in the 'Tab' order. Set 'total' when the feed holds one page of a longer list, and each row says its place in the whole of it. */
+  /** Notifications are slotted children. Each one is your own markup, with an avatar, a link, or a button in it. Feeds usually hold tens of items, so writing them out lets an item hold anything.  The list does not virtualize. Windowing needs the list to own the data, and here you own it, so N notifications are N elements. For a feed of thousands, use a data table with a custom cell.  Read state is reported to you. Marking read goes from the root to the item and from the item to you, so a canceled 'helix-read' changes nothing, and if you own 'read', nothing changes until you set it. 'unread' is derived from the items and written to an attribute, so a stylesheet and a badge can both use it without counting.  **The feed is one 'Tab' stop for its rows.** Each row takes focus itself and is read by its label. 'ArrowDown' and 'ArrowUp' move to the next and the previous row, 'Home' and 'End' to the first and the last, and 'PageDown' and 'PageUp' move a row on or back from anywhere inside one, as in the APG feed pattern. The controls inside a row stay in the 'Tab' order. Set 'total' when the feed holds one page of a longer list, and each row says its place in the whole of it.  **'load-more' adds a button after the list** that sends 'helix-load-more', for a feed that holds one page of a longer list. Append the next page, set 'loading' while it is on its way, and take 'load-more' off once there is nothing more. The button is hidden while the feed is loading. */
   "helix-headless-notifications": DefineCustomElement<
     HelixHeadlessNotifications,
     HelixHeadlessNotificationsVueProps,
@@ -14501,7 +15062,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessNumberInputVueProps,
     HelixHeadlessNumberInputVueEvents
   >;
-  /** Object Inspector shows a structured value, such as an API response, a config, or a raw record, as a read-only tree with each entry's type visible.  Pass the object to 'value', or name a '<script type="application/json">' by id with 'for', the same source 'VirtualList' and the charts read. JSON text works with server rendering and with React hydration, which skips object properties. 'value' wins when both are set.  The tree is one tab stop. Up and Down move between rows, Right opens a branch or moves into it, Left closes it or moves to its parent, and Home and End move to the first and last rows. Typing moves to the next row whose key starts with what was typed, and '*' opens every branch beside the active row. Focus stays on the tree, and 'aria-activedescendant' marks the active row. Each row carries its real level, position, and set size, including in a windowed tree.  A new 'value' keeps the branches a reader opened or closed, and the active row, where the new value still has them. A branch the old value did not have opens to 'default-depth'.  The copy button copies the active row, a branch as JSON and a string as its text. So do Command+C and Control+C while the tree has focus and no text is selected. The button sits beside the tree, because assistive technology cannot reliably reach a button inside a tree item.  'windowed' draws only the rows in view, for values with thousands of entries. The box needs a height for windowing to work. The styled tier sets one, and in the headless tier you set it yourself. */
+  /** Object Inspector shows a structured value, such as an API response, a config, or a raw record, as a read-only tree with each entry's type visible.  Pass the object to 'value', or name a '<script type="application/json">' by id with 'for', the same source 'VirtualList' and the charts read. JSON text works with server rendering and with React hydration, which skips object properties. 'value' wins when both are set.  The tree is one tab stop. Up and Down move between rows, Right opens a branch or moves into it, Left closes it or moves to its parent, and Home and End move to the first and last rows. Typing moves to the next row whose key starts with what was typed, and '*' opens every branch beside the active row. Focus stays on the tree, and 'aria-activedescendant' marks the active row. Each row carries its real level, position, and set size, including in a windowed tree.  'active' is the active row's path, written the way a JSON Pointer writes it: the empty string for the root and '/meta/tags/0' for an entry under it. Moving to another row sends 'helix-before-activate', which you can cancel, and then 'helix-activate', both with the path. Writing 'active' moves there and opens the branches around it, and sends nothing. 'expanded' holds the open branches by path, and writing it opens those and closes the rest. A row that closes around the active one hands it to the nearest open branch.  'filter' narrows the tree to the entries whose key or value holds the text, ignoring case, and the branches that lead to them, which it opens. A matched branch keeps everything under it. Each matched row carries 'row-match', and a screen reader hears how many entries matched from 'result-label' and 'results-label'. 'filterable' adds a field that sets it: typing sends 'helix-filter', which you can cancel, and then 'helix-filtered', and Down moves from the field to the tree.  A new 'value' keeps the branches a reader opened or closed, and the active row, where the new value still has them. A branch the old value did not have opens to 'default-depth'.  The copy button copies the active row, a branch as JSON and a string as its text. So do Command+C and Control+C while the tree has focus and no text is selected. The button sits beside the tree, because assistive technology cannot reliably reach a button inside a tree item.  'windowed' draws only the rows in view, for values with thousands of entries. The box needs a height for windowing to work. The styled tier sets one, and in the headless tier you set it yourself. */
   "helix-headless-object-inspector": DefineCustomElement<
     HelixHeadlessObjectInspector,
     HelixHeadlessObjectInspectorVueProps,
@@ -14519,7 +15080,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessOptionVueProps,
     HelixHeadlessOptionVueEvents
   >;
-  /** Outline is a table of contents for a document. 'Navigation' does the same job for a site.  The links are your own anchors. A router renders its own '<a>' and cannot render one inside the outline's shadow root, and the hrefs are fragments on the same page.  Write the anchors flat, with 'data-level' for their depth, or nested in lists, '<ul><li><a>'. A screen reader hears a nested list's levels; it hears 'data-level' as a flat run of links.  The current section is decided by the headings' positions. An 'IntersectionObserver' with a band near the top fails both ways: when headings are far apart, none is in the band and no section is marked, and when they are close together, several are in the band at once. */
+  /** Outline is a table of contents for a document. 'Navigation' does the same job for a site.  The links are your own anchors. A router renders its own '<a>' and cannot render one inside the outline's shadow root, and the hrefs are fragments on the same page.  Write the anchors flat, with 'data-level' for their depth, or nested in lists, '<ul><li><a>'. A screen reader hears the levels either way: the outline puts a flat run into lists inside list items of its own, nested by 'data-level', and leaves the links where they are. A link without 'data-level' is at the top level.  A heading slotted into 'heading' names the navigation, in place of 'label'.  The current section is decided by the headings' positions. An 'IntersectionObserver' with a band near the top fails both ways: when headings are far apart, none is in the band and no section is marked, and when they are close together, several are in the band at once. */
   "helix-headless-outline": DefineCustomElement<
     HelixHeadlessOutline,
     HelixHeadlessOutlineVueProps,
@@ -14531,7 +15092,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessPaginationVueProps,
     HelixHeadlessPaginationVueEvents
   >;
-  /** A separate element that you place beside 'Pagination', like 'Pagination.Summary', so you choose the direction and order of your footer.  It uses 'Select', so it matches a table's filter dropdowns in the same footer, both open and closed. The caret is 'Select''s, so it follows 'currentColor', and the label is a real '<label for>' pointing at the trigger's id.  The label sits on the same row as the select. 'Select''s host is a column, and an outer-tree rule overrides a ':host' rule, so the row layout needs no property on 'Select' and nothing added to your markup.  An empty 'sizes' renders nothing and does not fall back to the built-in list. 'Pagination' does the same with a single page, and both report it through 'ElementInternals.states'.  'value' is the current size, and 'default-value' is the size from the markup. Changing it dispatches 'helix-before-change', and then 'input' and 'change' once the size has moved, as a native '<select>' sends them together. Re-querying and returning to page one is up to you, because only you know whether the current position should be kept. */
+  /** A separate element that you place beside 'Pagination', like 'Pagination.Summary', so you choose the direction and order of your footer.  It uses 'Select', so it matches a table's filter dropdowns in the same footer, both open and closed. The caret is 'Select''s, so it follows 'currentColor', and the label is a real '<label for>' pointing at the trigger's id.  The label sits on the same row as the select. 'Select''s host is a column, and an outer-tree rule overrides a ':host' rule, so the row layout needs no property on 'Select' and nothing added to your markup.  An empty 'sizes' renders nothing and does not fall back to the built-in list. 'Pagination' does the same with a single page, and both report it through 'ElementInternals.states'.  'value' is the current size, and 'default-value' is the size from the markup. Changing it dispatches 'helix-before-change', and then 'input' and 'change' once the size has moved, as a native '<select>' sends them together. Re-querying and returning to page one is up to you, because only you know whether the current position should be kept.  It takes part in a form. Give it a 'name' and the size in force is submitted under that name, so a 'GET' form carries it in the address beside the page. A form reset returns it to 'default-value', and 'disabled', or a disabled '<fieldset>' around it, turns the select off. */
   "helix-headless-pagination-size": DefineCustomElement<
     HelixHeadlessPaginationSize,
     HelixHeadlessPaginationSizeVueProps,
@@ -14597,7 +15158,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessScatterChartVueProps,
     HelixHeadlessScatterChartVueEvents
   >;
-  /** Measures which edges have content past them and sets one custom state per edge. CSS cannot read scroll position, so a stylesheet cannot work this out on its own. The styled tier draws a fade on each edge that has a state.  Custom states keep an element that upgrades after a framework rendered it from adding markup the framework did not write. Select them with ':host(:state(more-block-end))'.  While the content overflows, the region gets a 'tabindex', so keyboard users can scroll it. When nothing overflows, it is not a tab stop.  It has 'role="region"' only when you set a 'label', because a screen reader announces an unnamed region as only "region". */
+  /** Measures which edges have content past them and sets one custom state per edge. CSS cannot read scroll position, so a stylesheet cannot work this out on its own. The styled tier draws a fade on each edge that has a state.  Custom states keep an element that upgrades after a framework rendered it from adding markup the framework did not write. Select them with ':host(:state(more-block-end))'.  While the content overflows, the region gets a 'tabindex', so keyboard users can scroll it. When nothing overflows, it is not a tab stop.  It has 'role="region"' only when you set a 'label', because a screen reader announces an unnamed region as only "region".  **'scrollbars' draws scrollbars of its own** in place of the browser's: a 'scrollbar' part for each axis that scrolls, a 'thumb' in each, and a 'corner' where the two meet. They are for the pointer. The thumb drags, and a press on the track moves the thumb to the press. The viewport stays the tab stop and the region a screen reader reads, and the scrollbars are hidden from screen readers. On the headless tier your stylesheet sizes and places them, hides the browser's own with 'scrollbar-width: none' on the viewport, and draws the thumb from the two custom properties written on each scrollbar. An axis whose 'overflow' is 'hidden' gets no scrollbar.  The viewport's 'scroll' and 'scrollend' are sent again from the host, which is the element you hold. In React, bind them with 'onScroll' and 'onScrollEnd'. */
   "helix-headless-scroll-area": DefineCustomElement<
     HelixHeadlessScrollArea,
     HelixHeadlessScrollAreaVueProps,
@@ -14663,13 +15224,13 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessStatVueProps,
     HelixHeadlessStatVueEvents
   >;
-  /** 'active' sets where the user is, and 'complete' stays on each step. Returning to stage one of three leaves stages one and two finished, so the root sets 'current' on the steps and never changes 'complete'.  'active' is optional. Without it, each step keeps its own 'current', so the sequence is correct in the server's markup, where the root cannot count its slotted children. */
+  /** 'active' sets where the user is, and 'complete' stays on each step. Returning to stage one of three leaves stages one and two finished, so the root sets 'current' on the steps and never changes 'complete'.  'active' is optional. Without it, each step keeps its own 'current', so the sequence is correct in the server's markup, where the root cannot count its slotted children.  '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. To check a stage before a reader leaves it, cancel 'helix-before-activate' while it is not valid. 'next()' and 'previous()' move one stage either way, under the same rules, for your own buttons. */
   "helix-headless-steps": DefineCustomElement<
     HelixHeadlessSteps,
     HelixHeadlessStepsVueProps,
     HelixHeadlessStepsVueEvents
   >;
-  /** Only the step's name is a button. The marker is 'aria-hidden' decoration, so it is outside the button. The name uses 'Button', so the hover wash, the focus ring, and the disabled style come from 'Button'.  Every step can be pressed and fires 'helix-select'. To stop the user from moving to a step, set 'disabled' on it.  The marker is a slot, and its fallback shows the step's state: a check for a finished stage, a target for the current stage, and an empty ring for a stage not reached yet. Only that one mark is rendered, so the accessibility tree has no hidden marks.  The half lines on each side of the mark are drawn on the step's '::before' and '::after' from properties the list sets, so the step renders no extra element for them. */
+  /** Only the step's name is a button. The marker is 'aria-hidden' decoration, so it is outside the button. The name uses 'Button', so the hover wash, the focus ring, and the disabled style come from 'Button'.  Every step can be pressed and fires 'helix-select'. To stop the user from moving to a step, set 'disabled' on it.  The marker is a slot, and its fallback shows the step's state: a check for a finished stage, a target for the current stage, and an empty ring for a stage not reached yet. Only that one mark is rendered, so the accessibility tree has no hidden marks.  The half lines on each side of the mark are drawn on the step's '::before' and '::after' from properties the list sets, so the step renders no extra element for them.  A finished stage says so in words: the name's button is described by 'complete-label', "Complete" unless you translate it, and a stage that becomes complete while the page is open says it once in a polite live region. The current stage's button carries 'aria-current="step"', and only the button, so the state is said once, on the control. */
   "helix-headless-step": DefineCustomElement<
     HelixHeadlessStep,
     HelixHeadlessStepVueProps,
@@ -14693,31 +15254,31 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessTableColumnVueProps,
     HelixHeadlessTableColumnVueEvents
   >;
-  /** Lays out the rows on a CSS grid, so every column lines up across rows and each row stays a real element that can be styled, hidden, or made interactive. A '<table>' layout aligns columns but limits almost everything else.  A grid of elements has no table structure for assistive technology, so the roles are set explicitly: 'table', 'row', 'cell', 'columnheader', and 'rowheader' for a 'header' cell in a row of values. Rows are 'display: contents', so their cells become items of the one grid.  A column with 'sortable' and a 'field' sorts the rows by the text of its cells, numbers by their value. Your markup is not reordered: the table draws the rows in the sorted order. 'helix-sort' asks first, so you can refuse it and reorder the rows yourself.  The CSS custom properties listed for this component are written by it and read by the stylesheet that draws it. Do not set them. Each holds a number the component computes and CSS cannot, so the stylesheet can draw the table without measuring anything. */
+  /** Lays out the rows on a CSS grid, so every column lines up across rows and each row stays a real element that can be styled, hidden, or made interactive. A '<table>' layout aligns columns but limits almost everything else.  A grid of elements has no table structure for assistive technology, so the roles are set explicitly: 'table', 'row', 'cell', 'columnheader', and 'rowheader' for a 'header' cell in a row of values. Rows are 'display: contents', so their cells become items of the one grid.  A column with 'sortable' and a 'field' sorts the rows by the text of its cells, numbers by their value. Your markup is not reordered: the table draws the rows in the sorted order. 'helix-sort' asks first, so you can refuse it and reorder the rows yourself.  The 'heading' slot names the table: slot a heading or a line of text into it, and the table is named by its words. An 'aria-label' or 'aria-labelledby' on the host wins over it.  'selectable' adds a column of checkboxes. Each row is known by its 'value', and 'selected' holds the chosen keys, comma separated, the same shape 'DataTable' uses. The checkbox in the heading selects every row. For a grid a reader moves through with the arrow keys, with typeahead and range selection, use 'DataTable'. To act on one row, put a link or a button in a cell.  The CSS custom properties listed for this component are written by it and read by the stylesheet that draws it. Do not set them. Each holds a number the component computes and CSS cannot, so the stylesheet can draw the table without measuring anything. */
   "helix-headless-table": DefineCustomElement<
     HelixHeadlessTable,
     HelixHeadlessTableVueProps,
     HelixHeadlessTableVueEvents
   >;
-  /** The row renders its cells straight through and lays out none of them, so a stylesheet can place them in the table's grid and every column lines up across rows. The row still exists as an element, so you can style it, hide it, or make it interactive. */
+  /** The row renders its cells straight through and lays out none of them, so a stylesheet can place them in the table's grid and every column lines up across rows. The row still exists as an element, so you can style it, hide it, or make it interactive.  In a 'selectable' table the row draws a checkbox cell before its own cells, and 'value' is the key the table's 'selected' lists it by. */
   "helix-headless-table-row": DefineCustomElement<
     HelixHeadlessTableRow,
     HelixHeadlessTableRowVueProps,
     HelixHeadlessTableRowVueEvents
   >;
-  /** An inactive panel is hidden and stays mounted. Anything typed into it is still there when the person comes back, and the content of every panel is in the server-rendered markup for crawlers, whichever tab is open. */
+  /** An inactive panel is hidden and stays mounted. Anything typed into it is still there when the person comes back, and the content of every panel is in the server-rendered markup for crawlers, whichever tab is open.  The host is the 'tabpanel' while its tab is selected, through 'ElementInternals', so the tab's 'aria-controls' can reach it from the tab's shadow root. The box inside takes the focus, for a panel with nothing focusable in it. */
   "helix-headless-tab-panel": DefineCustomElement<
     HelixHeadlessTabPanel,
     HelixHeadlessTabPanelVueProps,
     HelixHeadlessTabPanelVueEvents
   >;
-  /** Selection works through an event, the same as in the accordion and the tree. A tab dispatches 'helix-select', and the root pairs it with the panel of the same value. Nothing registers with anything, so tabs added later work with no extra setup.  The tab list is a single tab stop, and the arrow keys move between tabs through 'KeyboardNavigationController', the same as in the radio and toggle groups. Selection follows focus, which suits a small set where showing a panel is cheap. Set 'manual' when showing a panel is expensive, so focus can move without selecting. */
+  /** Selection works through an event, the same as in the accordion and the tree. A tab dispatches 'helix-select', and the root pairs it with the panel of the same value. Nothing registers with anything, so tabs added later work with no extra setup.  The tab list is a single tab stop, and the arrow keys move between tabs through 'KeyboardNavigationController', the same as in the radio and toggle groups. Selection follows focus, which suits a small set where showing a panel is cheap. Set 'manual' when showing a panel is expensive, so focus can move without selecting.  'orientation="vertical"' sets the tabs in a column beside the panels, and the tab list says 'aria-orientation="vertical"'. The arrow keys of both axes move between tabs either way.  A tab with an 'href' is a link, for tabs that are pages of a site. Pressing it follows the link, and the arrow keys move focus without choosing, so arrowing past a tab never leaves the page. Mark the tab of the page you are on with 'selected', or set 'active' to its value.  Each tab says which panel it controls through 'aria-controls', set as an element reference to the panel's host, where the engine has reflection. */
   "helix-headless-tabs": DefineCustomElement<
     HelixHeadlessTabs,
     HelixHeadlessTabsVueProps,
     HelixHeadlessTabsVueEvents
   >;
-  /** A tab is an element, because it manages selection and its own tab stop.  Its id and the id it controls both come from 'value', so the link between a tab and its panel works with server rendering. A generated id would differ between the server render and the client render, and 'aria-controls' would point at nothing. */
+  /** A tab is an element, because it manages selection and its own tab stop.  With an 'href', the tab is a link: 'role="tab"' on an '<a>', which a press, Enter and the browser's own link gestures follow. 'helix-select' is sent first, and canceling it keeps the browser from following, so a client-side router follows it instead. */
   "helix-headless-tab": DefineCustomElement<
     HelixHeadlessTab,
     HelixHeadlessTabVueProps,
@@ -14753,13 +15314,19 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessTimePickerVueProps,
     HelixHeadlessTimePickerVueEvents
   >;
+  /** Groups entries by date, such as "Today" and "Yesterday", in a timeline that holds many. The group is an entry of the timeline, and its entries are a list of their own, named by the heading. A screen reader lists the heading with the page's headings and hears how many entries each day holds.  The heading's level is 'heading-level', and 3 where it is not set.  Each group draws its own line, so the line stops at the last entry of one day and starts again at the first entry of the next. */
+  "helix-headless-timeline-group": DefineCustomElement<
+    HelixHeadlessTimelineGroup,
+    HelixHeadlessTimelineGroupVueProps,
+    HelixHeadlessTimelineGroupVueEvents
+  >;
   /** Given 'datetime', the label you write is wrapped in a '<time>' element, so a machine-readable value such as "2026-08-19" travels with a label such as "yesterday". Without 'datetime', the label is a '<span>'.  Each entry draws the connector line that arrives at it and hides it when it is the first entry, using ':host(:first-child)'. This needs no index, no counting parent, and no script. 'Steps' and 'Breadcrumbs' work the same way.  'tone' sets the kind of event and is the only thing that colors the mark. It uses the same values as 'Announcement'. */
   "helix-headless-timeline-item": DefineCustomElement<
     HelixHeadlessTimelineItem,
     HelixHeadlessTimelineItemVueProps,
     HelixHeadlessTimelineItemVueEvents
   >;
-  /** A timeline is a record of events that happened or are scheduled. Each entry carries a time, and no entry is current or complete. For a process you move through, with a current stage and 'active' and 'complete' states, use 'Steps'.  Each entry draws the connector line that arrives at it and hides it when it is first, using ':host(:first-child)'. This resolves at layout with no script, so the server markup is correct before anything runs.  The host has 'role="list"', because the entries are your elements in the light DOM. 'Steps' does the same.  A timeline runs down the page and has no horizontal layout. For stages laid out horizontally, use 'Steps', which is horizontal by default. */
+  /** A timeline is a record of events that happened or are scheduled. Each entry carries a time, and no entry is current or complete. For a process you move through, with a current stage and 'active' and 'complete' states, use 'Steps'.  Each entry draws the connector line that arrives at it and hides it when it is first, using ':host(:first-child)'. This resolves at layout with no script, so the server markup is correct before anything runs.  The host has 'role="list"', because the entries are your elements in the light DOM. 'Steps' does the same.  **Group entries by date with 'Timeline.Group'**, which puts a heading such as "Today" over its entries. The group is an entry of the timeline, and its entries are a list of their own named by the heading.  **The reading order is the order you write the entries in**, in every layout the styled tier draws: down the page, either side of a line down the middle, or across the page. Inside each entry the time is read before what happened. Write the entries in the order the events happened, oldest or newest first, and the layout only moves where they are drawn. */
   "helix-headless-timeline": DefineCustomElement<
     HelixHeadlessTimeline,
     HelixHeadlessTimelineVueProps,
@@ -14789,7 +15356,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessToggleVueProps,
     HelixHeadlessToggleVueEvents
   >;
-  /** A toolbar holds a mix of controls, such as buttons, toggles, and menus. A button group holds one kind, so the two are separate components.  The toolbar is one tab stop, and the arrow keys move between its controls, so three toolbars take three presses of Tab to pass. Any element the browser can focus counts as a control, including your own elements. A child that takes no focus, such as a divider, is skipped. A menu is reached at its trigger.  A nested composite, such as a toggle group, is one stop on the toolbar's axis: the toolbar's arrows move past it, and the arrows across the toolbar move inside it. A composite with a 'focusable' property, as Toggle Group has, gives up its own tab stop while the toolbar's is elsewhere, so Tab stops once in the toolbar. A composite without one keeps its own tab stop. */
+  /** A toolbar holds a mix of controls, such as buttons, toggles, and menus. A button group holds one kind, so the two are separate components.  The toolbar is one tab stop, and the arrow keys move between its controls, so three toolbars take three presses of Tab to pass. Any element the browser can focus counts as a control, including your own elements. A child that takes no focus, such as a divider, is skipped. A menu is reached at its trigger.  Controls inside a plain wrapper, such as a 'Button Group', are each a stop of the toolbar's own, as React Aria's toolbar flattens a group: the arrows walk through the group's buttons and on past it, and the group takes no tab stop of its own.  The arrows wrap from the last control to the first. Set 'stop-at-ends' to keep them at the ends, as Radix's 'loop' set to false does.  A nested composite, such as a toggle group, is one stop on the toolbar's axis: the toolbar's arrows move past it, and the arrows across the toolbar move inside it. A composite with a 'focusable' property, as Toggle Group has, gives up its own tab stop while the toolbar's is elsewhere, so Tab stops once in the toolbar. A composite without one keeps its own tab stop. */
   "helix-headless-toolbar": DefineCustomElement<
     HelixHeadlessToolbar,
     HelixHeadlessToolbarVueProps,
@@ -14813,13 +15380,13 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessTourStopVueProps,
     HelixHeadlessTourStopVueEvents
   >;
-  /** 'open' comes from 'MixinControllerOpen', the same state a disclosure holds, so you can respond to a branch opening and control the state yourself. The row renders 'aria-expanded'.  Each item is an element because it holds state: whether it is open, selected, and focused.  An item is a branch when something is slotted into 'children'. This is detected on the client, so server-rendered markup shows a leaf and the twisty appears on hydration.  **'href' makes the whole row a link**, rendered as an '<a>'. Enter, middle click, and the status bar then work anywhere on the row.  Pressing a branch, or Enter or Space on it, opens or closes it. A branch with a 'value' is chosen as well and sends 'helix-select', unless the tree has 'nesting="heading"', where a branch names the list under it. */
+  /** 'open' comes from 'MixinControllerOpen', the same state a disclosure holds, so you can respond to a branch opening and control the state yourself. The row renders 'aria-expanded'.  Each item is an element because it holds state: whether it is open, selected, and focused.  An item is a branch when something is slotted into 'children'. This is detected on the client, so server-rendered markup shows a leaf and the twisty appears on hydration.  **'href' makes the whole row a link**, rendered as an '<a>'. Enter, middle click, and the status bar then work anywhere on the row.  Pressing a branch, or Enter or Space on it, opens or closes it. A branch with a 'value' is chosen as well and sends 'helix-select', unless the tree has 'nesting="heading"', where a branch names the list under it.  A 'disabled' item is reached by the arrow keys and announced as unavailable, and a press, Enter or Space on it does nothing.  A 'lazy' item is a branch whose children you load when it opens: opening it sends 'helix-load', the row says it is busy, and the children you add appear in it. Remove 'lazy' once they are in. */
   "helix-headless-tree-item": DefineCustomElement<
     HelixHeadlessTreeItem,
     HelixHeadlessTreeItemVueProps,
     HelixHeadlessTreeItemVueEvents
   >;
-  /** The tree is a single tab stop, and arrow keys move focus between items, as the tree pattern requires, so Tab moves past a long sidebar in one press. The tree moves the tab stop to the focused item, so the browser's focus order stays intact.  Items are found with 'instanceof', never by tag name, so the headless tier does not depend on the styled one.  Typing a letter moves to the next visible item whose name starts with it, and '*' opens every branch beside the focused item. */
+  /** The tree is a single tab stop, and arrow keys move focus between items, as the tree pattern requires, so Tab moves past a long sidebar in one press. The tree moves the tab stop to the focused item, so the browser's focus order stays intact.  Items are found with 'instanceof', never by tag name, so the headless tier does not depend on the styled one.  Typing a letter moves to the next visible item whose name starts with it, and '*' opens every branch beside the focused item.  'selection-mode="multiple"' draws a check mark on every row and lets a reader check many, as Web Awesome's and Ark UI's checkbox trees do. Checking a branch checks every item under it, and a branch some of whose items are checked is partly checked. Space or a press on the mark checks the focused row, and Enter or a press on a branch's row opens it. 'active' then holds the checked values, comma separated, which 'values' also gives as a list, and the tree says 'aria-multiselectable'. */
   "helix-headless-tree": DefineCustomElement<
     HelixHeadlessTree,
     HelixHeadlessTreeVueProps,
@@ -14843,19 +15410,19 @@ export interface WcToolkitVueGlobalComponents {
     HelixHeadlessVideoPlaylistMenuVueProps,
     HelixHeadlessVideoPlaylistMenuVueEvents
   >;
-  /** **You slot the player**, so it keeps your appearance, extra controls, captions, and poster treatment. 'Sandbox' takes its preview and 'Menu' its trigger the same way.  **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 measurement. Markup also makes each entry a real button with its name inside.  **The playlist does not play media.** It sets 'src' on the player and tracks which entry is current. The current entry moves when:  - an entry is pressed, - the player dispatches 'helix-next' or 'helix-previous', or - the player reaches the end.  On 'ended' the playlist advances and the next clip starts playing, because the user already pressed play once. */
+  /** **You slot the player**, so it keeps your appearance, extra controls, captions, and poster treatment. 'Sandbox' takes its preview and 'Menu' its trigger the same way.  **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 measurement. Markup also makes each entry a real button with its name inside.  **The playlist does not play media.** It sets 'src' on the player and tracks which entry is current. The current entry moves when:  - an entry is pressed, - the player dispatches 'helix-next' or 'helix-previous', or - the player reaches the end.  On 'ended' the playlist advances and the next clip starts playing, because the user already pressed play once. 'repeat' decides what happens at the end: 'one' plays the same entry again, and 'all' goes from the last entry back to the first. Without it, the playlist stops on the last entry and sends 'helix-end'. 'shuffle' plays the entries in a random order, starting from the one that is current, and 'previous' retraces that order. */
   "helix-headless-video-playlist": DefineCustomElement<
     HelixHeadlessVideoPlaylist,
     HelixHeadlessVideoPlaylistVueProps,
     HelixHeadlessVideoPlaylistVueEvents
   >;
-  /** The picture is a native '<video>', so decoding, buffering, captions, Picture in Picture, AirPlay, and codecs come from the platform. The component replaces the control bar, because the native bar cannot be styled.  The scrubber and the volume are '<input type="range">' elements, so arrow keys, Home and End, touch targets, and screen reader announcements work as they do natively.  When you set 'controls', the browser's control bar is used, the Helix bar is not drawn, and the keys below are not bound, so a key press does not seek twice.  The keys match other players, and they are bound on the element only: - Space and 'k' play or pause. - The arrow keys seek and change the volume. - 'm' mutes. - 'f' toggles fullscreen.  '<source>' and '<track>' children are copied into the video. A media element selects resources from its own child nodes, and a slot is one node, so slotted sources would give the video no text tracks, no current source, and a 'readyState' of zero, and it would not play. They are copied so your light DOM stays intact, and are copied again whenever the slot changes. */
+  /** The picture is a native '<video>', so decoding, buffering, captions, Picture in Picture, AirPlay, and codecs come from the platform. The component replaces the control bar, because the native bar cannot be styled.  The scrubber and the volume are '<input type="range">' elements, so arrow keys, Home and End, touch targets, and screen reader announcements work as they do natively.  When you set 'controls', the browser's control bar is used, the Helix bar is not drawn, and the keys below are not bound, so a key press does not seek twice.  The keys match other players, and they are bound on the element only: - Space and 'k' play or pause. - The arrow keys seek and change the volume. - 'm' mutes. - 'f' toggles fullscreen.  '<source>' and '<track>' children are copied into the video. A media element selects resources from its own child nodes, and a slot is one node, so slotted sources would give the video no text tracks, no current source, and a 'readyState' of zero, and it would not play. They are copied so your light DOM stays intact, and are copied again whenever the slot changes.  The player sends every media event of its inner video under the same name, without bubbling, as a '<video>' sends it. Listen on the player as you would on a video: 'timeupdate', 'volumechange', 'loadedmetadata', 'error', and the rest. */
   "helix-headless-video": DefineCustomElement<
     HelixHeadlessVideo,
     HelixHeadlessVideoVueProps,
     HelixHeadlessVideoVueEvents
   >;
-  /** The items arrive as data:  - 'for' names a '<script type="application/json">' that holds an array of   objects. - A '<template>' child defines one row. Elements with 'data-field="name"' are   filled with that field of the item.  Both are markup. React hydration skips every property it would have to set imperatively, so an 'items' property would be lost, and light-DOM children would all exist before anything could window them. The JSON text is one node whatever the row count.  For assistive technology the list exposes the rendered window with 'aria-setsize'. Charts that use the same 'for="<id>"' shape render an accessible '<table>', and ten thousand rows in one is the cost this component avoids.  The list follows the source: editing the script's text, or replacing the script under the same id, draws the new rows. A row that stays in view keeps its element as the list scrolls, and the row holding focus stays drawn when it scrolls out, so a link or a button in a row keeps focus.  The viewport scrolls on this tier. It carries 'data-scroller', and 'core' ships '[data-scroller] { overflow: auto }' into every shadow root, so 'scrollTop' works with no stylesheet. You still need to set a block size. */
+  /** The items arrive as data, in one of two ways:  - 'items' takes an array. A framework sets it as a property, and React   hydration keeps it. - 'for' names a '<script type="application/json">' that holds an array, which   a server sends as markup.  Each item is drawn into a row in one of two ways:  - 'renderItem' is a function from an item and its index to the row's   content: a Lit template, a string, or a DOM node. - A '<template>' child defines one row. 'data-field="name"' fills an element   with the item's 'name' as text, and 'data-field-href="url"' writes the   item's 'url' into 'href', the same for any attribute. A field may be a path   of keys, such as 'author.name'.  Rows are your markup in the light DOM, so your stylesheet styles them.  **Keyboard.** The list is one tab stop. Up and Down move between items, Home and End go to the first and the last, and Page Up and Page Down move by a screen. An item that is not drawn is scrolled into view and focused, so a keyboard reaches the whole set. Tab moves on into the focused row's own links and buttons. When the row holding the tab stop scrolls away, the stop moves to the first row on screen.  Each row says its place in the whole set with 'aria-posinset' and 'aria-setsize', so a screen reader says "4,000 of 10,000". The row holding focus stays drawn when it scrolls out.  **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 fire again. 'scrollToIndex' takes a reader to an item.  The list follows its source. A new 'items' array, an edit to the script's text, or a script replaced under the same id draws the new rows. A row that stays in view keeps its element as the list scrolls.  The viewport scrolls on this tier. It carries 'data-scroller', and 'core' ships '[data-scroller] { overflow: auto }' into every shadow root, so 'scrollTop' works with no stylesheet. You still need to set a block size. */
   "helix-headless-virtual-list": DefineCustomElement<
     HelixHeadlessVirtualList,
     HelixHeadlessVirtualListVueProps,