@fusion.dev/helix-headless 0.40.0 → 0.41.0

package/types/jsx.d.ts

@@ -749,9 +749,13 @@ the property carries the part's name, `content`. */
 export type HelixHeadlessAreaChartProps = {
   /** 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?: (HelixHeadlessAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -788,9 +792,13 @@ words and is already written. */
 export type HelixHeadlessAreaChartSolidJsProps = {
   /** 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"?: (HelixHeadlessAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -1022,28 +1030,38 @@ and reach no reader through the table. */
   gridlines?: (HelixHeadlessBarChart["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?: (HelixHeadlessBarChart["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
@@ -1110,28 +1128,38 @@ and reach no reader through the table. */
   "prop:gridlines"?: (HelixHeadlessBarChart["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"?: (HelixHeadlessBarChart["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
@@ -5607,7 +5635,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?: (HelixHeadlessDonutChart["hole"]) | undefined;
   /** How much of the circle the whole occupies.
 
@@ -5664,7 +5700,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"?: (HelixHeadlessDonutChart["hole"]) | undefined;
   /** How much of the circle the whole occupies.
 
@@ -8037,7 +8081,20 @@ export type HelixHeadlessLegendProps = {
   /** 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?: (HelixHeadlessLegend["entries"]) | undefined;
   /** The id of the table to take the names from.
 
@@ -8053,7 +8110,20 @@ export type HelixHeadlessLegendSolidJsProps = {
   /** 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"?: (HelixHeadlessLegend["entries"]) | undefined;
   /** The id of the table to take the names from.
 
@@ -8131,9 +8201,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
@@ -8225,9 +8306,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
@@ -17513,12 +17605,28 @@ export type CustomElements = {
    * else draws every part in proportion to nothing. `LineChart` measures from its
    * own range because a line claims a position; a band claims an amount.
    *
+   * **And so it is not a streamgraph**, which is the near neighbor to name.
+   * A streamgraph moves its baseline to center the bands and reads as a river; it
+   * is a real form and it is the one thing the rule above refuses, so this
+   * carries no alias for it. What it has instead is `share`, which answers the
+   * question a streamgraph is usually reached for, how the composition changed,
+   * without giving up a floor a reader can measure against.
+   *
    * **Straight between readings unless asked otherwise.** A band's top edge is a
    * sum, and a curve fitted through one sum can pass under the curve fitted
    * through the sum beneath it, so a smoothed stack can draw a part as less than
    * nothing between two readings. Straight segments between ordered points stay
    * ordered. `curve="smooth"` is there for a stack that is read as a shape.
    *
+   * `curve="step"` falls on the safe side of that argument rather than being
+   * unanswered by it, and it is worth saying which side because a reader cannot
+   * tell from the argument alone. A step takes no value the readings do not have:
+   * it holds one, jumps at the midpoint, and holds the next. So two stepped edges
+   * that are ordered at every reading are ordered everywhere between them, which
+   * is what `straight` is chosen for. It is the curve for a quantity that changes
+   * at a moment rather than across an interval, a headcount or a price, where a
+   * sloped edge claims a gradual change nothing measured.
+   *
    * **`share` draws each reading as a hundred percent**, so the bands are the
    * parts' shares and the top edge is flat. It answers "which part grew" where
    * the default answers "did the whole grow".
@@ -17540,9 +17648,13 @@ export type CustomElements = {
    *
    * - `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
@@ -17594,6 +17706,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.
    *
@@ -17616,6 +17733,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 Parts
    *
    * Custom selectors for styling elements within the component.
@@ -17957,27 +18092,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
@@ -18038,6 +18183,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.
    *
@@ -18060,11 +18210,29 @@ 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.
    *
-   * - `--bar-chart-axis`: The color of a single-series axis, taken from that series. (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`)
    *
@@ -22295,6 +22463,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
@@ -22356,6 +22532,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.
    *
@@ -22384,6 +22565,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.
@@ -24077,6 +24276,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.
    *
@@ -24113,6 +24317,24 @@ export type CustomElements = {
    * - `start`: Below the strip, at the leading edge: usually the oldest date.
    * - `summary`: Below the strip, in the middle: the reading over the range drawn.
    *
+   * ## 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.
@@ -24927,7 +25149,8 @@ export type CustomElements = {
    * `entries` picks which way to read that table. `series` is one entry per data
    * column, named by the header row, which is a line or a bar chart.
    * `categories` is one entry per body row, which is a donut: its slices are the
-   * rows and it has no axis to write their names along.
+   * rows and it has no axis to write their names along. `measures` drops the
+   * first data column, which is a scatter.
    *
    * **The table is resolved on the client and there is no server pass.**
    *
@@ -24939,6 +25162,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
@@ -25077,9 +25313,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
@@ -25132,6 +25379,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.
    *
@@ -25154,6 +25406,31 @@ 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-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
    *
    * Custom selectors for styling elements within the component.
@@ -29037,6 +29314,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.
    *
@@ -29059,6 +29341,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 a cell of a row is drawn in, which here is shifted by one.
+   *
+   * **A scatter's first plotted series is the table's *second* numeric
+   * column**, the first having been split off as the measure across. So the
+   * mixin's answer, which is right for a chart whose columns are its series in
+   * order, is one too high on every column here and names a color for the
+   * across, which is drawn in none. Left at that, the bubble painted the across
+   * column in series one, the color the points themselves are drawn in, and
+   * gave the series actually plotted series two.
+   *
+   * The across gets no dot at all rather than a shifted one. It is an axis and
+   * not a series: it has a scale under the plot with its name at the end of it,
+   * which is where a reader is told what it is.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -34952,12 +35252,28 @@ export type CustomElementsSolidJs = {
    * else draws every part in proportion to nothing. `LineChart` measures from its
    * own range because a line claims a position; a band claims an amount.
    *
+   * **And so it is not a streamgraph**, which is the near neighbor to name.
+   * A streamgraph moves its baseline to center the bands and reads as a river; it
+   * is a real form and it is the one thing the rule above refuses, so this
+   * carries no alias for it. What it has instead is `share`, which answers the
+   * question a streamgraph is usually reached for, how the composition changed,
+   * without giving up a floor a reader can measure against.
+   *
    * **Straight between readings unless asked otherwise.** A band's top edge is a
    * sum, and a curve fitted through one sum can pass under the curve fitted
    * through the sum beneath it, so a smoothed stack can draw a part as less than
    * nothing between two readings. Straight segments between ordered points stay
    * ordered. `curve="smooth"` is there for a stack that is read as a shape.
    *
+   * `curve="step"` falls on the safe side of that argument rather than being
+   * unanswered by it, and it is worth saying which side because a reader cannot
+   * tell from the argument alone. A step takes no value the readings do not have:
+   * it holds one, jumps at the midpoint, and holds the next. So two stepped edges
+   * that are ordered at every reading are ordered everywhere between them, which
+   * is what `straight` is chosen for. It is the curve for a quantity that changes
+   * at a moment rather than across an interval, a headcount or a price, where a
+   * sloped edge claims a gradual change nothing measured.
+   *
    * **`share` draws each reading as a hundred percent**, so the bands are the
    * parts' shares and the top edge is flat. It answers "which part grew" where
    * the default answers "did the whole grow".
@@ -34979,9 +35295,13 @@ export type CustomElementsSolidJs = {
    *
    * - `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
@@ -35033,6 +35353,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.
    *
@@ -35055,6 +35380,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 Parts
    *
    * Custom selectors for styling elements within the component.
@@ -35406,27 +35749,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
@@ -35487,6 +35840,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.
    *
@@ -35509,11 +35867,29 @@ 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.
    *
-   * - `--bar-chart-axis`: The color of a single-series axis, taken from that series. (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`)
    *
@@ -39802,6 +40178,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
@@ -39863,6 +40247,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.
    *
@@ -39891,6 +40280,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.
@@ -41604,6 +42011,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.
    *
@@ -41640,6 +42052,24 @@ export type CustomElementsSolidJs = {
    * - `start`: Below the strip, at the leading edge: usually the oldest date.
    * - `summary`: Below the strip, in the middle: the reading over the range drawn.
    *
+   * ## 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.
@@ -42470,7 +42900,8 @@ export type CustomElementsSolidJs = {
    * `entries` picks which way to read that table. `series` is one entry per data
    * column, named by the header row, which is a line or a bar chart.
    * `categories` is one entry per body row, which is a donut: its slices are the
-   * rows and it has no axis to write their names along.
+   * rows and it has no axis to write their names along. `measures` drops the
+   * first data column, which is a scatter.
    *
    * **The table is resolved on the client and there is no server pass.**
    *
@@ -42482,6 +42913,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
@@ -42623,9 +43067,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
@@ -42678,6 +43133,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.
    *
@@ -42700,6 +43160,31 @@ 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-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
    *
    * Custom selectors for styling elements within the component.
@@ -46648,6 +47133,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.
    *
@@ -46670,6 +47160,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 a cell of a row is drawn in, which here is shifted by one.
+   *
+   * **A scatter's first plotted series is the table's *second* numeric
+   * column**, the first having been split off as the measure across. So the
+   * mixin's answer, which is right for a chart whose columns are its series in
+   * order, is one too high on every column here and names a color for the
+   * across, which is drawn in none. Left at that, the bubble painted the across
+   * column in series one, the color the points themselves are drawn in, and
+   * gave the series actually plotted series two.
+   *
+   * The across gets no dot at all rather than a shifted one. It is an axis and
+   * not a series: it has a scale under the plot with its name at the end of it,
+   * which is where a reader is told what it is.
+   *
    * ## CSS Custom Properties
    *
    * CSS variables available for styling the component.
@@ -52250,7 +52758,7 @@ export type CustomElementsSolidJs = {
 };
 
 export type CustomCssProperties = {
-  /** 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;
@@ -52318,6 +52826,10 @@ export type CustomCssProperties = {
   "--heatmap-tone-success"?: (string) | undefined;
   /** What `warning` is worth. */
   "--heatmap-tone-warning"?: (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;
   /** Where the panel starts, measured from the bar above it. */
   "--megamenu-top"?: (string) | undefined;
   /** Where a bound sits on the arc, as a length along it. */
@@ -52354,10 +52866,6 @@ export type CustomCssProperties = {
   "--slider-marker-at"?: (string) | undefined;
   /** Where the filled span ends, as a percentage of the track. */
   "--slider-to"?: (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;
   /** Where a nested splitter crosses this one, as a percentage. */
   "--splitter-corner-at"?: (string) | undefined;
   /** Where the divider sits, as a percentage of the box. */