@fusion.dev/helix-headless 0.52.0 → 0.52.1

package/custom-elements.json

@@ -2350,7 +2350,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How a band's edge gets from one reading to the next.\n\nThree values, and the class doc argues for each: `straight` is absent and\nis the default, `smooth` is for a stack read as a shape and is the one that\ncan draw a part as less than nothing, `step` is for a quantity that changes\nat a moment and is ordered the way `straight` is.\n\nAbsent rather than defaulted because a reflecting property with a default\nwrites its attribute onto every host, including the ones nobody configured.",
+              "description": "How a band's edge gets from one reading to the next.\n\nThree values, and the class doc argues for each: `straight` is absent and\nis the default, `smooth` is for a stack read as a shape and is the one that\ncan draw a part as less than nothing, `step` is for a quantity that changes\nat a moment and is ordered the way `straight` is.\n\nAbsent rather than defaulted because a reflecting property with a default\nwrites its attribute onto every host, including the ones nobody configured.\nThe resting value therefore lives in the render, as `curve ?? 'straight'`.\n\n**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A\nline claims a position, so the bounded invention a monotone cubic makes is\na reading aid and costs nothing. A band claims an amount, and two sums\nsmoothed independently can cross, so the same aid here draws a part as less\nthan nothing. Same axis, different mark, different resting value.",
               "attribute": "curve",
               "reflects": true
             },
@@ -3136,7 +3136,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How a band's edge gets from one reading to the next.\n\nThree values, and the class doc argues for each: `straight` is absent and\nis the default, `smooth` is for a stack read as a shape and is the one that\ncan draw a part as less than nothing, `step` is for a quantity that changes\nat a moment and is ordered the way `straight` is.\n\nAbsent rather than defaulted because a reflecting property with a default\nwrites its attribute onto every host, including the ones nobody configured.",
+              "description": "How a band's edge gets from one reading to the next.\n\nThree values, and the class doc argues for each: `straight` is absent and\nis the default, `smooth` is for a stack read as a shape and is the one that\ncan draw a part as less than nothing, `step` is for a quantity that changes\nat a moment and is ordered the way `straight` is.\n\nAbsent rather than defaulted because a reflecting property with a default\nwrites its attribute onto every host, including the ones nobody configured.\nThe resting value therefore lives in the render, as `curve ?? 'straight'`.\n\n**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A\nline claims a position, so the bounded invention a monotone cubic makes is\na reading aid and costs nothing. A band claims an amount, and two sums\nsmoothed independently can cross, so the same aid here draws a part as less\nthan nothing. Same axis, different mark, different resting value.",
               "fieldName": "curve"
             },
             {
@@ -49864,7 +49864,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A curve invents the values between two\nreadings, which is why `straight` still exists, but the invention is\nbounded: the interpolation is monotone cubic, so it never leaves the band\nthe data sets and never introduces a peak or a trough the series does not\nhave. Within that bound the smoothed line is the easier one to follow\nacross a long series, and `straight` becomes the deliberate claim.\n\n**Absent rather than defaulted on the property**, because a reflecting\nproperty with a default writes its attribute onto every host anybody\nrenders, including the ones nobody configured.\n`line-chart-root.ssr.spec.ts` asserts the host carries only what the\nconsumer wrote. The default therefore lives where the path is built, as\n`curve ?? 'smooth'`.\n\n`step` claims the opposite of both, that a reading holds until the next.",
+              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A curve invents the values between two\nreadings, which is why `straight` still exists, but the invention is\nbounded: the interpolation is monotone cubic, so it never leaves the band\nthe data sets and never introduces a peak or a trough the series does not\nhave. Within that bound the smoothed line is the easier one to follow\nacross a long series, and `straight` becomes the deliberate claim.\n\n**Absent rather than defaulted on the property**, because a reflecting\nproperty with a default writes its attribute onto every host anybody\nrenders, including the ones nobody configured.\n`line-chart-root.ssr.spec.ts` asserts the host carries only what the\nconsumer wrote. The default therefore lives where the path is built, as\n`curve ?? 'smooth'`.\n\n`step` claims the opposite of both, that a reading holds until the next.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "attribute": "curve",
               "reflects": true
             },
@@ -50647,7 +50647,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A curve invents the values between two\nreadings, which is why `straight` still exists, but the invention is\nbounded: the interpolation is monotone cubic, so it never leaves the band\nthe data sets and never introduces a peak or a trough the series does not\nhave. Within that bound the smoothed line is the easier one to follow\nacross a long series, and `straight` becomes the deliberate claim.\n\n**Absent rather than defaulted on the property**, because a reflecting\nproperty with a default writes its attribute onto every host anybody\nrenders, including the ones nobody configured.\n`line-chart-root.ssr.spec.ts` asserts the host carries only what the\nconsumer wrote. The default therefore lives where the path is built, as\n`curve ?? 'smooth'`.\n\n`step` claims the opposite of both, that a reading holds until the next.",
+              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A curve invents the values between two\nreadings, which is why `straight` still exists, but the invention is\nbounded: the interpolation is monotone cubic, so it never leaves the band\nthe data sets and never introduces a peak or a trough the series does not\nhave. Within that bound the smoothed line is the easier one to follow\nacross a long series, and `straight` becomes the deliberate claim.\n\n**Absent rather than defaulted on the property**, because a reflecting\nproperty with a default writes its attribute onto every host anybody\nrenders, including the ones nobody configured.\n`line-chart-root.ssr.spec.ts` asserts the host carries only what the\nconsumer wrote. The default therefore lives where the path is built, as\n`curve ?? 'smooth'`.\n\n`step` claims the opposite of both, that a reading holds until the next.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "fieldName": "curve"
             },
             {
@@ -69615,11 +69615,11 @@
               "kind": "field",
               "name": "shape",
               "type": {
-                "text": "QrStyle"
+                "text": "QrStyle | undefined"
               },
-              "default": "'square'",
-              "description": "How the modules are drawn.\n\n`square` is the default and the only one that joins runs of adjacent\nmodules into a single subpath, which is what keeps a thousand modules to a\nhandful of nodes. `rounded` and `dots` draw each module on its own, because\nthe corners are the thing being drawn and a joined run has none in the\nmiddle. That cost is paid only by a code that asks for them.\n\nA scanner reads contrast between cells, not their shape, so all three\nscan. `dots` sits a little under half a module so neighbors do not touch,\nwhich is what makes it read as dots rather than as a softened square code.",
-              "attribute": "shape"
+              "description": "How the modules are drawn.\n\n`square` is the resting state and is written by not writing it, per the\nrule that a reflected property takes no default. It is also the only one\nthat joins runs of adjacent modules into a single subpath, which is what\nkeeps a thousand modules to a handful of nodes. `rounded` and `dots` draw\neach module on its own, because the corners are the thing being drawn and a\njoined run has none in the middle. That cost is paid only by a code that\nasks for them.\n\nA scanner reads contrast between cells, not their shape, so all three\nscan. `dots` sits a little under half a module so neighbors do not touch,\nwhich is what makes it read as dots rather than as a softened square code.",
+              "attribute": "shape",
+              "reflects": true
             },
             {
               "kind": "field",
@@ -70007,10 +70007,9 @@
             {
               "name": "shape",
               "type": {
-                "text": "QrStyle"
+                "text": "QrStyle | undefined"
               },
-              "default": "'square'",
-              "description": "How the modules are drawn.\n\n`square` is the default and the only one that joins runs of adjacent\nmodules into a single subpath, which is what keeps a thousand modules to a\nhandful of nodes. `rounded` and `dots` draw each module on its own, because\nthe corners are the thing being drawn and a joined run has none in the\nmiddle. That cost is paid only by a code that asks for them.\n\nA scanner reads contrast between cells, not their shape, so all three\nscan. `dots` sits a little under half a module so neighbors do not touch,\nwhich is what makes it read as dots rather than as a softened square code.",
+              "description": "How the modules are drawn.\n\n`square` is the resting state and is written by not writing it, per the\nrule that a reflected property takes no default. It is also the only one\nthat joins runs of adjacent modules into a single subpath, which is what\nkeeps a thousand modules to a handful of nodes. `rounded` and `dots` draw\neach module on its own, because the corners are the thing being drawn and a\njoined run has none in the middle. That cost is paid only by a code that\nasks for them.\n\nA scanner reads contrast between cells, not their shape, so all three\nscan. `dots` sits a little under half a module so neighbors do not touch,\nwhich is what makes it read as dots rather than as a softened square code.",
               "fieldName": "shape"
             },
             {
@@ -79128,7 +79127,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A straight segment asserts nothing about\nthe values between two readings and a curve invents them, which is why\n`straight` exists. What settles the default the other way is that the\ninvention is bounded: the interpolation is monotone cubic, so it never\nleaves the band the data sets and never introduces a peak or a trough the\nseries does not have. Within that bound the smoothed line is the easier one\nto follow across a long series, which is what the drawing is for. `straight`\nbecomes the claim a consumer makes deliberately rather than the one they get\nby saying nothing.\n\n**The property stays optional and the default lives in the render.** A\nreflecting property with a default writes its attribute onto every host\nanybody renders, including the ones nobody configured, which the SSR specs\nassert against. So the resting state is still the attribute's absence, and\n`curve ?? 'smooth'` is what reads it.\n\n`step` claims the opposite of both, that a reading holds until the next.\nBars ignore it, having no between to interpolate.",
+              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A straight segment asserts nothing about\nthe values between two readings and a curve invents them, which is why\n`straight` exists. What settles the default the other way is that the\ninvention is bounded: the interpolation is monotone cubic, so it never\nleaves the band the data sets and never introduces a peak or a trough the\nseries does not have. Within that bound the smoothed line is the easier one\nto follow across a long series, which is what the drawing is for. `straight`\nbecomes the claim a consumer makes deliberately rather than the one they get\nby saying nothing.\n\n**The property stays optional and the default lives in the render.** A\nreflecting property with a default writes its attribute onto every host\nanybody renders, including the ones nobody configured, which the SSR specs\nassert against. So the resting state is still the attribute's absence, and\n`curve ?? 'smooth'` is what reads it.\n\n`step` claims the opposite of both, that a reading holds until the next.\nBars ignore it, having no between to interpolate.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "attribute": "curve",
               "reflects": true
             },
@@ -79521,7 +79520,7 @@
               "type": {
                 "text": "Curve | undefined"
               },
-              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A straight segment asserts nothing about\nthe values between two readings and a curve invents them, which is why\n`straight` exists. What settles the default the other way is that the\ninvention is bounded: the interpolation is monotone cubic, so it never\nleaves the band the data sets and never introduces a peak or a trough the\nseries does not have. Within that bound the smoothed line is the easier one\nto follow across a long series, which is what the drawing is for. `straight`\nbecomes the claim a consumer makes deliberately rather than the one they get\nby saying nothing.\n\n**The property stays optional and the default lives in the render.** A\nreflecting property with a default writes its attribute onto every host\nanybody renders, including the ones nobody configured, which the SSR specs\nassert against. So the resting state is still the attribute's absence, and\n`curve ?? 'smooth'` is what reads it.\n\n`step` claims the opposite of both, that a reading holds until the next.\nBars ignore it, having no between to interpolate.",
+              "description": "How the line gets from one reading to the next.\n\n**`smooth` is the resting curve.** A straight segment asserts nothing about\nthe values between two readings and a curve invents them, which is why\n`straight` exists. What settles the default the other way is that the\ninvention is bounded: the interpolation is monotone cubic, so it never\nleaves the band the data sets and never introduces a peak or a trough the\nseries does not have. Within that bound the smoothed line is the easier one\nto follow across a long series, which is what the drawing is for. `straight`\nbecomes the claim a consumer makes deliberately rather than the one they get\nby saying nothing.\n\n**The property stays optional and the default lives in the render.** A\nreflecting property with a default writes its attribute onto every host\nanybody renders, including the ones nobody configured, which the SSR specs\nassert against. So the resting state is still the attribute's absence, and\n`curve ?? 'smooth'` is what reads it.\n\n`step` claims the opposite of both, that a reading holds until the next.\nBars ignore it, having no between to interpolate.\n\n**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a\nposition and a stacked band claims an amount: a curve fitted through one\nsum can pass under the curve fitted through the sum beneath it, so a\nsmoothed stack can draw a part as less than nothing. There is no such edge\nhere, which is what lets a line take the reading aid.",
               "fieldName": "curve"
             },
             {

package/dist/area-chart/root/area-chart-root.d.ts

@@ -115,6 +115,13 @@ export declare class HelixHeadlessAreaChart extends HelixHeadlessAreaChart_base
      *
      * Absent rather than defaulted because a reflecting property with a default
      * writes its attribute onto every host, including the ones nobody configured.
+     * The resting value therefore lives in the render, as `curve ?? 'straight'`.
+     *
+     * **`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+     * line claims a position, so the bounded invention a monotone cubic makes is
+     * a reading aid and costs nothing. A band claims an amount, and two sums
+     * smoothed independently can cross, so the same aid here draws a part as less
+     * than nothing. Same axis, different mark, different resting value.
      */
     curve?: Curve;
     /**

package/dist/line-chart/root/line-chart-root.d.ts

@@ -101,6 +101,12 @@ export declare class HelixHeadlessLineChart extends HelixHeadlessLineChart_base
      * `curve ?? 'smooth'`.
      *
      * `step` claims the opposite of both, that a reading holds until the next.
+     *
+     * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+     * position and a stacked band claims an amount: a curve fitted through one
+     * sum can pass under the curve fitted through the sum beneath it, so a
+     * smoothed stack can draw a part as less than nothing. There is no such edge
+     * here, which is what lets a line take the reading aid.
      */
     curve?: Curve;
     /**

package/dist/qr-code/root/qr-code-root.d.ts

@@ -64,17 +64,19 @@ export declare class HelixHeadlessQrCode extends HelixElement {
     /**
      * How the modules are drawn.
      *
-     * `square` is the default and the only one that joins runs of adjacent
-     * modules into a single subpath, which is what keeps a thousand modules to a
-     * handful of nodes. `rounded` and `dots` draw each module on its own, because
-     * the corners are the thing being drawn and a joined run has none in the
-     * middle. That cost is paid only by a code that asks for them.
+     * `square` is the resting state and is written by not writing it, per the
+     * rule that a reflected property takes no default. It is also the only one
+     * that joins runs of adjacent modules into a single subpath, which is what
+     * keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+     * each module on its own, because the corners are the thing being drawn and a
+     * joined run has none in the middle. That cost is paid only by a code that
+     * asks for them.
      *
      * A scanner reads contrast between cells, not their shape, so all three
      * scan. `dots` sits a little under half a module so neighbors do not touch,
      * which is what makes it read as dots rather than as a softened square code.
      */
-    shape: QrStyle;
+    shape?: QrStyle;
     /**
      * What the code encodes, which is usually a URL.
      */

package/dist/qr-code/root/qr-code-root.js

@@ -63,7 +63,6 @@ let HelixHeadlessQrCode = class HelixHeadlessQrCode extends HelixElement {
     constructor() {
         super(...arguments);
         this.label = '';
-        this.shape = 'square';
         this.value = '';
         this.logo = false;
     }
@@ -99,7 +98,7 @@ let HelixHeadlessQrCode = class HelixHeadlessQrCode extends HelixElement {
     >
       <path
         part="modules"
-        d=${pathFor(result.data, this.shape, 'body')}
+        d=${pathFor(result.data, this.shape ?? 'square', 'body')}
         transform="translate(${quiet} ${quiet})"
         fill="currentColor"
       />
@@ -134,7 +133,7 @@ __decorate([
     property()
 ], HelixHeadlessQrCode.prototype, "label", void 0);
 __decorate([
-    property()
+    property({ reflect: true })
 ], HelixHeadlessQrCode.prototype, "shape", void 0);
 __decorate([
     property()

package/dist/sparkline/root/sparkline-root.d.ts

@@ -70,6 +70,12 @@ export declare class HelixHeadlessSparkline extends HelixElement {
      *
      * `step` claims the opposite of both, that a reading holds until the next.
      * Bars ignore it, having no between to interpolate.
+     *
+     * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+     * position and a stacked band claims an amount: a curve fitted through one
+     * sum can pass under the curve fitted through the sum beneath it, so a
+     * smoothed stack can draw a part as less than nothing. There is no such edge
+     * here, which is what lets a line take the reading aid.
      */
     curve?: Curve;
     /**

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-headless",
   "description": "Headless component tier. Structure, accessibility, state, and form participation. No styling.",
-  "version": "0.52.0",
+  "version": "0.52.1",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -46,14 +46,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.52.0",
-    "@fusion.dev/helix-icons": "0.52.0",
+    "@fusion.dev/helix-core": "0.52.1",
+    "@fusion.dev/helix-icons": "0.52.1",
     "uqr": "^0.1.3"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.52.0",
-    "@fusion.dev/helix-testing": "0.52.0",
+    "@fusion.dev/helix-cem": "0.52.1",
+    "@fusion.dev/helix-testing": "0.52.1",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^4.1.0",

package/types/jsx.d.ts

@@ -756,7 +756,14 @@ can draw a part as less than nothing, `step` is for a quantity that changes
 at a moment and is ordered the way `straight` is.
 
 Absent rather than defaulted because a reflecting property with a default
-writes its attribute onto every host, including the ones nobody configured. */
+writes its attribute onto every host, including the ones nobody configured.
+The resting value therefore lives in the render, as `curve ?? 'straight'`.
+
+**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+line claims a position, so the bounded invention a monotone cubic makes is
+a reading aid and costs nothing. A band claims an amount, and two sums
+smoothed independently can cross, so the same aid here draws a part as less
+than nothing. Same axis, different mark, different resting value. */
   curve?: (HelixHeadlessAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -799,7 +806,14 @@ can draw a part as less than nothing, `step` is for a quantity that changes
 at a moment and is ordered the way `straight` is.
 
 Absent rather than defaulted because a reflecting property with a default
-writes its attribute onto every host, including the ones nobody configured. */
+writes its attribute onto every host, including the ones nobody configured.
+The resting value therefore lives in the render, as `curve ?? 'straight'`.
+
+**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+line claims a position, so the bounded invention a monotone cubic makes is
+a reading aid and costs nothing. A band claims an amount, and two sums
+smoothed independently can cross, so the same aid here draws a part as less
+than nothing. Same axis, different mark, different resting value. */
   "prop:curve"?: (HelixHeadlessAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -8494,7 +8508,13 @@ renders, including the ones nobody configured.
 consumer wrote. The default therefore lives where the path is built, as
 `curve ?? 'smooth'`.
 
-`step` claims the opposite of both, that a reading holds until the next. */
+`step` claims the opposite of both, that a reading holds until the next.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixHeadlessLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -8599,7 +8619,13 @@ renders, including the ones nobody configured.
 consumer wrote. The default therefore lives where the path is built, as
 `curve ?? 'smooth'`.
 
-`step` claims the opposite of both, that a reading holds until the next. */
+`step` claims the opposite of both, that a reading holds until the next.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   "prop:curve"?: (HelixHeadlessLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -11780,11 +11806,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   label?: (HelixHeadlessQrCode["label"]) | undefined;
   /** How the modules are drawn.
 
-`square` is the default and the only one that joins runs of adjacent
-modules into a single subpath, which is what keeps a thousand modules to a
-handful of nodes. `rounded` and `dots` draw each module on its own, because
-the corners are the thing being drawn and a joined run has none in the
-middle. That cost is paid only by a code that asks for them.
+`square` is the resting state and is written by not writing it, per the
+rule that a reflected property takes no default. It is also the only one
+that joins runs of adjacent modules into a single subpath, which is what
+keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+each module on its own, because the corners are the thing being drawn and a
+joined run has none in the middle. That cost is paid only by a code that
+asks for them.
 
 A scanner reads contrast between cells, not their shape, so all three
 scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -11810,11 +11838,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   "prop:label"?: (HelixHeadlessQrCode["label"]) | undefined;
   /** How the modules are drawn.
 
-`square` is the default and the only one that joins runs of adjacent
-modules into a single subpath, which is what keeps a thousand modules to a
-handful of nodes. `rounded` and `dots` draw each module on its own, because
-the corners are the thing being drawn and a joined run has none in the
-middle. That cost is paid only by a code that asks for them.
+`square` is the resting state and is written by not writing it, per the
+rule that a reflected property takes no default. It is also the only one
+that joins runs of adjacent modules into a single subpath, which is what
+keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+each module on its own, because the corners are the thing being drawn and a
+joined run has none in the middle. That cost is paid only by a code that
+asks for them.
 
 A scanner reads contrast between cells, not their shape, so all three
 scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -13066,7 +13096,13 @@ assert against. So the resting state is still the attribute's absence, and
 `curve ?? 'smooth'` is what reads it.
 
 `step` claims the opposite of both, that a reading holds until the next.
-Bars ignore it, having no between to interpolate. */
+Bars ignore it, having no between to interpolate.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixHeadlessSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.
 
@@ -13141,7 +13177,13 @@ assert against. So the resting state is still the attribute's absence, and
 `curve ?? 'smooth'` is what reads it.
 
 `step` claims the opposite of both, that a reading holds until the next.
-Bars ignore it, having no between to interpolate. */
+Bars ignore it, having no between to interpolate.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   "prop:curve"?: (HelixHeadlessSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.
 
@@ -18202,6 +18244,13 @@ export type CustomElements = {
    *
    * Absent rather than defaulted because a reflecting property with a default
    * writes its attribute onto every host, including the ones nobody configured.
+   * The resting value therefore lives in the render, as `curve ?? 'straight'`.
+   *
+   * **`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+   * line claims a position, so the bounded invention a monotone cubic makes is
+   * a reading aid and costs nothing. A band claims an amount, and two sums
+   * smoothed independently can cross, so the same aid here draws a part as less
+   * than nothing. Same axis, different mark, different resting value.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * The same three values `LineChart` takes, with the same fallback: a bare
@@ -25934,6 +25983,12 @@ export type CustomElements = {
    * `curve ?? 'smooth'`.
    *
    * `step` claims the opposite of both, that a reading holds until the next.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * Absent draws none, which is the honest default rather than a timid one: a
@@ -29288,11 +29343,13 @@ export type CustomElements = {
    * and a URL is a better name than "QR code" for a reader who cannot see it.
    * - `shape`: How the modules are drawn.
    *
-   * `square` is the default and the only one that joins runs of adjacent
-   * modules into a single subpath, which is what keeps a thousand modules to a
-   * handful of nodes. `rounded` and `dots` draw each module on its own, because
-   * the corners are the thing being drawn and a joined run has none in the
-   * middle. That cost is paid only by a code that asks for them.
+   * `square` is the resting state and is written by not writing it, per the
+   * rule that a reflected property takes no default. It is also the only one
+   * that joins runs of adjacent modules into a single subpath, which is what
+   * keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+   * each module on its own, because the corners are the thing being drawn and a
+   * joined run has none in the middle. That cost is paid only by a code that
+   * asks for them.
    *
    * A scanner reads contrast between cells, not their shape, so all three
    * scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -30866,6 +30923,12 @@ export type CustomElements = {
    *
    * `step` claims the opposite of both, that a reading holds until the next.
    * Bars ignore it, having no between to interpolate.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `for`: The id of a table to read instead, when there is one behind the line.
    *
    * The first column of numbers is the series drawn. This wins over `values`,
@@ -36093,6 +36156,13 @@ export type CustomElementsSolidJs = {
    *
    * Absent rather than defaulted because a reflecting property with a default
    * writes its attribute onto every host, including the ones nobody configured.
+   * The resting value therefore lives in the render, as `curve ?? 'straight'`.
+   *
+   * **`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+   * line claims a position, so the bounded invention a monotone cubic makes is
+   * a reading aid and costs nothing. A band claims an amount, and two sums
+   * smoothed independently can cross, so the same aid here draws a part as less
+   * than nothing. Same axis, different mark, different resting value.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * The same three values `LineChart` takes, with the same fallback: a bare
@@ -43932,6 +44002,12 @@ export type CustomElementsSolidJs = {
    * `curve ?? 'smooth'`.
    *
    * `step` claims the opposite of both, that a reading holds until the next.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `gridlines`: Which rules are drawn across the plot, if any.
    *
    * Absent draws none, which is the honest default rather than a timid one: a
@@ -47338,11 +47414,13 @@ export type CustomElementsSolidJs = {
    * and a URL is a better name than "QR code" for a reader who cannot see it.
    * - `shape`: How the modules are drawn.
    *
-   * `square` is the default and the only one that joins runs of adjacent
-   * modules into a single subpath, which is what keeps a thousand modules to a
-   * handful of nodes. `rounded` and `dots` draw each module on its own, because
-   * the corners are the thing being drawn and a joined run has none in the
-   * middle. That cost is paid only by a code that asks for them.
+   * `square` is the resting state and is written by not writing it, per the
+   * rule that a reflected property takes no default. It is also the only one
+   * that joins runs of adjacent modules into a single subpath, which is what
+   * keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+   * each module on its own, because the corners are the thing being drawn and a
+   * joined run has none in the middle. That cost is paid only by a code that
+   * asks for them.
    *
    * A scanner reads contrast between cells, not their shape, so all three
    * scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -48943,6 +49021,12 @@ export type CustomElementsSolidJs = {
    *
    * `step` claims the opposite of both, that a reading holds until the next.
    * Bars ignore it, having no between to interpolate.
+   *
+   * **`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+   * position and a stacked band claims an amount: a curve fitted through one
+   * sum can pass under the curve fitted through the sum beneath it, so a
+   * smoothed stack can draw a part as less than nothing. There is no such edge
+   * here, which is what lets a line take the reading aid.
    * - `for`: The id of a table to read instead, when there is one behind the line.
    *
    * The first column of numbers is the series drawn. This wins over `values`,

package/types/vue.d.ts

@@ -408,7 +408,14 @@ can draw a part as less than nothing, `step` is for a quantity that changes
 at a moment and is ordered the way `straight` is.
 
 Absent rather than defaulted because a reflecting property with a default
-writes its attribute onto every host, including the ones nobody configured. */
+writes its attribute onto every host, including the ones nobody configured.
+The resting value therefore lives in the render, as `curve ?? 'straight'`.
+
+**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+line claims a position, so the bounded invention a monotone cubic makes is
+a reading aid and costs nothing. A band claims an amount, and two sums
+smoothed independently can cross, so the same aid here draws a part as less
+than nothing. Same axis, different mark, different resting value. */
   curve?: (HelixHeadlessAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -4360,7 +4367,13 @@ renders, including the ones nobody configured.
 consumer wrote. The default therefore lives where the path is built, as
 `curve ?? 'smooth'`.
 
-`step` claims the opposite of both, that a reading holds until the next. */
+`step` claims the opposite of both, that a reading holds until the next.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixHeadlessLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -6038,11 +6051,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   label?: (HelixHeadlessQrCode["label"]) | undefined;
   /** How the modules are drawn.
 
-`square` is the default and the only one that joins runs of adjacent
-modules into a single subpath, which is what keeps a thousand modules to a
-handful of nodes. `rounded` and `dots` draw each module on its own, because
-the corners are the thing being drawn and a joined run has none in the
-middle. That cost is paid only by a code that asks for them.
+`square` is the resting state and is written by not writing it, per the
+rule that a reflected property takes no default. It is also the only one
+that joins runs of adjacent modules into a single subpath, which is what
+keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+each module on its own, because the corners are the thing being drawn and a
+joined run has none in the middle. That cost is paid only by a code that
+asks for them.
 
 A scanner reads contrast between cells, not their shape, so all three
 scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -6693,7 +6708,13 @@ assert against. So the resting state is still the attribute's absence, and
 `curve ?? 'smooth'` is what reads it.
 
 `step` claims the opposite of both, that a reading holds until the next.
-Bars ignore it, having no between to interpolate. */
+Bars ignore it, having no between to interpolate.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixHeadlessSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.