@fusion.dev/helix 0.52.0 → 0.53.0

package/types/jsx.d.ts

@@ -621,10 +621,9 @@ export type HelixAnnouncementProps = {
 it up to the surface step, for a band that reads as part of the furniture
 rather than as a slot cut into it.
 
-**This was `tone="surface"`**, which put an elevation on the axis that says
-what a thing means. The band's own doc admitted it, calling `surface` the
-one value that was not a color. A band can be `info` and elevated at the
-same time, and two values that can both be true are two axes.
+**`separation` and not `tone`, because a rung is not a meaning.** A band
+can be `info` and elevated at the same time, and two values that can both
+be true are two axes, which is the test the registry answers to.
 
 Styled and not headless, because a rung of a ladder is paint: the headless
 tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -680,10 +679,9 @@ export type HelixAnnouncementSolidJsProps = {
 it up to the surface step, for a band that reads as part of the furniture
 rather than as a slot cut into it.
 
-**This was `tone="surface"`**, which put an elevation on the axis that says
-what a thing means. The band's own doc admitted it, calling `surface` the
-one value that was not a color. A band can be `info` and elevated at the
-same time, and two values that can both be true are two axes.
+**`separation` and not `tone`, because a rung is not a meaning.** A band
+can be `info` and elevated at the same time, and two values that can both
+be true are two axes, which is the test the registry answers to.
 
 Styled and not headless, because a rung of a ladder is paint: the headless
 tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -944,7 +942,14 @@ can draw a part as less than nothing, `step` is for a quantity that changes
 at a moment and is ordered the way `straight` is.
 
 Absent rather than defaulted because a reflecting property with a default
-writes its attribute onto every host, including the ones nobody configured. */
+writes its attribute onto every host, including the ones nobody configured.
+The resting value therefore lives in the render, as `curve ?? 'straight'`.
+
+**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+line claims a position, so the bounded invention a monotone cubic makes is
+a reading aid and costs nothing. A band claims an amount, and two sums
+smoothed independently can cross, so the same aid here draws a part as less
+than nothing. Same axis, different mark, different resting value. */
   curve?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -987,7 +992,14 @@ can draw a part as less than nothing, `step` is for a quantity that changes
 at a moment and is ordered the way `straight` is.
 
 Absent rather than defaulted because a reflecting property with a default
-writes its attribute onto every host, including the ones nobody configured. */
+writes its attribute onto every host, including the ones nobody configured.
+The resting value therefore lives in the render, as `curve ?? 'straight'`.
+
+**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+line claims a position, so the bounded invention a monotone cubic makes is
+a reading aid and costs nothing. A band claims an amount, and two sums
+smoothed independently can cross, so the same aid here draws a part as less
+than nothing. Same axis, different mark, different resting value. */
   "prop:curve"?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -10203,7 +10215,13 @@ renders, including the ones nobody configured.
 consumer wrote. The default therefore lives where the path is built, as
 `curve ?? 'smooth'`.
 
-`step` claims the opposite of both, that a reading holds until the next. */
+`step` claims the opposite of both, that a reading holds until the next.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -10348,7 +10366,13 @@ renders, including the ones nobody configured.
 consumer wrote. The default therefore lives where the path is built, as
 `curve ?? 'smooth'`.
 
-`step` claims the opposite of both, that a reading holds until the next. */
+`step` claims the opposite of both, that a reading holds until the next.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   "prop:curve"?: (HelixLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -11384,8 +11408,10 @@ the loudest thing in the region. The case is a dashboard of several meters
 where one is the number being watched and the rest are context, which is a
 fact about the region rather than about any one of them.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` earns its
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+the whole of what quiet means here. `outlined` earns its
 place in `BarChart`, which keeps the area and fades it toward the page, only
 because a chart has other series for the outlined one to be a *different
 kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -11494,8 +11520,10 @@ the loudest thing in the region. The case is a dashboard of several meters
 where one is the number being watched and the rest are context, which is a
 fact about the region rather than about any one of them.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` earns its
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+the whole of what quiet means here. `outlined` earns its
 place in `BarChart`, which keeps the area and fades it toward the page, only
 because a chart has other series for the outlined one to be a *different
 kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -11757,6 +11785,22 @@ separated.** A consumer wanting the whole feed carded says so once, in a
 document rule on the element, rather than on every item: this is a styled
 axis and a stylesheet is where it is set. */
   separation?: (HelixNotification["separation"]) | undefined;
+  /** Whether it offers a control to take it away. */
+  dismissible?: (HelixNotification["dismissible"]) | undefined;
+  /** Accessible name for that control.
+
+`attribute` is spelled out because Lit lowercases a property name to
+derive one rather than dash-casing it, so this would otherwise be
+reachable only as `dismisslabel`, which nobody would guess and no linter
+would catch. */
+  "dismiss-label"?: (HelixNotification["dismissLabel"]) | undefined;
+  /** Accessible name for that control.
+
+`attribute` is spelled out because Lit lowercases a property name to
+derive one rather than dash-casing it, so this would otherwise be
+reachable only as `dismisslabel`, which nobody would guess and no linter
+would catch. */
+  dismissLabel?: (HelixNotification["dismissLabel"]) | undefined;
   /** When it happened, as anything `Date` parses.
 
 An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -11782,12 +11826,6 @@ declaration. `:state(read)` is what the stylesheet reads.
   "default-read"?: (HelixNotification["defaultRead"]) | undefined;
   /** State to open with, where nothing declared one. */
   defaultRead?: (HelixNotification["defaultRead"]) | undefined;
-  /** Whether a reader may remove it. */
-  dismissible?: (HelixNotification["dismissible"]) | undefined;
-  /** Accessible name for the dismiss control. */
-  "dismiss-label"?: (HelixNotification["dismissLabel"]) | undefined;
-  /** Accessible name for the dismiss control. */
-  dismissLabel?: (HelixNotification["dismissLabel"]) | undefined;
   /** Locale for the timestamp.
 
 Empty is the runtime's own. */
@@ -11818,6 +11856,22 @@ separated.** A consumer wanting the whole feed carded says so once, in a
 document rule on the element, rather than on every item: this is a styled
 axis and a stylesheet is where it is set. */
   "prop:separation"?: (HelixNotification["separation"]) | undefined;
+  /** Whether it offers a control to take it away. */
+  "prop:dismissible"?: (HelixNotification["dismissible"]) | undefined;
+  /** Accessible name for that control.
+
+`attribute` is spelled out because Lit lowercases a property name to
+derive one rather than dash-casing it, so this would otherwise be
+reachable only as `dismisslabel`, which nobody would guess and no linter
+would catch. */
+  "attr:dismiss-label"?: (HelixNotification["dismissLabel"]) | undefined;
+  /** Accessible name for that control.
+
+`attribute` is spelled out because Lit lowercases a property name to
+derive one rather than dash-casing it, so this would otherwise be
+reachable only as `dismisslabel`, which nobody would guess and no linter
+would catch. */
+  "prop:dismissLabel"?: (HelixNotification["dismissLabel"]) | undefined;
   /** When it happened, as anything `Date` parses.
 
 An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -11843,12 +11897,6 @@ declaration. `:state(read)` is what the stylesheet reads.
   "bool:default-read"?: (HelixNotification["defaultRead"]) | undefined;
   /** State to open with, where nothing declared one. */
   "prop:defaultRead"?: (HelixNotification["defaultRead"]) | undefined;
-  /** Whether a reader may remove it. */
-  "prop:dismissible"?: (HelixNotification["dismissible"]) | undefined;
-  /** Accessible name for the dismiss control. */
-  "attr:dismiss-label"?: (HelixNotification["dismissLabel"]) | undefined;
-  /** Accessible name for the dismiss control. */
-  "prop:dismissLabel"?: (HelixNotification["dismissLabel"]) | undefined;
   /** Locale for the timestamp.
 
 Empty is the runtime's own. */
@@ -12578,7 +12626,7 @@ the name of the tool being run, or the file being read. */
 
 Reflected because the stylesheet selects on it. The mesh is chosen from the
 rendered box rather than from this, so `--orb-size` and a consumer's own
-`inline-size` get the same treatment as the three named steps. */
+`inline-size` get the same treatment as the named steps. */
   size?: (HelixOrb["size"]) | undefined;
   /** What the agent is doing.
 
@@ -12604,7 +12652,7 @@ the name of the tool being run, or the file being read. */
 
 Reflected because the stylesheet selects on it. The mesh is chosen from the
 rendered box rather than from this, so `--orb-size` and a consumer's own
-`inline-size` get the same treatment as the three named steps. */
+`inline-size` get the same treatment as the named steps. */
   "prop:size"?: (HelixOrb["size"]) | undefined;
   /** What the agent is doing.
 
@@ -13480,8 +13528,10 @@ export type HelixProgressProps = {
 the loudest thing in the region. The case is a background task, which has to
 be visible and must not compete with what the reader is actually looking at.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` is the
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+whole of what quiet means here. `outlined` is the
 interesting refusal: `BarChart` earns it by keeping the area and fading it
 toward the page, so an outlined column still encodes its value and stands as
 a *different kind of fact* from the series beside it (a forecast, a target,
@@ -13568,8 +13618,10 @@ export type HelixProgressSolidJsProps = {
 the loudest thing in the region. The case is a background task, which has to
 be visible and must not compete with what the reader is actually looking at.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` is the
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+whole of what quiet means here. `outlined` is the
 interesting refusal: `BarChart` earns it by keeping the area and fading it
 toward the page, so an outlined column still encodes its value and stands as
 a *different kind of fact* from the series beside it (a forecast, a target,
@@ -13670,11 +13722,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   label?: (HelixQrCode["label"]) | undefined;
   /** How the modules are drawn.
 
-`square` is the default and the only one that joins runs of adjacent
-modules into a single subpath, which is what keeps a thousand modules to a
-handful of nodes. `rounded` and `dots` draw each module on its own, because
-the corners are the thing being drawn and a joined run has none in the
-middle. That cost is paid only by a code that asks for them.
+`square` is the resting state and is written by not writing it, per the
+rule that a reflected property takes no default. It is also the only one
+that joins runs of adjacent modules into a single subpath, which is what
+keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+each module on its own, because the corners are the thing being drawn and a
+joined run has none in the middle. That cost is paid only by a code that
+asks for them.
 
 A scanner reads contrast between cells, not their shape, so all three
 scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -13700,11 +13754,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   "prop:label"?: (HelixQrCode["label"]) | undefined;
   /** How the modules are drawn.
 
-`square` is the default and the only one that joins runs of adjacent
-modules into a single subpath, which is what keeps a thousand modules to a
-handful of nodes. `rounded` and `dots` draw each module on its own, because
-the corners are the thing being drawn and a joined run has none in the
-middle. That cost is paid only by a code that asks for them.
+`square` is the resting state and is written by not writing it, per the
+rule that a reflected property takes no default. It is also the only one
+that joins runs of adjacent modules into a single subpath, which is what
+keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+each module on its own, because the corners are the thing being drawn and a
+joined run has none in the middle. That cost is paid only by a code that
+asks for them.
 
 A scanner reads contrast between cells, not their shape, so all three
 scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -13943,13 +13999,15 @@ The circle stays in both. A card whose only marker was its own border would
 ask a reader to compare surfaces across a row to find the answer, and would
 leave nothing for a high-contrast display. */
   variant?: (HelixRadio["variant"]) | undefined;
-  /** Whether this choice can be made. */
+  /** Whether this one can be chosen. */
   disabled?: (HelixRadio["disabled"]) | undefined;
-  /** Whether this is the current choice.
+  /** Whether this is the current one.
 
-Written by the group. */
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixRadio["selected"]) | undefined;
-  /** Identifies this choice to the group, and is what the form submits. */
+  /** Identifies this one to the set, and is what a form submits. */
   value?: (HelixRadio["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.
 
@@ -14048,13 +14106,15 @@ The circle stays in both. A card whose only marker was its own border would
 ask a reader to compare surfaces across a row to find the answer, and would
 leave nothing for a high-contrast display. */
   "prop:variant"?: (HelixRadio["variant"]) | undefined;
-  /** Whether this choice can be made. */
+  /** Whether this one can be chosen. */
   "prop:disabled"?: (HelixRadio["disabled"]) | undefined;
-  /** Whether this is the current choice.
+  /** Whether this is the current one.
 
-Written by the group. */
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   "prop:selected"?: (HelixRadio["selected"]) | undefined;
-  /** Identifies this choice to the group, and is what the form submits. */
+  /** Identifies this one to the set, and is what a form submits. */
   "prop:value"?: (HelixRadio["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.
 
@@ -15122,9 +15182,12 @@ inside a sentence.
 **`emphasis` and not `separation`, which the registry decides rather than
 taste.** Emphasis is asked of controls, how loud this one is; separation is
 asked of containers, where the surface ends. A trigger is a control, and a
-family may not declare both. Two of the four values are refused: `solid` and
-`subtle` are a button's way of being the one thing to press, which is not a
-thing an answer should ever be.
+family may not declare both. Three of the five values are refused: `solid`
+and `subtle` are a button's way of being the one thing to press, which is
+not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+takes, where a trigger's loudness is its frame rather than its ink.
+`outlined` is what the unset frame already draws, so writing it would be
+writing the resting state out.
 
 **The other three fields want this too and do not have it yet.** `Input`,
 `Textarea` and `Combobox` wear the same frame from the same shared
@@ -15262,9 +15325,12 @@ inside a sentence.
 **`emphasis` and not `separation`, which the registry decides rather than
 taste.** Emphasis is asked of controls, how loud this one is; separation is
 asked of containers, where the surface ends. A trigger is a control, and a
-family may not declare both. Two of the four values are refused: `solid` and
-`subtle` are a button's way of being the one thing to press, which is not a
-thing an answer should ever be.
+family may not declare both. Three of the five values are refused: `solid`
+and `subtle` are a button's way of being the one thing to press, which is
+not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+takes, where a trigger's loudness is its frame rather than its ink.
+`outlined` is what the unset frame already draws, so writing it would be
+writing the resting state out.
 
 **The other three fields want this too and do not have it yet.** `Input`,
 `Textarea` and `Combobox` wear the same frame from the same shared
@@ -15734,7 +15800,13 @@ assert against. So the resting state is still the attribute's absence, and
 `curve ?? 'smooth'` is what reads it.
 
 `step` claims the opposite of both, that a reading holds until the next.
-Bars ignore it, having no between to interpolate. */
+Bars ignore it, having no between to interpolate.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.
 
@@ -15867,7 +15939,13 @@ assert against. So the resting state is still the attribute's absence, and
 `curve ?? 'smooth'` is what reads it.
 
 `step` claims the opposite of both, that a reading holds until the next.
-Bars ignore it, having no between to interpolate. */
+Bars ignore it, having no between to interpolate.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   "prop:curve"?: (HelixSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.
 
@@ -17210,11 +17288,15 @@ export type HelixTabHelixSelectElementEvent =
   HelixTabElementEvent<HelixSelectEvent>;
 
 export type HelixTabProps = {
-  /** Whether the tab can be chosen. */
+  /** Whether this one can be chosen. */
   disabled?: (HelixTab["disabled"]) | undefined;
-  /** Whether this tab is the current one. */
+  /** Whether this is the current one.
+
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixTab["selected"]) | undefined;
-  /** Identifies the tab, and pairs it with the panel of the same value. */
+  /** Identifies this one to the set, and is what a form submits. */
   value?: (HelixTab["value"]) | undefined;
 
   /** Fired when the tab is chosen. Cancelable: refusing it takes the decision and nothing moves. */
@@ -17222,11 +17304,15 @@ export type HelixTabProps = {
 };
 
 export type HelixTabSolidJsProps = {
-  /** Whether the tab can be chosen. */
+  /** Whether this one can be chosen. */
   "prop:disabled"?: (HelixTab["disabled"]) | undefined;
-  /** Whether this tab is the current one. */
+  /** Whether this is the current one.
+
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   "prop:selected"?: (HelixTab["selected"]) | undefined;
-  /** Identifies the tab, and pairs it with the panel of the same value. */
+  /** Identifies this one to the set, and is what a form submits. */
   "prop:value"?: (HelixTab["value"]) | undefined;
   /** Fired when the tab is chosen. Cancelable: refusing it takes the decision and nothing moves. */
   "on:helix-select"?: ((e: HelixTabHelixSelectElementEvent) => void) | undefined;
@@ -18882,11 +18968,15 @@ export type HelixToggleHelixSelectElementEvent =
   HelixToggleElementEvent<HelixSelectEvent>;
 
 export type HelixToggleProps = {
-  /** Whether the item can be chosen. */
+  /** Whether this one can be chosen. */
   disabled?: (HelixToggle["disabled"]) | undefined;
-  /** Whether this item is the current one. */
+  /** Whether this is the current one.
+
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixToggle["selected"]) | undefined;
-  /** Identifies the item to the group. */
+  /** Identifies this one to the set, and is what a form submits. */
   value?: (HelixToggle["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.
 
@@ -18928,11 +19018,15 @@ hydration reports and does not patch up. */
 };
 
 export type HelixToggleSolidJsProps = {
-  /** Whether the item can be chosen. */
+  /** Whether this one can be chosen. */
   "prop:disabled"?: (HelixToggle["disabled"]) | undefined;
-  /** Whether this item is the current one. */
+  /** Whether this is the current one.
+
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   "prop:selected"?: (HelixToggle["selected"]) | undefined;
-  /** Identifies the item to the group. */
+  /** Identifies this one to the set, and is what a form submits. */
   "prop:value"?: (HelixToggle["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.
 
@@ -20999,10 +21093,9 @@ export type CustomElements = {
    * it up to the surface step, for a band that reads as part of the furniture
    * rather than as a slot cut into it.
    *
-   * **This was `tone="surface"`**, which put an elevation on the axis that says
-   * what a thing means. The band's own doc admitted it, calling `surface` the
-   * one value that was not a color. A band can be `info` and elevated at the
-   * same time, and two values that can both be true are two axes.
+   * **`separation` and not `tone`, because a rung is not a meaning.** A band
+   * can be `info` and elevated at the same time, and two values that can both
+   * be true are two axes, which is the test the registry answers to.
    *
    * Styled and not headless, because a rung of a ladder is paint: the headless
    * tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -21305,6 +21398,13 @@ export type CustomElements = {
    *
    * Absent rather than defaulted because a reflecting property with a default
    * writes its attribute onto every host, including the ones nobody configured.
+   * The resting value therefore lives in the render, as `curve ?? 'straight'`.
+   *
+   * **`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+   * line claims a position, so the bounded invention a monotone cubic makes is
+   * a reading aid and costs nothing. A band claims an amount, and two sums
+   * smoothed independently can cross, so the same aid here draws a part as less
+   * than nothing. Same axis, different mark, different resting value.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * The same three values `LineChart` takes, with the same fallback: a bare
@@ -27102,6 +27202,21 @@ export type CustomElements = {
    * - `showingPage`: Whether this row's own page is the one showing.
    *
    * Written by the stack. (property only)
+   * - `selected`: Whether this is the row the set is on, which in a drill-down is where focus
+   * is.
+   *
+   * A radio group's selection is an answer it holds; a page of rows has no
+   * answer, only the row a reader has walked to, so focus is the whole of what
+   * "the current one" can mean here. This is `Menu.Item`'s reading word for
+   * word, and the two are one pattern: a menu that drills and a drill-down are
+   * the same rows through the same controller.
+   *
+   * Asked of the document rather than of the shadow root. `focusItem` puts
+   * focus on the control inside this row and the platform retargets it, so from
+   * outside the shadow tree `activeElement` is this element already and nothing
+   * has to walk a tree. `ShadowRoot.activeElement` is also the reading that does
+   * not survive happy-dom, which climbs `getRootNode()` to the top and then
+   * dereferences what it ran out of. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -29665,6 +29780,12 @@ export type CustomElements = {
    * `curve ?? 'smooth'`.
    *
    * `step` claims the opposite of both, that a reading holds until the next.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * Absent draws none, which is the honest default rather than a timid one: a
@@ -30834,8 +30955,10 @@ export type CustomElements = {
    * where one is the number being watched and the rest are context, which is a
    * fact about the region rather than about any one of them.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` earns its
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+   * the whole of what quiet means here. `outlined` earns its
    * place in `BarChart`, which keeps the area and fades it toward the page, only
    * because a chart has other series for the outlined one to be a *different
    * kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -31203,6 +31326,13 @@ export type CustomElements = {
    * separated.** A consumer wanting the whole feed carded says so once, in a
    * document rule on the element, rather than on every item: this is a styled
    * axis and a stylesheet is where it is set.
+   * - `dismissible`: Whether it offers a control to take it away.
+   * - `dismiss-label`/`dismissLabel`: Accessible name for that control.
+   *
+   * `attribute` is spelled out because Lit lowercases a property name to
+   * derive one rather than dash-casing it, so this would otherwise be
+   * reachable only as `dismisslabel`, which nobody would guess and no linter
+   * would catch.
    * - `at`: When it happened, as anything `Date` parses.
    *
    * An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -31223,8 +31353,6 @@ export type CustomElements = {
    * declaration. `:state(read)` is what the stylesheet reads.
    * `hydration.dom.spec.ts` holds it.
    * - `default-read`/`defaultRead`: State to open with, where nothing declared one.
-   * - `dismissible`: Whether a reader may remove it.
-   * - `dismiss-label`/`dismissLabel`: Accessible name for the dismiss control.
    * - `locale`: Locale for the timestamp.
    *
    * Empty is the runtime's own.
@@ -31271,6 +31399,7 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `dismiss() => boolean`: Announces that it should go, and reports whether the request stood.
    * - `markRead(next = true) => boolean`: Asks to be marked read, and reports whether the request stood.
    *
    * Public because a consumer's own control is as likely to ask as this
@@ -32132,7 +32261,7 @@ export type CustomElements = {
    *
    * Reflected because the stylesheet selects on it. The mesh is chosen from the
    * rendered box rather than from this, so `--orb-size` and a consumer's own
-   * `inline-size` get the same treatment as the three named steps.
+   * `inline-size` get the same treatment as the named steps.
    * - `state`: What the agent is doing.
    *
    * **A name we do not draw is drawn as `thinking` rather than as nothing.**
@@ -32989,8 +33118,10 @@ export type CustomElements = {
    * the loudest thing in the region. The case is a background task, which has to
    * be visible and must not compete with what the reader is actually looking at.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` is the
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+   * whole of what quiet means here. `outlined` is the
    * interesting refusal: `BarChart` earns it by keeping the area and fading it
    * toward the page, so an outlined column still encodes its value and stands as
    * a *different kind of fact* from the series beside it (a forecast, a target,
@@ -33119,11 +33250,13 @@ export type CustomElements = {
    * and a URL is a better name than "QR code" for a reader who cannot see it.
    * - `shape`: How the modules are drawn.
    *
-   * `square` is the default and the only one that joins runs of adjacent
-   * modules into a single subpath, which is what keeps a thousand modules to a
-   * handful of nodes. `rounded` and `dots` draw each module on its own, because
-   * the corners are the thing being drawn and a joined run has none in the
-   * middle. That cost is paid only by a code that asks for them.
+   * `square` is the resting state and is written by not writing it, per the
+   * rule that a reflected property takes no default. It is also the only one
+   * that joins runs of adjacent modules into a single subpath, which is what
+   * keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+   * each module on its own, because the corners are the thing being drawn and a
+   * joined run has none in the middle. That cost is paid only by a code that
+   * asks for them.
    *
    * A scanner reads contrast between cells, not their shape, so all three
    * scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -33462,11 +33595,13 @@ export type CustomElements = {
    * The circle stays in both. A card whose only marker was its own border would
    * ask a reader to compare surfaces across a row to find the answer, and would
    * leave nothing for a high-contrast display.
-   * - `disabled`: Whether this choice can be made.
-   * - `selected`: Whether this is the current choice.
+   * - `disabled`: Whether this one can be chosen.
+   * - `selected`: Whether this is the current one.
    *
-   * Written by the group.
-   * - `value`: Identifies this choice to the group, and is what the form submits.
+   * Written by the set rather than by a consumer, which is why it takes no
+   * default from an attribute here: a family whose selection a consumer
+   * declares in markup carries `defaultSelected` of its own to say so.
+   * - `value`: Identifies this one to the set, and is what a form submits.
    * - `defaultSelected`: Whether the markup declared this one chosen, which is what a reset returns to.
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
@@ -33544,8 +33679,12 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `focusItem() => void`: Moves focus to this choice, for the group's arrow keys.
-   * - `select() => void`: Makes this choice and announces it.
+   * - `focusItem() => void`: Moves focus to the control this renders, for the set's arrow keys.
+   *
+   * The set drives the keys and cannot reach the control itself, which is
+   * inside this shadow root, so the intent is a method and the internals stay
+   * the item's.
+   * - `select() => boolean`: Chooses this one and announces it, and reports whether it stood.
    *
    * ## CSS Custom Properties
    *
@@ -34693,9 +34832,12 @@ export type CustomElements = {
    * **`emphasis` and not `separation`, which the registry decides rather than
    * taste.** Emphasis is asked of controls, how loud this one is; separation is
    * asked of containers, where the surface ends. A trigger is a control, and a
-   * family may not declare both. Two of the four values are refused: `solid` and
-   * `subtle` are a button's way of being the one thing to press, which is not a
-   * thing an answer should ever be.
+   * family may not declare both. Three of the five values are refused: `solid`
+   * and `subtle` are a button's way of being the one thing to press, which is
+   * not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+   * takes, where a trigger's loudness is its frame rather than its ink.
+   * `outlined` is what the unset frame already draws, so writing it would be
+   * writing the resting state out.
    *
    * **The other three fields want this too and do not have it yet.** `Input`,
    * `Textarea` and `Combobox` wear the same frame from the same shared
@@ -35372,6 +35514,12 @@ export type CustomElements = {
    *
    * `step` claims the opposite of both, that a reading holds until the next.
    * Bars ignore it, having no between to interpolate.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `for`: The id of a table to read instead, when there is one behind the line.
    *
    * The first column of numbers is the series drawn. This wins over `values`,
@@ -36936,9 +37084,13 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `disabled`: Whether the tab can be chosen.
-   * - `selected`: Whether this tab is the current one.
-   * - `value`: Identifies the tab, and pairs it with the panel of the same value.
+   * - `disabled`: Whether this one can be chosen.
+   * - `selected`: Whether this is the current one.
+   *
+   * Written by the set rather than by a consumer, which is why it takes no
+   * default from an attribute here: a family whose selection a consumer
+   * declares in markup carries `defaultSelected` of its own to say so.
+   * - `value`: Identifies this one to the set, and is what a form submits.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -36976,8 +37128,12 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `focusItem() => void`: Moves focus to this tab, for the list's arrow keys.
-   * - `select() => void`: Selects this tab and announces it.
+   * - `focusItem() => void`: Moves focus to the control this renders, for the set's arrow keys.
+   *
+   * The set drives the keys and cannot reach the control itself, which is
+   * inside this shadow root, so the intent is a method and the internals stay
+   * the item's.
+   * - `select() => boolean`: Chooses this one and announces it, and reports whether it stood.
    *
    * ## CSS Parts
    *
@@ -38543,9 +38699,13 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `disabled`: Whether the item can be chosen.
-   * - `selected`: Whether this item is the current one.
-   * - `value`: Identifies the item to the group.
+   * - `disabled`: Whether this one can be chosen.
+   * - `selected`: Whether this is the current one.
+   *
+   * Written by the set rather than by a consumer, which is why it takes no
+   * default from an attribute here: a family whose selection a consumer
+   * declares in markup carries `defaultSelected` of its own to say so.
+   * - `value`: Identifies this one to the set, and is what a form submits.
    * - `defaultSelected`: Whether the markup declared this one chosen, which is what a reset returns to.
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
@@ -38615,12 +38775,12 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `focusItem() => void`: Moves focus to this item's own control.
+   * - `focusItem() => void`: Moves focus to the control this renders, for the set's arrow keys.
    *
-   * The group drives arrow-key navigation and cannot reach the control itself,
-   * which is inside this shadow root. Exposing the intent as a method keeps the
-   * group out of the child's internals.
-   * - `select() => void`: Chooses this item and announces it.
+   * The set drives the keys and cannot reach the control itself, which is
+   * inside this shadow root, so the intent is a method and the internals stay
+   * the item's.
+   * - `select() => boolean`: Chooses this one and announces it, and reports whether it stood.
    *
    * ## CSS Parts
    *
@@ -40437,10 +40597,9 @@ export type CustomElementsSolidJs = {
    * it up to the surface step, for a band that reads as part of the furniture
    * rather than as a slot cut into it.
    *
-   * **This was `tone="surface"`**, which put an elevation on the axis that says
-   * what a thing means. The band's own doc admitted it, calling `surface` the
-   * one value that was not a color. A band can be `info` and elevated at the
-   * same time, and two values that can both be true are two axes.
+   * **`separation` and not `tone`, because a rung is not a meaning.** A band
+   * can be `info` and elevated at the same time, and two values that can both
+   * be true are two axes, which is the test the registry answers to.
    *
    * Styled and not headless, because a rung of a ladder is paint: the headless
    * tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -40749,6 +40908,13 @@ export type CustomElementsSolidJs = {
    *
    * Absent rather than defaulted because a reflecting property with a default
    * writes its attribute onto every host, including the ones nobody configured.
+   * The resting value therefore lives in the render, as `curve ?? 'straight'`.
+   *
+   * **`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+   * line claims a position, so the bounded invention a monotone cubic makes is
+   * a reading aid and costs nothing. A band claims an amount, and two sums
+   * smoothed independently can cross, so the same aid here draws a part as less
+   * than nothing. Same axis, different mark, different resting value.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * The same three values `LineChart` takes, with the same fallback: a bare
@@ -46647,6 +46813,21 @@ export type CustomElementsSolidJs = {
    * - `showingPage`: Whether this row's own page is the one showing.
    *
    * Written by the stack. (property only)
+   * - `selected`: Whether this is the row the set is on, which in a drill-down is where focus
+   * is.
+   *
+   * A radio group's selection is an answer it holds; a page of rows has no
+   * answer, only the row a reader has walked to, so focus is the whole of what
+   * "the current one" can mean here. This is `Menu.Item`'s reading word for
+   * word, and the two are one pattern: a menu that drills and a drill-down are
+   * the same rows through the same controller.
+   *
+   * Asked of the document rather than of the shadow root. `focusItem` puts
+   * focus on the control inside this row and the platform retargets it, so from
+   * outside the shadow tree `activeElement` is this element already and nothing
+   * has to walk a tree. `ShadowRoot.activeElement` is also the reading that does
+   * not survive happy-dom, which climbs `getRootNode()` to the top and then
+   * dereferences what it ran out of. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -49269,6 +49450,12 @@ export type CustomElementsSolidJs = {
    * `curve ?? 'smooth'`.
    *
    * `step` claims the opposite of both, that a reading holds until the next.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * Absent draws none, which is the honest default rather than a timid one: a
@@ -50460,8 +50647,10 @@ export type CustomElementsSolidJs = {
    * where one is the number being watched and the rest are context, which is a
    * fact about the region rather than about any one of them.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` earns its
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+   * the whole of what quiet means here. `outlined` earns its
    * place in `BarChart`, which keeps the area and fades it toward the page, only
    * because a chart has other series for the outlined one to be a *different
    * kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -50840,6 +51029,13 @@ export type CustomElementsSolidJs = {
    * separated.** A consumer wanting the whole feed carded says so once, in a
    * document rule on the element, rather than on every item: this is a styled
    * axis and a stylesheet is where it is set.
+   * - `dismissible`: Whether it offers a control to take it away.
+   * - `dismiss-label`/`dismissLabel`: Accessible name for that control.
+   *
+   * `attribute` is spelled out because Lit lowercases a property name to
+   * derive one rather than dash-casing it, so this would otherwise be
+   * reachable only as `dismisslabel`, which nobody would guess and no linter
+   * would catch.
    * - `at`: When it happened, as anything `Date` parses.
    *
    * An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -50860,8 +51056,6 @@ export type CustomElementsSolidJs = {
    * declaration. `:state(read)` is what the stylesheet reads.
    * `hydration.dom.spec.ts` holds it.
    * - `default-read`/`defaultRead`: State to open with, where nothing declared one.
-   * - `dismissible`: Whether a reader may remove it.
-   * - `dismiss-label`/`dismissLabel`: Accessible name for the dismiss control.
    * - `locale`: Locale for the timestamp.
    *
    * Empty is the runtime's own.
@@ -50908,6 +51102,7 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `dismiss() => boolean`: Announces that it should go, and reports whether the request stood.
    * - `markRead(next = true) => boolean`: Asks to be marked read, and reports whether the request stood.
    *
    * Public because a consumer's own control is as likely to ask as this
@@ -51787,7 +51982,7 @@ export type CustomElementsSolidJs = {
    *
    * Reflected because the stylesheet selects on it. The mesh is chosen from the
    * rendered box rather than from this, so `--orb-size` and a consumer's own
-   * `inline-size` get the same treatment as the three named steps.
+   * `inline-size` get the same treatment as the named steps.
    * - `state`: What the agent is doing.
    *
    * **A name we do not draw is drawn as `thinking` rather than as nothing.**
@@ -52664,8 +52859,10 @@ export type CustomElementsSolidJs = {
    * the loudest thing in the region. The case is a background task, which has to
    * be visible and must not compete with what the reader is actually looking at.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` is the
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+   * whole of what quiet means here. `outlined` is the
    * interesting refusal: `BarChart` earns it by keeping the area and fading it
    * toward the page, so an outlined column still encodes its value and stands as
    * a *different kind of fact* from the series beside it (a forecast, a target,
@@ -52797,11 +52994,13 @@ export type CustomElementsSolidJs = {
    * and a URL is a better name than "QR code" for a reader who cannot see it.
    * - `shape`: How the modules are drawn.
    *
-   * `square` is the default and the only one that joins runs of adjacent
-   * modules into a single subpath, which is what keeps a thousand modules to a
-   * handful of nodes. `rounded` and `dots` draw each module on its own, because
-   * the corners are the thing being drawn and a joined run has none in the
-   * middle. That cost is paid only by a code that asks for them.
+   * `square` is the resting state and is written by not writing it, per the
+   * rule that a reflected property takes no default. It is also the only one
+   * that joins runs of adjacent modules into a single subpath, which is what
+   * keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+   * each module on its own, because the corners are the thing being drawn and a
+   * joined run has none in the middle. That cost is paid only by a code that
+   * asks for them.
    *
    * A scanner reads contrast between cells, not their shape, so all three
    * scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -53151,11 +53350,13 @@ export type CustomElementsSolidJs = {
    * The circle stays in both. A card whose only marker was its own border would
    * ask a reader to compare surfaces across a row to find the answer, and would
    * leave nothing for a high-contrast display.
-   * - `disabled`: Whether this choice can be made.
-   * - `selected`: Whether this is the current choice.
+   * - `disabled`: Whether this one can be chosen.
+   * - `selected`: Whether this is the current one.
    *
-   * Written by the group.
-   * - `value`: Identifies this choice to the group, and is what the form submits.
+   * Written by the set rather than by a consumer, which is why it takes no
+   * default from an attribute here: a family whose selection a consumer
+   * declares in markup carries `defaultSelected` of its own to say so.
+   * - `value`: Identifies this one to the set, and is what a form submits.
    * - `defaultSelected`: Whether the markup declared this one chosen, which is what a reset returns to.
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
@@ -53233,8 +53434,12 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `focusItem() => void`: Moves focus to this choice, for the group's arrow keys.
-   * - `select() => void`: Makes this choice and announces it.
+   * - `focusItem() => void`: Moves focus to the control this renders, for the set's arrow keys.
+   *
+   * The set drives the keys and cannot reach the control itself, which is
+   * inside this shadow root, so the intent is a method and the internals stay
+   * the item's.
+   * - `select() => boolean`: Chooses this one and announces it, and reports whether it stood.
    *
    * ## CSS Custom Properties
    *
@@ -54414,9 +54619,12 @@ export type CustomElementsSolidJs = {
    * **`emphasis` and not `separation`, which the registry decides rather than
    * taste.** Emphasis is asked of controls, how loud this one is; separation is
    * asked of containers, where the surface ends. A trigger is a control, and a
-   * family may not declare both. Two of the four values are refused: `solid` and
-   * `subtle` are a button's way of being the one thing to press, which is not a
-   * thing an answer should ever be.
+   * family may not declare both. Three of the five values are refused: `solid`
+   * and `subtle` are a button's way of being the one thing to press, which is
+   * not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+   * takes, where a trigger's loudness is its frame rather than its ink.
+   * `outlined` is what the unset frame already draws, so writing it would be
+   * writing the resting state out.
    *
    * **The other three fields want this too and do not have it yet.** `Input`,
    * `Textarea` and `Combobox` wear the same frame from the same shared
@@ -55105,6 +55313,12 @@ export type CustomElementsSolidJs = {
    *
    * `step` claims the opposite of both, that a reading holds until the next.
    * Bars ignore it, having no between to interpolate.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `for`: The id of a table to read instead, when there is one behind the line.
    *
    * The first column of numbers is the series drawn. This wins over `values`,
@@ -56715,9 +56929,13 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `disabled`: Whether the tab can be chosen.
-   * - `selected`: Whether this tab is the current one.
-   * - `value`: Identifies the tab, and pairs it with the panel of the same value.
+   * - `disabled`: Whether this one can be chosen.
+   * - `selected`: Whether this is the current one.
+   *
+   * Written by the set rather than by a consumer, which is why it takes no
+   * default from an attribute here: a family whose selection a consumer
+   * declares in markup carries `defaultSelected` of its own to say so.
+   * - `value`: Identifies this one to the set, and is what a form submits.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
    * **Named `whenSettled` because `settled` is taken four times over**, by
@@ -56755,8 +56973,12 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `focusItem() => void`: Moves focus to this tab, for the list's arrow keys.
-   * - `select() => void`: Selects this tab and announces it.
+   * - `focusItem() => void`: Moves focus to the control this renders, for the set's arrow keys.
+   *
+   * The set drives the keys and cannot reach the control itself, which is
+   * inside this shadow root, so the intent is a method and the internals stay
+   * the item's.
+   * - `select() => boolean`: Chooses this one and announces it, and reports whether it stood.
    *
    * ## CSS Parts
    *
@@ -58354,9 +58576,13 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `disabled`: Whether the item can be chosen.
-   * - `selected`: Whether this item is the current one.
-   * - `value`: Identifies the item to the group.
+   * - `disabled`: Whether this one can be chosen.
+   * - `selected`: Whether this is the current one.
+   *
+   * Written by the set rather than by a consumer, which is why it takes no
+   * default from an attribute here: a family whose selection a consumer
+   * declares in markup carries `defaultSelected` of its own to say so.
+   * - `value`: Identifies this one to the set, and is what a form submits.
    * - `defaultSelected`: Whether the markup declared this one chosen, which is what a reset returns to.
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
@@ -58426,12 +58652,12 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
-   * - `focusItem() => void`: Moves focus to this item's own control.
+   * - `focusItem() => void`: Moves focus to the control this renders, for the set's arrow keys.
    *
-   * The group drives arrow-key navigation and cannot reach the control itself,
-   * which is inside this shadow root. Exposing the intent as a method keeps the
-   * group out of the child's internals.
-   * - `select() => void`: Chooses this item and announces it.
+   * The set drives the keys and cannot reach the control itself, which is
+   * inside this shadow root, so the intent is a method and the internals stay
+   * the item's.
+   * - `select() => boolean`: Chooses this one and announces it, and reports whether it stood.
    *
    * ## CSS Parts
    *