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

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

@@ -39,9 +39,19 @@ export declare class HelixHeadlessDrilldownItem extends HelixElement {
      */
     disabled: boolean;
     /**
-     * Identifies the row to whatever is listening.
+     * Whether this row holds the region's tab stop. Written by the stack.
+     *
+     * A drill-down keeps one stop and moves within it on the arrows, so every
+     * other row is at `-1`. Leave it off every row, including the first, and
+     * nothing in the region is tab-reachable: the keyboard cannot get in without
+     * first clicking something with a pointer.
+     *
+     * No attribute, the same as `Button`'s: this is coordination between
+     * elements, and writing `tabindex` onto a host the consumer rendered is a
+     * change a React consumer's hydration reports and does not patch up. The stop
+     * lands inside this shadow root instead.
      */
-    value: string;
+    focusable: boolean;
     /**
      * @internal Read by a parent to identify its children across the light DOM,
      * which is cheaper than `instanceof` and is why this is public rather than
@@ -61,19 +71,9 @@ export declare class HelixHeadlessDrilldownItem extends HelixElement {
      */
     showingPage: boolean;
     /**
-     * Whether this row holds the region's tab stop. Written by the stack.
-     *
-     * A drill-down keeps one stop and moves within it on the arrows, so every
-     * other row is at `-1`. Every row was, including the first, which left
-     * nothing in the region tab-reachable at all: the keyboard could not get in
-     * without first clicking something with a pointer.
-     *
-     * No attribute, the same as `Button`'s: this is coordination between
-     * elements, and writing `tabindex` onto a host the consumer rendered is a
-     * change a React consumer's hydration reports and does not patch up. The stop
-     * lands inside this shadow root instead.
+     * Identifies the row to whatever is listening.
      */
-    focusable: boolean;
+    value: string;
     /** Moves focus onto the row itself. */
     focusItem(): void;
     /** Announces that this row was chosen. */

package/dist/drilldown/item/drilldown-item.js

@@ -48,9 +48,19 @@ let HelixHeadlessDrilldownItem = class HelixHeadlessDrilldownItem extends HelixE
          */
         this.disabled = false;
         /**
-         * Identifies the row to whatever is listening.
+         * Whether this row holds the region's tab stop. Written by the stack.
+         *
+         * A drill-down keeps one stop and moves within it on the arrows, so every
+         * other row is at `-1`. Leave it off every row, including the first, and
+         * nothing in the region is tab-reachable: the keyboard cannot get in without
+         * first clicking something with a pointer.
+         *
+         * No attribute, the same as `Button`'s: this is coordination between
+         * elements, and writing `tabindex` onto a host the consumer rendered is a
+         * change a React consumer's hydration reports and does not patch up. The stop
+         * lands inside this shadow root instead.
          */
-        this.value = '';
+        this.focusable = false;
         /**
          * @internal Read by a parent to identify its children across the light DOM,
          * which is cheaper than `instanceof` and is why this is public rather than
@@ -70,19 +80,9 @@ let HelixHeadlessDrilldownItem = class HelixHeadlessDrilldownItem extends HelixE
          */
         this.showingPage = false;
         /**
-         * Whether this row holds the region's tab stop. Written by the stack.
-         *
-         * A drill-down keeps one stop and moves within it on the arrows, so every
-         * other row is at `-1`. Every row was, including the first, which left
-         * nothing in the region tab-reachable at all: the keyboard could not get in
-         * without first clicking something with a pointer.
-         *
-         * No attribute, the same as `Button`'s: this is coordination between
-         * elements, and writing `tabindex` onto a host the consumer rendered is a
-         * change a React consumer's hydration reports and does not patch up. The stop
-         * lands inside this shadow root instead.
+         * Identifies the row to whatever is listening.
          */
-        this.focusable = false;
+        this.value = '';
     }
     /** Moves focus onto the row itself. */
     focusItem() {
@@ -104,16 +104,14 @@ let HelixHeadlessDrilldownItem = class HelixHeadlessDrilldownItem extends HelixE
         }
         /* A real `<button>`, and `role="menuitem"` on it.
          *
-         * It was a `<div role="button">` with a click handler and nothing else, so
-         * the row could not be activated from the keyboard at all: Enter and Space
-         * are behavior the platform gives a real button and gives nothing else,
-         * and neither was handled here. Same argument `Button` makes for rendering
-         * one rather than reproducing it.
+         * A `<div role="button">` with a click handler cannot be activated from the
+         * keyboard: Enter and Space are behavior the platform gives a real button
+         * and gives nothing else. Same argument `Button` makes for rendering one
+         * rather than reproducing it.
          *
          * `menuitem` because the stack says `role="menu"`, and a menu whose
-         * children are buttons is not a menu: the roles contradicted each other and
-         * a reader was told the count of items by one and the kind of them by the
-         * other.
+         * children are buttons is not a menu: a reader would be told the count of
+         * items by one role and the kind of them by the other.
          *
          * `aria-disabled` rather than `disabled`, so a row that cannot be chosen is
          * still reachable and still announces why. `select()` is what refuses. */
@@ -135,8 +133,8 @@ __decorate([
     property({ reflect: true, type: Boolean })
 ], HelixHeadlessDrilldownItem.prototype, "disabled", void 0);
 __decorate([
-    property()
-], HelixHeadlessDrilldownItem.prototype, "value", void 0);
+    property({ attribute: false })
+], HelixHeadlessDrilldownItem.prototype, "focusable", void 0);
 __decorate([
     property({ attribute: false })
 ], HelixHeadlessDrilldownItem.prototype, "onPage", void 0);
@@ -144,8 +142,8 @@ __decorate([
     property({ attribute: false })
 ], HelixHeadlessDrilldownItem.prototype, "showingPage", void 0);
 __decorate([
-    property({ attribute: false })
-], HelixHeadlessDrilldownItem.prototype, "focusable", void 0);
+    property()
+], HelixHeadlessDrilldownItem.prototype, "value", void 0);
 HelixHeadlessDrilldownItem = __decorate([
     customElement('helix-headless-drilldown-item')
 ], HelixHeadlessDrilldownItem);

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

@@ -61,12 +61,11 @@ export declare class HelixHeadlessDrilldown extends HelixHeadlessDrilldown_base
      * reader went deeper or came back. Without it a slide has to pick one
      * direction and be wrong half the time.
      *
-     * **Undefined until a move has happened**, which is what "the last move" means
-     * before there has been one. It defaulted to `forward` and was written on the
-     * first update, which cost two things: an attribute on the host that a
-     * consumer's server never sent, reported as a hydration mismatch, and a first
-     * page that animated itself in on load, since an animation is not a transition
-     * and the settle guard does not suppress it.
+     * **Undefined until a move has happened**, and never defaulted. A value
+     * written on the first update puts an attribute on the host that a consumer's
+     * server never sent, reported as a hydration mismatch, and animates the first
+     * page in on load: an animation is not a transition, so the settle guard does
+     * not suppress it.
      */
     private direction?;
     private readonly drilldown;
@@ -75,10 +74,9 @@ export declare class HelixHeadlessDrilldown extends HelixHeadlessDrilldown_base
     /**
      * Puts the region's one tab stop on the first row of the page showing.
      *
-     * Every row rendered at `-1`, so nothing in the region was tab-reachable and
-     * the keyboard could not get in at all without a pointer first. One row holds
-     * the stop and the arrows move within, which is the roving pattern the
-     * toolbar uses and the one a `menu` wants.
+     * One row holds the stop and the arrows move within, which is the roving
+     * pattern the toolbar uses and the one a `menu` wants. Every row at `-1` is
+     * a region the keyboard cannot get into at all without a pointer first.
      *
      * Called after every update, because the set changes with the page: drilling
      * in replaces the rows outright, and the stop has to land on rows that are

package/dist/drilldown/root/drilldown-root.js

@@ -133,10 +133,9 @@ let HelixHeadlessDrilldown = class HelixHeadlessDrilldown extends MixinCollectio
     /**
      * Puts the region's one tab stop on the first row of the page showing.
      *
-     * Every row rendered at `-1`, so nothing in the region was tab-reachable and
-     * the keyboard could not get in at all without a pointer first. One row holds
-     * the stop and the arrows move within, which is the roving pattern the
-     * toolbar uses and the one a `menu` wants.
+     * One row holds the stop and the arrows move within, which is the roving
+     * pattern the toolbar uses and the one a `menu` wants. Every row at `-1` is
+     * a region the keyboard cannot get into at all without a pointer first.
      *
      * Called after every update, because the set changes with the page: drilling
      * in replaces the rows outright, and the stop has to land on rows that are
@@ -247,9 +246,9 @@ let HelixHeadlessDrilldown = class HelixHeadlessDrilldown extends MixinCollectio
 };
 __decorate([
     property()
-    /* Not "Menu", which is what it was: this component's own description is built
-       around not being one, and a default accessible name is the one place that
-       claim reaches a reader. */
+    /* Not "Menu". This component's own description is built around not being one,
+       and a default accessible name is the one place that claim reaches a
+       reader. */
 ], HelixHeadlessDrilldown.prototype, "label", void 0);
 __decorate([
     property({ attribute: 'back-label' })

package/dist/element-events.generated.js

@@ -1,4 +1,4 @@
-/* Generated by `bun run element-events` from this package's manifest. Do not edit.
+/* Generated by `bun run gen:element-events` from this package's manifest. Do not edit.
  *
  * Which events each tag dispatches, registered so the React prop audit can tell
  * a handler on the wrong element from one on the right one. See

package/dist/file-input/root/file-input-root.d.ts

@@ -9,10 +9,9 @@ declare const HelixHeadlessFileInput_base: (new (...args: any[]) => import("@fus
  * **A real `<input type="file">`, kept and made invisible rather than
  * replaced.** It is the only way to open a file picker: the dialog is a
  * privileged action a script cannot start on its own, and it opens for a click
- * on the input or on a `<label>` pointing at it. Every version of this component
- * that draws its own button ends up calling `.click()` on a hidden input
- * anyway, and then has two things a screen reader can find where there is one
- * control.
+ * on the input or on a `<label>` pointing at it. A component that draws its own
+ * button ends up calling `.click()` on a hidden input anyway, and then has two
+ * things a screen reader can find where there is one control.
  *
  * So the input stays, holds the label, the name, the validity and the focus,
  * and the visible trigger is a `<label for>` rather than a button. A label is
@@ -25,10 +24,10 @@ declare const HelixHeadlessFileInput_base: (new (...args: any[]) => import("@fus
  *
  * **Files are not a value a consumer can hand back.** Every other control here
  * takes the controlled and uncontrolled pair, and this one does not: a `FileList`
- * cannot be constructed from markup, and a consumer writing `value` on a file
- * input is the one thing browsers refuse outright, because a page that could
- * name a file could read it. So this element owns what was chosen, announces it,
- * and offers `clear()` for the one change a consumer can legitimately ask for.
+ * cannot be constructed from markup, and browsers refuse a consumer writing
+ * `value` on a file input outright, because a page that could name a file could
+ * read it. So this element owns what was chosen, announces it, and offers
+ * `clear()` for the one change a consumer can legitimately ask for.
  *
  * **The list under it is the control's own, not decoration.** A file input with
  * files chosen reports "3 files" and nothing else, which is unusable for
@@ -55,7 +54,6 @@ declare const HelixHeadlessFileInput_base: (new (...args: any[]) => import("@fus
  * @csspart field - The box that is pressed and dropped on.
  * @csspart file - One chosen file.
  * @csspart hint - Help under the field, while nothing is wrong.
- * @csspart icon - A glyph this component draws.
  * @csspart kind - What kind of file it is.
  * @csspart kind-dismiss - The remove button, when `dismissible`.
  * @csspart kind-dismiss-mark - The glyph on the dismiss control, where none is slotted.
@@ -77,28 +75,28 @@ export declare class HelixHeadlessFileInput extends HelixHeadlessFileInput_base
      * Which files the picker offers, as a native `accept` list.
      */
     accept: string;
-    /**
-     * Whether more than one file can be chosen.
-     */
-    multiple: boolean;
     /**
      * Which camera or microphone a mobile picker should offer, if any.
      */
     capture?: 'environment' | 'user';
-    /**
-     * What the trigger reads, where nothing is slotted into it.
-     */
-    triggerLabel: string;
     /**
      * Language tag the sizes are written in.
      *
      * Absent uses the runtime's own.
      */
     locale: string;
+    /**
+     * Whether more than one file can be chosen.
+     */
+    multiple: boolean;
     /**
      * What the control removing one file is called, per file.
      */
     removeLabel: string;
+    /**
+     * What the trigger reads, where nothing is slotted into it.
+     */
+    triggerLabel: string;
     /**
      * Whether something is being dragged over the field.
      *
@@ -175,15 +173,13 @@ export declare class HelixHeadlessFileInput extends HelixHeadlessFileInput_base
      * element saying two things and two methods would be two places to keep in
      * step. Both parts are written out rather than passed in, and that is not
      * style: a part name behind an interpolation is a part the manifest cannot
-     * see, so `check:selectors` reported the stylesheet as matching nothing the
-     * moment this took the name as an argument.
+     * see, so a stylesheet targeting it matches nothing.
      *
      * 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
-     * out, without reimplementing the whole template to do any of them. The tag is
-     * interpolated rather than written, so `tier` resolves it: this renders the
-     * headless element, and a styled subclass that sets `tier` renders the styled one
-     * from the same template.
+     * wrap this one, or leave it out without reimplementing the whole template.
+     * The tag is interpolated rather than written, so `tier` resolves it: this
+     * renders the headless element, and a styled subclass that sets `tier`
+     * renders the styled one from the same template.
      */
     protected renderMeta(file: File): TemplateResult;
     protected render(): TemplateResult;

package/dist/file-input/root/file-input-root.js

@@ -19,7 +19,7 @@ import '../../tag/index.js';
  * a thing.
  *
  * `Intl.NumberFormat` for the number rather than `toFixed`, so a decimal comma
- * lands where a decimal comma belongs. The unit is not localised with it: `MB`
+ * lands where a decimal comma belongs. The unit is not localized with it: `MB`
  * is written the same way in the places this ships, and `Intl`'s own byte units
  * carry no scale to pick from.
  */
@@ -62,10 +62,9 @@ const kind = (file) => {
  * **A real `<input type="file">`, kept and made invisible rather than
  * replaced.** It is the only way to open a file picker: the dialog is a
  * privileged action a script cannot start on its own, and it opens for a click
- * on the input or on a `<label>` pointing at it. Every version of this component
- * that draws its own button ends up calling `.click()` on a hidden input
- * anyway, and then has two things a screen reader can find where there is one
- * control.
+ * on the input or on a `<label>` pointing at it. A component that draws its own
+ * button ends up calling `.click()` on a hidden input anyway, and then has two
+ * things a screen reader can find where there is one control.
  *
  * So the input stays, holds the label, the name, the validity and the focus,
  * and the visible trigger is a `<label for>` rather than a button. A label is
@@ -78,10 +77,10 @@ const kind = (file) => {
  *
  * **Files are not a value a consumer can hand back.** Every other control here
  * takes the controlled and uncontrolled pair, and this one does not: a `FileList`
- * cannot be constructed from markup, and a consumer writing `value` on a file
- * input is the one thing browsers refuse outright, because a page that could
- * name a file could read it. So this element owns what was chosen, announces it,
- * and offers `clear()` for the one change a consumer can legitimately ask for.
+ * cannot be constructed from markup, and browsers refuse a consumer writing
+ * `value` on a file input outright, because a page that could name a file could
+ * read it. So this element owns what was chosen, announces it, and offers
+ * `clear()` for the one change a consumer can legitimately ask for.
  *
  * **The list under it is the control's own, not decoration.** A file input with
  * files chosen reports "3 files" and nothing else, which is unusable for
@@ -108,7 +107,6 @@ const kind = (file) => {
  * @csspart field - The box that is pressed and dropped on.
  * @csspart file - One chosen file.
  * @csspart hint - Help under the field, while nothing is wrong.
- * @csspart icon - A glyph this component draws.
  * @csspart kind - What kind of file it is.
  * @csspart kind-dismiss - The remove button, when `dismissible`.
  * @csspart kind-dismiss-mark - The glyph on the dismiss control, where none is slotted.
@@ -139,24 +137,24 @@ let HelixHeadlessFileInput = class HelixHeadlessFileInput extends MixinField(Hel
          * Which files the picker offers, as a native `accept` list.
          */
         this.accept = '';
-        /**
-         * Whether more than one file can be chosen.
-         */
-        this.multiple = false;
-        /**
-         * What the trigger reads, where nothing is slotted into it.
-         */
-        this.triggerLabel = 'Choose files';
         /**
          * Language tag the sizes are written in.
          *
          * Absent uses the runtime's own.
          */
         this.locale = '';
+        /**
+         * Whether more than one file can be chosen.
+         */
+        this.multiple = false;
         /**
          * What the control removing one file is called, per file.
          */
         this.removeLabel = 'Remove';
+        /**
+         * What the trigger reads, where nothing is slotted into it.
+         */
+        this.triggerLabel = 'Choose files';
         /**
          * Whether something is being dragged over the field.
          *
@@ -295,12 +293,10 @@ let HelixHeadlessFileInput = class HelixHeadlessFileInput extends MixinField(Hel
            bind and what a native file input sends when the chosen files move: both,
            in that order, the way every other control here does.
     
-           `input` was declared and never sent until 27 Aug 2026. The only one a
-           consumer received was the inner `<input type="file">`'s own, composed out
-           of this shadow root, so the documented event did not exist and an
-           undocumented one arrived in its place. Found by sweeping every family
-           that renders a native control rather than every family the first pass
-           named. See 308. */
+           Without the explicit `input`, the only one a consumer receives is the
+           inner `<input type="file">`'s own, composed out of this shadow root, so
+           the documented event does not exist and an undocumented one arrives in
+           its place. */
         this.dispatchEvent(new Event('input', { bubbles: true, composed: true }));
         this.dispatchEvent(new Event('change', { bubbles: true, composed: false }));
     }
@@ -327,12 +323,10 @@ let HelixHeadlessFileInput = class HelixHeadlessFileInput extends MixinField(Hel
            Kept, as a decision rather than an omission. A phantom entry naming a file
            that does not exist is a thing every server reading this form has to know
            to discard, and the reason the platform sends one is compatibility with
-           form encodings that predate `FormData` rather than anything a reader wants.
-           `check:platform-fidelity` excuses `value` on this family already, for the
-           neighbouring reason that the native one is `C:\fakepath\name`; this is
-           the same component declining to reproduce a lie, one level down. Recorded
-           here because a divergence nobody wrote down is indistinguishable from one
-           nobody noticed. */
+           form encodings that predate `FormData`. `value` is excused on this family
+           already, for the neighboring reason that the native one is
+           `C:\fakepath\name`; this is the same component declining to reproduce a
+           lie, one level down. */
         this.internals.setFormValue(data);
         const control = this.control;
         if (!control) {
@@ -361,22 +355,15 @@ let HelixHeadlessFileInput = class HelixHeadlessFileInput extends MixinField(Hel
     /*
      * The hint goes under the field, and the list after both.
      *
-     * It was under the list, on the reading that the field and its files are one
-     * block and the hint describes the block. Three things say otherwise.
-     *
      * A hint is instruction for the next action rather than a note about the
      * result: "up to 10MB each" is a rule for what may be added, and a rule read
-     * after the outcome is a rule read too late.
+     * after the outcome is a rule read too late. Its position also has to be
+     * stable, and under the list it travels down the page as files are added, a
+     * card's height at a time. Every other field here puts it immediately under
+     * the control.
      *
-     * Its position has to be stable, and this is the one that decides it. Under
-     * the list the hint travels down the page as files are added, a card's height
-     * at a time, so the one piece of guidance the control carries is never twice
-     * in the same place. Every other field here puts it immediately under the
-     * control, and a reader who has learned where to look should not have to
-     * relearn it for this one.
-     *
-     * And feedback stands in place of the hint rather than beside it, so wherever
-     * the hint is, an error is. An error about a file that was refused belongs
+     * Feedback stands in place of the hint rather than beside it, so wherever the
+     * hint is, an error is. An error about a file that was refused belongs
      * against the control that refused it, not below a list of the ones that were
      * not.
      */
@@ -388,15 +375,13 @@ let HelixHeadlessFileInput = class HelixHeadlessFileInput extends MixinField(Hel
      * element saying two things and two methods would be two places to keep in
      * step. Both parts are written out rather than passed in, and that is not
      * style: a part name behind an interpolation is a part the manifest cannot
-     * see, so `check:selectors` reported the stylesheet as matching nothing the
-     * moment this took the name as an argument.
+     * see, so a stylesheet targeting it matches nothing.
      *
      * 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
-     * out, without reimplementing the whole template to do any of them. The tag is
-     * interpolated rather than written, so `tier` resolves it: this renders the
-     * headless element, and a styled subclass that sets `tier` renders the styled one
-     * from the same template.
+     * wrap this one, or leave it out without reimplementing the whole template.
+     * The tag is interpolated rather than written, so `tier` resolves it: this
+     * renders the headless element, and a styled subclass that sets `tier`
+     * renders the styled one from the same template.
      */
     renderMeta(file) {
         return html `<${this.tag('tag')} part="size"
@@ -435,7 +420,7 @@ let HelixHeadlessFileInput = class HelixHeadlessFileInput extends MixinField(Hel
       </div>
       <!-- The hint sits under the field and the list goes last, which is the
            one ordering decision this component makes differently from the way it
-           reads. Reasoning below the template. -->
+           reads. Reasoning above renderMeta. -->
       ${this.renderHint()}${this.renderFeedback()}
       ${files.length === 0
             ? nothing
@@ -464,21 +449,21 @@ let HelixHeadlessFileInput = class HelixHeadlessFileInput extends MixinField(Hel
 __decorate([
     property()
 ], HelixHeadlessFileInput.prototype, "accept", void 0);
-__decorate([
-    property({ reflect: true, type: Boolean })
-], HelixHeadlessFileInput.prototype, "multiple", void 0);
 __decorate([
     property()
 ], HelixHeadlessFileInput.prototype, "capture", void 0);
-__decorate([
-    property({ attribute: 'trigger-label' })
-], HelixHeadlessFileInput.prototype, "triggerLabel", void 0);
 __decorate([
     property()
 ], HelixHeadlessFileInput.prototype, "locale", void 0);
+__decorate([
+    property({ reflect: true, type: Boolean })
+], HelixHeadlessFileInput.prototype, "multiple", void 0);
 __decorate([
     property({ attribute: 'remove-label' })
 ], HelixHeadlessFileInput.prototype, "removeLabel", void 0);
+__decorate([
+    property({ attribute: 'trigger-label' })
+], HelixHeadlessFileInput.prototype, "triggerLabel", void 0);
 __decorate([
     state()
 ], HelixHeadlessFileInput.prototype, "dropping", void 0);

package/dist/format-date/root/format-date-root.js

@@ -142,7 +142,7 @@ let HelixHeadlessFormatDate = class HelixHeadlessFormatDate extends HelixElement
            ordinary reasons: built in `firstUpdated` alone this comes back
            permanently dead the first time a list is reordered. Guarded on
            `hasUpdated` because the first connection happens before there is anything
-           to watch. See `check:observers`. */
+           to watch. */
         if (this.hasUpdated) {
             this.watch();
         }

package/dist/heatmap/root/buckets.d.ts

@@ -3,7 +3,7 @@
  *
  * Kept apart from the element because both answers are arithmetic and both are
  * easy to get subtly wrong in ways a picture hides: a threshold comparison off
- * by one boundary colours a handful of cells wrong out of ninety, and a fit
+ * by one boundary colors a handful of cells wrong out of ninety, and a fit
  * calculation off by one drops a day silently. Neither is visible in a
  * screenshot of a strip.
  */
@@ -18,7 +18,7 @@ export interface Reading {
  * **The cell's own tone wins**, and that ordering is the whole reason both
  * exist. A status page already knows a day was degraded; making it encode that
  * as a number so a component can decode it again is work for nothing, and the
- * encoding would have to agree with the thresholds or the colours would drift
+ * encoding would have to agree with the thresholds or the colors would drift
  * from the truth. A contribution graph has only counts and wants the buckets.
  *
  * Thresholds are read as lower bounds, in the order given, and the last one that
@@ -48,13 +48,13 @@ export declare const words: (source: string) => string[];
  * cannot show, which is why the element reflects the number and announces it.
  *
  * **What crosses the width is a column, and `rows` is how many cells are in
- * one.** This counted cells until 27 Aug 2026, which is the same number only
- * while `rows` is 1. At `rows="7"` a ten week graph came out at fifty-nine
+ * one.** Counting cells is the same number only while `rows` is 1. Divide by
+ * the wrong thing at `rows="7"` and a ten week graph comes back as fifty-nine
  * readings in a 592px box: eleven days dropped to fit a strip that wanted 156
- * pixels, and the fifty-nine were not a multiple of seven, so every column after
- * the cut was offset by a day and the day-of-week rows stopped meaning anything.
- * A calendar heatmap that silently rotates its own weekdays is worse than one
- * that drops a week, and both came from dividing by the wrong thing.
+ * pixels, and fifty-nine is not a multiple of seven, so every column after the
+ * cut is offset by a day and the day-of-week rows stop meaning anything. A
+ * calendar heatmap that silently rotates its own weekdays is worse than one
+ * that drops a week.
  *
  * The count is therefore always a whole number of columns, which is what keeps
  * the tail slice aligned.

package/dist/heatmap/root/buckets.js

@@ -3,7 +3,7 @@
  *
  * Kept apart from the element because both answers are arithmetic and both are
  * easy to get subtly wrong in ways a picture hides: a threshold comparison off
- * by one boundary colours a handful of cells wrong out of ninety, and a fit
+ * by one boundary colors a handful of cells wrong out of ninety, and a fit
  * calculation off by one drops a day silently. Neither is visible in a
  * screenshot of a strip.
  */
@@ -13,7 +13,7 @@
  * **The cell's own tone wins**, and that ordering is the whole reason both
  * exist. A status page already knows a day was degraded; making it encode that
  * as a number so a component can decode it again is work for nothing, and the
- * encoding would have to agree with the thresholds or the colours would drift
+ * encoding would have to agree with the thresholds or the colors would drift
  * from the truth. A contribution graph has only counts and wants the buckets.
  *
  * Thresholds are read as lower bounds, in the order given, and the last one that
@@ -61,13 +61,13 @@ export const words = (source) => source.split(/[\s,]+/).filter((one) => one !==
  * cannot show, which is why the element reflects the number and announces it.
  *
  * **What crosses the width is a column, and `rows` is how many cells are in
- * one.** This counted cells until 27 Aug 2026, which is the same number only
- * while `rows` is 1. At `rows="7"` a ten week graph came out at fifty-nine
+ * one.** Counting cells is the same number only while `rows` is 1. Divide by
+ * the wrong thing at `rows="7"` and a ten week graph comes back as fifty-nine
  * readings in a 592px box: eleven days dropped to fit a strip that wanted 156
- * pixels, and the fifty-nine were not a multiple of seven, so every column after
- * the cut was offset by a day and the day-of-week rows stopped meaning anything.
- * A calendar heatmap that silently rotates its own weekdays is worse than one
- * that drops a week, and both came from dividing by the wrong thing.
+ * pixels, and fifty-nine is not a multiple of seven, so every column after the
+ * cut is offset by a day and the day-of-week rows stop meaning anything. A
+ * calendar heatmap that silently rotates its own weekdays is worse than one
+ * that drops a week.
  *
  * The count is therefore always a whole number of columns, which is what keeps
  * the tail slice aligned.