@fusion.dev/helix 0.104.0 → 0.105.0

package/types/vue.d.ts

@@ -67,7 +67,12 @@ import type {
   HelixList,
   HelixListbox,
   HelixLoader,
+  HelixMapArea,
+  HelixMapMarker,
+  HelixMapPoints,
+  HelixMapPosition,
   HelixMap,
+  HelixMapRoute,
   HelixMegamenu,
   HelixMenuItem,
   HelixMenu,
@@ -179,6 +184,8 @@ import type {
   HelixShortcutEvent,
   HelixActivateEvent,
   HelixBeforeActivateEvent,
+  HelixMapPartChangeEvent,
+  HelixMapClusterEvent,
   HelixMapPanEvent,
   HelixMapZoomEvent,
   HelixReadEvent,
@@ -246,9 +253,9 @@ export type HelixAccordionItemHelixBeforeOpenElementEvent =
   HelixAccordionItemElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixAccordionItemVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixAccordionItem["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixAccordionItem["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -368,16 +375,16 @@ Styled and not headless, because a rung of a ladder is paint: the headless
 tier has no stylesheet to sit a band on. `tone` crosses because meaning
 survives having nothing to paint with, and it is the only axis that does. */
   separation?: (HelixAnnouncement["separation"]) | undefined;
-  /** Whether it offers a control to take it away. */
+  /** Whether the element shows a control that dismisses it. */
   dismissible?: (HelixAnnouncement["dismissible"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
 reachable only as `dismisslabel`, which nobody would guess and no linter
 would catch. */
   "dismiss-label"?: (HelixAnnouncement["dismissLabel"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
@@ -520,7 +527,7 @@ shadow root reads a table in that root rather than one in the document. A
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
   for?: (HelixAreaChart["for"]) | undefined;
-  /** The drawing's name, for a pointer resting on it.
+  /** The chart's name, which starts the chart's text summary.
 
 Absent falls back to the table's own caption, which is usually the right
 words and is already written. */
@@ -890,7 +897,7 @@ shadow root reads a table in that root rather than one in the document. A
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
   for?: (HelixBarChart["for"]) | undefined;
-  /** The drawing's name, for a pointer resting on it.
+  /** The chart's name, which starts the chart's text summary.
 
 Absent falls back to the table's own caption, which is usually the right
 words and is already written. */
@@ -1198,7 +1205,7 @@ synchronous call.
 clipboard, which is not this and is why it is declared there rather than
 inherited. */
   value?: (HelixButton["value"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -1207,7 +1214,7 @@ 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?: (HelixButton["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -1498,7 +1505,7 @@ Absent is no ruling, a resting value being an attribute's absence. */
 Framed is where it rests. Plain is for a board that fills a panel or an
 app's working area, where the container is already the frame. */
   separation?: (HelixCanvas["separation"]) | undefined;
-  /** Which of the controls this surface draws, as a list of what to keep.
+  /** Which controls to show, as a list of `pan`, `zoom`, and `fullscreen`, or `none`.
 
 **A list rather than a switch, because the overlap is not symmetric.** A
 surface a consumer brings often has zoom controls of its own and almost
@@ -1518,14 +1525,14 @@ board, which a reader drags and whose pad took a third of the frame. The
 stylesheet lays the cluster out by which buttons are in it rather than by
 this attribute, so the two defaults need no rule each. */
   controls?: (HelixCanvas["controls"]) | undefined;
-  /** What the group of controls is called, for a reader who meets it.
+  /** The name of the group of controls, read by screen readers.
 
 Absent is the family's own name for it, "Map controls" or "Board
 controls", which names what the controls drive rather than the
 mechanism. Written here to say it in another language, which every other
 string this surface speaks already allowed and this one did not. */
   "controls-label"?: (HelixCanvas["controlsLabel"]) | undefined;
-  /** What the group of controls is called, for a reader who meets it.
+  /** The name of the group of controls, read by screen readers.
 
 Absent is the family's own name for it, "Map controls" or "Board
 controls", which names what the controls drive rather than the
@@ -1556,25 +1563,25 @@ them without a consumer writing a second rule. Absent is the top end, a
 resting value being an attribute's absence: a default that reflected
 would write an attribute onto every host that no server sent. */
   controlsPlacement?: (HelixCanvas["controlsPlacement"]) | undefined;
-  /** What the control that fills the screen is called. */
+  /** The fullscreen button's label. */
   "fullscreen-label"?: (HelixCanvas["fullscreenLabel"]) | undefined;
-  /** What the control that fills the screen is called. */
+  /** The fullscreen button's label. */
   fullscreenLabel?: (HelixCanvas["fullscreenLabel"]) | undefined;
-  /** How long the reader may be still before the chrome hides, in milliseconds.
+  /** How long, in milliseconds, before the header and footer hide when the user is inactive. `0` keeps them visible.
 
 Zero keeps it up, which is the default: these controls are how a keyboard
 reader operates the surface, and chrome that hid itself by default would
 be the component undoing its own argument. Set it for a display nobody
 drives. */
   "idle-delay"?: (HelixCanvas["idleDelay"] | `${number}`) | undefined;
-  /** How long the reader may be still before the chrome hides, in milliseconds.
+  /** How long, in milliseconds, before the header and footer hide when the user is inactive. `0` keeps them visible.
 
 Zero keeps it up, which is the default: these controls are how a keyboard
 reader operates the surface, and chrome that hid itself by default would
 be the component undoing its own argument. Set it for a display nobody
 drives. */
   idleDelay?: (HelixCanvas["idleDelay"]) | undefined;
-  /** What the control that pans down is called.
+  /** The pan down button's label.
 
 **A label for each way rather than one with the way filled in**, which is
 what this was: `Pan {way}` filled in with `left`, so a page that said it
@@ -1582,7 +1589,7 @@ in French read out "Déplacer left". The word for a direction is as much
 the translator's as the word for panning, and a language can put it
 anywhere in the phrase. */
   "pan-down-label"?: (HelixCanvas["panDownLabel"]) | undefined;
-  /** What the control that pans down is called.
+  /** The pan down button's label.
 
 **A label for each way rather than one with the way filled in**, which is
 what this was: `Pan {way}` filled in with `left`, so a page that said it
@@ -1590,37 +1597,37 @@ in French read out "Déplacer left". The word for a direction is as much
 the translator's as the word for panning, and a language can put it
 anywhere in the phrase. */
   panDownLabel?: (HelixCanvas["panDownLabel"]) | undefined;
-  /** What the control that pans left is called, on screen. */
+  /** The pan left button's label. */
   "pan-left-label"?: (HelixCanvas["panLeftLabel"]) | undefined;
-  /** What the control that pans left is called, on screen. */
+  /** The pan left button's label. */
   panLeftLabel?: (HelixCanvas["panLeftLabel"]) | undefined;
-  /** What the control that pans right is called, on screen. */
+  /** The pan right button's label. */
   "pan-right-label"?: (HelixCanvas["panRightLabel"]) | undefined;
-  /** What the control that pans right is called, on screen. */
+  /** The pan right button's label. */
   panRightLabel?: (HelixCanvas["panRightLabel"]) | undefined;
-  /** How far one press moves the view, as a fraction of what is on screen.
+  /** How far one press pans the view, as a fraction of its size.
 
 A fraction rather than a distance, because this surface does not know the
 scale of what is inside it: a quarter of the viewport is the same gesture
 at any zoom, and a consumer who wants their own units multiplies by them. */
   "pan-step"?: (HelixCanvas["panStep"] | `${number}`) | undefined;
-  /** How far one press moves the view, as a fraction of what is on screen.
+  /** How far one press pans the view, as a fraction of its size.
 
 A fraction rather than a distance, because this surface does not know the
 scale of what is inside it: a quarter of the viewport is the same gesture
 at any zoom, and a consumer who wants their own units multiplies by them. */
   panStep?: (HelixCanvas["panStep"]) | undefined;
-  /** What the control that pans up is called. */
+  /** The pan up button's label. */
   "pan-up-label"?: (HelixCanvas["panUpLabel"]) | undefined;
-  /** What the control that pans up is called. */
+  /** The pan up button's label. */
   panUpLabel?: (HelixCanvas["panUpLabel"]) | undefined;
-  /** What the control that zooms in is called. */
+  /** The zoom in button's label. */
   "zoom-in-label"?: (HelixCanvas["zoomInLabel"]) | undefined;
-  /** What the control that zooms in is called. */
+  /** The zoom in button's label. */
   zoomInLabel?: (HelixCanvas["zoomInLabel"]) | undefined;
-  /** What the control that zooms out is called. */
+  /** The zoom out button's label. */
   "zoom-out-label"?: (HelixCanvas["zoomOutLabel"]) | undefined;
-  /** What the control that zooms out is called. */
+  /** The zoom out button's label. */
   zoomOutLabel?: (HelixCanvas["zoomOutLabel"]) | undefined;
   /** How a card says where its connections come from, with `{cards}`. */
   "comes-from-label"?: (HelixCanvas["comesFromLabel"]) | undefined;
@@ -2421,19 +2428,19 @@ export type HelixChatHelixSendElementEvent =
   HelixChatElementEvent<HelixSendEvent>;
 
 export type HelixChatVueProps = {
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixChat["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixChat["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixChat["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixChat["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixChat["loadingText"]) | undefined;
   /** Whether to open pinned, where nothing declared it.
 
@@ -2517,16 +2524,17 @@ export type HelixCheckboxGroupHelixBeforeChangeElementEvent =
 export type HelixCheckboxGroupVueProps = {
   /** Which way the boxes run. */
   orientation?: (HelixCheckboxGroup["orientation"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixCheckboxGroup["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixCheckboxGroup["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixCheckboxGroup["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixCheckboxGroup["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -2535,8 +2543,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixCheckboxGroup["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -2547,7 +2554,7 @@ the field and does not reach that one. */
   valueMissingMessage?: (HelixCheckboxGroup["valueMissingMessage"]) | undefined;
   /** The checked values, comma separated. */
   value?: (HelixCheckboxGroup["value"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -2556,7 +2563,7 @@ 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?: (HelixCheckboxGroup["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -2625,20 +2632,21 @@ Not reflected: the attribute is the consumer's input and stays as they
 wrote it, and `:state(checked)` carries the resolved state for
 stylesheets. */
   checked?: (HelixCheckbox["checked"]) | undefined;
-  /** Whether the markup declared it checked, which is where a reset returns to. */
+  /** Whether the control starts checked. A form reset returns it to this state. */
   "default-checked"?: (HelixCheckbox["defaultChecked"]) | undefined;
-  /** Whether the markup declared it checked, which is where a reset returns to. */
+  /** Whether the control starts checked. A form reset returns it to this state. */
   defaultChecked?: (HelixCheckbox["defaultChecked"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixCheckbox["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixCheckbox["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixCheckbox["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixCheckbox["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -2647,8 +2655,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixCheckbox["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -2663,7 +2670,7 @@ Presentation only. It never submits, and the first change resolves it. */
   indeterminate?: (HelixCheckbox["indeterminate"]) | undefined;
   /** Value submitted when the box is checked. */
   value?: (HelixCheckbox["value"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -2672,7 +2679,7 @@ 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?: (HelixCheckbox["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -2781,25 +2788,25 @@ export type HelixColorInputHelixBeforeOpenElementEvent =
   HelixColorInputElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixColorInputVueProps = {
-  /** What a reader is told when the field holds something the picker cannot
-read: a date that is not one, a time, a color.
+  /** The message shown when the field holds text the picker cannot read as a
+date, a time, or a color.
 
 **Every sentence a control raises in the browser's bubble is a
 property**, named for the validity flag it reports, so a form in another
 language speaks it. Absent is the family's own sentence, in English,
 which says what the value should look like. */
   "bad-input-message"?: (HelixColorInput["badInputMessage"]) | undefined;
-  /** What a reader is told when the field holds something the picker cannot
-read: a date that is not one, a time, a color.
+  /** The message shown when the field holds text the picker cannot read as a
+date, a time, or a color.
 
 **Every sentence a control raises in the browser's bubble is a
 property**, named for the validity flag it reports, so a form in another
 language speaks it. Absent is the family's own sentence, in English,
 which says what the value should look like. */
   badInputMessage?: (HelixColorInput["badInputMessage"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixColorInput["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixColorInput["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -2814,27 +2821,28 @@ hydration, or diffed by a framework, it comes back holding whatever the
 last reader did rather than what the author wrote. `:state(open)` carries
 the resolved state for stylesheets, which is what the mirror is for. */
   open?: (HelixColorInput["open"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixColorInput["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixColorInput["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixColorInput["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixColorInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixColorInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixColorInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixColorInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -2843,8 +2851,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixColorInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -2900,7 +2907,7 @@ The trade is real and is the reason this is not the default: a swatch cannot
 be read or pasted into without opening the panel, which is worse for a form
 where the color is the answer rather than a setting. */
   variant?: (HelixColorInput["variant"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -2909,7 +2916,7 @@ 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?: (HelixColorInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -2962,11 +2969,11 @@ export type HelixColorPickerHelixSampleStartElementEvent =
   HelixColorPickerElementEvent<HelixSampleStartEvent>;
 
 export type HelixColorPickerVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixColorPicker["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixColorPicker["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
@@ -3169,7 +3176,7 @@ speaks it. Absent is the control's own sentence, in English. */
 named for the validity flag it reports, so a form in another language
 speaks it. Absent is the control's own sentence, in English. */
   valueMissingMessage?: (HelixColorPicker["valueMissingMessage"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -3178,7 +3185,7 @@ 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?: (HelixColorPicker["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -3231,9 +3238,9 @@ export type HelixComboboxHelixFilterElementEvent =
   HelixComboboxElementEvent<HelixFilterEvent>;
 
 export type HelixComboboxVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixCombobox["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixCombobox["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -3248,41 +3255,44 @@ hydration, or diffed by a framework, it comes back holding whatever the
 last reader did rather than what the author wrote. `:state(open)` carries
 the resolved state for stylesheets, which is what the mirror is for. */
   open?: (HelixCombobox["open"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   "collapse-label"?: (HelixCombobox["collapseLabel"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   collapseLabel?: (HelixCombobox["collapseLabel"]) | undefined;
-  /** Whether the count is a control that shows the rest. */
+  /** Whether the count is a button that shows the hidden tokens. */
   expandable?: (HelixCombobox["expandable"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   "expand-label"?: (HelixCombobox["expandLabel"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   expandLabel?: (HelixCombobox["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
   "max-tags"?: (HelixCombobox["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixCombobox["maxTags"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixCombobox["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixCombobox["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixCombobox["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixCombobox["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixCombobox["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixCombobox["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixCombobox["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -3291,8 +3301,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixCombobox["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -3373,7 +3382,7 @@ element already sets on the input it renders, and two things of one name
 meaning different things on the same control is a question a consumer
 should not have to ask. */
   suggest?: (HelixCombobox["suggest"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -3382,7 +3391,7 @@ 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?: (HelixCombobox["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -3440,9 +3449,9 @@ export type HelixCommandHelixSelectElementEvent =
   HelixCommandElementEvent<HelixSelectEvent>;
 
 export type HelixCommandVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixCommand["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixCommand["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -3610,7 +3619,7 @@ native submitter would have given it, which is the point. */
   formTarget?: (HelixCopyButton["formTarget"]) | undefined;
   /** What activating the button does to its form. */
   type?: (HelixCopyButton["type"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -3619,7 +3628,7 @@ 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?: (HelixCopyButton["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -3709,19 +3718,19 @@ export type HelixDataTableHelixSortElementEvent =
   HelixDataTableElementEvent<HelixSortEvent>;
 
 export type HelixDataTableVueProps = {
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixDataTable["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixDataTable["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixDataTable["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixDataTable["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixDataTable["loadingText"]) | undefined;
   /** Query to open with, where nothing declared one. */
   "default-filter"?: (HelixDataTable["defaultFilter"]) | undefined;
@@ -3925,7 +3934,7 @@ export type HelixDateInputHelixBeforeOpenElementEvent =
   HelixDateInputElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixDateInputVueProps = {
-  /** Whether the control refuses changes while still submitting its value.
+  /** Whether the value is locked. A read-only control still submits its value.
 
 **Enforced by refusing every request in one place**, which is the seam this
 component already has: `requestValue` is what every path here comes through,
@@ -3937,7 +3946,7 @@ submits nothing and leaves the tab order, and a read-only one submits its
 value and stays reachable, which is what a form showing a value somebody
 else set needs. */
   readonly?: (HelixDateInput["readOnly"]) | undefined;
-  /** Whether the control refuses changes while still submitting its value.
+  /** Whether the value is locked. A read-only control still submits its value.
 
 **Enforced by refusing every request in one place**, which is the seam this
 component already has: `requestValue` is what every path here comes through,
@@ -3949,25 +3958,25 @@ submits nothing and leaves the tab order, and a read-only one submits its
 value and stays reachable, which is what a form showing a value somebody
 else set needs. */
   readOnly?: (HelixDateInput["readOnly"]) | undefined;
-  /** What a reader is told when the field holds something the picker cannot
-read: a date that is not one, a time, a color.
+  /** The message shown when the field holds text the picker cannot read as a
+date, a time, or a color.
 
 **Every sentence a control raises in the browser's bubble is a
 property**, named for the validity flag it reports, so a form in another
 language speaks it. Absent is the family's own sentence, in English,
 which says what the value should look like. */
   "bad-input-message"?: (HelixDateInput["badInputMessage"]) | undefined;
-  /** What a reader is told when the field holds something the picker cannot
-read: a date that is not one, a time, a color.
+  /** The message shown when the field holds text the picker cannot read as a
+date, a time, or a color.
 
 **Every sentence a control raises in the browser's bubble is a
 property**, named for the validity flag it reports, so a form in another
 language speaks it. Absent is the family's own sentence, in English,
 which says what the value should look like. */
   badInputMessage?: (HelixDateInput["badInputMessage"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixDateInput["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixDateInput["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -3982,41 +3991,44 @@ hydration, or diffed by a framework, it comes back holding whatever the
 last reader did rather than what the author wrote. `:state(open)` carries
 the resolved state for stylesheets, which is what the mirror is for. */
   open?: (HelixDateInput["open"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   "collapse-label"?: (HelixDateInput["collapseLabel"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   collapseLabel?: (HelixDateInput["collapseLabel"]) | undefined;
-  /** Whether the count is a control that shows the rest. */
+  /** Whether the count is a button that shows the hidden tokens. */
   expandable?: (HelixDateInput["expandable"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   "expand-label"?: (HelixDateInput["expandLabel"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   expandLabel?: (HelixDateInput["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
   "max-tags"?: (HelixDateInput["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixDateInput["maxTags"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixDateInput["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixDateInput["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixDateInput["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixDateInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixDateInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixDateInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixDateInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -4025,8 +4037,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixDateInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -4165,7 +4176,7 @@ platform's base. */
   "trigger-label"?: (HelixDateInput["triggerLabel"]) | undefined;
   /** Accessible name for the control that opens the calendar. */
   triggerLabel?: (HelixDateInput["triggerLabel"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -4174,7 +4185,7 @@ 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?: (HelixDateInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -4235,11 +4246,11 @@ export type HelixDatePickerHelixNavigateElementEvent =
   HelixDatePickerElementEvent<HelixNavigateEvent>;
 
 export type HelixDatePickerVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixDatePicker["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixDatePicker["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
@@ -4356,7 +4367,7 @@ date including the one already chosen. */
   "value-missing-message"?: (HelixDatePicker["valueMissingMessage"]) | undefined;
   /** What a reader is told when a date is required and none is chosen. */
   valueMissingMessage?: (HelixDatePicker["valueMissingMessage"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -4365,7 +4376,7 @@ 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?: (HelixDatePicker["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -4531,9 +4542,9 @@ write the same two arrangements, and a fourth way to get one of them wrong.
 Unset is `start` and stays unset, so a reflected default cannot appear on a
 host whose server output never had it. */
   textAlign?: (HelixDialog["textAlign"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixDialog["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixDialog["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -4677,7 +4688,7 @@ shadow root reads a table in that root rather than one in the document. A
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
   for?: (HelixDonutChart["for"]) | undefined;
-  /** The drawing's name, for a pointer resting on it.
+  /** The chart's name, which starts the chart's text summary.
 
 Absent falls back to the table's own caption, which is usually the right
 words and is already written. */
@@ -4759,9 +4770,9 @@ content is only readable because it has a ground; dropping it makes an
 unreadable drawer rather than a lighter one. `frosted` and `glass` are the
 two honest points here. */
   material?: (HelixDrawer["material"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixDrawer["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixDrawer["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -4898,19 +4909,19 @@ export type HelixDrilldownHelixSelectElementEvent =
   HelixDrilldownElementEvent<HelixSelectEvent>;
 
 export type HelixDrilldownVueProps = {
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixDrilldown["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixDrilldown["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixDrilldown["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixDrilldown["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixDrilldown["loadingText"]) | undefined;
   /** Accessible name for the region. */
   label?: (HelixDrilldown["label"]) | undefined;
@@ -4952,16 +4963,17 @@ export type HelixFileInputHelixBeforeChangeElementEvent =
   HelixFileInputElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixFileInputVueProps = {
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixFileInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixFileInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixFileInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixFileInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -4970,8 +4982,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixFileInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -5006,7 +5017,7 @@ removes rather than as "Remove" said once per file. A label with no
   "trigger-label"?: (HelixFileInput["triggerLabel"]) | undefined;
   /** What the trigger reads, where nothing is slotted into it. */
   triggerLabel?: (HelixFileInput["triggerLabel"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -5015,7 +5026,7 @@ 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?: (HelixFileInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -5053,16 +5064,16 @@ export type HelixFilterChipHelixDismissElementEvent =
   HelixFilterChipElementEvent<HelixDismissEvent>;
 
 export type HelixFilterChipVueProps = {
-  /** Whether it offers a control to take it away. */
+  /** Whether the element shows a control that dismisses it. */
   dismissible?: (HelixFilterChip["dismissible"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
 reachable only as `dismisslabel`, which nobody would guess and no linter
 would catch. */
   "dismiss-label"?: (HelixFilterChip["dismissLabel"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
@@ -5233,9 +5244,9 @@ export type HelixFilterInputHelixSelectElementEvent =
   HelixFilterInputElementEvent<HelixSelectEvent>;
 
 export type HelixFilterInputVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixFilterInput["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixFilterInput["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -5250,41 +5261,44 @@ hydration, or diffed by a framework, it comes back holding whatever the
 last reader did rather than what the author wrote. `:state(open)` carries
 the resolved state for stylesheets, which is what the mirror is for. */
   open?: (HelixFilterInput["open"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   "collapse-label"?: (HelixFilterInput["collapseLabel"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   collapseLabel?: (HelixFilterInput["collapseLabel"]) | undefined;
-  /** Whether the count is a control that shows the rest. */
+  /** Whether the count is a button that shows the hidden tokens. */
   expandable?: (HelixFilterInput["expandable"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   "expand-label"?: (HelixFilterInput["expandLabel"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   expandLabel?: (HelixFilterInput["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
   "max-tags"?: (HelixFilterInput["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixFilterInput["maxTags"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixFilterInput["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixFilterInput["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixFilterInput["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixFilterInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixFilterInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixFilterInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixFilterInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -5293,8 +5307,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixFilterInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -5318,7 +5331,7 @@ them. */
 
 Not a label: it goes when typing starts. */
   placeholder?: (HelixFilterInput["placeholder"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -5327,7 +5340,7 @@ 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?: (HelixFilterInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -5541,7 +5554,7 @@ shadow root reads a table in that root rather than one in the document. A
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
   for?: (HelixHeatmap["for"]) | undefined;
-  /** The drawing's name, for a pointer resting on it.
+  /** The chart's name, which starts the chart's text summary.
 
 Absent falls back to the table's own caption, which is usually the right
 words and is already written. */
@@ -5762,7 +5775,7 @@ synchronous call.
 clipboard, which is not this and is why it is declared there rather than
 inherited. */
   value?: (HelixIconButton["value"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -5771,7 +5784,7 @@ 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?: (HelixIconButton["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -5967,27 +5980,28 @@ export type HelixInputHelixBeforeChangeElementEvent =
   HelixInputElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixInputVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixInput["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixInput["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixInput["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -5996,8 +6010,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -6087,7 +6100,7 @@ Nothing reads it from the attribute either. The real `<input>` inside takes
 it as a property binding, which is what makes the keyboard and the
 validation follow. */
   type?: (HelixInput["type"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -6096,7 +6109,7 @@ 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?: (HelixInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -6296,7 +6309,7 @@ export type HelixLightboxHelixBeforeOpenElementEvent =
   HelixLightboxElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixLightboxVueProps = {
-  /** Which item is current, by its `value`.
+  /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
 different question from which one is chosen.
@@ -6305,17 +6318,17 @@ Writing always applies, so `<helix-tabs active="one">` starts on that
 tab, and `default-active` is how markup says where to start without
 naming the current one. */
   active?: (HelixLightbox["active"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   "default-active"?: (HelixLightbox["defaultActive"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   defaultActive?: (HelixLightbox["defaultActive"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixLightbox["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixLightbox["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -6427,7 +6440,7 @@ shadow root reads a table in that root rather than one in the document. A
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
   for?: (HelixLineChart["for"]) | undefined;
-  /** The drawing's name, for a pointer resting on it.
+  /** The chart's name, which starts the chart's text summary.
 
 Absent falls back to the table's own caption, which is usually the right
 words and is already written. */
@@ -6616,41 +6629,42 @@ export type HelixListboxHelixFilterElementEvent =
   HelixListboxElementEvent<HelixFilterEvent>;
 
 export type HelixListboxVueProps = {
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixListbox["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixListbox["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixListbox["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixListbox["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixListbox["loadingText"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixListbox["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixListbox["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixListbox["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixListbox["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixListbox["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixListbox["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixListbox["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -6659,8 +6673,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixListbox["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -6700,7 +6713,7 @@ own search boxes would be three copies of one field. */
   filterLabel?: (HelixListbox["filterLabel"]) | undefined;
   /** Whether more than one option can be the answer. */
   multiple?: (HelixListbox["multiple"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -6709,7 +6722,7 @@ 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?: (HelixListbox["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -6769,17 +6782,199 @@ around a logo reads as chrome bolted to the brand. */
 
 export type HelixLoaderVueEvents = {};
 
+/** `HelixMapArea` component event */
+export type HelixMapAreaElementEvent<E = Event> = TypedEvent<HelixMapArea, E>;
+/** `helix-map-part-change` event type */
+export type HelixMapAreaHelixMapPartChangeElementEvent =
+  HelixMapAreaElementEvent<HelixMapPartChangeEvent>;
+
+export type HelixMapAreaVueProps = {
+  /** The area's color. Uses your primary color unless set. */
+  tone?: (HelixMapArea["tone"]) | undefined;
+  /** More about the area. Read after its label in the frame's list. */
+  description?: (HelixMapArea["description"]) | undefined;
+  /** The area's name, used in the frame's list. */
+  label?: (HelixMapArea["label"]) | undefined;
+  /** The corners of the shape, in order. The last point connects back to the
+first. */
+  points?: (HelixMapArea["points"]) | undefined;
+};
+
+export type HelixMapAreaVueEvents = {
+  /** The area's points, name, or color changed. Used by `connectMap`; pages do not need to listen for it. */
+  "helix-map-part-change": HelixMapAreaHelixMapPartChangeElementEvent;
+};
+
+/** `HelixMapMarker` component event */
+export type HelixMapMarkerElementEvent<E = Event> = TypedEvent<
+  HelixMapMarker,
+  E
+>;
+/** `helix-map-cluster` event type */
+export type HelixMapMarkerHelixMapClusterElementEvent =
+  HelixMapMarkerElementEvent<HelixMapClusterEvent>;
+/** `helix-map-part-change` event type */
+export type HelixMapMarkerHelixMapPartChangeElementEvent =
+  HelixMapMarkerElementEvent<HelixMapPartChangeEvent>;
+
+export type HelixMapMarkerVueProps = {
+  /** The background of the name. Leave unset for solid. `glass` shows the map
+through a blur, `frosted` blurs more, and `transparent` has no background. */
+  material?: (HelixMapMarker["material"]) | undefined;
+  /** How the point stands out from the map. Leave unset for a surface-colored
+edge and a small shadow. `outlined` has the edge only, `elevated` a larger
+shadow, `filled` a soft halo in the marker's color, and `plain` no edge or
+shadow. */
+  separation?: (HelixMapMarker["separation"]) | undefined;
+  /** The point's shape. A circle unless set. Use shapes with tones to tell
+kinds of places apart. `pin` places the tip of a pin on the location, for
+a destination. */
+  shape?: (HelixMapMarker["shape"]) | undefined;
+  /** The point's color. Uses your primary color unless set. */
+  tone?: (HelixMapMarker["tone"]) | undefined;
+  /** The place's name. Shown next to the marker and read by screen readers. */
+  label?: (HelixMapMarker["label"]) | undefined;
+  /** Latitude, in degrees. A marker without both `lat` and `lng` is not shown. */
+  lat?: (HelixMapMarker["lat"]) | undefined;
+  /** Longitude, in degrees. */
+  lng?: (HelixMapMarker["lng"]) | undefined;
+  /** The value `helix-activate` reports. Defaults to the label. */
+  name?: (HelixMapMarker["name"]) | undefined;
+  /** Marks the place as passed, such as a stop already visited. The marker is
+drawn muted, and its name is followed by `passed-label`. */
+  passed?: (HelixMapMarker["passed"]) | undefined;
+  /** The word added after a passed place's name. Defaults to "passed". */
+  "passed-label"?: (HelixMapMarker["passedLabel"]) | undefined;
+  /** The word added after a passed place's name. Defaults to "passed". */
+  passedLabel?: (HelixMapMarker["passedLabel"]) | undefined;
+};
+
+export type HelixMapMarkerVueEvents = {
+  /** This marker shows a cluster and was pressed. `connectMap` zooms in to its places. */
+  "helix-map-cluster": HelixMapMarkerHelixMapClusterElementEvent;
+  /** The marker moved or was renamed. Used by `connectMap`; pages do not need to listen for it. */
+  "helix-map-part-change": HelixMapMarkerHelixMapPartChangeElementEvent;
+};
+
+/** `HelixMapPoints` component event */
+export type HelixMapPointsElementEvent<E = Event> = TypedEvent<
+  HelixMapPoints,
+  E
+>;
+/** `helix-activate` event type */
+export type HelixMapPointsHelixActivateElementEvent =
+  HelixMapPointsElementEvent<HelixActivateEvent>;
+/** `helix-map-cluster` event type */
+export type HelixMapPointsHelixMapClusterElementEvent =
+  HelixMapPointsElementEvent<HelixMapClusterEvent>;
+/** `helix-map-part-change` event type */
+export type HelixMapPointsHelixMapPartChangeElementEvent =
+  HelixMapPointsElementEvent<HelixMapPartChangeEvent>;
+
+export type HelixMapPointsVueProps = {
+  /** The points' color. Uses your primary color unless set. */
+  tone?: (HelixMapPoints["tone"]) | undefined;
+  /** Combines nearby points into counts. Pressing a count zooms in to it. */
+  cluster?: (HelixMapPoints["cluster"]) | undefined;
+  /** The name read for a count. `{count}` is replaced by the number of places.
+Defaults to "{count} places". */
+  "count-label"?: (HelixMapPoints["countLabel"]) | undefined;
+  /** The name read for a count. `{count}` is replaced by the number of places.
+Defaults to "{count} places". */
+  countLabel?: (HelixMapPoints["countLabel"]) | undefined;
+  /** More about the points, such as how many there are. Read after the label in
+the frame's list. */
+  description?: (HelixMapPoints["description"]) | undefined;
+  /** The layer's name, used in the frame's list. */
+  label?: (HelixMapPoints["label"]) | undefined;
+  /** The GeoJSON property each point is named by. Defaults to `name`. */
+  "name-key"?: (HelixMapPoints["nameKey"]) | undefined;
+  /** The GeoJSON property each point is named by. Defaults to `name`. */
+  nameKey?: (HelixMapPoints["nameKey"]) | undefined;
+  /** A GeoJSON file of points to load. Ignored when `data` is set. */
+  src?: (HelixMapPoints["src"]) | undefined;
+  /** The points, as a GeoJSON collection or a list of `{ lat, lng, label, id }`
+places. */
+  data?: (HelixMapPoints["data"]) | undefined;
+};
+
+export type HelixMapPointsVueEvents = {
+  /** A point in view was pressed. The value is its id, or its name if it has no id. */
+  "helix-activate": HelixMapPointsHelixActivateElementEvent;
+  /** A count in view was pressed from the keyboard. `connectMap` zooms in to it. */
+  "helix-map-cluster": HelixMapPointsHelixMapClusterElementEvent;
+  /** The points, name, or color changed. Used by `connectMap`; pages do not need to listen for it. */
+  "helix-map-part-change": HelixMapPointsHelixMapPartChangeElementEvent;
+};
+
+/** `HelixMapPosition` component event */
+export type HelixMapPositionElementEvent<E = Event> = TypedEvent<
+  HelixMapPosition,
+  E
+>;
+/** `helix-map-part-change` event type */
+export type HelixMapPositionHelixMapPartChangeElementEvent =
+  HelixMapPositionElementEvent<HelixMapPartChangeEvent>;
+
+export type HelixMapPositionVueProps = {
+  /** How the point stands out from the map. Leave unset for an edge, a halo,
+and a small shadow. `outlined` has the edge only, `elevated` a larger
+shadow, `filled` the halo without an edge, and `plain` none of these. */
+  separation?: (HelixMapPosition["separation"]) | undefined;
+  /** The point's shape. A circle unless set. A position with a heading is
+always an arrow. */
+  shape?: (HelixMapPosition["shape"]) | undefined;
+  /** The position's color. Uses your theme's foreground color unless set. */
+  tone?: (HelixMapPosition["tone"]) | undefined;
+  /** How accurate the position is, in meters. Drawn as a ring with this radius. */
+  accuracy?: (HelixMapPosition["accuracy"]) | undefined;
+  /** The least time between announcements, in milliseconds. A change during the
+wait is announced when the wait ends. */
+  "announce-every"?: (HelixMapPosition["announceEvery"] | `${number}`) | undefined;
+  /** The least time between announcements, in milliseconds. A change during the
+wait is announced when the wait ends. */
+  announceEvery?: (HelixMapPosition["announceEvery"]) | undefined;
+  /** What screen readers announce when it changes, such as "Two stops away". */
+  description?: (HelixMapPosition["description"]) | undefined;
+  /** The direction it faces, in degrees clockwise from north. Shows an arrow. */
+  heading?: (HelixMapPosition["heading"]) | undefined;
+  /** What it is, such as "Van 12". Read by screen readers. */
+  label?: (HelixMapPosition["label"]) | undefined;
+  /** Latitude, in degrees. */
+  lat?: (HelixMapPosition["lat"]) | undefined;
+  /** Longitude, in degrees. */
+  lng?: (HelixMapPosition["lng"]) | undefined;
+};
+
+export type HelixMapPositionVueEvents = {
+  /** It moved, turned, or its accuracy changed. Used by `connectMap`; pages do not need to listen for it. */
+  "helix-map-part-change": HelixMapPositionHelixMapPartChangeElementEvent;
+};
+
 /** `HelixMap` component event */
 export type HelixMapElementEvent<E = Event> = TypedEvent<HelixMap, E>;
+/** `helix-activate` event type */
+export type HelixMapHelixActivateElementEvent =
+  HelixMapElementEvent<HelixActivateEvent>;
+/** `helix-map-cluster` event type */
+export type HelixMapHelixMapClusterElementEvent =
+  HelixMapElementEvent<HelixMapClusterEvent>;
 /** `helix-map-pan` event type */
 export type HelixMapHelixMapPanElementEvent =
   HelixMapElementEvent<HelixMapPanEvent>;
+/** `helix-map-part-change` event type */
+export type HelixMapHelixMapPartChangeElementEvent =
+  HelixMapElementEvent<HelixMapPartChangeEvent>;
 /** `helix-map-zoom` event type */
 export type HelixMapHelixMapZoomElementEvent =
   HelixMapElementEvent<HelixMapZoomEvent>;
 
 export type HelixMapVueProps = {
-  /** Which of the controls this surface draws, as a list of what to keep.
+  /** The background of the pan and zoom buttons. Leave unset for solid. `glass`
+shows the map through a blur, `frosted` blurs more, and `transparent` has
+no background. Your theme sets how see-through each one is. */
+  material?: (HelixMap["material"]) | undefined;
+  /** Which controls to show, as a list of `pan`, `zoom`, and `fullscreen`, or `none`.
 
 **A list rather than a switch, because the overlap is not symmetric.** A
 surface a consumer brings often has zoom controls of its own and almost
@@ -6799,14 +6994,14 @@ board, which a reader drags and whose pad took a third of the frame. The
 stylesheet lays the cluster out by which buttons are in it rather than by
 this attribute, so the two defaults need no rule each. */
   controls?: (HelixMap["controls"]) | undefined;
-  /** What the group of controls is called, for a reader who meets it.
+  /** The name of the group of controls, read by screen readers.
 
 Absent is the family's own name for it, "Map controls" or "Board
 controls", which names what the controls drive rather than the
 mechanism. Written here to say it in another language, which every other
 string this surface speaks already allowed and this one did not. */
   "controls-label"?: (HelixMap["controlsLabel"]) | undefined;
-  /** What the group of controls is called, for a reader who meets it.
+  /** The name of the group of controls, read by screen readers.
 
 Absent is the family's own name for it, "Map controls" or "Board
 controls", which names what the controls drive rather than the
@@ -6837,25 +7032,25 @@ them without a consumer writing a second rule. Absent is the top end, a
 resting value being an attribute's absence: a default that reflected
 would write an attribute onto every host that no server sent. */
   controlsPlacement?: (HelixMap["controlsPlacement"]) | undefined;
-  /** What the control that fills the screen is called. */
+  /** The fullscreen button's label. */
   "fullscreen-label"?: (HelixMap["fullscreenLabel"]) | undefined;
-  /** What the control that fills the screen is called. */
+  /** The fullscreen button's label. */
   fullscreenLabel?: (HelixMap["fullscreenLabel"]) | undefined;
-  /** How long the reader may be still before the chrome hides, in milliseconds.
+  /** How long, in milliseconds, before the header and footer hide when the user is inactive. `0` keeps them visible.
 
 Zero keeps it up, which is the default: these controls are how a keyboard
 reader operates the surface, and chrome that hid itself by default would
 be the component undoing its own argument. Set it for a display nobody
 drives. */
   "idle-delay"?: (HelixMap["idleDelay"] | `${number}`) | undefined;
-  /** How long the reader may be still before the chrome hides, in milliseconds.
+  /** How long, in milliseconds, before the header and footer hide when the user is inactive. `0` keeps them visible.
 
 Zero keeps it up, which is the default: these controls are how a keyboard
 reader operates the surface, and chrome that hid itself by default would
 be the component undoing its own argument. Set it for a display nobody
 drives. */
   idleDelay?: (HelixMap["idleDelay"]) | undefined;
-  /** What the control that pans down is called.
+  /** The pan down button's label.
 
 **A label for each way rather than one with the way filled in**, which is
 what this was: `Pan {way}` filled in with `left`, so a page that said it
@@ -6863,7 +7058,7 @@ in French read out "Déplacer left". The word for a direction is as much
 the translator's as the word for panning, and a language can put it
 anywhere in the phrase. */
   "pan-down-label"?: (HelixMap["panDownLabel"]) | undefined;
-  /** What the control that pans down is called.
+  /** The pan down button's label.
 
 **A label for each way rather than one with the way filled in**, which is
 what this was: `Pan {way}` filled in with `left`, so a page that said it
@@ -6871,60 +7066,95 @@ in French read out "Déplacer left". The word for a direction is as much
 the translator's as the word for panning, and a language can put it
 anywhere in the phrase. */
   panDownLabel?: (HelixMap["panDownLabel"]) | undefined;
-  /** What the control that pans left is called, on screen. */
+  /** The pan left button's label. */
   "pan-left-label"?: (HelixMap["panLeftLabel"]) | undefined;
-  /** What the control that pans left is called, on screen. */
+  /** The pan left button's label. */
   panLeftLabel?: (HelixMap["panLeftLabel"]) | undefined;
-  /** What the control that pans right is called, on screen. */
+  /** The pan right button's label. */
   "pan-right-label"?: (HelixMap["panRightLabel"]) | undefined;
-  /** What the control that pans right is called, on screen. */
+  /** The pan right button's label. */
   panRightLabel?: (HelixMap["panRightLabel"]) | undefined;
-  /** How far one press moves the view, as a fraction of what is on screen.
+  /** How far one press pans the view, as a fraction of its size.
 
 A fraction rather than a distance, because this surface does not know the
 scale of what is inside it: a quarter of the viewport is the same gesture
 at any zoom, and a consumer who wants their own units multiplies by them. */
   "pan-step"?: (HelixMap["panStep"] | `${number}`) | undefined;
-  /** How far one press moves the view, as a fraction of what is on screen.
+  /** How far one press pans the view, as a fraction of its size.
 
 A fraction rather than a distance, because this surface does not know the
 scale of what is inside it: a quarter of the viewport is the same gesture
 at any zoom, and a consumer who wants their own units multiplies by them. */
   panStep?: (HelixMap["panStep"]) | undefined;
-  /** What the control that pans up is called. */
+  /** The pan up button's label. */
   "pan-up-label"?: (HelixMap["panUpLabel"]) | undefined;
-  /** What the control that pans up is called. */
+  /** The pan up button's label. */
   panUpLabel?: (HelixMap["panUpLabel"]) | undefined;
-  /** What the control that zooms in is called. */
+  /** The zoom in button's label. */
   "zoom-in-label"?: (HelixMap["zoomInLabel"]) | undefined;
-  /** What the control that zooms in is called. */
+  /** The zoom in button's label. */
   zoomInLabel?: (HelixMap["zoomInLabel"]) | undefined;
-  /** What the control that zooms out is called. */
+  /** The zoom out button's label. */
   "zoom-out-label"?: (HelixMap["zoomOutLabel"]) | undefined;
-  /** What the control that zooms out is called. */
+  /** The zoom out button's label. */
   zoomOutLabel?: (HelixMap["zoomOutLabel"]) | undefined;
-  /** Accessible name for the map, which is the one thing a consumer must write.
-
-There is no sensible default. "Map" names the widget rather than the place,
-and a reader meeting three of them on a page learns nothing from hearing the
-same word three times.
-
-**The region is a tab stop**, so the keys are reachable however the controls
-are configured: the listener is on the region, and without a stop of its own
-a frame at `controls="none"` around a map with nothing focusable in it had
-arrow keys no reader could ever press. `aria-keyshortcuts` says which keys
-rather than spelling them into the name, which would otherwise be read out
-at every encounter. */
+  /** Combines markers that would overlap into one count. Counts split apart as
+the map zooms in, and pressing one zooms in to its places. */
+  cluster?: (HelixMap["cluster"]) | undefined;
+  /** The map's name, read by screen readers. Name the place, such as "Delivery
+area", so that several maps on one page can be told apart. Required. */
   label?: (HelixMap["label"]) | undefined;
+  /** The name of the list of routes, areas, and points layers, read by screen
+readers. */
+  "layers-label"?: (HelixMap["layersLabel"]) | undefined;
+  /** The name of the list of routes, areas, and points layers, read by screen
+readers. */
+  layersLabel?: (HelixMap["layersLabel"]) | undefined;
 };
 
 export type HelixMapVueEvents = {
-  /** The reader asked the map to move. Answer it against your own map. */
+  /** A marker was pressed. The value is the marker's `name`, or its `label` if it has no name. A cluster sends `helix-map-cluster` instead. */
+  "helix-activate": HelixMapHelixActivateElementEvent;
+  /** A cluster was pressed. Sent from the marker that shows the cluster, with the names of its places. */
+  "helix-map-cluster": HelixMapHelixMapClusterElementEvent;
+  /** A pan button or arrow key was pressed. Move your map in response. */
   "helix-map-pan": HelixMapHelixMapPanElementEvent;
-  /** The reader asked the map to zoom, by a direction rather than to a level. */
+  /** Clustering was turned on or off. Used by `connectMap`; pages do not need to listen for it. */
+  "helix-map-part-change": HelixMapHelixMapPartChangeElementEvent;
+  /** A zoom button or key was pressed, with a direction. Zoom your map in response. */
   "helix-map-zoom": HelixMapHelixMapZoomElementEvent;
 };
 
+/** `HelixMapRoute` component event */
+export type HelixMapRouteElementEvent<E = Event> = TypedEvent<HelixMapRoute, E>;
+/** `helix-map-part-change` event type */
+export type HelixMapRouteHelixMapPartChangeElementEvent =
+  HelixMapRouteElementEvent<HelixMapPartChangeEvent>;
+
+export type HelixMapRouteVueProps = {
+  /** The route's color. Uses your primary color unless set. */
+  tone?: (HelixMapRoute["tone"]) | undefined;
+  /** `dotted` draws the route as dots, for a walk off the road network. */
+  variant?: (HelixMapRoute["variant"]) | undefined;
+  /** More about the route, such as its distance or time. Read after its label
+in the frame's list. */
+  description?: (HelixMapRoute["description"]) | undefined;
+  /** The route's name, used in the frame's list. */
+  label?: (HelixMapRoute["label"]) | undefined;
+  /** The points the line passes through, in order. Write the attribute as
+`lat,lng` pairs separated by spaces, or set the property to an array of `{
+lat, lng }`. */
+  points?: (HelixMapRoute["points"]) | undefined;
+  /** How much of the route has been traveled, from 0 to 1. The traveled part is
+drawn in a lighter color. */
+  progress?: (HelixMapRoute["progress"]) | undefined;
+};
+
+export type HelixMapRouteVueEvents = {
+  /** The route's points, progress, name, or color changed. Used by `connectMap`; pages do not need to listen for it. */
+  "helix-map-part-change": HelixMapRouteHelixMapPartChangeElementEvent;
+};
+
 /** `HelixMegamenu` component event */
 export type HelixMegamenuElementEvent<E = Event> = TypedEvent<HelixMegamenu, E>;
 /** `helix-before-close` event type */
@@ -6935,9 +7165,9 @@ export type HelixMegamenuHelixBeforeOpenElementEvent =
   HelixMegamenuElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixMegamenuVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixMegamenu["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixMegamenu["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -7146,23 +7376,23 @@ export type HelixMenuHelixSelectElementEvent =
   HelixMenuElementEvent<HelixSelectEvent>;
 
 export type HelixMenuVueProps = {
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixMenu["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixMenu["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixMenu["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixMenu["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixMenu["loadingText"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixMenu["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixMenu["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -7336,9 +7566,9 @@ export type HelixNotificationGroupHelixBeforeOpenElementEvent =
   HelixNotificationGroupElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixNotificationGroupVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixNotificationGroup["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixNotificationGroup["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -7411,16 +7641,16 @@ separated.** A consumer wanting the whole feed carded says so once, in a
 document rule on the element, rather than on every item: this is a styled
 axis and a stylesheet is where it is set. */
   separation?: (HelixNotification["separation"]) | undefined;
-  /** Whether it offers a control to take it away. */
+  /** Whether the element shows a control that dismisses it. */
   dismissible?: (HelixNotification["dismissible"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
 reachable only as `dismisslabel`, which nobody would guess and no linter
 would catch. */
   "dismiss-label"?: (HelixNotification["dismissLabel"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
@@ -7478,19 +7708,19 @@ export type HelixNotificationsHelixReadElementEvent =
   HelixNotificationsElementEvent<HelixReadEvent>;
 
 export type HelixNotificationsVueProps = {
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixNotifications["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixNotifications["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixNotifications["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixNotifications["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixNotifications["loadingText"]) | undefined;
   /** Accessible name for the feed. */
   label?: (HelixNotifications["label"]) | undefined;
@@ -7521,27 +7751,28 @@ export type HelixNumberInputHelixBeforeChangeElementEvent =
   HelixNumberInputElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixNumberInputVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixNumberInput["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixNumberInput["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixNumberInput["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixNumberInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixNumberInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixNumberInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixNumberInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -7550,8 +7781,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixNumberInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -7636,7 +7866,7 @@ one they already know. */
   scrub?: (HelixNumberInput["scrub"]) | undefined;
   /** How far one step moves. */
   step?: (HelixNumberInput["step"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -7645,7 +7875,7 @@ 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?: (HelixNumberInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -8198,27 +8428,28 @@ export type HelixPinInputHelixCompleteElementEvent =
   HelixPinInputElementEvent<HelixCompleteEvent>;
 
 export type HelixPinInputVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixPinInput["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixPinInput["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixPinInput["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixPinInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixPinInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixPinInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixPinInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -8227,8 +8458,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixPinInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -8293,7 +8523,7 @@ attribute no consumer's markup had. The area rules carry the sentence
 "reflect only what CSS selects on". The real inputs take it as a binding,
 which is what makes the keyboard follow. */
   type?: (HelixPinInput["type"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -8302,7 +8532,7 @@ 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?: (HelixPinInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -8353,9 +8583,9 @@ Unset is a surface with an inset, which is what a panel of content wants.
 `plain` removes both, for a panel holding something that brings its own,
 such as a list whose rows run to the edges. */
   separation?: (HelixPopover["separation"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixPopover["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixPopover["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -8535,27 +8765,28 @@ export type HelixRadioGroupHelixSelectElementEvent =
   HelixRadioGroupElementEvent<HelixSelectEvent>;
 
 export type HelixRadioGroupVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixRadioGroup["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixRadioGroup["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixRadioGroup["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixRadioGroup["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixRadioGroup["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixRadioGroup["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixRadioGroup["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -8564,8 +8795,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixRadioGroup["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -8583,7 +8813,7 @@ not touch, and React reads that as a hydration mismatch. The absent
 attribute *is* the column, which the stylesheet reads as the base rule, so
 only `horizontal` has to be named. */
   orientation?: (HelixRadioGroup["orientation"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -8592,7 +8822,7 @@ 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?: (HelixRadioGroup["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -8699,15 +8929,16 @@ which is why `hide-control` says it is unnecessary here, and it takes the
 words out of the flow to be the accessible name. That removes the
 distinction `separation` exists to make rather than answering it. */
   variant?: (HelixRadio["variant"]) | undefined;
-  /** Whether this one can be chosen. */
+  /** Whether the item is disabled and cannot be chosen. */
   disabled?: (HelixRadio["disabled"]) | undefined;
-  /** Whether this is the current one.
+  /** Whether the item is selected.
 
 Written by the set rather than by a consumer, which is why it takes no
 default from an attribute here: a family whose selection a consumer
 declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixRadio["selected"]) | undefined;
-  /** Identifies this one to the set, and is what a form submits. */
+  /** The item's value, which identifies it in its set and is what a form
+submits. */
   value?: (HelixRadio["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.
 
@@ -8786,27 +9017,28 @@ an attribute React holds no prop for and so a hydration mismatch for each
 one. The stylesheet names only `dots`, so an unset one draws the star by
 landing on the base rule. */
   shape?: (HelixRating["shape"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixRating["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixRating["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixRating["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixRating["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixRating["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixRating["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixRating["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -8815,8 +9047,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixRating["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -8919,7 +9150,7 @@ answer from the value than from a sentence: "3.5" alone is a number without
 a subject. This names the readout, where a control is named by its `label`
 and each of its options by the score that option is. */
   valueText?: (HelixRating["valueText"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -8928,7 +9159,7 @@ 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?: (HelixRating["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -9256,7 +9487,7 @@ shadow root reads a table in that root rather than one in the document. A
 **In React this arrives as a property and not as an attribute**, the way
 `Tooltip.for` does, so it does not reflect and nothing styles on it. */
   for?: (HelixScatterChart["for"]) | undefined;
-  /** The drawing's name, for a pointer resting on it.
+  /** The chart's name, which starts the chart's text summary.
 
 Absent falls back to the table's own caption, which is usually the right
 words and is already written. */
@@ -9335,9 +9566,9 @@ are left alone rather than swept, because each has a different thing inside
 the frame and guessing at a set of them is how an axis ends up meaning four
 things, which is the fault `appearance` was retired for. */
   emphasis?: (HelixSelect["emphasis"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixSelect["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixSelect["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -9352,27 +9583,28 @@ hydration, or diffed by a framework, it comes back holding whatever the
 last reader did rather than what the author wrote. `:state(open)` carries
 the resolved state for stylesheets, which is what the mirror is for. */
   open?: (HelixSelect["open"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixSelect["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixSelect["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixSelect["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixSelect["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixSelect["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixSelect["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixSelect["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -9381,8 +9613,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixSelect["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -9414,7 +9645,7 @@ consumer wiring the same flag twice. */
   multiple?: (HelixSelect["multiple"]) | undefined;
   /** Shown on the trigger while nothing is chosen. */
   placeholder?: (HelixSelect["placeholder"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -9423,7 +9654,7 @@ 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?: (HelixSelect["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -9497,27 +9728,28 @@ export type HelixSliderHelixBeforeChangeElementEvent =
   HelixSliderElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixSliderVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixSlider["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixSlider["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixSlider["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixSlider["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixSlider["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixSlider["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixSlider["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -9526,8 +9758,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixSlider["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -9601,7 +9832,7 @@ the two, since a range has no single number. */
   showValue?: (HelixSlider["showValue"]) | undefined;
   /** How far one press of an arrow key moves it. */
   step?: (HelixSlider["step"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -9610,7 +9841,7 @@ 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?: (HelixSlider["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -9816,9 +10047,9 @@ export type HelixSpeedDialHelixSelectElementEvent =
   HelixSpeedDialElementEvent<HelixSelectEvent>;
 
 export type HelixSpeedDialVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixSpeedDial["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixSpeedDial["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -10046,7 +10277,7 @@ export type HelixStepsHelixSelectElementEvent =
   HelixStepsElementEvent<HelixSelectEvent>;
 
 export type HelixStepsVueProps = {
-  /** Which item is current, by its `value`.
+  /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
 different question from which one is chosen.
@@ -10055,11 +10286,11 @@ Writing always applies, so `<helix-tabs active="one">` starts on that
 tab, and `default-active` is how markup says where to start without
 naming the current one. */
   active?: (HelixSteps["active"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   "default-active"?: (HelixSteps["defaultActive"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   defaultActive?: (HelixSteps["defaultActive"]) | undefined;
@@ -10140,20 +10371,21 @@ Not reflected: the attribute is the consumer's input and stays as they
 wrote it, and `:state(checked)` carries the resolved state for
 stylesheets. */
   checked?: (HelixSwitch["checked"]) | undefined;
-  /** Whether the markup declared it checked, which is where a reset returns to. */
+  /** Whether the control starts checked. A form reset returns it to this state. */
   "default-checked"?: (HelixSwitch["defaultChecked"]) | undefined;
-  /** Whether the markup declared it checked, which is where a reset returns to. */
+  /** Whether the control starts checked. A form reset returns it to this state. */
   defaultChecked?: (HelixSwitch["defaultChecked"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixSwitch["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixSwitch["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixSwitch["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixSwitch["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -10162,8 +10394,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixSwitch["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -10174,7 +10405,7 @@ the field and does not reach that one. */
   valueMissingMessage?: (HelixSwitch["valueMissingMessage"]) | undefined;
   /** Value submitted when the switch is on. */
   value?: (HelixSwitch["value"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -10183,7 +10414,7 @@ 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?: (HelixSwitch["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -10388,19 +10619,19 @@ export type HelixTableColumnVueEvents = {
 };
 
 export type HelixTableVueProps = {
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixTable["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixTable["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixTable["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixTable["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixTable["loadingText"]) | undefined;
   /** The column widths as one track list, written once on the table.
 
@@ -10475,7 +10706,7 @@ export type HelixTabsHelixSelectElementEvent =
   HelixTabsElementEvent<HelixSelectEvent>;
 
 export type HelixTabsVueProps = {
-  /** Which item is current, by its `value`.
+  /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
 different question from which one is chosen.
@@ -10484,11 +10715,11 @@ Writing always applies, so `<helix-tabs active="one">` starts on that
 tab, and `default-active` is how markup says where to start without
 naming the current one. */
   active?: (HelixTabs["active"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   "default-active"?: (HelixTabs["defaultActive"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   defaultActive?: (HelixTabs["defaultActive"]) | undefined;
@@ -10541,15 +10772,16 @@ export type HelixTabHelixSelectElementEvent =
   HelixTabElementEvent<HelixSelectEvent>;
 
 export type HelixTabVueProps = {
-  /** Whether this one can be chosen. */
+  /** Whether the item is disabled and cannot be chosen. */
   disabled?: (HelixTab["disabled"]) | undefined;
-  /** Whether this is the current one.
+  /** Whether the item is selected.
 
 Written by the set rather than by a consumer, which is why it takes no
 default from an attribute here: a family whose selection a consumer
 declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixTab["selected"]) | undefined;
-  /** Identifies this one to the set, and is what a form submits. */
+  /** The item's value, which identifies it in its set and is what a form
+submits. */
   value?: (HelixTab["value"]) | undefined;
 };
 
@@ -10593,16 +10825,16 @@ somewhere that draws one.
 `Badge` and `Announcement` take the same seven, all three being a mark that
 carries a meaning beside something else. */
   tone?: (HelixTag["tone"]) | undefined;
-  /** Whether it offers a control to take it away. */
+  /** Whether the element shows a control that dismisses it. */
   dismissible?: (HelixTag["dismissible"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
 reachable only as `dismisslabel`, which nobody would guess and no linter
 would catch. */
   "dismiss-label"?: (HelixTag["dismissLabel"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
@@ -10662,27 +10894,28 @@ export type HelixTextareaHelixBeforeChangeElementEvent =
   HelixTextareaElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixTextareaVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixTextarea["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixTextarea["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixTextarea["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixTextarea["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixTextarea["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixTextarea["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixTextarea["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -10691,8 +10924,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixTextarea["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -10767,7 +10999,7 @@ Not a label: it goes when typing starts. */
   /** How the browser wraps the text, and whether the breaks are submitted with
 it. */
   wrap?: (HelixTextarea["wrap"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -10776,7 +11008,7 @@ 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?: (HelixTextarea["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -10836,7 +11068,7 @@ export type HelixTimeInputHelixBeforeOpenElementEvent =
   HelixTimeInputElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixTimeInputVueProps = {
-  /** Whether the control refuses changes while still submitting its value.
+  /** Whether the value is locked. A read-only control still submits its value.
 
 **Enforced by refusing every request in one place**, which is the seam this
 component already has: `requestValue` is what every path here comes through,
@@ -10848,7 +11080,7 @@ submits nothing and leaves the tab order, and a read-only one submits its
 value and stays reachable, which is what a form showing a value somebody
 else set needs. */
   readonly?: (HelixTimeInput["readOnly"]) | undefined;
-  /** Whether the control refuses changes while still submitting its value.
+  /** Whether the value is locked. A read-only control still submits its value.
 
 **Enforced by refusing every request in one place**, which is the seam this
 component already has: `requestValue` is what every path here comes through,
@@ -10860,25 +11092,25 @@ submits nothing and leaves the tab order, and a read-only one submits its
 value and stays reachable, which is what a form showing a value somebody
 else set needs. */
   readOnly?: (HelixTimeInput["readOnly"]) | undefined;
-  /** What a reader is told when the field holds something the picker cannot
-read: a date that is not one, a time, a color.
+  /** The message shown when the field holds text the picker cannot read as a
+date, a time, or a color.
 
 **Every sentence a control raises in the browser's bubble is a
 property**, named for the validity flag it reports, so a form in another
 language speaks it. Absent is the family's own sentence, in English,
 which says what the value should look like. */
   "bad-input-message"?: (HelixTimeInput["badInputMessage"]) | undefined;
-  /** What a reader is told when the field holds something the picker cannot
-read: a date that is not one, a time, a color.
+  /** The message shown when the field holds text the picker cannot read as a
+date, a time, or a color.
 
 **Every sentence a control raises in the browser's bubble is a
 property**, named for the validity flag it reports, so a form in another
 language speaks it. Absent is the family's own sentence, in English,
 which says what the value should look like. */
   badInputMessage?: (HelixTimeInput["badInputMessage"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixTimeInput["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixTimeInput["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -10893,41 +11125,44 @@ hydration, or diffed by a framework, it comes back holding whatever the
 last reader did rather than what the author wrote. `:state(open)` carries
 the resolved state for stylesheets, which is what the mirror is for. */
   open?: (HelixTimeInput["open"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   "collapse-label"?: (HelixTimeInput["collapseLabel"]) | undefined;
-  /** What the control is called once everything is showing. */
+  /** The button's label, read by screen readers, once every token is showing. */
   collapseLabel?: (HelixTimeInput["collapseLabel"]) | undefined;
-  /** Whether the count is a control that shows the rest. */
+  /** Whether the count is a button that shows the hidden tokens. */
   expandable?: (HelixTimeInput["expandable"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   "expand-label"?: (HelixTimeInput["expandLabel"]) | undefined;
-  /** What the collapsed count is called, since `+3` names nothing. */
+  /** The count button's label, read by screen readers. Its visible text, such
+as `+3`, does not say what it does. */
   expandLabel?: (HelixTimeInput["expandLabel"]) | undefined;
   /** How many tokens to show before the rest become a count. */
   "max-tags"?: (HelixTimeInput["maxTags"] | `${number}`) | undefined;
   /** How many tokens to show before the rest become a count. */
   maxTags?: (HelixTimeInput["maxTags"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixTimeInput["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixTimeInput["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixTimeInput["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixTimeInput["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixTimeInput["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixTimeInput["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixTimeInput["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -10936,8 +11171,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixTimeInput["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -11036,7 +11270,7 @@ not touch, and React reads that as a hydration mismatch. The absent
 attribute *is* the list, which the stylesheet reads as the base rule, so
 only the departure has to be named. */
   variant?: (HelixTimeInput["variant"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -11045,7 +11279,7 @@ 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?: (HelixTimeInput["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -11099,11 +11333,11 @@ export type HelixTimePickerHelixBeforeChangeElementEvent =
   HelixTimePickerElementEvent<HelixBeforeChangeEvent>;
 
 export type HelixTimePickerVueProps = {
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixTimePicker["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixTimePicker["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
@@ -11241,7 +11475,7 @@ not touch, and React reads that as a hydration mismatch. The absent
 attribute *is* the list, which the stylesheet reads as the base rule, so
 only the departure has to be named. */
   variant?: (HelixTimePicker["variant"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -11250,7 +11484,7 @@ 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?: (HelixTimePicker["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -11318,16 +11552,16 @@ export type HelixToastItemHelixDismissElementEvent =
   HelixToastItemElementEvent<HelixDismissEvent>;
 
 export type HelixToastItemVueProps = {
-  /** Whether it offers a control to take it away. */
+  /** Whether the element shows a control that dismisses it. */
   dismissible?: (HelixToastItem["dismissible"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
 reachable only as `dismisslabel`, which nobody would guess and no linter
 would catch. */
   "dismiss-label"?: (HelixToastItem["dismissLabel"]) | undefined;
-  /** Accessible name for that control.
+  /** The dismiss control's label, read by screen readers.
 
 `attribute` is spelled out because Lit lowercases a property name to
 derive one rather than dash-casing it, so this would otherwise be
@@ -11431,27 +11665,28 @@ because a row of tabs is a row until asked; here it is the resting state,
 because a group of toggles is one control. Same groove, opposite polarity,
 and what decides the polarity is which reading is ordinary for the family. */
   separation?: (HelixToggleGroup["separation"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   "default-value"?: (HelixToggleGroup["defaultValue"]) | undefined;
-  /** The value the markup declared, which is where a reset returns to. */
+  /** The value the control starts with. A form reset returns it to this value. */
   defaultValue?: (HelixToggleGroup["defaultValue"]) | undefined;
-  /** What the control holds now, and what its form submits.
+  /** The control's current value, which its form submits.
 
 One property, not two, so `input.value` answers the question anyone
 asking it meant. Writing always applies; `<helix-input value="x">` is the
 same statement in markup, and `default-value` is how markup seeds a value
 a reset should return to. */
   value?: (HelixToggleGroup["value"]) | undefined;
-  /** What is wrong, in the reader's words rather than the browser's. */
+  /** The validation message shown under the control. It replaces the
+browser's message. */
   feedback?: (HelixToggleGroup["feedback"]) | undefined;
-  /** Help under the control, shown while there is nothing wrong. */
+  /** Help text shown under the control. A validation message replaces it. */
   hint?: (HelixToggleGroup["hint"]) | undefined;
-  /** The accessible name, and the fallback for the `label` slot. */
+  /** The field's label, which is also its accessible name. Content in the
+`label` slot replaces it. */
   label?: (HelixToggleGroup["label"]) | undefined;
-  /** Whether the form refuses to submit without it. */
+  /** Whether the field needs a value before the form can submit. */
   required?: (HelixToggleGroup["required"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -11460,8 +11695,7 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "value-missing-message"?: (HelixToggleGroup["valueMissingMessage"]) | undefined;
-  /** What a reader is told when the field is required and empty, where the
-page says.
+  /** The message shown when the field is required and empty.
 
 **Absent, or empty, is the control's own sentence**, "Choose one to continue." on a
 set and the browser's own on a text field, which the browser writes in
@@ -11500,7 +11734,7 @@ reader while looking correct to everybody else. Worse, setting both draws
 it twice. One property moves the label the consumer already has to give,
 and cannot be used to remove it. */
   labelPlacement?: (HelixToggleGroup["labelPlacement"]) | undefined;
-  /** Whether the control is non-interactive.
+  /** 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
@@ -11509,7 +11743,7 @@ 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?: (HelixToggleGroup["disabled"]) | undefined;
-  /** Name submitted with the form.
+  /** 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
@@ -11546,15 +11780,16 @@ export type HelixToggleHelixSelectElementEvent =
   HelixToggleElementEvent<HelixSelectEvent>;
 
 export type HelixToggleVueProps = {
-  /** Whether this one can be chosen. */
+  /** Whether the item is disabled and cannot be chosen. */
   disabled?: (HelixToggle["disabled"]) | undefined;
-  /** Whether this is the current one.
+  /** Whether the item is selected.
 
 Written by the set rather than by a consumer, which is why it takes no
 default from an attribute here: a family whose selection a consumer
 declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixToggle["selected"]) | undefined;
-  /** Identifies this one to the set, and is what a form submits. */
+  /** The item's value, which identifies it in its set and is what a form
+submits. */
   value?: (HelixToggle["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.
 
@@ -11644,9 +11879,9 @@ content is only readable because it has a ground; dropping it makes an
 unreadable tooltip rather than a lighter one. `frosted` and `glass` are the
 two honest points here. */
   material?: (HelixTooltip["material"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixTooltip["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixTooltip["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -11876,9 +12111,9 @@ export type HelixTreeItemHelixBeforeOpenElementEvent =
   HelixTreeItemElementEvent<HelixBeforeOpenEvent>;
 
 export type HelixTreeItemVueProps = {
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: (HelixTreeItem["defaultOpen"]) | undefined;
-  /** Whether the markup declared it open. Ignored once `open` is written. */
+  /** Whether the element starts open. Ignored once `open` is written. */
   defaultOpen?: (HelixTreeItem["defaultOpen"]) | undefined;
   /** Whether the element is open.
 
@@ -12010,21 +12245,21 @@ and the row's `end` slot already carries an auto margin of its own, so the
 two split the free space and the chevron lands halfway along. Measured at
 70px short. That is the kind of thing a component should absorb once. */
   chevronPlacement?: (HelixTree["chevronPlacement"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   "empty-text"?: (HelixTree["emptyText"]) | undefined;
-  /** What is said where there are none, and none are coming. */
+  /** The text shown and announced when there are no rows and none are loading. */
   emptyText?: (HelixTree["emptyText"]) | undefined;
-  /** Whether the rows are still on their way.
+  /** Whether the rows are still loading.
 
 Reflected, because a stylesheet needs it: the rows that are already there
 are dimmed rather than removed while a new set arrives, and only CSS can
 say that without the component knowing what a row looks like. */
   loading?: (HelixTree["loading"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   "loading-text"?: (HelixTree["loadingText"]) | undefined;
-  /** What is said while they are on their way. */
+  /** The text shown and announced while the rows load. */
   loadingText?: (HelixTree["loadingText"]) | undefined;
-  /** Which item is current, by its `value`.
+  /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
 different question from which one is chosen.
@@ -12033,11 +12268,11 @@ Writing always applies, so `<helix-tabs active="one">` starts on that
 tab, and `default-active` is how markup says where to start without
 naming the current one. */
   active?: (HelixTree["active"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   "default-active"?: (HelixTree["defaultActive"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   defaultActive?: (HelixTree["defaultActive"]) | undefined;
@@ -12186,7 +12421,7 @@ export type HelixVideoPlaylistHelixBeforeActivateElementEvent =
   HelixVideoPlaylistElementEvent<HelixBeforeActivateEvent>;
 
 export type HelixVideoPlaylistVueProps = {
-  /** Which item is current, by its `value`.
+  /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
 different question from which one is chosen.
@@ -12195,11 +12430,11 @@ Writing always applies, so `<helix-tabs active="one">` starts on that
 tab, and `default-active` is how markup says where to start without
 naming the current one. */
   active?: (HelixVideoPlaylist["active"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   "default-active"?: (HelixVideoPlaylist["defaultActive"]) | undefined;
-  /** Which item the markup declared current.
+  /** The `value` of the item declared current in markup.
 
 Ignored once `active` is written. */
   defaultActive?: (HelixVideoPlaylist["defaultActive"]) | undefined;
@@ -13191,12 +13426,46 @@ export type CustomCssProperties = {
   "--loader-size"?: (string) | undefined;
   /** Color of the circle behind it. */
   "--loader-track-color"?: (string) | undefined;
-  /** The well behind the map, seen while tiles are on their way. */
+  /** The area's color when no tone is set. */
+  "--map-area-color"?: (string) | undefined;
+  /** A cluster's fill color. */
+  "--map-marker-cluster-color"?: (string) | undefined;
+  /** A cluster's width. */
+  "--map-marker-cluster-size"?: (string) | undefined;
+  /** The point's color when no tone is set. */
+  "--map-marker-color"?: (string) | undefined;
+  /** The color of a letter or icon in the point. Set it with `--map-marker-color` when white is hard to read on your color. */
+  "--map-marker-ink"?: (string) | undefined;
+  /** The width of the name's border. */
+  "--map-marker-label-border-width"?: (string) | undefined;
+  /** The name's shadow. */
+  "--map-marker-label-shadow"?: (string) | undefined;
+  /** The point's width. */
+  "--map-marker-size"?: (string) | undefined;
+  /** The edge around each point and count. */
+  "--map-points-casing-color"?: (string) | undefined;
+  /** The points' color when no tone is set. */
+  "--map-points-color"?: (string) | undefined;
+  /** The color of the numbers in counts. */
+  "--map-points-ink"?: (string) | undefined;
+  /** The color of the halo, direction cone, and pulse when no tone is set. */
+  "--map-position-color"?: (string) | undefined;
+  /** The edge around the point and the arrow. */
+  "--map-position-edge"?: (string) | undefined;
+  /** The color of the point and the arrow when no tone is set. */
+  "--map-position-fill"?: (string) | undefined;
+  /** The point's width. */
+  "--map-position-size"?: (string) | undefined;
+  /** The color behind the map while tiles load. */
   "--map-background-color"?: (string) | undefined;
-  /** How tall the frame is. A length, since the map fills it. */
+  /** The frame's height, as a length. */
   "--map-block-size"?: (string) | undefined;
-  /** Color of the frame's edge. */
+  /** The frame's border color. */
   "--map-border-color"?: (string) | undefined;
+  /** The color of the casing under the route. */
+  "--map-route-casing-color"?: (string) | undefined;
+  /** The route's color when no tone is set. */
+  "--map-route-color"?: (string) | undefined;
   /** A filter behind the panel, which is `none` until one is asked for: this family carries no `material`, so the pair is two hooks rather than a word. */
   "--megamenu-backdrop"?: (string) | undefined;
   /** The panel's own fill. */
@@ -14119,12 +14388,42 @@ export interface WcToolkitVueGlobalComponents {
     HelixLoaderVueProps,
     HelixLoaderVueEvents
   >;
-  /** Presentation only: a bordered well with the controls over it, at the corner every map puts them. What the frame is for, and why the controls are buttons rather than arrow keys, is the base class.  **The controls do not fade with the chrome.** A reader who has gone still has not stopped needing the only controls this frame offers, so the idle state takes the header and footer a consumer slotted and leaves the buttons alone. */
+  /** Fills the area in your theme's colors. Uses your primary color unless 'tone' sets another. */
+  "helix-map-area": DefineCustomElement<
+    HelixMapArea,
+    HelixMapAreaVueProps,
+    HelixMapAreaVueEvents
+  >;
+  /** A point in your theme's colors with the place's name beside it. Uses your primary color unless 'tone' sets another. */
+  "helix-map-marker": DefineCustomElement<
+    HelixMapMarker,
+    HelixMapMarkerVueProps,
+    HelixMapMarkerVueEvents
+  >;
+  /** Draws the points in your theme's colors, with counts in white on your primary color unless 'tone' sets another. */
+  "helix-map-points": DefineCustomElement<
+    HelixMapPoints,
+    HelixMapPointsVueProps,
+    HelixMapPointsVueEvents
+  >;
+  /** Draws the position in your theme's foreground color with a surface-colored edge, or in a 'tone'. A position with a heading is drawn as an arrow. */
+  "helix-map-position": DefineCustomElement<
+    HelixMapPosition,
+    HelixMapPositionVueProps,
+    HelixMapPositionVueEvents
+  >;
+  /** The styled frame: a bordered box with the pan and zoom buttons in its top corner. The buttons stay visible when the header and footer fade. */
   "helix-map": DefineCustomElement<
     HelixMap,
     HelixMapVueProps,
     HelixMapVueEvents
   >;
+  /** Draws the route in your theme's colors, with a surface-colored casing under it so it stands out from the roads. Uses your primary color unless 'tone' sets another. */
+  "helix-map-route": DefineCustomElement<
+    HelixMapRoute,
+    HelixMapRouteVueProps,
+    HelixMapRouteVueEvents
+  >;
   /** Presentation only: the trigger, and the panel it opens as a grid of columns. Everything about what opens it and what closes it is the base class. */
   "helix-megamenu": DefineCustomElement<
     HelixMegamenu,