@fusion.dev/helix-headless 0.0.0-dev → 0.0.3

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

@@ -83,33 +83,6 @@ declare const HelixHeadlessTimePicker_base: (new (...args: any[]) => import("@fu
  * @csspart option-text - The words and the caption, as one column.
  */
 export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_base {
-    /**
-     * Whether the current selection fails validation.
-     *
-     * A flag rather than a message, which is the split Date Picker already drew and
-     * these two now follow. A flat picker has no room of its own for a sentence:
-     * the field that wraps one owns the label, the hint and the feedback, and a
-     * second message inside the panel would be the same error said twice. What is
-     * left for the picker is the one thing the field cannot draw from outside, the
-     * mark on the answer itself.
-     */
-    invalid: boolean;
-    /**
-     * How far apart the offered times are, in minutes.
-     *
-     * Fifteen, which is four rows an hour and ninety-six in a day: enough that a
-     * reader scrolls rather than hunts, and few enough that the list is a list.
-     * Anything under five is a thousand rows and wants a field instead.
-     */
-    step: number;
-    /**
-     * Earliest time offered, as `HH:mm`.
-     */
-    min: string;
-    /**
-     * Latest time offered, as `HH:mm`.
-     */
-    max: string;
     /**
      * Times that cannot be chosen, comma separated, as `HH:mm`.
      *
@@ -123,6 +96,20 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
      * reached honestly rather than by handing over an empty range.
      */
     disableTimes: string;
+    /**
+     * Whether the current selection fails validation.
+     *
+     * A flag rather than a message, the same split Date Picker draws. A flat
+     * picker has no room of its own for a sentence: the field that wraps one owns
+     * the label, the hint and the feedback, and a second message inside the panel
+     * would be the same error said twice. What is left for the picker is the one
+     * thing the field cannot draw from outside, the mark on the answer itself.
+     */
+    invalid: boolean;
+    /**
+     * Accessible name for the list, which has no visible one of its own.
+     */
+    label: string;
     /**
      * Language tag the times are written in.
      *
@@ -130,9 +117,13 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
      */
     locale: string;
     /**
-     * Accessible name for the list, which has no visible one of its own.
+     * Latest time offered, as `HH:mm`.
      */
-    label: string;
+    max: string;
+    /**
+     * Earliest time offered, as `HH:mm`.
+     */
+    min: string;
     /**
      * How many times can be held at once.
      *
@@ -146,7 +137,7 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
      * separate "from" and "to" control, is two answers to what a product asks as
      * one, and it makes the between part impossible to show.
      *
-     * **Neither works on wheels and the appearance falls back.** A range on
+     * **Neither works on wheels and the variant falls back.** A range on
      * wheels is two sets of wheels, which is two controls; a multiple is a set,
      * and a wheel has exactly one value by construction. Rather than draw
      * something that cannot say what it holds, `wheels` renders as a list
@@ -154,32 +145,23 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
      */
     mode?: 'multiple' | 'range';
     /**
-     * Whether the times are one list or a column each.
-     *
-     * `list` is the default and offers whole times, which is what a product with
-     * opening hours or slots actually has. `wheels` splits them into an hour, a
-     * minute and, where the locale uses one, a meridiem: three short columns
-     * instead of ninety-six rows, and the only way to reach `23:45` without
-     * scrolling most of a day.
-     *
-     * The trade is that a wheel cannot say which *combinations* are on offer. A
-     * list of half hours from nine to five is seventeen rows and every one of them
-     * is a time the product has; the same thing as columns is an hour column and a
-     * minute column, and nothing in either says the two are only valid together.
-     * The bounds are still enforced, so a reader can be refused after the fact,
-     * which is worse than not being offered it.
+     * Whether the control refuses changes while still submitting its value.
      *
-     * So: `list` where the set is the point, `wheels` where any time is allowed
-     * and the range is a whole day.
+     * **Enforced by refusing every request in one place**, which is the seam this
+     * component already has: `requestValue` is what every path here comes through,
+     * and gating it once is what stops the next call site from being written
+     * without the check.
      *
-     * **Optional rather than defaulted, which is not a style preference.** A
-     * reflecting property with a default writes its attribute onto every host the
-     * moment the element upgrades, including the ones a consumer rendered and did
-     * not touch, and React reads that as a hydration mismatch. The absent
-     * attribute *is* the list, which the stylesheet reads as the base rule, so
-     * only the departure has to be named.
+     * Not `disabled`, which is the confusion worth naming: a disabled control
+     * submits nothing and leaves the tab order, and a read-only one submits its
+     * value and stays reachable, which is what a form showing a value somebody
+     * else set needs.
      */
-    variant?: 'list' | 'wheels';
+    readOnly: boolean;
+    /**
+     * Whether the form refuses to submit while nothing is chosen.
+     */
+    required: boolean;
     /**
      * Every time on offer, as minutes since midnight.
      *
@@ -255,25 +237,42 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
      */
     reveal(): void;
     /**
-     * Whether the control refuses changes while still submitting its value.
-     *
-     * **Enforced by refusing every request in one place**, which is the seam this
-     * component already has: `requestValue` is what every path here comes through,
-     * and gating it once is what stops the next call site from being written
-     * without the check.
+     * How far apart the offered times are, in minutes.
      *
-     * Not `disabled`, which is the confusion worth naming: a disabled control
-     * submits nothing and leaves the tab order, and a read-only one submits its
-     * value and stays reachable, which is what a form showing a value somebody
-     * else set needs.
+     * Fifteen, which is four rows an hour and ninety-six in a day: enough that a
+     * reader scrolls rather than hunts, and few enough that the list is a list.
+     * Anything under five is a thousand rows and wants a field instead.
      */
-    readOnly: boolean;
+    step: number;
     /** Refuses every change while read-only. See `readOnly`. */
     requestValue(next: string): boolean;
     /**
-     * Whether the form refuses to submit while nothing is chosen.
+     * Whether the times are one list or a column each.
+     *
+     * `list` is the default and offers whole times, which is what a product with
+     * opening hours or slots actually has. `wheels` splits them into an hour, a
+     * minute and, where the locale uses one, a meridiem: three short columns
+     * instead of ninety-six rows, and the only way to reach `23:45` without
+     * scrolling most of a day.
+     *
+     * The trade is that a wheel cannot say which *combinations* are on offer. A
+     * list of half hours from nine to five is seventeen rows and every one of them
+     * is a time the product has; the same thing as columns is an hour column and a
+     * minute column, and nothing in either says the two are only valid together.
+     * The bounds are still enforced, so a reader can be refused after the fact,
+     * which is worse than not being offered it.
+     *
+     * So: `list` where the set is the point, `wheels` where any time is allowed
+     * and the range is a whole day.
+     *
+     * **Optional rather than defaulted, which is not a style preference.** A
+     * reflecting property with a default writes its attribute onto every host the
+     * moment the element upgrades, including the ones a consumer rendered and did
+     * not touch, and React reads that as a hydration mismatch. The absent
+     * attribute *is* the list, which the stylesheet reads as the base rule, so
+     * only the departure has to be named.
      */
-    required: boolean;
+    variant?: 'list' | 'wheels';
     /**
      * Reports "required and empty", or clears it.
      *
@@ -288,14 +287,6 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
     /**
      * Reports the times to the form, one entry each.
      *
-     * **This element was form-associated, took a `name`, held a `value` and
-     * reported `valueMissing`, and never called `setFormValue` at all.** So
-     * `<helix-time-picker name="start" required>` refused the submit until a
-     * reader filled it and then submitted nothing, which is the worst shape the
-     * omission takes: every visible signal says the control is participating.
-     * Measured before the fix, one form holding both pickers, both named and
-     * both seeded: the entry list carried the date and no time.
-     *
      * `FormData` and one entry per time, which is `DatePicker.report` exactly.
      * `mode="multiple"` is genuinely several answers, and a server reading
      * `times=09:00,17:00` would have to split it on a convention this library
@@ -319,9 +310,9 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
      * sat at `scrollTop: 0` with the answer nine rows down, which reads as a wheel
      * showing the wrong time rather than as one that failed to scroll.
      *
-     * It survived because the case that was tested was the panel, and whatever
-     * opens a panel calls `reveal` again afterwards for the separate reason the
-     * method documents. Flat on a page there is no panel and no second call.
+     * Whatever opens a panel calls `reveal` again afterwards, for the separate
+     * reason that method documents. Flat on a page there is no panel and no
+     * second call.
      *
      * Safe to run on every update: the listbox stops as soon as the chosen row is
      * within a pixel of center, so a call with nothing to do costs two rect reads
@@ -334,7 +325,10 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
     /** Puts the keyboard on the list, which is the only control here. */
     focus(options?: FocusOptions): void;
     /**
-     * One wheel.
+     * One wheel, which is a listbox like the whole list is.
+     *
+     * `protected` rather than `private`, which is the whole of what a seam is
+     * here: a tier above has to be able to reach it.
      *
      * `barred` is passed per column rather than read from `disableTimes` here,
      * because a column holds a third of a time and only the caller knows the
@@ -346,7 +340,7 @@ export declare class HelixHeadlessTimePicker extends HelixHeadlessTimePicker_bas
     protected renderColumn(part: 'hour' | 'meridiem' | 'minute', label: string, values: string[], written: (one: string) => string, value: string, barred?: (one: string) => boolean): TemplateResult;
     private renderSpinner;
     /**
-     * The flat list of times, for the appearance that is not wheels, behind a seam the styled tier can move.
+     * The flat list of times, for the variant that is not wheels, behind a seam the styled tier can move.
      *
      * A method rather than a fragment inline, so a tier above can render its own,
      * wrap this one, pass it a property the base does not know about, or leave it

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

@@ -129,33 +129,6 @@ const isTwelveHour = (locale) => new Intl.DateTimeFormat(locale || undefined, {
 let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControllerValue(HelixFormElement) {
     constructor() {
         super(...arguments);
-        /**
-         * Whether the current selection fails validation.
-         *
-         * A flag rather than a message, which is the split Date Picker already drew and
-         * these two now follow. A flat picker has no room of its own for a sentence:
-         * the field that wraps one owns the label, the hint and the feedback, and a
-         * second message inside the panel would be the same error said twice. What is
-         * left for the picker is the one thing the field cannot draw from outside, the
-         * mark on the answer itself.
-         */
-        this.invalid = false;
-        /**
-         * How far apart the offered times are, in minutes.
-         *
-         * Fifteen, which is four rows an hour and ninety-six in a day: enough that a
-         * reader scrolls rather than hunts, and few enough that the list is a list.
-         * Anything under five is a thousand rows and wants a field instead.
-         */
-        this.step = 15;
-        /**
-         * Earliest time offered, as `HH:mm`.
-         */
-        this.min = '00:00';
-        /**
-         * Latest time offered, as `HH:mm`.
-         */
-        this.max = '23:59';
         /**
          * Times that cannot be chosen, comma separated, as `HH:mm`.
          *
@@ -169,6 +142,20 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
          * reached honestly rather than by handing over an empty range.
          */
         this.disableTimes = '';
+        /**
+         * Whether the current selection fails validation.
+         *
+         * A flag rather than a message, the same split Date Picker draws. A flat
+         * picker has no room of its own for a sentence: the field that wraps one owns
+         * the label, the hint and the feedback, and a second message inside the panel
+         * would be the same error said twice. What is left for the picker is the one
+         * thing the field cannot draw from outside, the mark on the answer itself.
+         */
+        this.invalid = false;
+        /**
+         * Accessible name for the list, which has no visible one of its own.
+         */
+        this.label = 'Time';
         /**
          * Language tag the times are written in.
          *
@@ -176,9 +163,31 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
          */
         this.locale = '';
         /**
-         * Accessible name for the list, which has no visible one of its own.
+         * Latest time offered, as `HH:mm`.
          */
-        this.label = 'Time';
+        this.max = '23:59';
+        /**
+         * Earliest time offered, as `HH:mm`.
+         */
+        this.min = '00:00';
+        /**
+         * Whether the control refuses changes while still submitting its value.
+         *
+         * **Enforced by refusing every request in one place**, which is the seam this
+         * component already has: `requestValue` is what every path here comes through,
+         * and gating it once is what stops the next call site from being written
+         * without the check.
+         *
+         * Not `disabled`, which is the confusion worth naming: a disabled control
+         * submits nothing and leaves the tab order, and a read-only one submits its
+         * value and stays reachable, which is what a form showing a value somebody
+         * else set needs.
+         */
+        this.readOnly = false;
+        /**
+         * Whether the form refuses to submit while nothing is chosen.
+         */
+        this.required = false;
         /**
          * Takes what the list announced and constrains it to what the mode allows.
          *
@@ -191,12 +200,9 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
          */
         this.handleChange = (event) => {
             event.stopPropagation();
-            /* `disabled` meant nothing here beyond dropping the value at submit time,
-               the same gap the calendar had: times still took a click, the keyboard
-               still moved through the list, and nothing said the control was off. The
-               listbox is told as well, which is what grays it and takes it out of the
-               tab order, and this refuses at the source so every path in is covered by
-               one check.
+            /* The listbox is told as well, which is what grays it and takes it out of
+               the tab order, and this refuses at the source so every path in is covered
+               by one check.
                `isDisabled` rather than `disabled`, which is only the half a consumer
                wrote: an ancestor `<fieldset disabled>` is the other half. */
             if (this.isDisabled) {
@@ -261,23 +267,13 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
             this.requestValue(whole);
         };
         /**
-         * Whether the control refuses changes while still submitting its value.
-         *
-         * **Enforced by refusing every request in one place**, which is the seam this
-         * component already has: `requestValue` is what every path here comes through,
-         * and gating it once is what stops the next call site from being written
-         * without the check.
+         * How far apart the offered times are, in minutes.
          *
-         * Not `disabled`, which is the confusion worth naming: a disabled control
-         * submits nothing and leaves the tab order, and a read-only one submits its
-         * value and stays reachable, which is what a form showing a value somebody
-         * else set needs.
-         */
-        this.readOnly = false;
-        /**
-         * Whether the form refuses to submit while nothing is chosen.
+         * Fifteen, which is four rows an hour and ninety-six in a day: enough that a
+         * reader scrolls rather than hunts, and few enough that the list is a list.
+         * Anything under five is a thousand rows and wants a field instead.
          */
-        this.required = false;
+        this.step = 15;
     }
     /**
      * Every time on offer, as minutes since midnight.
@@ -413,11 +409,11 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
             this.internals.setValidity({ valueMissing: true }, 'Choose a time.', anchor);
             return;
         }
-        /* A value the wheels cannot read is bad input, the same as on the calendar
-           and for the same measured reason: `value="not-a-time"` marked no row,
-           reported `:valid` and was handed to the form. `asTime` rejects the hours
-           and minutes that are shaped right and out of range as well as the ones
-           that are not shaped right at all. */
+        /* A value the wheels cannot read is bad input, the same as on the calendar:
+           `value="not-a-time"` marks no row, and would otherwise report `:valid` and
+           be handed to the form. `asTime` rejects the hours and minutes that are
+           shaped right and out of range as well as the ones that are not shaped
+           right at all. */
         const held = this.held;
         if (held.length > 0 && held.some((one) => asTime(one) === null)) {
             this.internals.setValidity({ badInput: true }, this.mode === undefined
@@ -430,14 +426,6 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
     /**
      * Reports the times to the form, one entry each.
      *
-     * **This element was form-associated, took a `name`, held a `value` and
-     * reported `valueMissing`, and never called `setFormValue` at all.** So
-     * `<helix-time-picker name="start" required>` refused the submit until a
-     * reader filled it and then submitted nothing, which is the worst shape the
-     * omission takes: every visible signal says the control is participating.
-     * Measured before the fix, one form holding both pickers, both named and
-     * both seeded: the entry list carried the date and no time.
-     *
      * `FormData` and one entry per time, which is `DatePicker.report` exactly.
      * `mode="multiple"` is genuinely several answers, and a server reading
      * `times=09:00,17:00` would have to split it on a convention this library
@@ -472,9 +460,9 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
      * sat at `scrollTop: 0` with the answer nine rows down, which reads as a wheel
      * showing the wrong time rather than as one that failed to scroll.
      *
-     * It survived because the case that was tested was the panel, and whatever
-     * opens a panel calls `reveal` again afterwards for the separate reason the
-     * method documents. Flat on a page there is no panel and no second call.
+     * Whatever opens a panel calls `reveal` again afterwards, for the separate
+     * reason that method documents. Flat on a page there is no panel and no
+     * second call.
      *
      * Safe to run on every update: the listbox stops as soon as the chosen row is
      * within a pixel of center, so a call with nothing to do costs two rect reads
@@ -510,9 +498,11 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
     focus(options) {
         this.renderRoot?.querySelector('[part="list"]')?.focus(options);
     }
-    /* One wheel, which is a listbox like the whole list is. */
     /**
-     * One wheel.
+     * One wheel, which is a listbox like the whole list is.
+     *
+     * `protected` rather than `private`, which is the whole of what a seam is
+     * here: a tier above has to be able to reach it.
      *
      * `barred` is passed per column rather than read from `disableTimes` here,
      * because a column holds a third of a time and only the caller knows the
@@ -521,8 +511,6 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
      * barred only when every minute in it is, since one free minute is a reason to
      * open the wheel rather than to close it.
      */
-    /* `protected` rather than `private`, which is the whole of what a seam is
-       here: the method already existed and a tier above could not reach it. */
     renderColumn(part, label, values, written, value, barred = () => false) {
         return html `<${this.tag('listbox')}
       part="column"
@@ -563,7 +551,7 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
     </div>`;
     }
     /**
-     * The flat list of times, for the appearance that is not wheels, behind a seam the styled tier can move.
+     * The flat list of times, for the variant that is not wheels, behind a seam the styled tier can move.
      *
      * A method rather than a fragment inline, so a tier above can render its own,
      * wrap this one, pass it a property the base does not know about, or leave it
@@ -630,39 +618,39 @@ let HelixHeadlessTimePicker = class HelixHeadlessTimePicker extends MixinControl
         this.value = Number.isNaN(ms) ? '' : fromTime(new Date(ms));
     }
 };
+__decorate([
+    property({ attribute: 'disable-times' })
+], HelixHeadlessTimePicker.prototype, "disableTimes", void 0);
 __decorate([
     property({ reflect: true, type: Boolean })
 ], HelixHeadlessTimePicker.prototype, "invalid", void 0);
-__decorate([
-    property({ type: Number })
-], HelixHeadlessTimePicker.prototype, "step", void 0);
 __decorate([
     property()
-], HelixHeadlessTimePicker.prototype, "min", void 0);
+], HelixHeadlessTimePicker.prototype, "label", void 0);
 __decorate([
     property()
-], HelixHeadlessTimePicker.prototype, "max", void 0);
-__decorate([
-    property({ attribute: 'disable-times' })
-], HelixHeadlessTimePicker.prototype, "disableTimes", void 0);
+], HelixHeadlessTimePicker.prototype, "locale", void 0);
 __decorate([
     property()
-], HelixHeadlessTimePicker.prototype, "locale", void 0);
+], HelixHeadlessTimePicker.prototype, "max", void 0);
 __decorate([
     property()
-], HelixHeadlessTimePicker.prototype, "label", void 0);
+], HelixHeadlessTimePicker.prototype, "min", void 0);
 __decorate([
     property({ reflect: true })
 ], HelixHeadlessTimePicker.prototype, "mode", void 0);
-__decorate([
-    property({ reflect: true })
-], HelixHeadlessTimePicker.prototype, "variant", void 0);
 __decorate([
     property({ attribute: 'readonly', reflect: true, type: Boolean })
 ], HelixHeadlessTimePicker.prototype, "readOnly", void 0);
 __decorate([
     property({ reflect: true, type: Boolean })
 ], HelixHeadlessTimePicker.prototype, "required", void 0);
+__decorate([
+    property({ type: Number })
+], HelixHeadlessTimePicker.prototype, "step", void 0);
+__decorate([
+    property({ reflect: true })
+], HelixHeadlessTimePicker.prototype, "variant", void 0);
 HelixHeadlessTimePicker = __decorate([
     customElement('helix-headless-time-picker')
 ], HelixHeadlessTimePicker);

package/dist/timeline/item/timeline-item.d.ts

@@ -16,7 +16,7 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  * settles with no index, no counting parent and no script. `Steps` and
  * `Breadcrumbs` both do it this way and for the same reason.
  *
- * `tone` says what kind of event it was, and it is the only thing that colours
+ * `tone` says what kind of event it was, and it is the only thing that colors
  * the mark. It takes `Announcement`'s vocabulary rather than a second one.
  *
  * @since 0.1.0
@@ -27,9 +27,8 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  *
  * @slot - What happened.
  * @slot marker - The mark on the line. Falls back to a dot, which is the slot's
- * own fallback content rather than anything this element works out: whether a
- * consumer slotted a mark is a question only the platform can answer, and it
- * answers it by rendering what is inside the slot when nothing replaced it.
+ * own fallback content: whether a consumer slotted a mark is a question only the
+ * platform can answer, and it answers it at assignment time.
  * @slot time - When it happened, as a reader should see it written.
  *
  * @csspart connector - The line arriving at this entry.
@@ -56,13 +55,11 @@ export declare class HelixHeadlessTimelineItem extends HelixElement {
     /**
      * The mark for an entry that slotted none, which the tone decides.
      *
-     * **A `protected render…()` and not a getter, which is what it was.** A slot's
-     * fallback answers a consumer and a seam answers the tier above, and a getter
-     * answers neither: `check:fallbacks` permits `${this.x}` because a property is
-     * not markup a tier would redraw, and it tests for parentheses, so a getter
-     * returning a template reads as a bare reference and was let through. That is
-     * the same hole the check's own comment records closing for a static helper,
-     * reopened by a different spelling of the same thing.
+     * **A seam is a `protected render…()` and never a getter.** A slot's fallback
+     * answers a consumer and a seam answers the tier above, and a getter answers
+     * neither. The check tests for parentheses, `${this.x}` being permitted
+     * because a property is not markup a tier would redraw, so a getter returning
+     * a template reads as a bare reference and is let through.
      *
      * Toned entries are reporting something, so they take the circle with a
      * center, which is `Steps` drawing the stage a reader is standing on. Untoned

package/dist/timeline/item/timeline-item.js

@@ -25,7 +25,7 @@ import { unsafeSVG } from 'lit/directives/unsafe-svg.js';
  * settles with no index, no counting parent and no script. `Steps` and
  * `Breadcrumbs` both do it this way and for the same reason.
  *
- * `tone` says what kind of event it was, and it is the only thing that colours
+ * `tone` says what kind of event it was, and it is the only thing that colors
  * the mark. It takes `Announcement`'s vocabulary rather than a second one.
  *
  * @since 0.1.0
@@ -36,9 +36,8 @@ import { unsafeSVG } from 'lit/directives/unsafe-svg.js';
  *
  * @slot - What happened.
  * @slot marker - The mark on the line. Falls back to a dot, which is the slot's
- * own fallback content rather than anything this element works out: whether a
- * consumer slotted a mark is a question only the platform can answer, and it
- * answers it by rendering what is inside the slot when nothing replaced it.
+ * own fallback content: whether a consumer slotted a mark is a question only the
+ * platform can answer, and it answers it at assignment time.
  * @slot time - When it happened, as a reader should see it written.
  *
  * @csspart connector - The line arriving at this entry.
@@ -67,13 +66,11 @@ let HelixHeadlessTimelineItem = class HelixHeadlessTimelineItem extends HelixEle
     /**
      * The mark for an entry that slotted none, which the tone decides.
      *
-     * **A `protected render…()` and not a getter, which is what it was.** A slot's
-     * fallback answers a consumer and a seam answers the tier above, and a getter
-     * answers neither: `check:fallbacks` permits `${this.x}` because a property is
-     * not markup a tier would redraw, and it tests for parentheses, so a getter
-     * returning a template reads as a bare reference and was let through. That is
-     * the same hole the check's own comment records closing for a static helper,
-     * reopened by a different spelling of the same thing.
+     * **A seam is a `protected render…()` and never a getter.** A slot's fallback
+     * answers a consumer and a seam answers the tier above, and a getter answers
+     * neither. The check tests for parentheses, `${this.x}` being permitted
+     * because a property is not markup a tier would redraw, so a getter returning
+     * a template reads as a bare reference and is let through.
      *
      * Toned entries are reporting something, so they take the circle with a
      * center, which is `Steps` drawing the stage a reader is standing on. Untoned

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

@@ -21,13 +21,11 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  * reason `Steps` gives: the entries are the consumer's elements in the light
  * DOM, so a list element here would be a list whose items are somewhere else.
  *
- * **It runs down the page and has no horizontal form.** There was one, and it
- * was removed rather than tuned: laid along a line there is no room for the
- * time or the sentence that are the whole reason to reach for a timeline, so
- * what survives is a mark and a short label, and that is a stepper. `Steps` is
- * already horizontal by default and already draws it, so the horizontal version
- * of this was a second component rendering the same picture from thinner data.
- * A run of stages along a page is `Steps`.
+ * **It runs down the page and has no horizontal form.** Laid along a line there
+ * is no room for the time or the sentence that are the whole reason to reach for
+ * a timeline, so what survives is a mark and a short label, and that is a
+ * stepper. `Steps` is already horizontal by default and already draws it. A run
+ * of stages along a page is `Steps`.
  *
  * @since 0.1.0
  * @status stable

package/dist/timeline/root/timeline-root.js

@@ -28,13 +28,11 @@ import { property } from 'lit/decorators.js';
  * reason `Steps` gives: the entries are the consumer's elements in the light
  * DOM, so a list element here would be a list whose items are somewhere else.
  *
- * **It runs down the page and has no horizontal form.** There was one, and it
- * was removed rather than tuned: laid along a line there is no room for the
- * time or the sentence that are the whole reason to reach for a timeline, so
- * what survives is a mark and a short label, and that is a stepper. `Steps` is
- * already horizontal by default and already draws it, so the horizontal version
- * of this was a second component rendering the same picture from thinner data.
- * A run of stages along a page is `Steps`.
+ * **It runs down the page and has no horizontal form.** Laid along a line there
+ * is no room for the time or the sentence that are the whole reason to reach for
+ * a timeline, so what survives is a mark and a short label, and that is a
+ * stepper. `Steps` is already horizontal by default and already draws it. A run
+ * of stages along a page is `Steps`.
  *
  * @since 0.1.0
  * @status stable