@fusion.dev/helix 0.40.0 → 0.41.1

package/types/jsx.d.ts

@@ -937,9 +937,13 @@ words and is already written. */
   label?: (HelixAreaChart["label"]) | undefined;
   /** How a band's edge gets from one reading to the next.
 
-Absent is `straight`, for the reason the class doc gives, and absent rather
-than defaulted because a reflecting property with a default writes its
-attribute onto every host, including the ones nobody configured. */
+Three values, and the class doc argues for each: `straight` is absent and
+is the default, `smooth` is for a stack read as a shape and is the one that
+can draw a part as less than nothing, `step` is for a quantity that changes
+at a moment and is ordered the way `straight` is.
+
+Absent rather than defaulted because a reflecting property with a default
+writes its attribute onto every host, including the ones nobody configured. */
   curve?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -976,9 +980,13 @@ words and is already written. */
   "prop:label"?: (HelixAreaChart["label"]) | undefined;
   /** How a band's edge gets from one reading to the next.
 
-Absent is `straight`, for the reason the class doc gives, and absent rather
-than defaulted because a reflecting property with a default writes its
-attribute onto every host, including the ones nobody configured. */
+Three values, and the class doc argues for each: `straight` is absent and
+is the default, `smooth` is for a stack read as a shape and is the one that
+can draw a part as less than nothing, `step` is for a quantity that changes
+at a moment and is ordered the way `straight` is.
+
+Absent rather than defaulted because a reflecting property with a default
+writes its attribute onto every host, including the ones nobody configured. */
   "prop:curve"?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -1411,6 +1419,12 @@ The chart's treatment, which every series takes unless `outlined` or
 of the series color with that edge on it, and absent is the filled column,
 per the rule that a reflected property takes no default.
 
+`solid` is that filled column written out. It matches no rule in the sheet
+and lands on the base one, which is what the resting value of every axis in
+the registry does, and it is worth having so a consumer switching a chart
+between treatments has a word for the one it started at rather than having
+to remove the attribute.
+
 **It composes with `material` rather than competing with it.** Emphasis
 decides what is drawn and material decides how much of it comes through, so
 `glass` thins whatever emphasis put there: the fill on a solid column, the
@@ -1467,10 +1481,15 @@ having the datum rather than by painting it invisibly. */
   material?: (HelixBarChart["material"]) | undefined;
   /** Which series are drawn as an outline rather than a fill, by name.
 
-Space separated and matched against the column headings the table gives,
-the way `lines` and `secondary` are, so a chart says `outlined="Forecast"`
-rather than counting columns. Names because they are what the table already
-carries and what the legend already shows.
+Separated by whitespace or commas and matched against the column headings
+the table gives, the way `lines` and `secondary` are, so a chart says
+`outlined="Forecast"` rather than counting columns. Names because they are
+what the table already carries and what the legend already shows.
+
+All five read one splitter, `seriesNames` in `core`, because the sentence
+above was true of the matching and false of the splitting: these three took
+a comma and those two did not, so `lines="Gateway, Billing"` drew no line
+and said nothing.
 
 **The case this exists for is a series that is not a measurement.** A
 forecast, a target, a budget: something drawn on the same axis as the
@@ -1539,28 +1558,38 @@ and reach no reader through the table. */
   gridlines?: (HelixBarChart["gridlines"]) | undefined;
   /** Which series are drawn as a line instead of as columns, by name.
 
-Space separated, matched against the column headings the table gives, so a
-chart says `lines="Margin"` rather than counting columns. Names because
-they are what the table already carries and what the legend already shows:
-an index is a fourth place the column order is written down and the first
-one to go stale when somebody moves a column.
-
-**A combination chart is one scale, and that is the honest half of it.**
-Both marks are measured against the same domain, so a line here says
-something comparable to the columns beside it. The usual reason to reach
-for a combination chart is the other thing, a count against a percentage on
-a second axis, and that is deliberately not this: two scales on one frame
-let the author put any two shapes in any relation by choosing the ranges,
-and the reader has no way to see it happening.
-
-A line among columns still measures from zero, because the columns do and
-they share the axis. */
+Separated by whitespace or commas and matched against the column headings
+the table gives, so a chart says `lines="Margin"` rather than counting
+columns. Names because they are what the table already carries and what the
+legend already shows: an index is a fourth place the column order is
+written down and the first one to go stale when somebody moves a column.
+
+**This says which mark a series takes and nothing about which scale it is
+measured on.** Named here alone, a line shares the columns' domain, so it
+says something comparable to the columns beside it.
+
+The other half of a combination chart, a count against a percentage on a
+scale of its own, is `secondary`, which is a separate property because it
+is a separate question and because the two compose: `with-a-second-axis`
+ships naming one series in both. The argument for why a second scale is opt
+in, and why setting it labels both axes, is written there.
+
+A line among columns measures from zero, because the columns do and they
+share the axis. So does a line on the second scale, which is that scale's
+own rule rather than this one's. */
   lines?: (HelixBarChart["lines"]) | undefined;
   /** Which series are measured against a scale of their own, by name.
 
-Space separated and matched the way `lines` is, against the column headings
-the table gives. Opt in: absent, every series shares one domain, which is
-what makes a chart comparable and is the right default.
+Separated and matched the way `lines` is, against the column headings the
+table gives. Opt in: absent, every series shares one domain, which is what
+makes a chart comparable and is the right default.
+
+**The scale, and `lines` is the mark.** The two are separate properties
+because they answer separate questions and a series usually wants both:
+a percentage beside a count is drawn as a line *and* measured on its own
+axis, which is what `with-a-second-axis` writes out. Neither implies the
+other, so a series can be a line on the shared scale and a column can have
+a scale to itself.
 
 **Two scales on one frame let an author put any two shapes in any relation
 by choosing the ranges, and a reader cannot see it happening.** That is not
@@ -1592,6 +1621,12 @@ The chart's treatment, which every series takes unless `outlined` or
 of the series color with that edge on it, and absent is the filled column,
 per the rule that a reflected property takes no default.
 
+`solid` is that filled column written out. It matches no rule in the sheet
+and lands on the base one, which is what the resting value of every axis in
+the registry does, and it is worth having so a consumer switching a chart
+between treatments has a word for the one it started at rather than having
+to remove the attribute.
+
 **It composes with `material` rather than competing with it.** Emphasis
 decides what is drawn and material decides how much of it comes through, so
 `glass` thins whatever emphasis put there: the fill on a solid column, the
@@ -1648,10 +1683,15 @@ having the datum rather than by painting it invisibly. */
   "prop:material"?: (HelixBarChart["material"]) | undefined;
   /** Which series are drawn as an outline rather than a fill, by name.
 
-Space separated and matched against the column headings the table gives,
-the way `lines` and `secondary` are, so a chart says `outlined="Forecast"`
-rather than counting columns. Names because they are what the table already
-carries and what the legend already shows.
+Separated by whitespace or commas and matched against the column headings
+the table gives, the way `lines` and `secondary` are, so a chart says
+`outlined="Forecast"` rather than counting columns. Names because they are
+what the table already carries and what the legend already shows.
+
+All five read one splitter, `seriesNames` in `core`, because the sentence
+above was true of the matching and false of the splitting: these three took
+a comma and those two did not, so `lines="Gateway, Billing"` drew no line
+and said nothing.
 
 **The case this exists for is a series that is not a measurement.** A
 forecast, a target, a budget: something drawn on the same axis as the
@@ -1720,28 +1760,38 @@ and reach no reader through the table. */
   "prop:gridlines"?: (HelixBarChart["gridlines"]) | undefined;
   /** Which series are drawn as a line instead of as columns, by name.
 
-Space separated, matched against the column headings the table gives, so a
-chart says `lines="Margin"` rather than counting columns. Names because
-they are what the table already carries and what the legend already shows:
-an index is a fourth place the column order is written down and the first
-one to go stale when somebody moves a column.
-
-**A combination chart is one scale, and that is the honest half of it.**
-Both marks are measured against the same domain, so a line here says
-something comparable to the columns beside it. The usual reason to reach
-for a combination chart is the other thing, a count against a percentage on
-a second axis, and that is deliberately not this: two scales on one frame
-let the author put any two shapes in any relation by choosing the ranges,
-and the reader has no way to see it happening.
-
-A line among columns still measures from zero, because the columns do and
-they share the axis. */
+Separated by whitespace or commas and matched against the column headings
+the table gives, so a chart says `lines="Margin"` rather than counting
+columns. Names because they are what the table already carries and what the
+legend already shows: an index is a fourth place the column order is
+written down and the first one to go stale when somebody moves a column.
+
+**This says which mark a series takes and nothing about which scale it is
+measured on.** Named here alone, a line shares the columns' domain, so it
+says something comparable to the columns beside it.
+
+The other half of a combination chart, a count against a percentage on a
+scale of its own, is `secondary`, which is a separate property because it
+is a separate question and because the two compose: `with-a-second-axis`
+ships naming one series in both. The argument for why a second scale is opt
+in, and why setting it labels both axes, is written there.
+
+A line among columns measures from zero, because the columns do and they
+share the axis. So does a line on the second scale, which is that scale's
+own rule rather than this one's. */
   "prop:lines"?: (HelixBarChart["lines"]) | undefined;
   /** Which series are measured against a scale of their own, by name.
 
-Space separated and matched the way `lines` is, against the column headings
-the table gives. Opt in: absent, every series shares one domain, which is
-what makes a chart comparable and is the right default.
+Separated and matched the way `lines` is, against the column headings the
+table gives. Opt in: absent, every series shares one domain, which is what
+makes a chart comparable and is the right default.
+
+**The scale, and `lines` is the mark.** The two are separate properties
+because they answer separate questions and a series usually wants both:
+a percentage beside a count is drawn as a line *and* measured on its own
+axis, which is what `with-a-second-axis` writes out. Neither implies the
+other, so a series can be a line on the shared scale and a column can have
+a scale to itself.
 
 **Two scales on one frame let an author put any two shapes in any relation
 by choosing the ranges, and a reader cannot see it happening.** That is not
@@ -6828,7 +6878,15 @@ the bar chart's baseline is not a property at all.
 circumference, which needs the radius, and reading a custom property means
 `getComputedStyle`, which is client-only: a server would draw a different
 ring than the client. A plot's proportions are markup for the same reason
-`curve` is. */
+`curve` is.
+
+**And so it does not reflect**, which is the same argument read forward. No
+selector on either tier asks about it and none can want to: everything the
+thickness decides is arithmetic done here and published as
+`--donut-chart-stroke`, which is a number a rule can do sums with where the
+word is not. Reflected, it wrote a value onto every host a script had set
+it on for nothing to read. `sweep` beside it is the converse and reflects,
+because three rules select on it. */
   hole?: (HelixDonutChart["hole"]) | undefined;
   /** How much of the circle the whole occupies.
 
@@ -6926,7 +6984,15 @@ the bar chart's baseline is not a property at all.
 circumference, which needs the radius, and reading a custom property means
 `getComputedStyle`, which is client-only: a server would draw a different
 ring than the client. A plot's proportions are markup for the same reason
-`curve` is. */
+`curve` is.
+
+**And so it does not reflect**, which is the same argument read forward. No
+selector on either tier asks about it and none can want to: everything the
+thickness decides is arithmetic done here and published as
+`--donut-chart-stroke`, which is a number a rule can do sums with where the
+word is not. Reflected, it wrote a value onto every host a script had set
+it on for nothing to read. `sweep` beside it is the converse and reflects,
+because three rules select on it. */
   "prop:hole"?: (HelixDonutChart["hole"]) | undefined;
   /** How much of the circle the whole occupies.
 
@@ -9513,7 +9579,20 @@ Matched as `outlined` is. */
   /** Which way to read the table.
 
 Absent is `series`, one entry per data column. `categories` reads one entry
-per body row instead, for a donut, whose slices are the rows. */
+per body row instead, for a donut, whose slices are the rows.
+
+**`measures` is `series` without the first column, and it is for a
+scatter.** That chart reads its first numeric column as the measure
+*across*, so its first plotted series is the table's second and everything
+a legend beside it named was one color out: the across column wearing the
+color of the first series drawn, and each real series wearing the next
+one's. The across gets no entry rather than a shifted one, because it is an
+axis and a scatter already writes its name at the end of the scale under
+the plot.
+
+A legend cannot ask the chart which of these it is, `for` naming the table
+they share and not each other, so the consumer says it. That is the same
+shape `categories` already has. */
   entries?: (HelixLegend["entries"]) | undefined;
   /** The id of the table to take the names from.
 
@@ -9596,7 +9675,20 @@ Matched as `outlined` is. */
   /** Which way to read the table.
 
 Absent is `series`, one entry per data column. `categories` reads one entry
-per body row instead, for a donut, whose slices are the rows. */
+per body row instead, for a donut, whose slices are the rows.
+
+**`measures` is `series` without the first column, and it is for a
+scatter.** That chart reads its first numeric column as the measure
+*across*, so its first plotted series is the table's second and everything
+a legend beside it named was one color out: the across column wearing the
+color of the first series drawn, and each real series wearing the next
+one's. The across gets no entry rather than a shifted one, because it is an
+axis and a scatter already writes its name at the end of the scale under
+the plot.
+
+A legend cannot ask the chart which of these it is, `for` naming the table
+they share and not each other, so the consumer says it. That is the same
+shape `categories` already has. */
   "prop:entries"?: (HelixLegend["entries"]) | undefined;
   /** The id of the table to take the names from.
 
@@ -9728,9 +9820,20 @@ useful thing: it is where a reader looks for "and what is it now", which is
 the question a sparkline's single mark answers too.
 
 `none` lets the lines stop on their own, which suits a chart read for its
-shape rather than for where it finished. The shapes come from
+shape rather than for where it finished. `square` is the same mark with its
+corners, for a drawing whose neighbors are square, the columns of a table
+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 set is identical wherever one appears.
+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
+four out of the same sheet and had left two of them unwritten, so the
+finding arrived twice. A shared vocabulary wants naming at each door into
+it, because a reader arrives at one door and not at the set.
 
 `ring` is the one that asks something of the drawing. It leaves a hole and a
 line ends at the reading, which is the hole's center, so the `<svg>` is
@@ -9862,9 +9965,20 @@ useful thing: it is where a reader looks for "and what is it now", which is
 the question a sparkline's single mark answers too.
 
 `none` lets the lines stop on their own, which suits a chart read for its
-shape rather than for where it finished. The shapes come from
+shape rather than for where it finished. `square` is the same mark with its
+corners, for a drawing whose neighbors are square, the columns of a table
+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 set is identical wherever one appears.
+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
+four out of the same sheet and had left two of them unwritten, so the
+finding arrived twice. A shared vocabulary wants naming at each door into
+it, because a reader arrives at one door and not at the set.
 
 `ring` is the one that asks something of the drawing. It leaves a hole and a
 line ends at the reading, which is the hole's center, so the `<svg>` is
@@ -20381,6 +20495,30 @@ export type CustomElements = {
    * the bands overlap where they are drawn and a translucent one would show the
    * others through it.
    *
+   * **No visual axis applies here, and that is the answer rather than a gap.**
+   * Both refusals are geometric and both were argued in the stylesheet before
+   * they were argued anywhere a reader looks.
+   *
+   * `emphasis` is which of a family's two marks carries the reading, and here
+   * neither can give way. The fill is the value, a band's thickness being its
+   * amount, and the edge is the boundary, which is why it is drawn at full color
+   * over a pale fill rather than left to two pale fills meeting. Every point on
+   * the axis moves one at the other's expense: `outlined` thins the fill until
+   * the chart is a set of cumulative lines, which is `LineChart` and is the form
+   * this one exists because a reader cannot read shares off; `solid` takes the
+   * fill to the series' own color, which is the edge's color, so the boundary
+   * disappears into the band it bounds. `LineChart` can take the axis because its
+   * wash is optional there, `area` deciding whether one is drawn at all.
+   *
+   * `material` is what reads through a mark, and a band cannot let anything
+   * through. Each is drawn as everything under its top edge with the next one
+   * down covering the rest, so a translucent band shows the bands behind it and
+   * reads as a third color that is in no palette. That is `LineChart`'s recorded
+   * reason for refusing `wash`, met here from the other side. The strength of a
+   * fill is still adjustable and is `--area-chart-fill-strength`, which is a
+   * continuum rather than an axis and is a theme's business rather than a
+   * reader's.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
@@ -20399,9 +20537,13 @@ export type CustomElements = {
    * words and is already written.
    * - `curve`: How a band's edge gets from one reading to the next.
    *
-   * Absent is `straight`, for the reason the class doc gives, and absent rather
-   * than defaulted because a reflecting property with a default writes its
-   * attribute onto every host, including the ones nobody configured.
+   * Three values, and the class doc argues for each: `straight` is absent and
+   * is the default, `smooth` is for a stack read as a shape and is the one that
+   * can draw a part as less than nothing, `step` is for a quantity that changes
+   * at a moment and is ordered the way `straight` is.
+   *
+   * Absent rather than defaulted because a reflecting property with a default
+   * writes its attribute onto every host, including the ones nobody configured.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * The same three values `LineChart` takes, with the same fallback: a bare
@@ -20441,6 +20583,11 @@ export type CustomElements = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -20463,6 +20610,24 @@ export type CustomElements = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -20472,6 +20637,7 @@ export type CustomElements = {
    * - `--area-chart-gap`: Space between the drawing and its labels. (default: `undefined`)
    * - `--area-chart-gridline-color`: One rule across the plot, under `gridlines`. (default: `undefined`)
    * - `--area-chart-width`: Thickness of a band's top edge, over `--chart-stroke`. (default: `undefined`)
+   * - `--chart-stroke`: Thickness of a band's top edge, one name across this family, Line Chart and Bar Chart's `lines`, since the three read one shared rule. `--area-chart-width` overrides it here. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -20949,6 +21115,12 @@ export type CustomElements = {
    * of the series color with that edge on it, and absent is the filled column,
    * per the rule that a reflected property takes no default.
    *
+   * `solid` is that filled column written out. It matches no rule in the sheet
+   * and lands on the base one, which is what the resting value of every axis in
+   * the registry does, and it is worth having so a consumer switching a chart
+   * between treatments has a word for the one it started at rather than having
+   * to remove the attribute.
+   *
    * **It composes with `material` rather than competing with it.** Emphasis
    * decides what is drawn and material decides how much of it comes through, so
    * `glass` thins whatever emphasis put there: the fill on a solid column, the
@@ -21002,10 +21174,15 @@ export type CustomElements = {
    * having the datum rather than by painting it invisibly.
    * - `outlined`: Which series are drawn as an outline rather than a fill, by name.
    *
-   * Space separated and matched against the column headings the table gives,
-   * the way `lines` and `secondary` are, so a chart says `outlined="Forecast"`
-   * rather than counting columns. Names because they are what the table already
-   * carries and what the legend already shows.
+   * Separated by whitespace or commas and matched against the column headings
+   * the table gives, the way `lines` and `secondary` are, so a chart says
+   * `outlined="Forecast"` rather than counting columns. Names because they are
+   * what the table already carries and what the legend already shows.
+   *
+   * All five read one splitter, `seriesNames` in `core`, because the sentence
+   * above was true of the matching and false of the splitting: these three took
+   * a comma and those two did not, so `lines="Gateway, Billing"` drew no line
+   * and said nothing.
    *
    * **The case this exists for is a series that is not a measurement.** A
    * forecast, a target, a budget: something drawn on the same axis as the
@@ -21067,27 +21244,37 @@ export type CustomElements = {
    * and reach no reader through the table.
    * - `lines`: Which series are drawn as a line instead of as columns, by name.
    *
-   * Space separated, matched against the column headings the table gives, so a
-   * chart says `lines="Margin"` rather than counting columns. Names because
-   * they are what the table already carries and what the legend already shows:
-   * an index is a fourth place the column order is written down and the first
-   * one to go stale when somebody moves a column.
-   *
-   * **A combination chart is one scale, and that is the honest half of it.**
-   * Both marks are measured against the same domain, so a line here says
-   * something comparable to the columns beside it. The usual reason to reach
-   * for a combination chart is the other thing, a count against a percentage on
-   * a second axis, and that is deliberately not this: two scales on one frame
-   * let the author put any two shapes in any relation by choosing the ranges,
-   * and the reader has no way to see it happening.
-   *
-   * A line among columns still measures from zero, because the columns do and
-   * they share the axis.
+   * Separated by whitespace or commas and matched against the column headings
+   * the table gives, so a chart says `lines="Margin"` rather than counting
+   * columns. Names because they are what the table already carries and what the
+   * legend already shows: an index is a fourth place the column order is
+   * written down and the first one to go stale when somebody moves a column.
+   *
+   * **This says which mark a series takes and nothing about which scale it is
+   * measured on.** Named here alone, a line shares the columns' domain, so it
+   * says something comparable to the columns beside it.
+   *
+   * The other half of a combination chart, a count against a percentage on a
+   * scale of its own, is `secondary`, which is a separate property because it
+   * is a separate question and because the two compose: `with-a-second-axis`
+   * ships naming one series in both. The argument for why a second scale is opt
+   * in, and why setting it labels both axes, is written there.
+   *
+   * A line among columns measures from zero, because the columns do and they
+   * share the axis. So does a line on the second scale, which is that scale's
+   * own rule rather than this one's.
    * - `secondary`: Which series are measured against a scale of their own, by name.
    *
-   * Space separated and matched the way `lines` is, against the column headings
-   * the table gives. Opt in: absent, every series shares one domain, which is
-   * what makes a chart comparable and is the right default.
+   * Separated and matched the way `lines` is, against the column headings the
+   * table gives. Opt in: absent, every series shares one domain, which is what
+   * makes a chart comparable and is the right default.
+   *
+   * **The scale, and `lines` is the mark.** The two are separate properties
+   * because they answer separate questions and a series usually wants both:
+   * a percentage beside a count is drawn as a line *and* measured on its own
+   * axis, which is what `with-a-second-axis` writes out. Neither implies the
+   * other, so a series can be a line on the shared scale and a column can have
+   * a scale to itself.
    *
    * **Two scales on one frame let an author put any two shapes in any relation
    * by choosing the ranges, and a reader cannot see it happening.** That is not
@@ -21136,6 +21323,11 @@ export type CustomElements = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -21158,6 +21350,24 @@ export type CustomElements = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -21170,7 +21380,8 @@ export type CustomElements = {
    * - `--bar-chart-gridline-color`: One rule across the plot, under `gridlines`. (default: `undefined`)
    * - `--bar-chart-line-color`: A `lines` series, overriding its series color. (default: `undefined`)
    * - `--bar-chart-line-width`: Thickness of a `lines` series, over `--chart-stroke`. (default: `undefined`)
-   * - `--bar-chart-axis`: The color of a single-series axis, taken from that series. (default: `undefined`)
+   * - `--chart-stroke`: Thickness of a `lines` series, one name across this family, Line Chart and Area Chart's top edge, since the three read one shared rule. `--bar-chart-line-width` overrides it here. (default: `undefined`)
+   * - `--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`)
    * - `--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`)
    *
@@ -25636,6 +25847,14 @@ export type CustomElements = {
    * `getComputedStyle`, which is client-only: a server would draw a different
    * ring than the client. A plot's proportions are markup for the same reason
    * `curve` is.
+   *
+   * **And so it does not reflect**, which is the same argument read forward. No
+   * selector on either tier asks about it and none can want to: everything the
+   * thickness decides is arithmetic done here and published as
+   * `--donut-chart-stroke`, which is a number a rule can do sums with where the
+   * word is not. Reflected, it wrote a value onto every host a script had set
+   * it on for nothing to read. `sweep` beside it is the converse and reflects,
+   * because three rules select on it.
    * - `sweep`: How much of the circle the whole occupies.
    *
    * Absent is the full turn. `half` is a semi-donut: the same shares spread
@@ -25685,6 +25904,11 @@ export type CustomElements = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -25713,6 +25937,24 @@ export type CustomElements = {
    *
    * - `(default)`: Goes in the middle of the ring. A total, usually.
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -27348,6 +27590,11 @@ export type CustomElements = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `visible`: How many cells are actually drawn.
    *
@@ -27398,6 +27645,24 @@ export type CustomElements = {
    * - `start`: Below the strip, at the leading edge.
    * - `summary`: Below the strip, in the middle.
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -28318,6 +28583,19 @@ export type CustomElements = {
    *
    * Absent is `series`, one entry per data column. `categories` reads one entry
    * per body row instead, for a donut, whose slices are the rows.
+   *
+   * **`measures` is `series` without the first column, and it is for a
+   * scatter.** That chart reads its first numeric column as the measure
+   * *across*, so its first plotted series is the table's second and everything
+   * a legend beside it named was one color out: the across column wearing the
+   * color of the first series drawn, and each real series wearing the next
+   * one's. The across gets no entry rather than a shifted one, because it is an
+   * axis and a scatter already writes its name at the end of the scale under
+   * the plot.
+   *
+   * A legend cannot ask the chart which of these it is, `for` naming the table
+   * they share and not each other, so the consumer says it. That is the same
+   * shape `categories` already has.
    * - `for`: The id of the table to take the names from.
    *
    * Resolved through `getRootNode()`, so a legend inside another component's
@@ -28383,9 +28661,15 @@ export type CustomElements = {
    * lets one drawing fill a narrow card and a wide panel, and without
    * `vector-effect: non-scaling-stroke` the same line comes out hairline in the
    * first and heavy in the second. It rescues strokes and not geometry, which is
-   * why the readings are joined by lines and marked by nothing: a circle in a
-   * stretched coordinate space is an ellipse, and there is no vector-effect that
-   * answers for a shape.
+   * why nothing inside the drawing marks a reading: a circle in a stretched
+   * coordinate space is an ellipse, and there is no vector-effect that answers
+   * for a shape.
+   *
+   * **The last reading of each series is marked, and that is the same rule rather
+   * than an exception to it.** `terminus` draws an HTML element placed over the
+   * plot by percentage instead of a shape inside it, so it keeps its shape at any
+   * width. It is on by default, as a dot, because the column of marks at the far
+   * edge is where a reader looks for "and what is it now".
    *
    * ## Attributes & Properties
    *
@@ -28498,9 +28782,20 @@ export type CustomElements = {
    * the question a sparkline's single mark answers too.
    *
    * `none` lets the lines stop on their own, which suits a chart read for its
-   * shape rather than for where it finished. The shapes come from
+   * shape rather than for where it finished. `square` is the same mark with its
+   * corners, for a drawing whose neighbors are square, the columns of a table
+   * 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 set is identical wherever one appears.
+   * 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
+   * four out of the same sheet and had left two of them unwritten, so the
+   * finding arrived twice. A shared vocabulary wants naming at each door into
+   * it, because a reader arrives at one door and not at the set.
    *
    * `ring` is the one that asks something of the drawing. It leaves a hole and a
    * line ends at the reading, which is the hole's center, so the `<svg>` is
@@ -28541,6 +28836,11 @@ export type CustomElements = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -28563,17 +28863,39 @@ export type CustomElements = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
    *
-   * - `--chart-stroke`: Thickness of a series drawn as a line, here and on Area Chart's top edge and Bar Chart's `lines`. Each family's own width hook overrides it. (default: `undefined`)
+   * - `--chart-stroke`: Thickness of a series drawn as a line, one name across this family, Area Chart's top edge and Bar Chart's `lines`, since the three read one shared rule. Each family's own width hook overrides it. (default: `undefined`)
+   * - `--chart-terminus-hole`: A fill for the middle of a `ring` terminus, which is otherwise open. One name across this family and Sparkline, the two reading one shared sheet. (default: `undefined`)
+   * - `--chart-terminus-size`: Size of the mark on each series' last reading. One name across this family and Sparkline, the two reading one shared sheet. (default: `undefined`)
    * - `--line-chart-area-opacity`: How much of a line's color its wash takes. (default: `undefined`)
    * - `--line-chart-band-color`: The slot the pointer is resting in. (default: `undefined`)
    * - `--line-chart-block-size`: Height of the drawing. (default: `undefined`)
    * - `--line-chart-gap`: Space between the drawing and its labels. (default: `undefined`)
    * - `--line-chart-gridline-color`: One rule across the plot, under `gridlines`. (default: `undefined`)
    * - `--line-chart-width`: Thickness of a line, over `--chart-stroke`. (default: `undefined`)
+   * - `--chart-terminus-x`: Where a series' last reading sits horizontally, as a percentage. Written by the component. (default: `undefined`)
+   * - `--chart-terminus-y`: Where a series' last reading sits vertically, as a percentage. Written by the component. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -33057,6 +33379,30 @@ export type CustomElements = {
    * dense cluster reads as dense rather than as one blot, and two points that
    * overlap each keep their edge.
    *
+   * **No visual axis applies here, and that is the answer rather than a gap.**
+   * Both refusals come out of that sentence, and both were argued in the
+   * stylesheet before they were argued anywhere a reader looks.
+   *
+   * `emphasis` is how much ink a mark claims, and on a scatter that channel is
+   * already carrying data. The points rest at 0.8 so that where they pile up they
+   * compound: how dark a region is *is* how many rows are in it, which is most of
+   * what a reader is looking at a scatter to see and is the one thing a table of
+   * the same numbers hides. `solid` flattens a dense cluster and a sparse one into
+   * the same picture; `outlined` replaces the pile with overlapping rings, which
+   * reads as texture rather than as count. An axis whose two ends each cost the
+   * drawing its density is not a treatment, it is a second meaning for a property
+   * the chart already spends.
+   *
+   * `material` is the same refusal said once more. Translucency is the density
+   * channel here, so `glass` and `frosted` are two more named stops on a scale
+   * the data is using, and a point admitting the page through is a point that
+   * counts for less than one.
+   *
+   * What stays adjustable is `--scatter-chart-point-opacity`, and it is a
+   * continuum rather than an axis: a chart drawn over a busier ground wants a
+   * different resting density, and that is a fact about the ground rather than a
+   * claim about the points.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
@@ -33109,6 +33455,11 @@ export type CustomElements = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -33131,6 +33482,24 @@ export type CustomElements = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -39243,6 +39612,30 @@ export type CustomElementsSolidJs = {
    * the bands overlap where they are drawn and a translucent one would show the
    * others through it.
    *
+   * **No visual axis applies here, and that is the answer rather than a gap.**
+   * Both refusals are geometric and both were argued in the stylesheet before
+   * they were argued anywhere a reader looks.
+   *
+   * `emphasis` is which of a family's two marks carries the reading, and here
+   * neither can give way. The fill is the value, a band's thickness being its
+   * amount, and the edge is the boundary, which is why it is drawn at full color
+   * over a pale fill rather than left to two pale fills meeting. Every point on
+   * the axis moves one at the other's expense: `outlined` thins the fill until
+   * the chart is a set of cumulative lines, which is `LineChart` and is the form
+   * this one exists because a reader cannot read shares off; `solid` takes the
+   * fill to the series' own color, which is the edge's color, so the boundary
+   * disappears into the band it bounds. `LineChart` can take the axis because its
+   * wash is optional there, `area` deciding whether one is drawn at all.
+   *
+   * `material` is what reads through a mark, and a band cannot let anything
+   * through. Each is drawn as everything under its top edge with the next one
+   * down covering the rest, so a translucent band shows the bands behind it and
+   * reads as a third color that is in no palette. That is `LineChart`'s recorded
+   * reason for refusing `wash`, met here from the other side. The strength of a
+   * fill is still adjustable and is `--area-chart-fill-strength`, which is a
+   * continuum rather than an axis and is a theme's business rather than a
+   * reader's.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
@@ -39261,9 +39654,13 @@ export type CustomElementsSolidJs = {
    * words and is already written.
    * - `curve`: How a band's edge gets from one reading to the next.
    *
-   * Absent is `straight`, for the reason the class doc gives, and absent rather
-   * than defaulted because a reflecting property with a default writes its
-   * attribute onto every host, including the ones nobody configured.
+   * Three values, and the class doc argues for each: `straight` is absent and
+   * is the default, `smooth` is for a stack read as a shape and is the one that
+   * can draw a part as less than nothing, `step` is for a quantity that changes
+   * at a moment and is ordered the way `straight` is.
+   *
+   * Absent rather than defaulted because a reflecting property with a default
+   * writes its attribute onto every host, including the ones nobody configured.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * The same three values `LineChart` takes, with the same fallback: a bare
@@ -39303,6 +39700,11 @@ export type CustomElementsSolidJs = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -39325,6 +39727,24 @@ export type CustomElementsSolidJs = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -39334,6 +39754,7 @@ export type CustomElementsSolidJs = {
    * - `--area-chart-gap`: Space between the drawing and its labels. (default: `undefined`)
    * - `--area-chart-gridline-color`: One rule across the plot, under `gridlines`. (default: `undefined`)
    * - `--area-chart-width`: Thickness of a band's top edge, over `--chart-stroke`. (default: `undefined`)
+   * - `--chart-stroke`: Thickness of a band's top edge, one name across this family, Line Chart and Bar Chart's `lines`, since the three read one shared rule. `--area-chart-width` overrides it here. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -39827,6 +40248,12 @@ export type CustomElementsSolidJs = {
    * of the series color with that edge on it, and absent is the filled column,
    * per the rule that a reflected property takes no default.
    *
+   * `solid` is that filled column written out. It matches no rule in the sheet
+   * and lands on the base one, which is what the resting value of every axis in
+   * the registry does, and it is worth having so a consumer switching a chart
+   * between treatments has a word for the one it started at rather than having
+   * to remove the attribute.
+   *
    * **It composes with `material` rather than competing with it.** Emphasis
    * decides what is drawn and material decides how much of it comes through, so
    * `glass` thins whatever emphasis put there: the fill on a solid column, the
@@ -39880,10 +40307,15 @@ export type CustomElementsSolidJs = {
    * having the datum rather than by painting it invisibly.
    * - `outlined`: Which series are drawn as an outline rather than a fill, by name.
    *
-   * Space separated and matched against the column headings the table gives,
-   * the way `lines` and `secondary` are, so a chart says `outlined="Forecast"`
-   * rather than counting columns. Names because they are what the table already
-   * carries and what the legend already shows.
+   * Separated by whitespace or commas and matched against the column headings
+   * the table gives, the way `lines` and `secondary` are, so a chart says
+   * `outlined="Forecast"` rather than counting columns. Names because they are
+   * what the table already carries and what the legend already shows.
+   *
+   * All five read one splitter, `seriesNames` in `core`, because the sentence
+   * above was true of the matching and false of the splitting: these three took
+   * a comma and those two did not, so `lines="Gateway, Billing"` drew no line
+   * and said nothing.
    *
    * **The case this exists for is a series that is not a measurement.** A
    * forecast, a target, a budget: something drawn on the same axis as the
@@ -39945,27 +40377,37 @@ export type CustomElementsSolidJs = {
    * and reach no reader through the table.
    * - `lines`: Which series are drawn as a line instead of as columns, by name.
    *
-   * Space separated, matched against the column headings the table gives, so a
-   * chart says `lines="Margin"` rather than counting columns. Names because
-   * they are what the table already carries and what the legend already shows:
-   * an index is a fourth place the column order is written down and the first
-   * one to go stale when somebody moves a column.
-   *
-   * **A combination chart is one scale, and that is the honest half of it.**
-   * Both marks are measured against the same domain, so a line here says
-   * something comparable to the columns beside it. The usual reason to reach
-   * for a combination chart is the other thing, a count against a percentage on
-   * a second axis, and that is deliberately not this: two scales on one frame
-   * let the author put any two shapes in any relation by choosing the ranges,
-   * and the reader has no way to see it happening.
-   *
-   * A line among columns still measures from zero, because the columns do and
-   * they share the axis.
+   * Separated by whitespace or commas and matched against the column headings
+   * the table gives, so a chart says `lines="Margin"` rather than counting
+   * columns. Names because they are what the table already carries and what the
+   * legend already shows: an index is a fourth place the column order is
+   * written down and the first one to go stale when somebody moves a column.
+   *
+   * **This says which mark a series takes and nothing about which scale it is
+   * measured on.** Named here alone, a line shares the columns' domain, so it
+   * says something comparable to the columns beside it.
+   *
+   * The other half of a combination chart, a count against a percentage on a
+   * scale of its own, is `secondary`, which is a separate property because it
+   * is a separate question and because the two compose: `with-a-second-axis`
+   * ships naming one series in both. The argument for why a second scale is opt
+   * in, and why setting it labels both axes, is written there.
+   *
+   * A line among columns measures from zero, because the columns do and they
+   * share the axis. So does a line on the second scale, which is that scale's
+   * own rule rather than this one's.
    * - `secondary`: Which series are measured against a scale of their own, by name.
    *
-   * Space separated and matched the way `lines` is, against the column headings
-   * the table gives. Opt in: absent, every series shares one domain, which is
-   * what makes a chart comparable and is the right default.
+   * Separated and matched the way `lines` is, against the column headings the
+   * table gives. Opt in: absent, every series shares one domain, which is what
+   * makes a chart comparable and is the right default.
+   *
+   * **The scale, and `lines` is the mark.** The two are separate properties
+   * because they answer separate questions and a series usually wants both:
+   * a percentage beside a count is drawn as a line *and* measured on its own
+   * axis, which is what `with-a-second-axis` writes out. Neither implies the
+   * other, so a series can be a line on the shared scale and a column can have
+   * a scale to itself.
    *
    * **Two scales on one frame let an author put any two shapes in any relation
    * by choosing the ranges, and a reader cannot see it happening.** That is not
@@ -40014,6 +40456,11 @@ export type CustomElementsSolidJs = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -40036,6 +40483,24 @@ export type CustomElementsSolidJs = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -40048,7 +40513,8 @@ export type CustomElementsSolidJs = {
    * - `--bar-chart-gridline-color`: One rule across the plot, under `gridlines`. (default: `undefined`)
    * - `--bar-chart-line-color`: A `lines` series, overriding its series color. (default: `undefined`)
    * - `--bar-chart-line-width`: Thickness of a `lines` series, over `--chart-stroke`. (default: `undefined`)
-   * - `--bar-chart-axis`: The color of a single-series axis, taken from that series. (default: `undefined`)
+   * - `--chart-stroke`: Thickness of a `lines` series, one name across this family, Line Chart and Area Chart's top edge, since the three read one shared rule. `--bar-chart-line-width` overrides it here. (default: `undefined`)
+   * - `--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`)
    * - `--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`)
    *
@@ -44593,6 +45059,14 @@ export type CustomElementsSolidJs = {
    * `getComputedStyle`, which is client-only: a server would draw a different
    * ring than the client. A plot's proportions are markup for the same reason
    * `curve` is.
+   *
+   * **And so it does not reflect**, which is the same argument read forward. No
+   * selector on either tier asks about it and none can want to: everything the
+   * thickness decides is arithmetic done here and published as
+   * `--donut-chart-stroke`, which is a number a rule can do sums with where the
+   * word is not. Reflected, it wrote a value onto every host a script had set
+   * it on for nothing to read. `sweep` beside it is the converse and reflects,
+   * because three rules select on it.
    * - `sweep`: How much of the circle the whole occupies.
    *
    * Absent is the full turn. `half` is a semi-donut: the same shares spread
@@ -44642,6 +45116,11 @@ export type CustomElementsSolidJs = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -44670,6 +45149,24 @@ export type CustomElementsSolidJs = {
    *
    * - `(default)`: Goes in the middle of the ring. A total, usually.
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -46347,6 +46844,11 @@ export type CustomElementsSolidJs = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `visible`: How many cells are actually drawn.
    *
@@ -46397,6 +46899,24 @@ export type CustomElementsSolidJs = {
    * - `start`: Below the strip, at the leading edge.
    * - `summary`: Below the strip, in the middle.
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -47337,6 +47857,19 @@ export type CustomElementsSolidJs = {
    *
    * Absent is `series`, one entry per data column. `categories` reads one entry
    * per body row instead, for a donut, whose slices are the rows.
+   *
+   * **`measures` is `series` without the first column, and it is for a
+   * scatter.** That chart reads its first numeric column as the measure
+   * *across*, so its first plotted series is the table's second and everything
+   * a legend beside it named was one color out: the across column wearing the
+   * color of the first series drawn, and each real series wearing the next
+   * one's. The across gets no entry rather than a shifted one, because it is an
+   * axis and a scatter already writes its name at the end of the scale under
+   * the plot.
+   *
+   * A legend cannot ask the chart which of these it is, `for` naming the table
+   * they share and not each other, so the consumer says it. That is the same
+   * shape `categories` already has.
    * - `for`: The id of the table to take the names from.
    *
    * Resolved through `getRootNode()`, so a legend inside another component's
@@ -47405,9 +47938,15 @@ export type CustomElementsSolidJs = {
    * lets one drawing fill a narrow card and a wide panel, and without
    * `vector-effect: non-scaling-stroke` the same line comes out hairline in the
    * first and heavy in the second. It rescues strokes and not geometry, which is
-   * why the readings are joined by lines and marked by nothing: a circle in a
-   * stretched coordinate space is an ellipse, and there is no vector-effect that
-   * answers for a shape.
+   * why nothing inside the drawing marks a reading: a circle in a stretched
+   * coordinate space is an ellipse, and there is no vector-effect that answers
+   * for a shape.
+   *
+   * **The last reading of each series is marked, and that is the same rule rather
+   * than an exception to it.** `terminus` draws an HTML element placed over the
+   * plot by percentage instead of a shape inside it, so it keeps its shape at any
+   * width. It is on by default, as a dot, because the column of marks at the far
+   * edge is where a reader looks for "and what is it now".
    *
    * ## Attributes & Properties
    *
@@ -47520,9 +48059,20 @@ export type CustomElementsSolidJs = {
    * the question a sparkline's single mark answers too.
    *
    * `none` lets the lines stop on their own, which suits a chart read for its
-   * shape rather than for where it finished. The shapes come from
+   * shape rather than for where it finished. `square` is the same mark with its
+   * corners, for a drawing whose neighbors are square, the columns of a table
+   * 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 set is identical wherever one appears.
+   * 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
+   * four out of the same sheet and had left two of them unwritten, so the
+   * finding arrived twice. A shared vocabulary wants naming at each door into
+   * it, because a reader arrives at one door and not at the set.
    *
    * `ring` is the one that asks something of the drawing. It leaves a hole and a
    * line ends at the reading, which is the hole's center, so the `<svg>` is
@@ -47563,6 +48113,11 @@ export type CustomElementsSolidJs = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -47585,17 +48140,39 @@ export type CustomElementsSolidJs = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
    *
-   * - `--chart-stroke`: Thickness of a series drawn as a line, here and on Area Chart's top edge and Bar Chart's `lines`. Each family's own width hook overrides it. (default: `undefined`)
+   * - `--chart-stroke`: Thickness of a series drawn as a line, one name across this family, Area Chart's top edge and Bar Chart's `lines`, since the three read one shared rule. Each family's own width hook overrides it. (default: `undefined`)
+   * - `--chart-terminus-hole`: A fill for the middle of a `ring` terminus, which is otherwise open. One name across this family and Sparkline, the two reading one shared sheet. (default: `undefined`)
+   * - `--chart-terminus-size`: Size of the mark on each series' last reading. One name across this family and Sparkline, the two reading one shared sheet. (default: `undefined`)
    * - `--line-chart-area-opacity`: How much of a line's color its wash takes. (default: `undefined`)
    * - `--line-chart-band-color`: The slot the pointer is resting in. (default: `undefined`)
    * - `--line-chart-block-size`: Height of the drawing. (default: `undefined`)
    * - `--line-chart-gap`: Space between the drawing and its labels. (default: `undefined`)
    * - `--line-chart-gridline-color`: One rule across the plot, under `gridlines`. (default: `undefined`)
    * - `--line-chart-width`: Thickness of a line, over `--chart-stroke`. (default: `undefined`)
+   * - `--chart-terminus-x`: Where a series' last reading sits horizontally, as a percentage. Written by the component. (default: `undefined`)
+   * - `--chart-terminus-y`: Where a series' last reading sits vertically, as a percentage. Written by the component. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -52190,6 +52767,30 @@ export type CustomElementsSolidJs = {
    * dense cluster reads as dense rather than as one blot, and two points that
    * overlap each keep their edge.
    *
+   * **No visual axis applies here, and that is the answer rather than a gap.**
+   * Both refusals come out of that sentence, and both were argued in the
+   * stylesheet before they were argued anywhere a reader looks.
+   *
+   * `emphasis` is how much ink a mark claims, and on a scatter that channel is
+   * already carrying data. The points rest at 0.8 so that where they pile up they
+   * compound: how dark a region is *is* how many rows are in it, which is most of
+   * what a reader is looking at a scatter to see and is the one thing a table of
+   * the same numbers hides. `solid` flattens a dense cluster and a sparse one into
+   * the same picture; `outlined` replaces the pile with overlapping rings, which
+   * reads as texture rather than as count. An axis whose two ends each cost the
+   * drawing its density is not a treatment, it is a second meaning for a property
+   * the chart already spends.
+   *
+   * `material` is the same refusal said once more. Translucency is the density
+   * channel here, so `glass` and `frosted` are two more named stops on a scale
+   * the data is using, and a point admitting the page through is a point that
+   * counts for less than one.
+   *
+   * What stays adjustable is `--scatter-chart-point-opacity`, and it is a
+   * continuum rather than an axis: a chart drawn over a busier ground wants a
+   * different resting density, and that is a fact about the ground rather than a
+   * claim about the points.
+   *
    * ## Attributes & Properties
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
@@ -52242,6 +52843,11 @@ export type CustomElementsSolidJs = {
    * calendar week, and declaring that against a base class whose `rows` is a
    * `Row[]` getter is a type error at best. Name the member for what it holds
    * rather than for the shortest word available. (property only) (readonly)
+   * - `plottedColumns`: Which cells of a row hold numbers, by their place in it, in table order.
+   *
+   * The same test `readSeries` applies when it drops a column of notes: a
+   * column is a series where any row parses, so a series survives one blank
+   * cell and a column of words is never one. (property only) (readonly)
    * - `readings`: How many readings there are, which is what the pointer maps onto. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -52264,6 +52870,24 @@ export type CustomElementsSolidJs = {
    * browser harness's awaits it alone: a browser always runs the frame, and a
    * timer beside it was a bet on how long one takes, which a busy run lost. (property only) (readonly)
    *
+   * ## Methods
+   *
+   * Methods that can be called to access component functionality.
+   *
+   * - `seriesOf(cell: number) => number | undefined`: The palette slot the cell at this place in a row is drawn in.
+   *
+   * **A cell's place in its row is not its series' depth, and the tooltip
+   * spent a while assuming it was.** `readSeries` drops a column nothing
+   * parses and `readRows` keeps it, so one column of notes among the figures
+   * moves every column after it one color along in the bubble: a row reading
+   * `Referral 1,080` wearing series three's green beside a legend that says
+   * series three is something else, which is the one failure the dot exists
+   * to prevent.
+   *
+   * Overridden where a chart reads the table some other way. `ScatterChart`
+   * splits the first plotted column off as the measure across, so its first
+   * *plotted* series is this table's second numeric column.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -58049,6 +58673,8 @@ export type CustomCssProperties = {
   "--area-chart-gridline-color"?: (string) | undefined;
   /** Thickness of a band's top edge, over `--chart-stroke`. */
   "--area-chart-width"?: (string) | undefined;
+  /** Thickness of a band's top edge, one name across this family, Line Chart and Bar Chart's `lines`, since the three read one shared rule. `--area-chart-width` overrides it here. */
+  "--chart-stroke"?: (string) | undefined;
   /** How far each avatar sits over the one before it. */
   "--avatar-group-overlap"?: (string) | undefined;
   /** The separation drawn between one avatar and the next. */
@@ -58079,7 +58705,7 @@ export type CustomCssProperties = {
   "--bar-chart-line-color"?: (string) | undefined;
   /** Thickness of a `lines` series, over `--chart-stroke`. */
   "--bar-chart-line-width"?: (string) | undefined;
-  /** The color of a single-series axis, taken from that series. */
+  /** 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. */
   "--bar-chart-secondary"?: (string) | undefined;
@@ -58491,8 +59117,10 @@ export type CustomCssProperties = {
   "--legend-swatch-size"?: (string) | undefined;
   /** Width of the edge an `outlined` or `subtle` swatch is drawn with. */
   "--legend-swatch-stroke"?: (string) | undefined;
-  /** Thickness of a series drawn as a line, here and on Area Chart's top edge and Bar Chart's `lines`. Each family's own width hook overrides it. */
-  "--chart-stroke"?: (string) | undefined;
+  /** A fill for the middle of a `ring` terminus, which is otherwise open. One name across this family and Sparkline, the two reading one shared sheet. */
+  "--chart-terminus-hole"?: (string) | undefined;
+  /** Size of the mark on each series' last reading. One name across this family and Sparkline, the two reading one shared sheet. */
+  "--chart-terminus-size"?: (string) | undefined;
   /** How much of a line's color its wash takes. */
   "--line-chart-area-opacity"?: (string) | undefined;
   /** The slot the pointer is resting in. */
@@ -58505,6 +59133,10 @@ export type CustomCssProperties = {
   "--line-chart-gridline-color"?: (string) | undefined;
   /** Thickness of a line, over `--chart-stroke`. */
   "--line-chart-width"?: (string) | undefined;
+  /** Where a series' last reading sits horizontally, as a percentage. Written by the component. */
+  "--chart-terminus-x"?: (string) | undefined;
+  /** Where a series' last reading sits vertically, as a percentage. Written by the component. */
+  "--chart-terminus-y"?: (string) | undefined;
   /** Padding inside the row. */
   "--list-item-padding"?: (string) | undefined;
   /** What the rail cell shows. Written by the list. */
@@ -58837,10 +59469,6 @@ export type CustomCssProperties = {
   "--slider-marker-at"?: (string) | undefined;
   /** Where the filled span ends, as a percentage of the track. */
   "--slider-to"?: (string) | undefined;
-  /** A fill for the middle of a `ring` terminus, which is otherwise open. */
-  "--chart-terminus-hole"?: (string) | undefined;
-  /** Size of the mark on the last reading. */
-  "--chart-terminus-size"?: (string) | undefined;
   /** How much of the line's color the wash takes where it meets the line. */
   "--sparkline-area-opacity"?: (string) | undefined;
   /** Corner radius on a column, under `plot="bar"`. */
@@ -58855,10 +59483,6 @@ export type CustomCssProperties = {
   "--sparkline-inline-size"?: (string) | undefined;
   /** Thickness of the line, overriding `weight`. */
   "--sparkline-width"?: (string) | undefined;
-  /** Where the last point sits horizontally, as a percentage. */
-  "--chart-terminus-x"?: (string) | undefined;
-  /** Where the last point sits vertically, as a percentage. */
-  "--chart-terminus-y"?: (string) | undefined;
   /** Edge length of the mark. */
   "--speed-dial-item-size"?: (string) | undefined;
   /** Space between the actions. */