@fusion.dev/helix 0.52.0 → 0.52.1

package/custom-elements.json

@@ -1387,7 +1387,7 @@
               "type": {
                 "text": "'elevated' | 'filled' | undefined"
               },
-              "description": "Which rung of the surface ladder the band rides.\n\n`filled` is the resting one, a well sunk below the page. `elevated` brings\nit up to the surface step, for a band that reads as part of the furniture\nrather than as a slot cut into it.\n\n**This was `tone=\"surface\"`**, which put an elevation on the axis that says\nwhat a thing means. The band's own doc admitted it, calling `surface` the\none value that was not a color. A band can be `info` and elevated at the\nsame time, and two values that can both be true are two axes.\n\nStyled and not headless, because a rung of a ladder is paint: the headless\ntier has no stylesheet to sit a band on. `tone` crosses because meaning\nsurvives having nothing to paint with, and it is the only axis that does.",
+              "description": "Which rung of the surface ladder the band rides.\n\n`filled` is the resting one, a well sunk below the page. `elevated` brings\nit up to the surface step, for a band that reads as part of the furniture\nrather than as a slot cut into it.\n\n**`separation` and not `tone`, because a rung is not a meaning.** A band\ncan be `info` and elevated at the same time, and two values that can both\nbe true are two axes, which is the test the registry answers to.\n\nStyled and not headless, because a rung of a ladder is paint: the headless\ntier has no stylesheet to sit a band on. `tone` crosses because meaning\nsurvives having nothing to paint with, and it is the only axis that does.",
               "attribute": "separation",
               "reflects": true
             },
@@ -1827,7 +1827,7 @@
               "type": {
                 "text": "'elevated' | 'filled' | undefined"
               },
-              "description": "Which rung of the surface ladder the band rides.\n\n`filled` is the resting one, a well sunk below the page. `elevated` brings\nit up to the surface step, for a band that reads as part of the furniture\nrather than as a slot cut into it.\n\n**This was `tone=\"surface\"`**, which put an elevation on the axis that says\nwhat a thing means. The band's own doc admitted it, calling `surface` the\none value that was not a color. A band can be `info` and elevated at the\nsame time, and two values that can both be true are two axes.\n\nStyled and not headless, because a rung of a ladder is paint: the headless\ntier has no stylesheet to sit a band on. `tone` crosses because meaning\nsurvives having nothing to paint with, and it is the only axis that does.",
+              "description": "Which rung of the surface ladder the band rides.\n\n`filled` is the resting one, a well sunk below the page. `elevated` brings\nit up to the surface step, for a band that reads as part of the furniture\nrather than as a slot cut into it.\n\n**`separation` and not `tone`, because a rung is not a meaning.** A band\ncan be `info` and elevated at the same time, and two values that can both\nbe true are two axes, which is the test the registry answers to.\n\nStyled and not headless, because a rung of a ladder is paint: the headless\ntier has no stylesheet to sit a band on. `tone` crosses because meaning\nsurvives having nothing to paint with, and it is the only axis that does.",
               "fieldName": "separation"
             },
             {
@@ -2899,7 +2899,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,
               "inheritedFrom": {
@@ -3681,7 +3681,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",
               "inheritedFrom": {
                 "name": "HelixHeadlessAreaChart",
@@ -62505,7 +62505,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,
               "inheritedFrom": {
@@ -63243,7 +63243,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",
               "inheritedFrom": {
                 "name": "HelixHeadlessLineChart",
@@ -70954,7 +70954,7 @@
               "type": {
                 "text": "'subtle' | undefined"
               },
-              "description": "How much ink the reading claims.\n\n`subtle` is the reading as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a dashboard of several meters\nwhere one is the number being watched and the rest are context, which is a\nfact about the region rather than about any one of them.\n\n**One value and not the four.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `outlined` earns its\nplace in `BarChart`, which keeps the area and fades it toward the page, only\nbecause a chart has other series for the outlined one to be a *different\nkind of fact from* (a forecast, a target, a budget). A meter reports one\nquantity against its own range, and the bands it carries already say which\npart of that range it is in, so there is no second kind of fact for an\noutline to name. `solid` is the resting state and is written by not writing\nit, per the rule that a reflected property takes no default.",
+              "description": "How much ink the reading claims.\n\n`subtle` is the reading as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a dashboard of several meters\nwhere one is the number being watched and the rest are context, which is a\nfact about the region rather than about any one of them.\n\n**One value of the five.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `muted` is the quiet\nink `Text` takes and a reading draws a fill rather than ink, so `subtle` is\nthe whole of what quiet means here. `outlined` earns its\nplace in `BarChart`, which keeps the area and fades it toward the page, only\nbecause a chart has other series for the outlined one to be a *different\nkind of fact from* (a forecast, a target, a budget). A meter reports one\nquantity against its own range, and the bands it carries already say which\npart of that range it is in, so there is no second kind of fact for an\noutline to name. `solid` is the resting state and is written by not writing\nit, per the rule that a reflected property takes no default.",
               "attribute": "emphasis",
               "reflects": true
             },
@@ -71567,7 +71567,7 @@
               "type": {
                 "text": "'subtle' | undefined"
               },
-              "description": "How much ink the reading claims.\n\n`subtle` is the reading as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a dashboard of several meters\nwhere one is the number being watched and the rest are context, which is a\nfact about the region rather than about any one of them.\n\n**One value and not the four.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `outlined` earns its\nplace in `BarChart`, which keeps the area and fades it toward the page, only\nbecause a chart has other series for the outlined one to be a *different\nkind of fact from* (a forecast, a target, a budget). A meter reports one\nquantity against its own range, and the bands it carries already say which\npart of that range it is in, so there is no second kind of fact for an\noutline to name. `solid` is the resting state and is written by not writing\nit, per the rule that a reflected property takes no default.",
+              "description": "How much ink the reading claims.\n\n`subtle` is the reading as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a dashboard of several meters\nwhere one is the number being watched and the rest are context, which is a\nfact about the region rather than about any one of them.\n\n**One value of the five.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `muted` is the quiet\nink `Text` takes and a reading draws a fill rather than ink, so `subtle` is\nthe whole of what quiet means here. `outlined` earns its\nplace in `BarChart`, which keeps the area and fades it toward the page, only\nbecause a chart has other series for the outlined one to be a *different\nkind of fact from* (a forecast, a target, a budget). A meter reports one\nquantity against its own range, and the bands it carries already say which\npart of that range it is in, so there is no second kind of fact for an\noutline to name. `solid` is the resting state and is written by not writing\nit, per the rule that a reflected property takes no default.",
               "fieldName": "emphasis"
             },
             {
@@ -79712,7 +79712,7 @@
               "type": {
                 "text": "'lg' | 'sm' | undefined"
               },
-              "description": "Diameter relative to the surrounding text.\n\nReflected because the stylesheet selects on it. The mesh is chosen from the\nrendered box rather than from this, so `--orb-size` and a consumer's own\n`inline-size` get the same treatment as the three named steps.",
+              "description": "Diameter relative to the surrounding text.\n\nReflected because the stylesheet selects on it. The mesh is chosen from the\nrendered box rather than from this, so `--orb-size` and a consumer's own\n`inline-size` get the same treatment as the named steps.",
               "attribute": "size",
               "reflects": true
             },
@@ -80334,7 +80334,7 @@
               "type": {
                 "text": "'lg' | 'sm' | undefined"
               },
-              "description": "Diameter relative to the surrounding text.\n\nReflected because the stylesheet selects on it. The mesh is chosen from the\nrendered box rather than from this, so `--orb-size` and a consumer's own\n`inline-size` get the same treatment as the three named steps.",
+              "description": "Diameter relative to the surrounding text.\n\nReflected because the stylesheet selects on it. The mesh is chosen from the\nrendered box rather than from this, so `--orb-size` and a consumer's own\n`inline-size` get the same treatment as the named steps.",
               "fieldName": "size"
             },
             {
@@ -87176,7 +87176,7 @@
               "type": {
                 "text": "'subtle' | undefined"
               },
-              "description": "How much ink the bar claims.\n\n`subtle` is the bar as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a background task, which has to\nbe visible and must not compete with what the reader is actually looking at.\n\n**One value and not the four.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `outlined` is the\ninteresting refusal: `BarChart` earns it by keeping the area and fading it\ntoward the page, so an outlined column still encodes its value and stands as\na *different kind of fact* from the series beside it (a forecast, a target,\na budget). A progress bar is alone in its region and has nothing to differ\nfrom, so an outline there costs legibility and buys no distinction. `solid`\nis the resting state and is written by not writing it, per the rule that a\nreflected property takes no default.",
+              "description": "How much ink the bar claims.\n\n`subtle` is the bar as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a background task, which has to\nbe visible and must not compete with what the reader is actually looking at.\n\n**One value of the five.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `muted` is the quiet\nink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the\nwhole of what quiet means here. `outlined` is the\ninteresting refusal: `BarChart` earns it by keeping the area and fading it\ntoward the page, so an outlined column still encodes its value and stands as\na *different kind of fact* from the series beside it (a forecast, a target,\na budget). A progress bar is alone in its region and has nothing to differ\nfrom, so an outline there costs legibility and buys no distinction. `solid`\nis the resting state and is written by not writing it, per the rule that a\nreflected property takes no default.",
               "attribute": "emphasis",
               "reflects": true
             },
@@ -87624,7 +87624,7 @@
               "type": {
                 "text": "'subtle' | undefined"
               },
-              "description": "How much ink the bar claims.\n\n`subtle` is the bar as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a background task, which has to\nbe visible and must not compete with what the reader is actually looking at.\n\n**One value and not the four.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `outlined` is the\ninteresting refusal: `BarChart` earns it by keeping the area and fading it\ntoward the page, so an outlined column still encodes its value and stands as\na *different kind of fact* from the series beside it (a forecast, a target,\na budget). A progress bar is alone in its region and has nothing to differ\nfrom, so an outline there costs legibility and buys no distinction. `solid`\nis the resting state and is written by not writing it, per the rule that a\nreflected property takes no default.",
+              "description": "How much ink the bar claims.\n\n`subtle` is the bar as a wash of its own color: still legible, no longer\nthe loudest thing in the region. The case is a background task, which has to\nbe visible and must not compete with what the reader is actually looking at.\n\n**One value of the five.** `ghost` would leave a track with nothing in\nit, which is not a quiet reading but an absent one. `muted` is the quiet\nink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the\nwhole of what quiet means here. `outlined` is the\ninteresting refusal: `BarChart` earns it by keeping the area and fading it\ntoward the page, so an outlined column still encodes its value and stands as\na *different kind of fact* from the series beside it (a forecast, a target,\na budget). A progress bar is alone in its region and has nothing to differ\nfrom, so an outline there costs legibility and buys no distinction. `solid`\nis the resting state and is written by not writing it, per the rule that a\nreflected property takes no default.",
               "fieldName": "emphasis"
             },
             {
@@ -87932,11 +87932,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.",
+              "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,
               "inheritedFrom": {
                 "name": "HelixHeadlessQrCode",
                 "module": "src/qr-code/root/qr-code-root.ts"
@@ -88443,10 +88443,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",
               "inheritedFrom": {
                 "name": "HelixHeadlessQrCode",
@@ -98391,7 +98390,7 @@
               "type": {
                 "text": "'ghost' | undefined"
               },
-              "description": "How much ink the trigger claims.\n\n**The first field in this library to take an axis, and the case that asked\nfor it is a control in a row rather than a control on a form.** A chat's\ncomposer wants a model picker beside an attachment button and a send button:\nat the field's own frame it is 40 pixels of bordered well in a line of 28\npixel glyphs, and it reads as the composer's subject rather than as one of\nits tools. The same is true of a select in a toolbar, in a table header, or\ninside a sentence.\n\n- Unset is the frame an `Input` wears, which is what a form wants: a control\n  that looks like a button among fields reads as an action rather than an\n  answer.\n- `ghost` drops the fill and the edge, takes the width of what is in it, and\n  puts the mark against the value instead of at the far end of the control.\n\n**`emphasis` and not `separation`, which the registry decides rather than\ntaste.** Emphasis is asked of controls, how loud this one is; separation is\nasked of containers, where the surface ends. A trigger is a control, and a\nfamily may not declare both. Two of the four values are refused: `solid` and\n`subtle` are a button's way of being the one thing to press, which is not a\nthing an answer should ever be.\n\n**The other three fields want this too and do not have it yet.** `Input`,\n`Textarea` and `Combobox` wear the same frame from the same shared\nstylesheet, and an inline one of each is as reasonable as an inline select.\nThey are left alone rather than swept, because each has a different thing\ninside the frame and guessing at three is how an axis ends up meaning four\nthings, which is the fault `appearance` was retired for.",
+              "description": "How much ink the trigger claims.\n\n**The first field in this library to take an axis, and the case that asked\nfor it is a control in a row rather than a control on a form.** A chat's\ncomposer wants a model picker beside an attachment button and a send button:\nat the field's own frame it is 40 pixels of bordered well in a line of 28\npixel glyphs, and it reads as the composer's subject rather than as one of\nits tools. The same is true of a select in a toolbar, in a table header, or\ninside a sentence.\n\n- Unset is the frame an `Input` wears, which is what a form wants: a control\n  that looks like a button among fields reads as an action rather than an\n  answer.\n- `ghost` drops the fill and the edge, takes the width of what is in it, and\n  puts the mark against the value instead of at the far end of the control.\n\n**`emphasis` and not `separation`, which the registry decides rather than\ntaste.** Emphasis is asked of controls, how loud this one is; separation is\nasked of containers, where the surface ends. A trigger is a control, and a\nfamily may not declare both. Three of the five values are refused: `solid`\nand `subtle` are a button's way of being the one thing to press, which is\nnot a thing an answer should ever be, and `muted` is the quiet ink `Text`\ntakes, where a trigger's loudness is its frame rather than its ink.\n`outlined` is what the unset frame already draws, so writing it would be\nwriting the resting state out.\n\n**The other three fields want this too and do not have it yet.** `Input`,\n`Textarea` and `Combobox` wear the same frame from the same shared\nstylesheet, and an inline one of each is as reasonable as an inline select.\nThey are left alone rather than swept, because each has a different thing\ninside the frame and guessing at three is how an axis ends up meaning four\nthings, which is the fault `appearance` was retired for.",
               "attribute": "emphasis",
               "reflects": true
             },
@@ -99578,7 +99577,7 @@
               "type": {
                 "text": "'ghost' | undefined"
               },
-              "description": "How much ink the trigger claims.\n\n**The first field in this library to take an axis, and the case that asked\nfor it is a control in a row rather than a control on a form.** A chat's\ncomposer wants a model picker beside an attachment button and a send button:\nat the field's own frame it is 40 pixels of bordered well in a line of 28\npixel glyphs, and it reads as the composer's subject rather than as one of\nits tools. The same is true of a select in a toolbar, in a table header, or\ninside a sentence.\n\n- Unset is the frame an `Input` wears, which is what a form wants: a control\n  that looks like a button among fields reads as an action rather than an\n  answer.\n- `ghost` drops the fill and the edge, takes the width of what is in it, and\n  puts the mark against the value instead of at the far end of the control.\n\n**`emphasis` and not `separation`, which the registry decides rather than\ntaste.** Emphasis is asked of controls, how loud this one is; separation is\nasked of containers, where the surface ends. A trigger is a control, and a\nfamily may not declare both. Two of the four values are refused: `solid` and\n`subtle` are a button's way of being the one thing to press, which is not a\nthing an answer should ever be.\n\n**The other three fields want this too and do not have it yet.** `Input`,\n`Textarea` and `Combobox` wear the same frame from the same shared\nstylesheet, and an inline one of each is as reasonable as an inline select.\nThey are left alone rather than swept, because each has a different thing\ninside the frame and guessing at three is how an axis ends up meaning four\nthings, which is the fault `appearance` was retired for.",
+              "description": "How much ink the trigger claims.\n\n**The first field in this library to take an axis, and the case that asked\nfor it is a control in a row rather than a control on a form.** A chat's\ncomposer wants a model picker beside an attachment button and a send button:\nat the field's own frame it is 40 pixels of bordered well in a line of 28\npixel glyphs, and it reads as the composer's subject rather than as one of\nits tools. The same is true of a select in a toolbar, in a table header, or\ninside a sentence.\n\n- Unset is the frame an `Input` wears, which is what a form wants: a control\n  that looks like a button among fields reads as an action rather than an\n  answer.\n- `ghost` drops the fill and the edge, takes the width of what is in it, and\n  puts the mark against the value instead of at the far end of the control.\n\n**`emphasis` and not `separation`, which the registry decides rather than\ntaste.** Emphasis is asked of controls, how loud this one is; separation is\nasked of containers, where the surface ends. A trigger is a control, and a\nfamily may not declare both. Three of the five values are refused: `solid`\nand `subtle` are a button's way of being the one thing to press, which is\nnot a thing an answer should ever be, and `muted` is the quiet ink `Text`\ntakes, where a trigger's loudness is its frame rather than its ink.\n`outlined` is what the unset frame already draws, so writing it would be\nwriting the resting state out.\n\n**The other three fields want this too and do not have it yet.** `Input`,\n`Textarea` and `Combobox` wear the same frame from the same shared\nstylesheet, and an inline one of each is as reasonable as an inline select.\nThey are left alone rather than swept, because each has a different thing\ninside the frame and guessing at three is how an axis ends up meaning four\nthings, which is the fault `appearance` was retired for.",
               "fieldName": "emphasis"
             },
             {
@@ -103366,7 +103365,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,
               "inheritedFrom": {
@@ -103811,7 +103810,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",
               "inheritedFrom": {
                 "name": "HelixHeadlessSparkline",

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

@@ -25,10 +25,9 @@ export declare class HelixAnnouncement extends HelixHeadlessAnnouncement {
      * it up to the surface step, for a band that reads as part of the furniture
      * rather than as a slot cut into it.
      *
-     * **This was `tone="surface"`**, which put an elevation on the axis that says
-     * what a thing means. The band's own doc admitted it, calling `surface` the
-     * one value that was not a color. A band can be `info` and elevated at the
-     * same time, and two values that can both be true are two axes.
+     * **`separation` and not `tone`, because a rung is not a meaning.** A band
+     * can be `info` and elevated at the same time, and two values that can both
+     * be true are two axes, which is the test the registry answers to.
      *
      * Styled and not headless, because a rung of a ladder is paint: the headless
      * tier has no stylesheet to sit a band on. `tone` crosses because meaning

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

@@ -64,8 +64,10 @@ export declare class HelixMeter extends HelixHeadlessMeter {
      * where one is the number being watched and the rest are context, which is a
      * fact about the region rather than about any one of them.
      *
-     * **One value and not the four.** `ghost` would leave a track with nothing in
-     * it, which is not a quiet reading but an absent one. `outlined` earns its
+     * **One value of the five.** `ghost` would leave a track with nothing in
+     * it, which is not a quiet reading but an absent one. `muted` is the quiet
+     * ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+     * the whole of what quiet means here. `outlined` earns its
      * place in `BarChart`, which keeps the area and fades it toward the page, only
      * because a chart has other series for the outlined one to be a *different
      * kind of fact from* (a forecast, a target, a budget). A meter reports one

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

@@ -68,7 +68,7 @@ export declare class HelixOrb extends HelixElement {
      *
      * Reflected because the stylesheet selects on it. The mesh is chosen from the
      * rendered box rather than from this, so `--orb-size` and a consumer's own
-     * `inline-size` get the same treatment as the three named steps.
+     * `inline-size` get the same treatment as the named steps.
      */
     size?: 'lg' | 'sm';
     /**

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

@@ -33,8 +33,10 @@ export declare class HelixProgress extends HelixHeadlessProgress {
      * the loudest thing in the region. The case is a background task, which has to
      * be visible and must not compete with what the reader is actually looking at.
      *
-     * **One value and not the four.** `ghost` would leave a track with nothing in
-     * it, which is not a quiet reading but an absent one. `outlined` is the
+     * **One value of the five.** `ghost` would leave a track with nothing in
+     * it, which is not a quiet reading but an absent one. `muted` is the quiet
+     * ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+     * whole of what quiet means here. `outlined` is the
      * interesting refusal: `BarChart` earns it by keeping the area and fading it
      * toward the page, so an outlined column still encodes its value and stands as
      * a *different kind of fact* from the series beside it (a forecast, a target,

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

@@ -51,9 +51,12 @@ export declare class HelixSelect extends HelixHeadlessSelect {
      * **`emphasis` and not `separation`, which the registry decides rather than
      * taste.** Emphasis is asked of controls, how loud this one is; separation is
      * asked of containers, where the surface ends. A trigger is a control, and a
-     * family may not declare both. Two of the four values are refused: `solid` and
-     * `subtle` are a button's way of being the one thing to press, which is not a
-     * thing an answer should ever be.
+     * family may not declare both. Three of the five values are refused: `solid`
+     * and `subtle` are a button's way of being the one thing to press, which is
+     * not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+     * takes, where a trigger's loudness is its frame rather than its ink.
+     * `outlined` is what the unset frame already draws, so writing it would be
+     * writing the resting state out.
      *
      * **The other three fields want this too and do not have it yet.** `Input`,
      * `Textarea` and `Combobox` wear the same frame from the same shared

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix",
   "description": "Styled component tier. Extends the headless tier with token-driven presentation.",
-  "version": "0.52.0",
+  "version": "0.52.1",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -47,14 +47,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.52.0",
-    "@fusion.dev/helix-headless": "0.52.0",
-    "@fusion.dev/helix-styles": "0.52.0"
+    "@fusion.dev/helix-core": "0.52.1",
+    "@fusion.dev/helix-headless": "0.52.1",
+    "@fusion.dev/helix-styles": "0.52.1"
   },
   "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

@@ -621,10 +621,9 @@ export type HelixAnnouncementProps = {
 it up to the surface step, for a band that reads as part of the furniture
 rather than as a slot cut into it.
 
-**This was `tone="surface"`**, which put an elevation on the axis that says
-what a thing means. The band's own doc admitted it, calling `surface` the
-one value that was not a color. A band can be `info` and elevated at the
-same time, and two values that can both be true are two axes.
+**`separation` and not `tone`, because a rung is not a meaning.** A band
+can be `info` and elevated at the same time, and two values that can both
+be true are two axes, which is the test the registry answers to.
 
 Styled and not headless, because a rung of a ladder is paint: the headless
 tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -680,10 +679,9 @@ export type HelixAnnouncementSolidJsProps = {
 it up to the surface step, for a band that reads as part of the furniture
 rather than as a slot cut into it.
 
-**This was `tone="surface"`**, which put an elevation on the axis that says
-what a thing means. The band's own doc admitted it, calling `surface` the
-one value that was not a color. A band can be `info` and elevated at the
-same time, and two values that can both be true are two axes.
+**`separation` and not `tone`, because a rung is not a meaning.** A band
+can be `info` and elevated at the same time, and two values that can both
+be true are two axes, which is the test the registry answers to.
 
 Styled and not headless, because a rung of a ladder is paint: the headless
 tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -944,7 +942,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?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -987,7 +992,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"?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -10203,7 +10215,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?: (HelixLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -10348,7 +10366,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"?: (HelixLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -11384,8 +11408,10 @@ the loudest thing in the region. The case is a dashboard of several meters
 where one is the number being watched and the rest are context, which is a
 fact about the region rather than about any one of them.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` earns its
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+the whole of what quiet means here. `outlined` earns its
 place in `BarChart`, which keeps the area and fades it toward the page, only
 because a chart has other series for the outlined one to be a *different
 kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -11494,8 +11520,10 @@ the loudest thing in the region. The case is a dashboard of several meters
 where one is the number being watched and the rest are context, which is a
 fact about the region rather than about any one of them.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` earns its
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+the whole of what quiet means here. `outlined` earns its
 place in `BarChart`, which keeps the area and fades it toward the page, only
 because a chart has other series for the outlined one to be a *different
 kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -12578,7 +12606,7 @@ the name of the tool being run, or the file being read. */
 
 Reflected because the stylesheet selects on it. The mesh is chosen from the
 rendered box rather than from this, so `--orb-size` and a consumer's own
-`inline-size` get the same treatment as the three named steps. */
+`inline-size` get the same treatment as the named steps. */
   size?: (HelixOrb["size"]) | undefined;
   /** What the agent is doing.
 
@@ -12604,7 +12632,7 @@ the name of the tool being run, or the file being read. */
 
 Reflected because the stylesheet selects on it. The mesh is chosen from the
 rendered box rather than from this, so `--orb-size` and a consumer's own
-`inline-size` get the same treatment as the three named steps. */
+`inline-size` get the same treatment as the named steps. */
   "prop:size"?: (HelixOrb["size"]) | undefined;
   /** What the agent is doing.
 
@@ -13480,8 +13508,10 @@ export type HelixProgressProps = {
 the loudest thing in the region. The case is a background task, which has to
 be visible and must not compete with what the reader is actually looking at.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` is the
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+whole of what quiet means here. `outlined` is the
 interesting refusal: `BarChart` earns it by keeping the area and fading it
 toward the page, so an outlined column still encodes its value and stands as
 a *different kind of fact* from the series beside it (a forecast, a target,
@@ -13568,8 +13598,10 @@ export type HelixProgressSolidJsProps = {
 the loudest thing in the region. The case is a background task, which has to
 be visible and must not compete with what the reader is actually looking at.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` is the
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+whole of what quiet means here. `outlined` is the
 interesting refusal: `BarChart` earns it by keeping the area and fading it
 toward the page, so an outlined column still encodes its value and stands as
 a *different kind of fact* from the series beside it (a forecast, a target,
@@ -13670,11 +13702,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   label?: (HelixQrCode["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,
@@ -13700,11 +13734,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   "prop:label"?: (HelixQrCode["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,
@@ -15122,9 +15158,12 @@ inside a sentence.
 **`emphasis` and not `separation`, which the registry decides rather than
 taste.** Emphasis is asked of controls, how loud this one is; separation is
 asked of containers, where the surface ends. A trigger is a control, and a
-family may not declare both. Two of the four values are refused: `solid` and
-`subtle` are a button's way of being the one thing to press, which is not a
-thing an answer should ever be.
+family may not declare both. Three of the five values are refused: `solid`
+and `subtle` are a button's way of being the one thing to press, which is
+not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+takes, where a trigger's loudness is its frame rather than its ink.
+`outlined` is what the unset frame already draws, so writing it would be
+writing the resting state out.
 
 **The other three fields want this too and do not have it yet.** `Input`,
 `Textarea` and `Combobox` wear the same frame from the same shared
@@ -15262,9 +15301,12 @@ inside a sentence.
 **`emphasis` and not `separation`, which the registry decides rather than
 taste.** Emphasis is asked of controls, how loud this one is; separation is
 asked of containers, where the surface ends. A trigger is a control, and a
-family may not declare both. Two of the four values are refused: `solid` and
-`subtle` are a button's way of being the one thing to press, which is not a
-thing an answer should ever be.
+family may not declare both. Three of the five values are refused: `solid`
+and `subtle` are a button's way of being the one thing to press, which is
+not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+takes, where a trigger's loudness is its frame rather than its ink.
+`outlined` is what the unset frame already draws, so writing it would be
+writing the resting state out.
 
 **The other three fields want this too and do not have it yet.** `Input`,
 `Textarea` and `Combobox` wear the same frame from the same shared
@@ -15734,7 +15776,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?: (HelixSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.
 
@@ -15867,7 +15915,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"?: (HelixSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.
 
@@ -20999,10 +21053,9 @@ export type CustomElements = {
    * it up to the surface step, for a band that reads as part of the furniture
    * rather than as a slot cut into it.
    *
-   * **This was `tone="surface"`**, which put an elevation on the axis that says
-   * what a thing means. The band's own doc admitted it, calling `surface` the
-   * one value that was not a color. A band can be `info` and elevated at the
-   * same time, and two values that can both be true are two axes.
+   * **`separation` and not `tone`, because a rung is not a meaning.** A band
+   * can be `info` and elevated at the same time, and two values that can both
+   * be true are two axes, which is the test the registry answers to.
    *
    * Styled and not headless, because a rung of a ladder is paint: the headless
    * tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -21305,6 +21358,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
@@ -29665,6 +29725,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
@@ -30834,8 +30900,10 @@ export type CustomElements = {
    * where one is the number being watched and the rest are context, which is a
    * fact about the region rather than about any one of them.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` earns its
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+   * the whole of what quiet means here. `outlined` earns its
    * place in `BarChart`, which keeps the area and fades it toward the page, only
    * because a chart has other series for the outlined one to be a *different
    * kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -32132,7 +32200,7 @@ export type CustomElements = {
    *
    * Reflected because the stylesheet selects on it. The mesh is chosen from the
    * rendered box rather than from this, so `--orb-size` and a consumer's own
-   * `inline-size` get the same treatment as the three named steps.
+   * `inline-size` get the same treatment as the named steps.
    * - `state`: What the agent is doing.
    *
    * **A name we do not draw is drawn as `thinking` rather than as nothing.**
@@ -32989,8 +33057,10 @@ export type CustomElements = {
    * the loudest thing in the region. The case is a background task, which has to
    * be visible and must not compete with what the reader is actually looking at.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` is the
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+   * whole of what quiet means here. `outlined` is the
    * interesting refusal: `BarChart` earns it by keeping the area and fading it
    * toward the page, so an outlined column still encodes its value and stands as
    * a *different kind of fact* from the series beside it (a forecast, a target,
@@ -33119,11 +33189,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,
@@ -34693,9 +34765,12 @@ export type CustomElements = {
    * **`emphasis` and not `separation`, which the registry decides rather than
    * taste.** Emphasis is asked of controls, how loud this one is; separation is
    * asked of containers, where the surface ends. A trigger is a control, and a
-   * family may not declare both. Two of the four values are refused: `solid` and
-   * `subtle` are a button's way of being the one thing to press, which is not a
-   * thing an answer should ever be.
+   * family may not declare both. Three of the five values are refused: `solid`
+   * and `subtle` are a button's way of being the one thing to press, which is
+   * not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+   * takes, where a trigger's loudness is its frame rather than its ink.
+   * `outlined` is what the unset frame already draws, so writing it would be
+   * writing the resting state out.
    *
    * **The other three fields want this too and do not have it yet.** `Input`,
    * `Textarea` and `Combobox` wear the same frame from the same shared
@@ -35372,6 +35447,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`,
@@ -40437,10 +40518,9 @@ export type CustomElementsSolidJs = {
    * it up to the surface step, for a band that reads as part of the furniture
    * rather than as a slot cut into it.
    *
-   * **This was `tone="surface"`**, which put an elevation on the axis that says
-   * what a thing means. The band's own doc admitted it, calling `surface` the
-   * one value that was not a color. A band can be `info` and elevated at the
-   * same time, and two values that can both be true are two axes.
+   * **`separation` and not `tone`, because a rung is not a meaning.** A band
+   * can be `info` and elevated at the same time, and two values that can both
+   * be true are two axes, which is the test the registry answers to.
    *
    * Styled and not headless, because a rung of a ladder is paint: the headless
    * tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -40749,6 +40829,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
@@ -49269,6 +49356,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
@@ -50460,8 +50553,10 @@ export type CustomElementsSolidJs = {
    * where one is the number being watched and the rest are context, which is a
    * fact about the region rather than about any one of them.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` earns its
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+   * the whole of what quiet means here. `outlined` earns its
    * place in `BarChart`, which keeps the area and fades it toward the page, only
    * because a chart has other series for the outlined one to be a *different
    * kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -51787,7 +51882,7 @@ export type CustomElementsSolidJs = {
    *
    * Reflected because the stylesheet selects on it. The mesh is chosen from the
    * rendered box rather than from this, so `--orb-size` and a consumer's own
-   * `inline-size` get the same treatment as the three named steps.
+   * `inline-size` get the same treatment as the named steps.
    * - `state`: What the agent is doing.
    *
    * **A name we do not draw is drawn as `thinking` rather than as nothing.**
@@ -52664,8 +52759,10 @@ export type CustomElementsSolidJs = {
    * the loudest thing in the region. The case is a background task, which has to
    * be visible and must not compete with what the reader is actually looking at.
    *
-   * **One value and not the four.** `ghost` would leave a track with nothing in
-   * it, which is not a quiet reading but an absent one. `outlined` is the
+   * **One value of the five.** `ghost` would leave a track with nothing in
+   * it, which is not a quiet reading but an absent one. `muted` is the quiet
+   * ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+   * whole of what quiet means here. `outlined` is the
    * interesting refusal: `BarChart` earns it by keeping the area and fading it
    * toward the page, so an outlined column still encodes its value and stands as
    * a *different kind of fact* from the series beside it (a forecast, a target,
@@ -52797,11 +52894,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,
@@ -54414,9 +54513,12 @@ export type CustomElementsSolidJs = {
    * **`emphasis` and not `separation`, which the registry decides rather than
    * taste.** Emphasis is asked of controls, how loud this one is; separation is
    * asked of containers, where the surface ends. A trigger is a control, and a
-   * family may not declare both. Two of the four values are refused: `solid` and
-   * `subtle` are a button's way of being the one thing to press, which is not a
-   * thing an answer should ever be.
+   * family may not declare both. Three of the five values are refused: `solid`
+   * and `subtle` are a button's way of being the one thing to press, which is
+   * not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+   * takes, where a trigger's loudness is its frame rather than its ink.
+   * `outlined` is what the unset frame already draws, so writing it would be
+   * writing the resting state out.
    *
    * **The other three fields want this too and do not have it yet.** `Input`,
    * `Textarea` and `Combobox` wear the same frame from the same shared
@@ -55105,6 +55207,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

@@ -340,10 +340,9 @@ export type HelixAnnouncementVueProps = {
 it up to the surface step, for a band that reads as part of the furniture
 rather than as a slot cut into it.
 
-**This was `tone="surface"`**, which put an elevation on the axis that says
-what a thing means. The band's own doc admitted it, calling `surface` the
-one value that was not a color. A band can be `info` and elevated at the
-same time, and two values that can both be true are two axes.
+**`separation` and not `tone`, because a rung is not a meaning.** A band
+can be `info` and elevated at the same time, and two values that can both
+be true are two axes, which is the test the registry answers to.
 
 Styled and not headless, because a rung of a ladder is paint: the headless
 tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -514,7 +513,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?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -5256,7 +5262,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?: (HelixLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -5822,8 +5834,10 @@ the loudest thing in the region. The case is a dashboard of several meters
 where one is the number being watched and the rest are context, which is a
 fact about the region rather than about any one of them.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` earns its
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+the whole of what quiet means here. `outlined` earns its
 place in `BarChart`, which keeps the area and fades it toward the page, only
 because a chart has other series for the outlined one to be a *different
 kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -6443,7 +6457,7 @@ the name of the tool being run, or the file being read. */
 
 Reflected because the stylesheet selects on it. The mesh is chosen from the
 rendered box rather than from this, so `--orb-size` and a consumer's own
-`inline-size` get the same treatment as the three named steps. */
+`inline-size` get the same treatment as the named steps. */
   size?: (HelixOrb["size"]) | undefined;
   /** What the agent is doing.
 
@@ -6906,8 +6920,10 @@ export type HelixProgressVueProps = {
 the loudest thing in the region. The case is a background task, which has to
 be visible and must not compete with what the reader is actually looking at.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` is the
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+whole of what quiet means here. `outlined` is the
 interesting refusal: `BarChart` earns it by keeping the area and fading it
 toward the page, so an outlined column still encodes its value and stands as
 a *different kind of fact* from the series beside it (a forecast, a target,
@@ -7005,11 +7021,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   label?: (HelixQrCode["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,
@@ -7760,9 +7778,12 @@ inside a sentence.
 **`emphasis` and not `separation`, which the registry decides rather than
 taste.** Emphasis is asked of controls, how loud this one is; separation is
 asked of containers, where the surface ends. A trigger is a control, and a
-family may not declare both. Two of the four values are refused: `solid` and
-`subtle` are a button's way of being the one thing to press, which is not a
-thing an answer should ever be.
+family may not declare both. Three of the five values are refused: `solid`
+and `subtle` are a button's way of being the one thing to press, which is
+not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+takes, where a trigger's loudness is its frame rather than its ink.
+`outlined` is what the unset frame already draws, so writing it would be
+writing the resting state out.
 
 **The other three fields want this too and do not have it yet.** `Input`,
 `Textarea` and `Combobox` wear the same frame from the same shared
@@ -8092,7 +8113,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?: (HelixSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.