@signal9/era-ui 29.0.0 → 30.0.1

package/CHANGELOG.md

@@ -1,3 +1,23 @@
+## [30.0.1](https://github.com/sig-nine/era-ui/compare/v30.0.0...v30.0.1) (2026-08-15)
+
+### Bug Fixes
+
+* **provider:** export axesAt/carryAxes, and gate the class of bug that hid them ([59ac508](https://github.com/sig-nine/era-ui/commit/59ac50883fcf198a14bfcbfebf38bab3c06073ed))
+
+## [30.0.0](https://github.com/sig-nine/era-ui/compare/v29.0.0...v30.0.0) (2026-08-15)
+
+### ⚠ BREAKING CHANGES
+
+* **notes:** createOverlayHost(from) now requires the element the overlay
+belongs to. It is internal to the notes app, which is not published.
+
+Claude-Session: https://claude.ai/code/session_011FjvULDrmxd61z2xUnYs6Z
+
+### Bug Fixes
+
+* **apps:** an icon beside a label goes in lead, not in children ([15d0589](https://github.com/sig-nine/era-ui/commit/15d0589045929c11b4dd6a29ef4f8a570c9a0156))
+* **notes:** the editor's overlay hosts carry the axes of the editor ([6a630c1](https://github.com/sig-nine/era-ui/commit/6a630c12d5847490305f279c73800e63094e5f8b))
+
 ## [29.0.0](https://github.com/sig-nine/era-ui/compare/v28.0.0...v29.0.0) (2026-08-15)
 
 ### ⚠ BREAKING CHANGES

package/dist/generated-docs/llms-full.txt

@@ -453,6 +453,20 @@ padding, the chrome doesn't move, and the caret and selection follow the
 text. In em on purpose: the correction is a fraction of the type, so it
 holds across every density and text size with one value.
 
+WHEN SOMEONE REPORTS A CORRECTLY-CENTRED FIELD AS "TOO HIGH", check the
+STRING before the geometry. A placeholder like "Filter…" has no descender and
+no cap, so its ink occupies only the x-height band — and a box that centres
+that band exactly still reads high, because the eye centres on the mass it
+can see and expects the space a descender would have filled. Measured at the
+pill tier on the shipped mono stack, "Filter…" sits within half a pixel of
+centre while looking a little high; the pill suite documents the same effect
+from the other side (see OFF_BAND_LOW in ink-centering.spec.ts, where "soon"
+cannot be symmetric and is bounded by sign instead of magnitude).
+
+That is not a licence to ignore the report — era-ink-center IS wrong by
+1.5–2px on the sans and serif stacks (pinned in FIELD_KNOWN_SKEW) — only a
+reason to measure the ink before touching the constant.
+
 Declared in `index.css`.
 
 ```css

package/dist/generated-docs/manifest.json

@@ -52,7 +52,7 @@
       "slug": "utilities",
       "title": "Utilities",
       "summary": "The CSS classes era ships alongside the components — links, ink-centred text, shimmer, hidden scrollbars.",
-      "tokenEstimate": 12389,
+      "tokenEstimate": 12608,
       "sections": [
         "Overview",
         "era-interactive",
@@ -1095,7 +1095,7 @@
       ],
       "file": "index.css",
       "useCase": "on a native single-line <input> (or the text layer that must mirror one) inside a fixed-height field — never alongside era-text-trim.",
-      "description": "The EDITABLE counterpart of era-text-trim — for native <input>s, which the\ntrim is forbidden on (it collapses the UA's inner editor box and slices the\nglyphs; see typography/collapsed-text-trim).\n\nWithout help, a tier-height input centres its text by FONT BOX, and the ui\nstacks' font box is deeply asymmetric: ascent ≈1.07em against descent\n≈0.29em. Centring that box parks the visible band (caps, x-height) ~0.115em\nLOW — so a field's text sat visibly below the trimmed label beside it.\n\nThe value is OPTICAL, not the derivation's: pure x-band centring computes\nto ~0.23em of padding, but pixel-measured against real Title-Case text it\nover-lifts — the eye weighs the cap-to-baseline mass, which x-band\ncentring parks ~2px high (caps 2.75px off the top against 5.7px of air\nunder the baseline, measured at dense). 0.08em splits the difference\nbetween the x-band ideal and the cap-band ideal, landing caps ~3.7px in an\n18px field with ~4.7px under the baseline — the reading where neither\nband's partisans win and neither complains.\n\nThe lift is padding, not a translateY: an icon-less Input paints the field\nchrome itself, and a transform would drag the field along with the ink.\npadding-bottom shrinks the content box from below, and a single-line input\nre-centres its line box in what remains — the ink rises by exactly half the\npadding, the chrome doesn't move, and the caret and selection follow the\ntext. In em on purpose: the correction is a fraction of the type, so it\nholds across every density and text size with one value.",
+      "description": "The EDITABLE counterpart of era-text-trim — for native <input>s, which the\ntrim is forbidden on (it collapses the UA's inner editor box and slices the\nglyphs; see typography/collapsed-text-trim).\n\nWithout help, a tier-height input centres its text by FONT BOX, and the ui\nstacks' font box is deeply asymmetric: ascent ≈1.07em against descent\n≈0.29em. Centring that box parks the visible band (caps, x-height) ~0.115em\nLOW — so a field's text sat visibly below the trimmed label beside it.\n\nThe value is OPTICAL, not the derivation's: pure x-band centring computes\nto ~0.23em of padding, but pixel-measured against real Title-Case text it\nover-lifts — the eye weighs the cap-to-baseline mass, which x-band\ncentring parks ~2px high (caps 2.75px off the top against 5.7px of air\nunder the baseline, measured at dense). 0.08em splits the difference\nbetween the x-band ideal and the cap-band ideal, landing caps ~3.7px in an\n18px field with ~4.7px under the baseline — the reading where neither\nband's partisans win and neither complains.\n\nThe lift is padding, not a translateY: an icon-less Input paints the field\nchrome itself, and a transform would drag the field along with the ink.\npadding-bottom shrinks the content box from below, and a single-line input\nre-centres its line box in what remains — the ink rises by exactly half the\npadding, the chrome doesn't move, and the caret and selection follow the\ntext. In em on purpose: the correction is a fraction of the type, so it\nholds across every density and text size with one value.\n\nWHEN SOMEONE REPORTS A CORRECTLY-CENTRED FIELD AS \"TOO HIGH\", check the\nSTRING before the geometry. A placeholder like \"Filter…\" has no descender and\nno cap, so its ink occupies only the x-height band — and a box that centres\nthat band exactly still reads high, because the eye centres on the mass it\ncan see and expects the space a descender would have filled. Measured at the\npill tier on the shipped mono stack, \"Filter…\" sits within half a pixel of\ncentre while looking a little high; the pill suite documents the same effect\nfrom the other side (see OFF_BAND_LOW in ink-centering.spec.ts, where \"soon\"\ncannot be symmetric and is bounded by sign instead of magnitude).\n\nThat is not a licence to ignore the report — era-ink-center IS wrong by\n1.5–2px on the sans and serif stacks (pinned in FIELD_KNOWN_SKEW) — only a\nreason to measure the ink before touching the constant.",
       "css": "@utility era-ink-center {\n\tpadding-bottom: 0.08em;\n}"
     },
     {

package/dist/generated-docs/utilities.json

@@ -67,7 +67,7 @@
       ],
       "file": "index.css",
       "useCase": "on a native single-line <input> (or the text layer that must mirror one) inside a fixed-height field — never alongside era-text-trim.",
-      "description": "The EDITABLE counterpart of era-text-trim — for native <input>s, which the\ntrim is forbidden on (it collapses the UA's inner editor box and slices the\nglyphs; see typography/collapsed-text-trim).\n\nWithout help, a tier-height input centres its text by FONT BOX, and the ui\nstacks' font box is deeply asymmetric: ascent ≈1.07em against descent\n≈0.29em. Centring that box parks the visible band (caps, x-height) ~0.115em\nLOW — so a field's text sat visibly below the trimmed label beside it.\n\nThe value is OPTICAL, not the derivation's: pure x-band centring computes\nto ~0.23em of padding, but pixel-measured against real Title-Case text it\nover-lifts — the eye weighs the cap-to-baseline mass, which x-band\ncentring parks ~2px high (caps 2.75px off the top against 5.7px of air\nunder the baseline, measured at dense). 0.08em splits the difference\nbetween the x-band ideal and the cap-band ideal, landing caps ~3.7px in an\n18px field with ~4.7px under the baseline — the reading where neither\nband's partisans win and neither complains.\n\nThe lift is padding, not a translateY: an icon-less Input paints the field\nchrome itself, and a transform would drag the field along with the ink.\npadding-bottom shrinks the content box from below, and a single-line input\nre-centres its line box in what remains — the ink rises by exactly half the\npadding, the chrome doesn't move, and the caret and selection follow the\ntext. In em on purpose: the correction is a fraction of the type, so it\nholds across every density and text size with one value.",
+      "description": "The EDITABLE counterpart of era-text-trim — for native <input>s, which the\ntrim is forbidden on (it collapses the UA's inner editor box and slices the\nglyphs; see typography/collapsed-text-trim).\n\nWithout help, a tier-height input centres its text by FONT BOX, and the ui\nstacks' font box is deeply asymmetric: ascent ≈1.07em against descent\n≈0.29em. Centring that box parks the visible band (caps, x-height) ~0.115em\nLOW — so a field's text sat visibly below the trimmed label beside it.\n\nThe value is OPTICAL, not the derivation's: pure x-band centring computes\nto ~0.23em of padding, but pixel-measured against real Title-Case text it\nover-lifts — the eye weighs the cap-to-baseline mass, which x-band\ncentring parks ~2px high (caps 2.75px off the top against 5.7px of air\nunder the baseline, measured at dense). 0.08em splits the difference\nbetween the x-band ideal and the cap-band ideal, landing caps ~3.7px in an\n18px field with ~4.7px under the baseline — the reading where neither\nband's partisans win and neither complains.\n\nThe lift is padding, not a translateY: an icon-less Input paints the field\nchrome itself, and a transform would drag the field along with the ink.\npadding-bottom shrinks the content box from below, and a single-line input\nre-centres its line box in what remains — the ink rises by exactly half the\npadding, the chrome doesn't move, and the caret and selection follow the\ntext. In em on purpose: the correction is a fraction of the type, so it\nholds across every density and text size with one value.\n\nWHEN SOMEONE REPORTS A CORRECTLY-CENTRED FIELD AS \"TOO HIGH\", check the\nSTRING before the geometry. A placeholder like \"Filter…\" has no descender and\nno cap, so its ink occupies only the x-height band — and a box that centres\nthat band exactly still reads high, because the eye centres on the mass it\ncan see and expects the space a descender would have filled. Measured at the\npill tier on the shipped mono stack, \"Filter…\" sits within half a pixel of\ncentre while looking a little high; the pill suite documents the same effect\nfrom the other side (see OFF_BAND_LOW in ink-centering.spec.ts, where \"soon\"\ncannot be symmetric and is bounded by sign instead of magnitude).\n\nThat is not a licence to ignore the report — era-ink-center IS wrong by\n1.5–2px on the sans and serif stacks (pinned in FIELD_KNOWN_SKEW) — only a\nreason to measure the ink before touching the constant.",
       "css": "@utility era-ink-center {\n\tpadding-bottom: 0.08em;\n}"
     },
     {

package/dist/generated-docs/utilities.md

@@ -304,6 +304,20 @@ padding, the chrome doesn't move, and the caret and selection follow the
 text. In em on purpose: the correction is a fraction of the type, so it
 holds across every density and text size with one value.
 
+WHEN SOMEONE REPORTS A CORRECTLY-CENTRED FIELD AS "TOO HIGH", check the
+STRING before the geometry. A placeholder like "Filter…" has no descender and
+no cap, so its ink occupies only the x-height band — and a box that centres
+that band exactly still reads high, because the eye centres on the mass it
+can see and expects the space a descender would have filled. Measured at the
+pill tier on the shipped mono stack, "Filter…" sits within half a pixel of
+centre while looking a little high; the pill suite documents the same effect
+from the other side (see OFF_BAND_LOW in ink-centering.spec.ts, where "soon"
+cannot be symmetric and is bounded by sign instead of magnitude).
+
+That is not a licence to ignore the report — era-ink-center IS wrong by
+1.5–2px on the sans and serif stacks (pinned in FIELD_KNOWN_SKEW) — only a
+reason to measure the ink before touching the constant.
+
 Declared in `index.css`.
 
 ```css

package/dist/styles/index.css

@@ -308,6 +308,20 @@
  * text. In em on purpose: the correction is a fraction of the type, so it
  * holds across every density and text size with one value.
  *
+ * WHEN SOMEONE REPORTS A CORRECTLY-CENTRED FIELD AS "TOO HIGH", check the
+ * STRING before the geometry. A placeholder like "Filter…" has no descender and
+ * no cap, so its ink occupies only the x-height band — and a box that centres
+ * that band exactly still reads high, because the eye centres on the mass it
+ * can see and expects the space a descender would have filled. Measured at the
+ * pill tier on the shipped mono stack, "Filter…" sits within half a pixel of
+ * centre while looking a little high; the pill suite documents the same effect
+ * from the other side (see OFF_BAND_LOW in ink-centering.spec.ts, where "soon"
+ * cannot be symmetric and is bounded by sign instead of magnitude).
+ *
+ * That is not a licence to ignore the report — era-ink-center IS wrong by
+ * 1.5–2px on the sans and serif stacks (pinned in FIELD_KNOWN_SKEW) — only a
+ * reason to measure the ink before touching the constant.
+ *
  * @use on a native single-line <input> (or the text layer that must mirror
  * one) inside a fixed-height field — never alongside era-text-trim. */
 @utility era-ink-center {

package/dist/ui/calendar/calendar-root.svelte.d.ts

@@ -1,4 +1,4 @@
 import { Calendar } from 'bits-ui';
-declare const CalendarRoot: import("svelte").Component<Calendar.RootProps, {}, "placeholder" | "value" | "ref">;
+declare const CalendarRoot: import("svelte").Component<Calendar.RootProps, {}, "value" | "placeholder" | "ref">;
 type CalendarRoot = ReturnType<typeof CalendarRoot>;
 export default CalendarRoot;

package/dist/ui/cycle/cycle.svelte.d.ts

@@ -3,7 +3,7 @@ import type { Snippet } from 'svelte';
 import { type ButtonVariants } from '../button/index.js';
 import type { CycleOption } from './types.js';
 declare function $$render<T extends string>(): {
-    props: Omit<HTMLButtonAttributes, "children" | "value"> & {
+    props: Omit<HTMLButtonAttributes, "value" | "children"> & {
         ref?: HTMLElement | null;
     } & Omit<ButtonVariants, "active"> & {
         /** The stops, in cycle order. Two or more. */

package/dist/ui/date-field/date-field-root.svelte.d.ts

@@ -1,3 +1,3 @@
-declare const DateFieldRoot: import("svelte").Component<import("bits-ui").DateFieldRootPropsWithoutHTML, {}, "placeholder" | "value">;
+declare const DateFieldRoot: import("svelte").Component<import("bits-ui").DateFieldRootPropsWithoutHTML, {}, "value" | "placeholder">;
 type DateFieldRoot = ReturnType<typeof DateFieldRoot>;
 export default DateFieldRoot;

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

@@ -1,3 +1,3 @@
-declare const DatePickerRoot: import("svelte").Component<import("bits-ui").DatePickerRootPropsWithoutHTML, {}, "placeholder" | "value" | "open">;
+declare const DatePickerRoot: import("svelte").Component<import("bits-ui").DatePickerRootPropsWithoutHTML, {}, "value" | "placeholder" | "open">;
 type DatePickerRoot = ReturnType<typeof DatePickerRoot>;
 export default DatePickerRoot;

package/dist/ui/date-range-field/date-range-field-root.svelte.d.ts

@@ -1,4 +1,4 @@
 import { DateRangeField } from 'bits-ui';
-declare const DateRangeFieldRoot: import("svelte").Component<DateRangeField.RootProps, {}, "placeholder" | "value" | "ref">;
+declare const DateRangeFieldRoot: import("svelte").Component<DateRangeField.RootProps, {}, "value" | "placeholder" | "ref">;
 type DateRangeFieldRoot = ReturnType<typeof DateRangeFieldRoot>;
 export default DateRangeFieldRoot;

package/dist/ui/date-range-picker/date-range-picker-root.svelte.d.ts

@@ -1,4 +1,4 @@
 import { DateRangePicker } from 'bits-ui';
-declare const DateRangePickerRoot: import("svelte").Component<DateRangePicker.RootProps, {}, "placeholder" | "value" | "open">;
+declare const DateRangePickerRoot: import("svelte").Component<DateRangePicker.RootProps, {}, "value" | "placeholder" | "open">;
 type DateRangePickerRoot = ReturnType<typeof DateRangePickerRoot>;
 export default DateRangePickerRoot;

package/dist/ui/provider/axes-at.d.ts

@@ -0,0 +1,16 @@
+export type Axes = {
+    /** Attributes to stamp on the receiving element. */
+    attrs: Record<string, string>;
+    /** `dark` / `light` when a scoped one is in force, else undefined. */
+    scheme?: 'dark' | 'light';
+};
+/** Read the axes governing `el`. Safe on null and on a detached node. */
+export declare function axesAt(el: Element | null | undefined): Axes;
+/**
+ * Stamp the axes governing `from` onto `to`.
+ *
+ * For hosts built by hand rather than rendered by a component, where there is
+ * no context to relay through and no markup to spread onto — the host has no
+ * other way to know where it logically belongs.
+ */
+export declare function carryAxes(to: HTMLElement, from: Element | null | undefined): void;

package/dist/ui/provider/axes-at.js

@@ -0,0 +1,65 @@
+import { axisKeys, axisRegistry } from './axes.js';
+/**
+ * THE AXES IN FORCE AT AN ELEMENT — the one implementation of that question.
+ *
+ * Anything that moves content to `document.body` has to answer it, because
+ * everything era styles with is inherited: the density ladder and roundness
+ * scale are custom properties on `*`, a surface re-baselines a token contract,
+ * the font axis publishes an inherited stack. Content that leaves its subtree
+ * stops inheriting from it and starts inheriting from `:root`.
+ *
+ * AxisRelay had this logic and could not share it. It lives in a `.svelte.ts`
+ * module because it holds `$state`, so a plain `.ts` consumer — the notes
+ * editor's overlay hosts, which are created by hand rather than by a component
+ * — could not import it without pulling runes into a non-rune module. So the
+ * notes app grew its own copy, and the copy was never written: the hosts simply
+ * did not carry the axes, and an editor inside `data-surface="flat"` opened a
+ * bevelled slash menu and bubble toolbar. Reported by signalnine.org, running
+ * flat demos inside a bevel site.
+ *
+ * Runes-free on purpose, for exactly the reason ancestor-path.ts is: the moment
+ * a shared truth can only be imported by components, the non-component callers
+ * reimplement it or skip it.
+ *
+ * NEAREST ANCESTOR PER AXIS, INDEPENDENTLY. A subtree can override density
+ * without touching surface, and `closest()` answers each question separately —
+ * which is what makes the axes orthogonal rather than a bundle.
+ */
+/** Theme is not an axis in the registry (no picker contract), but it inherits
+ *  the same way and breaks across a portal the same way. */
+const THEME_ATTR = 'data-theme';
+/** The colour-scheme pair is a CLASS, not an attribute, so it travels apart. */
+const SCHEME_CLASSES = ['dark', 'light'];
+/** Read the axes governing `el`. Safe on null and on a detached node. */
+export function axesAt(el) {
+    if (!el?.closest)
+        return { attrs: {} };
+    const attrs = {};
+    for (const key of axisKeys) {
+        const attr = axisRegistry[key].attr;
+        const value = el.closest(`[${attr}]`)?.getAttribute(attr);
+        if (value)
+            attrs[attr] = value;
+    }
+    const theme = el.closest(`[${THEME_ATTR}]`)?.getAttribute(THEME_ATTR);
+    if (theme)
+        attrs[THEME_ATTR] = theme;
+    const schemeHost = el.closest('.dark, .light');
+    const scheme = SCHEME_CLASSES.find((c) => schemeHost?.classList.contains(c));
+    return { attrs, scheme };
+}
+/**
+ * Stamp the axes governing `from` onto `to`.
+ *
+ * For hosts built by hand rather than rendered by a component, where there is
+ * no context to relay through and no markup to spread onto — the host has no
+ * other way to know where it logically belongs.
+ */
+export function carryAxes(to, from) {
+    const { attrs, scheme } = axesAt(from);
+    for (const [attr, value] of Object.entries(attrs))
+        to.setAttribute(attr, value);
+    to.classList.remove(...SCHEME_CLASSES);
+    if (scheme)
+        to.classList.add(scheme);
+}

package/dist/ui/provider/axis-relay.svelte.js

@@ -1,5 +1,5 @@
 import { getContext, hasContext, setContext } from 'svelte';
-import { axisKeys, axisRegistry } from './axes.js';
+import { axesAt } from './axes-at.js';
 /*
  * CARRYING THE AXES ACROSS A PORTAL.
  *
@@ -39,9 +39,6 @@ import { axisKeys, axisRegistry } from './axes.js';
  * absence is a null, not a crash.
  */
 const KEY = Symbol('era.axis-relay');
-/** The axis attributes, plus the theme pair, which is not in the axis registry. */
-const THEME_ATTR = 'data-theme';
-const SCHEME_CLASSES = ['dark', 'light'];
 export class AxisRelay {
     /** Attributes to stamp on portalled content. Empty until a capture runs. */
     attrs = $state({});
@@ -71,22 +68,12 @@ export class AxisRelay {
         const el = this.#anchor;
         if (!el?.closest)
             return;
-        const next = {};
-        for (const key of axisKeys) {
-            const attr = axisRegistry[key].attr;
-            const value = el.closest(`[${attr}]`)?.getAttribute(attr);
-            if (value)
-                next[attr] = value;
-        }
-        // Theme is not an axis in the registry (it has no picker contract), but it
-        // is inherited the same way and breaks across a portal the same way.
-        const theme = el.closest(`[${THEME_ATTR}]`)?.getAttribute(THEME_ATTR);
-        if (theme)
-            next[THEME_ATTR] = theme;
-        this.attrs = next;
-        // The colour-scheme pair is a CLASS, not an attribute, so it is separate.
-        const schemeHost = el.closest('.dark, .light');
-        this.scheme = SCHEME_CLASSES.find((c) => schemeHost?.classList.contains(c)) ?? undefined;
+        // The reading itself lives in axes-at.ts, runes-free, because the notes
+        // editor's hand-built overlay hosts need the same answer from a plain .ts
+        // module and cannot import this one. They had gone without it.
+        const { attrs, scheme } = axesAt(el);
+        this.attrs = attrs;
+        this.scheme = scheme;
     }
     /** The class string portalled content should carry. */
     get schemeClass() {

package/dist/ui/provider/index.d.ts

@@ -4,3 +4,17 @@ export { corners, defaultCorners, type Corners } from './modes.js';
 export { fonts, defaultFont, type Font } from './modes.js';
 export { motions, defaultMotion, type Motion } from './modes.js';
 export { axisRegistry, axisKeys, type AxisKey, type AxisMeta, type AxisLevel } from './axes.js';
+/**
+ * Reading the axes at a node, for anything that moves content to document.body
+ * outside era's own components — a hand-built overlay host, a canvas layer, an
+ * editor's floating chrome. era's portalling components go through AxisRelay;
+ * these have no context to relay through and no markup to spread onto.
+ *
+ * Exported because it shipped in the tarball reachable from nothing. `./*`
+ * resolves to a directory's index.js, so a module the index does not re-export
+ * is published and unimportable — a consumer measured it at runtime, got 13
+ * names, and correctly refused to deep-import past the exports map to reach the
+ * fourteenth. They kept a thirty-line copy instead, which is the right call and
+ * exactly the duplication axes-at.ts was extracted to prevent.
+ */
+export { axesAt, carryAxes, type Axes } from './axes-at.js';

package/dist/ui/provider/index.js

@@ -4,3 +4,17 @@ export { corners, defaultCorners } from './modes.js';
 export { fonts, defaultFont } from './modes.js';
 export { motions, defaultMotion } from './modes.js';
 export { axisRegistry, axisKeys } from './axes.js';
+/**
+ * Reading the axes at a node, for anything that moves content to document.body
+ * outside era's own components — a hand-built overlay host, a canvas layer, an
+ * editor's floating chrome. era's portalling components go through AxisRelay;
+ * these have no context to relay through and no markup to spread onto.
+ *
+ * Exported because it shipped in the tarball reachable from nothing. `./*`
+ * resolves to a directory's index.js, so a module the index does not re-export
+ * is published and unimportable — a consumer measured it at runtime, got 13
+ * names, and correctly refused to deep-import past the exports map to reach the
+ * fourteenth. They kept a thirty-line copy instead, which is the right call and
+ * exactly the duplication axes-at.ts was extracted to prevent.
+ */
+export { axesAt, carryAxes } from './axes-at.js';

package/dist/ui/time-field/time-field-root.svelte.d.ts

@@ -1,4 +1,4 @@
 import { TimeField } from 'bits-ui';
-declare const TimeFieldRoot: import("svelte").Component<TimeField.RootProps, {}, "placeholder" | "value">;
+declare const TimeFieldRoot: import("svelte").Component<TimeField.RootProps, {}, "value" | "placeholder">;
 type TimeFieldRoot = ReturnType<typeof TimeFieldRoot>;
 export default TimeFieldRoot;

package/dist/ui/time-range-field/time-range-field-root.svelte.d.ts

@@ -1,4 +1,4 @@
 import { TimeRangeField } from 'bits-ui';
-declare const TimeRangeFieldRoot: import("svelte").Component<TimeRangeField.RootProps, {}, "placeholder" | "value" | "ref">;
+declare const TimeRangeFieldRoot: import("svelte").Component<TimeRangeField.RootProps, {}, "value" | "placeholder" | "ref">;
 type TimeRangeFieldRoot = ReturnType<typeof TimeRangeFieldRoot>;
 export default TimeRangeFieldRoot;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@signal9/era-ui",
-	"version": "29.0.0",
+	"version": "30.0.1",
 	"scripts": {
 		"dev": "vite dev --host",
 		"build": "vite build && npm run prepack",
@@ -25,14 +25,15 @@
 		"check:classes": "node --experimental-strip-types scripts/check-classes.ts",
 		"check:twmerge": "node --experimental-strip-types scripts/check-twmerge.ts",
 		"build:llm-docs": "node --experimental-strip-types scripts/build-llm-docs.ts",
-		"prebuild": "npm run check:surfaces && npm run check:tokens && npm run check:routes && npm run check:canonical && npm run check:layers && npm run check:themes && npm run check:classes && npm run check:twmerge && npm run check:doc-tokens && npm run check:audit-controls && npm run check:specimen-coverage && npm run check:eslint-rules && npm run check:install && npm run check:double-edge && npm run build:llm-docs",
-		"validate": "npm run check && npm run lint && npm run format:check && npm run check:surfaces && npm run check:tokens && npm run check:routes && npm run check:canonical && npm run check:layers && npm run check:themes && npm run check:classes && npm run check:twmerge && npm run check:doc-tokens && npm run check:audit-controls && npm run check:specimen-coverage && npm run check:eslint-rules && npm run check:install && npm run check:double-edge",
+		"prebuild": "npm run check:surfaces && npm run check:tokens && npm run check:routes && npm run check:canonical && npm run check:layers && npm run check:themes && npm run check:classes && npm run check:twmerge && npm run check:doc-tokens && npm run check:audit-controls && npm run check:specimen-coverage && npm run check:eslint-rules && npm run check:install && npm run check:reachable && npm run check:double-edge && npm run build:llm-docs",
+		"validate": "npm run check && npm run lint && npm run format:check && npm run check:surfaces && npm run check:tokens && npm run check:routes && npm run check:canonical && npm run check:layers && npm run check:themes && npm run check:classes && npm run check:twmerge && npm run check:doc-tokens && npm run check:audit-controls && npm run check:specimen-coverage && npm run check:eslint-rules && npm run check:install && npm run check:reachable && npm run check:double-edge",
 		"test": "npm run test:visual",
 		"check:doc-tokens": "node --experimental-strip-types scripts/check-doc-tokens.ts",
 		"check:audit-controls": "node --experimental-strip-types scripts/check-audit-controls.ts",
 		"check:specimen-coverage": "node --experimental-strip-types scripts/check-specimen-coverage.ts",
 		"check:eslint-rules": "node --experimental-strip-types scripts/check-eslint-rules.ts",
 		"check:install": "node --experimental-strip-types scripts/check-install.ts",
+		"check:reachable": "node --experimental-strip-types scripts/check-reachable.ts",
 		"check:double-edge": "node --experimental-strip-types scripts/check-double-edge.ts",
 		"verify:published": "node scripts/verify-published.mjs"
 	},