@fusion.dev/helix 0.53.1 → 0.53.2

package/types/vue.d.ts

@@ -660,13 +660,13 @@ export type HelixAvatarGroupVueProps = {
 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
@@ -968,12 +968,12 @@ export type HelixBreadcrumbVueProps = {
   current?: (HelixBreadcrumb["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
@@ -1092,7 +1092,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
@@ -1549,13 +1549,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
@@ -1580,8 +1580,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
@@ -1609,13 +1609,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
@@ -1640,8 +1640,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
@@ -1835,13 +1835,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?: (HelixChat["pinned"]) | undefined;
   /** How near the bottom still counts as being at it, in pixels.
 
@@ -2034,11 +2034,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
@@ -2054,11 +2054,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
@@ -2364,10 +2364,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
@@ -2741,7 +2741,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
@@ -3030,17 +3030,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"?: (HelixDataTable["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?: (HelixDataTable["pageSize"]) | undefined;
   /** How many rows the whole result has, where this element cannot count them.
 
@@ -3888,10 +3888,10 @@ not, rather than shown or hidden by CSS. */
   modal?: (HelixDrawer["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?: (HelixDrawer["placement"]) | undefined;
   /** What the dialog closed with, the way `<dialog>` reports it.
 
@@ -4419,11 +4419,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?: (HelixFormatDate["date"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
@@ -4524,12 +4525,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. */
@@ -4542,12 +4543,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. */
@@ -4640,7 +4641,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
@@ -4875,10 +4876,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
@@ -4961,20 +4962,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?: (HelixInput["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?: (HelixInput["readOnly"]) | undefined;
   /** Whether a password field offers a toggle that shows what was typed.
 
@@ -4995,9 +4996,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
@@ -5310,8 +5311,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
@@ -5395,10 +5395,10 @@ has to survive with the stylesheet turned off.
   label?: (HelixList["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
@@ -6066,10 +6066,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?: (HelixNotification["read"]) | undefined;
   /** State to open with, where nothing declared one. */
@@ -6433,7 +6433,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
@@ -6822,10 +6822,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?: (HelixPinInput["type"]) | undefined;
   /** Whether the control is non-interactive.
 
@@ -7213,7 +7213,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
@@ -8412,9 +8412,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
@@ -8605,15 +8605,15 @@ export type HelixTableColumnHelixBeforeResizeElementEvent =
 export type HelixTableColumnVueProps = {
   /** 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
@@ -8660,8 +8660,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.
@@ -8721,15 +8721,14 @@ say that without the component knowing what a row looks like. */
   loadingText?: (HelixTable["loadingText"]) | undefined;
   /** 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
@@ -8743,13 +8742,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?: (HelixTable["columns"]) | undefined;
   /** Accessible name for the table. */
   label?: (HelixTable["label"]) | undefined;
@@ -9219,8 +9216,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?: (HelixTimeInput["mode"]) | undefined;
   /** What the field says before a time is in it. */
   placeholder?: (HelixTimeInput["placeholder"]) | undefined;
@@ -9249,7 +9246,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
@@ -9376,7 +9373,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
@@ -9586,7 +9583,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?: (HelixToast["placement"]) | undefined;
@@ -9734,11 +9731,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
@@ -10761,7 +10758,7 @@ export type CustomCssProperties = {
   "--bar-chart-line-width"?: (string) | undefined;
   /** 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;
@@ -10985,9 +10982,9 @@ export type CustomCssProperties = {
   "--data-table-rule-color"?: (string) | undefined;
   /** Type size, headings and cells alike. */
   "--data-table-text"?: (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;
   /** Fill behind the field. */
   "--date-input-background-color"?: (string) | undefined;
@@ -11591,7 +11588,7 @@ export type CustomCssProperties = {
   "--table-cell-align"?: (string) | undefined;
   /** Track list for the columns, which wins over the one the columns worked out. */
   "--table-columns"?: (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;
   /** Fill behind the tag. */
   "--tag-background-color"?: (string) | undefined;