@fusion.dev/helix-headless 0.158.0 → 0.160.0

package/custom-elements.json

@@ -2303,7 +2303,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Tracks whether the page has scrolled and sets the custom state `scrolled`, so\nthe styled tier can lift the bar without a scroll handler of its own. The\nstate is read when the element connects. A fresh load starts at the top,\nwhich matches the server markup, and a reload partway down the page is\ncorrected on hydration.\n\nThe element uses a custom state because an attribute such as `data-scrolled`,\nwritten onto its own host, is one the server did not send. A hydrating\nframework would report a mismatch whenever the page reloads far enough down.\n`ElementInternals.states` is not in the DOM, so hydration has nothing to\ncompare. Select the state with `:state(scrolled)`.\n\nThe page is the window unless `scroller` names the element that scrolls, for\nan app shell whose content scrolls inside a container.\n\n**Set `hide-on-scroll` for a bar that moves out of the way.** Scrolling down\npast the bar's own height hides it, and scrolling up shows it again, as does\nfocus moving into it. The custom state `hidden` is on the host while it is\nhidden, and the styled tier slides a `sticky` bar up out of view.\n\n**Set `fold-below` to fold the middle region on a narrow screen.** Below that\nmany pixels of the bar's own width, the middle region is hidden behind a\ntoggle at the end of the bar, named by `menu-label`. The toggle says whether\nthe region is open with `aria-expanded`, and the region opens below the row.\nEscape closes it and puts focus back on the toggle. The custom state\n`folded` is on the host while the bar is that narrow, and `open` while the\nfolded region is open. A server serves the bar unfolded, and the browser\nfolds it once it has measured it.\n\nThe host is the page's `banner` landmark. Placed inside `main`, `article`,\n`aside`, `nav` or `section`, it is a plain box instead, as a native\n`<header>` is there, so a header inside a card or a pane does not add a\nsecond banner. The ancestors are read as the accessibility tree reads them,\nthrough the slots that take the header in, so one slotted into a component\nthat draws a `<nav>`, such as `Navigation`, is not a banner either. A server\ncannot see the ancestors, so it serves the banner and the browser corrects\nit when the element connects.",
+          "description": "Tracks whether the page has scrolled and sets the custom state `scrolled`, so\nthe styled tier can lift the bar without a scroll handler of its own. The\nstate is read when the element connects. A fresh load starts at the top,\nwhich matches the server markup, and a reload partway down the page is\ncorrected on hydration.\n\nThe element uses a custom state because an attribute such as `data-scrolled`,\nwritten onto its own host, is one the server did not send. A hydrating\nframework would report a mismatch whenever the page reloads far enough down.\n`ElementInternals.states` is not in the DOM, so hydration has nothing to\ncompare. Select the state with `:state(scrolled)`.\n\nThe page is the window unless `scroller` names the element that scrolls, for\nan app shell whose content scrolls inside a container.\n\n**Set `hide-on-scroll` for a bar that moves out of the way.** Scrolling down\npast the bar's own height hides it, and scrolling up shows it again, as does\nfocus moving into it. The custom state `hidden` is on the host while it is\nhidden, and the styled tier slides a `sticky` bar up out of view.\n\n**Set `fold-below` to fold the middle region on a narrow screen.** Below that\nmany pixels of the bar's own width, the middle region is hidden behind a\ntoggle at the end of the bar, named by `menu-label`, or at its start with\n`toggle-placement=\"start\"`. The toggle says whether the region is open with\n`aria-expanded`, and the region opens below the row. The region follows the\ntoggle's region in focus order, so Tab from the toggle at the end goes into\nthe open region. The custom state `folded` is on the host while the bar is\nthat narrow, and `open` while the folded region is open. A server serves the\nbar unfolded, and the browser folds it once it has measured it.\n\n**`open` says whether the folded region is open, and setting it opens or\ncloses the region.** `requestOpen(true)` and `requestOpen(false)` do the same\nand send `helix-before-open` or `helix-before-close` first, which you can\ncancel, and `toggleOpen()` asks for the opposite. `toggle` follows every\nchange. The region closes on Escape, which puts focus back on the toggle,\nwhen focus moves to something outside the header, and on a press outside\nit. A bar that widens past `fold-below` closes its region.\n\nThe host is the page's `banner` landmark. Placed inside `main`, `article`,\n`aside`, `nav` or `section`, it is a plain box instead, as a native\n`<header>` is there, so a header inside a card or a pane does not add a\nsecond banner. The ancestors are read as the accessibility tree reads them,\nthrough the slots that take the header in, so one slotted into a component\nthat draws a `<nav>`, such as `Navigation`, is not a banner either. A server\ncannot see the ancestors, so it serves the banner and the browser corrects\nit when the element connects.",
           "name": "HelixHeadlessAppHeader",
           "cssParts": [
             {
@@ -2389,6 +2389,19 @@
               "description": "Hides the bar as the page scrolls down past it, and shows it again as the\npage scrolls up.",
               "attribute": "hide-on-scroll"
             },
+            {
+              "kind": "field",
+              "name": "menuLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Menu'",
+              "description": "The name of the toggle that opens a folded middle region.",
+              "attribute": "menu-label",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "folded",
@@ -2406,8 +2419,8 @@
                 "text": "boolean"
               },
               "privacy": "private",
-              "default": "false",
-              "description": "Whether the folded middle region is open."
+              "description": "Whether the folded middle region is open and showing.",
+              "readonly": true
             },
             {
               "kind": "field",
@@ -2446,7 +2459,7 @@
                   }
                 }
               ],
-              "description": "Folds the middle region where the bar is narrower than `fold-below`."
+              "description": "Folds the middle region where the bar is narrower than `fold-below`. A bar\nthat widens closes its region, so it starts closed when it folds again;\none that narrows keeps an `open` you set."
             },
             {
               "kind": "field",
@@ -2462,6 +2475,41 @@
               "readonly": true,
               "description": "Escape in the open region closes it and puts focus back on the toggle."
             },
+            {
+              "kind": "field",
+              "name": "handleFocusOut",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Closes the open region when focus moves to something outside the header.\nFocus leaving the window has no `relatedTarget`, and closes nothing."
+            },
+            {
+              "kind": "field",
+              "name": "handleOutsidePress",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Closes the open region on a press outside the header."
+            },
+            {
+              "kind": "field",
+              "name": "pressing",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the outside press is listened for, which is while the region is open."
+            },
+            {
+              "kind": "method",
+              "name": "watchPresses",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Listens for a press outside while the folded region is open, and only then."
+            },
             {
               "kind": "field",
               "name": "away",
@@ -2529,25 +2577,22 @@
             },
             {
               "kind": "field",
-              "name": "menuLabel",
+              "name": "scroller",
               "type": {
-                "text": "string"
+                "text": "string | undefined"
               },
-              "default": "'Menu'",
-              "description": "The name of the toggle that opens a folded middle region.",
-              "attribute": "menu-label",
-              "helix": {
-                "words": true
-              }
+              "description": "The id of the element whose scrolling lifts the bar, for an app shell that\nscrolls a container instead of the window. Unset is the window.",
+              "attribute": "scroller"
             },
             {
               "kind": "field",
-              "name": "scroller",
+              "name": "togglePlacement",
               "type": {
-                "text": "string | undefined"
+                "text": "'start' | undefined"
               },
-              "description": "The id of the element whose scrolling lifts the bar, for an app shell that\nscrolls a container instead of the window. Unset is the window.",
-              "attribute": "scroller"
+              "description": "Where the toggle that opens a folded middle region sits: at the end of the\nbar, after the trailing content, or with `start`, before the leading\ncontent.\n\nOptional, so the resting bar writes no attribute onto the host.",
+              "attribute": "toggle-placement",
+              "reflects": true
             },
             {
               "kind": "field",
@@ -2636,6 +2681,126 @@
               },
               "description": "The glyph on the toggle that opens a folded middle region, behind a seam:\nslot fallback, so a consumer replaces it by slotting, and a method, so a\ntier above replaces it by overriding."
             },
+            {
+              "kind": "field",
+              "name": "defaultOpen",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the element starts open. Ignored once `open` is written.",
+              "attribute": "default-open",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "open",
+              "type": {
+                "text": "boolean"
+              },
+              "description": "Whether the element is open.\n\nOne property, not two, so `dialog.open` answers the question anyone\nasking it meant. Writing always applies; `<helix-dialog open>` is the\nsame statement in markup.\n\n**Not reflected, and that is required rather than tidy.** Reflection\nwrites the resolved state back as an attribute, so an element that opened\nitself would put `open` on its own host: cloned, serialized for\nhydration, or diffed by a framework, it comes back holding whatever the\nlast reader did rather than what the author wrote. `:state(open)` carries\nthe resolved state for stylesheets, which is what the mirror is for.",
+              "attribute": "open",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "openState",
+              "type": {
+                "text": "boolean | undefined"
+              },
+              "privacy": "private",
+              "default": "undefined",
+              "description": "The state, whoever set it, and `undefined` until somebody has.\n\nPrefixed, and it has to be. These mixins compose onto one prototype\nchain, `Select` takes this one and `MixinControllerValue` together, and\nTypeScript's `private` is a compile-time fiction: two mixins with a field\ncalled `state` share one property on the instance, and the second one\nsilently overwrites the first. Measured, as a select whose `value` came\nback holding its `open` boolean.\n\nOne field and not two. Writing always applies, the way a native control\ndoes when a script assigns to it.",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "announcedOpen",
+              "type": {
+                "text": "boolean | undefined"
+              },
+              "privacy": "private",
+              "default": "undefined",
+              "description": "The state `toggle` last reported, and `undefined` before the first update.\n\n`requestOpen` announces at once. An assignment to `open` announces here,\nonce it has rendered, so a consumer binding `toggle` hears every change\nthat a `close` listener on a dialog hears. The first update sets it and\nannounces nothing, because a seed is where the element starts.",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "requestOpen",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "next",
+                  "type": {
+                    "text": "boolean"
+                  }
+                }
+              ],
+              "description": "Requests that the element open or close, and returns whether the change\nwas applied.\n\nAnnounces before it acts, so `preventDefault()` on the `helix-before-open` or\n`helix-before-close` is a refusal and nothing moves. Nobody refusing means the\nelement opens or closes itself, whether or not a consumer declared\n`open`: a declared property is a seed and a correction, and a consumer\nwho wants the decision for themselves refuses it and assigns their own.",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              },
+              "type": {
+                "text": "requestOpen(next: boolean) => boolean"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "announceToggle",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "open",
+                  "type": {
+                    "text": "boolean"
+                  }
+                }
+              ],
+              "description": "Says the state moved, under the platform's own name and in its shape.\n\n**A native `toggle` from inside a shadow root reaches nobody**, because\nit neither bubbles nor composes, so the ten families showing a\n`popover=\"manual\"` panel and the two rendering a real `<dialog>` announce\nnothing to a consumer. The disclosures have no native element to fire\nanything at all: `AccordionItem` and `TreeItem` are `aria-expanded` and\n`hidden` written by hand, which is `<details>`'s job done manually.\n\n**From here rather than from `PopoverController`.** The controller covers\neleven families and the mixin covers sixteen, so announcing from both\nwould announce twice on the ten they share. What `toggle` reports is the\n*state*, and the state is this mixin's; the controller is a way of\nputting a panel on the screen.\n\n**`newState` and `oldState`, because that is the platform's shape**, so a\nconsumer arriving from `<details>` reads the same two words. Not\ncancelable: the before events are the request, and a second cancelable\nevent for one transition is two answers to one question.",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "toggleOpen",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "description": "Requests the opposite of the current state.",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              },
+              "type": {
+                "text": "toggleOpen() => boolean"
+              }
+            },
             {
               "kind": "field",
               "name": "tier",
@@ -2977,6 +3142,22 @@
             }
           ],
           "events": [
+            {
+              "type": {
+                "text": "HelixBeforeCloseEvent"
+              },
+              "description": "The folded region is about to close. Cancelable: cancel it to keep it open.",
+              "name": "helix-before-close",
+              "reactProp": "onhelix-before-close"
+            },
+            {
+              "type": {
+                "text": "HelixBeforeOpenEvent"
+              },
+              "description": "The folded region is about to open. Cancelable: cancel it to keep it closed.",
+              "name": "helix-before-open",
+              "reactProp": "onhelix-before-open"
+            },
             {
               "type": {
                 "text": "HelixScrolledEvent"
@@ -2984,6 +3165,18 @@
               "description": "Fired when the page crosses the scroll threshold, with the new state. A custom state cannot be observed the way an attribute can, so listen for this event to follow it. The event uses the header's own threshold and hysteresis, so you do not need a second scroll listener.",
               "name": "helix-scrolled",
               "reactProp": "onhelix-scrolled"
+            },
+            {
+              "name": "toggle",
+              "type": {
+                "text": "ToggleEvent"
+              },
+              "description": "The folded region opened or closed. The event carries `newState` and `oldState`.",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              },
+              "reactProp": "ontoggle"
             }
           ],
           "attributes": [
@@ -3028,6 +3221,39 @@
               },
               "description": "The id of the element whose scrolling lifts the bar, for an app shell that\nscrolls a container instead of the window. Unset is the window.",
               "fieldName": "scroller"
+            },
+            {
+              "name": "toggle-placement",
+              "type": {
+                "text": "'start' | undefined"
+              },
+              "description": "Where the toggle that opens a folded middle region sits: at the end of the\nbar, after the trailing content, or with `start`, before the leading\ncontent.\n\nOptional, so the resting bar writes no attribute onto the host.",
+              "fieldName": "togglePlacement"
+            },
+            {
+              "name": "default-open",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the element starts open. Ignored once `open` is written.",
+              "fieldName": "defaultOpen",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              }
+            },
+            {
+              "name": "open",
+              "type": {
+                "text": "boolean"
+              },
+              "description": "Whether the element is open.\n\nOne property, not two, so `dialog.open` answers the question anyone\nasking it meant. Writing always applies; `<helix-dialog open>` is the\nsame statement in markup.\n\n**Not reflected, and that is required rather than tidy.** Reflection\nwrites the resolved state back as an attribute, so an element that opened\nitself would put `open` on its own host: cloned, serialized for\nhydration, or diffed by a framework, it comes back holding whatever the\nlast reader did rather than what the author wrote. `:state(open)` carries\nthe resolved state for stylesheets, which is what the mirror is for.",
+              "fieldName": "open",
+              "inheritedFrom": {
+                "name": "MixinControllerOpen",
+                "module": "src/mixins/mixin-controller-open/mixin-controller-open.ts"
+              }
             }
           ],
           "cssStates": [
@@ -3056,6 +3282,12 @@
               }
             }
           ],
+          "mixins": [
+            {
+              "name": "MixinControllerOpen",
+              "package": "@fusion.dev/helix-core"
+            }
+          ],
           "superclass": {
             "name": "HelixElement",
             "package": "@fusion.dev/helix-core"
@@ -10275,7 +10507,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Sets `role=\"group\"` on the host through internals, and `label` names the\ngroup. Without a name, a screen reader announces the buttons as separate\ncontrols, and a development build warns once with the kind `missing-name`.\n\nThe group does not manage focus, so each button keeps its own tab stop. For\none tab stop with arrow keys between a mix of controls, the APG toolbar\npattern, use Toolbar.\n\nButtons are slotted, so they stay your own elements and keep their own\nappearance and size.\n\n**Buttons that stay pressed.** With `selection-mode`, each button with a\n`value` is a toggle button: a press presses or releases it, and it says so\nwith `aria-pressed`. `single` keeps one pressed at a time, and a press on the\npressed one releases it. `multiple` lets any number be pressed. `value` is\nthe pressed values, comma separated. A press sends a cancelable\n`helix-before-change` with the value it would leave, then `change`.\n\nThe pressed state is written on the control inside each button's shadow\nroot, so the markup you rendered is never changed and a framework hydrating\nit sees what its server sent. That is also why only Helix buttons are\ntoggles: a native `<button>` or a button without a `value` stays a plain\naction button in the group, and a native one without its own\n`aria-pressed` warns once, with the runtime kind `untold-toggle`. The inner\ncontrol also carries\n`--button-group-pressed`, `1` or `0`, for a `::part(button)` rule of yours.\n\nUse Toggle Group instead for a choice that belongs in a form, or one where\nthe arrow keys choose as they move: it is a `radiogroup` of options with a\nform value, `required` and validation. A Button Group in a selection mode is\na set of actions that stay on, such as bold and italic, or a view that a\npress switches, and it submits nothing.\n\n**Keyboard.** In a selection mode the group is one tab stop: the button\nfocus was last on, then the first pressed one, then the first one.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Moves to the next button, from the last back to the first. |\n| Left, Up | Moves to the button before, from the first round to the last. |\n| Home, End | Moves to the first or the last button. |\n| Space, Enter | Presses or releases the focused button. |\n\nLeft and Right swap on a right-to-left page, and a disabled button is\npassed over. In a selection mode the group is a `toolbar`, with\n`aria-orientation` under `orientation=\"vertical\"`. Inside a toolbar it stays\na named `group`, and the toolbar's own arrow keys walk its buttons, so a\nreader meets one toolbar.",
+          "description": "Sets `role=\"group\"` on the host through internals, and `label` names the\ngroup. Without a name, a screen reader announces the buttons as separate\ncontrols, and a development build warns once with the kind `missing-name`.\n\nThe group does not manage focus, so each button keeps its own tab stop. For\none tab stop with arrow keys between a mix of controls, the APG toolbar\npattern, use Toolbar.\n\nButtons are slotted, so they stay your own elements and keep their own\nappearance and size.\n\n**Buttons that stay pressed.** With `selection-mode`, each button with a\n`value` is a toggle button: a press presses or releases it. `multiple` lets\nany number be pressed, and each button says so with `aria-pressed`. `single`\nkeeps one pressed at a time: the group is a `radiogroup` and each button a\n`radio` that says so with `aria-checked`, as React Aria's toggle button\ngroup is. A press on the pressed one releases it, unless\n`disallow-empty-selection` keeps one pressed. `value` is the pressed values,\ncomma separated. A press sends a cancelable `helix-before-change` with the\nvalue it would leave, then `change`. A pressed Helix button has\n`:state(pressed)` on its own element.\n\nThe pressed state is written on the control inside each button's shadow\nroot, so the markup you rendered is never changed and a framework hydrating\nit sees what its server sent. That is also why only Helix buttons are\ntoggles: a native `<button>` or a button without a `value` stays a plain\naction button in the group, and a native one without its own\n`aria-pressed` warns once, with the runtime kind `untold-toggle`. The inner\ncontrol also carries\n`--button-group-pressed`, `1` or `0`, for a `::part(button)` rule of yours.\n\nUse Toggle Group instead for a choice that belongs in a form, or one where\nthe arrow keys choose as they move: it is a `radiogroup` of options with a\nform value, `required` and validation. A Button Group in a selection mode is\na set of actions that stay on, such as bold and italic, or a view that a\npress switches, and it submits nothing.\n\n**Keyboard.** In a selection mode the group is one tab stop: the button\nfocus was last on, then the first pressed one, then the first one.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Moves to the next button, from the last back to the first. |\n| Left, Up | Moves to the button before, from the first round to the last. |\n| Home, End | Moves to the first or the last button. |\n| Space, Enter | Presses or releases the focused button. |\n\nLeft and Right swap on a right-to-left page, and a disabled button is\npassed over. Under `multiple` the group is a `toolbar`, with\n`aria-orientation` under `orientation=\"vertical\"`. Inside a toolbar it stays\na named `group`, and the toolbar's own arrow keys walk its buttons, so a\nreader meets one toolbar. Under `single` it is a `radiogroup` either way.",
           "name": "HelixHeadlessButtonGroup",
           "cssProperties": [
             {
@@ -10290,6 +10522,16 @@
             }
           ],
           "members": [
+            {
+              "kind": "field",
+              "name": "disallowEmptySelection",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Keeps at least one button pressed once one is, as React Aria's\n`disallowEmptySelection`: a press that would leave none pressed is\nrefused.",
+              "attribute": "disallow-empty-selection"
+            },
             {
               "kind": "field",
               "name": "label",
@@ -10479,7 +10721,7 @@
                   "description": "Whether the button is pressed, or undefined where it is not a toggle."
                 }
               ],
-              "description": "Says on a button's control whether it is pressed, or that it is no toggle\nat all where `pressed` is undefined. A styled tier draws the look here."
+              "description": "Says on a button's control whether it is pressed, or that it is no toggle\nat all where `pressed` is undefined. A styled tier draws the look here.\n\nUnder `single` the control is a `radio` that says so with `aria-checked`,\nand under `multiple` a toggle button that says so with `aria-pressed`."
             },
             {
               "kind": "field",
@@ -10861,6 +11103,15 @@
             }
           ],
           "attributes": [
+            {
+              "name": "disallow-empty-selection",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Keeps at least one button pressed once one is, as React Aria's\n`disallowEmptySelection`: a press that would leave none pressed is\nrefused.",
+              "fieldName": "disallowEmptySelection"
+            },
             {
               "name": "label",
               "type": {
@@ -12343,6 +12594,10 @@
               "description": "The button is pending: `pending` is set.",
               "name": "pending"
             },
+            {
+              "description": "A Button Group in a selection mode has this button pressed.",
+              "name": "pressed"
+            },
             {
               "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
               "name": "settled",
@@ -35523,6 +35778,20 @@
                 "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "touched",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the reader has committed an answer, or a form has refused the\npicker. A reset forgets it.",
+              "inheritedFrom": {
+                "name": "MixinPickerFeedback",
+                "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "marked",
@@ -35530,13 +35799,44 @@
                 "text": "boolean"
               },
               "privacy": "protected",
-              "description": "Whether a reader is told the answer is wrong: `invalid`, or `feedback`.",
+              "description": "Whether a reader is told the answer is wrong: `invalid`, `feedback`, a\nheld answer the picker refuses, or a missing answer once the reader has\ncommitted one or a form has refused the picker.\n\n**A refused answer is marked at once, and a missing one waits**, as\nChromium's tree does for native controls: a time input holding a time\npast its `max` reports invalid on load, and an empty required text field\ndoes not, since the reader already hears that it is required. Measured\nbefore this on Time Picker: `value=\"13:00\" max=\"12:00\"` reported\n`rangeOverflow` while the list said nothing and `:state(invalid)` was off.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "MixinPickerFeedback",
                 "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "failure",
+              "type": {
+                "text": "'missing' | 'refused' | undefined"
+              },
+              "privacy": "protected",
+              "description": "What the picker's own validation finds: `missing`, `refused`, or\nnothing, which is what a picker that does not answer it reports.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinPickerFeedback",
+                "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "formResetCallback",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Returns the control to its `defaultValue`, or to its `value` attribute\nwhere there is no `default-value`.\n\nBoth halves are dropped, the consumer's and the control's, because a\nreset means the form is as it was served. Clearing only the internal one\nwould leave a control that had been written to stuck at that value.",
+              "inheritedFrom": {
+                "name": "HelixFormElement",
+                "module": "src/helix-form-element/helix-form-element.ts"
+              },
+              "type": {
+                "text": "formResetCallback() => void"
+              }
+            },
             {
               "kind": "method",
               "name": "renderPickerFeedback",
@@ -35622,23 +35922,6 @@
                 "module": "src/mixins/mixin-controller-value/mixin-controller-value.ts"
               }
             },
-            {
-              "kind": "method",
-              "name": "formResetCallback",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "description": "Returns the control to its `defaultValue`, or to its `value` attribute\nwhere there is no `default-value`.\n\nBoth halves are dropped, the consumer's and the control's, because a\nreset means the form is as it was served. Clearing only the internal one\nwould leave a control that had been written to stuck at that value.",
-              "inheritedFrom": {
-                "name": "HelixFormElement",
-                "module": "src/helix-form-element/helix-form-element.ts"
-              },
-              "type": {
-                "text": "formResetCallback() => void"
-              }
-            },
             {
               "kind": "method",
               "name": "formStateRestoreCallback",
@@ -43308,6 +43591,14 @@
                 "module": "src/button/root/button-root.ts"
               }
             },
+            {
+              "description": "A Button Group in a selection mode has this button pressed.",
+              "name": "pressed",
+              "inheritedFrom": {
+                "name": "HelixHeadlessButton",
+                "module": "src/button/root/button-root.ts"
+              }
+            },
             {
               "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
               "name": "settled",
@@ -47567,9 +47858,13 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The calendar is `DatePicker`, which handles months, ranges, disabled days,\nthe first day of the week, and the grid's keyboard behavior. The date input\nadds the field, the overlay, and the connection between them.\n\nYou can type a date as well as pick one. The native `<input type=\"date\">`\ngives a picker and locale formatting but allows almost no styling, so the\nfield is a text field. Typing sends `input` on each keystroke and `change`\nwhen you leave the field, as a text field does. A date picked from the\ncalendar sends both.\n\nThe trigger and ArrowDown open the calendar with focus on the selected day,\nTab moves between the calendar's controls without leaving it, and Escape\ncloses it and returns focus to the field. A press into the field opens the\ncalendar too. Tab into the field opens nothing, and Tab out of the field\ncloses the calendar.\n\nWith `segmented`, the field is a row of segments in place of the text: a\nmonth, a day and a year in the order the locale writes them, each set with\ndigits or the arrow keys. Alt+Down opens the calendar from a segment.\n\nText that is not a date gives the form an empty value, as a native date\nfield does, and `value` keeps the text so it can be corrected.\n\n**Keyboard.** The field is one tab stop, or each segment is with\n`segmented`, and the trigger is one more.\n\n| Key | What it does |\n|---|---|\n| Down | In the text field, opens the calendar with focus on the chosen day. |\n| Alt with Down | Opens the calendar, from the text field or a segment. |\n| Enter | In the text field, takes the typed date and submits the form, as a native field does. |\n| Escape | Closes the calendar and puts focus back in the field. |\n| Tab | In the open calendar, moves between its controls. Out of the field, closes it. |\n| Up, Down on a segment | Steps the segment by one, round from its last value to its first. |\n| Page Up, Page Down on a segment | Steps by a page: a week of days, two months, or five years. |\n| Home, End on a segment | Goes to the segment's first or last value. |\n| Digits on a segment | Fill it, and move to the next once it can take no more. |\n| Backspace, Delete on a segment | Empty the segment. |\n| Left, Right on a segment | Move to the previous or the next segment, along the line of text. |\n\nIn the calendar, the keys are `DatePicker`'s: the arrows move by a day or a\nweek, Page Up and Page Down by a month, with Shift by a year, and Home and\nEnd to the start and the end of the week.",
+          "description": "The calendar is `DatePicker`, which handles months, ranges, disabled days,\nthe first day of the week, and the grid's keyboard behavior. The date input\nadds the field, the overlay, and the connection between them.\n\nYou can type a date as well as pick one. The native `<input type=\"date\">`\ngives a picker and locale formatting but allows almost no styling, so the\nfield is a text field. Typing sends `input` on each keystroke and `change`\nwhen you leave the field, as a text field does. A date picked from the\ncalendar sends both. The field reads ISO, `2026-08-04`, and a date written\nin the order, the digits, and the month names of `locale`, `8/4/2026` or\n`Aug 4, 2026` in `en-US` and `4.8.2026` in `de-DE`, which becomes the value\nas you leave the field.\n\nThe trigger and ArrowDown open the calendar with focus on the selected day,\nTab moves between the calendar's controls without leaving it, and Escape\ncloses it and returns focus to the field. A press into the field opens the\ncalendar too. Tab into the field opens nothing, and Tab out of the field\ncloses the calendar. The text field is a `combobox` with\n`aria-haspopup=\"dialog\"`, `aria-expanded`, and `aria-controls`, as in the\nAPG date picker combobox, since Down opens the calendar from it.\n\nWith `segmented`, the field is a row of segments in place of the text: a\nmonth, a day and a year in the order the locale writes them, each set with\ndigits or the arrow keys. Alt+Down opens the calendar from a segment. A\n`range` is two rows with a dash between them, the start and the end, as\nReact Aria's DateRangePicker draws them, and `multiple` keeps the text.\n\nText that is not a date gives the form an empty value, as a native date\nfield does, and `value` keeps the text so it can be corrected.\n\n**Keyboard.** The field is one tab stop, or each segment is with\n`segmented`, and the trigger is one more.\n\n| Key | What it does |\n|---|---|\n| Down | In the text field, opens the calendar with focus on the chosen day. |\n| Alt with Down | Opens the calendar, from the text field or a segment. |\n| Enter | In the text field, takes the typed date and submits the form, as a native field does. |\n| Escape | Closes the calendar and puts focus back in the field. |\n| Tab | In the open calendar, moves between its controls. Out of the field, closes it. |\n| Up, Down on a segment | Steps the segment by one, round from its last value to its first. |\n| Page Up, Page Down on a segment | Steps by a page: a week of days, two months, or five years. |\n| Home, End on a segment | Goes to the segment's first or last value. |\n| Digits on a segment | Fill it, and move to the next once it can take no more. |\n| Backspace, Delete on a segment | Empty the segment. |\n| Left, Right on a segment | Move to the previous or the next segment, along the line of text. |\n\nIn the calendar, the keys are `DatePicker`'s: the arrows move by a day or a\nweek, Page Up and Page Down by a month, with Shift by a year, and Home and\nEnd to the start and the end of the week.",
           "name": "HelixHeadlessDateInput",
           "cssParts": [
+            {
+              "description": "The button that empties the field, under `clearable`, while it holds a date.",
+              "name": "clear"
+            },
             {
               "description": "The text input.",
               "name": "control"
@@ -47734,6 +48029,10 @@
               "description": "The icon on the previous month control.",
               "name": "picker-previous-mark"
             },
+            {
+              "description": "The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.",
+              "name": "picker-selection"
+            },
             {
               "description": "One row of days.",
               "name": "picker-week"
@@ -47742,6 +48041,10 @@
               "description": "A column header naming a day of the week.",
               "name": "picker-weekday"
             },
+            {
+              "description": "The dash between a range's two rows of segments, in `segmented`, beside `literal`.",
+              "name": "range-separator"
+            },
             {
               "description": "The count of dates beyond the ones shown. It is a `<button>` with `expandable` and a `<span>` without it.",
               "name": "rest"
@@ -47776,6 +48079,10 @@
             }
           ],
           "slots": [
+            {
+              "description": "Replaces the cross on the clear button, under `clearable`.",
+              "name": "clear-icon"
+            },
             {
               "description": "Content after the date, before the trigger, such as a clear button.",
               "name": "end"
@@ -47846,16 +48153,16 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "What the browser may autofill here, as one of the platform's own tokens.\n\nEmpty leaves the attribute off, which is the browser's default and is what\nlets autofill work at all: hardcoding `off` here means a birthday or a\npostal code can never be filled in for a reader.",
+              "description": "What the browser may autofill here, as one of the platform's own tokens,\nsuch as `bday`.\n\nEmpty leaves the attribute off, which is the browser's default and is what\nlets autofill work at all: hardcoding `off` here means a birthday or a\npostal code can never be filled in for a reader. With `segmented`, a\nhidden native date input carries it, since no browser fills the segments.",
               "attribute": "autocomplete"
             },
             {
               "kind": "field",
               "name": "calendar",
               "type": {
-                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | undefined"
+                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'chinese' | 'coptic' | 'dangi' | 'ethioaa' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic' | 'islamic-civil' | 'islamic-rgsa' | 'islamic-tbla' | 'islamic-umalqura' | 'persian' | undefined"
               },
-              "description": "The calendar the written date and the calendar's days are in: `gregory`,\n`buddhist`, `japanese`, `roc`, or `iso8601`.\n\nAbsent is the locale's own where it is one of the five, and `gregory` for\nevery other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in\nevery calendar, and a focused field is ISO in every calendar. In\n`segmented`, the segments are the Gregorian day, month, and year, in the\norder the locale writes them, or ISO order for `iso8601`.",
+              "description": "The calendar the written date, the segments, and the calendar's days are\nin: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar\nwith months of its own that Date Picker's `calendar` names, such as\n`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.\n\nAbsent is the locale's own where its months are the Gregorian months, and\n`gregory` for every other, as Date Picker's `calendar` is. The value is\n`YYYY-MM-DD` in every calendar, and a focused text field is ISO in every\ncalendar. In `segmented`, the segments are the day, month, and year as\nthe calendar counts them, in the order the locale writes them: Mehr 14,\n1405 is month 7 and day 14 of 1405 under `persian`. Under the five with\nGregorian months they are the Gregorian day, month, and year, or ISO order\nfor `iso8601`.",
               "attribute": "calendar"
             },
             {
@@ -47871,6 +48178,29 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "clearable",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the field shows a button that empties it, as Input's `clearable`\ndoes. Shown only while the field holds something to clear and is neither\ndisabled nor read-only.",
+              "attribute": "clearable"
+            },
+            {
+              "kind": "field",
+              "name": "clearLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Clear'",
+              "description": "The accessible name of the clear button, which shows only an icon.",
+              "attribute": "clear-label",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "announcesInput",
@@ -47893,7 +48223,7 @@
                 "text": "'full' | 'iso' | 'long' | 'medium' | 'short'"
               },
               "default": "'long'",
-              "description": "How a date is written in the field: `short` through `full`, or ISO.\n\n**The field renders when it is idle and holds the value when it is being\nedited.** A written date is a rendering, and a document being edited must\nnot be a rendering of something else: `Intl.DateTimeFormat` formats and does\nnot parse, so `4 August 2026` cannot be typed back, and writing a parser per\nlocale is how a field ends up rejecting what it just displayed.\n\nThe way out is not to choose between the two but to separate them in time.\nIdle, the field shows `4 August 2026`, which is what a date is for reading.\nFocused, it shows `2026-08-04`, which is what a date is for typing, and it\ngoes back on the way out. Nothing parses a rendering, and nothing is\nread-only, which is what an earlier version of this settled for.\n\nA range is the exception that needs no swap: the dash between its two dates\nis a separator this element understands, so that much reads back either way.\n\n`iso` turns the rendering off, for a field whose reader is entering data\nrather than reading it, or where the ISO form is itself the point.\n\nThe value is always `YYYY-MM-DD` regardless, because that is what a form\nsubmits and what `min` and `max` compare against.",
+              "description": "How a date is written in the field: `short` through `full`, or ISO.\n\n**The field renders when it is idle and holds the value when it is being\nedited.** A written date is a rendering, and a document being edited must\nnot be a rendering of something else: `Intl.DateTimeFormat` formats and does\nnot parse, so a rendering such as `Tuesday, August 4, 2026` is no text to\nedit. The field does read a date typed in the locale's order and digits as\nyou leave it, which covers what a reader types.\n\nThe way out is not to choose between the two but to separate them in time.\nIdle, the field shows `4 August 2026`, which is what a date is for reading.\nFocused, it shows `2026-08-04`, which is what a date is for typing, and it\ngoes back on the way out. Nothing parses a rendering, and nothing is\nread-only, which is what an earlier version of this settled for.\n\nA range is the exception that needs no swap: the dash between its two dates\nis a separator this element understands, so that much reads back either way.\n\n`iso` turns the rendering off, for a field whose reader is entering data\nrather than reading it, or where the ISO form is itself the point.\n\nThe value is always `YYYY-MM-DD` regardless, because that is what a form\nsubmits and what `min` and `max` compare against.",
               "attribute": "date-style"
             },
             {
@@ -48209,6 +48539,19 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "selectionLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{kind, select, date {Selected date: {start}} start {Range starts {start}. Choose the day it ends.} range {Selected range: {start} to {end}} other {{count, plural, one {# date selected} other {# dates selected}}}}'",
+              "description": "What a screen reader hears about the dates chosen in the calendar, with\n`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's\n`selection-label` says.",
+              "attribute": "selection-label",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "step",
@@ -48232,6 +48575,16 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "timeZone",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The time zone today is read in, such as `America/New_York`, handed to the\ncalendar: the day marked today, and the month an empty field opens on.\nEmpty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone.",
+              "attribute": "time-zone"
+            },
             {
               "kind": "field",
               "name": "triggerLabel",
@@ -48262,7 +48615,21 @@
                 "text": "boolean"
               },
               "privacy": "protected",
-              "description": "Segments hold one date, so `range` and `multiple` keep the line of text,\nwhose separators and tags are how those modes write several.",
+              "description": "A row of segments holds one date, and `range` takes two rows with a dash\nbetween them, as React Aria's range fields do. `multiple` keeps the line\nof text, whose tags are how it writes several.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "segmentGroups",
+              "type": {
+                "text": "number"
+              },
+              "privacy": "protected",
+              "description": "How many rows of segments the value takes: two for a range, one otherwise.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "MixinSegmentedField",
@@ -48290,7 +48657,21 @@
                 "text": "string"
               },
               "privacy": "protected",
-              "description": "The segments are the Gregorian day, month and year, which is what they\nhold, in ISO order where the calendar is `iso8601`. A year shown as 2569\nor Reiwa 8 would be a year the segment does not hold.",
+              "description": "The segments are the Gregorian day, month and year, which is what they\nhold, in ISO order where the calendar is `iso8601`. A year shown as 2569\nor Reiwa 8 would be a year the segment does not hold. Under a calendar\nwith months of its own they hold that calendar's parts, so they are laid\nout and named in it.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "segmentSystem",
+              "type": {
+                "text": "MonthSystem | undefined"
+              },
+              "privacy": "protected",
+              "description": "The calendar the segments count in, where it has months of its own.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "MixinSegmentedField",
@@ -48347,6 +48728,32 @@
               "readonly": true,
               "description": "Relayed under this element's name, so a consumer hears one control."
             },
+            {
+              "kind": "method",
+              "name": "read",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "text",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "A date as the reader wrote it, as `YYYY-MM-DD`: ISO as it is, and the\norder, the digits, and the month names of the field's locale and calendar\nread back, so `8/4/2026` in `en-US` is August 4, 2026. Empty where it is\nno date."
+            },
+            {
+              "kind": "field",
+              "name": "handleTextCommit",
+              "privacy": "private",
+              "readonly": true,
+              "description": "The text the reader leaves, read in the field's locale: a date written as\nthe locale writes one becomes the value, as ISO, when the field commits.\nNot on each key, where `8/4/202` is a date in the year 202 and taking it\nwould move the caret mid-year."
+            },
             {
               "kind": "field",
               "name": "handleDraftKey",
@@ -48429,6 +48836,19 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "unreadableMessage",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{mode, select, single {Enter a date as YYYY-MM-DD.} other {Enter dates as YYYY-MM-DD, separated by commas.}}'",
+              "description": "The message for text that is no date, where `bad-input-message` is not\nset. `{mode}` is `single`, `range`, or `multiple`.",
+              "attribute": "unreadable-message",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "yearViewLabel",
@@ -48508,6 +48928,51 @@
               },
               "description": "The mark on the button that opens the calendar, behind a seam.\n\nSlot fallback, so a consumer replaces it by slotting; and a method, so the\ntier above replaces it by overriding.\n\n**A named import rather than `<helix-headless-icon>`**, which loses on\nthree counts. `Icon` indexes the whole icon map at runtime,\n`icons[this.name]`, and no bundler can shake a runtime lookup, so every\nconsumer of any component that renders one ships all 50kB of path data; a\nnamed import ships one path. The import is checked when the package\ncompiles, where a `name` string is checked only by a later name lookup. And\n`Icon` is not registered on the headless tier at all, which registers\n`helix-headless-icon`, so a headless consumer gets an inert unknown element\nand no mark whatsoever."
             },
+            {
+              "kind": "method",
+              "name": "renderAutofill",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "TemplateResult | typeof nothing"
+                }
+              },
+              "description": "A native date input a browser's autofill can fill, where the field shows\nsegments: a row of spans that no browser fills. React Aria's\n`HiddenDateInput` is the same answer for its segmented field.\n\nDrawn and never seen, a pixel and see-through, as Select's hidden select\nis, since Safari skips a field that is `display: none`. `aria-hidden` and\nout of the tab order, and in this shadow root, so the form still takes\nthe value once, from the host. A fill is taken as a pick, with `input`\nand `change` from the host."
+            },
+            {
+              "kind": "field",
+              "name": "handleAutofill",
+              "privacy": "private",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "showsClear",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "description": "Whether there is a clear button on screen right now.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handleClear",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Empties the field, through `requestValue` so a consumer who owns the\nvalue decides, then says `change` and `helix-clear` and puts focus back\nin the field, the button having gone."
+            },
+            {
+              "kind": "method",
+              "name": "renderClearIcon",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "TemplateResult"
+                }
+              },
+              "description": "The cross on the clear button, behind a seam a tier can move."
+            },
             {
               "kind": "method",
               "name": "renderControl",
@@ -48586,6 +49051,40 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "rangeEndLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'End'",
+              "description": "What a screen reader hears before the segments of a range's second date\nor time, after each segment's own name.",
+              "attribute": "range-end-label",
+              "helix": {
+                "words": true
+              },
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "rangeStartLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Start'",
+              "description": "What a screen reader hears before the segments of a range's first date\nor time, after each segment's own name: \"month, Start, Stay\".",
+              "attribute": "range-start-label",
+              "helix": {
+                "words": true
+              },
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "segmented",
@@ -48604,11 +49103,11 @@
               "kind": "field",
               "name": "parts",
               "type": {
-                "text": "Segments"
+                "text": "Segments[]"
               },
               "privacy": "private",
-              "default": "{}",
-              "description": "The parts set so far, which may be fewer than a whole value.",
+              "default": "[{}]",
+              "description": "The parts set so far in each row, which may be fewer than a whole\nvalue: one row, or two for a range.",
               "inheritedFrom": {
                 "name": "MixinSegmentedField",
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
@@ -48667,6 +49166,35 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "opener",
+              "type": {
+                "text": "HTMLElement | undefined"
+              },
+              "privacy": "private",
+              "default": "undefined",
+              "description": "The segment Alt+Down opened the picker from, which focus goes back to.",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "returnFocus",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Puts focus back on the segment the picker was opened from, as the\ntrigger takes it back to the field. Measured before this: Escape after\nAlt+Down on AM/PM put focus on the hour.",
+              "inheritedFrom": {
+                "name": "MixinPickerField",
+                "module": "src/mixins/mixin-picker-field/mixin-picker-field.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "segmentsShown",
@@ -48681,6 +49209,52 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "joined",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "rows",
+                  "type": {
+                    "text": "readonly Segments[]"
+                  }
+                }
+              ],
+              "description": "The value the rows add up to: each row's, joined by commas, or empty while any row is not whole.",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "rowsOf",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "Segments[]"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "value",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "The rows a value names, one per row, empty where it names none.",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "segmentOptions",
@@ -48760,6 +49334,12 @@
                 }
               },
               "parameters": [
+                {
+                  "name": "row",
+                  "type": {
+                    "text": "number"
+                  }
+                },
                 {
                   "name": "next",
                   "type": {
@@ -49197,21 +49777,6 @@
                 "module": "src/mixins/mixin-picker-field/mixin-picker-field.ts"
               }
             },
-            {
-              "kind": "method",
-              "name": "returnFocus",
-              "privacy": "protected",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "description": "Puts the caret back in the field without the field reopening the panel.\n\nThe anchor rather than the text, which is the trigger where there is no\ntext: Color Input's swatch dropped focus to the body on Escape.",
-              "inheritedFrom": {
-                "name": "MixinPickerField",
-                "module": "src/mixins/mixin-picker-field/mixin-picker-field.ts"
-              }
-            },
             {
               "kind": "method",
               "name": "focus",
@@ -50870,6 +51435,14 @@
               "name": "helix-before-open",
               "reactProp": "onhelix-before-open"
             },
+            {
+              "type": {
+                "text": "HelixClearEvent"
+              },
+              "description": "Fired after the clear button has emptied the field, after `input` and `change`.",
+              "name": "helix-clear",
+              "reactProp": "onhelix-clear"
+            },
             {
               "type": {
                 "text": "Event"
@@ -50898,15 +51471,15 @@
                 "text": "string"
               },
               "default": "''",
-              "description": "What the browser may autofill here, as one of the platform's own tokens.\n\nEmpty leaves the attribute off, which is the browser's default and is what\nlets autofill work at all: hardcoding `off` here means a birthday or a\npostal code can never be filled in for a reader.",
+              "description": "What the browser may autofill here, as one of the platform's own tokens,\nsuch as `bday`.\n\nEmpty leaves the attribute off, which is the browser's default and is what\nlets autofill work at all: hardcoding `off` here means a birthday or a\npostal code can never be filled in for a reader. With `segmented`, a\nhidden native date input carries it, since no browser fills the segments.",
               "fieldName": "autocomplete"
             },
             {
               "name": "calendar",
               "type": {
-                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | undefined"
+                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'chinese' | 'coptic' | 'dangi' | 'ethioaa' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic' | 'islamic-civil' | 'islamic-rgsa' | 'islamic-tbla' | 'islamic-umalqura' | 'persian' | undefined"
               },
-              "description": "The calendar the written date and the calendar's days are in: `gregory`,\n`buddhist`, `japanese`, `roc`, or `iso8601`.\n\nAbsent is the locale's own where it is one of the five, and `gregory` for\nevery other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in\nevery calendar, and a focused field is ISO in every calendar. In\n`segmented`, the segments are the Gregorian day, month, and year, in the\norder the locale writes them, or ISO order for `iso8601`.",
+              "description": "The calendar the written date, the segments, and the calendar's days are\nin: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar\nwith months of its own that Date Picker's `calendar` names, such as\n`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.\n\nAbsent is the locale's own where its months are the Gregorian months, and\n`gregory` for every other, as Date Picker's `calendar` is. The value is\n`YYYY-MM-DD` in every calendar, and a focused text field is ISO in every\ncalendar. In `segmented`, the segments are the day, month, and year as\nthe calendar counts them, in the order the locale writes them: Mehr 14,\n1405 is month 7 and day 14 of 1405 under `persian`. Under the five with\nGregorian months they are the Gregorian day, month, and year, or ISO order\nfor `iso8601`.",
               "fieldName": "calendar"
             },
             {
@@ -50918,13 +51491,31 @@
               "description": "The name of the calendar's grid of days, read by screen readers.",
               "fieldName": "calendarLabel"
             },
+            {
+              "name": "clearable",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the field shows a button that empties it, as Input's `clearable`\ndoes. Shown only while the field holds something to clear and is neither\ndisabled nor read-only.",
+              "fieldName": "clearable"
+            },
+            {
+              "name": "clear-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Clear'",
+              "description": "The accessible name of the clear button, which shows only an icon.",
+              "fieldName": "clearLabel"
+            },
             {
               "name": "date-style",
               "type": {
                 "text": "'full' | 'iso' | 'long' | 'medium' | 'short'"
               },
               "default": "'long'",
-              "description": "How a date is written in the field: `short` through `full`, or ISO.\n\n**The field renders when it is idle and holds the value when it is being\nedited.** A written date is a rendering, and a document being edited must\nnot be a rendering of something else: `Intl.DateTimeFormat` formats and does\nnot parse, so `4 August 2026` cannot be typed back, and writing a parser per\nlocale is how a field ends up rejecting what it just displayed.\n\nThe way out is not to choose between the two but to separate them in time.\nIdle, the field shows `4 August 2026`, which is what a date is for reading.\nFocused, it shows `2026-08-04`, which is what a date is for typing, and it\ngoes back on the way out. Nothing parses a rendering, and nothing is\nread-only, which is what an earlier version of this settled for.\n\nA range is the exception that needs no swap: the dash between its two dates\nis a separator this element understands, so that much reads back either way.\n\n`iso` turns the rendering off, for a field whose reader is entering data\nrather than reading it, or where the ISO form is itself the point.\n\nThe value is always `YYYY-MM-DD` regardless, because that is what a form\nsubmits and what `min` and `max` compare against.",
+              "description": "How a date is written in the field: `short` through `full`, or ISO.\n\n**The field renders when it is idle and holds the value when it is being\nedited.** A written date is a rendering, and a document being edited must\nnot be a rendering of something else: `Intl.DateTimeFormat` formats and does\nnot parse, so a rendering such as `Tuesday, August 4, 2026` is no text to\nedit. The field does read a date typed in the locale's order and digits as\nyou leave it, which covers what a reader types.\n\nThe way out is not to choose between the two but to separate them in time.\nIdle, the field shows `4 August 2026`, which is what a date is for reading.\nFocused, it shows `2026-08-04`, which is what a date is for typing, and it\ngoes back on the way out. Nothing parses a rendering, and nothing is\nread-only, which is what an earlier version of this settled for.\n\nA range is the exception that needs no swap: the dash between its two dates\nis a separator this element understands, so that much reads back either way.\n\n`iso` turns the rendering off, for a field whose reader is entering data\nrather than reading it, or where the ISO form is itself the point.\n\nThe value is always `YYYY-MM-DD` regardless, because that is what a form\nsubmits and what `min` and `max` compare against.",
               "fieldName": "dateStyle"
             },
             {
@@ -51113,6 +51704,15 @@
               "description": "The name of the button that removes one date. `{name}` is replaced with\nthe date.\n\n**The name goes in**, so a row of them is heard as which one each\nremoves rather than as \"Remove\" said once per date.",
               "fieldName": "removeLabel"
             },
+            {
+              "name": "selection-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{kind, select, date {Selected date: {start}} start {Range starts {start}. Choose the day it ends.} range {Selected range: {start} to {end}} other {{count, plural, one {# date selected} other {# dates selected}}}}'",
+              "description": "What a screen reader hears about the dates chosen in the calendar, with\n`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's\n`selection-label` says.",
+              "fieldName": "selectionLabel"
+            },
             {
               "name": "step",
               "type": {
@@ -51131,6 +51731,15 @@
               "description": "The message shown when a date is not on `step`.",
               "fieldName": "stepMismatchMessage"
             },
+            {
+              "name": "time-zone",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The time zone today is read in, such as `America/New_York`, handed to the\ncalendar: the day marked today, and the month an empty field opens on.\nEmpty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone.",
+              "fieldName": "timeZone"
+            },
             {
               "name": "trigger-label",
               "type": {
@@ -51149,6 +51758,15 @@
               "description": "The message shown when `disable-dates` or `disable-days` bars a date.",
               "fieldName": "unavailableMessage"
             },
+            {
+              "name": "unreadable-message",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{mode, select, single {Enter a date as YYYY-MM-DD.} other {Enter dates as YYYY-MM-DD, separated by commas.}}'",
+              "description": "The message for text that is no date, where `bad-input-message` is not\nset. `{mode}` is `single`, `range`, or `multiple`.",
+              "fieldName": "unreadableMessage"
+            },
             {
               "name": "year-view-label",
               "type": {
@@ -51197,6 +51815,32 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "name": "range-end-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'End'",
+              "description": "What a screen reader hears before the segments of a range's second date\nor time, after each segment's own name.",
+              "fieldName": "rangeEndLabel",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "name": "range-start-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Start'",
+              "description": "What a screen reader hears before the segments of a range's first date\nor time, after each segment's own name: \"month, Start, Stay\".",
+              "fieldName": "rangeStartLabel",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
             {
               "name": "segmented",
               "type": {
@@ -51455,6 +52099,10 @@
             }
           ],
           "cssStates": [
+            {
+              "description": "The field holds no date.",
+              "name": "blank"
+            },
             {
               "description": "The field has an error to show, from the browser's validation or from your `feedback`.",
               "name": "invalid"
@@ -51578,7 +52226,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A grid of days that follows the APG date grid pattern:\n\n- The grid is one tab stop. Only the focused cell is in the tab sequence.\n- Arrow keys move by day and by week.\n- `PageUp` and `PageDown` move by month.\n- `Home` and `End` move to the start and end of the week.\n\n**Dates are `YYYY-MM-DD` strings, and every calculation is in UTC**, because\na local-time `Date` shifts across a time zone or daylight-saving boundary.\n\n**The days are the Gregorian calendar's**, written in `calendar`: the\nlocale's own where its months are the Gregorian months, as `th-TH` writes\n2569 for 2026, and `gregory` where they are not, as for `fa-IR`.\n\n`month` sets which month the grid shows, separately from `value`, so paging\nselects nothing and you can control the view. When unset, it follows the\nfirst selected date, then the current month.\n\n`mode` sets how many dates are held. Unset holds one, `range` holds two and\nmarks the dates between them, and `multiple` toggles each date. All three\nread and write the same comma-separated `value`.\n\n`max-view` makes the heading a button that steps back to the months of the\nyear, and with `year` to a page of years, as Zag's date picker does. The\narrows, Home, End and the page keys move there, Enter or a press chooses, and\nEscape goes back to the days.\n\n`isDateUnavailable` and `dayContent` are properties for a script: a rule\nthat bars dates, and what each day shows in place of its number.\n\nThe month heading is a live region, so a screen reader hears the new month\nwhen Previous or Next is pressed. Neither moves past `min` or `max`, and the\nkeys stop at them too. A value outside the bounds, on a barred day, or off\n`step` reports `rangeUnderflow`, `rangeOverflow`, `badInput` or\n`stepMismatch`, so a form does not submit it.",
+          "description": "A grid of days that follows the APG date grid pattern:\n\n- The grid is one tab stop. Only the focused cell is in the tab sequence.\n- Arrow keys move by day and by week.\n- `PageUp` and `PageDown` move by month.\n- `Home` and `End` move to the start and end of the week.\n\n**Dates are `YYYY-MM-DD` strings, and every calculation is in UTC**, because\na local-time `Date` shifts across a time zone or daylight-saving boundary.\n\n**The months are the ones `calendar` counts**: the Gregorian months for the\nlocale's own calendar where its months are the Gregorian months, as `th-TH`\nwrites 2569 for 2026, and `gregory` where they are not, as for `fa-IR`\nwith no `calendar`. Name a calendar with months of its own, such as\n`persian`, and every view counts its days, months, and years from `Intl`.\n\n`month` sets which month the grid shows, separately from `value`, so paging\nselects nothing and you can control the view. When unset, it follows the\nfirst selected date, then the current month.\n\n`mode` sets how many dates are held. Unset holds one, `range` holds two and\nmarks the dates between them, and `multiple` toggles each date. All three\nread and write the same comma-separated `value`. With a `mode`, the grid\ncarries `aria-multiselectable`. While a range holds one end, the grid draws\nthe range to the day under the pointer or the focus, marking those cells\n`data-range-preview`.\n\nThe chosen date, range, or count of dates is the grid's description, in a\nregion screen readers announce when it changes, as React Aria's calendars\ndo. `selection-label` words it.\n\n`max-view` makes the heading a button that steps back to the months of the\nyear, and with `year` to a page of years, as Zag's date picker does. The\narrows, Home, End and the page keys move there, Enter or a press chooses, and\nEscape goes back to the days.\n\n`isDateUnavailable` and `dayContent` are properties for a script: a rule\nthat bars dates, and what each day shows in place of its number.\n\nThe month heading is a live region, so a screen reader hears the new month\nwhen Previous or Next is pressed. Neither moves past `min` or `max`, and the\nkeys stop at them too. A value outside the bounds, on a barred day, or off\n`step` reports `rangeUnderflow`, `rangeOverflow`, `badInput` or\n`stepMismatch`, so a form does not submit it.",
           "name": "HelixHeadlessDatePicker",
           "cssProperties": [
             {
@@ -51592,7 +52240,7 @@
               "name": "cell"
             },
             {
-              "description": "The cell of a range's last day, beside `cell`.",
+              "description": "The cell of a range's last day, beside `cell`, or of the day a waiting range is drawn to.",
               "name": "cell-range-end"
             },
             {
@@ -51695,6 +52343,10 @@
               "description": "The glyph on the previous month control, where none is slotted.",
               "name": "previous-mark"
             },
+            {
+              "description": "The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.",
+              "name": "selection"
+            },
             {
               "description": "One row of days.",
               "name": "week"
@@ -51750,9 +52402,9 @@
               "kind": "field",
               "name": "calendar",
               "type": {
-                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'coptic' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic-civil' | 'islamic-umalqura' | 'persian' | undefined"
+                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'chinese' | 'coptic' | 'dangi' | 'ethioaa' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic' | 'islamic-civil' | 'islamic-rgsa' | 'islamic-tbla' | 'islamic-umalqura' | 'persian' | undefined"
               },
-              "description": "The calendar the heading, the days, and the months are written in.\n\n`gregory`, `buddhist`, `japanese`, `roc`, and `iso8601` are the five\nwhose months are the Gregorian months. Absent is the locale's own where\nit is one of the five, such as `buddhist` for `th-TH` or `japanese` for\n`ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`\nfor `fa-IR`.\n\n`persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,\n`coptic`, and `indian` draw a calendar with months of its own, as React\nAria's calendars do: each grid is one of that calendar's months, the\nHebrew leap month and Ethiopia's five-day thirteenth month included, and\nPrevious, Next and the page keys move by those months. `month` and\n`helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The\nheading stays text, as the months and years views are drawn in Gregorian\nmonths only. The value is `YYYY-MM-DD` in every calendar.",
+              "description": "The calendar the heading, the days, and the months are written in.\n\n`gregory`, `buddhist`, `japanese`, `roc`, and `iso8601` are the five\nwhose months are the Gregorian months. Absent is the locale's own where\nit is one of the five, such as `buddhist` for `th-TH` or `japanese` for\n`ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`\nfor `fa-IR`.\n\n`persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,\n`islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,\n`indian`, `chinese`, and `dangi` draw a calendar with months of its own,\nas React Aria's calendars do: each grid is one of that calendar's months,\nthe Hebrew and Chinese leap months and Ethiopia's five-day thirteenth\nmonth included, and Previous, Next and the page keys move by those\nmonths. With `max-view`, the months view shows that calendar's year, of\ntwelve or thirteen months, and the years view its years. `month` and\n`helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The\nvalue is `YYYY-MM-DD` in every calendar.",
               "attribute": "calendar"
             },
             {
@@ -51892,6 +52544,16 @@
               "default": "undefined",
               "description": "The month on show, whoever set it, and `undefined` until somebody has."
             },
+            {
+              "kind": "field",
+              "name": "browsed",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the month on show is one the reader paged to, which `showChosen` forgets."
+            },
             {
               "kind": "field",
               "name": "month",
@@ -52075,6 +52737,61 @@
               "description": "The range's ends, when there are two and the mode asks for them.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "previewed",
+              "type": {
+                "text": "string"
+              },
+              "privacy": "private",
+              "default": "''",
+              "description": "The day a reader points at or moves to while a range holds one end, which\nthe grid draws the range to before it is chosen."
+            },
+            {
+              "kind": "field",
+              "name": "pending",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "description": "Whether a range holds its first end and waits for the second.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "drawnRange",
+              "type": {
+                "text": "{ ends: [string, string]; preview: boolean } | null"
+              },
+              "privacy": "private",
+              "description": "The range the grid draws: the chosen one, or, while one end waits for\nthe other, the run to the day under the pointer or the focus.",
+              "readonly": true
+            },
+            {
+              "kind": "method",
+              "name": "preview",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "iso",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "Draws a waiting range to the day the pointer is on."
+            },
+            {
+              "kind": "field",
+              "name": "handleGridLeave",
+              "privacy": "private",
+              "readonly": true
+            },
             {
               "kind": "method",
               "name": "isSelected",
@@ -52113,16 +52830,6 @@
               "description": "The months the calendar pages through: its own under a `calendar` with\nmonths of its own, and the Gregorian months otherwise.",
               "readonly": true
             },
-            {
-              "kind": "field",
-              "name": "ownMonths",
-              "type": {
-                "text": "boolean"
-              },
-              "privacy": "private",
-              "description": "Whether `calendar` names a calendar with months of its own.",
-              "readonly": true
-            },
             {
               "kind": "field",
               "name": "derivedMonth",
@@ -52469,6 +53176,19 @@
                 "text": "focus(options?: FocusOptions) => void"
               }
             },
+            {
+              "kind": "method",
+              "name": "showChosen",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Shows the days again, on the month of the chosen date, with the tab stop\non that date, forgetting the month and the day the reader browsed to.\n\nDate Input calls it each time its panel opens, which is where the APG\ndate picker dialog puts focus. Measured before this: from August 4, two\npresses of Page Down, Escape, and Down again opened on October 4.\nA `month` you set stays until the reader pages away from it.",
+              "type": {
+                "text": "showChosen() => void"
+              }
+            },
             {
               "kind": "field",
               "name": "rangeUnderflowMessage",
@@ -52529,6 +53249,29 @@
               "attribute": "required",
               "reflects": true
             },
+            {
+              "kind": "field",
+              "name": "selectionLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{kind, select, date {Selected date: {start}} start {Range starts {start}. Choose the day it ends.} range {Selected range: {start} to {end}} other {{count, plural, one {# date selected} other {# dates selected}}}}'",
+              "description": "What a screen reader hears about the chosen dates: the grid's\ndescription, said again whenever the dates change. `{kind}` is `date`,\n`start` while a range holds one end, `range`, or `dates` for `multiple`.\n`{start}` and `{end}` are dates written in `locale`, and `{count}` is how\nmany dates are chosen.",
+              "attribute": "selection-label",
+              "helix": {
+                "words": true
+              }
+            },
+            {
+              "kind": "field",
+              "name": "selectionWords",
+              "type": {
+                "text": "string"
+              },
+              "privacy": "private",
+              "description": "`selectionLabel` for the dates chosen now, or nothing while there are none.\n\nReact Aria's calendars describe the grid by the chosen date or range and\nannounce it when it changes. Measured before this: a range of seven days\nwas seven cells with `aria-selected` in a grid that said nothing of a\nrange, and choosing its end was heard as one more selected cell.",
+              "readonly": true
+            },
             {
               "kind": "field",
               "name": "step",
@@ -52660,6 +53403,30 @@
               },
               "description": "Reports \"required and empty\", or clears it.\n\nWritten out rather than taken from `MixinField`, which is where the seven\nform controls get this. That mixin brings a label, a hint and a feedback\nregion with it, and this is a grid rather than a field: it is composed\n*into* the field that has those, so taking the mixin would give one control\ntwo of each. What is shared is five lines, and the anchor is what the\nbrowser points its bubble at."
             },
+            {
+              "kind": "field",
+              "name": "problem",
+              "type": {
+                "text": "[ValidityStateFlags, string] | undefined"
+              },
+              "privacy": "private",
+              "description": "What is wrong with the answer, as validity flags and a message, or nothing.\n`reportRequired` hands it to the form, and `failure` to the mark.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "failure",
+              "type": {
+                "text": "'missing' | 'refused' | undefined"
+              },
+              "privacy": "protected",
+              "description": "A missing date waits for the reader; a refused one is marked at once.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinPickerFeedback",
+                "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "report",
@@ -52850,6 +53617,20 @@
                 "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "touched",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the reader has committed an answer, or a form has refused the\npicker. A reset forgets it.",
+              "inheritedFrom": {
+                "name": "MixinPickerFeedback",
+                "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "marked",
@@ -52857,13 +53638,30 @@
                 "text": "boolean"
               },
               "privacy": "protected",
-              "description": "Whether a reader is told the answer is wrong: `invalid`, or `feedback`.",
+              "description": "Whether a reader is told the answer is wrong: `invalid`, `feedback`, a\nheld answer the picker refuses, or a missing answer once the reader has\ncommitted one or a form has refused the picker.\n\n**A refused answer is marked at once, and a missing one waits**, as\nChromium's tree does for native controls: a time input holding a time\npast its `max` reports invalid on load, and an empty required text field\ndoes not, since the reader already hears that it is required. Measured\nbefore this on Time Picker: `value=\"13:00\" max=\"12:00\"` reported\n`rangeOverflow` while the list said nothing and `:state(invalid)` was off.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "MixinPickerFeedback",
                 "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "formResetCallback",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Returns the control to its `defaultValue`, or to its `value` attribute\nwhere there is no `default-value`.\n\nBoth halves are dropped, the consumer's and the control's, because a\nreset means the form is as it was served. Clearing only the internal one\nwould leave a control that had been written to stuck at that value.",
+              "inheritedFrom": {
+                "name": "HelixFormElement",
+                "module": "src/helix-form-element/helix-form-element.ts"
+              },
+              "type": {
+                "text": "formResetCallback() => void"
+              }
+            },
             {
               "kind": "method",
               "name": "renderPickerFeedback",
@@ -52964,23 +53762,6 @@
                 "module": "src/mixins/mixin-controller-value/mixin-controller-value.ts"
               }
             },
-            {
-              "kind": "method",
-              "name": "formResetCallback",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "description": "Returns the control to its `defaultValue`, or to its `value` attribute\nwhere there is no `default-value`.\n\nBoth halves are dropped, the consumer's and the control's, because a\nreset means the form is as it was served. Clearing only the internal one\nwould leave a control that had been written to stuck at that value.",
-              "inheritedFrom": {
-                "name": "HelixFormElement",
-                "module": "src/helix-form-element/helix-form-element.ts"
-              },
-              "type": {
-                "text": "formResetCallback() => void"
-              }
-            },
             {
               "kind": "method",
               "name": "formStateRestoreCallback",
@@ -53814,9 +54595,9 @@
             {
               "name": "calendar",
               "type": {
-                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'coptic' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic-civil' | 'islamic-umalqura' | 'persian' | undefined"
+                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'chinese' | 'coptic' | 'dangi' | 'ethioaa' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic' | 'islamic-civil' | 'islamic-rgsa' | 'islamic-tbla' | 'islamic-umalqura' | 'persian' | undefined"
               },
-              "description": "The calendar the heading, the days, and the months are written in.\n\n`gregory`, `buddhist`, `japanese`, `roc`, and `iso8601` are the five\nwhose months are the Gregorian months. Absent is the locale's own where\nit is one of the five, such as `buddhist` for `th-TH` or `japanese` for\n`ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`\nfor `fa-IR`.\n\n`persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,\n`coptic`, and `indian` draw a calendar with months of its own, as React\nAria's calendars do: each grid is one of that calendar's months, the\nHebrew leap month and Ethiopia's five-day thirteenth month included, and\nPrevious, Next and the page keys move by those months. `month` and\n`helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The\nheading stays text, as the months and years views are drawn in Gregorian\nmonths only. The value is `YYYY-MM-DD` in every calendar.",
+              "description": "The calendar the heading, the days, and the months are written in.\n\n`gregory`, `buddhist`, `japanese`, `roc`, and `iso8601` are the five\nwhose months are the Gregorian months. Absent is the locale's own where\nit is one of the five, such as `buddhist` for `th-TH` or `japanese` for\n`ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`\nfor `fa-IR`.\n\n`persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,\n`islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,\n`indian`, `chinese`, and `dangi` draw a calendar with months of its own,\nas React Aria's calendars do: each grid is one of that calendar's months,\nthe Hebrew and Chinese leap months and Ethiopia's five-day thirteenth\nmonth included, and Previous, Next and the page keys move by those\nmonths. With `max-view`, the months view shows that calendar's year, of\ntwelve or thirteen months, and the years view its years. `month` and\n`helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The\nvalue is `YYYY-MM-DD` in every calendar.",
               "fieldName": "calendar"
             },
             {
@@ -54022,6 +54803,15 @@
               "description": "Stops the form from submitting while no date is chosen.",
               "fieldName": "required"
             },
+            {
+              "name": "selection-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{kind, select, date {Selected date: {start}} start {Range starts {start}. Choose the day it ends.} range {Selected range: {start} to {end}} other {{count, plural, one {# date selected} other {# dates selected}}}}'",
+              "description": "What a screen reader hears about the chosen dates: the grid's\ndescription, said again whenever the dates change. `{kind}` is `date`,\n`start` while a range holds one end, `range`, or `dates` for `multiple`.\n`{start}` and `{end}` are dates written in `locale`, and `{count}` is how\nmany dates are chosen.",
+              "fieldName": "selectionLabel"
+            },
             {
               "name": "step",
               "type": {
@@ -54165,9 +54955,25 @@
           ],
           "cssStates": [
             {
-              "description": "While `invalid` is set or `feedback` says what is wrong.",
+              "description": "While no date is chosen.",
+              "name": "blank"
+            },
+            {
+              "description": "While `invalid` is set, `feedback` says what is wrong, the picker holds a date outside `min` and `max` or one it bars, or it is `required`, holds no date, and the reader has answered once or a form has refused it.",
               "name": "invalid"
             },
+            {
+              "description": "While the months of a year are shown, where `max-view` is set.",
+              "name": "month-view"
+            },
+            {
+              "description": "While a `range` holds its first end and waits for the second.",
+              "name": "range-pending"
+            },
+            {
+              "description": "While a page of years is shown, where `max-view` is `year`.",
+              "name": "year-view"
+            },
             {
               "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
               "name": "settled",
@@ -69760,7 +70566,7 @@
           "type": {
             "text": "Record<string, (value: string) => TemplateResult>"
           },
-          "default": "{ day: (value) => html`<span part=\"day\">${value}</span>`, dayPeriod: (value) => html`<span part=\"day-period\">${value}</span>`, era: (value) => html`<span part=\"era\">${value}</span>`, hour: (value) => html`<span part=\"hour\">${value}</span>`, minute: (value) => html`<span part=\"minute\">${value}</span>`, month: (value) => html`<span part=\"month\">${value}</span>`, second: (value) => html`<span part=\"second\">${value}</span>`, timeZoneName: (value) => html`<span part=\"time-zone-name\">${value}</span>`, weekday: (value) => html`<span part=\"weekday\">${value}</span>`, year: (value) => html`<span part=\"year\">${value}</span>`, }",
+          "default": "{ day: (value) => html`<span part=\"day\">${value}</span>`, dayPeriod: (value) => html`<span part=\"day-period\">${value}</span>`, era: (value) => html`<span part=\"era\">${value}</span>`, fractionalSecond: (value) => html`<span part=\"fractional-second\">${value}</span>`, hour: (value) => html`<span part=\"hour\">${value}</span>`, minute: (value) => html`<span part=\"minute\">${value}</span>`, month: (value) => html`<span part=\"month\">${value}</span>`, second: (value) => html`<span part=\"second\">${value}</span>`, timeZoneName: (value) => html`<span part=\"time-zone-name\">${value}</span>`, weekday: (value) => html`<span part=\"weekday\">${value}</span>`, year: (value) => html`<span part=\"year\">${value}</span>`, }",
           "description": "Each date field `Intl` names, drawn as a part of its own.\n\nKeyed by the `type` of `Intl.DateTimeFormat#formatToParts`. Written out one\ntemplate to a field rather than bound through one `part` binding, because a\npart is read from the source as a literal: a bound name is a part no\nstylesheet check can find. A type left out, the punctuation between the\nfields among them, is drawn as plain text."
         },
         {
@@ -69860,7 +70666,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Formats a date with `Intl` where it is shown, so you do not write the same\n`Intl` call and options in your own code.\n\n**`elapsed` shows compact relative time for a feed**, such as \"42m\", \"3h\", or\n\"1d\". After six days it shows a date. In en-US, `Intl.NumberFormat` narrow\nrenders both `minute` and `month` as `m`, so a compact \"3m\" could mean three\nminutes or three months. `elapsedTime` in `helix/core` does the measurement.\n\n**`relative` shows the same reading in words**, such as \"3 hours ago\" at\n`long`, \"3 hr. ago\" at `short` and \"3h ago\" at `narrow`, the styles\n`sl-relative-time` offers. `numeric=\"always\"` says \"1 day ago\" where the\ndefault says \"yesterday\".\n\n**`date-style` and `time-style` take each locale's own pattern**, such as\n\"Tuesday, August 4, 2026\" at `full`, and stand in for the separate fields,\nwhich `Intl` refuses beside them. `hour-cycle` sets a twelve or twenty-four\nhour clock either way.\n\n**The text refreshes on one timer shared by the page.** Each element\nschedules an update for when its current reading expires, and an element\nshowing a date schedules none, so a long feed left open costs almost nothing.\n`frozen` draws the reading once and leaves it.\n\n**`fields` draws each field of a date as a part of its own**, such as\n`day`, `month` and `year`, so a stylesheet can set the year in a lighter ink\nor the weekday in capitals with `::part()`. The text between the fields is\nthe locale's own and has no part. An `elapsed` or `relative` reading is one\nphrase, with no parts inside it.\n\n**The output is always `<time datetime>`**, so copy and paste and scripts\nparsing the page get the exact instant, whatever the visible text says. A\nscreen reader reads the text, so an `elapsed` reading is named in full, such\nas \"3 hours ago\", and carries the whole date as its title.\n\n**A date with no time, such as `2026-08-04`, is that day everywhere.** It is\nformatted in UTC unless `time-zone` says otherwise, as Date Input and Date\nPicker format their dates, so a reader west of UTC sees August 4 and not\nAugust 3.\n\n**A date is written in a calendar Date Picker draws**: the locale's own\nwhere its months are the Gregorian months, as `th-TH` writes 2569 for 2026,\nand `gregory` where they are not, as for `fa-IR`. `calendar` picks one of\nthe five.",
+          "description": "Formats a date with `Intl` where it is shown, so you do not write the same\n`Intl` call and options in your own code.\n\n**`elapsed` shows compact relative time for a feed**, such as \"42m\", \"3h\", or\n\"1d\". After six days it shows a date. In en-US, `Intl.NumberFormat` narrow\nrenders both `minute` and `month` as `m`, so a compact \"3m\" could mean three\nminutes or three months. `elapsedTime` in `helix/core` does the measurement.\n\n**`relative` shows the same reading in words**, such as \"3 hours ago\" at\n`long`, \"3 hr. ago\" at `short` and \"3h ago\" at `narrow`, the styles\n`sl-relative-time` offers. `numeric=\"always\"` says \"1 day ago\" where the\ndefault says \"yesterday\".\n\n**`date-style` and `time-style` take each locale's own pattern**, such as\n\"Tuesday, August 4, 2026\" at `full`, and stand in for the separate fields,\nwhich `Intl` refuses beside them. `hour-cycle` sets a twelve or twenty-four\nhour clock either way.\n\n**The text refreshes on one timer shared by the page.** Each element\nschedules an update for when its current reading expires, and an element\nshowing a date schedules none, so a long feed left open costs almost nothing.\n`frozen` draws the reading once and leaves it.\n\n**`fields` draws each field of a date as a part of its own**, such as\n`day`, `month` and `year`, so a stylesheet can set the year in a lighter ink\nor the weekday in capitals with `::part()`. The text between the fields is\nthe locale's own and has no part. An `elapsed` or `relative` reading is one\nphrase, with no parts inside it.\n\n**The output is always `<time datetime>`**, so copy and paste and scripts\nparsing the page get the exact instant, whatever the visible text says. A\nscreen reader reads the text, so an `elapsed` reading is named in full, such\nas \"3 hours ago\", and carries the whole date as its title.\n\n**A date with no time, such as `2026-08-04`, is that day everywhere.** It is\nformatted in UTC unless `time-zone` says otherwise, as Date Input and Date\nPicker format their dates, so a reader west of UTC sees August 4 and not\nAugust 3.\n\n**A date is written in a calendar Date Picker draws**: the locale's own\nwhere its months are the Gregorian months, as `th-TH` writes 2569 for 2026,\nand `gregory` where they are not, as for `fa-IR`. `calendar` picks any of\nthem, `persian` and `hebrew` included.",
           "name": "HelixHeadlessFormatDate",
           "cssParts": [
             {
@@ -69875,6 +70681,10 @@
               "description": "The era, such as AD, with `fields` and `era`.",
               "name": "era"
             },
+            {
+              "description": "The fraction of a second, with `fields` and `fractional-second-digits`.",
+              "name": "fractional-second"
+            },
             {
               "description": "The hour, with `fields`.",
               "name": "hour"
@@ -69913,9 +70723,9 @@
               "kind": "field",
               "name": "calendar",
               "type": {
-                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | undefined"
+                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'chinese' | 'coptic' | 'dangi' | 'ethioaa' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic' | 'islamic-civil' | 'islamic-rgsa' | 'islamic-tbla' | 'islamic-umalqura' | 'persian' | undefined"
               },
-              "description": "The calendar a date is written in: `gregory`, `buddhist`, `japanese`,\n`roc`, or `iso8601`, the calendars Date Picker and Date Input draw.\n\nAbsent is the locale's own where it is one of the five, such as\n`buddhist` for `th-TH`, and `gregory` for every other, such as `persian`\nfor `fa-IR`, so a date written here reads as the same date a Date Picker\nbeside it shows.",
+              "description": "The calendar a date is written in: `gregory`, `buddhist`, `japanese`,\n`roc`, or `iso8601`, or a calendar with months of its own, such as\n`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every\ncalendar Date Picker and Date Input draw.\n\nAbsent is the locale's own where its months are the Gregorian months,\nsuch as `buddhist` for `th-TH`, and `gregory` for every other, such as\n`persian` for `fa-IR`, so a date written here reads as the same date a\nDate Picker beside it shows. Write `calendar=\"persian\"` for Mehr 14, 1405.",
               "attribute": "calendar"
             },
             {
@@ -69946,6 +70756,15 @@
               "description": "How the day of the month is written, where a date is shown.",
               "attribute": "day"
             },
+            {
+              "kind": "field",
+              "name": "dayPeriod",
+              "type": {
+                "text": "'long' | 'narrow' | 'short' | undefined"
+              },
+              "description": "Writes the part of the day in words, such as \"in the morning\" or \"at\nnight\", in its `long`, `short`, or `narrow` form, where `hour` is on a\ntwelve-hour clock.",
+              "attribute": "day-period"
+            },
             {
               "kind": "field",
               "name": "elapsed",
@@ -69975,6 +70794,15 @@
               "description": "Draws each field of a date in a part of its own: `weekday`, `day`,\n`month`, `year`, `era`, `hour`, `minute`, `second`, `day-period` and\n`time-zone-name`, so `::part(year)` can set the year apart.\n\nOff by default, which draws the date as one run of text, as Shoelace and\nWeb Awesome do. An `elapsed` or `relative` reading is one phrase either\nway.",
               "attribute": "fields"
             },
+            {
+              "kind": "field",
+              "name": "fractionalSecondDigits",
+              "type": {
+                "text": "1 | 2 | 3 | undefined"
+              },
+              "description": "How many digits of a fraction of a second to write after `second`: 1, 2,\nor 3, as in 09:41:07.250.",
+              "attribute": "fractional-second-digits"
+            },
             {
               "kind": "field",
               "name": "frozen",
@@ -70090,9 +70918,9 @@
               "kind": "field",
               "name": "timeZoneName",
               "type": {
-                "text": "'long' | 'short' | undefined"
+                "text": "'long' | 'longGeneric' | 'longOffset' | 'short' | 'shortGeneric' | 'shortOffset' | undefined"
               },
-              "description": "Shows the name of the time zone, in its `long` or `short` form.",
+              "description": "Shows the name of the time zone: `long` or `short`, as Pacific Daylight\nTime or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or\n`longGeneric` or `shortGeneric`, as Pacific Time or PT.",
               "attribute": "time-zone-name"
             },
             {
@@ -70569,9 +71397,9 @@
             {
               "name": "calendar",
               "type": {
-                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | undefined"
+                "text": "'buddhist' | 'gregory' | 'iso8601' | 'japanese' | 'roc' | 'chinese' | 'coptic' | 'dangi' | 'ethioaa' | 'ethiopic' | 'hebrew' | 'indian' | 'islamic' | 'islamic-civil' | 'islamic-rgsa' | 'islamic-tbla' | 'islamic-umalqura' | 'persian' | undefined"
               },
-              "description": "The calendar a date is written in: `gregory`, `buddhist`, `japanese`,\n`roc`, or `iso8601`, the calendars Date Picker and Date Input draw.\n\nAbsent is the locale's own where it is one of the five, such as\n`buddhist` for `th-TH`, and `gregory` for every other, such as `persian`\nfor `fa-IR`, so a date written here reads as the same date a Date Picker\nbeside it shows.",
+              "description": "The calendar a date is written in: `gregory`, `buddhist`, `japanese`,\n`roc`, or `iso8601`, or a calendar with months of its own, such as\n`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every\ncalendar Date Picker and Date Input draw.\n\nAbsent is the locale's own where its months are the Gregorian months,\nsuch as `buddhist` for `th-TH`, and `gregory` for every other, such as\n`persian` for `fa-IR`, so a date written here reads as the same date a\nDate Picker beside it shows. Write `calendar=\"persian\"` for Mehr 14, 1405.",
               "fieldName": "calendar"
             },
             {
@@ -70599,6 +71427,14 @@
               "description": "How the day of the month is written, where a date is shown.",
               "fieldName": "day"
             },
+            {
+              "name": "day-period",
+              "type": {
+                "text": "'long' | 'narrow' | 'short' | undefined"
+              },
+              "description": "Writes the part of the day in words, such as \"in the morning\" or \"at\nnight\", in its `long`, `short`, or `narrow` form, where `hour` is on a\ntwelve-hour clock.",
+              "fieldName": "dayPeriod"
+            },
             {
               "name": "elapsed",
               "type": {
@@ -70624,6 +71460,14 @@
               "description": "Draws each field of a date in a part of its own: `weekday`, `day`,\n`month`, `year`, `era`, `hour`, `minute`, `second`, `day-period` and\n`time-zone-name`, so `::part(year)` can set the year apart.\n\nOff by default, which draws the date as one run of text, as Shoelace and\nWeb Awesome do. An `elapsed` or `relative` reading is one phrase either\nway.",
               "fieldName": "fields"
             },
+            {
+              "name": "fractional-second-digits",
+              "type": {
+                "text": "1 | 2 | 3 | undefined"
+              },
+              "description": "How many digits of a fraction of a second to write after `second`: 1, 2,\nor 3, as in 09:41:07.250.",
+              "fieldName": "fractionalSecondDigits"
+            },
             {
               "name": "frozen",
               "type": {
@@ -70717,9 +71561,9 @@
             {
               "name": "time-zone-name",
               "type": {
-                "text": "'long' | 'short' | undefined"
+                "text": "'long' | 'longGeneric' | 'longOffset' | 'short' | 'shortGeneric' | 'shortOffset' | undefined"
               },
-              "description": "Shows the name of the time zone, in its `long` or `short` form.",
+              "description": "Shows the name of the time zone: `long` or `short`, as Pacific Daylight\nTime or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or\n`longGeneric` or `shortGeneric`, as Pacific Time or PT.",
               "fieldName": "timeZoneName"
             },
             {
@@ -77572,6 +78416,14 @@
                 "module": "src/button/root/button-root.ts"
               }
             },
+            {
+              "description": "A Button Group in a selection mode has this button pressed.",
+              "name": "pressed",
+              "inheritedFrom": {
+                "name": "HelixHeadlessButton",
+                "module": "src/button/root/button-root.ts"
+              }
+            },
             {
               "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
               "name": "settled",
@@ -84197,7 +85049,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Wraps one piece of content in the lightbox, such as a picture, a video frame,\nor a chart. The lightbox shows one item at a time, and the root decides\nwhich.\n\nEach item is a `group` with the role description `slide`, named by its\n`label` or, without one, by its place in the set, such as \"2 of 5\", as the\nAPG carousel pattern names a slide. The lightbox supplies both words, so they\nare translated on the lightbox.\n\nAn item that is not current is hidden and stays in the DOM, as a `TabPanel`\ndoes. Crawlers can read it, it is in the server-rendered markup, and an\n`<img>` that has decoded does not decode again when you go back to it.",
+          "description": "Wraps one piece of content in the lightbox, such as a picture, a video frame,\nor a chart. The lightbox shows one item at a time, and the root decides\nwhich.\n\nEach item is a `group` with the role description `slide`, named by its\n`label` or, without one, by its place in the set, such as \"2 of 5\", as the\nAPG carousel pattern names a slide. The lightbox supplies both words, so they\nare translated on the lightbox. A `description`, while there is one,\ndescribes the group, so a screen reader says it with the name.\n\nAn item that is not current is hidden and stays in the DOM, as a `TabPanel`\ndoes. Crawlers can read it, it is in the server-rendered markup, and an\n`<img>` that has decoded does not decode again when you go back to it.",
           "name": "HelixHeadlessLightboxItem",
           "cssParts": [
             {
@@ -84246,6 +85098,23 @@
               "description": "The item's identifier. The root compares its `active` value against it.",
               "attribute": "value"
             },
+            {
+              "kind": "field",
+              "name": "described",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether anything is slotted into `description`, which then describes the group."
+            },
+            {
+              "kind": "field",
+              "name": "readDescription",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Reads whether the `description` slot holds anything."
+            },
             {
               "kind": "field",
               "name": "tier",
@@ -84678,7 +85547,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The frame around content you open, such as a picture, a video frame, or a\nchart. The lightbox draws no content of its own. It provides the frame, the\nkeyboard behavior, and text that states the current position in the set.\n\nThe modal behavior comes from a native `<dialog>` opened with `showModal()`,\nwhich provides the top layer, a backdrop, Escape to close, and `inert` on the\nrest of the document. Every way of closing goes through `requestOpen`, as in\n`Dialog` and `Drawer`.\n\nA lightbox shows one item at a time and has no scrolling track, so `active`\nholds the current item, as in `Tabs`. The arrow keys change the item while\nfocus stays in the dialog.\n\nSet `controls` for the viewer's own previous, next and close controls, named\nby `previous-label`, `next-label` and `dismiss-label`, whose glyphs you can\nreplace in the `previous-icon`, `next-icon` and `dismiss-icon` slots. Without\nit, compose the chrome yourself in the `header` and `footer` slots, with\nbuttons that send `--previous`, `--next` and `--close`.\n\n**Set `max-zoom` to let a reader zoom into the shown item**, such as `3`.\nTwo fingers pinch it, a double click or a double tap zooms all the way in\nabout the point pressed and back out, and once zoomed one pointer drags it\nabout. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.\nThe scale and the offset are on the `viewport` part as `--lightbox-zoom`,\n`--lightbox-pan-x` and `--lightbox-pan-y`, written only while zoomed, and a\nswipe moves to the next item only while the item is at its own size. With\n`controls`, the viewer also draws zoom-out and zoom-in controls, for a\npointer with no wheel and no second finger. Once a reader stops zooming, the\nlive region says the new scale in the words of `zoom-status-label`, such as\n\"Zoomed to 150%\".\n\nEach item is a slide: a `group` with the role description in\n`slide-role-label`, named by its `label` or by `slide-label`. A touch or a pen\nswiped across the picture shows the next or the previous item, the way the\nline of text runs.\n\nA press on the empty area around the item closes the viewer, as a press on\nthe backdrop does. Under `max-zoom`, a press beside the item zooms on a\ndouble press and closes nothing, and only the space outside the viewport\ncloses the viewer. A press that dragged closes nothing.\n\n**Keyboard.** Opening moves focus to the viewer itself, which a screen\nreader names.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Shows the next item. On a right-to-left page, Left does. While the item is zoomed, the arrows move about it instead. |\n| Left, Up | Shows the previous item. |\n| Home, End | Shows the first or the last item. |\n| `+`, `-`, `0` | Zooms in, zooms out, and puts the item back at its own size, where `max-zoom` allows zooming. |\n| Tab, Shift+Tab | Moves through the controls in the viewer, from the last round to the first and from the first round to the last. |\n| Escape | Closes the viewer. A `helix-before-close` listener can refuse. |\n\nA development build warns when a viewer opens with no `label`.\n\nThe chrome hides when there is no input, through `IdleController`, and comes\nback on a pointer move, a key press, or a focus. It stays while focus is on a\ncontrol in the header or the footer, so a keyboard reader is never left on\na control that has gone. `fullscreen` uses `FullscreenController`, as `Video`\ndoes. While the viewer is open, the page behind it does not scroll.",
+          "description": "The frame around content you open, such as a picture, a video frame, or a\nchart. The lightbox draws no content of its own. It provides the frame, the\nkeyboard behavior, and text that states the current position in the set.\n\nThe modal behavior comes from a native `<dialog>` opened with `showModal()`,\nwhich provides the top layer, a backdrop, Escape to close, and `inert` on the\nrest of the document. Every way of closing goes through `requestOpen`, as in\n`Dialog` and `Drawer`.\n\nA lightbox shows one item at a time and has no scrolling track, so `active`\nholds the current item, as in `Tabs`. The arrow keys change the item while\nfocus stays in the dialog.\n\nSet `controls` for the viewer's own previous, next and close controls, named\nby `previous-label`, `next-label` and `dismiss-label`, whose glyphs you can\nreplace in the `previous-icon`, `next-icon` and `dismiss-icon` slots. Without\nit, compose the chrome yourself in the `header` and `footer` slots, with\nbuttons that send `--previous`, `--next` and `--close`.\n\n**Set `max-zoom` to let a reader zoom into the shown item**, such as `3`.\nTwo fingers pinch it, and so does a trackpad pinch or the wheel with Ctrl\nheld, about the point under the pointer. A double click or a double tap\nzooms all the way in about the point pressed and back out, and once zoomed\none pointer drags it about and the wheel moves it. `+` and `-` zoom in and out from the keyboard, and `0` puts it back.\nThe scale and the offset are on the `viewport` part as `--lightbox-zoom`,\n`--lightbox-pan-x` and `--lightbox-pan-y`, written only while zoomed, and a\nswipe moves to the next item only while the item is at its own size. With\n`controls`, the viewer also draws zoom-out and zoom-in controls, for a\npointer with no wheel and no second finger. Once a reader stops zooming, the\nlive region says the new scale in the words of `zoom-status-label`, such as\n\"Zoomed to 150%\".\n\nEach item is a slide: a `group` with the role description in\n`slide-role-label`, named by its `label` or by `slide-label`. A touch or a pen\nswiped across the picture shows the next or the previous item, the way the\nline of text runs.\n\nA press on the empty area around the item closes the viewer, as a press on\nthe backdrop does. Under `max-zoom`, a press beside the item zooms on a\ndouble press and closes nothing, and only the space outside the viewport\ncloses the viewer. A press that dragged closes nothing.\n\n**Keyboard.** Opening moves focus to the viewer itself, which a screen\nreader names.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Shows the next item. On a right-to-left page, Left does. While the item is zoomed, the arrows move about it instead. |\n| Left, Up | Shows the previous item. |\n| Home, End | Shows the first or the last item. |\n| `+`, `-`, `0` | Zooms in, zooms out, and puts the item back at its own size, where `max-zoom` allows zooming. |\n| Tab, Shift+Tab | Moves through the controls in the viewer, from the last round to the first and from the first round to the last. |\n| Escape | Closes the viewer. A `helix-before-close` listener can refuse. |\n\nA development build warns when a viewer opens with no `label`.\n\nThe chrome hides when there is no input, through `IdleController`, and comes\nback on a pointer move, a key press, or a focus. It stays while focus is on a\ncontrol in the header or the footer, so a keyboard reader is never left on\na control that has gone. `fullscreen` uses `FullscreenController`, as `Video`\ndoes. While the viewer is open, the page behind it does not scroll.",
           "name": "HelixHeadlessLightbox",
           "cssProperties": [
             {
@@ -85069,6 +85938,13 @@
               "readonly": true,
               "default": "new FocusScopeController(this, { contain: () => this.open, contents: () => [ ...['header', '', 'footer'].flatMap( (name) => this.renderRoot ?.querySelector<HTMLSlotElement>(name ? `slot[name=\"${name}\"]` : 'slot:not([name])') ?.assignedElements({ flatten: true }) ?? [], ), /* And the controls the viewer draws itself. */ ...[...(this.dialog?.children ?? [])].filter((one) => one.localName === 'button'), ], surface: () => this.dialog, })"
             },
+            {
+              "kind": "field",
+              "name": "phases",
+              "privacy": "protected",
+              "readonly": true,
+              "default": "new OpenPhaseController(this, { mark: { entering: (on) => this.toggleState('entering', on), exiting: (on) => this.toggleState('exiting', on), }, open: () => this.open, surface: () => this.dialog, })"
+            },
             {
               "kind": "field",
               "name": "zoomer",
@@ -86347,6 +87223,14 @@
             }
           ],
           "cssStates": [
+            {
+              "description": "From the moment the viewer opens until its entrance has finished.",
+              "name": "entering"
+            },
+            {
+              "description": "From the moment the viewer closes until its exit has finished.",
+              "name": "exiting"
+            },
             {
               "description": "While the viewer fills the screen.",
               "name": "fullscreen"
@@ -86444,7 +87328,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Pinch, double press and drag to zoom into the item a viewer shows, and to\nmove about it once zoomed.\n\nTwo fingers scale the item about the point between them. A double press, a\ndouble click or a double tap, zooms all the way in about the point pressed,\nand back out again. One pointer dragged across a zoomed item moves it, never\nso far that an edge comes inside the box. What it reports is a scale and an\noffset from the middle of the box; drawing them is the caller's.",
+          "description": "Pinch, double press and drag to zoom into the item a viewer shows, and to\nmove about it once zoomed.\n\nTwo fingers scale the item about the point between them. A trackpad pinch,\nwhich the browser sends as a wheel with Ctrl held, and the wheel with Ctrl\nheld scale it about the pointer. A double press, a double click or a double\ntap, zooms all the way in about the point pressed, and back out again. One\npointer dragged across a zoomed item moves it, never so far that an edge\ncomes inside the box, and so does the wheel without Ctrl. What it reports is a scale and an\noffset from the middle of the box; drawing them is the caller's.",
           "name": "ZoomController",
           "members": [
             {
@@ -86682,6 +87566,13 @@
               "privacy": "private",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "handleWheel",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A wheel with Ctrl held, which is also how the browser sends a trackpad\npinch, scales the item about the pointer. Without Ctrl, a wheel over a\nzoomed item moves it. Over an item at its own size, a plain wheel is left\nto the page."
+            },
             {
               "kind": "field",
               "name": "handleDouble",
@@ -110733,6 +111624,10 @@
               "description": "Format Date's `era`, forwarded for a time drawn as fields. An elapsed time draws none.",
               "name": "time-era"
             },
+            {
+              "description": "Format Date's `fractional-second`, forwarded for a time drawn as fields. An elapsed time draws none.",
+              "name": "time-fractional-second"
+            },
             {
               "description": "Format Date's `hour`, forwarded for a time drawn as fields. An elapsed time draws none.",
               "name": "time-hour"
@@ -139686,7 +140581,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Renders a native `<input type=\"range\">`, so the drag, the arrow keys, Home,\nEnd, the page keys, and the touch target come from the platform. A native\nrange has a hit area larger than its thumb, sized for a finger.\n\nThe value is a string, like every other form control's, and\n`MixinControllerValue` holds text. Use `valueAsNumber` for arithmetic.\n\nMarks are drawn by the component. The ticks of a `<datalist>` cannot be\nstyled, and Firefox does not render them for a range. Marks are decoration.\n`step` sets where the value can land, and the input enforces it whether or\nnot marks are drawn. `markers` is a count, so a slider from zero to a hundred\ndoes not draw a hundred and one marks by accident.\n\nA range with two thumbs is two inputs stacked on one track, because there is\nno native two-thumb range. Each thumb keeps its own value, and a named range\nsubmits one entry per thumb under its name, the lowest first. A range given\nmore than two values, such as `default-value=\"20,50,80\"`, has a thumb for\neach, as React Aria's slider takes any number of thumbs: each stops at its\nneighbors, and the ones between the first and the last are named by\n`thumb-label`.\n`min-steps-between-thumbs` keeps them that many steps apart, and the readout\njoins the two as `range-text` writes them.\n\n`origin` sets where a single thumb's fill starts: at `min`, at the middle of\nthe track, or at `max`. A balance or an offset from zero fills from the\nmiddle, as Zag's slider `origin` does. The fill's ends are published as\n`--slider-from` and `--slider-to`.\n\n`format-options` writes the value with `Intl.NumberFormat` in `locale`, as a\ncurrency, a percent or a unit, and `formatter` writes it with a function of\nyour own, such as words for a scale. Either one is what a screen reader\nhears, what the readout shows and what the marker labels say. `value-text`\nstill wraps it in a sentence, with the formatted value in its place.\n\n`required` comes with the field mixin and cannot fail. A range is never\nempty: the platform shows its midpoint when no value is set, and `willUpdate`\nseeds that midpoint into `defaultValue`, so the value matches the handle from\nthe first render. HTML does not apply `required` to a range either, so it is\nnot set on the input. It only adds the marker beside the label.\n\n**Keyboard.** Each thumb is one tab stop, and its keys are the native\nrange's.\n\n| Key | What it does |\n|---|---|\n| Right, Up | Moves the thumb up by `step`. |\n| Left, Down | Moves the thumb down by `step`. |\n| Page Up, Page Down | Moves the thumb by a larger step. |\n| Home, End | Moves the thumb to its lowest or highest value. |\n\nUnder `readonly` none of these move the thumb, and Tab still reaches it.\n\nEach thumb is an `<input type=\"range\">` with `aria-valuetext` where the value\nis formatted or worded. A range's thumbs say they stop at each other with\n`aria-valuemin` and `aria-valuemax`.",
+          "description": "Renders a native `<input type=\"range\">`, so the drag, the arrow keys, Home,\nEnd, the page keys, and the touch target come from the platform. A native\nrange has a hit area larger than its thumb, sized for a finger.\n\nThe value is a string, like every other form control's, and\n`MixinControllerValue` holds text. Use `valueAsNumber` for arithmetic.\n\nMarks are drawn by the component. The ticks of a `<datalist>` cannot be\nstyled, and Firefox does not render them for a range. Marks are decoration.\n`step` sets where the value can land, and the input enforces it whether or\nnot marks are drawn. `markers` is a count, so a slider from zero to a hundred\ndoes not draw a hundred and one marks by accident.\n\nA range with two thumbs is two inputs stacked on one track, because there is\nno native two-thumb range. Each thumb keeps its own value, and a named range\nsubmits one entry per thumb under its name, the lowest first. A range given\nmore than two values, such as `default-value=\"20,50,80\"`, has a thumb for\neach, as React Aria's slider takes any number of thumbs: each stops at its\nneighbors, and the ones between the first and the last are named by\n`thumb-label`.\n`min-steps-between-thumbs` keeps them that many steps apart, and the readout\njoins the two as `range-text` writes them.\n\nA press on a range's track takes the nearest thumb to the point pressed,\nand moving the pointer drags it, as React Aria's and Web Awesome's sliders\ndo. The thumb takes focus, and `change` is sent as the press ends.\n\n`origin` sets where a single thumb's fill starts: at `min`, at the middle of\nthe track, or at `max`. A balance or an offset from zero fills from the\nmiddle, as Zag's slider `origin` does. The fill's ends are published as\n`--slider-from` and `--slider-to`.\n\n`format-options` writes the value with `Intl.NumberFormat` in `locale`, as a\ncurrency, a percent or a unit, and `formatter` writes it with a function of\nyour own, such as words for a scale. Either one is what a screen reader\nhears, what the readout shows and what the marker labels say. `value-text`\nstill wraps it in a sentence, with the formatted value in its place.\n\n`required` comes with the field mixin and cannot fail. A range is never\nempty: the platform shows its midpoint when no value is set, and `willUpdate`\nseeds that midpoint into `defaultValue`, so the value matches the handle from\nthe first render. HTML does not apply `required` to a range either, so it is\nnot set on the input. It only adds the marker beside the label.\n\n**Keyboard.** Each thumb is one tab stop, and its keys are the native\nrange's.\n\n| Key | What it does |\n|---|---|\n| Right, Up | Moves the thumb up by `step`. |\n| Left, Down | Moves the thumb down by `step`. |\n| Page Up, Page Down | Moves the thumb by `page-step`, or by the platform's larger step where it is not set. |\n| Home, End | Moves the thumb to its lowest or highest value. |\n\nUnder `readonly` none of these move the thumb, and Tab still reaches it.\n\nEach thumb is an `<input type=\"range\">` with `aria-valuetext` where the value\nis formatted or worded. A range's thumbs say they stop at each other with\n`aria-valuemin` and `aria-valuemax`.",
           "name": "HelixHeadlessSlider",
           "cssProperties": [
             {
@@ -139943,6 +140838,15 @@
               "attribute": "origin",
               "reflects": true
             },
+            {
+              "kind": "field",
+              "name": "pageStep",
+              "type": {
+                "text": "number | undefined"
+              },
+              "description": "How far Page Up and Page Down move a thumb, in the slider's own units, as\nReact Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys\nto the platform, which moves a tenth of the track.",
+              "attribute": "page-step"
+            },
             {
               "kind": "field",
               "name": "range",
@@ -140124,6 +141028,115 @@
               "privacy": "private",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "dragging",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether a pointer is dragging a thumb, which `:state(dragging)` says."
+            },
+            {
+              "kind": "field",
+              "name": "endDrag",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Ends a drag when its pointer lifts, wherever it lifts."
+            },
+            {
+              "kind": "method",
+              "name": "startDrag",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              }
+            },
+            {
+              "kind": "method",
+              "name": "thumbInset",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "number"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "field",
+                  "type": {
+                    "text": "HTMLElement"
+                  }
+                }
+              ],
+              "description": "Half a thumb, which is where the thumb's center stops short of each end\nof its input. Measured off the thumb's length as the stylesheet sets it,\nor a platform thumb's 16 pixels where none does."
+            },
+            {
+              "kind": "method",
+              "name": "valueAt",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "number"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "event",
+                  "type": {
+                    "text": "PointerEvent"
+                  }
+                },
+                {
+                  "name": "input",
+                  "type": {
+                    "text": "HTMLElement"
+                  }
+                },
+                {
+                  "name": "inset",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "The value under a pointer, along a thumb's input, less `inset` at each\nend. Upward on a vertical track, and from the right on a right-to-left\npage."
+            },
+            {
+              "kind": "method",
+              "name": "moveThumb",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "boolean"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "at",
+                  "type": {
+                    "text": "number"
+                  }
+                },
+                {
+                  "name": "wanted",
+                  "type": {
+                    "text": "number"
+                  }
+                }
+              ],
+              "description": "Moves one of a range's thumbs, kept between its neighbors, and says whether it moved."
+            },
+            {
+              "kind": "field",
+              "name": "handlePress",
+              "privacy": "private",
+              "readonly": true,
+              "description": "A press on the field: on a thumb, the start of the platform's own drag,\nand on a range's track, the nearest thumb taken to the point and dragged\nfrom there.\n\n**A range's inputs take presses on their thumbs only**, being stacked on\none track, so a press beside a thumb reached no input at all and did\nnothing. Measured before this: a press at 90 on a range holding 20 and 60\nleft it at 20 and 60. React Aria's and Web Awesome's sliders move the\nnearest thumb there."
+            },
             {
               "kind": "field",
               "name": "handleChange",
@@ -140136,7 +141149,14 @@
               "name": "handleKeydown",
               "privacy": "private",
               "readonly": true,
-              "description": "Keeps a read-only thumb still under the keys that move it. Tab and every\nother key pass, so focus moves on."
+              "description": "Keeps a read-only thumb still under the keys that move it, and moves a\nthumb by `page-step` under Page Up and Page Down. Tab and every other key\npass, so focus moves on."
+            },
+            {
+              "kind": "field",
+              "name": "handleFocusChange",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Says whether the keyboard brought focus to a thumb, as\n`:state(focus-visible)` on the host, where a stylesheet outside can reach\nthe whole control: a ring around the track, or the readout in bold."
             },
             {
               "kind": "method",
@@ -141751,6 +142771,14 @@
               "description": "Where a single thumb's fill starts: `start` at `min`, `center` at the\nmiddle of the track, or `end` at `max`. Absent is `start`. A range fills\nbetween its thumbs and ignores it.",
               "fieldName": "origin"
             },
+            {
+              "name": "page-step",
+              "type": {
+                "text": "number | undefined"
+              },
+              "description": "How far Page Up and Page Down move a thumb, in the slider's own units, as\nReact Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys\nto the platform, which moves a tenth of the track.",
+              "fieldName": "pageStep"
+            },
             {
               "name": "range",
               "type": {
@@ -141953,6 +142981,14 @@
             }
           ],
           "cssStates": [
+            {
+              "description": "A thumb is being dragged, by its thumb or from a press on the track.",
+              "name": "dragging"
+            },
+            {
+              "description": "A thumb has focus that the keyboard brought, where the browser draws a focus ring.",
+              "name": "focus-visible"
+            },
             {
               "description": "The slider has an error to show, from the browser's validation or from your `feedback`.",
               "name": "invalid"
@@ -148972,7 +150008,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Only the step's name is a button. The marker is `aria-hidden` decoration, so\nit is outside the button. The name uses `Button`, so the hover wash, the\nfocus ring, and the disabled style come from `Button`.\n\nEvery step can be pressed and fires `helix-select`. To stop the user from\nmoving to a step, set `disabled` on it.\n\nThe marker is a slot, and its fallback shows the step's state: a check for a\nfinished stage, a target for the current stage, and an empty ring for a stage\nnot reached yet. Only that one mark is rendered, so the accessibility tree\nhas no hidden marks.\n\nThe half lines on each side of the mark are drawn on the step's `::before`\nand `::after` from properties the list sets, so the step renders no extra\nelement for them.\n\nA finished stage says so in words: the name's button is described by\n`complete-label`, \"Complete\" unless you translate it, and a stage that\nbecomes complete while the page is open says it once in a polite live\nregion. The current stage's button carries `aria-current=\"step\"`, and only\nthe button, so the state is said once, on the control.",
+          "description": "Only the step's name is a button. The marker is `aria-hidden` decoration, so\nit is outside the button. The name uses `Button`, so the hover wash, the\nfocus ring, and the disabled style come from `Button`.\n\nEvery step can be pressed and fires `helix-select`. To stop the user from\nmoving to a step, set `disabled` on it.\n\nThe marker is a slot, and its fallback shows the step's state: a check for a\nfinished stage, a target for the current stage, and an empty ring for a stage\nnot reached yet. Only that one mark is rendered, so the accessibility tree\nhas no hidden marks.\n\nThe half lines on each side of the mark are drawn on the step's `::before`\nand `::after` from properties the list sets, so the step renders no extra\nelement for them.\n\nA finished stage says so in words: the name's button is described by\n`complete-label`, \"Complete\" unless you translate it, and a stage that\nbecomes complete while the page is open says it once in a polite live\nregion. The current stage's button carries `aria-current=\"step\"`, and only\nthe button, so the state is said once, on the control.\n\nA stage's `content`, while it holds anything, is a group named by the\nstage's name, so a screen reader moving into it hears which stage it\nbelongs to.",
           "name": "HelixHeadlessStep",
           "cssParts": [
             {
@@ -149133,6 +150169,23 @@
               "description": "The value the step sends in `helix-select`.",
               "attribute": "value"
             },
+            {
+              "kind": "field",
+              "name": "holding",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether anything is slotted into `content`, which makes it a named group."
+            },
+            {
+              "kind": "field",
+              "name": "readContent",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Reads whether the `content` slot holds anything."
+            },
             {
               "kind": "field",
               "name": "status",
@@ -155815,7 +156868,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "An inactive panel is hidden and stays mounted. Anything typed into it is\nstill there when the person comes back, and the content of every panel is in\nthe server-rendered markup for crawlers, whichever tab is open.\n\nThe host is the `tabpanel` while its tab is selected, through\n`ElementInternals`, so the tab's `aria-controls` can reach it from the tab's\nshadow root. The box inside is a tab stop only while the panel holds nothing\nfocusable, as the ARIA tabs pattern and React Aria's tab panel do: Tab from\nthe tab list lands on the panel's first link or control where there is one,\nand on the panel itself where there is none.",
+          "description": "An inactive panel is hidden and stays mounted. Anything typed into it is\nstill there when the person comes back, and the content of every panel is in\nthe server-rendered markup for crawlers, whichever tab is open.\n\nThe host is the `tabpanel` while its tab is selected, through\n`ElementInternals`, so the tab's `aria-controls` can reach it from the tab's\nshadow root. The box inside is a tab stop only while the panel holds nothing\nfocusable, as the ARIA tabs pattern and React Aria's tab panel do: Tab from\nthe tab list lands on the panel's first link or control where there is one,\nand on the panel itself where there is none.\n\n**Set `lazy` for a panel that is expensive to draw.** Its content waits in a\n`<template>` inside it, and goes into the panel the first time the panel is\nshown, so it costs nothing until a reader opens that tab. Once in, it stays.\nThe panel sends `helix-load` at the same moment, for content your code\nrenders itself.",
           "name": "HelixHeadlessTabPanel",
           "cssParts": [
             {
@@ -155825,7 +156878,7 @@
           ],
           "slots": [
             {
-              "description": "The panel's content.",
+              "description": "The panel's content. Under `lazy`, a `<template>` holding it.",
               "name": ""
             }
           ],
@@ -155839,6 +156892,37 @@
               "default": "''",
               "description": "The name of the panel, which is the text of the tab that opens it.\n\nSet by the root, which is the only thing that sees both. No attribute,\nbecause it is coordination between elements rather than anything a consumer\nwrites: the tab already says it.\n\nA string and not a reference: an IDREF resolves only in the tree it is\nwritten in, and the tab's control is inside the tab's shadow root, which no\nreference from the light DOM can reach. `aria-label` on a `tabpanel` is how\nthe pattern names one anyway."
             },
+            {
+              "kind": "field",
+              "name": "lazy",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the panel's content waits in a `<template>` until the panel is\nfirst shown.",
+              "attribute": "lazy"
+            },
+            {
+              "kind": "field",
+              "name": "loaded",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether a `lazy` panel has put its content in."
+            },
+            {
+              "kind": "method",
+              "name": "load",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Puts a `lazy` panel's content in the first time the panel is shown: the\ncontent of each `<template>` it holds, in place of the template."
+            },
             {
               "kind": "field",
               "name": "selected",
@@ -156222,7 +157306,26 @@
               }
             }
           ],
+          "events": [
+            {
+              "type": {
+                "text": "HelixLoadEvent"
+              },
+              "description": "Fired the first time a `lazy` panel is shown, once its template's content is in.",
+              "name": "helix-load",
+              "reactProp": "onhelix-load"
+            }
+          ],
           "attributes": [
+            {
+              "name": "lazy",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the panel's content waits in a `<template>` until the panel is\nfirst shown.",
+              "fieldName": "lazy"
+            },
             {
               "name": "selected",
               "type": {
@@ -156243,6 +157346,10 @@
             }
           ],
           "cssStates": [
+            {
+              "description": "Once a `lazy` panel has been shown and its content is in.",
+              "name": "loaded"
+            },
             {
               "description": "While its tab is the one selected.",
               "name": "selected"
@@ -156303,7 +157410,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Selection works through an event, the same as in the accordion and the tree.\nA tab dispatches `helix-select`, and the root pairs it with the panel of the\nsame value. Nothing registers with anything, so tabs added later work with no\nextra setup.\n\nThe tab list is a single tab stop, and the arrow keys move between tabs\nthrough `KeyboardNavigationController`, the same as in the radio and toggle\ngroups. Selection follows focus, which suits a small set where showing a\npanel is cheap. Set `manual` when showing a panel is expensive, so focus can\nmove without selecting.\n\n`orientation=\"vertical\"` sets the tabs in a column beside the panels, and the\ntab list says `aria-orientation=\"vertical\"`. The arrow keys of both axes move\nbetween tabs either way.\n\nA tab with an `href` is a link, for tabs that are pages of a site. Pressing\nit follows the link. Where any tab is a link, the arrow keys move focus\nwithout choosing on every tab of the list, as under `manual`, so arrowing\npast a tab never leaves the page and the list answers the keys one way.\nMark the tab of the page you are on with `selected`, or set `active` to its\nvalue.\n\nEach tab says which panel it controls through `aria-controls`, set as an\nelement reference to the panel's host, where the engine has reflection.\n\nKeys, on the tab list: Left and Right Arrow move between tabs, and so do Up\nand Down; Home and End go to the first and the last. The horizontal arrows\nfollow the reading direction, so on a right-to-left page Left moves on.\nDisabled tabs are passed over. Tab leaves the list for the selected panel,\nwhich is a tab stop only while it holds nothing focusable.\n\n**Keyboard.**\n\n| Key | What it does |\n|---|---|\n| Right, Down | Moves to the next tab, from the last round to the first. Selects it, unless `manual` is set or a tab is a link. |\n| Left, Up | Moves to the tab before, from the first round to the last. |\n| Home, End | Moves to the first or the last tab. |\n| Enter, Space | Selects the tab with focus, or follows its link. |\n| Tab | Leaves the list for the selected panel. |\n\nRemoving the selected tab selects the first enabled tab that is left, and\n`active` says so, with `helix-activate`. Where the removed tab had focus,\nfocus moves to the tab now selected.\n\n**More tabs than fit.** With `scroll-controls`, a strip that scrolls shows a\nbutton at each end it can scroll toward, as Web Awesome's tab group does,\nand a press scrolls it most of its own length. The buttons are for the\npointer, so they are out of the tab order and hidden from screen readers;\nthe arrow keys already reach every tab, and the strip scrolls the selected\ntab into view. A strip scrolls once a stylesheet gives the `tabs` part an\n`overflow`, as the styled tier does.\n\nA tab with `dismissible` can be closed: see `Tabs.Tab`.\n\nThe `indicator` part moves to the selected tab and carries its place and\nsize, so a mark of your own can be drawn there: style the part, or slot an\nelement into `indicator`, which sits inside the part and reads the same\nproperties.",
+          "description": "Selection works through an event, the same as in the accordion and the tree.\nA tab dispatches `helix-select`, and the root pairs it with the panel of the\nsame value. Nothing registers with anything, so tabs added later work with no\nextra setup.\n\nThe tab list is a single tab stop, and the arrow keys move between tabs\nthrough `KeyboardNavigationController`, the same as in the radio and toggle\ngroups. Selection follows focus, which suits a small set where showing a\npanel is cheap. Set `manual` when showing a panel is expensive, so focus can\nmove without selecting.\n\n`orientation=\"vertical\"` sets the tabs in a column beside the panels, and the\ntab list says `aria-orientation=\"vertical\"`. The arrow keys of both axes move\nbetween tabs either way.\n\nA tab with an `href` is a link, for tabs that are pages of a site. Pressing\nit follows the link. Where any tab is a link, the arrow keys move focus\nwithout choosing on every tab of the list, as under `manual`, so arrowing\npast a tab never leaves the page and the list answers the keys one way.\nMark the tab of the page you are on with `selected`, or set `active` to its\nvalue.\n\nEach tab says which panel it controls through `aria-controls`, set as an\nelement reference to the panel's host, where the engine has reflection.\n\nKeys, on the tab list: Left and Right Arrow move between tabs, and so do Up\nand Down; Home and End go to the first and the last. The horizontal arrows\nfollow the reading direction, so on a right-to-left page Left moves on.\nDisabled tabs are passed over. Tab leaves the list for the selected panel,\nwhich is a tab stop only while it holds nothing focusable.\n\n**Keyboard.**\n\n| Key | What it does |\n|---|---|\n| Right, Down | Moves to the next tab, from the last round to the first. Selects it, unless `manual` is set or a tab is a link. |\n| Left, Up | Moves to the tab before, from the first round to the last. |\n| Home, End | Moves to the first or the last tab. |\n| Enter, Space | Selects the tab with focus, or follows its link. |\n| Tab | Leaves the list for the selected panel. |\n\nRemoving the selected tab selects the enabled tab beside it, the next one\nor else the one before, and `active` says so, with `helix-activate`. Where\nthe removed tab had focus, focus moves to the tab now selected.\n\n**More tabs than fit.** With `scroll-controls`, a strip that scrolls shows a\nbutton at each end it can scroll toward, as Web Awesome's tab group does,\nand a press scrolls it most of its own length. The buttons are for the\npointer, so they are out of the tab order and hidden from screen readers;\nthe arrow keys already reach every tab, and the strip scrolls the selected\ntab into view. A strip scrolls once a stylesheet gives the `tabs` part an\n`overflow`, as the styled tier does.\n\nA tab with `dismissible` can be closed: see `Tabs.Tab`.\n\nThe `indicator` part moves to the selected tab and carries its place and\nsize, so a mark of your own can be drawn there: style the part, or slot an\nelement into `indicator`, which sits inside the part and reads the same\nproperties.",
           "name": "HelixHeadlessTabs",
           "cssParts": [
             {
@@ -156318,10 +157425,18 @@
               "description": "The button that scrolls the strip toward its end, shown under `scroll-controls` while there is more that way.",
               "name": "scroll-end"
             },
+            {
+              "description": "The glyph on that button, where none is slotted.",
+              "name": "scroll-end-mark"
+            },
             {
               "description": "The button that scrolls the strip toward its start, shown under `scroll-controls` while there is more that way.",
               "name": "scroll-start"
             },
+            {
+              "description": "The glyph on that button, where none is slotted.",
+              "name": "scroll-start-mark"
+            },
             {
               "description": "The tab list.",
               "name": "tabs"
@@ -156339,6 +157454,14 @@
             {
               "description": "The panels, as direct children of this element. Panels inside a wrapper are not paired with tabs, because pairing reads only the direct children.",
               "name": "panels"
+            },
+            {
+              "description": "Replaces the glyph on the button that scrolls the strip toward its end.",
+              "name": "scroll-end-icon"
+            },
+            {
+              "description": "Replaces the glyph on the button that scrolls the strip toward its start.",
+              "name": "scroll-start-icon"
             }
           ],
           "members": [
@@ -156518,6 +157641,31 @@
               "default": "[]",
               "description": "The values of the tabs the last pairing read, to tell a removed tab from one not yet here."
             },
+            {
+              "kind": "method",
+              "name": "beside",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "HelixHeadlessTab | undefined"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "gone",
+                  "type": {
+                    "text": "string"
+                  }
+                },
+                {
+                  "name": "tabs",
+                  "type": {
+                    "text": "HelixHeadlessTab[]"
+                  }
+                }
+              ],
+              "description": "The enabled tab nearest to where a removed one stood: the next ones\nnearest first, then the ones before it nearest first. The same order a\ndismissed tab hands focus in."
+            },
             {
               "kind": "method",
               "name": "sync",
@@ -156601,7 +157749,26 @@
                   }
                 }
               ],
-              "description": "One of the two scroll buttons, pointing the way it scrolls. A caret along\nthe line is mirrored on a right-to-left page, and one down a column is not."
+              "description": "One of the two scroll buttons, with the glyph pointing the way it scrolls."
+            },
+            {
+              "kind": "method",
+              "name": "renderScrollIcon",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "TemplateResult"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "toward",
+                  "type": {
+                    "text": "1 | -1"
+                  }
+                }
+              ],
+              "description": "The glyph on a scroll button, behind a seam: slot fallback, so a consumer\nreplaces it by slotting, and a method, so a tier above replaces it by\noverriding. A caret along the line is mirrored on a right-to-left page, and\none down a column is not."
             },
             {
               "kind": "field",
@@ -157229,13 +158396,17 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A tab is an element, because it manages selection and its own tab stop.\n\nWith an `href`, the tab is a link: `role=\"tab\"` on an `<a>`, which a press,\nEnter and the browser's own link gestures follow. `helix-select` is sent\nfirst, and canceling it keeps the browser from following, so a client-side\nrouter follows it instead.\n\nWith `dismissible`, the tab can be closed, as Web Awesome's closable tab\ncan: a press on its `dismiss` mark, or Delete or Backspace while the tab\nhas focus, sends `helix-dismiss`. The tab does not remove itself, because\nyour code owns the set, so remove the tab and its panel in your handler.\nFocus moves to the tab beside it, and the tab set selects a tab that is\nleft.\nThe tab says the key through `aria-keyshortcuts`, and the mark is for the\npointer, hidden from screen readers.",
+          "description": "A tab is an element, because it manages selection and its own tab stop.\n\nWith an `href`, the tab is a link: `role=\"tab\"` on an `<a>`, which a press,\nEnter and the browser's own link gestures follow. `helix-select` is sent\nfirst, and canceling it keeps the browser from following, so a client-side\nrouter follows it instead.\n\nWith `dismissible`, the tab can be closed, as Web Awesome's closable tab\ncan: a press on its `dismiss` mark, or Delete or Backspace while the tab\nhas focus, sends `helix-dismiss`. The tab does not remove itself, because\nyour code owns the set, so remove the tab and its panel in your handler.\nFocus moves to the tab beside it, and where the tab was selected, the tab\nset selects that same tab.\nThe tab says the key through `aria-keyshortcuts`, and the mark is for the\npointer, hidden from screen readers.",
           "name": "HelixHeadlessTab",
           "cssParts": [
             {
               "description": "The mark a pointer presses to close a `dismissible` tab.",
               "name": "dismiss"
             },
+            {
+              "description": "The glyph on that mark, where none is slotted.",
+              "name": "dismiss-mark"
+            },
             {
               "description": "The tab itself.",
               "name": "tab"
@@ -157245,6 +158416,10 @@
             {
               "description": "The tab's label.",
               "name": ""
+            },
+            {
+              "description": "Replaces the glyph on the mark that closes a `dismissible` tab.",
+              "name": "dismiss-icon"
             }
           ],
           "members": [
@@ -161989,9 +163164,13 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The list is a `TimePicker`, which you can also use on its own, for example in\na settings pane. This element adds the field, the overlay, and the form\nassociation, the same arrangement Date Input has with `DatePicker` and Color\nInput has with `ColorPicker`.\n\nYou can type a time or pick one. The list offers times at a step, and the\nfield lets you enter any time, such as `09:07`.\n\nThe value is always `HH:mm` on a 24-hour clock, or `HH:mm:ss` with\n`seconds`, because that is what the form\nsubmits, what `min` and `max` compare against, and what sorts correctly as a\nstring. While idle, the field shows the time in the user's locale format.\nOnce the caret is in the field, it shows the value itself, because a\nformatted time such as `2:30 PM` cannot be typed back and `Intl` has no\nparser for it.\n\nTyping sends `input` on each keystroke and `change` when you leave the\nfield. The trigger and ArrowDown open the list, and so does a press into the\nfield; Tab into the field opens nothing. In the list, the arrow keys, typed digits and PageUp and PageDown\nmove through the times, and Enter, Space or a click chooses one and closes\nthe panel. With `variant=\"wheels\"` each wheel moves the time as you turn it,\nthe panel stays open, and Enter or Escape closes it.\n\nWith `segmented`, the field is a row of segments in place of the text: an\nhour, a minute, and AM or PM where the clock has them, each set with digits\nor the arrow keys. Alt+Down opens the list from a segment.\n\nText that is not a time gives the form an empty value, as a native time\nfield does, and `value` keeps the text so it can be corrected.\n\n**Keyboard.** The field is one tab stop, or each segment is with\n`segmented`, and the trigger is one more.\n\n| Key | What it does |\n|---|---|\n| Down | In the text field, opens the list on the chosen time. |\n| Alt with Down | Opens the list, from the text field or a segment. |\n| Enter | In the text field, takes the typed time and submits the form, as a native field does. In the list, chooses the highlighted time. |\n| Escape | Closes the list and puts focus back in the field. |\n| Up, Down on a segment | Steps the segment by one, round from its last value to its first. |\n| Page Up, Page Down on a segment | Steps by a page: two hours, or fifteen minutes or seconds. |\n| Home, End on a segment | Goes to the segment's first or last value. |\n| Digits on a segment | Fill it, and move to the next once it can take no more. |\n| A letter on the half of the day | Picks the half whose name starts with it, such as A for AM. |\n| Backspace, Delete on a segment | Empty the segment. |\n| Left, Right on a segment | Move to the previous or the next segment, along the line of text. |\n\nIn the list, the keys are `TimePicker`'s.",
+          "description": "The list is a `TimePicker`, which you can also use on its own, for example in\na settings pane. This element adds the field, the overlay, and the form\nassociation, the same arrangement Date Input has with `DatePicker` and Color\nInput has with `ColorPicker`.\n\nYou can type a time or pick one. The list offers times at a step, and the\nfield lets you enter any time, such as `09:07`.\n\nThe value is always `HH:mm` on a 24-hour clock, or `HH:mm:ss` with\n`seconds`, because that is what the form\nsubmits, what `min` and `max` compare against, and what sorts correctly as a\nstring. While idle, the field shows the time in the user's locale format.\nOnce the caret is in the field, it shows the value itself. You can type\n`14:30`, or a time as you write one, such as `2:30 PM`, `2.30pm`, or\n`14h30`, and the field reads it as you leave it, with AM and PM in the\nlocale's words.\n\nTyping sends `input` on each keystroke and `change` when you leave the\nfield. The trigger and ArrowDown open the list, and so does a press into the\nfield; Tab into the field opens nothing. The text field is a `combobox`\nwith `aria-haspopup=\"dialog\"`, `aria-expanded`, and `aria-controls`, since\nDown opens the list from it. In the list, the arrow keys, typed digits and PageUp and PageDown\nmove through the times, and Enter, Space or a click chooses one and closes\nthe panel. With `variant=\"wheels\"` each wheel moves the time as you turn it,\nthe panel stays open, and Enter or Escape closes it.\n\nWith `segmented`, the field is a row of segments in place of the text: an\nhour, a minute, and AM or PM where the clock has them, each set with digits\nor the arrow keys. Alt+Down opens the list from a segment. A `range` is two\nrows with a dash between them, the start and the end, and `multiple` keeps\nthe text.\n\nText that is not a time gives the form an empty value, as a native time\nfield does, and `value` keeps the text so it can be corrected.\n\n**Keyboard.** The field is one tab stop, or each segment is with\n`segmented`, and the trigger is one more.\n\n| Key | What it does |\n|---|---|\n| Down | In the text field, opens the list on the chosen time. |\n| Alt with Down | Opens the list, from the text field or a segment. |\n| Enter | In the text field, takes the typed time and submits the form, as a native field does. In the list, chooses the highlighted time. |\n| Escape | Closes the list and puts focus back in the field. |\n| Up, Down on a segment | Steps the segment by one, round from its last value to its first. |\n| Page Up, Page Down on a segment | Steps by a page: two hours, or fifteen minutes or seconds. |\n| Home, End on a segment | Goes to the segment's first or last value. |\n| Digits on a segment | Fill it, and move to the next once it can take no more. |\n| A letter on the half of the day | Picks the half whose name starts with it, such as A for AM. |\n| Backspace, Delete on a segment | Empty the segment. |\n| Left, Right on a segment | Move to the previous or the next segment, along the line of text. |\n\nIn the list, the keys are `TimePicker`'s.",
           "name": "HelixHeadlessTimeInput",
           "cssParts": [
+            {
+              "description": "The button that empties the field, under `clearable`, while it holds a time.",
+              "name": "clear"
+            },
             {
               "description": "The text input.",
               "name": "control"
@@ -162172,6 +163351,10 @@
               "description": "The label and the caption, as one column.",
               "name": "picker-option-text"
             },
+            {
+              "description": "The dash between a range's two rows of segments, in `segmented`, beside `literal`.",
+              "name": "range-separator"
+            },
             {
               "description": "The count of times held beyond the ones shown. A `<button>` with `expandable`, and a `<span>` without it.",
               "name": "rest"
@@ -162234,6 +163417,10 @@
             }
           ],
           "slots": [
+            {
+              "description": "Replaces the cross on the clear button, under `clearable`.",
+              "name": "clear-icon"
+            },
             {
               "description": "Content after the time, before the trigger, such as a clear button.",
               "name": "end"
@@ -162299,6 +163486,29 @@
               "description": "What the browser may autofill here, as one of the platform's own tokens.\n\nEmpty leaves the attribute off, which is the browser's default and is what\nlets autofill work at all.",
               "attribute": "autocomplete"
             },
+            {
+              "kind": "field",
+              "name": "clearable",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the field shows a button that empties it, as Input's `clearable`\ndoes. Shown only while the field holds something to clear and is neither\ndisabled nor read-only.",
+              "attribute": "clearable"
+            },
+            {
+              "kind": "field",
+              "name": "clearLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Clear'",
+              "description": "The accessible name of the clear button, which shows only an icon.",
+              "attribute": "clear-label",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "announcesInput",
@@ -162504,6 +163714,19 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "unreadableMessage",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{mode, select, single {Enter a time as {shape}.} other {Enter times as {shape}, separated by commas.}}'",
+              "description": "The message for text that is no time, where `bad-input-message` is not\nset. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`.",
+              "attribute": "unreadable-message",
+              "helix": {
+                "words": true
+              }
+            },
             {
               "kind": "field",
               "name": "held",
@@ -162521,7 +163744,21 @@
                 "text": "boolean"
               },
               "privacy": "protected",
-              "description": "Segments hold one time, so `range` and `multiple` keep the line of text,\nwhose separators and tags are how those modes write several.",
+              "description": "A row of segments holds one time, and `range` takes two rows with a dash\nbetween them, as React Aria's range fields do. `multiple` keeps the line\nof text, whose tags are how it writes several.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "segmentGroups",
+              "type": {
+                "text": "number"
+              },
+              "privacy": "protected",
+              "description": "How many rows of segments the value takes: two for a range, one otherwise.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "MixinSegmentedField",
@@ -162652,6 +163889,32 @@
               "description": "How many are held beyond the ones shown.",
               "readonly": true
             },
+            {
+              "kind": "method",
+              "name": "read",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "text",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "A time as the reader wrote it, as the value writes one: `HH:mm` as it\nis, and `2:30 PM`, `2.30pm`, `14h30`, or `1430` read back, with the half\nof the day in the locale's words. Empty where it is no time."
+            },
+            {
+              "kind": "field",
+              "name": "handleTextCommit",
+              "privacy": "private",
+              "readonly": true,
+              "description": "The text the reader leaves, read: a time written as a reader writes one\nbecomes the value as the field commits. Not on each key, where `2:3` is\na time a moment before it is `2:30`."
+            },
             {
               "kind": "field",
               "name": "handleDraftKey",
@@ -162775,6 +164038,34 @@
               },
               "description": "The mark on the button that opens the clock, behind a seam.\n\nSlot fallback, so a consumer replaces it by slotting; and a method, so the\ntier above replaces it by overriding.\n\n**A named import rather than `<helix-headless-icon>`**, on three counts.\n`Icon` indexes the whole icon map at runtime, `icons[this.name]`, and no\nbundler can shake a runtime lookup, so every consumer of any component that\nrenders one ships all 50kB of path data; a named import ships one path. The\nimport is checked when the package compiles, where a `name` string is\nchecked only by a later name lookup. And `Icon` is not registered on the\nheadless tier at all, which registers `helix-headless-icon`, so a headless\nconsumer gets an inert unknown element and no mark whatsoever."
             },
+            {
+              "kind": "field",
+              "name": "showsClear",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "description": "Whether there is a clear button on screen right now.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handleClear",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Empties the field, through `requestValue` so a consumer who owns the\nvalue decides, then says `change` and `helix-clear` and puts focus back\nin the field, the button having gone."
+            },
+            {
+              "kind": "method",
+              "name": "renderClearIcon",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "TemplateResult"
+                }
+              },
+              "description": "The cross on the clear button, behind a seam a tier can move."
+            },
             {
               "kind": "method",
               "name": "renderControl",
@@ -162853,6 +164144,40 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "rangeEndLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'End'",
+              "description": "What a screen reader hears before the segments of a range's second date\nor time, after each segment's own name.",
+              "attribute": "range-end-label",
+              "helix": {
+                "words": true
+              },
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "rangeStartLabel",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Start'",
+              "description": "What a screen reader hears before the segments of a range's first date\nor time, after each segment's own name: \"month, Start, Stay\".",
+              "attribute": "range-start-label",
+              "helix": {
+                "words": true
+              },
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "segmented",
@@ -162871,11 +164196,11 @@
               "kind": "field",
               "name": "parts",
               "type": {
-                "text": "Segments"
+                "text": "Segments[]"
               },
               "privacy": "private",
-              "default": "{}",
-              "description": "The parts set so far, which may be fewer than a whole value.",
+              "default": "[{}]",
+              "description": "The parts set so far in each row, which may be fewer than a whole\nvalue: one row, or two for a range.",
               "inheritedFrom": {
                 "name": "MixinSegmentedField",
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
@@ -162934,6 +164259,35 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "opener",
+              "type": {
+                "text": "HTMLElement | undefined"
+              },
+              "privacy": "private",
+              "default": "undefined",
+              "description": "The segment Alt+Down opened the picker from, which focus goes back to.",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "returnFocus",
+              "privacy": "protected",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Puts focus back on the segment the picker was opened from, as the\ntrigger takes it back to the field. Measured before this: Escape after\nAlt+Down on AM/PM put focus on the hour.",
+              "inheritedFrom": {
+                "name": "MixinPickerField",
+                "module": "src/mixins/mixin-picker-field/mixin-picker-field.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "segmentsShown",
@@ -162948,6 +164302,66 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "joined",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "string"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "rows",
+                  "type": {
+                    "text": "readonly Segments[]"
+                  }
+                }
+              ],
+              "description": "The value the rows add up to: each row's, joined by commas, or empty while any row is not whole.",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "method",
+              "name": "rowsOf",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "Segments[]"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "value",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "description": "The rows a value names, one per row, empty where it names none.",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "kind": "field",
+              "name": "segmentSystem",
+              "type": {
+                "text": "MonthSystem | undefined"
+              },
+              "privacy": "protected",
+              "description": "The calendar a date's parts are counted in, or `undefined` for the Gregorian calendar.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "layout",
@@ -163013,6 +164427,12 @@
                 }
               },
               "parameters": [
+                {
+                  "name": "row",
+                  "type": {
+                    "text": "number"
+                  }
+                },
                 {
                   "name": "next",
                   "type": {
@@ -163473,21 +164893,6 @@
                 "module": "src/mixins/mixin-picker-field/mixin-picker-field.ts"
               }
             },
-            {
-              "kind": "method",
-              "name": "returnFocus",
-              "privacy": "protected",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "description": "Puts the caret back in the field without the field reopening the panel.\n\nThe anchor rather than the text, which is the trigger where there is no\ntext: Color Input's swatch dropped focus to the body on Escape.",
-              "inheritedFrom": {
-                "name": "MixinPickerField",
-                "module": "src/mixins/mixin-picker-field/mixin-picker-field.ts"
-              }
-            },
             {
               "kind": "method",
               "name": "focus",
@@ -165146,6 +166551,14 @@
               "name": "helix-before-open",
               "reactProp": "onhelix-before-open"
             },
+            {
+              "type": {
+                "text": "HelixClearEvent"
+              },
+              "description": "Fired after the clear button has emptied the field, after `input` and `change`.",
+              "name": "helix-clear",
+              "reactProp": "onhelix-clear"
+            },
             {
               "type": {
                 "text": "Event"
@@ -165177,6 +166590,24 @@
               "description": "What the browser may autofill here, as one of the platform's own tokens.\n\nEmpty leaves the attribute off, which is the browser's default and is what\nlets autofill work at all.",
               "fieldName": "autocomplete"
             },
+            {
+              "name": "clearable",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether the field shows a button that empties it, as Input's `clearable`\ndoes. Shown only while the field holds something to clear and is neither\ndisabled nor read-only.",
+              "fieldName": "clearable"
+            },
+            {
+              "name": "clear-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Clear'",
+              "description": "The accessible name of the clear button, which shows only an icon.",
+              "fieldName": "clearLabel"
+            },
             {
               "name": "disable-times",
               "type": {
@@ -165319,6 +166750,15 @@
               "description": "The message shown when `disable-times` bars a time.",
               "fieldName": "unavailableMessage"
             },
+            {
+              "name": "unreadable-message",
+              "type": {
+                "text": "string"
+              },
+              "default": "'{mode, select, single {Enter a time as {shape}.} other {Enter times as {shape}, separated by commas.}}'",
+              "description": "The message for text that is no time, where `bad-input-message` is not\nset. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`.",
+              "fieldName": "unreadableMessage"
+            },
             {
               "name": "variant",
               "type": {
@@ -165366,6 +166806,32 @@
                 "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
               }
             },
+            {
+              "name": "range-end-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'End'",
+              "description": "What a screen reader hears before the segments of a range's second date\nor time, after each segment's own name.",
+              "fieldName": "rangeEndLabel",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
+            {
+              "name": "range-start-label",
+              "type": {
+                "text": "string"
+              },
+              "default": "'Start'",
+              "description": "What a screen reader hears before the segments of a range's first date\nor time, after each segment's own name: \"month, Start, Stay\".",
+              "fieldName": "rangeStartLabel",
+              "inheritedFrom": {
+                "name": "MixinSegmentedField",
+                "module": "src/mixins/mixin-segmented-field/mixin-segmented-field.ts"
+              }
+            },
             {
               "name": "segmented",
               "type": {
@@ -165624,6 +167090,10 @@
             }
           ],
           "cssStates": [
+            {
+              "description": "The field holds no time.",
+              "name": "blank"
+            },
             {
               "description": "The control has an error to show, from the browser's validation or from your `feedback`.",
               "name": "invalid"
@@ -165746,7 +167216,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Shows the times at each `step` as a `Listbox`, which provides the keyboard\nbehavior, typeahead, scrolling into view, and announcements for a set of\noptions. `variant=\"wheels\"` shows a column each for the hour, the minute, and\nthe meridiem, and one for the second with `seconds`. Left and Right move\nbetween the wheels, and Tab does too.\n\n`hour-cycle` writes every time on a twelve or a twenty-four hour clock\nwhatever the locale, and `seconds` holds times to the second.\n\nThe step keeps the list usable. At the default of 15 minutes a day is 96\nrows, which people can scroll or type into. At 1 minute it is 1,440. Use the\nlist for the times your product offers, and Time Input for any time, the same\nway Date Input separates typing a date from picking one on the calendar.\n\nThe value is always `HH:mm` on a 24-hour clock, or `HH:mm:ss` with\n`seconds`. A form submits that shape,\n`min` and `max` compare against it, and it sorts as a string. Each row's text\nfollows the person's own conventions, from `Intl`.\n\nThe chosen row is marked in the served markup. The listbox gets the answer as\n`.value`, and Lit SSR serializes no property binding, so without more the 96\nserved rows would carry no mark until the listbox upgrades and runs `place`.\nEach option also gets `selected`, an attribute binding that does serialize,\nand `place` then writes the same answer from the same value. This is the same\n`selected` you write on `Option` elsewhere in Helix, and Date Picker marks\nits choice in markup for the same reason. The list and the wheels both do\nthis, because each wheel is also a listbox.\n\n**Keyboard.** The list is one tab stop, and each wheel is one.\n\n| Key | What it does |\n|---|---|\n| Down, Up | Moves to the next or the previous time, or in a wheel to the next or the previous hour, minute, second, or half of the day. |\n| Home, End | Moves to the first or the last time, or the first or the last in a wheel. |\n| Page Down, Page Up | Moves by as many times as the list shows at once. |\n| Digits | Moves to the next time that starts with what you typed, such as `9` for 9:00. |\n| Enter, Space | Chooses the highlighted time. Moving chooses too, except under `manual` or with a `mode`. With a `mode`, Space adds or removes the time. |\n| Right, Left | In the wheels, moves to the next or the previous wheel, mirrored right to left. |\n| Tab | Moves to the next wheel, then out of the picker. |\n\n**ARIA.** The list is a `listbox` named by `label`, a slotted label, the\nhost's `aria-label` or its `aria-labelledby`. A development build warns\nwhere all four are empty. The list is described by the hint, or by the\nmessage in `feedback` in its place, and carries `aria-multiselectable` with\na `mode` and `aria-invalid` while `feedback` says what is wrong. The wheels\nare a `group` with that name, holding one `listbox` per wheel, named \"Hour\",\n\"Minute\", \"Second\" and \"AM/PM\" in the page's language, and each described\nthe same way.",
+          "description": "Shows the times at each `step` as a `Listbox`, which provides the keyboard\nbehavior, typeahead, scrolling into view, and announcements for a set of\noptions. `variant=\"wheels\"` shows a column each for the hour, the minute, and\nthe meridiem, and one for the second with `seconds`. Left and Right move\nbetween the wheels, and Tab does too.\n\n`hour-cycle` writes every time on a twelve or a twenty-four hour clock\nwhatever the locale, and `seconds` holds times to the second.\n\nThe step keeps the list usable. At the default of 15 minutes a day is 96\nrows, which people can scroll or type into. At 1 minute it is 1,440. Use the\nlist for the times your product offers, and Time Input for any time, the same\nway Date Input separates typing a date from picking one on the calendar.\n\nThe value is always `HH:mm` on a 24-hour clock, or `HH:mm:ss` with\n`seconds`. A form submits that shape,\n`min` and `max` compare against it, and it sorts as a string. Each row's text\nfollows the person's own conventions, from `Intl`.\n\nThe chosen row is marked in the served markup. The listbox gets the answer as\n`.value`, and Lit SSR serializes no property binding, so without more the 96\nserved rows would carry no mark until the listbox upgrades and runs `place`.\nEach option also gets `selected`, an attribute binding that does serialize,\nand `place` then writes the same answer from the same value. This is the same\n`selected` you write on `Option` elsewhere in Helix, and Date Picker marks\nits choice in markup for the same reason. The list and the wheels both do\nthis, because each wheel is also a listbox.\n\n**Keyboard.** The list is one tab stop, and each wheel is one.\n\n| Key | What it does |\n|---|---|\n| Down, Up | Moves to the next or the previous time, or in a wheel to the next or the previous hour, minute, second, or half of the day. |\n| Home, End | Moves to the first or the last time, or the first or the last in a wheel. |\n| Page Down, Page Up | Moves by as many times as the list shows at once. |\n| Digits | Moves to the next time that starts with what you typed, such as `9` for 9:00. |\n| Enter, Space | Chooses the highlighted time. Moving chooses too, except under `manual` or with a `mode`. With a `mode`, Space adds or removes the time. |\n| Right, Left | In the wheels, moves to the next or the previous wheel, mirrored right to left. |\n| Tab | Moves to the next wheel, then out of the picker. |\n\n**ARIA.** The list is a `listbox` named by `label`, a slotted label, the\nhost's `aria-label` or its `aria-labelledby`. A development build warns\nwhere all four are empty. The list is described by the hint, or by the\nmessage in `feedback` in its place, and carries `aria-multiselectable` with\na `mode`. It carries `aria-invalid` while `feedback` says what is wrong,\nwhile it holds a time outside `min` and `max` or one the picker does not\noffer, and, for a `required` picker with no time, once the reader has\nchosen one or a form has refused the picker. The wheels\nare a `group` with that name, holding one `listbox` per wheel, named \"Hour\",\n\"Minute\", \"Second\" and \"AM/PM\" in the page's language, and each described\nthe same way.",
           "name": "HelixHeadlessTimePicker",
           "cssParts": [
             {
@@ -165870,7 +167340,7 @@
               "name": "list-search-field"
             },
             {
-              "description": "One time in the list. It carries `data-between` inside a range.",
+              "description": "One time in the list. It carries `data-between` inside a range, and inside the run to the time under the pointer while a range waits for its second end.",
               "name": "option"
             },
             {
@@ -166273,6 +167743,28 @@
               "readonly": true,
               "description": "Takes what the list announced and constrains it to what the mode allows.\n\nThe listbox is put in `multiple` for both modes, because that is what marks\nmore than one row and toggles on press. A range then differs only in what is\nkept: two, and a third pick starts again from that third one. Working out\nwhich is newest by difference rather than by position, since a toggle can\nremove as easily as add and the announced list is a set rather than a\nsequence."
             },
+            {
+              "kind": "field",
+              "name": "previewed",
+              "type": {
+                "text": "string"
+              },
+              "privacy": "private",
+              "default": "''",
+              "description": "The time under the pointer while a range holds one end, which the list\nbands the range to before it is chosen, as Date Picker does."
+            },
+            {
+              "kind": "field",
+              "name": "handleListHover",
+              "privacy": "private",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handleListLeave",
+              "privacy": "private",
+              "readonly": true
+            },
             {
               "kind": "method",
               "name": "between",
@@ -166290,7 +167782,7 @@
                   }
                 }
               ],
-              "description": "Whether a time falls inside a range, which is what gets banded."
+              "description": "Whether a time falls inside a range, which is what gets banded: the\nchosen range, or while one end waits, the run to the time under the\npointer."
             },
             {
               "kind": "field",
@@ -166507,6 +167999,30 @@
               },
               "description": "Reports \"required and empty\", or clears it.\n\nWritten out rather than taken from `MixinField`, which is where the seven\nform controls get this. That mixin brings a label, a hint and a feedback\nregion with it, and this is a grid rather than a field: it is composed\n*into* the field that has those, so taking the mixin would give one control\ntwo of each. What is shared is five lines, and the anchor is what the\nbrowser points its bubble at."
             },
+            {
+              "kind": "field",
+              "name": "problem",
+              "type": {
+                "text": "[ValidityStateFlags, string] | undefined"
+              },
+              "privacy": "private",
+              "description": "What is wrong with the answer, as validity flags and a message, or nothing.\n`reportRequired` hands it to the form, and `failure` to the mark.",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "failure",
+              "type": {
+                "text": "'missing' | 'refused' | undefined"
+              },
+              "privacy": "protected",
+              "description": "A missing time waits for the reader; a refused one is marked at once.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "MixinPickerFeedback",
+                "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "report",
@@ -166777,6 +168293,20 @@
                 "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "touched",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the reader has committed an answer, or a form has refused the\npicker. A reset forgets it.",
+              "inheritedFrom": {
+                "name": "MixinPickerFeedback",
+                "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "marked",
@@ -166784,13 +168314,30 @@
                 "text": "boolean"
               },
               "privacy": "protected",
-              "description": "Whether a reader is told the answer is wrong: `invalid`, or `feedback`.",
+              "description": "Whether a reader is told the answer is wrong: `invalid`, `feedback`, a\nheld answer the picker refuses, or a missing answer once the reader has\ncommitted one or a form has refused the picker.\n\n**A refused answer is marked at once, and a missing one waits**, as\nChromium's tree does for native controls: a time input holding a time\npast its `max` reports invalid on load, and an empty required text field\ndoes not, since the reader already hears that it is required. Measured\nbefore this on Time Picker: `value=\"13:00\" max=\"12:00\"` reported\n`rangeOverflow` while the list said nothing and `:state(invalid)` was off.",
               "readonly": true,
               "inheritedFrom": {
                 "name": "MixinPickerFeedback",
                 "module": "src/mixins/mixin-picker-feedback/mixin-picker-feedback.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "formResetCallback",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Returns the control to its `defaultValue`, or to its `value` attribute\nwhere there is no `default-value`.\n\nBoth halves are dropped, the consumer's and the control's, because a\nreset means the form is as it was served. Clearing only the internal one\nwould leave a control that had been written to stuck at that value.",
+              "inheritedFrom": {
+                "name": "HelixFormElement",
+                "module": "src/helix-form-element/helix-form-element.ts"
+              },
+              "type": {
+                "text": "formResetCallback() => void"
+              }
+            },
             {
               "kind": "method",
               "name": "renderPickerFeedback",
@@ -166891,23 +168438,6 @@
                 "module": "src/mixins/mixin-controller-value/mixin-controller-value.ts"
               }
             },
-            {
-              "kind": "method",
-              "name": "formResetCallback",
-              "return": {
-                "type": {
-                  "text": "void"
-                }
-              },
-              "description": "Returns the control to its `defaultValue`, or to its `value` attribute\nwhere there is no `default-value`.\n\nBoth halves are dropped, the consumer's and the control's, because a\nreset means the form is as it was served. Clearing only the internal one\nwould leave a control that had been written to stuck at that value.",
-              "inheritedFrom": {
-                "name": "HelixFormElement",
-                "module": "src/helix-form-element/helix-form-element.ts"
-              },
-              "type": {
-                "text": "formResetCallback() => void"
-              }
-            },
             {
               "kind": "method",
               "name": "formStateRestoreCallback",
@@ -168023,9 +169553,13 @@
               "name": "blank"
             },
             {
-              "description": "While `invalid` is set or `feedback` says what is wrong.",
+              "description": "While `invalid` is set, `feedback` says what is wrong, or the list carries `aria-invalid`.",
               "name": "invalid"
             },
+            {
+              "description": "While a `range` holds its first time and waits for the second.",
+              "name": "range-pending"
+            },
             {
               "description": "Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.",
               "name": "settled",
@@ -169658,7 +171192,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Each message is an element because it has a timeout, a tone, a dismiss\ncontrol, and a lifetime that pauses.\n\n**Each item runs its own timer.** A timer held by the region would restart\nwith each new message, and the last of three messages would stay for nine\nseconds. It pauses while the pointer or focus is on the message, and while\nthe page is hidden, so a message is not spent in a background tab.\n\n**Each message is an `alertdialog` named by its words**, which is how a reader\nwho moves into the stack hears which message they are on. Give it a\n`heading` and a `description`, and the heading names it and the description\ndescribes it, for a message with a title and a line of detail. The region\nsays each message once as it arrives, a `danger` one assertively, so a\nmessage is never a live region of its own.\n\nA touch or a pen swipes a message toward the end of the line, and past\nhalfway, or quickly, dismisses it through the same `helix-dismiss` as its\ncontrol. While it moves, the distance is on the `item` part as\n`--toast-swipe-x`.\n\n**Escape dismisses the message holding focus**, through the same\n`helix-dismiss`, and focus moves to the next message.\n\n**Messages are inverted by default.** The item flips `color-scheme`, so a new\nmessage stands out from the page without using a color that carries meaning.",
+          "description": "Each message is an element because it has a timeout, a tone, a dismiss\ncontrol, and a lifetime that pauses.\n\n**Each item runs its own timer.** A timer held by the region would restart\nwith each new message, and the last of three messages would stay for nine\nseconds. It pauses while the pointer or focus is on the message or anywhere\nin the region's stack, and while the page is hidden, so a message is not\nspent in a background tab.\n\n**Each message is an `alertdialog` named by its words**, which is how a reader\nwho moves into the stack hears which message they are on. Give it a\n`heading` and a `description`, and the heading names it and the description\ndescribes it, for a message with a title and a line of detail. The region\nsays each message once as it arrives, a `danger` one assertively, so a\nmessage is never a live region of its own.\n\nA touch or a pen swipes a message toward the end of the line, or toward the\nedge the region's `swipe-direction` names, and past halfway, or quickly,\ndismisses it through the same `helix-dismiss` as its control. While it\nmoves, the distance is on the `item` part as `--toast-swipe-x` or\n`--toast-swipe-y`.\n\n**Escape dismisses the message holding focus**, through the same\n`helix-dismiss`, and focus moves to the next message.\n\n**Messages are inverted by default.** The item flips `color-scheme`, so a new\nmessage stands out from the page without using a color that carries meaning.",
           "name": "HelixHeadlessToastItem",
           "cssProperties": [
             {
@@ -169668,6 +171202,10 @@
             {
               "description": "How far a swipe has moved the message across, in pixels, toward the right.",
               "name": "--toast-swipe-x"
+            },
+            {
+              "description": "How far a swipe has moved the message down, in pixels, under a `swipe-direction` of `top` or `bottom`.",
+              "name": "--toast-swipe-y"
             }
           ],
           "cssParts": [
@@ -169771,12 +171309,43 @@
               "description": "Whether the message is still showing.\n\nThe item always applies: it goes when it is asked to, having announced\n`helix-dismiss` first, and a consumer who owns the list refuses that event\nto take the decision instead.\n\n**No `default-open`, unlike the four mixins.** A `default-` seed exists so\nmarkup can choose a starting state without claiming ownership, and there is\nonly one starting state that makes sense: a message that has been rendered\nis showing. An attribute whose only legal value is the default is an\nattribute nobody can use.",
               "attribute": "open"
             },
+            {
+              "kind": "field",
+              "name": "regionHolding",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether the timer is held for `regionHeld`, so the hold is let go once."
+            },
+            {
+              "kind": "method",
+              "name": "holdForRegion",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Holds the timer while the region asks, and lets it go once."
+            },
+            {
+              "kind": "field",
+              "name": "swipeTo",
+              "type": {
+                "text": "ReturnType<typeof swipeEdge>"
+              },
+              "privacy": "private",
+              "description": "The physical edge a swipe dismisses toward.",
+              "readonly": true
+            },
             {
               "kind": "field",
               "name": "swipes",
               "privacy": "protected",
               "readonly": true,
-              "default": "new SwipeController(this, { axis: () => (this.open ? 'x' : undefined), end: (dx, _dy, vx) => { const edge = swipeEdge('end', isRtl(this)) const width = this.partNamed('item')?.getBoundingClientRect().width ?? 0 const shown = settleSwipe({ points: [1], size: width, travel: Math.max(0, towardEdge(edge, dx, 0)), velocity: towardEdge(edge, vx, 0), }) if (shown === 0 && this.dismiss()) { return } this.slide(0) }, move: (dx) => this.slide(Math.max(0, towardEdge(swipeEdge('end', isRtl(this)), dx, 0))), start: (_target, event) => event.pointerType !== 'mouse', surface: () => this.partNamed('item'), })"
+              "default": "new SwipeController(this, { axis: () => (this.open ? swipeAxis(this.swipeTo) : undefined), end: (dx, dy, vx, vy) => { const edge = this.swipeTo const box = this.partNamed('item')?.getBoundingClientRect() const across = swipeAxis(edge) === 'x' const shown = settleSwipe({ points: [1], size: (across ? box?.width : box?.height) ?? 0, travel: Math.max(0, towardEdge(edge, dx, dy)), velocity: towardEdge(edge, vx, vy), }) if (shown === 0 && this.dismiss()) { return } this.slide(0) }, move: (dx, dy) => this.slide(Math.max(0, towardEdge(this.swipeTo, dx, dy))), start: (_target, event) => event.pointerType !== 'mouse', surface: () => this.partNamed('item'), })"
             },
             {
               "kind": "method",
@@ -169795,7 +171364,7 @@
                   }
                 }
               ],
-              "description": "Writes how far a swipe has moved the message toward the end of the line."
+              "description": "Writes how far a swipe has moved the message toward its edge."
             },
             {
               "kind": "field",
@@ -170548,7 +172117,7 @@
               "name": "closed"
             },
             {
-              "description": "The dismiss timer is paused, while a pointer or focus is on the message, or while the page is hidden.",
+              "description": "The dismiss timer is paused, while a pointer or focus is on the message or in the stack, or while the page is hidden.",
               "name": "paused"
             },
             {
@@ -170614,7 +172183,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The region and its items are one family because a live region must be in the\ndocument before a message is added to it. Assistive technology often does not\nannounce a region that arrives already holding its message. `Radio.Group` is\npart of its family for the same reason.\n\n**The region is a landmark named by `label`, and it says each message once\nas it arrives**: a `danger` message assertively, and every other one\npolitely. It says the word for the tone, the heading, the description and\nthe text, and not the actions, through two live regions of its own, the\n`live` parts, which it empties again a moment later. The stack itself is not\na live region, so a message is never said twice, and changing the words of a\nmessage already showing says nothing. Each message is an `alertdialog` named\nby its words, so a reader who moves into the stack hears which message they\nare on.\n\n**`hotkey` takes focus to the stack and back**, F8 unless you set it, and\n`label` says which key: `{hotkey}` in it is filled in, so the default name\nis \"Notifications (F8)\". Pressed while focus is in the stack, it gives focus\nback to where it was.\n\n**The region never creates or removes items.** You render items and remove\nthem. An item requests closing with a cancelable `helix-dismiss` event. A\ndismissed item hides itself and stays in the DOM, so your framework's state\nand the DOM stay in sync. It hides on its own unless you set `open`, which\nmakes the state yours.\n\n**`add()` shows a message from script**, for a page with no framework state\nto render them from: it appends a message of the region's own tier and\nremoves it once it has been dismissed and has finished leaving. Messages\nyou render yourself stay yours, and the region never removes them. A touch\nor a pen swipes a message away toward the end of the line.\n\n**The stack is in the top layer.** The `region` part is a `popover=\"manual\"`\nshown while a message is showing, and shown again above a modal dialog that\nopened after it. Position the `region` part, which is the box in the top\nlayer. While a modal `Dialog`, `Drawer` or `Lightbox` is open, the browser\nmakes everything outside it inert, the stack included, so a message stays\nvisible and its actions cannot be pressed. Where the browser has\n`ariaNotify`, a message that arrives then is announced through it. For a\nmessage with an action, render a second region inside the dialog.\n\nWhen a message with focus inside it is dismissed, focus moves to the next\nmessage, then the one before it, then back to where it was before it entered\nthe stack.\n\n**`max-visible` limits how many messages show at once**, as Zag's `max`\ndoes. The messages after that many, in document order, wait: each is hidden,\nits timer has not started, and the region says it once it shows, when a\nmessage before it goes. A waiting message has `:state(waiting)`.\n\n**Keyboard.**\n\n| Key | What it does |\n|---|---|\n| F8, or your `hotkey` | Moves focus to the first control in the stack, and back to where it was when pressed in the stack. |\n| Tab, Shift+Tab | Moves between the controls of the messages. |\n| Escape | Dismisses the message holding focus. Focus moves to the next message, then the one before it, then back to where it was. |",
+          "description": "The region and its items are one family because a live region must be in the\ndocument before a message is added to it. Assistive technology often does not\nannounce a region that arrives already holding its message. `Radio.Group` is\npart of its family for the same reason.\n\n**The region is a landmark named by `label`, and it says each message once\nas it arrives**: a `danger` message assertively, and every other one\npolitely. It says the word for the tone, the heading, the description and\nthe text, and not the actions, through two live regions of its own, the\n`live` parts, which it empties again a moment later. The stack itself is not\na live region, so a message is never said twice, and changing the words of a\nmessage already showing says nothing. Each message is an `alertdialog` named\nby its words, so a reader who moves into the stack hears which message they\nare on.\n\n**`hotkey` takes focus to the stack and back**, F8 unless you set it, and\n`label` says which key: `{hotkey}` in it is filled in, so the default name\nis \"Notifications (F8)\". Pressed while focus is in the stack, it gives focus\nback to where it was.\n\n**The region never creates or removes items.** You render items and remove\nthem. An item requests closing with a cancelable `helix-dismiss` event. A\ndismissed item hides itself and stays in the DOM, so your framework's state\nand the DOM stay in sync. It hides on its own unless you set `open`, which\nmakes the state yours.\n\n**`add()` shows a message from script**, for a page with no framework state\nto render them from: it appends a message of the region's own tier and\nremoves it once it has been dismissed and has finished leaving. Messages\nyou render yourself stay yours, and the region never removes them. A touch\nor a pen swipes a message away toward the end of the line, or toward the\nedge `swipe-direction` names.\n\n**Every message's timer waits while a pointer or focus is in the stack**, as\nReact Aria's and Radix's regions do, so a reader moving from one message to\nthe next does not lose the one behind them.\n\n**The stack is in the top layer.** The `region` part is a `popover=\"manual\"`\nshown while a message is showing, and shown again above a modal dialog that\nopened after it. Position the `region` part, which is the box in the top\nlayer. While a modal `Dialog`, `Drawer` or `Lightbox` is open, the browser\nmakes everything outside it inert, the stack included, so a message stays\nvisible and its actions cannot be pressed. Where the browser has\n`ariaNotify`, a message that arrives then is announced through it. For a\nmessage with an action, render a second region inside the dialog.\n\nWhen a message with focus inside it is dismissed, focus moves to the next\nmessage, then the one before it, then back to where it was before it entered\nthe stack.\n\n**`max-visible` limits how many messages show at once**, as Zag's `max`\ndoes. The messages after that many, in document order, wait: each is hidden,\nits timer has not started, and the region says it once it shows, when a\nmessage before it goes. A waiting message has `:state(waiting)`.\n\n**Keyboard.**\n\n| Key | What it does |\n|---|---|\n| F8, or your `hotkey` | Moves focus to the first control in the stack, and back to where it was when pressed in the stack. |\n| Tab, Shift+Tab | Moves between the controls of the messages. |\n| Escape | Dismisses the message holding focus. Focus moves to the next message, then the one before it, then back to where it was. |",
           "name": "HelixHeadlessToast",
           "cssParts": [
             {
@@ -170685,6 +172254,15 @@
               "attribute": "placement",
               "reflects": true
             },
+            {
+              "kind": "field",
+              "name": "swipeDirection",
+              "type": {
+                "text": "'bottom' | 'end' | 'start' | 'top' | undefined"
+              },
+              "description": "The edge a touch or a pen swipes a message toward to dismiss it: `end`,\nthe end of the line, or `start`, `top` or `bottom`. Unset is `end`.",
+              "attribute": "swipe-direction"
+            },
             {
               "kind": "field",
               "name": "said",
@@ -170860,6 +172438,56 @@
               "description": "The messages that are showing, in order.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "pointerIn",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether a pointer is over the stack."
+            },
+            {
+              "kind": "field",
+              "name": "focusIn",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Whether focus is in the stack."
+            },
+            {
+              "kind": "method",
+              "name": "inform",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Tells every message whether the stack holds its timer and which way it\nswipes, which only the region knows."
+            },
+            {
+              "kind": "field",
+              "name": "handlePointerEnter",
+              "privacy": "private",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handlePointerLeave",
+              "privacy": "private",
+              "readonly": true
+            },
+            {
+              "kind": "field",
+              "name": "handleFocusOut",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Focus leaving the stack, and not moving between its messages."
+            },
             {
               "kind": "field",
               "name": "held",
@@ -171366,6 +172994,14 @@
               },
               "description": "Which corner or edge the stack sits at.\n\nNamed here rather than on each message, because where a page puts its\ntoasts is a fact about the page: a stack whose members disagreed about\nwhere they were would not be a stack.\n\n**Six corners in one word, where `Carousel` splits the same question in\ntwo.** That family takes a placement and an alignment, and argues at its own\ndeclaration that one attribute naming both facts multiplies rather than\ncomposing. It is right there and wrong here, and the difference is the\nshape of the product. A carousel's is ragged: its `overlay` belongs to no\nedge at all, and its two groups of chrome move independently, shipping\ndifferent defaults so they do not land on each other, which is what makes\nrewriting one to move the other a real cost. A stack's is two edges by\nthree alignments, every pair real and every pair named this way by every\ntoast a reader has already met. Fusing spells the domain out and loses\nnothing; a stack has one position and takes it once.\n\n**Optional, and bottom-end is the absence of it.** Reflecting *and*\ndefaulting is the pair that writes onto a host: every toast region anybody\nrendered would gain a `placement=\"bottom-end\"` nobody typed, which a React\nconsumer's server markup does not have. A sheet carries the resting\narrangement in its own `:host` rule and the selectors describe only the\ndepartures, which is what `orientation` does.",
               "fieldName": "placement"
+            },
+            {
+              "name": "swipe-direction",
+              "type": {
+                "text": "'bottom' | 'end' | 'start' | 'top' | undefined"
+              },
+              "description": "The edge a touch or a pen swipes a message toward to dismiss it: `end`,\nthe end of the line, or `start`, `top` or `bottom`. Unset is `end`.",
+              "fieldName": "swipeDirection"
             }
           ],
           "superclass": {
@@ -171494,7 +173130,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The indicator is one element that moves to the selected item. A single moving\nobject is easier to follow than a fill that swaps, and it shows where the\nselection came from.\n\nIts size and position are measured from the selected item and written to the\nindicator as custom properties, because labels have different lengths.\nMeasurement happens on the client, so the server renders the indicator hidden\nand it fades in once measured.\n\n`selection-mode=\"multiple\"` makes the group a toolbar of buttons that each\nsay whether they are pressed with `aria-pressed`, as React Aria's\nToggleButtonGroup and Radix's ToggleGroup do. A press presses or releases\none item, the arrow keys move focus without pressing, and `value` is the\npressed values, comma separated, which `values` also gives as a list. Use\n`values` where an item's value holds a comma. The form receives one entry\nper pressed value, and a page the browser brings back presses the same\nitems again. The indicator stays hidden, and each pressed item is marked\nwith `:state(pressed)`. Inside a toolbar it is a named group of that\ntoolbar's controls instead, so a reader meets one toolbar.\n\n`orientation=\"vertical\"` runs the items down a column, says so to the\naccessibility tree, and the up and down arrows move between them.\n\n**Keyboard.** The group is one tab stop: the chosen item, or the first that\ncan be chosen, as in a radio group, and in a multiple group the item focus\nwas last on.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Moves to the next item, from the last back to the first. In a single group, chooses it. |\n| Left, Up | Moves to the item before, from the first round to the last. In a single group, chooses it. |\n| Home, End | Moves to the first or the last item. In a single group, chooses it. |\n| Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. |\n\nLeft and Right swap on a right-to-left page, and a disabled item is passed\nover. A single group is a `radiogroup` of items with `role=\"radio\"` and\n`aria-checked`. A multiple group is a `toolbar` of buttons with\n`aria-pressed`, or a `group` inside a toolbar. The group is named by\n`label` and carries `aria-orientation` under `orientation`.",
+          "description": "The indicator is one element that moves to the selected item. A single moving\nobject is easier to follow than a fill that swaps, and it shows where the\nselection came from.\n\nIts size and position are measured from the selected item and written to the\nindicator as custom properties, because labels have different lengths.\nMeasurement happens on the client, so the server renders the indicator hidden\nand it fades in once measured.\n\n`selection-mode=\"multiple\"` makes the group a toolbar of buttons that each\nsay whether they are pressed with `aria-pressed`, as React Aria's\nToggleButtonGroup and Radix's ToggleGroup do. A press presses or releases\none item, the arrow keys move focus without pressing, and `value` is the\npressed values, comma separated, which `values` also gives as a list. Use\n`values` where an item's value holds a comma. The form receives one entry\nper pressed value, and a page the browser brings back presses the same\nitems again. The indicator stays hidden, and each pressed item is marked\nwith `:state(pressed)`. Inside a toolbar it is a named group of that\ntoolbar's controls instead, so a reader meets one toolbar.\n\n`orientation=\"vertical\"` runs the items down a column, says so to the\naccessibility tree, and the up and down arrows move between them.\n\n**Keyboard.** The group is one tab stop: the chosen item, or the first that\ncan be chosen, as in a radio group, and in a multiple group the item focus\nwas last on.\n\n| Key | What it does |\n|---|---|\n| Right, Down | Moves to the next item, from the last back to the first. In a single group, chooses it. |\n| Left, Up | Moves to the item before, from the first round to the last. In a single group, chooses it. |\n| Home, End | Moves to the first or the last item. In a single group, chooses it. |\n| Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. With `allow-empty-selection`, takes back the chosen item. |\n\nLeft and Right swap on a right-to-left page, and a disabled item is passed\nover. A single group is a `radiogroup` of items with `role=\"radio\"` and\n`aria-checked`. A multiple group is a `toolbar` of buttons with\n`aria-pressed`, or a `group` inside a toolbar. The group is named by\n`label` and carries `aria-orientation` under `orientation`.",
           "name": "HelixHeadlessToggleGroup",
           "cssParts": [
             {
@@ -171560,6 +173196,14 @@
               },
               "description": "Takes the markup's own answer where nothing has set a value.\n\n**The case a server renders**, and `Tabs` records the same fault from the\nother side. This element cannot choose on the server, having no children to\ncount, so a consumer whose first paint is right wrote `selected` on the\nitem: that serves `aria-checked=\"true\"`, and `sync` then cleared it one\nframe later, because `value` is `''` and nothing matches it. The shipped\n`disabled` example is exactly that markup, and drew both of its groups with\nnothing chosen.\n\n**Onto `defaultValue`, never onto `value`**, which is the same call\n`Slider` makes about the midpoint it seeds: what the markup declared is a\nfact about the markup, so it is where a reset returns to rather than\nsomething the reader chose. It also makes the group report the answer it is\nshowing, which marking the item alone would not: a `required` group would\notherwise tell a reader a value is missing while they are looking at one.\n\nA written `value` still wins, a declared property being a seed and a\ncorrection, and a group with neither still marks nothing at all.\n\n**The property and never `defaultSelected`, which is the attribute.** React\nassigns a JSX prop as a property where the custom element has one, and\nwrites no attribute at all, so keying on the attribute answers for markup\nand not for JSX. Measured by the parity check on the shipped `disabled`\nexample, whose two syntaxes are the same tree: 192 pixels apart, the HTML\nmarking `List` and the TSX marking nothing. The attribute seeds the\nproperty at upgrade, so reading the property covers both.\n\nRead before `sync` writes to it, which is the only moment it still holds\nwhat the consumer declared: after that it holds this group's answer, and\n`value` is no longer empty, so this returns above.\n\n**Called from `willUpdate` and from the slot, never from `sync`**, which\nruns in `updated`: a reactive property set there schedules a second update,\nand Lit's development build warns about exactly that once per group. From\n`willUpdate` the first render already carries the value, which is the pass\nthat has to be right. `children` is undefined on the server, whose element\nshim carries attributes and no tree, and that is the same guard\n`MixinCollection` records for the same reason."
             },
+            {
+              "kind": "field",
+              "name": "marked",
+              "privacy": "private",
+              "readonly": true,
+              "default": "new WeakSet<HelixHeadlessToggle>()",
+              "description": "The items whose `selected` this group has written, which `adopt` passes\nover: the mark is this group's answer, and the markup declared nothing.\n\nMeasured before this: in a group with no default, choosing List and then\nresetting the form left List chosen and submitted, because `adopt` read\nthe mark `sync` had put on it as a declaration and made it the default."
+            },
             {
               "kind": "method",
               "name": "sync",
@@ -171618,6 +173262,16 @@
               "description": "Whether several items can be pressed at once.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "allowEmptySelection",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether a press on the chosen item, or Space or Enter on it, takes it\nback so nothing is chosen, as React Aria's `ToggleButtonGroup` and\nRadix's `ToggleGroup` do in a single group. Absent, a single group always\nkeeps its choice once it has one, as a radio group does. A multiple group\nreleases a pressed item either way.",
+              "attribute": "allow-empty-selection"
+            },
             {
               "kind": "field",
               "name": "focusable",
@@ -173094,6 +174748,15 @@
             }
           ],
           "attributes": [
+            {
+              "name": "allow-empty-selection",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Whether a press on the chosen item, or Space or Enter on it, takes it\nback so nothing is chosen, as React Aria's `ToggleButtonGroup` and\nRadix's `ToggleGroup` do in a single group. Absent, a single group always\nkeeps its choice once it has one, as a radio group does. A multiple group\nreleases a pressed item either way.",
+              "fieldName": "allowEmptySelection"
+            },
             {
               "name": "label-placement",
               "type": {
@@ -173348,7 +175011,7 @@
           "name": "HelixHeadlessToggle",
           "cssParts": [
             {
-              "description": "The radio button.",
+              "description": "The button: a radio in a group where one is chosen, and a button with `aria-pressed` on its own or in a group where several can be.",
               "name": "item"
             }
           ],
@@ -173860,7 +175523,7 @@
           ],
           "cssStates": [
             {
-              "description": "The item is pressed, in a group where several can be.",
+              "description": "The item is pressed, on its own or in a group where several can be.",
               "name": "pressed"
             },
             {
@@ -176018,7 +177681,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "The root holds the order of the stops: which stop is current, what Next and\nBack do, and when the tour is finished. Each stop holds its target, and you\nwrite all the text.\n\n**The spotlight is a shadow.** The scrim is a box the size of the current\ntarget with a very large `box-shadow` spread, and the shadow paints the\ndarkness. A `clip-path` on a full-screen scrim breaks as soon as an element\nbetween the scrim and the viewport is transformed.\n\nThe root measures the target's position in the browser. Nothing is measured\non the server, because a tour starts only on request.\n\n`open`, `default-open`, `helix-before-open`, `helix-before-close` and\n`toggle` work as they do on `Dialog`. Setting `open` starts the run, and\n`skip()` and `requestOpen(false)` end it early.\n\nThe box the light falls on is on the `spotlight` part as\n`--tour-spotlight-x`, `--tour-spotlight-y`, `--tour-spotlight-width` and\n`--tour-spotlight-height`, for a sheet that draws its own light, such as a\nring around the target.\n\nEach stop is told its place in the run, from `progress-label`, such as \"2 of\n5\". It describes the stop's panel, so a screen reader says it at every stop,\nand `progress` draws it in the panel as well. A dialog or a floating stop,\nwhich has nothing to light, is shown over the `backdrop` part. At a `wait`\nstop the run waits for that stop's target to be on the page, and moves on by\nitself.\n\n**Focus follows the run.** Opening moves focus to the first stop's panel,\nand moving on from a control in a stop moves it to the next one. Ending the\ntour puts focus back on the element that had it when the tour opened, unless\nyou have moved it somewhere else on the page. A stop does not trap focus, so\nyou can still `Tab` out to the element it describes.\n\n**The target is scrolled into view** before its stop is shown, by the\nleast distance that brings it on screen, so the stop that points at it is\non screen too.\n\n**Keyboard.** Focus is on the current stop's panel, which is not in the\n`Tab` order itself.\n\n| Key | What it does |\n|---|---|\n| Right | Goes to the next stop. On the last stop it does nothing, and Next finishes the tour. |\n| Left | Goes back to the previous stop. |\n| Escape | Skips the tour, and puts focus back where it was when the tour opened. |\n| Tab, Shift+Tab | Moves through the controls in the stop, and on out to the page. A stop does not trap focus. |\n| Enter, Space | On Back, Next, or Skip, presses it. |\n\nThe arrow that points the way the line runs goes on, and the other goes\nback, so on a right-to-left page Left goes on and Right goes back. A text field in a stop keeps\nits own arrows.\n\nThe tour is a region named by `label` while it runs. A development build\nwarns when a tour opens with no `label`.",
+          "description": "The root holds the order of the stops: which stop is current, what Next and\nBack do, and when the tour is finished. Each stop holds its target, and you\nwrite all the text.\n\n**The spotlight is a shadow.** The scrim is a box the size of the current\ntarget with a very large `box-shadow` spread, and the shadow paints the\ndarkness. A `clip-path` on a full-screen scrim breaks as soon as an element\nbetween the scrim and the viewport is transformed.\n\nThe root measures the target's position in the browser. Nothing is measured\non the server, because a tour starts only on request.\n\n`open`, `default-open`, `helix-before-open`, `helix-before-close` and\n`toggle` work as they do on `Dialog`. Setting `open` starts the run, and\n`skip()` and `requestOpen(false)` end it early.\n\nThe box the light falls on is on the `spotlight` part as\n`--tour-spotlight-x`, `--tour-spotlight-y`, `--tour-spotlight-width` and\n`--tour-spotlight-height`, for a sheet that draws its own light, such as a\nring around the target.\n\nEach stop is told its place in the run, from `progress-label`, such as \"2 of\n5\". It describes the stop's panel, so a screen reader says it at every stop,\nand `progress` draws it in the panel as well. A dialog or a floating stop,\nwhich has nothing to light, is shown over the `backdrop` part. At a `wait`\nstop the run waits for that stop's target to be on the page, and moves on by\nitself.\n\n**Focus follows the run.** Opening moves focus to the first stop's panel,\nand moving on from a control in a stop moves it to the next one. Ending the\ntour puts focus back on the element that had it when the tour opened, unless\nyou have moved it somewhere else on the page. A stop does not trap focus, so\nyou can still `Tab` out to the element it describes.\n\n**The target is scrolled into view** before its stop is shown, by the\nleast distance that brings it on screen, so the stop that points at it is\non screen too.\n\n**A stop's `effect` runs as the tour reaches it**, before it is shown, and\nthe stop waits for a promise it returns, with `:state(preparing)` on the\ntour meanwhile. A function it returns runs when the tour leaves the stop.\n\n**A press outside the current stop and its target does nothing by\ndefault**, so a reader can use the page the tour is describing. Set\n`outside-press=\"close\"` to end the tour on one, through `helix-before-close`\nas Skip does, or `outside-press=\"block\"` to refuse it, so the stop and its\ntarget are all a pointer can reach while the tour runs, as Zag's\n`preventInteraction` does.\n\n**Keyboard.** Focus is on the current stop's panel, which is not in the\n`Tab` order itself.\n\n| Key | What it does |\n|---|---|\n| Right | Goes to the next stop. On the last stop it does nothing, and Next finishes the tour. |\n| Left | Goes back to the previous stop. |\n| Escape | Skips the tour, and puts focus back where it was when the tour opened. |\n| Tab, Shift+Tab | Moves through the controls in the stop, and on out to the page. A stop does not trap focus. |\n| Enter, Space | On Back, Next, or Skip, presses it. |\n\nThe arrow that points the way the line runs goes on, and the other goes\nback, so on a right-to-left page Left goes on and Right goes back. A text field in a stop keeps\nits own arrows.\n\nThe tour is a region named by `label` while it runs. A development build\nwarns when a tour opens with no `label`.",
           "name": "HelixHeadlessTour",
           "cssProperties": [
             {
@@ -176134,6 +177797,15 @@
               "description": "Label for the control that goes on.",
               "attribute": "next-label"
             },
+            {
+              "kind": "field",
+              "name": "outsidePress",
+              "type": {
+                "text": "'block' | 'close' | undefined"
+              },
+              "description": "What a press outside the current stop and its target does while the tour\nruns. Unset, nothing: the page stays usable. `close` ends the tour, as\nSkip does, and `block` refuses the press.",
+              "attribute": "outside-press"
+            },
             {
               "kind": "field",
               "name": "progress",
@@ -176334,6 +178006,50 @@
               "privacy": "private",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "handleOutside",
+              "privacy": "private",
+              "readonly": true,
+              "description": "Answers a press outside the current stop and its target, as\n`outside-press` asks. A press on the tour's own parts, the stop or the\ntarget is the reader using the tour."
+            },
+            {
+              "kind": "field",
+              "name": "entered",
+              "type": {
+                "text": "{ leave?: () => void; stop: HelixHeadlessTourStop } | undefined"
+              },
+              "privacy": "private",
+              "description": "The stop whose `effect` has run, and the function to run on leaving it."
+            },
+            {
+              "kind": "field",
+              "name": "preparing",
+              "type": {
+                "text": "HelixHeadlessTourStop | undefined"
+              },
+              "privacy": "private",
+              "description": "The stop held back while its `effect` settles."
+            },
+            {
+              "kind": "method",
+              "name": "enter",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "stop",
+                  "type": {
+                    "text": "HelixHeadlessTourStop | undefined"
+                  }
+                }
+              ],
+              "description": "Runs the current stop's `effect` as the tour reaches it, and the last\none's leaving function as it leaves, and holds the stop back while a\npromise settles."
+            },
             {
               "kind": "field",
               "name": "revealed",
@@ -177096,6 +178812,14 @@
               "description": "Label for the control that goes on.",
               "fieldName": "nextLabel"
             },
+            {
+              "name": "outside-press",
+              "type": {
+                "text": "'block' | 'close' | undefined"
+              },
+              "description": "What a press outside the current stop and its target does while the tour\nruns. Unset, nothing: the page stays usable. `close` ends the tour, as\nSkip does, and `block` refuses the press.",
+              "fieldName": "outsidePress"
+            },
             {
               "name": "progress",
               "type": {
@@ -177163,6 +178887,10 @@
               "description": "While the tour is running.",
               "name": "open"
             },
+            {
+              "description": "While the tour waits for the current stop's `effect` before showing the stop.",
+              "name": "preparing"
+            },
             {
               "description": "While the tour waits at a `wait` stop for its target to be on the page.",
               "name": "waiting"
@@ -177241,7 +178969,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A stop names its target with `for` and holds the content you put in it. The\nstop handles three things:\n\n- **Placement.** The panel is anchored to the target by the same floating\n  positioning as the other Helix overlays.\n- **Stacking.** The panel is a popover, so it is in the top layer and shows\n  above dialogs, scrolling regions, and other stacking contexts.\n- **Visibility.** The stop shows when it is `current`, which the root sets.\n\nPut any content in the stop, such as a `Card`, or a heading and a line of\ntext. The `heading` and `description` slots are optional places for the\ntitle and the line under it, which then name and describe the panel.\n\n**A stop has a type.** Without one it is a bubble pointing at its target.\n`type=\"dialog\"` is a panel in the middle of the window, over a backdrop, for\na welcome or a summary with nothing to point at. `type=\"floating\"` is a\npanel in a corner of the window, which the styled tier puts at the end of\nthe line, for a note that points at nothing in particular. `type=\"wait\"` shows nothing: the tour waits\nfor the element `for` names to be on the page, such as a menu the reader has\nto open, and moves on by itself.\n\n**The buttons are slot fallback.** With nothing in the `actions` slot, you\nget Back, Next, and Skip, already wired. Slot your own `actions` and drive\nthem with `next()`, `back()`, and `skip()` on the root.\n\n**`for` is an id, as with `Tooltip`**, so you can point at a target elsewhere\non the page from markup. It resolves against the stop's root node, so a stop\ninside a shadow tree points at a target in that tree.\n\nThe panel is a `group`, and a `dialog` for a dialog stop, only while the\nstop is shown. It is named by the `heading` slot, then by the first heading\nin the content, then by `label`, and otherwise by its place in the tour. It\nis described by the `description` slot, or where that is empty by the words\nat the start of the content, and by its place, such as \"2 of 5\",\nso a screen reader says where the reader is at every stop. `focus()` moves\nfocus to the panel, which is what the tour does when it opens or moves on.",
+          "description": "A stop names its target with `for` and holds the content you put in it. The\nstop handles three things:\n\n- **Placement.** The panel is anchored to the target by the same floating\n  positioning as the other Helix overlays.\n- **Stacking.** The panel is a popover, so it is in the top layer and shows\n  above dialogs, scrolling regions, and other stacking contexts.\n- **Visibility.** The stop shows when it is `current`, which the root sets.\n\nPut any content in the stop, such as a `Card`, or a heading and a line of\ntext. The `heading` and `description` slots are optional places for the\ntitle and the line under it, which then name and describe the panel.\n\n**A stop has a type.** Without one it is a bubble pointing at its target.\n`type=\"dialog\"` is a panel in the middle of the window, over a backdrop, for\na welcome or a summary with nothing to point at. `type=\"floating\"` is a\npanel in a corner of the window, which the styled tier puts at the end of\nthe line, for a note that points at nothing in particular. `type=\"wait\"` shows nothing: the tour waits\nfor the element `for` names to be on the page, such as a menu the reader has\nto open, and moves on by itself.\n\n**The buttons are slot fallback.** With nothing in the `actions` slot, you\nget Back, Next, and Skip, already wired. Slot your own `actions` and drive\nthem with `next()`, `back()`, and `skip()` on the root.\n\n**Set `effect` to prepare the page for a stop**, such as opening the menu\nit points into or loading what it describes. It is a function, set from\nscript, that the tour runs as it reaches the stop. Return a promise and the\nstop waits for it, and the tour has `:state(preparing)` meanwhile; return a\nfunction, or resolve to one, and the tour runs it when it leaves the stop.\nZag's tour step has the same `effect`.\n\n**`for` is an id, as with `Tooltip`**, so you can point at a target elsewhere\non the page from markup. It resolves against the stop's root node, so a stop\ninside a shadow tree points at a target in that tree.\n\nThe panel is a `group`, and a `dialog` for a dialog stop, only while the\nstop is shown. It is named by the `heading` slot, then by the first heading\nin the content, then by `label`, and otherwise by its place in the tour. It\nis described by the `description` slot, or where that is empty by the words\nat the start of the content, and by its place, such as \"2 of 5\",\nso a screen reader says where the reader is at every stop. `focus()` moves\nfocus to the panel, which is what the tour does when it opens or moves on.",
           "name": "HelixHeadlessTourStop",
           "cssParts": [
             {
@@ -177415,6 +179143,14 @@
                 "words": true
               }
             },
+            {
+              "kind": "field",
+              "name": "effect",
+              "type": {
+                "text": "TourStopEffect | undefined"
+              },
+              "description": "Run as the tour reaches the stop, before it is shown: see the description\nabove. A function, so it is set from script and has no attribute."
+            },
             {
               "kind": "field",
               "name": "first",
@@ -177512,6 +179248,13 @@
               "privacy": "private",
               "description": "The side of its target the panel last landed on, which names the arrow's\nsecond part. Undefined until the first placement, which the server never\nmakes."
             },
+            {
+              "kind": "field",
+              "name": "phases",
+              "privacy": "protected",
+              "readonly": true,
+              "default": "new OpenPhaseController(this, { mark: { entering: (on) => this.toggleState('entering', on), exiting: (on) => this.toggleState('exiting', on), }, open: () => this.current && this.type !== 'wait', surface: () => this.partNamed('bubble'), })"
+            },
             {
               "kind": "field",
               "name": "target",
@@ -178042,6 +179785,14 @@
             }
           ],
           "cssStates": [
+            {
+              "description": "From the moment the stop is shown until its entrance has finished.",
+              "name": "entering"
+            },
+            {
+              "description": "From the moment the stop is left until its exit has finished.",
+              "name": "exiting"
+            },
             {
               "description": "The panel sits below its target.",
               "name": "placed-bottom"
@@ -188884,6 +190635,6 @@
   ],
   "helix": {
     "package": "@fusion.dev/helix-headless",
-    "version": "0.158.0"
+    "version": "0.160.0"
   }
 }