@fusion.dev/helix-headless 0.159.0 → 0.160.0

package/custom-elements.json

@@ -35778,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",
@@ -35785,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",
@@ -35877,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",
@@ -47830,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"
@@ -47997,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"
@@ -48005,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"
@@ -48039,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"
@@ -48109,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"
             },
             {
@@ -48134,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",
@@ -48156,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"
             },
             {
@@ -48472,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",
@@ -48495,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",
@@ -48525,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",
@@ -48553,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",
@@ -48610,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",
@@ -48692,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",
@@ -48771,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",
@@ -48849,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",
@@ -48867,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"
@@ -48930,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",
@@ -48944,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",
@@ -49023,6 +49334,12 @@
                 }
               },
               "parameters": [
+                {
+                  "name": "row",
+                  "type": {
+                    "text": "number"
+                  }
+                },
                 {
                   "name": "next",
                   "type": {
@@ -49460,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",
@@ -51133,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"
@@ -51161,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"
             },
             {
@@ -51181,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"
             },
             {
@@ -51376,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": {
@@ -51394,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": {
@@ -51412,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": {
@@ -51460,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": {
@@ -51718,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"
@@ -51841,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": [
             {
@@ -51855,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"
             },
             {
@@ -51958,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"
@@ -52013,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"
             },
             {
@@ -52155,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",
@@ -52338,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",
@@ -52376,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",
@@ -52732,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",
@@ -52792,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",
@@ -52923,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",
@@ -53113,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",
@@ -53120,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",
@@ -53227,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",
@@ -54077,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"
             },
             {
@@ -54285,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": {
@@ -54428,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",
@@ -70023,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."
         },
         {
@@ -70123,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": [
             {
@@ -70138,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"
@@ -70176,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"
             },
             {
@@ -70209,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",
@@ -70238,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",
@@ -70353,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"
             },
             {
@@ -70832,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"
             },
             {
@@ -70862,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": {
@@ -70887,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": {
@@ -70980,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"
             },
             {
@@ -111043,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"
@@ -139996,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": [
             {
@@ -140253,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",
@@ -140434,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",
@@ -140446,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",
@@ -142061,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": {
@@ -142263,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"
@@ -162438,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"
@@ -162621,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"
@@ -162683,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"
@@ -162748,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",
@@ -162953,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",
@@ -162970,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",
@@ -163101,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",
@@ -163224,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",
@@ -163302,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",
@@ -163320,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"
@@ -163383,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",
@@ -163397,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",
@@ -163462,6 +164427,12 @@
                 }
               },
               "parameters": [
+                {
+                  "name": "row",
+                  "type": {
+                    "text": "number"
+                  }
+                },
                 {
                   "name": "next",
                   "type": {
@@ -163922,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",
@@ -165595,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"
@@ -165626,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": {
@@ -165768,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": {
@@ -165815,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": {
@@ -166073,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"
@@ -166195,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": [
             {
@@ -166319,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"
             },
             {
@@ -166722,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",
@@ -166739,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",
@@ -166956,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",
@@ -167226,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",
@@ -167233,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",
@@ -167340,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",
@@ -168472,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",
@@ -172045,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": [
             {
@@ -172111,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",
@@ -172169,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",
@@ -173645,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": {
@@ -173899,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"
             }
           ],
@@ -174411,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"
             },
             {
@@ -189523,6 +190635,6 @@
   ],
   "helix": {
     "package": "@fusion.dev/helix-headless",
-    "version": "0.159.0"
+    "version": "0.160.0"
   }
 }