@fusion.dev/helix-headless 0.42.0 → 0.44.0

package/custom-elements.json

@@ -11148,7 +11148,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/chat",
             "aliases": [
               "Message box",
@@ -11882,7 +11882,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/chat",
             "aliases": [
               "Message",
@@ -13286,7 +13286,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/chat",
             "aliases": [
               "Conversation",
@@ -30667,7 +30667,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/date-picker",
             "aliases": [
               "Calendar",
@@ -42521,7 +42521,7 @@
           "helix": {
             "category": "typography",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/format-date",
             "aliases": [
               "RelativeTime",
@@ -42533,7 +42533,7 @@
             "part": "Root",
             "examples": [
               {
-                "description": "The same readings on the headless tier, where the value is the element's own text.",
+                "description": "The same readings on the headless tier, with every rule written by hand.",
                 "slug": "preview"
               }
             ],
@@ -57791,6 +57791,16 @@
               "description": "How many the group says it stands for, which is the count or the rows.",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "counted",
+              "type": {
+                "text": "number | undefined"
+              },
+              "privacy": "private",
+              "description": "The same number where anything can know it, and nothing where nothing can.\n\n**A server has no rows to count and must not say zero.** `items` reads\n`knownChildren`, which is empty on a server and while hydrating what one\nsent, so a group written around three notifications with no `count` of its\nown served `<span part=\"count\">0</span>`: a crawler, and a reader before the\npage has run, given a group that says it holds nothing over the three rows\nunderneath it. Not knowing is not zero, which is the rule `MixinCollection`\nalready states about an empty list.\n\nA declared `count` is a fact about the group rather than about its children,\nso it serves whole, which is the shape a feed trimmed by a server already\nwants: it is the number the rows were cut from.",
+              "readonly": true
+            },
             {
               "kind": "method",
               "name": "assign",
@@ -57808,16 +57818,6 @@
               "privacy": "private",
               "readonly": true
             },
-            {
-              "kind": "field",
-              "name": "folded",
-              "type": {
-                "text": "number"
-              },
-              "privacy": "private",
-              "description": "How many rows the collapse is hiding, for the control to say so.",
-              "readonly": true
-            },
             {
               "kind": "field",
               "name": "open",
@@ -58348,7 +58348,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.24.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/notifications",
             "aliases": [
               "NotificationSection",
@@ -58481,6 +58481,10 @@
               "description": "A block belonging to the row rather than a line about it: a quoted comment, a status moving from one value to another, a preview. Unlike `caption` nothing here sets a size or an ink, because whatever fills it usually brings its own.",
               "name": "detail"
             },
+            {
+              "description": "Replaces the glyph inside the dismiss control, which is drawn only where the row is `dismissible`.",
+              "name": "dismiss"
+            },
             {
               "description": "An avatar or icon identifying who or what it came from.",
               "name": "media"
@@ -59058,7 +59062,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/notifications",
             "aliases": [
               "Notification item",
@@ -59283,7 +59287,7 @@
                   "text": "void"
                 }
               },
-              "description": "Says whether anything in the feed has media, so every item can hold the\ncolumn open whether or not it has one of its own.\n\n**A fact no item can answer for itself**, which is why it is here. An item\nknows about its own media slot and nothing about its neighbors, so a feed\nwhere some rows have an avatar and some do not draws two different left\nedges for its text: measured on a four item feed, the rows without media\nstarted their text 32 pixels to the left of the rows with it. The styled\ntier turns this into a width; this tier ships no stylesheet and is\nunaffected.\n\nRead off the light DOM rather than off the items, so it does not depend on\nwhich children have upgraded by the time this runs."
+              "description": "Says whether anything in the feed has media, so every item can hold the\ncolumn open whether or not it has one of its own.\n\n**A fact no item can answer for itself**, which is why it is here. An item\nknows about its own media slot and nothing about its neighbors, so a feed\nwhere some rows have an avatar and some do not draws two different left\nedges for its text: measured on a four item feed, the rows without media\nstarted their text 32 pixels to the left of the rows with it. The styled\ntier turns this into a width; this tier ships no stylesheet and is\nunaffected.\n\n**What is asked of each row is its light DOM, not the row.** A notification\npublishes no property for this, and asking one would make the answer depend\non the row having drawn itself; a `[slot=\"media\"]` child is there from the\nmoment the markup is parsed. The rows themselves come from `items`, which\ndoes need them upgraded, and that is the honest limit rather than a claim\nthis had made the other way: a row that upgrades late is counted on the next\nupdate, which its own `slotchange` asks for."
             },
             {
               "kind": "method",
@@ -59917,7 +59921,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/notifications",
             "aliases": [
               "Notification feed",
@@ -63024,13 +63028,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so what is captured here is what\nthe markup said at upgrade, before anything could overwrite it: read the\nattribute later and the listbox's own writes answer instead.\n\n**The deeper half is 302 and is not this.** State reflecting under the\ndeclaration's name is the fault `TreeItem` already avoids by mirroring to\n`data-selected`, and four families here still write `selected` back into a\nconsumer's markup. Splitting them means moving what every stylesheet selects\non, which is a change of its own rather than a property being added."
-            },
-            {
-              "kind": "field",
-              "name": "seeded",
-              "privacy": "private",
-              "description": "What the markup said, read once at construction for the reason above."
+              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so the declaration is the\nattribute and the state is the property.\n\n**The attribute, read when it is asked for, and never a snapshot taken in\nthe constructor.** A field initializer runs there, and an element the HTML\nparser created has none of its attributes yet at that moment: measured on\nthis element, on `Radio` and on `Toggle`, `<helix-option value=\"a\"\nselected>` reported `defaultSelected` as `false` both from parsed markup\nand from `createElement` followed by `setAttribute`, which is every way a\nconsumer writes one. The snapshot could only ever be true for an element\nalready in the document when `customElements.define` ran.\n\nNothing overwrites it either, which is what makes reading it late correct\nrather than merely later: `selected` does not reflect, for the reason\n`willUpdate` records, so the listbox's writes never reach the attribute and\nwhat it says is what the markup said.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added."
             },
             {
               "kind": "field",
@@ -71504,13 +71502,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so what is captured here is what\nthe markup said at upgrade, before anything could overwrite it: read the\nattribute later and the listbox's own writes answer instead.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added."
-            },
-            {
-              "kind": "field",
-              "name": "seeded",
-              "privacy": "private",
-              "description": "What the markup said, read once at construction for the reason above."
+              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so the declaration is the\nattribute and the state is the property.\n\n**The attribute, read when it is asked for, and never a snapshot taken in\nthe constructor.** A field initializer runs there, and an element the HTML\nparser created has none of its attributes yet at that moment: measured on\nthis element, on `Option` and on `Toggle`, `<helix-radio value=\"a\"\nselected>` reported `defaultSelected` as `false` both from parsed markup\nand from `createElement` followed by `setAttribute`, which is every way a\nconsumer writes one. The snapshot could only ever be true for an element\nalready in the document when `customElements.define` ran.\n\nNothing overwrites it either, which is what makes reading it late correct\nrather than merely later: `selected` does not reflect, for the reason\n`willUpdate` records, so the group's writes never reach the attribute and\nwhat it says is what the markup said.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added."
             },
             {
               "kind": "field",
@@ -77355,7 +77347,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "A real `<input type=\"range\">`, so the drag, the arrow keys, Home and End, the\npage keys and the touch target are the platform's. The last is the one nobody\nnotices: a native range has a hit area larger than its thumb, sized by the\nplatform for a finger.\n\n**The value is a string, like every other form control's.** A range submits\ntext and `MixinControllerValue` holds text, so the number is a reading of the\nvalue. `valueAsNumber` is there for arithmetic.\n\n**Marks are drawn rather than left to `<datalist>`**, whose ticks cannot be\nstyled and which Firefox does not render for a range at all. A mark is\ndecoration; what a reader can land on is `step`, which the input enforces\nwhether or not anything is drawn. `markers` is a count rather than a flag, so\na slider from zero to a hundred cannot silently ask for a hundred and one.\n\n**A range is two of them.** There is no native two-thumb range, so two are\nstacked on one track and each thumb keeps its own.",
+          "description": "A real `<input type=\"range\">`, so the drag, the arrow keys, Home and End, the\npage keys and the touch target are the platform's. The last is the one nobody\nnotices: a native range has a hit area larger than its thumb, sized by the\nplatform for a finger.\n\n**The value is a string, like every other form control's.** A range submits\ntext and `MixinControllerValue` holds text, so the number is a reading of the\nvalue. `valueAsNumber` is there for arithmetic.\n\n**Marks are drawn rather than left to `<datalist>`**, whose ticks cannot be\nstyled and which Firefox does not render for a range at all. A mark is\ndecoration; what a reader can land on is `step`, which the input enforces\nwhether or not anything is drawn. `markers` is a count rather than a flag, so\na slider from zero to a hundred cannot silently ask for a hundred and one.\n\n**A range is two of them.** There is no native two-thumb range, so two are\nstacked on one track and each thumb keeps its own.\n\n**`required` arrives with the field mixin and cannot fail here**, which is\nworth saying rather than leaving a reader to find. A range is never empty:\nthe platform shows its own midpoint whatever is set, and `willUpdate` seeds\nthat midpoint into `defaultValue` so the value agrees with the handle from the\nfirst render. HTML does not apply `required` to a range either, so it stays\noff the control and the marker beside the label is all it does.",
           "name": "HelixHeadlessSlider",
           "cssProperties": [
             {
@@ -77363,7 +77355,7 @@
               "name": "--slider-fraction"
             },
             {
-              "description": "Where the filled span starts, as a percentage of the track.",
+              "description": "Where a range's filled span starts, as a fraction of the track, 0 to 1.",
               "name": "--slider-from"
             },
             {
@@ -77371,7 +77363,7 @@
               "name": "--slider-marker-at"
             },
             {
-              "description": "Where the filled span ends, as a percentage of the track.",
+              "description": "Where a range's filled span ends, as a fraction of the track, 0 to 1.",
               "name": "--slider-to"
             }
           ],
@@ -78720,7 +78712,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/slider",
             "aliases": [
               "Range",
@@ -79830,7 +79822,7 @@
           "helix": {
             "category": "actions",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/speed-dial",
             "aliases": [
               "Speed dial action",
@@ -80567,7 +80559,7 @@
           "helix": {
             "category": "actions",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/speed-dial",
             "aliases": [
               "FAB",
@@ -81074,7 +81066,7 @@
                   }
                 }
               ],
-              "description": "Asks to move, and applies it where the position is this element's to move.\n\nNot announced per step: `helix-before-resize` is the settling, below. A drag that\nannounced every position would be asking a consumer to record a hundred\ndecisions to keep one."
+              "description": "Moves the divider under a gesture that is still happening.\n\nNot announced per step: `helix-before-resize` is the settling, below. A drag that\nannounced every position would be asking a consumer to record a hundred\ndecisions to keep one.\n\n**A drag only, which is the whole of why applying before announcing is\nright here.** The divider has to follow the hand, and the one number worth\na decision is where the hand let go. Nothing discrete calls this: a key and\na double click go straight to `settle`, so their announcement comes before\ntheir change and refusing one takes the decision, and the corner's arrows\nalready did."
             },
             {
               "kind": "method",
@@ -81093,7 +81085,7 @@
                   }
                 }
               ],
-              "description": "Says the arrangement has settled, so a consumer can keep it.\n\nThrough the audited path, so a consumer who owns `position` is told what was\nasked for and decides, and one who does not has already had it applied."
+              "description": "Says the arrangement has settled, so a consumer can keep it.\n\nThrough the audited path, so a consumer who owns `position` is told what was\nasked for and decides, and one who does not has already had it applied.\n\n**The second announcement is conditional on the first, because it is derived\nfrom it.** `shutAt` reads the position the gesture ended on, so a refused\n`helix-before-resize` leaves a collapse computed from a number that was\nrefused. Announced anyway, the refusal produced the outcome it was refusing:\nmeasured on a divider at 40 with a listener calling `preventDefault`, Home\nleft `position` reporting 0 and `collapsed` reporting `start`, because the\ncollapse applied and `position` reads the sliver once a pane is shut. The\nreturn of the first request is what says so, and it was being dropped: a\ncancelable event dispatched as a bare statement with nothing reading the\nanswer, which is the shape the navigation cohort named on `Outline` and left.\n\nRefusing the collapse alone still leaves the resize, which is the other way\nround and is coherent: the divider goes where the drag put it and the pane\nis not declared shut. What a consumer cannot have is a pane that collapses\nout from under a position they said no to."
             },
             {
               "kind": "field",
@@ -81597,7 +81589,7 @@
               "type": {
                 "text": "HelixBeforeCollapseEvent"
               },
-              "description": "Fired before a pane shuts or reopens, and cancelable.",
+              "description": "Fired before a pane shuts or reopens, and only where the position it is derived from stood. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it.",
               "name": "helix-before-collapse",
               "reactProp": "onhelix-before-collapse"
             },
@@ -81605,7 +81597,7 @@
               "type": {
                 "text": "HelixBeforeResizeEvent"
               },
-              "description": "Fired before the divider settles, and cancelable.",
+              "description": "Fired before the divider settles. Cancelable: refusing it takes the whole of where the gesture ended, so no collapse follows from it either. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own.",
               "name": "helix-before-resize",
               "reactProp": "onhelix-before-resize"
             }
@@ -96647,7 +96639,7 @@
           "summary": "One message in the toast region.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toast",
             "tier": "headless",
             "group": "BaseToast",
@@ -97091,12 +97083,11 @@
           "helix": {
             "category": "overlays",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toast",
             "aliases": [
               "Toaster",
-              "Snackbar",
-              "Notifications"
+              "Snackbar"
             ],
             "tier": "headless",
             "group": "BaseToast",
@@ -97186,9 +97177,28 @@
             {
               "description": "The group's items.",
               "name": ""
+            },
+            {
+              "description": "Whatever sits after the track on its own line, such as a count or a reset.",
+              "name": "end"
+            },
+            {
+              "description": "Whatever sits before the track on its own line, such as an icon or a caption.",
+              "name": "start"
             }
           ],
           "members": [
+            {
+              "kind": "method",
+              "name": "adopt",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Takes the markup's own answer where nothing has set a value.\n\n**The case a server renders**, and `Tabs` records the same fault from the\nother side. This element cannot choose on the server, having no children to\ncount, so a consumer whose first paint is right wrote `selected` on the\nitem: that serves `aria-checked=\"true\"`, and `sync` then cleared it one\nframe later, because `value` is `''` and nothing matches it. The shipped\n`disabled` example is exactly that markup, and drew both of its groups with\nnothing chosen.\n\n**Onto `defaultValue`, never onto `value`**, which is the same call\n`Slider` makes about the midpoint it seeds: what the markup declared is a\nfact about the markup, so it is where a reset returns to rather than\nsomething the reader chose. It also makes the group report the answer it is\nshowing, which marking the item alone would not: a `required` group would\notherwise tell a reader a value is missing while they are looking at one.\n\nA written `value` still wins, a declared property being a seed and a\ncorrection, and a group with neither still marks nothing at all.\n\n**The property and never `defaultSelected`, which is the attribute.** React\nassigns a JSX prop as a property where the custom element has one, and\nwrites no attribute at all, so keying on the attribute answers for markup\nand not for JSX. Measured by the parity check on the shipped `disabled`\nexample, whose two syntaxes are the same tree: 192 pixels apart, the HTML\nmarking `List` and the TSX marking nothing. The attribute seeds the\nproperty at upgrade, so reading the property covers both.\n\nRead before `sync` writes to it, which is the only moment it still holds\nwhat the consumer declared: after that it holds this group's answer, and\n`value` is no longer empty, so this returns above.\n\n**Called from `willUpdate` and from the slot, never from `sync`**, which\nruns in `updated`: a reactive property set there schedules a second update,\nand Lit's development build warns about exactly that once per group. From\n`willUpdate` the first render already carries the value, which is the pass\nthat has to be right. `children` is undefined on the server, whose element\nshim carries attributes and no tree, and that is the same guard\n`MixinCollection` records for the same reason."
+            },
             {
               "kind": "method",
               "name": "sync",
@@ -98278,7 +98288,7 @@
           "summary": "A row of options with the selection marked by a moving indicator.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toggle",
             "aliases": [
               "SegmentedControl",
@@ -98376,13 +98386,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so what is captured here is what\nthe markup said at upgrade, before anything could overwrite it: read the\nattribute later and the listbox's own writes answer instead.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added."
-            },
-            {
-              "kind": "field",
-              "name": "seeded",
-              "privacy": "private",
-              "description": "What the markup said, read once at construction for the reason above."
+              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so the declaration is the\nattribute and the state is the property.\n\n**The attribute, read when it is asked for, and never a snapshot taken in\nthe constructor.** A field initializer runs there, and an element the HTML\nparser created has none of its attributes yet at that moment: measured on\nthis element, on `Option` and on `Radio`, `<helix-toggle value=\"light\"\nselected>` reported `defaultSelected` as `false` both from parsed markup\nand from `createElement` followed by `setAttribute`, which is every way a\nconsumer writes one. The snapshot could only ever be true for an element\nalready in the document when `customElements.define` ran.\n\nNothing overwrites it either, which is what makes reading it late correct\nrather than merely later: `selected` does not reflect, for the reason\n`willUpdate` records, so the group's writes never reach the attribute and\nwhat it says is what the markup said.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added."
             },
             {
               "kind": "field",
@@ -98825,7 +98829,7 @@
           "helix": {
             "category": "actions",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toggle",
             "aliases": [
               "Segment",
@@ -101153,14 +101157,6 @@
               "description": "A stop's own controls asking the tour to move, dispatched by the stop and heard here because the tour is what moves.",
               "name": "helix-tour-ask",
               "reactProp": "onhelix-tour-ask"
-            },
-            {
-              "type": {
-                "text": "Event"
-              },
-              "description": "Says the state moved, carrying `newState` and `oldState`.",
-              "name": "toggle",
-              "reactProp": "ontoggle"
             }
           ],
           "attributes": [

package/dist/chat/composer/chat-composer.d.ts

@@ -19,7 +19,7 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  * of what the reader wrote.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Message box, Prompt input
  * @documentation https://fusion.dev/helix/components/chat

package/dist/chat/message/chat-message.d.ts

@@ -23,7 +23,7 @@ export declare const FAILED_LABEL = "Not sent";
  * completion is the only version of this that works.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @aliases Message, Bubble, Turn
  * @documentation https://fusion.dev/helix/components/chat

package/dist/chat/message/chat-message.js

@@ -40,7 +40,7 @@ let HelixHeadlessChatMessage = class HelixHeadlessChatMessage extends HelixEleme
             this.clock = Date.now();
         }
         hostAria(this.internals, { role: 'article' });
-        this.toggleAttribute('aria-busy', this.state === 'streaming');
+        this.internals.ariaBusy = this.state === 'streaming' ? 'true' : null;
     }
     renderTime() {
         const moment = this.moment;

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

@@ -69,7 +69,7 @@ declare const HelixHeadlessChat_base: (new (...args: any[]) => import("@fusion.d
  * turns as children.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @aliases Conversation, Transcript, Thread, Messages
  * @documentation https://fusion.dev/helix/components/chat

package/dist/color-picker/root/color-picker-root.js

@@ -264,8 +264,7 @@ let HelixHeadlessColorPicker = class HelixHeadlessColorPicker extends MixinContr
                     @click=${() => this.handleSwatch(preset)}
                   ></button>`;
             })}
-              </div>`}
-      </div>`;
+              </div>`}`;
     }
 };
 __decorate([

package/dist/date-picker/root/date-picker-root.d.ts

@@ -21,7 +21,7 @@ declare const HelixHeadlessDatePicker_base: (new (...args: any[]) => import("@fu
  * write the same comma-separated `value`.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Calendar, Date grid, Month view
  * @documentation https://fusion.dev/helix/components/date-picker

package/dist/element-events.generated.js

@@ -138,7 +138,6 @@ registerElementEvents({
         'helix-before-close',
         'helix-complete',
         'helix-tour-ask',
-        'toggle',
     ],
     'helix-headless-tour-stop': ['helix-tour-ask'],
     'helix-headless-tree': ['helix-activate', 'helix-before-activate', 'helix-select'],

package/dist/format-date/root/format-date-root.d.ts

@@ -30,7 +30,7 @@ import { nothing, type PropertyValues, type TemplateResult } from 'lit';
  * "yesterday".
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category typography
  * @aliases RelativeTime, Timestamp, TimeAgo
  * @documentation https://fusion.dev/helix/components/format-date

package/dist/notifications/group/notification-group.d.ts

@@ -27,7 +27,7 @@ declare const HelixHeadlessNotificationGroup_base: (new (...args: any[]) => impo
  * Left off, it is the number of rows.
  *
  * @since 0.24.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @aliases NotificationSection, FeedGroup
  * @documentation https://fusion.dev/helix/components/notifications
@@ -100,6 +100,22 @@ export declare class HelixHeadlessNotificationGroup extends HelixHeadlessNotific
     get items(): HelixHeadlessNotification[];
     /** How many the group says it stands for, which is the count or the rows. */
     get total(): number;
+    /**
+     * The same number where anything can know it, and nothing where nothing can.
+     *
+     * **A server has no rows to count and must not say zero.** `items` reads
+     * `knownChildren`, which is empty on a server and while hydrating what one
+     * sent, so a group written around three notifications with no `count` of its
+     * own served `<span part="count">0</span>`: a crawler, and a reader before the
+     * page has run, given a group that says it holds nothing over the three rows
+     * underneath it. Not knowing is not zero, which is the rule `MixinCollection`
+     * already states about an empty list.
+     *
+     * A declared `count` is a fact about the group rather than about its children,
+     * so it serves whole, which is the shape a feed trimmed by a server already
+     * wants: it is the number the rows were cut from.
+     */
+    private get counted();
     protected willUpdate(changed: PropertyValues): void;
     protected firstUpdated(changed: PropertyValues): void;
     protected updated(changed: PropertyValues): void;
@@ -119,8 +135,6 @@ export declare class HelixHeadlessNotificationGroup extends HelixHeadlessNotific
      */
     private assign;
     private readonly handleToggle;
-    /** How many rows the collapse is hiding, for the control to say so. */
-    private get folded();
     protected render(): TemplateResult;
 }
 declare global {

package/dist/notifications/group/notification-group.js

@@ -29,6 +29,9 @@ let HelixHeadlessNotificationGroup = class HelixHeadlessNotificationGroup extend
     get total() {
         return this.count ?? this.items.length;
     }
+    get counted() {
+        return this.count ?? (this.childrenKnown ? this.items.length : undefined);
+    }
     willUpdate(changed) {
         super.willUpdate(changed);
         hostAria(this.internals, this.label === '' ? { role: 'group' } : { label: this.label, role: 'group' });
@@ -60,11 +63,9 @@ let HelixHeadlessNotificationGroup = class HelixHeadlessNotificationGroup extend
         const label = this.renderRoot?.querySelector?.('slot[name="label"]');
         label?.assign?.(...[...this.children].filter((child) => child.getAttribute('slot') === 'label'));
     }
-    get folded() {
-        return Math.max(this.items.length - 1, 0);
-    }
     render() {
-        const collapsed = this.collapsible && !this.open;
+        const counted = this.counted;
+        const count = html `<span part="count">${counted ?? nothing}</span>`;
         return html `<div part="header">
         ${this.collapsible
             ? html `<button
@@ -76,17 +77,13 @@ let HelixHeadlessNotificationGroup = class HelixHeadlessNotificationGroup extend
                 @click=${this.handleToggle}
               >
                 <span part="label"><slot name="label">${this.label}</slot></span>
-                <span part="count">${this.total}</span>
+                ${count}
               </button>`
             : html `<span part="label"><slot name="label">${this.label}</slot></span>
-                <span part="count">${this.total}</span>`}
+                ${count}`}
         <span part="action"><slot name="action"></slot></span>
       </div>
-      <div
-        id=${ITEMS_ID}
-        part="items"
-        aria-label=${collapsed && this.folded > 0 ? `${this.folded} more` : nothing}
-      >
+      <div id=${ITEMS_ID} part="items">
         <slot></slot>
       </div>`;
     }

package/dist/notifications/notification/notification.d.ts

@@ -30,7 +30,7 @@ import '../../format-date/index.js';
  * cancelable, and a `read` set by the consumer makes this element defer entirely.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @aliases Notification item, Inbox item
  * @documentation https://fusion.dev/helix/components/notifications
@@ -44,6 +44,8 @@ import '../../format-date/index.js';
  * @slot detail - A block belonging to the row rather than a line about it: a quoted
  * comment, a status moving from one value to another, a preview. Unlike `caption` nothing
  * here sets a size or an ink, because whatever fills it usually brings its own.
+ * @slot dismiss - Replaces the glyph inside the dismiss control, which is drawn
+ * only where the row is `dismissible`.
  * @slot media - An avatar or icon identifying who or what it came from.
  *
  * @event {HelixDismissEvent} helix-dismiss - Fired when a reader asks to remove it, and cancelable.

package/dist/notifications/notification/notification.js

@@ -22,7 +22,7 @@ let HelixHeadlessNotification = class HelixHeadlessNotification extends HelixEle
         this.isNotification = true;
         this.readState = undefined;
         this.handleActions = () => {
-            this.markControls();
+            this.markActions();
         };
         this.handleDismiss = (event) => {
             event.stopPropagation();

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

@@ -25,7 +25,7 @@ declare const HelixHeadlessNotifications_base: (new (...args: any[]) => import("
  * either of them counting.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @aliases Notification feed, Inbox, Activity
  * @documentation https://fusion.dev/helix/components/notifications
@@ -174,8 +174,13 @@ export declare class HelixHeadlessNotifications extends HelixHeadlessNotificatio
      * tier turns this into a width; this tier ships no stylesheet and is
      * unaffected.
      *
-     * Read off the light DOM rather than off the items, so it does not depend on
-     * which children have upgraded by the time this runs.
+     * **What is asked of each row is its light DOM, not the row.** A notification
+     * publishes no property for this, and asking one would make the answer depend
+     * on the row having drawn itself; a `[slot="media"]` child is there from the
+     * moment the markup is parsed. The rows themselves come from `items`, which
+     * does need them upgraded, and that is the honest limit rather than a claim
+     * this had made the other way: a row that upgrades late is counted on the next
+     * update, which its own `slotchange` asks for.
      */
     private markMedia;
     /**