@fusion.dev/helix-headless 0.53.0 → 0.53.2

package/types/jsx.d.ts

@@ -860,13 +860,13 @@ export type HelixHeadlessAvatarGroupProps = {
 Unset shows all of them, which is what no limit means and is more useful
 than refusing to render.
 
-**Reflected, because the fold is a stylesheet rule and nothing else.** The
-styled tier hides past the limit with `:host([max="N"]) ::slotted(:nth-child(n + N+1))`,
-so the attribute *is* the mechanism: a `max` that reaches this property and
-never reaches the host matches no rule, and every avatar is drawn beside a
-count claiming some are hidden. Markup is the safe path and hides the fault;
-a script is the broken one, and React takes it for everyone, assigning a
-matching property rather than an attribute.
+**Reflected, because the fold is a stylesheet rule and nothing else.** A
+sheet hides past the limit one selector per value, as `FOLDS_UP_TO`
+describes, so the attribute *is* the mechanism: a `max` that reaches this
+property and never reaches the host matches no rule, and every avatar is
+drawn beside a count claiming some are hidden. Markup is the safe path and
+hides the fault; a script is the broken one, and React takes it for
+everyone, assigning a matching property rather than an attribute.
 
 **Optional rather than defaulted, per the rule that a reflected property
 takes no default**: `max = 0` would stamp `max="0"` onto every host that
@@ -882,13 +882,13 @@ export type HelixHeadlessAvatarGroupSolidJsProps = {
 Unset shows all of them, which is what no limit means and is more useful
 than refusing to render.
 
-**Reflected, because the fold is a stylesheet rule and nothing else.** The
-styled tier hides past the limit with `:host([max="N"]) ::slotted(:nth-child(n + N+1))`,
-so the attribute *is* the mechanism: a `max` that reaches this property and
-never reaches the host matches no rule, and every avatar is drawn beside a
-count claiming some are hidden. Markup is the safe path and hides the fault;
-a script is the broken one, and React takes it for everyone, assigning a
-matching property rather than an attribute.
+**Reflected, because the fold is a stylesheet rule and nothing else.** A
+sheet hides past the limit one selector per value, as `FOLDS_UP_TO`
+describes, so the attribute *is* the mechanism: a `max` that reaches this
+property and never reaches the host matches no rule, and every avatar is
+drawn beside a count claiming some are hidden. Markup is the safe path and
+hides the fault; a script is the broken one, and React takes it for
+everyone, assigning a matching property rather than an attribute.
 
 **Optional rather than defaulted, per the rule that a reflected property
 takes no default**: `max = 0` would stamp `max="0"` onto every host that
@@ -1237,12 +1237,12 @@ export type HelixHeadlessBreadcrumbProps = {
   current?: (HelixHeadlessBreadcrumb["current"]) | undefined;
   /** Where the crumb goes, and nothing where it is the current page.
 
-**Optional and reflected, because a stylesheet does select on it.**
-`breadcrumb.css` writes `:host(:not([href])) [part="link"]` to take the
-block padding off a crumb that is not a link, so the attribute is what
-decides how tall a crumb is. Unreflected, an `href` set from script reached
-the property, rendered the anchor, and left the host looking unlinked: the
-crumb drew at 20px where a markup twin drew at 28.
+**Optional and reflected, because a stylesheet does select on it.** A sheet
+writes `:host(:not([href])) [part="link"]` to take the block padding off a
+crumb that is not a link, so the attribute is what decides how tall a crumb
+is. Unreflected, an `href` set from script reached the property, rendered
+the anchor, and left the host looking unlinked: the crumb drew at 20px
+where a markup twin drew at 28.
 
 Optional rather than defaulted, which is the general rule that a reflected
 property takes no default: an `href` written onto every host would be a link
@@ -1265,12 +1265,12 @@ export type HelixHeadlessBreadcrumbSolidJsProps = {
   "prop:current"?: (HelixHeadlessBreadcrumb["current"]) | undefined;
   /** Where the crumb goes, and nothing where it is the current page.
 
-**Optional and reflected, because a stylesheet does select on it.**
-`breadcrumb.css` writes `:host(:not([href])) [part="link"]` to take the
-block padding off a crumb that is not a link, so the attribute is what
-decides how tall a crumb is. Unreflected, an `href` set from script reached
-the property, rendered the anchor, and left the host looking unlinked: the
-crumb drew at 20px where a markup twin drew at 28.
+**Optional and reflected, because a stylesheet does select on it.** A sheet
+writes `:host(:not([href])) [part="link"]` to take the block padding off a
+crumb that is not a link, so the attribute is what decides how tall a crumb
+is. Unreflected, an `href` set from script reached the property, rendered
+the anchor, and left the host looking unlinked: the crumb drew at 20px
+where a markup twin drew at 28.
 
 Optional rather than defaulted, which is the general rule that a reflected
 property takes no default: an `href` written onto every host would be a link
@@ -1369,7 +1369,7 @@ the trigger silently does nothing at all. A wrapper has to hand them down,
 the same way `label` becomes `aria-label` in there.
 
 ```html
-<helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+<helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
 ```
 
 `commandFor` spells its attribute out, because Lit lowercases a property
@@ -1530,7 +1530,7 @@ the trigger silently does nothing at all. A wrapper has to hand them down,
 the same way `label` becomes `aria-label` in there.
 
 ```html
-<helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+<helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
 ```
 
 `commandFor` spells its attribute out, because Lit lowercases a property
@@ -1857,13 +1857,13 @@ end while the slides stop moving a third of the way through.
 **The number is published to the styles rather than enumerated by them**,
 as `--carousel-per-view` on the track, which is what keeps a width and a
 count from disagreeing. A sheet can only name a value it wrote a rule for,
-so the styled tier enumerated `per-view="2"` through `5` and called five a
-judgment; above it the pane fell back to one across while this file went on
-counting positions. Measured in Chromium over eight slides, six across gave
-three dots, a pane taking the whole track and five slides reachable only by
-dragging. Written from here there is no ceiling to exceed, and a consumer's
-own sheet reads the same declaration the styled one does. `runEnd` publishes
-its correction the same way and for the same reason.
+so a sheet enumerating `per-view="2"` through `5` is a ceiling of five, and
+above it the pane falls back to one across while this file goes on counting
+positions. Measured in Chromium over eight slides against such a sheet, six
+across gave three dots, a pane taking the whole track and five slides
+reachable only by dragging. Published from here there is no ceiling to
+exceed, and every sheet reads the same declaration. `runEnd` publishes its
+correction the same way and for the same reason.
 
 **On the track and not on the host.** A custom property on the host is a
 reflected attribute by another name: it would arrive on upgrade, and a
@@ -1888,8 +1888,8 @@ inline the count would outrank the sheet that computes it, which is why an
 `auto` track is handed nothing. A count stays for the design that calls for
 exactly three.
 
-The styled sheet says how it divides, and the headless `auto` example
-carries the same three lines for a consumer writing their own.
+A sheet says how it divides, and the `auto` example here carries the same
+three lines for a consumer writing their own.
 
 **A value rather than the resting behavior**, which is what the
 responsiveness policy asks of every axis that a box decides: a splitter
@@ -1917,13 +1917,13 @@ end while the slides stop moving a third of the way through.
 **The number is published to the styles rather than enumerated by them**,
 as `--carousel-per-view` on the track, which is what keeps a width and a
 count from disagreeing. A sheet can only name a value it wrote a rule for,
-so the styled tier enumerated `per-view="2"` through `5` and called five a
-judgment; above it the pane fell back to one across while this file went on
-counting positions. Measured in Chromium over eight slides, six across gave
-three dots, a pane taking the whole track and five slides reachable only by
-dragging. Written from here there is no ceiling to exceed, and a consumer's
-own sheet reads the same declaration the styled one does. `runEnd` publishes
-its correction the same way and for the same reason.
+so a sheet enumerating `per-view="2"` through `5` is a ceiling of five, and
+above it the pane falls back to one across while this file goes on counting
+positions. Measured in Chromium over eight slides against such a sheet, six
+across gave three dots, a pane taking the whole track and five slides
+reachable only by dragging. Published from here there is no ceiling to
+exceed, and every sheet reads the same declaration. `runEnd` publishes its
+correction the same way and for the same reason.
 
 **On the track and not on the host.** A custom property on the host is a
 reflected attribute by another name: it would arrive on upgrade, and a
@@ -1948,8 +1948,8 @@ inline the count would outrank the sheet that computes it, which is why an
 `auto` track is handed nothing. A count stays for the design that calls for
 exactly three.
 
-The styled sheet says how it divides, and the headless `auto` example
-carries the same three lines for a consumer writing their own.
+A sheet says how it divides, and the `auto` example here carries the same
+three lines for a consumer writing their own.
 
 **A value rather than the resting behavior**, which is what the
 responsiveness policy asks of every axis that a box decides: a splitter
@@ -2046,13 +2046,13 @@ end while the slides stop moving a third of the way through.
 **The number is published to the styles rather than enumerated by them**,
 as `--carousel-per-view` on the track, which is what keeps a width and a
 count from disagreeing. A sheet can only name a value it wrote a rule for,
-so the styled tier enumerated `per-view="2"` through `5` and called five a
-judgment; above it the pane fell back to one across while this file went on
-counting positions. Measured in Chromium over eight slides, six across gave
-three dots, a pane taking the whole track and five slides reachable only by
-dragging. Written from here there is no ceiling to exceed, and a consumer's
-own sheet reads the same declaration the styled one does. `runEnd` publishes
-its correction the same way and for the same reason.
+so a sheet enumerating `per-view="2"` through `5` is a ceiling of five, and
+above it the pane falls back to one across while this file goes on counting
+positions. Measured in Chromium over eight slides against such a sheet, six
+across gave three dots, a pane taking the whole track and five slides
+reachable only by dragging. Published from here there is no ceiling to
+exceed, and every sheet reads the same declaration. `runEnd` publishes its
+correction the same way and for the same reason.
 
 **On the track and not on the host.** A custom property on the host is a
 reflected attribute by another name: it would arrive on upgrade, and a
@@ -2077,8 +2077,8 @@ inline the count would outrank the sheet that computes it, which is why an
 `auto` track is handed nothing. A count stays for the design that calls for
 exactly three.
 
-The styled sheet says how it divides, and the headless `auto` example
-carries the same three lines for a consumer writing their own.
+A sheet says how it divides, and the `auto` example here carries the same
+three lines for a consumer writing their own.
 
 **A value rather than the resting behavior**, which is what the
 responsiveness policy asks of every axis that a box decides: a splitter
@@ -2106,13 +2106,13 @@ end while the slides stop moving a third of the way through.
 **The number is published to the styles rather than enumerated by them**,
 as `--carousel-per-view` on the track, which is what keeps a width and a
 count from disagreeing. A sheet can only name a value it wrote a rule for,
-so the styled tier enumerated `per-view="2"` through `5` and called five a
-judgment; above it the pane fell back to one across while this file went on
-counting positions. Measured in Chromium over eight slides, six across gave
-three dots, a pane taking the whole track and five slides reachable only by
-dragging. Written from here there is no ceiling to exceed, and a consumer's
-own sheet reads the same declaration the styled one does. `runEnd` publishes
-its correction the same way and for the same reason.
+so a sheet enumerating `per-view="2"` through `5` is a ceiling of five, and
+above it the pane falls back to one across while this file goes on counting
+positions. Measured in Chromium over eight slides against such a sheet, six
+across gave three dots, a pane taking the whole track and five slides
+reachable only by dragging. Published from here there is no ceiling to
+exceed, and every sheet reads the same declaration. `runEnd` publishes its
+correction the same way and for the same reason.
 
 **On the track and not on the host.** A custom property on the host is a
 reflected attribute by another name: it would arrive on upgrade, and a
@@ -2137,8 +2137,8 @@ inline the count would outrank the sheet that computes it, which is why an
 `auto` track is handed nothing. A count stays for the design that calls for
 exactly three.
 
-The styled sheet says how it divides, and the headless `auto` example
-carries the same three lines for a consumer writing their own.
+A sheet says how it divides, and the `auto` example here carries the same
+three lines for a consumer writing their own.
 
 **A value rather than the resting behavior**, which is what the
 responsiveness policy asks of every axis that a box decides: a splitter
@@ -2387,13 +2387,13 @@ pinned because a conversation opens at its most recent turn.
 
 **Not reflected, and the default is why.** A reflected property that
 defaults to true writes its attribute on upgrade whether or not the
-consumer wrote one, so the server serves `<helix-chat label="x">` and the
-client turns it into `<helix-chat label="x" pinned>`: a hydration mismatch a
-React consumer reports and does not patch up. Nothing needs the attribute
-either, because the one thing that changes with the pin is the way back, and
-that is a part inside the shadow tree where a stylesheet can already reach
-it. Measured rather than assumed: `label, pinned` after upgrade against
-`label` from the server. */
+consumer wrote one, so the server serves `<helix-headless-chat label="x">`
+and the client turns it into `<helix-headless-chat label="x" pinned>`: a
+hydration mismatch a React consumer reports and does not patch up. Nothing
+needs the attribute either, because the one thing that changes with the pin
+is the way back, and that is a part inside the shadow tree where a
+stylesheet can already reach it. Measured rather than assumed: `label,
+pinned` after upgrade against `label` from the server. */
   pinned?: (HelixHeadlessChat["pinned"]) | undefined;
   /** How near the bottom still counts as being at it, in pixels.
 
@@ -2464,13 +2464,13 @@ pinned because a conversation opens at its most recent turn.
 
 **Not reflected, and the default is why.** A reflected property that
 defaults to true writes its attribute on upgrade whether or not the
-consumer wrote one, so the server serves `<helix-chat label="x">` and the
-client turns it into `<helix-chat label="x" pinned>`: a hydration mismatch a
-React consumer reports and does not patch up. Nothing needs the attribute
-either, because the one thing that changes with the pin is the way back, and
-that is a part inside the shadow tree where a stylesheet can already reach
-it. Measured rather than assumed: `label, pinned` after upgrade against
-`label` from the server. */
+consumer wrote one, so the server serves `<helix-headless-chat label="x">`
+and the client turns it into `<helix-headless-chat label="x" pinned>`: a
+hydration mismatch a React consumer reports and does not patch up. Nothing
+needs the attribute either, because the one thing that changes with the pin
+is the way back, and that is a part inside the shadow tree where a
+stylesheet can already reach it. Measured rather than assumed: `label,
+pinned` after upgrade against `label` from the server. */
   "prop:pinned"?: (HelixHeadlessChat["pinned"]) | undefined;
   /** How near the bottom still counts as being at it, in pixels.
 
@@ -2790,11 +2790,11 @@ present, which is true. Measured, and it is why this is named the other way
 round. The platform already writes booleans like this for the same reason,
 `novalidate` and `nomodule` and `noreferrer` among them.
 
-**Reflected, because the gutter is a stylesheet rule.** `code-block.css`
-reserves the copy button's width with `:host(:not([no-copy]))`, so the
-attribute is what decides whether the block pays for a control. Unreflected,
-setting it from script takes the button away (`render` reads the property)
-and leaves the 40px it stood in reserved.
+**Reflected, because the gutter is a stylesheet rule.** A sheet reserves
+the copy button's width with `:host(:not([no-copy]))`, so the attribute is
+what decides whether the block pays for a control. Unreflected, setting it
+from script takes the button away (`render` reads the property) and leaves
+the 40px it stood in reserved.
 
 A false boolean reflects as the attribute's absence, so this costs no
 `no-copy=""` on hosts that never asked for one, and the rule about a
@@ -2810,11 +2810,11 @@ present, which is true. Measured, and it is why this is named the other way
 round. The platform already writes booleans like this for the same reason,
 `novalidate` and `nomodule` and `noreferrer` among them.
 
-**Reflected, because the gutter is a stylesheet rule.** `code-block.css`
-reserves the copy button's width with `:host(:not([no-copy]))`, so the
-attribute is what decides whether the block pays for a control. Unreflected,
-setting it from script takes the button away (`render` reads the property)
-and leaves the 40px it stood in reserved.
+**Reflected, because the gutter is a stylesheet rule.** A sheet reserves
+the copy button's width with `:host(:not([no-copy]))`, so the attribute is
+what decides whether the block pays for a control. Unreflected, setting it
+from script takes the button away (`render` reads the property) and leaves
+the 40px it stood in reserved.
 
 A false boolean reflects as the attribute's absence, so this costs no
 `no-copy=""` on hosts that never asked for one, and the rule about a
@@ -2849,11 +2849,11 @@ present, which is true. Measured, and it is why this is named the other way
 round. The platform already writes booleans like this for the same reason,
 `novalidate` and `nomodule` and `noreferrer` among them.
 
-**Reflected, because the gutter is a stylesheet rule.** `code-block.css`
-reserves the copy button's width with `:host(:not([no-copy]))`, so the
-attribute is what decides whether the block pays for a control. Unreflected,
-setting it from script takes the button away (`render` reads the property)
-and leaves the 40px it stood in reserved.
+**Reflected, because the gutter is a stylesheet rule.** A sheet reserves
+the copy button's width with `:host(:not([no-copy]))`, so the attribute is
+what decides whether the block pays for a control. Unreflected, setting it
+from script takes the button away (`render` reads the property) and leaves
+the 40px it stood in reserved.
 
 A false boolean reflects as the attribute's absence, so this costs no
 `no-copy=""` on hosts that never asked for one, and the rule about a
@@ -2869,11 +2869,11 @@ present, which is true. Measured, and it is why this is named the other way
 round. The platform already writes booleans like this for the same reason,
 `novalidate` and `nomodule` and `noreferrer` among them.
 
-**Reflected, because the gutter is a stylesheet rule.** `code-block.css`
-reserves the copy button's width with `:host(:not([no-copy]))`, so the
-attribute is what decides whether the block pays for a control. Unreflected,
-setting it from script takes the button away (`render` reads the property)
-and leaves the 40px it stood in reserved.
+**Reflected, because the gutter is a stylesheet rule.** A sheet reserves
+the copy button's width with `:host(:not([no-copy]))`, so the attribute is
+what decides whether the block pays for a control. Unreflected, setting it
+from script takes the button away (`render` reads the property) and leaves
+the 40px it stood in reserved.
 
 A false boolean reflects as the attribute's absence, so this costs no
 `no-copy=""` on hosts that never asked for one, and the rule about a
@@ -3315,10 +3315,10 @@ letting it open would take a color from the reader and drop it. */
 
 **A color is exactly as requirable as a date**, which is the comparison
 that settles it: this element extends `HelixFormElement`, carries `name`
-and reports its value, so a consumer writing
-`<helix-color-picker name="brand" required>` inside a form has every reason
-to expect the form to refuse an empty one. Its two siblings in the same
-composition position, Date Picker and Time Picker, both check it.
+and reports its value, so a consumer writing `<helix-headless-color-picker
+name="brand" required>` inside a form has every reason to expect the form
+to refuse an empty one. Its two siblings in the same composition position,
+Date Picker and Time Picker, both check it.
 
 Written out rather than taken from `MixinField`, for the reason those two
 record: the mixin brings a label, a hint and a feedback region, and this is
@@ -3508,10 +3508,10 @@ letting it open would take a color from the reader and drop it. */
 
 **A color is exactly as requirable as a date**, which is the comparison
 that settles it: this element extends `HelixFormElement`, carries `name`
-and reports its value, so a consumer writing
-`<helix-color-picker name="brand" required>` inside a form has every reason
-to expect the form to refuse an empty one. Its two siblings in the same
-composition position, Date Picker and Time Picker, both check it.
+and reports its value, so a consumer writing `<helix-headless-color-picker
+name="brand" required>` inside a form has every reason to expect the form
+to refuse an empty one. Its two siblings in the same composition position,
+Date Picker and Time Picker, both check it.
 
 Written out rather than taken from `MixinField`, for the reason those two
 record: the mixin brings a label, a hint and a feedback region, and this is
@@ -4123,7 +4123,7 @@ the trigger silently does nothing at all. A wrapper has to hand them down,
 the same way `label` becomes `aria-label` in there.
 
 ```html
-<helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+<helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
 ```
 
 `commandFor` spells its attribute out, because Lit lowercases a property
@@ -4292,7 +4292,7 @@ the trigger silently does nothing at all. A wrapper has to hand them down,
 the same way `label` becomes `aria-label` in there.
 
 ```html
-<helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+<helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
 ```
 
 `commandFor` spells its attribute out, because Lit lowercases a property
@@ -4569,17 +4569,17 @@ refusing it leaves the selection as it was. */
 
 **It announces nothing, and that is not an omission.** Nothing in this
 element ever asks for a different page size: a size selector is
-`helix-pagination-size`, which a consumer puts in the `footer` slot and
-answers themselves. Routing this through `requestChange` would announce an
-event the element never has cause to fire. */
+`PaginationSize`, which a consumer puts in the `footer` slot and answers
+themselves. Routing this through `requestChange` would announce an event
+the element never has cause to fire. */
   "page-size"?: (HelixHeadlessDataTable["pageSize"] | `${number}`) | undefined;
   /** How many rows a page holds. Zero is every row, which is what "no paging" means.
 
 **It announces nothing, and that is not an omission.** Nothing in this
 element ever asks for a different page size: a size selector is
-`helix-pagination-size`, which a consumer puts in the `footer` slot and
-answers themselves. Routing this through `requestChange` would announce an
-event the element never has cause to fire. */
+`PaginationSize`, which a consumer puts in the `footer` slot and answers
+themselves. Routing this through `requestChange` would announce an event
+the element never has cause to fire. */
   pageSize?: (HelixHeadlessDataTable["pageSize"]) | undefined;
   /** How many rows the whole result has, where this element cannot count them.
 
@@ -4772,17 +4772,17 @@ refusing it leaves the selection as it was. */
 
 **It announces nothing, and that is not an omission.** Nothing in this
 element ever asks for a different page size: a size selector is
-`helix-pagination-size`, which a consumer puts in the `footer` slot and
-answers themselves. Routing this through `requestChange` would announce an
-event the element never has cause to fire. */
+`PaginationSize`, which a consumer puts in the `footer` slot and answers
+themselves. Routing this through `requestChange` would announce an event
+the element never has cause to fire. */
   "attr:page-size"?: (HelixHeadlessDataTable["pageSize"] | `${number}`) | undefined;
   /** How many rows a page holds. Zero is every row, which is what "no paging" means.
 
 **It announces nothing, and that is not an omission.** Nothing in this
 element ever asks for a different page size: a size selector is
-`helix-pagination-size`, which a consumer puts in the `footer` slot and
-answers themselves. Routing this through `requestChange` would announce an
-event the element never has cause to fire. */
+`PaginationSize`, which a consumer puts in the `footer` slot and answers
+themselves. Routing this through `requestChange` would announce an event
+the element never has cause to fire. */
   "prop:pageSize"?: (HelixHeadlessDataTable["pageSize"]) | undefined;
   /** How many rows the whole result has, where this element cannot count them.
 
@@ -6147,10 +6147,10 @@ not, rather than shown or hidden by CSS. */
   modal?: (HelixHeadlessDrawer["modal"]) | undefined;
   /** Which edge the drawer comes from.
 
-Unset is `end`, which the styled tier reads as `:host(:not([placement]))`
-beside `:host([placement="end"])` rather than as a value written here: a
+Unset is `end`, and it stays unset rather than being written down: a
 default assigned to the property would reflect onto every host and put a
-`placement="end"` into markup no consumer wrote. */
+`placement="end"` into markup no consumer wrote. So what this tier
+guarantees is the absence, and a sheet selects on it. */
   placement?: (HelixHeadlessDrawer["placement"]) | undefined;
   /** Whether the element is open.
 
@@ -6238,10 +6238,10 @@ not, rather than shown or hidden by CSS. */
   "prop:modal"?: (HelixHeadlessDrawer["modal"]) | undefined;
   /** Which edge the drawer comes from.
 
-Unset is `end`, which the styled tier reads as `:host(:not([placement]))`
-beside `:host([placement="end"])` rather than as a value written here: a
+Unset is `end`, and it stays unset rather than being written down: a
 default assigned to the property would reflect onto every host and put a
-`placement="end"` into markup no consumer wrote. */
+`placement="end"` into markup no consumer wrote. So what this tier
+guarantees is the absence, and a sheet selects on it. */
   "prop:placement"?: (HelixHeadlessDrawer["placement"]) | undefined;
   /** Whether the element is open.
 
@@ -7217,11 +7217,12 @@ renders nothing rather than the epoch, which is what parsing an empty string
 would give.
 
 **The element's own text is read as a fallback, and only in a browser.**
-`<helix-format-date elapsed>2026-08-27T01:00:00Z</helix-format-date>` is the
-spelling that reads best in markup, and it cannot be the only one: measured
-against Lit's server shim, `textContent`, `children`, `firstChild` and
-`querySelector` are all `undefined` there, so a server has no way to see it.
-An element rendered on a server needs the attribute; one rendered in a
+`<helix-headless-format-date
+elapsed>2026-08-27T01:00:00Z</helix-headless-format-date>` is the spelling
+that reads best in markup, and it cannot be the only one: measured against
+Lit's server shim, `textContent`, `children`, `firstChild` and
+`querySelector` are all `undefined` there, so a server has no way to see
+it. An element rendered on a server needs the attribute; one rendered in a
 browser may use either. */
   date?: (HelixHeadlessFormatDate["date"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
@@ -7271,11 +7272,12 @@ renders nothing rather than the epoch, which is what parsing an empty string
 would give.
 
 **The element's own text is read as a fallback, and only in a browser.**
-`<helix-format-date elapsed>2026-08-27T01:00:00Z</helix-format-date>` is the
-spelling that reads best in markup, and it cannot be the only one: measured
-against Lit's server shim, `textContent`, `children`, `firstChild` and
-`querySelector` are all `undefined` there, so a server has no way to see it.
-An element rendered on a server needs the attribute; one rendered in a
+`<helix-headless-format-date
+elapsed>2026-08-27T01:00:00Z</helix-headless-format-date>` is the spelling
+that reads best in markup, and it cannot be the only one: measured against
+Lit's server shim, `textContent`, `children`, `firstChild` and
+`querySelector` are all `undefined` there, so a server has no way to see
+it. An element rendered on a server needs the attribute; one rendered in a
 browser may use either. */
   "prop:date"?: (HelixHeadlessFormatDate["date"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
@@ -7352,12 +7354,12 @@ so a number written here that disagrees with the sheet is a promise the
 consumer has to keep by hand, and the one number a summary is told to trust
 is the one it gets wrong.
 
-The strip measures itself, so `--heatmap-cell-inline-size` and `--heatmap-gap` are
-enough on their own and these two are the estimate used until the first
-measurement lands. Writing the attribute pins the value and stops the
-measurement being consulted, which is what a container query or a transition
-on the cell size wants, where what is drawn this frame is not what the
-arithmetic should plan around.
+The strip measures itself, so sizing the cells in a sheet is enough on its
+own and these two are the estimate used until the first measurement lands.
+Writing the attribute pins the value and stops the measurement being
+consulted, which is what a container query or a transition on the cell size
+wants, where what is drawn this frame is not what the arithmetic should
+plan around.
 
 Zero turns the dropping off altogether, which is right for a strip in a
 container that cannot get narrow. */
@@ -7370,12 +7372,12 @@ so a number written here that disagrees with the sheet is a promise the
 consumer has to keep by hand, and the one number a summary is told to trust
 is the one it gets wrong.
 
-The strip measures itself, so `--heatmap-cell-inline-size` and `--heatmap-gap` are
-enough on their own and these two are the estimate used until the first
-measurement lands. Writing the attribute pins the value and stops the
-measurement being consulted, which is what a container query or a transition
-on the cell size wants, where what is drawn this frame is not what the
-arithmetic should plan around.
+The strip measures itself, so sizing the cells in a sheet is enough on its
+own and these two are the estimate used until the first measurement lands.
+Writing the attribute pins the value and stops the measurement being
+consulted, which is what a container query or a transition on the cell size
+wants, where what is drawn this frame is not what the arithmetic should
+plan around.
 
 Zero turns the dropping off altogether, which is right for a strip in a
 container that cannot get narrow. */
@@ -7447,12 +7449,12 @@ so a number written here that disagrees with the sheet is a promise the
 consumer has to keep by hand, and the one number a summary is told to trust
 is the one it gets wrong.
 
-The strip measures itself, so `--heatmap-cell-inline-size` and `--heatmap-gap` are
-enough on their own and these two are the estimate used until the first
-measurement lands. Writing the attribute pins the value and stops the
-measurement being consulted, which is what a container query or a transition
-on the cell size wants, where what is drawn this frame is not what the
-arithmetic should plan around.
+The strip measures itself, so sizing the cells in a sheet is enough on its
+own and these two are the estimate used until the first measurement lands.
+Writing the attribute pins the value and stops the measurement being
+consulted, which is what a container query or a transition on the cell size
+wants, where what is drawn this frame is not what the arithmetic should
+plan around.
 
 Zero turns the dropping off altogether, which is right for a strip in a
 container that cannot get narrow. */
@@ -7465,12 +7467,12 @@ so a number written here that disagrees with the sheet is a promise the
 consumer has to keep by hand, and the one number a summary is told to trust
 is the one it gets wrong.
 
-The strip measures itself, so `--heatmap-cell-inline-size` and `--heatmap-gap` are
-enough on their own and these two are the estimate used until the first
-measurement lands. Writing the attribute pins the value and stops the
-measurement being consulted, which is what a container query or a transition
-on the cell size wants, where what is drawn this frame is not what the
-arithmetic should plan around.
+The strip measures itself, so sizing the cells in a sheet is enough on its
+own and these two are the estimate used until the first measurement lands.
+Writing the attribute pins the value and stops the measurement being
+consulted, which is what a container query or a transition on the cell size
+wants, where what is drawn this frame is not what the arithmetic should
+plan around.
 
 Zero turns the dropping off altogether, which is right for a strip in a
 container that cannot get narrow. */
@@ -7534,7 +7536,7 @@ the trigger silently does nothing at all. A wrapper has to hand them down,
 the same way `label` becomes `aria-label` in there.
 
 ```html
-<helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+<helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
 ```
 
 `commandFor` spells its attribute out, because Lit lowercases a property
@@ -7695,7 +7697,7 @@ the trigger silently does nothing at all. A wrapper has to hand them down,
 the same way `label` becomes `aria-label` in there.
 
 ```html
-<helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+<helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
 ```
 
 `commandFor` spells its attribute out, because Lit lowercases a property
@@ -7945,10 +7947,10 @@ Read-only to a consumer: it is a report rather than a setting.
 **Mirrored to `data-status`, and not reflected as `status`.** It is element
 state, so reflecting it puts the element's own bookkeeping into the markup
 a consumer rendered: React reads the attribute appearing at upgrade as a
-hydration mismatch, and a serialized `<helix-image status="loaded">` pasted
-back declares that a picture has arrived which this element has never
-fetched. The `data-` name is the library's answer to both, being a name a
-re-parse cannot mistake for a declaration, and it is what `data-closed` on
+hydration mismatch, and a host pasted back carrying `status="loaded"`
+declares that a picture has arrived which this element has never fetched.
+The `data-` name is the library's answer to both, being a name a re-parse
+cannot mistake for a declaration, and it is what `data-closed` on
 `Toast.Item` already does. A picture arrives after somebody fetched it,
 which puts this on the safe side of hydration: a fact that can be true on
 the *first* update mirrors to a custom state instead, which is what
@@ -8021,10 +8023,10 @@ Read-only to a consumer: it is a report rather than a setting.
 **Mirrored to `data-status`, and not reflected as `status`.** It is element
 state, so reflecting it puts the element's own bookkeeping into the markup
 a consumer rendered: React reads the attribute appearing at upgrade as a
-hydration mismatch, and a serialized `<helix-image status="loaded">` pasted
-back declares that a picture has arrived which this element has never
-fetched. The `data-` name is the library's answer to both, being a name a
-re-parse cannot mistake for a declaration, and it is what `data-closed` on
+hydration mismatch, and a host pasted back carrying `status="loaded"`
+declares that a picture has arrived which this element has never fetched.
+The `data-` name is the library's answer to both, being a name a re-parse
+cannot mistake for a declaration, and it is what `data-closed` on
 `Toast.Item` already does. A picture arrives after somebody fetched it,
 which puts this on the safe side of hydration: a fact that can be true on
 the *first* update mirrors to a custom state instead, which is what
@@ -8093,20 +8095,20 @@ Not a label: it goes when typing starts. */
 **The attribute is `readonly`, which is the platform's spelling.** A
 camelCase property needs an explicit `attribute`, and dash-casing a word
 HTML writes as one costs what an attribute always costs here: nothing
-warns. `<helix-input readonly>` is what anybody who has written HTML types;
-against `read-only` it parses to no property at all, and the field stays
-editable with no error anywhere. Measured on the dash-cased form, `readOnly`
-came back `false`. */
+warns. `<helix-headless-input readonly>` is what anybody who has written
+HTML types; against `read-only` it parses to no property at all, and the
+field stays editable with no error anywhere. Measured on the dash-cased
+form, `readOnly` came back `false`. */
   readonly?: (HelixHeadlessInput["readOnly"]) | undefined;
   /** Whether the field refuses input while still submitting its value.
 
 **The attribute is `readonly`, which is the platform's spelling.** A
 camelCase property needs an explicit `attribute`, and dash-casing a word
 HTML writes as one costs what an attribute always costs here: nothing
-warns. `<helix-input readonly>` is what anybody who has written HTML types;
-against `read-only` it parses to no property at all, and the field stays
-editable with no error anywhere. Measured on the dash-cased form, `readOnly`
-came back `false`. */
+warns. `<helix-headless-input readonly>` is what anybody who has written
+HTML types; against `read-only` it parses to no property at all, and the
+field stays editable with no error anywhere. Measured on the dash-cased
+form, `readOnly` came back `false`. */
   readOnly?: (HelixHeadlessInput["readOnly"]) | undefined;
   /** Whether a password field offers a toggle that shows what was typed.
 
@@ -8127,9 +8129,9 @@ The state is `aria-pressed`, not this. */
 
 **Not reflected.** Reflection exists so a selector can reach a value, and
 no stylesheet in this repository selects on `type`. Reflecting it writes
-`type="text"` onto every `<helix-input>` ever rendered, an attribute no
-consumer's markup has, which is the fault the area rules write up under
-`Button`'s `href`, `target` and `rel`.
+`type="text"` onto every `<helix-headless-input>` ever rendered, an
+attribute no consumer's markup has, which is the fault the area rules write
+up under `Button`'s `href`, `target` and `rel`.
 
 Nothing reads it from the attribute either. The real `<input>` inside takes
 it as a property binding, which is what makes the keyboard and the
@@ -8247,20 +8249,20 @@ Not a label: it goes when typing starts. */
 **The attribute is `readonly`, which is the platform's spelling.** A
 camelCase property needs an explicit `attribute`, and dash-casing a word
 HTML writes as one costs what an attribute always costs here: nothing
-warns. `<helix-input readonly>` is what anybody who has written HTML types;
-against `read-only` it parses to no property at all, and the field stays
-editable with no error anywhere. Measured on the dash-cased form, `readOnly`
-came back `false`. */
+warns. `<helix-headless-input readonly>` is what anybody who has written
+HTML types; against `read-only` it parses to no property at all, and the
+field stays editable with no error anywhere. Measured on the dash-cased
+form, `readOnly` came back `false`. */
   "bool:readonly"?: (HelixHeadlessInput["readOnly"]) | undefined;
   /** Whether the field refuses input while still submitting its value.
 
 **The attribute is `readonly`, which is the platform's spelling.** A
 camelCase property needs an explicit `attribute`, and dash-casing a word
 HTML writes as one costs what an attribute always costs here: nothing
-warns. `<helix-input readonly>` is what anybody who has written HTML types;
-against `read-only` it parses to no property at all, and the field stays
-editable with no error anywhere. Measured on the dash-cased form, `readOnly`
-came back `false`. */
+warns. `<helix-headless-input readonly>` is what anybody who has written
+HTML types; against `read-only` it parses to no property at all, and the
+field stays editable with no error anywhere. Measured on the dash-cased
+form, `readOnly` came back `false`. */
   "prop:readOnly"?: (HelixHeadlessInput["readOnly"]) | undefined;
   /** Whether a password field offers a toggle that shows what was typed.
 
@@ -8281,9 +8283,9 @@ The state is `aria-pressed`, not this. */
 
 **Not reflected.** Reflection exists so a selector can reach a value, and
 no stylesheet in this repository selects on `type`. Reflecting it writes
-`type="text"` onto every `<helix-input>` ever rendered, an attribute no
-consumer's markup has, which is the fault the area rules write up under
-`Button`'s `href`, `target` and `rel`.
+`type="text"` onto every `<helix-headless-input>` ever rendered, an
+attribute no consumer's markup has, which is the fault the area rules write
+up under `Button`'s `href`, `target` and `rel`.
 
 Nothing reads it from the attribute either. The real `<input>` inside takes
 it as a property binding, which is what makes the keyboard and the
@@ -8556,8 +8558,7 @@ beside it for instance. `ring` lets the ground through, for a chart drawn
 over something busy. `triangle` points along the axis and reads as "and
 onward" rather than as a second claim about the data.
 
-The shapes come from
-`helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so
+The shapes come from one shared sheet, the same one `Sparkline` takes, so
 the set is identical wherever one appears. **Which is why every value is
 named here.** `Sparkline` shipped `square` implemented, drawn, asserted and
 undocumented until the cohort before this one; this family reads the same
@@ -8667,8 +8668,7 @@ beside it for instance. `ring` lets the ground through, for a chart drawn
 over something busy. `triangle` points along the axis and reads as "and
 onward" rather than as a second claim about the data.
 
-The shapes come from
-`helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so
+The shapes come from one shared sheet, the same one `Sparkline` takes, so
 the set is identical wherever one appears. **Which is why every value is
 named here.** `Sparkline` shipped `square` implemented, drawn, asserted and
 undocumented until the cohort before this one; this family reads the same
@@ -8769,10 +8769,10 @@ has to survive with the stylesheet turned off.
   label?: (HelixHeadlessList["label"]) | undefined;
   /** Which markers an ordered list draws, in `<ol type>`'s own five values.
 
-Reflected, because this is one of the things a stylesheet selects on and
-the styled tier maps each to a `list-style-type`. The platform's spellings
-rather than the CSS ones, so `<helix-list kind="ordered" type="i">` is what
-a consumer would have written on an `<ol>`.
+Reflected, because this is one of the things a stylesheet selects on, each
+value mapping to a `list-style-type`. The platform's spellings rather than
+the CSS ones, so `<helix-headless-list kind="ordered" type="i">` is what a
+consumer would have written on an `<ol>`.
 
 **`start` and `reversed` are both absent and neither can be done here.**
 This renders no `<ol>`: the rows are slotted and numbered by the CSS
@@ -8811,10 +8811,10 @@ has to survive with the stylesheet turned off.
   "prop:label"?: (HelixHeadlessList["label"]) | undefined;
   /** Which markers an ordered list draws, in `<ol type>`'s own five values.
 
-Reflected, because this is one of the things a stylesheet selects on and
-the styled tier maps each to a `list-style-type`. The platform's spellings
-rather than the CSS ones, so `<helix-list kind="ordered" type="i">` is what
-a consumer would have written on an `<ol>`.
+Reflected, because this is one of the things a stylesheet selects on, each
+value mapping to a `list-style-type`. The platform's spellings rather than
+the CSS ones, so `<helix-headless-list kind="ordered" type="i">` is what a
+consumer would have written on an `<ol>`.
 
 **`start` and `reversed` are both absent and neither can be done here.**
 This renders no `<ol>`: the rows are slotted and numbered by the CSS
@@ -9995,10 +9995,10 @@ this element then owns.
 
 **Not reflected.** Unread is a visual state, which is why the four mixins
 mirror theirs, but the mirror may not be the property's own attribute:
-`<helix-notification default-read>` comes back from a server without `read`
-and would gain it on the first update, which React reports as a hydration
-mismatch, and which a copy of the serialized element re-parses as a
-declaration. `:state(read)` is what the stylesheet reads.
+`<helix-headless-notification default-read>` comes back from a server
+without `read` and would gain it on the first update, which React reports
+as a hydration mismatch, and which a copy of the serialized element
+re-parses as a declaration. `:state(read)` is what the stylesheet reads.
 `hydration.dom.spec.ts` holds it. */
   read?: (HelixHeadlessNotification["read"]) | undefined;
   /** State to open with, where nothing declared one. */
@@ -10050,10 +10050,10 @@ this element then owns.
 
 **Not reflected.** Unread is a visual state, which is why the four mixins
 mirror theirs, but the mirror may not be the property's own attribute:
-`<helix-notification default-read>` comes back from a server without `read`
-and would gain it on the first update, which React reports as a hydration
-mismatch, and which a copy of the serialized element re-parses as a
-declaration. `:state(read)` is what the stylesheet reads.
+`<helix-headless-notification default-read>` comes back from a server
+without `read` and would gain it on the first update, which React reports
+as a hydration mismatch, and which a copy of the serialized element
+re-parses as a declaration. `:state(read)` is what the stylesheet reads.
 `hydration.dom.spec.ts` holds it. */
   "prop:read"?: (HelixHeadlessNotification["read"]) | undefined;
   /** State to open with, where nothing declared one. */
@@ -10677,7 +10677,7 @@ attribute and the state is the property.
 **The attribute, read when it is asked for, and never a snapshot taken in
 the constructor.** A field initializer runs there, and an element the HTML
 parser created has none of its attributes yet at that moment: measured on
-this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+this element, on `Radio` and on `Toggle`, `<helix-headless-option value="a"
 selected>` reported `defaultSelected` as `false` both from parsed markup
 and from `createElement` followed by `setAttribute`, which is every way a
 consumer writes one. The snapshot could only ever be true for an element
@@ -10784,7 +10784,7 @@ attribute and the state is the property.
 **The attribute, read when it is asked for, and never a snapshot taken in
 the constructor.** A field initializer runs there, and an element the HTML
 parser created has none of its attributes yet at that moment: measured on
-this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+this element, on `Radio` and on `Toggle`, `<helix-headless-option value="a"
 selected>` reported `defaultSelected` as `false` both from parsed markup
 and from `createElement` followed by `setAttribute`, which is every way a
 consumer writes one. The snapshot could only ever be true for an element
@@ -11387,10 +11387,10 @@ other end is going to reject. A consumer whose codes really do carry
 marked letters wants `text`, which judges nothing.
 
 **Not reflected**: nothing selects on it, so reflecting only writes
-`type="numeric"` onto every `<helix-pin-input>` ever rendered, an attribute
-no consumer's markup had. The area rules carry the sentence "reflect only
-what CSS selects on". The real inputs take it as a binding, which is what
-makes the keyboard follow. */
+`type="numeric"` onto every `<helix-headless-pin-input>` ever rendered, an
+attribute no consumer's markup had. The area rules carry the sentence
+"reflect only what CSS selects on". The real inputs take it as a binding,
+which is what makes the keyboard follow. */
   type?: (HelixHeadlessPinInput["type"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
   "default-value"?: (HelixHeadlessPinInput["defaultValue"]) | undefined;
@@ -11498,10 +11498,10 @@ other end is going to reject. A consumer whose codes really do carry
 marked letters wants `text`, which judges nothing.
 
 **Not reflected**: nothing selects on it, so reflecting only writes
-`type="numeric"` onto every `<helix-pin-input>` ever rendered, an attribute
-no consumer's markup had. The area rules carry the sentence "reflect only
-what CSS selects on". The real inputs take it as a binding, which is what
-makes the keyboard follow. */
+`type="numeric"` onto every `<helix-headless-pin-input>` ever rendered, an
+attribute no consumer's markup had. The area rules carry the sentence
+"reflect only what CSS selects on". The real inputs take it as a binding,
+which is what makes the keyboard follow. */
   "prop:type"?: (HelixHeadlessPinInput["type"]) | undefined;
   /** The value the markup declared, which is where a reset returns to. */
   "attr:default-value"?: (HelixHeadlessPinInput["defaultValue"]) | undefined;
@@ -12080,7 +12080,7 @@ attribute and the state is the property.
 **The attribute, read when it is asked for, and never a snapshot taken in
 the constructor.** A field initializer runs there, and an element the HTML
 parser created has none of its attributes yet at that moment: measured on
-this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+this element, on `Option` and on `Toggle`, `<helix-headless-radio value="a"
 selected>` reported `defaultSelected` as `false` both from parsed markup
 and from `createElement` followed by `setAttribute`, which is every way a
 consumer writes one. The snapshot could only ever be true for an element
@@ -12137,7 +12137,7 @@ attribute and the state is the property.
 **The attribute, read when it is asked for, and never a snapshot taken in
 the constructor.** A field initializer runs there, and an element the HTML
 parser created has none of its attributes yet at that moment: measured on
-this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+this element, on `Option` and on `Toggle`, `<helix-headless-radio value="a"
 selected>` reported `defaultSelected` as `false` both from parsed markup
 and from `createElement` followed by `setAttribute`, which is every way a
 consumer writes one. The snapshot could only ever be true for an element
@@ -13661,9 +13661,9 @@ the headline and the label is a caption under it.
 The row directions set them side by side, for a figure in a line of text or
 a narrow strip where a stacked pair would be two lines of almost nothing.
 
-A property rather than a `helix-flex` around it, because the unit has to
-stay on the value's baseline whichever way the pair goes, and only this
-element knows which of its children the unit belongs to.
+A property rather than a `Flex` around it, because the unit has to stay on
+the value's baseline whichever way the pair goes, and only this element
+knows which of its children the unit belongs to.
 
 **Optional rather than defaulted to `column`, which is not a style
 preference.** A reflecting property with a default writes its attribute onto
@@ -13686,9 +13686,9 @@ the headline and the label is a caption under it.
 The row directions set them side by side, for a figure in a line of text or
 a narrow strip where a stacked pair would be two lines of almost nothing.
 
-A property rather than a `helix-flex` around it, because the unit has to
-stay on the value's baseline whichever way the pair goes, and only this
-element knows which of its children the unit belongs to.
+A property rather than a `Flex` around it, because the unit has to stay on
+the value's baseline whichever way the pair goes, and only this element
+knows which of its children the unit belongs to.
 
 **Optional rather than defaulted to `column`, which is not a style
 preference.** A reflecting property with a default writes its attribute onto
@@ -14043,15 +14043,15 @@ export type HelixHeadlessTableColumnHelixBeforeResizeElementEvent =
 export type HelixHeadlessTableColumnProps = {
   /** Which edge the values line up against.
 
-`end` is what a column of numbers wants, so digits of the same magnitude sit
-above each other. Left unset the cell inherits the table's own alignment,
-which is `start` for text in either writing direction. `helix-data-table`
-aligns the cells it draws. A `helix-table`'s cells are markup the consumer
-wrote, so the table writes nothing onto them: it publishes the edge to each
-cell under this column as `--table-cell-align`, which `@fusion.dev/helix`
-reads. The heading is this element's own, and `@fusion.dev/helix` sets it to
-the same edge in either table. `end` is the inline end, so in a
-right-to-left table it is the left.
+`end` is what a column of numbers wants, so digits of the same magnitude
+sit above each other. Left unset the cell inherits the table's own
+alignment, which is `start` for text in either writing direction.
+`DataTable` aligns the cells it draws. A `Table`'s cells are markup the
+consumer wrote, so the table writes nothing onto them: it publishes the
+edge to each cell under this column as `--table-cell-align`, which
+`@fusion.dev/helix` reads. The heading is this element's own, and
+`@fusion.dev/helix` sets it to the same edge in either table. `end` is the
+inline end, so in a right-to-left table it is the left.
 
 **Reflected, because the heading is drawn by a stylesheet and has no other
 way to learn it.** Set as a property, which is how React sets it, an
@@ -14098,8 +14098,8 @@ onto its host. */
   /** The track this column takes, as CSS.
 
 A single track value, so anything valid in `grid-template-columns` works:
-`16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track
-in its place in a `helix-table`'s `columns`, where that table sets one, and
+`16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track in
+its place in a `Table`'s `columns`, where that table sets one, and
 otherwise shares what is left over equally, as `minmax(max-content, 1fr)`.
 Set here, it wins over that list, which is what lets a reader resize a
 column in a table that set one.
@@ -14145,15 +14145,15 @@ correct default: the raw value is what an API sorted by. */
 export type HelixHeadlessTableColumnSolidJsProps = {
   /** Which edge the values line up against.
 
-`end` is what a column of numbers wants, so digits of the same magnitude sit
-above each other. Left unset the cell inherits the table's own alignment,
-which is `start` for text in either writing direction. `helix-data-table`
-aligns the cells it draws. A `helix-table`'s cells are markup the consumer
-wrote, so the table writes nothing onto them: it publishes the edge to each
-cell under this column as `--table-cell-align`, which `@fusion.dev/helix`
-reads. The heading is this element's own, and `@fusion.dev/helix` sets it to
-the same edge in either table. `end` is the inline end, so in a
-right-to-left table it is the left.
+`end` is what a column of numbers wants, so digits of the same magnitude
+sit above each other. Left unset the cell inherits the table's own
+alignment, which is `start` for text in either writing direction.
+`DataTable` aligns the cells it draws. A `Table`'s cells are markup the
+consumer wrote, so the table writes nothing onto them: it publishes the
+edge to each cell under this column as `--table-cell-align`, which
+`@fusion.dev/helix` reads. The heading is this element's own, and
+`@fusion.dev/helix` sets it to the same edge in either table. `end` is the
+inline end, so in a right-to-left table it is the left.
 
 **Reflected, because the heading is drawn by a stylesheet and has no other
 way to learn it.** Set as a property, which is how React sets it, an
@@ -14200,8 +14200,8 @@ onto its host. */
   /** The track this column takes, as CSS.
 
 A single track value, so anything valid in `grid-template-columns` works:
-`16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track
-in its place in a `helix-table`'s `columns`, where that table sets one, and
+`16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track in
+its place in a `Table`'s `columns`, where that table sets one, and
 otherwise shares what is left over equally, as `minmax(max-content, 1fr)`.
 Set here, it wins over that list, which is what lets a reader resize a
 column in a table that set one.
@@ -14251,15 +14251,14 @@ correct default: the raw value is what an API sorted by. */
 export type HelixHeadlessTableProps = {
   /** The column widths as one track list, written once on the table.
 
-With `helix-table-column` children, each track sizes the column in its
-place, a hidden column counted, so hiding one takes its track with it and
-the rest keep theirs. The columns decide how many tracks there are and this
-list only how wide: a track past the last column is dropped, and a column
-past the last track shares what is left. With no columns declared it is
-the whole track list. Tracks count as the grid counts them, so
-`minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid
-would refuse leaves its column at the default rather than taking the table
-down to one column.
+With `TableColumn` children, each track sizes the column in its place, a
+hidden column counted, so hiding one takes its track with it and the rest
+keep theirs. The columns decide how many tracks there are and this list
+only how wide: a track past the last column is dropped, and a column past
+the last track shares what is left. With no columns declared it is the
+whole track list. Tracks count as the grid counts them, so `minmax(0, 1fr)`
+is one and `repeat(2, 8rem)` is two, and one the grid would refuse leaves
+its column at the default rather than taking the table down to one column.
 
 **A column's own `width` wins over its track here.** The width is written
 on the column it sizes, which is the more particular statement, and it is
@@ -14273,13 +14272,11 @@ to walk, so a render there knows of no columns and this attribute is the
 whole answer: a table given one lays its grid out in the first paint, and a
 table sized only by its columns is one track wide until it upgrades.
 
-**`helix-data-table` has none of this, and should not.** Its columns are
-its schema rather than an option, so there is always a column to write a
-`width` on and a list here would be a second way to say what that says.
-This table's cells are markup, and a table written as rows of cells with no
-`helix-table-column` in it has nowhere else to be sized from. Both families
-take the same CSS hook, `--table-columns` and `--data-table-columns`, which
-wins over whichever list the element worked out. */
+**Data Table has none of this, and should not.** Its columns are its schema
+rather than an option, so there is always a column to write a `width` on
+and a list here would be a second way to say what that says. This table's
+cells are markup, and a table written as rows of cells with no column
+declared in it has nowhere else to be sized from. */
   columns?: (HelixHeadlessTable["columns"]) | undefined;
   /** Accessible name for the table. */
   label?: (HelixHeadlessTable["label"]) | undefined;
@@ -14302,15 +14299,14 @@ say that without the component knowing what a row looks like. */
 export type HelixHeadlessTableSolidJsProps = {
   /** The column widths as one track list, written once on the table.
 
-With `helix-table-column` children, each track sizes the column in its
-place, a hidden column counted, so hiding one takes its track with it and
-the rest keep theirs. The columns decide how many tracks there are and this
-list only how wide: a track past the last column is dropped, and a column
-past the last track shares what is left. With no columns declared it is
-the whole track list. Tracks count as the grid counts them, so
-`minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid
-would refuse leaves its column at the default rather than taking the table
-down to one column.
+With `TableColumn` children, each track sizes the column in its place, a
+hidden column counted, so hiding one takes its track with it and the rest
+keep theirs. The columns decide how many tracks there are and this list
+only how wide: a track past the last column is dropped, and a column past
+the last track shares what is left. With no columns declared it is the
+whole track list. Tracks count as the grid counts them, so `minmax(0, 1fr)`
+is one and `repeat(2, 8rem)` is two, and one the grid would refuse leaves
+its column at the default rather than taking the table down to one column.
 
 **A column's own `width` wins over its track here.** The width is written
 on the column it sizes, which is the more particular statement, and it is
@@ -14324,13 +14320,11 @@ to walk, so a render there knows of no columns and this attribute is the
 whole answer: a table given one lays its grid out in the first paint, and a
 table sized only by its columns is one track wide until it upgrades.
 
-**`helix-data-table` has none of this, and should not.** Its columns are
-its schema rather than an option, so there is always a column to write a
-`width` on and a list here would be a second way to say what that says.
-This table's cells are markup, and a table written as rows of cells with no
-`helix-table-column` in it has nowhere else to be sized from. Both families
-take the same CSS hook, `--table-columns` and `--data-table-columns`, which
-wins over whichever list the element worked out. */
+**Data Table has none of this, and should not.** Its columns are its schema
+rather than an option, so there is always a column to write a `width` on
+and a list here would be a second way to say what that says. This table's
+cells are markup, and a table written as rows of cells with no column
+declared in it has nowhere else to be sized from. */
   "prop:columns"?: (HelixHeadlessTable["columns"]) | undefined;
   /** Accessible name for the table. */
   "prop:label"?: (HelixHeadlessTable["label"]) | undefined;
@@ -14956,8 +14950,8 @@ Absent uses the runtime's own. */
 
 Absent is one. `range` holds a start and an end, `multiple` holds any
 number, and both are carried as one comma-separated value, which is what a
-form submits. `helix-time-picker` carries the longer note on the interaction and on
-why a wheel cannot do either. */
+form submits. `TimePicker` carries the longer note on the interaction and
+on why a wheel cannot do either. */
   mode?: (HelixHeadlessTimeInput["mode"]) | undefined;
   /** What the field says before a time is in it. */
   placeholder?: (HelixHeadlessTimeInput["placeholder"]) | undefined;
@@ -14986,7 +14980,7 @@ never something this element would refuse to read back. */
 `list` offers whole times, which is what a product with slots or opening
 hours has. `wheels` splits them into an hour, a minute and a meridiem where
 the locale uses one, which is the only way to reach `23:45` without
-scrolling most of a day. `helix-time-picker` carries the longer note on the trade.
+scrolling most of a day. `TimePicker` carries the longer note on the trade.
 
 **Optional rather than defaulted, which is not a style preference.** A
 reflecting property with a default writes its attribute onto every host the
@@ -15144,8 +15138,8 @@ Absent uses the runtime's own. */
 
 Absent is one. `range` holds a start and an end, `multiple` holds any
 number, and both are carried as one comma-separated value, which is what a
-form submits. `helix-time-picker` carries the longer note on the interaction and on
-why a wheel cannot do either. */
+form submits. `TimePicker` carries the longer note on the interaction and
+on why a wheel cannot do either. */
   "prop:mode"?: (HelixHeadlessTimeInput["mode"]) | undefined;
   /** What the field says before a time is in it. */
   "prop:placeholder"?: (HelixHeadlessTimeInput["placeholder"]) | undefined;
@@ -15174,7 +15168,7 @@ never something this element would refuse to read back. */
 `list` offers whole times, which is what a product with slots or opening
 hours has. `wheels` splits them into an hour, a minute and a meridiem where
 the locale uses one, which is the only way to reach `23:45` without
-scrolling most of a day. `helix-time-picker` carries the longer note on the trade.
+scrolling most of a day. `TimePicker` carries the longer note on the trade.
 
 **Optional rather than defaulted, which is not a style preference.** A
 reflecting property with a default writes its attribute onto every host the
@@ -15372,7 +15366,7 @@ Absent uses the runtime's own. */
 
 Absent is one. `range` holds a start and an end with everything between
 them shown as part of the answer, `multiple` holds any number, and both are
-carried as one comma-separated value: the same shape `helix-date-picker` uses,
+carried as one comma-separated value: the same shape `DatePicker` uses,
 because it is the same question asked of a different unit.
 
 **A range is two picks, and a third starts over.** That is the calendar's
@@ -15546,7 +15540,7 @@ Absent uses the runtime's own. */
 
 Absent is one. `range` holds a start and an end with everything between
 them shown as part of the answer, `multiple` holds any number, and both are
-carried as one comma-separated value: the same shape `helix-date-picker` uses,
+carried as one comma-separated value: the same shape `DatePicker` uses,
 because it is the same question asked of a different unit.
 
 **A range is two picks, and a third starts over.** That is the calendar's
@@ -15845,7 +15839,7 @@ where they were would not be a stack.
 **Optional, and bottom-end is the absence of it.** Reflecting *and*
 defaulting is the pair that writes onto a host: every toast region anybody
 rendered would gain a `placement="bottom-end"` nobody typed, which a React
-consumer's server markup does not have. The styled sheet carries the resting
+consumer's server markup does not have. A sheet carries the resting
 arrangement in its own `:host` rule and the selectors describe only the
 departures, which is what `orientation` does. */
   placement?: (HelixHeadlessToast["placement"]) | undefined;
@@ -15866,7 +15860,7 @@ where they were would not be a stack.
 **Optional, and bottom-end is the absence of it.** Reflecting *and*
 defaulting is the pair that writes onto a host: every toast region anybody
 rendered would gain a `placement="bottom-end"` nobody typed, which a React
-consumer's server markup does not have. The styled sheet carries the resting
+consumer's server markup does not have. A sheet carries the resting
 arrangement in its own `:host` rule and the selectors describe only the
 departures, which is what `orientation` does. */
   "prop:placement"?: (HelixHeadlessToast["placement"]) | undefined;
@@ -16107,11 +16101,11 @@ attribute and the state is the property.
 **The attribute, read when it is asked for, and never a snapshot taken in
 the constructor.** A field initializer runs there, and an element the HTML
 parser created has none of its attributes yet at that moment: measured on
-this element, on `Option` and on `Radio`, `<helix-toggle value="light"
-selected>` reported `defaultSelected` as `false` both from parsed markup
-and from `createElement` followed by `setAttribute`, which is every way a
-consumer writes one. The snapshot could only ever be true for an element
-already in the document when `customElements.define` ran.
+this element, on `Option` and on `Radio`, `<helix-headless-toggle
+value="light" selected>` reported `defaultSelected` as `false` both from
+parsed markup and from `createElement` followed by `setAttribute`, which is
+every way a consumer writes one. The snapshot could only ever be true for
+an element already in the document when `customElements.define` ran.
 
 Nothing overwrites it either, which is what makes reading it late correct
 rather than merely later: `selected` does not reflect, for the reason
@@ -16157,11 +16151,11 @@ attribute and the state is the property.
 **The attribute, read when it is asked for, and never a snapshot taken in
 the constructor.** A field initializer runs there, and an element the HTML
 parser created has none of its attributes yet at that moment: measured on
-this element, on `Option` and on `Radio`, `<helix-toggle value="light"
-selected>` reported `defaultSelected` as `false` both from parsed markup
-and from `createElement` followed by `setAttribute`, which is every way a
-consumer writes one. The snapshot could only ever be true for an element
-already in the document when `customElements.define` ran.
+this element, on `Option` and on `Radio`, `<helix-headless-toggle
+value="light" selected>` reported `defaultSelected` as `false` both from
+parsed markup and from `createElement` followed by `setAttribute`, which is
+every way a consumer writes one. The snapshot could only ever be true for
+an element already in the document when `customElements.define` ran.
 
 Nothing overwrites it either, which is what makes reading it late correct
 rather than merely later: `selected` does not reflect, for the reason
@@ -17962,7 +17956,7 @@ export type CustomElements = {
    * item added a second after render coordinates on its first click.
    *
    * Items are matched with `instanceof HelixHeadlessAccordionItem`, never by tag
-   * name. Matching `helix-accordion-item` would tie this tier to the styled one.
+   * name, so this tier does not learn about the styled one.
    *
    * The keyboard listener is the controller's and is attached on connect, so
    * none of it runs on the server, where there is no tree to walk and no events
@@ -18450,13 +18444,13 @@ export type CustomElements = {
    * Unset shows all of them, which is what no limit means and is more useful
    * than refusing to render.
    *
-   * **Reflected, because the fold is a stylesheet rule and nothing else.** The
-   * styled tier hides past the limit with `:host([max="N"]) ::slotted(:nth-child(n + N+1))`,
-   * so the attribute *is* the mechanism: a `max` that reaches this property and
-   * never reaches the host matches no rule, and every avatar is drawn beside a
-   * count claiming some are hidden. Markup is the safe path and hides the fault;
-   * a script is the broken one, and React takes it for everyone, assigning a
-   * matching property rather than an attribute.
+   * **Reflected, because the fold is a stylesheet rule and nothing else.** A
+   * sheet hides past the limit one selector per value, as `FOLDS_UP_TO`
+   * describes, so the attribute *is* the mechanism: a `max` that reaches this
+   * property and never reaches the host matches no rule, and every avatar is
+   * drawn beside a count claiming some are hidden. Markup is the safe path and
+   * hides the fault; a script is the broken one, and React takes it for
+   * everyone, assigning a matching property rather than an attribute.
    *
    * **Optional rather than defaulted, per the rule that a reflected property
    * takes no default**: `max = 0` would stamp `max="0"` onto every host that
@@ -18869,7 +18863,7 @@ export type CustomElements = {
    * CSS variables available for styling the component.
    *
    * - `--bar-chart-axis`: How wide an axis column is drawn, in `ch`, from the widest number on it. Written on the axis itself, and only where the categories run along the bottom: turned sideways an axis is a row and takes a line's height instead. (default: `undefined`)
-   * - `--bar-chart-secondary`: The color of the secondary axis when one series owns it. It resolves a `--helix-color-series-*` token, so on the headless tier alone it names something that is not there. #138. (default: `undefined`)
+   * - `--bar-chart-secondary`: The color of the secondary axis, where one series owns it. Written by the component from that series' `--chart-series-*`, so it promises the series color and nothing more: whatever that hook resolves to is what the axis is drawn in. (default: `undefined`)
    * - `--chart-bar-wash`: The gradient a bar would take, named per bar so the styled tier can point `fill` at it. Drawn whatever the treatment and used only where `wash="gradient"` asks for it. (default: `undefined`)
    *
    * ## CSS Parts
@@ -19012,12 +19006,12 @@ export type CustomElements = {
    * - `current`: Whether this item is the page the reader is on.
    * - `href`: Where the crumb goes, and nothing where it is the current page.
    *
-   * **Optional and reflected, because a stylesheet does select on it.**
-   * `breadcrumb.css` writes `:host(:not([href])) [part="link"]` to take the
-   * block padding off a crumb that is not a link, so the attribute is what
-   * decides how tall a crumb is. Unreflected, an `href` set from script reached
-   * the property, rendered the anchor, and left the host looking unlinked: the
-   * crumb drew at 20px where a markup twin drew at 28.
+   * **Optional and reflected, because a stylesheet does select on it.** A sheet
+   * writes `:host(:not([href])) [part="link"]` to take the block padding off a
+   * crumb that is not a link, so the attribute is what decides how tall a crumb
+   * is. Unreflected, an `href` set from script reached the property, rendered
+   * the anchor, and left the host looking unlinked: the crumb drew at 20px
+   * where a markup twin drew at 28.
    *
    * Optional rather than defaulted, which is the general rule that a reflected
    * property takes no default: an `href` written onto every host would be a link
@@ -19254,7 +19248,7 @@ export type CustomElements = {
    * the same way `label` becomes `aria-label` in there.
    *
    * ```html
-   * <helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+   * <helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
    * ```
    *
    * `commandFor` spells its attribute out, because Lit lowercases a property
@@ -19530,7 +19524,7 @@ export type CustomElements = {
    *
    * The host is the surface. A wrapper `<div part="container">` would be a second
    * box doing nothing the host cannot: the element itself takes the border, the
-   * radius, and the grid, and a consumer styles `helix-card` rather than reaching
+   * radius, and the grid, and a consumer styles `Card` rather than reaching
    * through `::part`. One node instead of two, on every card on the page.
    *
    * Name the card with `aria-label` or `aria-labelledby`. That is the only
@@ -19679,13 +19673,13 @@ export type CustomElements = {
    * **The number is published to the styles rather than enumerated by them**,
    * as `--carousel-per-view` on the track, which is what keeps a width and a
    * count from disagreeing. A sheet can only name a value it wrote a rule for,
-   * so the styled tier enumerated `per-view="2"` through `5` and called five a
-   * judgment; above it the pane fell back to one across while this file went on
-   * counting positions. Measured in Chromium over eight slides, six across gave
-   * three dots, a pane taking the whole track and five slides reachable only by
-   * dragging. Written from here there is no ceiling to exceed, and a consumer's
-   * own sheet reads the same declaration the styled one does. `runEnd` publishes
-   * its correction the same way and for the same reason.
+   * so a sheet enumerating `per-view="2"` through `5` is a ceiling of five, and
+   * above it the pane falls back to one across while this file goes on counting
+   * positions. Measured in Chromium over eight slides against such a sheet, six
+   * across gave three dots, a pane taking the whole track and five slides
+   * reachable only by dragging. Published from here there is no ceiling to
+   * exceed, and every sheet reads the same declaration. `runEnd` publishes its
+   * correction the same way and for the same reason.
    *
    * **On the track and not on the host.** A custom property on the host is a
    * reflected attribute by another name: it would arrive on upgrade, and a
@@ -19710,8 +19704,8 @@ export type CustomElements = {
    * `auto` track is handed nothing. A count stays for the design that calls for
    * exactly three.
    *
-   * The styled sheet says how it divides, and the headless `auto` example
-   * carries the same three lines for a consumer writing their own.
+   * A sheet says how it divides, and the `auto` example here carries the same
+   * three lines for a consumer writing their own.
    *
    * **A value rather than the resting behavior**, which is what the
    * responsiveness policy asks of every axis that a box decides: a splitter
@@ -20085,13 +20079,13 @@ export type CustomElements = {
    *
    * **Not reflected, and the default is why.** A reflected property that
    * defaults to true writes its attribute on upgrade whether or not the
-   * consumer wrote one, so the server serves `<helix-chat label="x">` and the
-   * client turns it into `<helix-chat label="x" pinned>`: a hydration mismatch a
-   * React consumer reports and does not patch up. Nothing needs the attribute
-   * either, because the one thing that changes with the pin is the way back, and
-   * that is a part inside the shadow tree where a stylesheet can already reach
-   * it. Measured rather than assumed: `label, pinned` after upgrade against
-   * `label` from the server.
+   * consumer wrote one, so the server serves `<helix-headless-chat label="x">`
+   * and the client turns it into `<helix-headless-chat label="x" pinned>`: a
+   * hydration mismatch a React consumer reports and does not patch up. Nothing
+   * needs the attribute either, because the one thing that changes with the pin
+   * is the way back, and that is a part inside the shadow tree where a
+   * stylesheet can already reach it. Measured rather than assumed: `label,
+   * pinned` after upgrade against `label` from the server.
    * - `threshold`: How near the bottom still counts as being at it, in pixels.
    *
    * A hook rather than a constant, because the right number depends on how tall
@@ -20148,7 +20142,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The turns, as `helix-chat-message` children.
+   * - `(default)`: The turns.
    * - `actions`: Beside the header: what can be done to the conversation itself.
    * - `composer`: Below the transcript, where the reader writes.
    * - `header`: Above the transcript: what this conversation is.
@@ -20611,11 +20605,11 @@ export type CustomElements = {
    * round. The platform already writes booleans like this for the same reason,
    * `novalidate` and `nomodule` and `noreferrer` among them.
    *
-   * **Reflected, because the gutter is a stylesheet rule.** `code-block.css`
-   * reserves the copy button's width with `:host(:not([no-copy]))`, so the
-   * attribute is what decides whether the block pays for a control. Unreflected,
-   * setting it from script takes the button away (`render` reads the property)
-   * and leaves the 40px it stood in reserved.
+   * **Reflected, because the gutter is a stylesheet rule.** A sheet reserves
+   * the copy button's width with `:host(:not([no-copy]))`, so the attribute is
+   * what decides whether the block pays for a control. Unreflected, setting it
+   * from script takes the button away (`render` reads the property) and leaves
+   * the 40px it stood in reserved.
    *
    * A false boolean reflects as the attribute's absence, so this costs no
    * `no-copy=""` on hosts that never asked for one, and the rule about a
@@ -20759,11 +20753,11 @@ export type CustomElements = {
   >;
 
   /**
-   * **The picker is `helix-color-picker`, not a second one written here.** It owns the
+   * **The picker is `ColorPicker`, not a second one written here.** It owns the
    * square, the ramps, the eyedropper and the syntax toggle, and it is worth
    * having on its own: a settings pane wants a picker flat on the page with
    * nothing to open. This element is the field, the overlay, and the form.
-   * Exactly the arrangement Date Input has with `helix-date-picker`.
+   * Exactly the arrangement Date Input has with `DatePicker`.
    *
    * **Typed as well as picked, and the typing is the reason this is not
    * `<input type="color">`.** The native control gives a free picker and takes
@@ -21123,10 +21117,10 @@ export type CustomElements = {
    *
    * **A color is exactly as requirable as a date**, which is the comparison
    * that settles it: this element extends `HelixFormElement`, carries `name`
-   * and reports its value, so a consumer writing
-   * `<helix-color-picker name="brand" required>` inside a form has every reason
-   * to expect the form to refuse an empty one. Its two siblings in the same
-   * composition position, Date Picker and Time Picker, both check it.
+   * and reports its value, so a consumer writing `<helix-headless-color-picker
+   * name="brand" required>` inside a form has every reason to expect the form
+   * to refuse an empty one. Its two siblings in the same composition position,
+   * Date Picker and Time Picker, both check it.
    *
    * Written out rather than taken from `MixinField`, for the reason those two
    * record: the mixin brings a label, a hint and a feedback region, and this is
@@ -21317,10 +21311,10 @@ export type CustomElements = {
   >;
 
   /**
-   * **The list is `helix-listbox`, and the filtering is its own.** It owns
-   * narrowing, the empty state, the highlight, `aria-activedescendant` and
-   * scrolling an option into view. What is left for this element is the field,
-   * the panel and the traffic between them.
+   * **The list is `Listbox`, and the filtering is its own.** It owns narrowing,
+   * the empty state, the highlight, `aria-activedescendant` and scrolling an
+   * option into view. What is left for this element is the field, the panel and
+   * the traffic between them.
    *
    * **The text and the value are two things.** What a reader types is a filter:
    * it narrows the list and is thrown away. The value is whichever option they
@@ -21491,7 +21485,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The options, which are `helix-option` elements.
+   * - `(default)`: The options.
    * - `end`: After it, for a unit or a clear button.
    * - `indicator`: Replaces the caret saying the field opens.
    * - `start`: Before the text, for an icon.
@@ -21602,12 +21596,11 @@ export type CustomElements = {
   >;
 
   /**
-   * **The list is `helix-listbox`, filtering and all.** Listbox already owns
-   * narrowing, the empty state, the highlight over what matched,
-   * `aria-activedescendant`, scrolling an option into view and the keyboard that
-   * moves between them. Its own note says a command palette is that list again
-   * with something different opening it, and this is that something: a dialog,
-   * and a key that summons it.
+   * **The list is `Listbox`, filtering and all.** Listbox already owns narrowing,
+   * the empty state, the highlight over what matched, `aria-activedescendant`,
+   * scrolling an option into view and the keyboard that moves between them. Its
+   * own note says a command palette is that list again with something different
+   * opening it, and this is that something: a dialog, and a key that summons it.
    *
    * **The value is not kept.** A palette runs a command and forgets it: nothing
    * here is a form control and nothing is submitted, so what it reports is that
@@ -21684,7 +21677,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The commands, which are `helix-option` elements and their groups.
+   * - `(default)`: The commands, and any groups of them.
    * - `footer`: Under the list, for the keys a reader can press.
    *
    * ## Methods
@@ -21771,7 +21764,7 @@ export type CustomElements = {
    * the same way `label` becomes `aria-label` in there.
    *
    * ```html
-   * <helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+   * <helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
    * ```
    *
    * `commandFor` spells its attribute out, because Lit lowercases a property
@@ -21969,19 +21962,19 @@ export type CustomElements = {
 
   /**
    * **The schema is markup and the data is a property.** Columns are declared as
-   * `helix-table-column` children, because a schema is small and something a
-   * reader should see in the HTML; rows are handed over as an array, because a
-   * table that draws ten thousand elements cannot window them.
+   * `TableColumn` children, because a schema is small and something a reader
+   * should see in the HTML; rows are handed over as an array, because a table
+   * that draws ten thousand elements cannot window them.
    *
    * ```html
-   * <helix-data-table .rows=${rows} sort="name:asc" page-size="20">
-   *   <helix-table-column field="name" sortable>Name</helix-table-column>
-   *   <helix-table-column field="size" align="end" sortable .cell=${bytes}>Size</helix-table-column>
-   * </helix-data-table>
+   * <helix-headless-data-table .rows=${rows} sort="name:asc" page-size="20">
+   *   <helix-headless-table-column field="name" sortable>Name</helix-headless-table-column>
+   *   <helix-headless-table-column field="size" align="end" sortable .cell=${bytes}>Size</helix-headless-table-column>
+   * </helix-headless-data-table>
    * ```
    *
-   * `helix-table` takes rows as markup and is the right component for a table of
-   * twelve things a person wrote out.
+   * `Table` takes rows as markup and is the right component for a table of twelve
+   * things a person wrote out.
    *
    * **Sort and filter apply to the whole set, never the page.** Sorting the drawn
    * window is correct on the first screen and wrong on every other one.
@@ -21990,7 +21983,7 @@ export type CustomElements = {
    * elements do, but reading a cell needs the columns, and the columns are markup
    * children Lit SSR does not hand this element. So a crawler sees a table of the
    * right shape with nothing in it. That is the cost of the first paragraph: use
-   * `helix-table` where the served HTML has to carry the values.
+   * `Table` where the served HTML has to carry the values.
    *
    * **`selectable` adds a column of checkboxes, keyed on `row-key`.** A row is
    * selected by its identity rather than its position, so a selection survives a
@@ -22011,14 +22004,13 @@ export type CustomElements = {
    * in the order on screen, in the columns on screen. Saving it is the page's
    * business, the same as any other file.
    *
-   * **There is no `columns` attribute here, and `helix-table` has one.** The
-   * difference is what a column is in each: here it is the schema, so a table
-   * without one has nothing to read a row with, and every column is a place to
-   * write a `width`. A `helix-table` holds cells a consumer wrote and can be
-   * written with no column at all, so its `columns` is where such a table is
-   * sized from. Written on this element the attribute is inert, which is the trap
-   * worth knowing when moving between the two. What both take is the CSS hook,
-   * `--data-table-columns` here and `--table-columns` there.
+   * **There is no `columns` attribute here, and Table has one.** The difference
+   * is what a column is in each: here it is the schema, so a table without one
+   * has nothing to read a row with, and every column is a place to write a
+   * `width`. A Table holds cells a consumer wrote and can be written with no
+   * column at all, so its `columns` is where such a table is sized from. Written
+   * on this element the attribute is inert, which is the trap worth knowing when
+   * moving between the two.
    *
    * ## Attributes & Properties
    *
@@ -22099,9 +22091,9 @@ export type CustomElements = {
    *
    * **It announces nothing, and that is not an omission.** Nothing in this
    * element ever asks for a different page size: a size selector is
-   * `helix-pagination-size`, which a consumer puts in the `footer` slot and
-   * answers themselves. Routing this through `requestChange` would announce an
-   * event the element never has cause to fire.
+   * `PaginationSize`, which a consumer puts in the `footer` slot and answers
+   * themselves. Routing this through `requestChange` would announce an event
+   * the element never has cause to fire.
    * - `total`: How many rows the whole result has, where this element cannot count them.
    *
    * Only read in `server` mode, where `rows` is one page and its length says
@@ -22188,7 +22180,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The columns, declared as `helix-table-column` children.
+   * - `(default)`: The columns, declared rather than drawn.
    * - `footer`: Below the grid, replacing the pagination this would otherwise draw.
    * - `toolbar`: Above the grid, for a search field or actions.
    *
@@ -22224,8 +22216,8 @@ export type CustomElements = {
    *
    * CSS variables available for styling the component.
    *
-   * - `--data-table-cell-align`: The edge the column a cell sits under is set to, `start`, `center` or `end`, and unset under a column that sets none. Written by the component onto each cell it draws, read by the sheet that paints one; `helix-table` publishes `--table-cell-align` for the same attribute on the cells a consumer wrote, under its own family's name. (default: `undefined`)
-   * - `--data-table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--data-table-columns` is the one to set. (default: `undefined`)
+   * - `--data-table-cell-align`: The edge the column a cell sits under is set to, `start`, `center` or `end`, and unset under a column that sets none. Written by the component onto each cell it draws, read by the sheet that paints one; Table publishes `--table-cell-align` for the same attribute on the cells a consumer wrote, under its own family's name. (default: `undefined`)
+   * - `--data-table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. A column's `width` is the one to set. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -22280,9 +22272,9 @@ export type CustomElements = {
   >;
 
   /**
-   * **The calendar is `helix-date-picker`, not a second one written here.** It
-   * already knows about months, ranges, disabled days, the first day of the week
-   * and every keyboard rule a grid owes a reader. This element is the field, the
+   * **The calendar is `DatePicker`, not a second one written here.** It already
+   * knows about months, ranges, disabled days, the first day of the week and
+   * every keyboard rule a grid owes a reader. This element is the field, the
    * overlay, and the translation between them.
    *
    * **Typed as well as picked, and the typing is why it is not
@@ -23386,8 +23378,8 @@ export type CustomElements = {
    * Opened declaratively with the platform's invoker attributes:
    *
    * ```html
-   * <helix-button commandfor="nav" command="--toggle">Menu</helix-button>
-   * <helix-drawer id="nav">…</helix-drawer>
+   * <helix-headless-button commandfor="nav" command="--toggle">Menu</helix-headless-button>
+   * <helix-headless-drawer id="nav">…</helix-headless-drawer>
    * ```
    *
    * ## Attributes & Properties
@@ -23418,10 +23410,10 @@ export type CustomElements = {
    * not, rather than shown or hidden by CSS.
    * - `placement`: Which edge the drawer comes from.
    *
-   * Unset is `end`, which the styled tier reads as `:host(:not([placement]))`
-   * beside `:host([placement="end"])` rather than as a value written here: a
+   * Unset is `end`, and it stays unset rather than being written down: a
    * default assigned to the property would reflect onto every host and put a
-   * `placement="end"` into markup no consumer wrote.
+   * `placement="end"` into markup no consumer wrote. So what this tier
+   * guarantees is the absence, and a sheet selects on it.
    * - `open`: Whether the element is open.
    *
    * One property, not two, so `dialog.open` answers the question anyone
@@ -24304,7 +24296,13 @@ export type CustomElements = {
    * - `fields`: The fields declared inside this, in the order they were written.
    *
    * What a render may know of them: none on a server, whose shim has no tree
-   * and threw here, and none while hydrating what one sent. (property only) (readonly)
+   * and threw here, and none while hydrating what one sent.
+   *
+   * By identity rather than by tag. A list of names can only hold the tags this
+   * package knows about, so it misses any third one, which is what subclassing
+   * a headless element produces, and it is also how a headless package learns a
+   * styled tag. `instanceof` answers for every one of them and proves the type
+   * the signature claims. (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
@@ -24541,12 +24539,12 @@ export type CustomElements = {
    * `FilterField` already plays on its own children.
    *
    * **It can suggest what to type next, and deciding what to suggest is still the
-   * consumer's.** Slot `helix-option` elements into `suggestions` and the field
-   * shows them, moves through them with the arrows, and lets Enter press one; the
-   * option fires its own `helix-select` and the consumer decides what choosing
-   * meant. Keys before a colon and values after it are the same panel with
-   * different contents, and `readFilterText` is exported for a consumer narrowing
-   * that panel against what a reader has half typed.
+   * consumer's.** Slot options into `suggestions` and the field shows them, moves
+   * through them with the arrows, and lets Enter press one; the option fires its
+   * own `helix-select` and the consumer decides what choosing meant. Keys before
+   * a colon and values after it are the same panel with different contents, and
+   * `readFilterText` is exported for a consumer narrowing that panel against what
+   * a reader has half typed.
    *
    * **The panel opens when there is something in it and closes when there is
    * not**, rather than on a choice. A reader who picks a key wants its values
@@ -24844,11 +24842,12 @@ export type CustomElements = {
    * would give.
    *
    * **The element's own text is read as a fallback, and only in a browser.**
-   * `<helix-format-date elapsed>2026-08-27T01:00:00Z</helix-format-date>` is the
-   * spelling that reads best in markup, and it cannot be the only one: measured
-   * against Lit's server shim, `textContent`, `children`, `firstChild` and
-   * `querySelector` are all `undefined` there, so a server has no way to see it.
-   * An element rendered on a server needs the attribute; one rendered in a
+   * `<helix-headless-format-date
+   * elapsed>2026-08-27T01:00:00Z</helix-headless-format-date>` is the spelling
+   * that reads best in markup, and it cannot be the only one: measured against
+   * Lit's server shim, `textContent`, `children`, `firstChild` and
+   * `querySelector` are all `undefined` there, so a server has no way to see
+   * it. An element rendered on a server needs the attribute; one rendered in a
    * browser may use either.
    * - `day`: How the day of the month is written, where a date is shown.
    * - `elapsed`: Show how long ago it was, compactly, instead of the date.
@@ -24948,12 +24947,12 @@ export type CustomElements = {
    * consumer has to keep by hand, and the one number a summary is told to trust
    * is the one it gets wrong.
    *
-   * The strip measures itself, so `--heatmap-cell-inline-size` and `--heatmap-gap` are
-   * enough on their own and these two are the estimate used until the first
-   * measurement lands. Writing the attribute pins the value and stops the
-   * measurement being consulted, which is what a container query or a transition
-   * on the cell size wants, where what is drawn this frame is not what the
-   * arithmetic should plan around.
+   * The strip measures itself, so sizing the cells in a sheet is enough on its
+   * own and these two are the estimate used until the first measurement lands.
+   * Writing the attribute pins the value and stops the measurement being
+   * consulted, which is what a container query or a transition on the cell size
+   * wants, where what is drawn this frame is not what the arithmetic should
+   * plan around.
    *
    * Zero turns the dropping off altogether, which is right for a strip in a
    * container that cannot get narrow.
@@ -25097,11 +25096,6 @@ export type CustomElements = {
    *
    * CSS variables available for styling the component.
    *
-   * - `--heatmap-cell-height`: How tall a cell is. A row of a tall thin cell is what a status page draws. (default: `undefined`)
-   * - `--heatmap-cell-inline-size`: How wide a cell is. The strip fits as many as the container allows. (default: `undefined`)
-   * - `--heatmap-cell-radius`: How far a cell's corners are rounded. (default: `undefined`)
-   * - `--heatmap-cell-size`: The size a cell wants on both axes, where neither is given its own. (default: `undefined`)
-   * - `--heatmap-gap`: Space between cells. Zero is a continuous field rather than a grid of tiles. (default: `undefined`)
    * - `--heatmap-rows`: How many rows the strip lays out. Written by the component from the data, read by the tier that draws it. (default: `undefined`)
    * - `--heatmap-tone`: The tone of the cell this is set on. Written by the component, read by the sheet that paints. (default: `undefined`)
    * - `--heatmap-tone-1`: The quietest step of the magnitude ramp, reached by `tones="1 …"`. (default: `undefined`)
@@ -25185,7 +25179,7 @@ export type CustomElements = {
    * the same way `label` becomes `aria-label` in there.
    *
    * ```html
-   * <helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+   * <helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
    * ```
    *
    * `commandFor` spells its attribute out, because Lit lowercases a property
@@ -25502,10 +25496,10 @@ export type CustomElements = {
    * **Mirrored to `data-status`, and not reflected as `status`.** It is element
    * state, so reflecting it puts the element's own bookkeeping into the markup
    * a consumer rendered: React reads the attribute appearing at upgrade as a
-   * hydration mismatch, and a serialized `<helix-image status="loaded">` pasted
-   * back declares that a picture has arrived which this element has never
-   * fetched. The `data-` name is the library's answer to both, being a name a
-   * re-parse cannot mistake for a declaration, and it is what `data-closed` on
+   * hydration mismatch, and a host pasted back carrying `status="loaded"`
+   * declares that a picture has arrived which this element has never fetched.
+   * The `data-` name is the library's answer to both, being a name a re-parse
+   * cannot mistake for a declaration, and it is what `data-closed` on
    * `Toast.Item` already does. A picture arrives after somebody fetched it,
    * which puts this on the safe side of hydration: a fact that can be true on
    * the *first* update mirrors to a custom state instead, which is what
@@ -25618,10 +25612,10 @@ export type CustomElements = {
    * **The attribute is `readonly`, which is the platform's spelling.** A
    * camelCase property needs an explicit `attribute`, and dash-casing a word
    * HTML writes as one costs what an attribute always costs here: nothing
-   * warns. `<helix-input readonly>` is what anybody who has written HTML types;
-   * against `read-only` it parses to no property at all, and the field stays
-   * editable with no error anywhere. Measured on the dash-cased form, `readOnly`
-   * came back `false`.
+   * warns. `<helix-headless-input readonly>` is what anybody who has written
+   * HTML types; against `read-only` it parses to no property at all, and the
+   * field stays editable with no error anywhere. Measured on the dash-cased
+   * form, `readOnly` came back `false`.
    * - `reveal`: Whether a password field offers a toggle that shows what was typed.
    *
    * Ignored on every other type. A reveal on an email field would be a button
@@ -25635,9 +25629,9 @@ export type CustomElements = {
    *
    * **Not reflected.** Reflection exists so a selector can reach a value, and
    * no stylesheet in this repository selects on `type`. Reflecting it writes
-   * `type="text"` onto every `<helix-input>` ever rendered, an attribute no
-   * consumer's markup has, which is the fault the area rules write up under
-   * `Button`'s `href`, `target` and `rel`.
+   * `type="text"` onto every `<helix-headless-input>` ever rendered, an
+   * attribute no consumer's markup has, which is the fault the area rules write
+   * up under `Button`'s `href`, `target` and `rel`.
    *
    * Nothing reads it from the attribute either. The real `<input>` inside takes
    * it as a property binding, which is what makes the keyboard and the
@@ -26083,8 +26077,7 @@ export type CustomElements = {
    * over something busy. `triangle` points along the axis and reads as "and
    * onward" rather than as a second claim about the data.
    *
-   * The shapes come from
-   * `helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so
+   * The shapes come from one shared sheet, the same one `Sparkline` takes, so
    * the set is identical wherever one appears. **Which is why every value is
    * named here.** `Sparkline` shipped `square` implemented, drawn, asserted and
    * undocumented until the cohort before this one; this family reads the same
@@ -26349,10 +26342,10 @@ export type CustomElements = {
    * - `label`: Accessible name for the set.
    * - `type`: Which markers an ordered list draws, in `<ol type>`'s own five values.
    *
-   * Reflected, because this is one of the things a stylesheet selects on and
-   * the styled tier maps each to a `list-style-type`. The platform's spellings
-   * rather than the CSS ones, so `<helix-list kind="ordered" type="i">` is what
-   * a consumer would have written on an `<ol>`.
+   * Reflected, because this is one of the things a stylesheet selects on, each
+   * value mapping to a `list-style-type`. The platform's spellings rather than
+   * the CSS ones, so `<helix-headless-list kind="ordered" type="i">` is what a
+   * consumer would have written on an `<ol>`.
    *
    * **`start` and `reversed` are both absent and neither can be done here.**
    * This renders no `<ol>`: the rows are slotted and numbered by the CSS
@@ -27511,9 +27504,9 @@ export type CustomElements = {
   >;
 
   /**
-   * A notification is a toast that did not go away. `helix-toast` is deliberately
-   * the opposite of this: a live region whose items carry a `duration` and whose
-   * root never creates or destroys anything. What makes this its own family is the
+   * A notification is a toast that did not go away. `Toast` is deliberately the
+   * opposite of this: a live region whose items carry a `duration` and whose root
+   * never creates or destroys anything. What makes this its own family is the
    * state each item carries rather than the arrangement it sits in: read and
    * unread, a timestamp that has to stay correct, and an action a reader can take
    * later.
@@ -27525,9 +27518,9 @@ export type CustomElements = {
    * reader wants exactly one of them at a time: the time while they are scanning,
    * and what they can do about it once they have stopped on a row.
    *
-   * **The timestamp is `helix-format-date`**, which is where the reading, the
-   * `<time datetime>` and the shared timer now live. It was implemented here, and
-   * a component that formats a date is not a fact about notifications: Chat wanted
+   * **The timestamp is `FormatDate`**, which is where the reading, the `<time
+   * datetime>` and the shared timer now live. It was implemented here, and a
+   * component that formats a date is not a fact about notifications: Chat wanted
    * the same thing and had its own copy of half of it.
    *
    * **Read state is reported, not invented.** Marking something read is usually a
@@ -27553,10 +27546,10 @@ export type CustomElements = {
    *
    * **Not reflected.** Unread is a visual state, which is why the four mixins
    * mirror theirs, but the mirror may not be the property's own attribute:
-   * `<helix-notification default-read>` comes back from a server without `read`
-   * and would gain it on the first update, which React reports as a hydration
-   * mismatch, and which a copy of the serialized element re-parses as a
-   * declaration. `:state(read)` is what the stylesheet reads.
+   * `<helix-headless-notification default-read>` comes back from a server
+   * without `read` and would gain it on the first update, which React reports
+   * as a hydration mismatch, and which a copy of the serialized element
+   * re-parses as a 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.
    * - `locale`: Locale for the timestamp.
@@ -27748,7 +27741,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The notifications, as `helix-notification` children.
+   * - `(default)`: The notifications.
    * - `footer`: Below the list, for a link to everything.
    * - `header`: Above the list, for a title and the mark-all control.
    *
@@ -28338,7 +28331,7 @@ export type CustomElements = {
    * **The attribute, read when it is asked for, and never a snapshot taken in
    * the constructor.** A field initializer runs there, and an element the HTML
    * parser created has none of its attributes yet at that moment: measured on
-   * this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+   * this element, on `Radio` and on `Toggle`, `<helix-headless-option value="a"
    * selected>` reported `defaultSelected` as `false` both from parsed markup
    * and from `createElement` followed by `setAttribute`, which is every way a
    * consumer writes one. The snapshot could only ever be true for an element
@@ -28556,8 +28549,8 @@ export type CustomElements = {
   /**
    * **The component is the truncation.** Given a page and a total it works out
    * which numbers to show and where the runs break, so this is data-driven rather
-   * than composed: `<helix-pagination page="4" pages="12">` rather than twelve
-   * slotted children a consumer keeps in step with their own query.
+   * than composed: `<helix-headless-pagination page="4" pages="12">` rather than
+   * twelve slotted children a consumer keeps in step with their own query.
    *
    * **The width does not change as you page.** The run around the current page is
    * `siblings` either side, and grows to absorb a gap slot at a boundary, so the
@@ -28995,10 +28988,10 @@ export type CustomElements = {
    * marked letters wants `text`, which judges nothing.
    *
    * **Not reflected**: nothing selects on it, so reflecting only writes
-   * `type="numeric"` onto every `<helix-pin-input>` ever rendered, an attribute
-   * no consumer's markup had. The area rules carry the sentence "reflect only
-   * what CSS selects on". The real inputs take it as a binding, which is what
-   * makes the keyboard follow.
+   * `type="numeric"` onto every `<helix-headless-pin-input>` ever rendered, an
+   * attribute no consumer's markup had. The area rules carry the sentence
+   * "reflect only what CSS selects on". The real inputs take it as a binding,
+   * which is what makes the keyboard follow.
    * - `default-value`/`defaultValue`: The value the markup declared, which is where a reset returns to.
    * - `value`: What the control holds now, and what its form submits.
    *
@@ -29741,7 +29734,7 @@ export type CustomElements = {
    * **The attribute, read when it is asked for, and never a snapshot taken in
    * the constructor.** A field initializer runs there, and an element the HTML
    * parser created has none of its attributes yet at that moment: measured on
-   * this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+   * this element, on `Option` and on `Toggle`, `<helix-headless-radio value="a"
    * selected>` reported `defaultSelected` as `false` both from parsed markup
    * and from `createElement` followed by `setAttribute`, which is every way a
    * consumer writes one. The snapshot could only ever be true for an element
@@ -31190,11 +31183,10 @@ export type CustomElements = {
    * mean defining what a dial with a submenu in it does.
    *
    * **The trigger is a control the consumer slots**, and the floating action
-   * button is the usual one: `helix-icon-button` with `shape="circle"` and
-   * `raised`. There is no `helix-fab`, because it would re-declare `emphasis`,
-   * `tone`, `label` and a size around a control that already has all four. A
-   * round raised button is a shape, and where it sits is `data-dock` in the base
-   * layer.
+   * button is the usual one: `IconButton` with `shape="circle"` and `raised`.
+   * There is no `helix-fab`, because it would re-declare `emphasis`, `tone`,
+   * `label` and a size around a control that already has all four. A round raised
+   * button is a shape, and where it sits is `data-dock` in the base layer.
    *
    * **Nothing is reserved from the keyboard.** A menu that drills has to keep the
    * horizontal pair for going in and coming back; a dial goes nowhere, so all four
@@ -31553,9 +31545,9 @@ export type CustomElements = {
    * The row directions set them side by side, for a figure in a line of text or
    * a narrow strip where a stacked pair would be two lines of almost nothing.
    *
-   * A property rather than a `helix-flex` around it, because the unit has to
-   * stay on the value's baseline whichever way the pair goes, and only this
-   * element knows which of its children the unit belongs to.
+   * A property rather than a `Flex` around it, because the unit has to stay on
+   * the value's baseline whichever way the pair goes, and only this element
+   * knows which of its children the unit belongs to.
    *
    * **Optional rather than defaulted to `column`, which is not a style
    * preference.** A reflecting property with a default writes its attribute onto
@@ -31688,7 +31680,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The steps, which are `helix-step` elements.
+   * - `(default)`: The steps.
    *
    * ## Methods
    *
@@ -31715,9 +31707,9 @@ export type CustomElements = {
 
   /**
    * **The name is a button, and only the name.** The marker is `aria-hidden`
-   * decoration, so wrapping it would add hit area and no meaning. It is
-   * `helix-button` rather than a `<button>` this element resets: the hover wash,
-   * the focus ring and the disabled treatment are decisions the button carries.
+   * decoration, so wrapping it would add hit area and no meaning. It is `Button`
+   * rather than a `<button>` this element resets: the hover wash, the focus ring
+   * and the disabled treatment are decisions the button carries.
    *
    * **It says nothing about where a reader may go.** Every step is pressable and
    * announces itself with `helix-select`; refusing the ones ahead is `disabled`,
@@ -31770,7 +31762,7 @@ export type CustomElements = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The step's name.
-   * - `content`: What the stage holds. Always rendered here, a tier with no stylesheet having nothing to fold it with; the styled tier opens it on the current step down a column, and a row has no space under a step to open it into.
+   * - `content`: What the stage holds. Always rendered here, a tier with no stylesheet having nothing to fold it with, so whether it is folded away is the sheet's answer and not this tier's.
    * - `description`: A line under the name, for what the stage is for.
    * - `marker`: Replaces the number, or the check a complete step shows.
    *
@@ -31787,7 +31779,7 @@ export type CustomElements = {
    * - `body`: The name and its description.
    * - `content`: What the stage holds, while it is open.
    * - `description`: The line under it.
-   * - `label`: The step's name, which is a `helix-button`.
+   * - `label`: The step's name, which is a control.
    * - `label-button`: The inner control.
    * - `lead`: The half line arriving from the step before.
    * - `mark`: The glyph inside the marker: a tick, a dot, or an empty ring.
@@ -32047,23 +32039,23 @@ export type CustomElements = {
    * the table has another track; remove one and it does not. That is what ties
    * the two together, and a table-level track list on its own does not: a list
    * that is accidentally the headings is invalid CSS a grid ignores in silence,
-   * drawing the whole table as one column. `helix-table`'s `columns` is dealt out
-   * a track at a time against the columns declared under it, so a heading among
-   * the widths costs its own column a width and no more, and a list longer or
-   * shorter than the columns is trimmed or shared rather than being a second
-   * count of them. A column's own `width` wins over the track in its place.
+   * drawing the whole table as one column. `Table`'s `columns` is dealt out a
+   * track at a time against the columns declared under it, so a heading among the
+   * widths costs its own column a width and no more, and a list longer or shorter
+   * than the columns is trimmed or shared rather than being a second count of
+   * them. A column's own `width` wins over the track in its place.
    *
    * **It is also where every per-column fact goes**, which is the reason
-   * `helix-data-table` needs no column config object. `field` names the key the
-   * cell reads, `sortable` says a reader may reorder by it, `align` says which
-   * edge the values line up against, and `cell` takes a function for anything the
+   * `DataTable` needs no column config object. `field` names the key the cell
+   * reads, `sortable` says a reader may reorder by it, `align` says which edge
+   * the values line up against, and `cell` takes a function for anything the
    * field alone cannot express. The schema is markup and the data is a property:
    * a schema is small, declarative, and something a reader should be able to see
    * in the HTML, and data is large and windowed.
    *
    * **The same element serves both tables**, the markup one and the data one. It
-   * is identified by a flag rather than by `instanceof`, so a `helix-table-column`
-   * works inside either without the two roots sharing anything else.
+   * is identified by a flag rather than by `instanceof`, so a `TableColumn` works
+   * inside either without the two roots sharing anything else.
    *
    * **It generates no box of its own**, the same as a row: the heading is a grid
    * item of the table, so it lines up with the cells under it rather than sitting
@@ -32073,10 +32065,10 @@ export type CustomElements = {
    * both, so the columns after it keep their own widths and every row keeps its
    * cells under their headings. `hidden="until-found"` keeps its track, the
    * heading being left drawn, as every Helix element leaves one with that value.
-   * `helix-data-table` draws the cells, so it leaves out the ones under a hidden
-   * column. A `helix-table`'s cells are markup the consumer wrote, so hide them
-   * with the column, as removing a column means removing its cells: a row with a
-   * cell more than the table has tracks wraps into the next.
+   * `DataTable` draws the cells, so it leaves out the ones under a hidden column.
+   * A `Table`'s cells are markup the consumer wrote, so hide them with the
+   * column, as removing a column means removing its cells: a row with a cell more
+   * than the table has tracks wraps into the next.
    *
    * **A heading that does something holds a control that does it.** The host is
    * the column header, and a header is not focusable, so a sortable heading is a
@@ -32092,15 +32084,15 @@ export type CustomElements = {
    *
    * - `align`: Which edge the values line up against.
    *
-   * `end` is what a column of numbers wants, so digits of the same magnitude sit
-   * above each other. Left unset the cell inherits the table's own alignment,
-   * which is `start` for text in either writing direction. `helix-data-table`
-   * aligns the cells it draws. A `helix-table`'s cells are markup the consumer
-   * wrote, so the table writes nothing onto them: it publishes the edge to each
-   * cell under this column as `--table-cell-align`, which `@fusion.dev/helix`
-   * reads. The heading is this element's own, and `@fusion.dev/helix` sets it to
-   * the same edge in either table. `end` is the inline end, so in a
-   * right-to-left table it is the left.
+   * `end` is what a column of numbers wants, so digits of the same magnitude
+   * sit above each other. Left unset the cell inherits the table's own
+   * alignment, which is `start` for text in either writing direction.
+   * `DataTable` aligns the cells it draws. A `Table`'s cells are markup the
+   * consumer wrote, so the table writes nothing onto them: it publishes the
+   * edge to each cell under this column as `--table-cell-align`, which
+   * `@fusion.dev/helix` reads. The heading is this element's own, and
+   * `@fusion.dev/helix` sets it to the same edge in either table. `end` is the
+   * inline end, so in a right-to-left table it is the left.
    *
    * **Reflected, because the heading is drawn by a stylesheet and has no other
    * way to learn it.** Set as a property, which is how React sets it, an
@@ -32143,8 +32135,8 @@ export type CustomElements = {
    * - `width`: The track this column takes, as CSS.
    *
    * A single track value, so anything valid in `grid-template-columns` works:
-   * `16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track
-   * in its place in a `helix-table`'s `columns`, where that table sets one, and
+   * `16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track in
+   * its place in a `Table`'s `columns`, where that table sets one, and
    * otherwise shares what is left over equally, as `minmax(max-content, 1fr)`.
    * Set here, it wins over that list, which is what lets a reader resize a
    * column in a table that set one.
@@ -32269,15 +32261,14 @@ export type CustomElements = {
    *
    * - `columns`: The column widths as one track list, written once on the table.
    *
-   * With `helix-table-column` children, each track sizes the column in its
-   * place, a hidden column counted, so hiding one takes its track with it and
-   * the rest keep theirs. The columns decide how many tracks there are and this
-   * list only how wide: a track past the last column is dropped, and a column
-   * past the last track shares what is left. With no columns declared it is
-   * the whole track list. Tracks count as the grid counts them, so
-   * `minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid
-   * would refuse leaves its column at the default rather than taking the table
-   * down to one column.
+   * With `TableColumn` children, each track sizes the column in its place, a
+   * hidden column counted, so hiding one takes its track with it and the rest
+   * keep theirs. The columns decide how many tracks there are and this list
+   * only how wide: a track past the last column is dropped, and a column past
+   * the last track shares what is left. With no columns declared it is the
+   * whole track list. Tracks count as the grid counts them, so `minmax(0, 1fr)`
+   * is one and `repeat(2, 8rem)` is two, and one the grid would refuse leaves
+   * its column at the default rather than taking the table down to one column.
    *
    * **A column's own `width` wins over its track here.** The width is written
    * on the column it sizes, which is the more particular statement, and it is
@@ -32291,13 +32282,11 @@ export type CustomElements = {
    * whole answer: a table given one lays its grid out in the first paint, and a
    * table sized only by its columns is one track wide until it upgrades.
    *
-   * **`helix-data-table` has none of this, and should not.** Its columns are
-   * its schema rather than an option, so there is always a column to write a
-   * `width` on and a list here would be a second way to say what that says.
-   * This table's cells are markup, and a table written as rows of cells with no
-   * `helix-table-column` in it has nowhere else to be sized from. Both families
-   * take the same CSS hook, `--table-columns` and `--data-table-columns`, which
-   * wins over whichever list the element worked out.
+   * **Data Table has none of this, and should not.** Its columns are its schema
+   * rather than an option, so there is always a column to write a `width` on
+   * and a list here would be a second way to say what that says. This table's
+   * cells are markup, and a table written as rows of cells with no column
+   * declared in it has nowhere else to be sized from.
    * - `label`: Accessible name for the table.
    * - `empty-text`/`emptyText`: What is said where there are none, and none are coming.
    * - `loading`: Whether the rows are still on their way.
@@ -32338,7 +32327,7 @@ export type CustomElements = {
    *
    * CSS variables available for styling the component.
    *
-   * - `--table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--table-columns` is the one to set. (default: `undefined`)
+   * - `--table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `columns` is the one to set. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -32360,10 +32349,10 @@ export type CustomElements = {
   >;
 
   /**
-   * `display: contents` in the styled tier, so the row's cells become items of
-   * the table's own grid and every column lines up across every row. The row
-   * still exists as an element, which is what a `<table>` gives away when its
-   * cells are laid out by the table algorithm.
+   * The row renders its cells straight through and lays out none of them, so a
+   * sheet can take them into the table's own grid and every column lines up
+   * across every row. The row still exists as an element, which is what a
+   * `<table>` gives away when its cells are laid out by the table algorithm.
    *
    * ## Attributes & Properties
    *
@@ -32964,10 +32953,10 @@ export type CustomElements = {
   >;
 
   /**
-   * **The list is `helix-time-picker`, not a second one written here.** It is worth
+   * **The list is `TimePicker`, not a second one written here.** It is worth
    * having on its own, flat in a settings pane with nothing to open, and this
    * element is the field, the overlay and the form. Exactly the arrangement Input
-   * Date has with `helix-date-picker` and Color Input with `helix-color-picker`.
+   * Date has with `DatePicker` and Color Input with `ColorPicker`.
    *
    * **Typed as well as picked, and that is the division the list depends on.** A
    * list at a step offers the times a product actually has, and the field is how a
@@ -32998,8 +32987,8 @@ export type CustomElements = {
    *
    * Absent is one. `range` holds a start and an end, `multiple` holds any
    * number, and both are carried as one comma-separated value, which is what a
-   * form submits. `helix-time-picker` carries the longer note on the interaction and on
-   * why a wheel cannot do either.
+   * form submits. `TimePicker` carries the longer note on the interaction and
+   * on why a wheel cannot do either.
    * - `placeholder`: What the field says before a time is in it.
    * - `step`: How far apart the offered times are, in minutes.
    * - `time-style`/`timeStyle`: Whether the field writes the time out, or holds the value as it is.
@@ -33014,7 +33003,7 @@ export type CustomElements = {
    * `list` offers whole times, which is what a product with slots or opening
    * hours has. `wheels` splits them into an hour, a minute and a meridiem where
    * the locale uses one, which is the only way to reach `23:45` without
-   * scrolling most of a day. `helix-time-picker` carries the longer note on the trade.
+   * scrolling most of a day. `TimePicker` carries the longer note on the trade.
    *
    * **Optional rather than defaulted, which is not a style preference.** A
    * reflecting property with a default writes its attribute onto every host the
@@ -33258,8 +33247,8 @@ export type CustomElements = {
 
   /**
    * **A list rather than three wheels**, and the reason is what a list already
-   * is. `helix-listbox` brings the keyboard, the typeahead, the scroll into view
-   * and the announcement of a set of options, and a time at a step is a set of
+   * is. `Listbox` brings the keyboard, the typeahead, the scroll into view and
+   * the announcement of a set of options, and a time at a step is a set of
    * options. Three little wheels for hours, minutes and a meridiem are three
    * controls to build, three to test, and a tab stop each for something a reader
    * answers once.
@@ -33320,7 +33309,7 @@ export type CustomElements = {
    *
    * Absent is one. `range` holds a start and an end with everything between
    * them shown as part of the answer, `multiple` holds any number, and both are
-   * carried as one comma-separated value: the same shape `helix-date-picker` uses,
+   * carried as one comma-separated value: the same shape `DatePicker` uses,
    * because it is the same question asked of a different unit.
    *
    * **A range is two picks, and a third starts over.** That is the calendar's
@@ -33869,7 +33858,7 @@ export type CustomElements = {
    * **Optional, and bottom-end is the absence of it.** Reflecting *and*
    * defaulting is the pair that writes onto a host: every toast region anybody
    * rendered would gain a `placement="bottom-end"` nobody typed, which a React
-   * consumer's server markup does not have. The styled sheet carries the resting
+   * consumer's server markup does not have. A sheet carries the resting
    * arrangement in its own `:host` rule and the selectors describe only the
    * departures, which is what `orientation` does.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -33903,7 +33892,7 @@ export type CustomElements = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The messages, as `helix-toast-item` elements.
+   * - `(default)`: The messages.
    *
    * ## CSS Parts
    *
@@ -34133,11 +34122,11 @@ export type CustomElements = {
    * **The attribute, read when it is asked for, and never a snapshot taken in
    * the constructor.** A field initializer runs there, and an element the HTML
    * parser created has none of its attributes yet at that moment: measured on
-   * this element, on `Option` and on `Radio`, `<helix-toggle value="light"
-   * selected>` reported `defaultSelected` as `false` both from parsed markup
-   * and from `createElement` followed by `setAttribute`, which is every way a
-   * consumer writes one. The snapshot could only ever be true for an element
-   * already in the document when `customElements.define` ran.
+   * this element, on `Option` and on `Radio`, `<helix-headless-toggle
+   * value="light" selected>` reported `defaultSelected` as `false` both from
+   * parsed markup and from `createElement` followed by `setAttribute`, which is
+   * every way a consumer writes one. The snapshot could only ever be true for
+   * an element already in the document when `customElements.define` ran.
    *
    * Nothing overwrites it either, which is what makes reading it late correct
    * rather than merely later: `selected` does not reflect, for the reason
@@ -34293,8 +34282,8 @@ export type CustomElements = {
    * the ordinary way:
    *
    * ```html
-   * <helix-button id="save" aria-describedby="save-tip">Save</helix-button>
-   * <helix-tooltip id="save-tip" for="save" content="Save your work"></helix-tooltip>
+   * <helix-headless-button id="save" aria-describedby="save-tip">Save</helix-headless-button>
+   * <helix-headless-tooltip id="save-tip" for="save" content="Save your work"></helix-headless-tooltip>
    * ```
    *
    * The reference points at *this host*, not at the bubble in its shadow root:
@@ -34603,9 +34592,9 @@ export type CustomElements = {
    * - **When it shows.** Which is `current`, and which the root decides.
    *
    * What it does not own is the heading, the paragraph, the picture and the
-   * layout. Slot a `helix-card`, or a heading and a line of prose, or anything
-   * else. Fixed `title` and `body` parts would be a component deciding what a
-   * tour is allowed to say.
+   * layout. Slot a `Card`, or a heading and a line of prose, or anything else.
+   * Fixed `title` and `body` parts would be a component deciding what a tour is
+   * allowed to say.
    *
    * **The buttons are slot fallback, so the common case costs nothing and the
    * uncommon one is possible.** Write nothing and get Back, Next and Skip already
@@ -35352,7 +35341,7 @@ export type CustomElements = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The entries.
-   * - `player`: The `helix-video` they play in.
+   * - `player`: The player the entries take turns in.
    *
    * ## Methods
    *
@@ -35906,7 +35895,7 @@ export type CustomElementsSolidJs = {
    * item added a second after render coordinates on its first click.
    *
    * Items are matched with `instanceof HelixHeadlessAccordionItem`, never by tag
-   * name. Matching `helix-accordion-item` would tie this tier to the styled one.
+   * name, so this tier does not learn about the styled one.
    *
    * The keyboard listener is the controller's and is attached on connect, so
    * none of it runs on the server, where there is no tree to walk and no events
@@ -36404,13 +36393,13 @@ export type CustomElementsSolidJs = {
    * Unset shows all of them, which is what no limit means and is more useful
    * than refusing to render.
    *
-   * **Reflected, because the fold is a stylesheet rule and nothing else.** The
-   * styled tier hides past the limit with `:host([max="N"]) ::slotted(:nth-child(n + N+1))`,
-   * so the attribute *is* the mechanism: a `max` that reaches this property and
-   * never reaches the host matches no rule, and every avatar is drawn beside a
-   * count claiming some are hidden. Markup is the safe path and hides the fault;
-   * a script is the broken one, and React takes it for everyone, assigning a
-   * matching property rather than an attribute.
+   * **Reflected, because the fold is a stylesheet rule and nothing else.** A
+   * sheet hides past the limit one selector per value, as `FOLDS_UP_TO`
+   * describes, so the attribute *is* the mechanism: a `max` that reaches this
+   * property and never reaches the host matches no rule, and every avatar is
+   * drawn beside a count claiming some are hidden. Markup is the safe path and
+   * hides the fault; a script is the broken one, and React takes it for
+   * everyone, assigning a matching property rather than an attribute.
    *
    * **Optional rather than defaulted, per the rule that a reflected property
    * takes no default**: `max = 0` would stamp `max="0"` onto every host that
@@ -36830,7 +36819,7 @@ export type CustomElementsSolidJs = {
    * CSS variables available for styling the component.
    *
    * - `--bar-chart-axis`: How wide an axis column is drawn, in `ch`, from the widest number on it. Written on the axis itself, and only where the categories run along the bottom: turned sideways an axis is a row and takes a line's height instead. (default: `undefined`)
-   * - `--bar-chart-secondary`: The color of the secondary axis when one series owns it. It resolves a `--helix-color-series-*` token, so on the headless tier alone it names something that is not there. #138. (default: `undefined`)
+   * - `--bar-chart-secondary`: The color of the secondary axis, where one series owns it. Written by the component from that series' `--chart-series-*`, so it promises the series color and nothing more: whatever that hook resolves to is what the axis is drawn in. (default: `undefined`)
    * - `--chart-bar-wash`: The gradient a bar would take, named per bar so the styled tier can point `fill` at it. Drawn whatever the treatment and used only where `wash="gradient"` asks for it. (default: `undefined`)
    *
    * ## CSS Parts
@@ -36977,12 +36966,12 @@ export type CustomElementsSolidJs = {
    * - `current`: Whether this item is the page the reader is on.
    * - `href`: Where the crumb goes, and nothing where it is the current page.
    *
-   * **Optional and reflected, because a stylesheet does select on it.**
-   * `breadcrumb.css` writes `:host(:not([href])) [part="link"]` to take the
-   * block padding off a crumb that is not a link, so the attribute is what
-   * decides how tall a crumb is. Unreflected, an `href` set from script reached
-   * the property, rendered the anchor, and left the host looking unlinked: the
-   * crumb drew at 20px where a markup twin drew at 28.
+   * **Optional and reflected, because a stylesheet does select on it.** A sheet
+   * writes `:host(:not([href])) [part="link"]` to take the block padding off a
+   * crumb that is not a link, so the attribute is what decides how tall a crumb
+   * is. Unreflected, an `href` set from script reached the property, rendered
+   * the anchor, and left the host looking unlinked: the crumb drew at 20px
+   * where a markup twin drew at 28.
    *
    * Optional rather than defaulted, which is the general rule that a reflected
    * property takes no default: an `href` written onto every host would be a link
@@ -37222,7 +37211,7 @@ export type CustomElementsSolidJs = {
    * the same way `label` becomes `aria-label` in there.
    *
    * ```html
-   * <helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+   * <helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
    * ```
    *
    * `commandFor` spells its attribute out, because Lit lowercases a property
@@ -37504,7 +37493,7 @@ export type CustomElementsSolidJs = {
    *
    * The host is the surface. A wrapper `<div part="container">` would be a second
    * box doing nothing the host cannot: the element itself takes the border, the
-   * radius, and the grid, and a consumer styles `helix-card` rather than reaching
+   * radius, and the grid, and a consumer styles `Card` rather than reaching
    * through `::part`. One node instead of two, on every card on the page.
    *
    * Name the card with `aria-label` or `aria-labelledby`. That is the only
@@ -37656,13 +37645,13 @@ export type CustomElementsSolidJs = {
    * **The number is published to the styles rather than enumerated by them**,
    * as `--carousel-per-view` on the track, which is what keeps a width and a
    * count from disagreeing. A sheet can only name a value it wrote a rule for,
-   * so the styled tier enumerated `per-view="2"` through `5` and called five a
-   * judgment; above it the pane fell back to one across while this file went on
-   * counting positions. Measured in Chromium over eight slides, six across gave
-   * three dots, a pane taking the whole track and five slides reachable only by
-   * dragging. Written from here there is no ceiling to exceed, and a consumer's
-   * own sheet reads the same declaration the styled one does. `runEnd` publishes
-   * its correction the same way and for the same reason.
+   * so a sheet enumerating `per-view="2"` through `5` is a ceiling of five, and
+   * above it the pane falls back to one across while this file goes on counting
+   * positions. Measured in Chromium over eight slides against such a sheet, six
+   * across gave three dots, a pane taking the whole track and five slides
+   * reachable only by dragging. Published from here there is no ceiling to
+   * exceed, and every sheet reads the same declaration. `runEnd` publishes its
+   * correction the same way and for the same reason.
    *
    * **On the track and not on the host.** A custom property on the host is a
    * reflected attribute by another name: it would arrive on upgrade, and a
@@ -37687,8 +37676,8 @@ export type CustomElementsSolidJs = {
    * `auto` track is handed nothing. A count stays for the design that calls for
    * exactly three.
    *
-   * The styled sheet says how it divides, and the headless `auto` example
-   * carries the same three lines for a consumer writing their own.
+   * A sheet says how it divides, and the `auto` example here carries the same
+   * three lines for a consumer writing their own.
    *
    * **A value rather than the resting behavior**, which is what the
    * responsiveness policy asks of every axis that a box decides: a splitter
@@ -38067,13 +38056,13 @@ export type CustomElementsSolidJs = {
    *
    * **Not reflected, and the default is why.** A reflected property that
    * defaults to true writes its attribute on upgrade whether or not the
-   * consumer wrote one, so the server serves `<helix-chat label="x">` and the
-   * client turns it into `<helix-chat label="x" pinned>`: a hydration mismatch a
-   * React consumer reports and does not patch up. Nothing needs the attribute
-   * either, because the one thing that changes with the pin is the way back, and
-   * that is a part inside the shadow tree where a stylesheet can already reach
-   * it. Measured rather than assumed: `label, pinned` after upgrade against
-   * `label` from the server.
+   * consumer wrote one, so the server serves `<helix-headless-chat label="x">`
+   * and the client turns it into `<helix-headless-chat label="x" pinned>`: a
+   * hydration mismatch a React consumer reports and does not patch up. Nothing
+   * needs the attribute either, because the one thing that changes with the pin
+   * is the way back, and that is a part inside the shadow tree where a
+   * stylesheet can already reach it. Measured rather than assumed: `label,
+   * pinned` after upgrade against `label` from the server.
    * - `threshold`: How near the bottom still counts as being at it, in pixels.
    *
    * A hook rather than a constant, because the right number depends on how tall
@@ -38130,7 +38119,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The turns, as `helix-chat-message` children.
+   * - `(default)`: The turns.
    * - `actions`: Beside the header: what can be done to the conversation itself.
    * - `composer`: Below the transcript, where the reader writes.
    * - `header`: Above the transcript: what this conversation is.
@@ -38600,11 +38589,11 @@ export type CustomElementsSolidJs = {
    * round. The platform already writes booleans like this for the same reason,
    * `novalidate` and `nomodule` and `noreferrer` among them.
    *
-   * **Reflected, because the gutter is a stylesheet rule.** `code-block.css`
-   * reserves the copy button's width with `:host(:not([no-copy]))`, so the
-   * attribute is what decides whether the block pays for a control. Unreflected,
-   * setting it from script takes the button away (`render` reads the property)
-   * and leaves the 40px it stood in reserved.
+   * **Reflected, because the gutter is a stylesheet rule.** A sheet reserves
+   * the copy button's width with `:host(:not([no-copy]))`, so the attribute is
+   * what decides whether the block pays for a control. Unreflected, setting it
+   * from script takes the button away (`render` reads the property) and leaves
+   * the 40px it stood in reserved.
    *
    * A false boolean reflects as the attribute's absence, so this costs no
    * `no-copy=""` on hosts that never asked for one, and the rule about a
@@ -38754,11 +38743,11 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * **The picker is `helix-color-picker`, not a second one written here.** It owns the
+   * **The picker is `ColorPicker`, not a second one written here.** It owns the
    * square, the ramps, the eyedropper and the syntax toggle, and it is worth
    * having on its own: a settings pane wants a picker flat on the page with
    * nothing to open. This element is the field, the overlay, and the form.
-   * Exactly the arrangement Date Input has with `helix-date-picker`.
+   * Exactly the arrangement Date Input has with `DatePicker`.
    *
    * **Typed as well as picked, and the typing is the reason this is not
    * `<input type="color">`.** The native control gives a free picker and takes
@@ -39119,10 +39108,10 @@ export type CustomElementsSolidJs = {
    *
    * **A color is exactly as requirable as a date**, which is the comparison
    * that settles it: this element extends `HelixFormElement`, carries `name`
-   * and reports its value, so a consumer writing
-   * `<helix-color-picker name="brand" required>` inside a form has every reason
-   * to expect the form to refuse an empty one. Its two siblings in the same
-   * composition position, Date Picker and Time Picker, both check it.
+   * and reports its value, so a consumer writing `<helix-headless-color-picker
+   * name="brand" required>` inside a form has every reason to expect the form
+   * to refuse an empty one. Its two siblings in the same composition position,
+   * Date Picker and Time Picker, both check it.
    *
    * Written out rather than taken from `MixinField`, for the reason those two
    * record: the mixin brings a label, a hint and a feedback region, and this is
@@ -39314,10 +39303,10 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * **The list is `helix-listbox`, and the filtering is its own.** It owns
-   * narrowing, the empty state, the highlight, `aria-activedescendant` and
-   * scrolling an option into view. What is left for this element is the field,
-   * the panel and the traffic between them.
+   * **The list is `Listbox`, and the filtering is its own.** It owns narrowing,
+   * the empty state, the highlight, `aria-activedescendant` and scrolling an
+   * option into view. What is left for this element is the field, the panel and
+   * the traffic between them.
    *
    * **The text and the value are two things.** What a reader types is a filter:
    * it narrows the list and is thrown away. The value is whichever option they
@@ -39488,7 +39477,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The options, which are `helix-option` elements.
+   * - `(default)`: The options.
    * - `end`: After it, for a unit or a clear button.
    * - `indicator`: Replaces the caret saying the field opens.
    * - `start`: Before the text, for an icon.
@@ -39602,12 +39591,11 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * **The list is `helix-listbox`, filtering and all.** Listbox already owns
-   * narrowing, the empty state, the highlight over what matched,
-   * `aria-activedescendant`, scrolling an option into view and the keyboard that
-   * moves between them. Its own note says a command palette is that list again
-   * with something different opening it, and this is that something: a dialog,
-   * and a key that summons it.
+   * **The list is `Listbox`, filtering and all.** Listbox already owns narrowing,
+   * the empty state, the highlight over what matched, `aria-activedescendant`,
+   * scrolling an option into view and the keyboard that moves between them. Its
+   * own note says a command palette is that list again with something different
+   * opening it, and this is that something: a dialog, and a key that summons it.
    *
    * **The value is not kept.** A palette runs a command and forgets it: nothing
    * here is a form control and nothing is submitted, so what it reports is that
@@ -39684,7 +39672,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The commands, which are `helix-option` elements and their groups.
+   * - `(default)`: The commands, and any groups of them.
    * - `footer`: Under the list, for the keys a reader can press.
    *
    * ## Methods
@@ -39774,7 +39762,7 @@ export type CustomElementsSolidJs = {
    * the same way `label` becomes `aria-label` in there.
    *
    * ```html
-   * <helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+   * <helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
    * ```
    *
    * `commandFor` spells its attribute out, because Lit lowercases a property
@@ -39973,19 +39961,19 @@ export type CustomElementsSolidJs = {
 
   /**
    * **The schema is markup and the data is a property.** Columns are declared as
-   * `helix-table-column` children, because a schema is small and something a
-   * reader should see in the HTML; rows are handed over as an array, because a
-   * table that draws ten thousand elements cannot window them.
+   * `TableColumn` children, because a schema is small and something a reader
+   * should see in the HTML; rows are handed over as an array, because a table
+   * that draws ten thousand elements cannot window them.
    *
    * ```html
-   * <helix-data-table .rows=${rows} sort="name:asc" page-size="20">
-   *   <helix-table-column field="name" sortable>Name</helix-table-column>
-   *   <helix-table-column field="size" align="end" sortable .cell=${bytes}>Size</helix-table-column>
-   * </helix-data-table>
+   * <helix-headless-data-table .rows=${rows} sort="name:asc" page-size="20">
+   *   <helix-headless-table-column field="name" sortable>Name</helix-headless-table-column>
+   *   <helix-headless-table-column field="size" align="end" sortable .cell=${bytes}>Size</helix-headless-table-column>
+   * </helix-headless-data-table>
    * ```
    *
-   * `helix-table` takes rows as markup and is the right component for a table of
-   * twelve things a person wrote out.
+   * `Table` takes rows as markup and is the right component for a table of twelve
+   * things a person wrote out.
    *
    * **Sort and filter apply to the whole set, never the page.** Sorting the drawn
    * window is correct on the first screen and wrong on every other one.
@@ -39994,7 +39982,7 @@ export type CustomElementsSolidJs = {
    * elements do, but reading a cell needs the columns, and the columns are markup
    * children Lit SSR does not hand this element. So a crawler sees a table of the
    * right shape with nothing in it. That is the cost of the first paragraph: use
-   * `helix-table` where the served HTML has to carry the values.
+   * `Table` where the served HTML has to carry the values.
    *
    * **`selectable` adds a column of checkboxes, keyed on `row-key`.** A row is
    * selected by its identity rather than its position, so a selection survives a
@@ -40015,14 +40003,13 @@ export type CustomElementsSolidJs = {
    * in the order on screen, in the columns on screen. Saving it is the page's
    * business, the same as any other file.
    *
-   * **There is no `columns` attribute here, and `helix-table` has one.** The
-   * difference is what a column is in each: here it is the schema, so a table
-   * without one has nothing to read a row with, and every column is a place to
-   * write a `width`. A `helix-table` holds cells a consumer wrote and can be
-   * written with no column at all, so its `columns` is where such a table is
-   * sized from. Written on this element the attribute is inert, which is the trap
-   * worth knowing when moving between the two. What both take is the CSS hook,
-   * `--data-table-columns` here and `--table-columns` there.
+   * **There is no `columns` attribute here, and Table has one.** The difference
+   * is what a column is in each: here it is the schema, so a table without one
+   * has nothing to read a row with, and every column is a place to write a
+   * `width`. A Table holds cells a consumer wrote and can be written with no
+   * column at all, so its `columns` is where such a table is sized from. Written
+   * on this element the attribute is inert, which is the trap worth knowing when
+   * moving between the two.
    *
    * ## Attributes & Properties
    *
@@ -40103,9 +40090,9 @@ export type CustomElementsSolidJs = {
    *
    * **It announces nothing, and that is not an omission.** Nothing in this
    * element ever asks for a different page size: a size selector is
-   * `helix-pagination-size`, which a consumer puts in the `footer` slot and
-   * answers themselves. Routing this through `requestChange` would announce an
-   * event the element never has cause to fire.
+   * `PaginationSize`, which a consumer puts in the `footer` slot and answers
+   * themselves. Routing this through `requestChange` would announce an event
+   * the element never has cause to fire.
    * - `total`: How many rows the whole result has, where this element cannot count them.
    *
    * Only read in `server` mode, where `rows` is one page and its length says
@@ -40192,7 +40179,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The columns, declared as `helix-table-column` children.
+   * - `(default)`: The columns, declared rather than drawn.
    * - `footer`: Below the grid, replacing the pagination this would otherwise draw.
    * - `toolbar`: Above the grid, for a search field or actions.
    *
@@ -40228,8 +40215,8 @@ export type CustomElementsSolidJs = {
    *
    * CSS variables available for styling the component.
    *
-   * - `--data-table-cell-align`: The edge the column a cell sits under is set to, `start`, `center` or `end`, and unset under a column that sets none. Written by the component onto each cell it draws, read by the sheet that paints one; `helix-table` publishes `--table-cell-align` for the same attribute on the cells a consumer wrote, under its own family's name. (default: `undefined`)
-   * - `--data-table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--data-table-columns` is the one to set. (default: `undefined`)
+   * - `--data-table-cell-align`: The edge the column a cell sits under is set to, `start`, `center` or `end`, and unset under a column that sets none. Written by the component onto each cell it draws, read by the sheet that paints one; Table publishes `--table-cell-align` for the same attribute on the cells a consumer wrote, under its own family's name. (default: `undefined`)
+   * - `--data-table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. A column's `width` is the one to set. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -40287,9 +40274,9 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * **The calendar is `helix-date-picker`, not a second one written here.** It
-   * already knows about months, ranges, disabled days, the first day of the week
-   * and every keyboard rule a grid owes a reader. This element is the field, the
+   * **The calendar is `DatePicker`, not a second one written here.** It already
+   * knows about months, ranges, disabled days, the first day of the week and
+   * every keyboard rule a grid owes a reader. This element is the field, the
    * overlay, and the translation between them.
    *
    * **Typed as well as picked, and the typing is why it is not
@@ -41406,8 +41393,8 @@ export type CustomElementsSolidJs = {
    * Opened declaratively with the platform's invoker attributes:
    *
    * ```html
-   * <helix-button commandfor="nav" command="--toggle">Menu</helix-button>
-   * <helix-drawer id="nav">…</helix-drawer>
+   * <helix-headless-button commandfor="nav" command="--toggle">Menu</helix-headless-button>
+   * <helix-headless-drawer id="nav">…</helix-headless-drawer>
    * ```
    *
    * ## Attributes & Properties
@@ -41438,10 +41425,10 @@ export type CustomElementsSolidJs = {
    * not, rather than shown or hidden by CSS.
    * - `placement`: Which edge the drawer comes from.
    *
-   * Unset is `end`, which the styled tier reads as `:host(:not([placement]))`
-   * beside `:host([placement="end"])` rather than as a value written here: a
+   * Unset is `end`, and it stays unset rather than being written down: a
    * default assigned to the property would reflect onto every host and put a
-   * `placement="end"` into markup no consumer wrote.
+   * `placement="end"` into markup no consumer wrote. So what this tier
+   * guarantees is the absence, and a sheet selects on it.
    * - `open`: Whether the element is open.
    *
    * One property, not two, so `dialog.open` answers the question anyone
@@ -42339,7 +42326,13 @@ export type CustomElementsSolidJs = {
    * - `fields`: The fields declared inside this, in the order they were written.
    *
    * What a render may know of them: none on a server, whose shim has no tree
-   * and threw here, and none while hydrating what one sent. (property only) (readonly)
+   * and threw here, and none while hydrating what one sent.
+   *
+   * By identity rather than by tag. A list of names can only hold the tags this
+   * package knows about, so it misses any third one, which is what subclassing
+   * a headless element produces, and it is also how a headless package learns a
+   * styled tag. `instanceof` answers for every one of them and proves the type
+   * the signature claims. (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
@@ -42578,12 +42571,12 @@ export type CustomElementsSolidJs = {
    * `FilterField` already plays on its own children.
    *
    * **It can suggest what to type next, and deciding what to suggest is still the
-   * consumer's.** Slot `helix-option` elements into `suggestions` and the field
-   * shows them, moves through them with the arrows, and lets Enter press one; the
-   * option fires its own `helix-select` and the consumer decides what choosing
-   * meant. Keys before a colon and values after it are the same panel with
-   * different contents, and `readFilterText` is exported for a consumer narrowing
-   * that panel against what a reader has half typed.
+   * consumer's.** Slot options into `suggestions` and the field shows them, moves
+   * through them with the arrows, and lets Enter press one; the option fires its
+   * own `helix-select` and the consumer decides what choosing meant. Keys before
+   * a colon and values after it are the same panel with different contents, and
+   * `readFilterText` is exported for a consumer narrowing that panel against what
+   * a reader has half typed.
    *
    * **The panel opens when there is something in it and closes when there is
    * not**, rather than on a choice. A reader who picks a key wants its values
@@ -42882,11 +42875,12 @@ export type CustomElementsSolidJs = {
    * would give.
    *
    * **The element's own text is read as a fallback, and only in a browser.**
-   * `<helix-format-date elapsed>2026-08-27T01:00:00Z</helix-format-date>` is the
-   * spelling that reads best in markup, and it cannot be the only one: measured
-   * against Lit's server shim, `textContent`, `children`, `firstChild` and
-   * `querySelector` are all `undefined` there, so a server has no way to see it.
-   * An element rendered on a server needs the attribute; one rendered in a
+   * `<helix-headless-format-date
+   * elapsed>2026-08-27T01:00:00Z</helix-headless-format-date>` is the spelling
+   * that reads best in markup, and it cannot be the only one: measured against
+   * Lit's server shim, `textContent`, `children`, `firstChild` and
+   * `querySelector` are all `undefined` there, so a server has no way to see
+   * it. An element rendered on a server needs the attribute; one rendered in a
    * browser may use either.
    * - `day`: How the day of the month is written, where a date is shown.
    * - `elapsed`: Show how long ago it was, compactly, instead of the date.
@@ -42987,12 +42981,12 @@ export type CustomElementsSolidJs = {
    * consumer has to keep by hand, and the one number a summary is told to trust
    * is the one it gets wrong.
    *
-   * The strip measures itself, so `--heatmap-cell-inline-size` and `--heatmap-gap` are
-   * enough on their own and these two are the estimate used until the first
-   * measurement lands. Writing the attribute pins the value and stops the
-   * measurement being consulted, which is what a container query or a transition
-   * on the cell size wants, where what is drawn this frame is not what the
-   * arithmetic should plan around.
+   * The strip measures itself, so sizing the cells in a sheet is enough on its
+   * own and these two are the estimate used until the first measurement lands.
+   * Writing the attribute pins the value and stops the measurement being
+   * consulted, which is what a container query or a transition on the cell size
+   * wants, where what is drawn this frame is not what the arithmetic should
+   * plan around.
    *
    * Zero turns the dropping off altogether, which is right for a strip in a
    * container that cannot get narrow.
@@ -43136,11 +43130,6 @@ export type CustomElementsSolidJs = {
    *
    * CSS variables available for styling the component.
    *
-   * - `--heatmap-cell-height`: How tall a cell is. A row of a tall thin cell is what a status page draws. (default: `undefined`)
-   * - `--heatmap-cell-inline-size`: How wide a cell is. The strip fits as many as the container allows. (default: `undefined`)
-   * - `--heatmap-cell-radius`: How far a cell's corners are rounded. (default: `undefined`)
-   * - `--heatmap-cell-size`: The size a cell wants on both axes, where neither is given its own. (default: `undefined`)
-   * - `--heatmap-gap`: Space between cells. Zero is a continuous field rather than a grid of tiles. (default: `undefined`)
    * - `--heatmap-rows`: How many rows the strip lays out. Written by the component from the data, read by the tier that draws it. (default: `undefined`)
    * - `--heatmap-tone`: The tone of the cell this is set on. Written by the component, read by the sheet that paints. (default: `undefined`)
    * - `--heatmap-tone-1`: The quietest step of the magnitude ramp, reached by `tones="1 …"`. (default: `undefined`)
@@ -43227,7 +43216,7 @@ export type CustomElementsSolidJs = {
    * the same way `label` becomes `aria-label` in there.
    *
    * ```html
-   * <helix-button commandfor="confirm" command="--show">Delete…</helix-button>
+   * <helix-headless-button commandfor="confirm" command="--show">Delete…</helix-headless-button>
    * ```
    *
    * `commandFor` spells its attribute out, because Lit lowercases a property
@@ -43548,10 +43537,10 @@ export type CustomElementsSolidJs = {
    * **Mirrored to `data-status`, and not reflected as `status`.** It is element
    * state, so reflecting it puts the element's own bookkeeping into the markup
    * a consumer rendered: React reads the attribute appearing at upgrade as a
-   * hydration mismatch, and a serialized `<helix-image status="loaded">` pasted
-   * back declares that a picture has arrived which this element has never
-   * fetched. The `data-` name is the library's answer to both, being a name a
-   * re-parse cannot mistake for a declaration, and it is what `data-closed` on
+   * hydration mismatch, and a host pasted back carrying `status="loaded"`
+   * declares that a picture has arrived which this element has never fetched.
+   * The `data-` name is the library's answer to both, being a name a re-parse
+   * cannot mistake for a declaration, and it is what `data-closed` on
    * `Toast.Item` already does. A picture arrives after somebody fetched it,
    * which puts this on the safe side of hydration: a fact that can be true on
    * the *first* update mirrors to a custom state instead, which is what
@@ -43667,10 +43656,10 @@ export type CustomElementsSolidJs = {
    * **The attribute is `readonly`, which is the platform's spelling.** A
    * camelCase property needs an explicit `attribute`, and dash-casing a word
    * HTML writes as one costs what an attribute always costs here: nothing
-   * warns. `<helix-input readonly>` is what anybody who has written HTML types;
-   * against `read-only` it parses to no property at all, and the field stays
-   * editable with no error anywhere. Measured on the dash-cased form, `readOnly`
-   * came back `false`.
+   * warns. `<helix-headless-input readonly>` is what anybody who has written
+   * HTML types; against `read-only` it parses to no property at all, and the
+   * field stays editable with no error anywhere. Measured on the dash-cased
+   * form, `readOnly` came back `false`.
    * - `reveal`: Whether a password field offers a toggle that shows what was typed.
    *
    * Ignored on every other type. A reveal on an email field would be a button
@@ -43684,9 +43673,9 @@ export type CustomElementsSolidJs = {
    *
    * **Not reflected.** Reflection exists so a selector can reach a value, and
    * no stylesheet in this repository selects on `type`. Reflecting it writes
-   * `type="text"` onto every `<helix-input>` ever rendered, an attribute no
-   * consumer's markup has, which is the fault the area rules write up under
-   * `Button`'s `href`, `target` and `rel`.
+   * `type="text"` onto every `<helix-headless-input>` ever rendered, an
+   * attribute no consumer's markup has, which is the fault the area rules write
+   * up under `Button`'s `href`, `target` and `rel`.
    *
    * Nothing reads it from the attribute either. The real `<input>` inside takes
    * it as a property binding, which is what makes the keyboard and the
@@ -44141,8 +44130,7 @@ export type CustomElementsSolidJs = {
    * over something busy. `triangle` points along the axis and reads as "and
    * onward" rather than as a second claim about the data.
    *
-   * The shapes come from
-   * `helix/styled/src/shared/chart/terminus.css`, the same sheet `Sparkline` takes, so
+   * The shapes come from one shared sheet, the same one `Sparkline` takes, so
    * the set is identical wherever one appears. **Which is why every value is
    * named here.** `Sparkline` shipped `square` implemented, drawn, asserted and
    * undocumented until the cohort before this one; this family reads the same
@@ -44413,10 +44401,10 @@ export type CustomElementsSolidJs = {
    * - `label`: Accessible name for the set.
    * - `type`: Which markers an ordered list draws, in `<ol type>`'s own five values.
    *
-   * Reflected, because this is one of the things a stylesheet selects on and
-   * the styled tier maps each to a `list-style-type`. The platform's spellings
-   * rather than the CSS ones, so `<helix-list kind="ordered" type="i">` is what
-   * a consumer would have written on an `<ol>`.
+   * Reflected, because this is one of the things a stylesheet selects on, each
+   * value mapping to a `list-style-type`. The platform's spellings rather than
+   * the CSS ones, so `<helix-headless-list kind="ordered" type="i">` is what a
+   * consumer would have written on an `<ol>`.
    *
    * **`start` and `reversed` are both absent and neither can be done here.**
    * This renders no `<ol>`: the rows are slotted and numbered by the CSS
@@ -45598,9 +45586,9 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * A notification is a toast that did not go away. `helix-toast` is deliberately
-   * the opposite of this: a live region whose items carry a `duration` and whose
-   * root never creates or destroys anything. What makes this its own family is the
+   * A notification is a toast that did not go away. `Toast` is deliberately the
+   * opposite of this: a live region whose items carry a `duration` and whose root
+   * never creates or destroys anything. What makes this its own family is the
    * state each item carries rather than the arrangement it sits in: read and
    * unread, a timestamp that has to stay correct, and an action a reader can take
    * later.
@@ -45612,9 +45600,9 @@ export type CustomElementsSolidJs = {
    * reader wants exactly one of them at a time: the time while they are scanning,
    * and what they can do about it once they have stopped on a row.
    *
-   * **The timestamp is `helix-format-date`**, which is where the reading, the
-   * `<time datetime>` and the shared timer now live. It was implemented here, and
-   * a component that formats a date is not a fact about notifications: Chat wanted
+   * **The timestamp is `FormatDate`**, which is where the reading, the `<time
+   * datetime>` and the shared timer now live. It was implemented here, and a
+   * component that formats a date is not a fact about notifications: Chat wanted
    * the same thing and had its own copy of half of it.
    *
    * **Read state is reported, not invented.** Marking something read is usually a
@@ -45640,10 +45628,10 @@ export type CustomElementsSolidJs = {
    *
    * **Not reflected.** Unread is a visual state, which is why the four mixins
    * mirror theirs, but the mirror may not be the property's own attribute:
-   * `<helix-notification default-read>` comes back from a server without `read`
-   * and would gain it on the first update, which React reports as a hydration
-   * mismatch, and which a copy of the serialized element re-parses as a
-   * declaration. `:state(read)` is what the stylesheet reads.
+   * `<helix-headless-notification default-read>` comes back from a server
+   * without `read` and would gain it on the first update, which React reports
+   * as a hydration mismatch, and which a copy of the serialized element
+   * re-parses as a 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.
    * - `locale`: Locale for the timestamp.
@@ -45836,7 +45824,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The notifications, as `helix-notification` children.
+   * - `(default)`: The notifications.
    * - `footer`: Below the list, for a link to everything.
    * - `header`: Above the list, for a title and the mark-all control.
    *
@@ -46430,7 +46418,7 @@ export type CustomElementsSolidJs = {
    * **The attribute, read when it is asked for, and never a snapshot taken in
    * the constructor.** A field initializer runs there, and an element the HTML
    * parser created has none of its attributes yet at that moment: measured on
-   * this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+   * this element, on `Radio` and on `Toggle`, `<helix-headless-option value="a"
    * selected>` reported `defaultSelected` as `false` both from parsed markup
    * and from `createElement` followed by `setAttribute`, which is every way a
    * consumer writes one. The snapshot could only ever be true for an element
@@ -46654,8 +46642,8 @@ export type CustomElementsSolidJs = {
   /**
    * **The component is the truncation.** Given a page and a total it works out
    * which numbers to show and where the runs break, so this is data-driven rather
-   * than composed: `<helix-pagination page="4" pages="12">` rather than twelve
-   * slotted children a consumer keeps in step with their own query.
+   * than composed: `<helix-headless-pagination page="4" pages="12">` rather than
+   * twelve slotted children a consumer keeps in step with their own query.
    *
    * **The width does not change as you page.** The run around the current page is
    * `siblings` either side, and grows to absorb a gap slot at a boundary, so the
@@ -47096,10 +47084,10 @@ export type CustomElementsSolidJs = {
    * marked letters wants `text`, which judges nothing.
    *
    * **Not reflected**: nothing selects on it, so reflecting only writes
-   * `type="numeric"` onto every `<helix-pin-input>` ever rendered, an attribute
-   * no consumer's markup had. The area rules carry the sentence "reflect only
-   * what CSS selects on". The real inputs take it as a binding, which is what
-   * makes the keyboard follow.
+   * `type="numeric"` onto every `<helix-headless-pin-input>` ever rendered, an
+   * attribute no consumer's markup had. The area rules carry the sentence
+   * "reflect only what CSS selects on". The real inputs take it as a binding,
+   * which is what makes the keyboard follow.
    * - `default-value`/`defaultValue`: The value the markup declared, which is where a reset returns to.
    * - `value`: What the control holds now, and what its form submits.
    *
@@ -47858,7 +47846,7 @@ export type CustomElementsSolidJs = {
    * **The attribute, read when it is asked for, and never a snapshot taken in
    * the constructor.** A field initializer runs there, and an element the HTML
    * parser created has none of its attributes yet at that moment: measured on
-   * this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+   * this element, on `Option` and on `Toggle`, `<helix-headless-radio value="a"
    * selected>` reported `defaultSelected` as `false` both from parsed markup
    * and from `createElement` followed by `setAttribute`, which is every way a
    * consumer writes one. The snapshot could only ever be true for an element
@@ -49331,11 +49319,10 @@ export type CustomElementsSolidJs = {
    * mean defining what a dial with a submenu in it does.
    *
    * **The trigger is a control the consumer slots**, and the floating action
-   * button is the usual one: `helix-icon-button` with `shape="circle"` and
-   * `raised`. There is no `helix-fab`, because it would re-declare `emphasis`,
-   * `tone`, `label` and a size around a control that already has all four. A
-   * round raised button is a shape, and where it sits is `data-dock` in the base
-   * layer.
+   * button is the usual one: `IconButton` with `shape="circle"` and `raised`.
+   * There is no `helix-fab`, because it would re-declare `emphasis`, `tone`,
+   * `label` and a size around a control that already has all four. A round raised
+   * button is a shape, and where it sits is `data-dock` in the base layer.
    *
    * **Nothing is reserved from the keyboard.** A menu that drills has to keep the
    * horizontal pair for going in and coming back; a dial goes nowhere, so all four
@@ -49703,9 +49690,9 @@ export type CustomElementsSolidJs = {
    * The row directions set them side by side, for a figure in a line of text or
    * a narrow strip where a stacked pair would be two lines of almost nothing.
    *
-   * A property rather than a `helix-flex` around it, because the unit has to
-   * stay on the value's baseline whichever way the pair goes, and only this
-   * element knows which of its children the unit belongs to.
+   * A property rather than a `Flex` around it, because the unit has to stay on
+   * the value's baseline whichever way the pair goes, and only this element
+   * knows which of its children the unit belongs to.
    *
    * **Optional rather than defaulted to `column`, which is not a style
    * preference.** A reflecting property with a default writes its attribute onto
@@ -49841,7 +49828,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The steps, which are `helix-step` elements.
+   * - `(default)`: The steps.
    *
    * ## Methods
    *
@@ -49871,9 +49858,9 @@ export type CustomElementsSolidJs = {
 
   /**
    * **The name is a button, and only the name.** The marker is `aria-hidden`
-   * decoration, so wrapping it would add hit area and no meaning. It is
-   * `helix-button` rather than a `<button>` this element resets: the hover wash,
-   * the focus ring and the disabled treatment are decisions the button carries.
+   * decoration, so wrapping it would add hit area and no meaning. It is `Button`
+   * rather than a `<button>` this element resets: the hover wash, the focus ring
+   * and the disabled treatment are decisions the button carries.
    *
    * **It says nothing about where a reader may go.** Every step is pressable and
    * announces itself with `helix-select`; refusing the ones ahead is `disabled`,
@@ -49926,7 +49913,7 @@ export type CustomElementsSolidJs = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The step's name.
-   * - `content`: What the stage holds. Always rendered here, a tier with no stylesheet having nothing to fold it with; the styled tier opens it on the current step down a column, and a row has no space under a step to open it into.
+   * - `content`: What the stage holds. Always rendered here, a tier with no stylesheet having nothing to fold it with, so whether it is folded away is the sheet's answer and not this tier's.
    * - `description`: A line under the name, for what the stage is for.
    * - `marker`: Replaces the number, or the check a complete step shows.
    *
@@ -49943,7 +49930,7 @@ export type CustomElementsSolidJs = {
    * - `body`: The name and its description.
    * - `content`: What the stage holds, while it is open.
    * - `description`: The line under it.
-   * - `label`: The step's name, which is a `helix-button`.
+   * - `label`: The step's name, which is a control.
    * - `label-button`: The inner control.
    * - `lead`: The half line arriving from the step before.
    * - `mark`: The glyph inside the marker: a tick, a dot, or an empty ring.
@@ -50212,23 +50199,23 @@ export type CustomElementsSolidJs = {
    * the table has another track; remove one and it does not. That is what ties
    * the two together, and a table-level track list on its own does not: a list
    * that is accidentally the headings is invalid CSS a grid ignores in silence,
-   * drawing the whole table as one column. `helix-table`'s `columns` is dealt out
-   * a track at a time against the columns declared under it, so a heading among
-   * the widths costs its own column a width and no more, and a list longer or
-   * shorter than the columns is trimmed or shared rather than being a second
-   * count of them. A column's own `width` wins over the track in its place.
+   * drawing the whole table as one column. `Table`'s `columns` is dealt out a
+   * track at a time against the columns declared under it, so a heading among the
+   * widths costs its own column a width and no more, and a list longer or shorter
+   * than the columns is trimmed or shared rather than being a second count of
+   * them. A column's own `width` wins over the track in its place.
    *
    * **It is also where every per-column fact goes**, which is the reason
-   * `helix-data-table` needs no column config object. `field` names the key the
-   * cell reads, `sortable` says a reader may reorder by it, `align` says which
-   * edge the values line up against, and `cell` takes a function for anything the
+   * `DataTable` needs no column config object. `field` names the key the cell
+   * reads, `sortable` says a reader may reorder by it, `align` says which edge
+   * the values line up against, and `cell` takes a function for anything the
    * field alone cannot express. The schema is markup and the data is a property:
    * a schema is small, declarative, and something a reader should be able to see
    * in the HTML, and data is large and windowed.
    *
    * **The same element serves both tables**, the markup one and the data one. It
-   * is identified by a flag rather than by `instanceof`, so a `helix-table-column`
-   * works inside either without the two roots sharing anything else.
+   * is identified by a flag rather than by `instanceof`, so a `TableColumn` works
+   * inside either without the two roots sharing anything else.
    *
    * **It generates no box of its own**, the same as a row: the heading is a grid
    * item of the table, so it lines up with the cells under it rather than sitting
@@ -50238,10 +50225,10 @@ export type CustomElementsSolidJs = {
    * both, so the columns after it keep their own widths and every row keeps its
    * cells under their headings. `hidden="until-found"` keeps its track, the
    * heading being left drawn, as every Helix element leaves one with that value.
-   * `helix-data-table` draws the cells, so it leaves out the ones under a hidden
-   * column. A `helix-table`'s cells are markup the consumer wrote, so hide them
-   * with the column, as removing a column means removing its cells: a row with a
-   * cell more than the table has tracks wraps into the next.
+   * `DataTable` draws the cells, so it leaves out the ones under a hidden column.
+   * A `Table`'s cells are markup the consumer wrote, so hide them with the
+   * column, as removing a column means removing its cells: a row with a cell more
+   * than the table has tracks wraps into the next.
    *
    * **A heading that does something holds a control that does it.** The host is
    * the column header, and a header is not focusable, so a sortable heading is a
@@ -50257,15 +50244,15 @@ export type CustomElementsSolidJs = {
    *
    * - `align`: Which edge the values line up against.
    *
-   * `end` is what a column of numbers wants, so digits of the same magnitude sit
-   * above each other. Left unset the cell inherits the table's own alignment,
-   * which is `start` for text in either writing direction. `helix-data-table`
-   * aligns the cells it draws. A `helix-table`'s cells are markup the consumer
-   * wrote, so the table writes nothing onto them: it publishes the edge to each
-   * cell under this column as `--table-cell-align`, which `@fusion.dev/helix`
-   * reads. The heading is this element's own, and `@fusion.dev/helix` sets it to
-   * the same edge in either table. `end` is the inline end, so in a
-   * right-to-left table it is the left.
+   * `end` is what a column of numbers wants, so digits of the same magnitude
+   * sit above each other. Left unset the cell inherits the table's own
+   * alignment, which is `start` for text in either writing direction.
+   * `DataTable` aligns the cells it draws. A `Table`'s cells are markup the
+   * consumer wrote, so the table writes nothing onto them: it publishes the
+   * edge to each cell under this column as `--table-cell-align`, which
+   * `@fusion.dev/helix` reads. The heading is this element's own, and
+   * `@fusion.dev/helix` sets it to the same edge in either table. `end` is the
+   * inline end, so in a right-to-left table it is the left.
    *
    * **Reflected, because the heading is drawn by a stylesheet and has no other
    * way to learn it.** Set as a property, which is how React sets it, an
@@ -50308,8 +50295,8 @@ export type CustomElementsSolidJs = {
    * - `width`: The track this column takes, as CSS.
    *
    * A single track value, so anything valid in `grid-template-columns` works:
-   * `16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track
-   * in its place in a `helix-table`'s `columns`, where that table sets one, and
+   * `16rem`, `auto`, `minmax(0, 2fr)`. Left unset the column takes the track in
+   * its place in a `Table`'s `columns`, where that table sets one, and
    * otherwise shares what is left over equally, as `minmax(max-content, 1fr)`.
    * Set here, it wins over that list, which is what lets a reader resize a
    * column in a table that set one.
@@ -50435,15 +50422,14 @@ export type CustomElementsSolidJs = {
    *
    * - `columns`: The column widths as one track list, written once on the table.
    *
-   * With `helix-table-column` children, each track sizes the column in its
-   * place, a hidden column counted, so hiding one takes its track with it and
-   * the rest keep theirs. The columns decide how many tracks there are and this
-   * list only how wide: a track past the last column is dropped, and a column
-   * past the last track shares what is left. With no columns declared it is
-   * the whole track list. Tracks count as the grid counts them, so
-   * `minmax(0, 1fr)` is one and `repeat(2, 8rem)` is two, and one the grid
-   * would refuse leaves its column at the default rather than taking the table
-   * down to one column.
+   * With `TableColumn` children, each track sizes the column in its place, a
+   * hidden column counted, so hiding one takes its track with it and the rest
+   * keep theirs. The columns decide how many tracks there are and this list
+   * only how wide: a track past the last column is dropped, and a column past
+   * the last track shares what is left. With no columns declared it is the
+   * whole track list. Tracks count as the grid counts them, so `minmax(0, 1fr)`
+   * is one and `repeat(2, 8rem)` is two, and one the grid would refuse leaves
+   * its column at the default rather than taking the table down to one column.
    *
    * **A column's own `width` wins over its track here.** The width is written
    * on the column it sizes, which is the more particular statement, and it is
@@ -50457,13 +50443,11 @@ export type CustomElementsSolidJs = {
    * whole answer: a table given one lays its grid out in the first paint, and a
    * table sized only by its columns is one track wide until it upgrades.
    *
-   * **`helix-data-table` has none of this, and should not.** Its columns are
-   * its schema rather than an option, so there is always a column to write a
-   * `width` on and a list here would be a second way to say what that says.
-   * This table's cells are markup, and a table written as rows of cells with no
-   * `helix-table-column` in it has nowhere else to be sized from. Both families
-   * take the same CSS hook, `--table-columns` and `--data-table-columns`, which
-   * wins over whichever list the element worked out.
+   * **Data Table has none of this, and should not.** Its columns are its schema
+   * rather than an option, so there is always a column to write a `width` on
+   * and a list here would be a second way to say what that says. This table's
+   * cells are markup, and a table written as rows of cells with no column
+   * declared in it has nowhere else to be sized from.
    * - `label`: Accessible name for the table.
    * - `empty-text`/`emptyText`: What is said where there are none, and none are coming.
    * - `loading`: Whether the rows are still on their way.
@@ -50504,7 +50488,7 @@ export type CustomElementsSolidJs = {
    *
    * CSS variables available for styling the component.
    *
-   * - `--table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--table-columns` is the one to set. (default: `undefined`)
+   * - `--table-template`: The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `columns` is the one to set. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -50529,10 +50513,10 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * `display: contents` in the styled tier, so the row's cells become items of
-   * the table's own grid and every column lines up across every row. The row
-   * still exists as an element, which is what a `<table>` gives away when its
-   * cells are laid out by the table algorithm.
+   * The row renders its cells straight through and lays out none of them, so a
+   * sheet can take them into the table's own grid and every column lines up
+   * across every row. The row still exists as an element, which is what a
+   * `<table>` gives away when its cells are laid out by the table algorithm.
    *
    * ## Attributes & Properties
    *
@@ -51151,10 +51135,10 @@ export type CustomElementsSolidJs = {
   >;
 
   /**
-   * **The list is `helix-time-picker`, not a second one written here.** It is worth
+   * **The list is `TimePicker`, not a second one written here.** It is worth
    * having on its own, flat in a settings pane with nothing to open, and this
    * element is the field, the overlay and the form. Exactly the arrangement Input
-   * Date has with `helix-date-picker` and Color Input with `helix-color-picker`.
+   * Date has with `DatePicker` and Color Input with `ColorPicker`.
    *
    * **Typed as well as picked, and that is the division the list depends on.** A
    * list at a step offers the times a product actually has, and the field is how a
@@ -51185,8 +51169,8 @@ export type CustomElementsSolidJs = {
    *
    * Absent is one. `range` holds a start and an end, `multiple` holds any
    * number, and both are carried as one comma-separated value, which is what a
-   * form submits. `helix-time-picker` carries the longer note on the interaction and on
-   * why a wheel cannot do either.
+   * form submits. `TimePicker` carries the longer note on the interaction and
+   * on why a wheel cannot do either.
    * - `placeholder`: What the field says before a time is in it.
    * - `step`: How far apart the offered times are, in minutes.
    * - `time-style`/`timeStyle`: Whether the field writes the time out, or holds the value as it is.
@@ -51201,7 +51185,7 @@ export type CustomElementsSolidJs = {
    * `list` offers whole times, which is what a product with slots or opening
    * hours has. `wheels` splits them into an hour, a minute and a meridiem where
    * the locale uses one, which is the only way to reach `23:45` without
-   * scrolling most of a day. `helix-time-picker` carries the longer note on the trade.
+   * scrolling most of a day. `TimePicker` carries the longer note on the trade.
    *
    * **Optional rather than defaulted, which is not a style preference.** A
    * reflecting property with a default writes its attribute onto every host the
@@ -51448,8 +51432,8 @@ export type CustomElementsSolidJs = {
 
   /**
    * **A list rather than three wheels**, and the reason is what a list already
-   * is. `helix-listbox` brings the keyboard, the typeahead, the scroll into view
-   * and the announcement of a set of options, and a time at a step is a set of
+   * is. `Listbox` brings the keyboard, the typeahead, the scroll into view and
+   * the announcement of a set of options, and a time at a step is a set of
    * options. Three little wheels for hours, minutes and a meridiem are three
    * controls to build, three to test, and a tab stop each for something a reader
    * answers once.
@@ -51510,7 +51494,7 @@ export type CustomElementsSolidJs = {
    *
    * Absent is one. `range` holds a start and an end with everything between
    * them shown as part of the answer, `multiple` holds any number, and both are
-   * carried as one comma-separated value: the same shape `helix-date-picker` uses,
+   * carried as one comma-separated value: the same shape `DatePicker` uses,
    * because it is the same question asked of a different unit.
    *
    * **A range is two picks, and a third starts over.** That is the calendar's
@@ -52067,7 +52051,7 @@ export type CustomElementsSolidJs = {
    * **Optional, and bottom-end is the absence of it.** Reflecting *and*
    * defaulting is the pair that writes onto a host: every toast region anybody
    * rendered would gain a `placement="bottom-end"` nobody typed, which a React
-   * consumer's server markup does not have. The styled sheet carries the resting
+   * consumer's server markup does not have. A sheet carries the resting
    * arrangement in its own `:host` rule and the selectors describe only the
    * departures, which is what `orientation` does.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -52101,7 +52085,7 @@ export type CustomElementsSolidJs = {
    *
    * Areas where markup can be added to the component.
    *
-   * - `(default)`: The messages, as `helix-toast-item` elements.
+   * - `(default)`: The messages.
    *
    * ## CSS Parts
    *
@@ -52335,11 +52319,11 @@ export type CustomElementsSolidJs = {
    * **The attribute, read when it is asked for, and never a snapshot taken in
    * the constructor.** A field initializer runs there, and an element the HTML
    * parser created has none of its attributes yet at that moment: measured on
-   * this element, on `Option` and on `Radio`, `<helix-toggle value="light"
-   * selected>` reported `defaultSelected` as `false` both from parsed markup
-   * and from `createElement` followed by `setAttribute`, which is every way a
-   * consumer writes one. The snapshot could only ever be true for an element
-   * already in the document when `customElements.define` ran.
+   * this element, on `Option` and on `Radio`, `<helix-headless-toggle
+   * value="light" selected>` reported `defaultSelected` as `false` both from
+   * parsed markup and from `createElement` followed by `setAttribute`, which is
+   * every way a consumer writes one. The snapshot could only ever be true for
+   * an element already in the document when `customElements.define` ran.
    *
    * Nothing overwrites it either, which is what makes reading it late correct
    * rather than merely later: `selected` does not reflect, for the reason
@@ -52501,8 +52485,8 @@ export type CustomElementsSolidJs = {
    * the ordinary way:
    *
    * ```html
-   * <helix-button id="save" aria-describedby="save-tip">Save</helix-button>
-   * <helix-tooltip id="save-tip" for="save" content="Save your work"></helix-tooltip>
+   * <helix-headless-button id="save" aria-describedby="save-tip">Save</helix-headless-button>
+   * <helix-headless-tooltip id="save-tip" for="save" content="Save your work"></helix-headless-tooltip>
    * ```
    *
    * The reference points at *this host*, not at the bubble in its shadow root:
@@ -52817,9 +52801,9 @@ export type CustomElementsSolidJs = {
    * - **When it shows.** Which is `current`, and which the root decides.
    *
    * What it does not own is the heading, the paragraph, the picture and the
-   * layout. Slot a `helix-card`, or a heading and a line of prose, or anything
-   * else. Fixed `title` and `body` parts would be a component deciding what a
-   * tour is allowed to say.
+   * layout. Slot a `Card`, or a heading and a line of prose, or anything else.
+   * Fixed `title` and `body` parts would be a component deciding what a tour is
+   * allowed to say.
    *
    * **The buttons are slot fallback, so the common case costs nothing and the
    * uncommon one is possible.** Write nothing and get Back, Next and Skip already
@@ -53580,7 +53564,7 @@ export type CustomElementsSolidJs = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The entries.
-   * - `player`: The `helix-video` they play in.
+   * - `player`: The player the entries take turns in.
    *
    * ## Methods
    *
@@ -53997,7 +53981,7 @@ export type CustomElementsSolidJs = {
 export type CustomCssProperties = {
   /** How wide an axis column is drawn, in `ch`, from the widest number on it. Written on the axis itself, and only where the categories run along the bottom: turned sideways an axis is a row and takes a line's height instead. */
   "--bar-chart-axis"?: (string) | undefined;
-  /** The color of the secondary axis when one series owns it. It resolves a `--helix-color-series-*` token, so on the headless tier alone it names something that is not there. #138. */
+  /** The color of the secondary axis, where one series owns it. Written by the component from that series' `--chart-series-*`, so it promises the series color and nothing more: whatever that hook resolves to is what the axis is drawn in. */
   "--bar-chart-secondary"?: (string) | undefined;
   /** The gradient a bar would take, named per bar so the styled tier can point `fill` at it. Drawn whatever the treatment and used only where `wash="gradient"` asks for it. */
   "--chart-bar-wash"?: (string) | undefined;
@@ -54021,24 +54005,14 @@ export type CustomCssProperties = {
   "--color-picker-saturation"?: (string) | undefined;
   /** A color to paint: the current one on the sample, a preset's on each preset. */
   "--color-picker-swatch"?: (string) | undefined;
-  /** The edge the column a cell sits under is set to, `start`, `center` or `end`, and unset under a column that sets none. Written by the component onto each cell it draws, read by the sheet that paints one; `helix-table` publishes `--table-cell-align` for the same attribute on the cells a consumer wrote, under its own family's name. */
+  /** The edge the column a cell sits under is set to, `start`, `center` or `end`, and unset under a column that sets none. Written by the component onto each cell it draws, read by the sheet that paints one; Table publishes `--table-cell-align` for the same attribute on the cells a consumer wrote, under its own family's name. */
   "--data-table-cell-align"?: (string) | undefined;
-  /** The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--data-table-columns` is the one to set. */
+  /** The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. A column's `width` is the one to set. */
   "--data-table-template"?: (string) | undefined;
   /** How many month columns are drawn, capped at two. `--date-picker-columns` overrides it. */
   "--date-picker-column-count"?: (string) | undefined;
   /** How thick the ring is drawn, derived from `hole`. */
   "--donut-chart-stroke"?: (string) | undefined;
-  /** How tall a cell is. A row of a tall thin cell is what a status page draws. */
-  "--heatmap-cell-height"?: (string) | undefined;
-  /** How wide a cell is. The strip fits as many as the container allows. */
-  "--heatmap-cell-inline-size"?: (string) | undefined;
-  /** How far a cell's corners are rounded. */
-  "--heatmap-cell-radius"?: (string) | undefined;
-  /** The size a cell wants on both axes, where neither is given its own. */
-  "--heatmap-cell-size"?: (string) | undefined;
-  /** Space between cells. Zero is a continuous field rather than a grid of tiles. */
-  "--heatmap-gap"?: (string) | undefined;
   /** How many rows the strip lays out. Written by the component from the data, read by the tier that draws it. */
   "--heatmap-rows"?: (string) | undefined;
   /** The tone of the cell this is set on. Written by the component, read by the sheet that paints. */
@@ -54113,7 +54087,7 @@ export type CustomCssProperties = {
   "--splitter-position"?: (string) | undefined;
   /** The edge the column this cell sits under is set to, `start`, `center` or `end`, and unset under a column that sets none. Written by the table around it, since the cell is the consumer's markup and nothing is written onto it; read by the sheet that draws the cell, where `justify-content` and `text-align` both take it as it comes and both follow the writing direction. */
   "--table-cell-align"?: (string) | undefined;
-  /** The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `--table-columns` is the one to set. */
+  /** The column track list this element worked out from the columns declared in it. Written by the component, read by the sheet that paints: a stylesheet takes it to lay the grid out, and setting it does nothing, because the component writes it inline on the very element that reads it and an inline declaration beats any sheet. `columns` is the one to set. */
   "--table-template"?: (string) | undefined;
   /** How long this message stays, in milliseconds, for a progress hint. */
   "--toast-duration"?: (string) | undefined;