@ecoma-io/loom 0.2.0 → 0.3.0

package/dist/lib/count-labels.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"count-labels.js","names":[],"sources":["../../src/lib/count-labels.ts"],"sourcesContent":["import type { LabelOf } from \"./labels\";\n\n/**\n * The five counter keys shared by TextField and Textarea — the ones a host\n * worded for one can copy across unchanged to the other. The keys match by\n * name and by argument shape; the slots are separate in `LoomLabels` only\n * because `textField` also carries `reveal`.\n *\n * The four counting keys take the **numbers**, never a formatted string, for\n * the reason `./labels.ts` gives at length: `${count}/${max}` is a punctuation\n * choice made in one language, and \"3 characters left\" has one plural form in\n * Vietnamese, two in English and six in Arabic. A host handed the integers\n * reaches `Intl.PluralRules` for the category and `Intl.NumberFormat` for the\n * digits; a host handed \"3/20\" can do neither.\n *\n * There are three visible counter strings rather than one with a conditional\n * inside it, because the three say different things: a running total against\n * no limit, a total against a limit, and a limit already passed. The last is\n * the one that must not read as merely a redder version of the second — see\n * `countOverMax`.\n */\nexport interface CountLabels {\n  /** The counter when the field has no maximum: a running total, nothing more. */\n  readonly count: LabelOf<{ count: number }>;\n  /** The counter when the field has a maximum and is within it. */\n  readonly countOfMax: LabelOf<{ count: number; max: number }>;\n  /**\n   * The counter once the value is past the maximum.\n   *\n   * Loom's English adds words rather than only digits, and that is the\n   * accessibility requirement rather than a flourish: over-limit is painted\n   * `text-destructive`, and a state carried by colour alone fails WCAG 1.4.1.\n   * An override that returns the same shape as `countOfMax` puts that failure\n   * back.\n   */\n  readonly countOverMax: LabelOf<{ count: number; max: number; over: number }>;\n  /**\n   * Announced **once**, as the value crosses into the last stretch of its\n   * allowance — not on every keystroke after it. The numbers are true at the\n   * moment it is spoken; the visible counter is what carries them afterwards.\n   */\n  readonly approachingLimit: LabelOf<{ remaining: number; max: number }>;\n  /** Announced once, as the value crosses the maximum. */\n  readonly limitExceeded: LabelOf<{ over: number; max: number }>;\n}\n\n/**\n * Loom's English defaults for the counter vocabulary, co-located here so the\n * two components that share it tree-shake together and an importing host can\n * build a partial vocabulary against the real thing rather than a transcription.\n */\nexport const COUNT_LABELS: CountLabels = {\n  count: ({ count }) => String(count),\n  countOfMax: ({ count, max }) => `${String(count)}/${String(max)}`,\n  countOverMax: ({ count, max }) => `${String(count)}/${String(max)} over limit`,\n  approachingLimit: ({ remaining }) =>\n    `${String(remaining)} ${remaining === 1 ? \"character\" : \"characters\"} left`,\n  limitExceeded: ({ over, max }) =>\n    `${String(over)} ${over === 1 ? \"character\" : \"characters\"} over the limit of ${String(max)}`,\n};\n\n/**\n * How close to the maximum the warning fires: the last quarter of a short\n * allowance, or the last ten characters of a long one, whichever is smaller.\n *\n * Ten is about a word, and a warning is only worth anything while there is\n * still room to act on it — a fixed tenth would give a 280-character field\n * twenty-eight characters of notice and a twenty-character field two, which is\n * either too early to mean anything or too late to be a warning.\n */\nexport function warningWindow(max: number): number {\n  return Math.min(10, Math.ceil(max / 4));\n}\n\n/** Where the value sits against its maximum, and the only thing the announcement watches. */\nexport type CountBand = \"under\" | \"near\" | \"over\";\n"],"mappings":";;;;;;AAmDA,IAAa,eAA4B;CACvC,QAAQ,EAAE,YAAY,OAAO,KAAK;CAClC,aAAa,EAAE,OAAO,UAAU,GAAG,OAAO,KAAK,EAAE,GAAG,OAAO,GAAG;CAC9D,eAAe,EAAE,OAAO,UAAU,GAAG,OAAO,KAAK,EAAE,GAAG,OAAO,GAAG,EAAE;CAClE,mBAAmB,EAAE,gBACnB,GAAG,OAAO,SAAS,EAAE,GAAG,cAAc,IAAI,cAAc,aAAa;CACvE,gBAAgB,EAAE,MAAM,UACtB,GAAG,OAAO,IAAI,EAAE,GAAG,SAAS,IAAI,cAAc,aAAa,qBAAqB,OAAO,GAAG;AAC9F;;;;;;;;;;AAWA,SAAgB,cAAc,KAAqB;CACjD,OAAO,KAAK,IAAI,IAAI,KAAK,KAAK,MAAM,CAAC,CAAC;AACxC"}

package/dist/lib/date-labels.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"date-labels.d.ts","sourceRoot":"","sources":["../../src/lib/date-labels.ts"],"names":[],"mappings":"AAAA,OAAO,EAAoB,KAAK,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAC3E,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,UAAU,CAAC;AAExC;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,WAAW,iBAAiB;IAChC,yCAAyC;IACzC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,gCAAgC;IAChC,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,wBAAwB;IACxB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB;;;OAGG;IACH,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB;;;;;;;;;;;;OAYG;IACH,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB;;;;;;;;;;;;;;;;;OAiBG;IACH,QAAQ,CAAC,WAAW,EAAE,OAAO,CAAC;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CAClE;AAED;;;;GAIG;AACH,eAAO,MAAM,mBAAmB,EAAE,iBAkBjC,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,WAAW,iBAAiB;IAChC,wBAAwB;IACxB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,0BAA0B;IAC1B,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,+EAA+E;IAC/E,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,6DAA6D;IAC7D,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,oGAAoG;IACpG,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB;;;;;;;;;;;;;;OAcG;IACH,QAAQ,CAAC,eAAe,EAAE,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CAC1D;AAED,uEAAuE;AACvE,eAAO,MAAM,mBAAmB,EAAE,iBAUjC,CAAC;AAEF;;;;;;;;;GASG;AACH,MAAM,MAAM,eAAe,GAAG,OAAO,CAAC,MAAM,iBAAiB,EAAE,OAAO,GAAG,aAAa,CAAC,CAAC;AACxF,MAAM,MAAM,eAAe,GAAG,OAAO,CAAC,MAAM,iBAAiB,EAAE,OAAO,GAAG,iBAAiB,CAAC,CAAC;AAqB5F;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,qBAAqB,CACnC,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE,MAAM,EACb,KAAK,EAAE,MAAM,GACZ;IAAE,gBAAgB,CAAC,EAAE,MAAM,CAAA;CAAE,CAE/B;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,IAAI,eAAe,CAEvE;AAED,gFAAgF;AAChF,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,IAAI,eAAe,CAEvE;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,WAAW,mBAAmB;IAClC,8EAA8E;IAC9E,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,+DAA+D;IAC/D,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,yDAAyD;IACzD,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;IAC/B,uDAAuD;IACvD,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;CAC5B;AAED,0EAA0E;AAC1E,eAAO,MAAM,qBAAqB,EAAE,mBAKnC,CAAC;AAEF;;;;;;;;GAQG;AACH,MAAM,MAAM,aAAa,GAAG,OAAO,GAAG,KAAK,GAAG,MAAM,GAAG,QAAQ,CAAC;AAEhE;;;;;;;;;GASG;AACH,MAAM,WAAW,eAAe;IAC9B;;;;;;OAMG;IACH,QAAQ,CAAC,IAAI,EAAE,OAAO,CAAC;QACrB,MAAM,EAAE,MAAM,CAAC;QACf,IAAI,EAAE,SAAS,CAAC;QAChB,IAAI,EAAE,aAAa,GAAG,SAAS,CAAC;KACjC,CAAC,CAAC;CACJ;AAED;;;;;;GAMG;AACH,eAAO,MAAM,iBAAiB,EAAE,eAQ/B,CAAC;AAaF;;;;;;GAMG;AACH,wBAAgB,SAAS,CAAC,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,CAQ/D;AAED;;;;;;;GAOG;AACH,wBAAgB,aAAa,CAAC,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,GAAG,MAAM,CAYrE"}

package/dist/lib/date-labels.js

@@ -1,157 +0,0 @@
-import { getLocalTimeZone as $ad063034c8620db8$export$aa8b41735afcabd2 } from "../node_modules/.pnpm/@internationalized_date@3.12.3/node_modules/@internationalized/date/dist/private/queries.js";
-//#region src/lib/date-labels.ts
-/**
-* Loom's English for the date segments, co-located so it tree-shakes with the
-* controls that use it, and exported so a host can build a partial vocabulary
-* against the real thing rather than a transcription of it.
-*/
-var DATE_SEGMENT_LABELS = {
-	month: "Month",
-	day: "Day",
-	year: "Year",
-	era: "Era",
-	empty: "Not set",
-	filledMonth: ({ value, locale }) => {
-		const name = monthName(locale, value);
-		return `${String(value)} - ${name}`;
-	}
-};
-/** Loom's English for the time segments. See `DATE_SEGMENT_LABELS`. */
-var TIME_SEGMENT_LABELS = {
-	hour: "Hour",
-	minute: "Minute",
-	second: "Second",
-	dayPeriod: "AM or PM",
-	empty: "Not set",
-	filledDayPeriod: ({ dayPeriod }) => dayPeriod
-};
-var DATE_SEGMENT_PARTS = /* @__PURE__ */ new Set([
-	"month",
-	"day",
-	"year",
-	"era"
-]);
-var TIME_SEGMENT_PARTS = /* @__PURE__ */ new Set([
-	"hour",
-	"minute",
-	"second",
-	"dayPeriod"
-]);
-/**
-* The six segments Reka reports as `aria-valuetext="Empty"` when they hold
-* nothing — and, not by coincidence, the six that render as digits when they
-* hold something. `dayPeriod` and `era` are absent because Reka never writes
-* "Empty" on either: an unset `dayPeriod` reads `AM` and an unset `era` reads
-* the placeholder's own era, both of which are already the locale's words.
-*/
-var EMPTIABLE_SEGMENT_PARTS = /* @__PURE__ */ new Set([
-	"day",
-	"month",
-	"year",
-	"hour",
-	"minute",
-	"second"
-]);
-/**
-* The `aria-valuetext` override for one segment, as an object to `v-bind`
-* rather than a string to bind directly — and that is the whole point of it.
-*
-* Reka writes `aria-valuetext="Empty"` on an unfilled segment and the number
-* on a filled one, and only the first is a hard-coded English literal: the
-* second is `${valueNow}`, and the month's `"3 - March"` takes its month name
-* from the field's own `locale`. So this replaces exactly the empty case and
-* leaves the rest alone. Binding `:aria-valuetext` directly could not do that
-* — Vue merges a fallthrough `undefined` over Reka's value and *removes* the
-* attribute, so a filled segment would lose the number it is there to read
-* out. An absent key merges as nothing at all, which is what `optional()`
-* exists for elsewhere and what returning `{}` does here.
-*
-* Emptiness is read off the digits in the segment's own displayed value, which
-* is sound in both directions for these six parts: every locale's placeholder
-* for them is letters (`mm`, `jj`, `aaaa`) and every value they can hold is
-* digits. The two parts where that would not hold are the two excluded above.
-*/
-function emptySegmentValueText(part, value, empty) {
-	return EMPTIABLE_SEGMENT_PARTS.has(part) && !/\d/.test(value) ? { "aria-valuetext": empty } : {};
-}
-/**
-* Whether a part named by Reka's `segments` slot is one this slice names.
-*
-* A guard rather than an index, because the slot also yields `literal` — the
-* slashes and colons between the segments, which Reka renders `aria-hidden`
-* and which must stay unnamed — and `timeZoneName`, which none of these five
-* controls can produce: their values parse through `parseDate`, `parseTime` and
-* `parseDateTime`, none of which yields a zoned value, and no prop on any of
-* them accepts a zone. Reka's `"timezone, "` is therefore unreachable from
-* here, and a key for it would be a key nothing could ever render.
-*/
-function isDateSegmentPart(part) {
-	return DATE_SEGMENT_PARTS.has(part);
-}
-/** Whether a part named by Reka's `segments` slot belongs to the clock half. */
-function isTimeSegmentPart(part) {
-	return TIME_SEGMENT_PARTS.has(part);
-}
-/** Loom's English for the calendar popover. See `DATE_SEGMENT_LABELS`. */
-var CALENDAR_PANEL_LABELS = {
-	calendar: "Calendar",
-	openCalendar: "Open calendar",
-	previousMonth: "Previous month",
-	nextMonth: "Next month"
-};
-/**
-* Loom's English for a range calendar's cells. The three fills that carry the
-* first day, the last and the ones between are three shades of one colour,
-* which survives neither a colour deficiency nor forced-colors mode — naming
-* the part is what tells them apart, and it is what makes a one-day span say so
-* once rather than announce itself twice as two different things.
-*/
-var RANGE_CELL_LABELS = { cell: ({ locale, date, part }) => {
-	const full = formatFullDay(locale, date);
-	if (part === "both") return `${full}, the whole range, first and last day`;
-	if (part === "start") return `${full}, first day of the range`;
-	if (part === "end") return `${full}, last day of the range`;
-	return part === "within" ? `${full}, within the range` : full;
-} };
-var dayFormatters = /* @__PURE__ */ new Map();
-var monthFormatters = /* @__PURE__ */ new Map();
-/**
-* A month name in the control's locale, for use in `aria-valuetext`.
-*
-* Exported so a host building a partial vocabulary can call it from their own
-* `filledMonth` override rather than formatting from scratch — the same reason
-* `formatFullDay` is exported.
-*/
-function monthName(locale, month) {
-	let formatter = monthFormatters.get(locale);
-	if (!formatter) {
-		formatter = new Intl.DateTimeFormat(locale, { month: "long" });
-		monthFormatters.set(locale, formatter);
-	}
-	return formatter.format(new Date(2026, month - 1, 1));
-}
-/**
-* A whole day written out — weekday, day, month and year — in the control's
-* locale, which is the half of a range cell's name that is not a qualifier.
-*
-* Exported because both range controls' English defaults need it and neither
-* should own it; a host replacing those defaults formats with whatever their
-* own application already uses and never calls this.
-*/
-function formatFullDay(locale, date) {
-	let formatter = dayFormatters.get(locale);
-	if (!formatter) {
-		formatter = new Intl.DateTimeFormat(locale, {
-			weekday: "long",
-			day: "numeric",
-			month: "long",
-			year: "numeric"
-		});
-		dayFormatters.set(locale, formatter);
-	}
-	return formatter.format(date.toDate($ad063034c8620db8$export$aa8b41735afcabd2()));
-}
-//#endregion
-export { CALENDAR_PANEL_LABELS, DATE_SEGMENT_LABELS, RANGE_CELL_LABELS, TIME_SEGMENT_LABELS, emptySegmentValueText, formatFullDay, isDateSegmentPart, isTimeSegmentPart, monthName };
-
-//# sourceMappingURL=date-labels.js.map

package/dist/lib/date-labels.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"date-labels.js","names":[],"sources":["../../src/lib/date-labels.ts"],"sourcesContent":["import { getLocalTimeZone, type DateValue } from \"@internationalized/date\";\nimport type { LabelOf } from \"./labels\";\n\n/**\n * The four slices the five date and time controls share, and the one decision\n * behind putting them here rather than five times over.\n *\n * Every other component in the library declares its own bag beside its own\n * markup, because its vocabulary is its own. These five do not have five\n * vocabularies: `DatePicker`, `DateTimePicker`, `DateRangePicker` and\n * `DateTimeRangePicker` all say *Open calendar*, *Previous month* and *Next\n * month*, and all five name the parts of a segmented field with the same\n * words — the words are Reka UI's `useDateField` and `CalendarRoot` speaking,\n * one implementation underneath all five. Declared per component that would be\n * fifty-two keys with the same twelve strings written four times, and a\n * translator doing the same work four times to make one language complete.\n *\n * **Sliced by what a control actually says, not merged into one family bag.**\n * A `TimePicker` has no calendar and never renders a month or a year, so it\n * registers `timeSegments` alone: its documented vocabulary is four keys, and a\n * consumer importing only that control ships only those four strings. One\n * shared bag for the whole family would have made every one of the five carry\n * all twenty, and would have printed keys on `TimePicker`'s API page that it\n * has no element to put them on.\n *\n * What is deliberately *not* shared is the two range controls' half-group names\n * and status lines. They name the same concepts with different words (`Start\n * date` against `Start date and time`) and from different facts (a count of\n * whole days against a signed duration in minutes), so a shared key would have\n * to be a sentence that is never true of both. Their calendar cells' names are\n * shared, because those differ in neither.\n */\n\n/**\n * The names Reka UI's `useDateField` writes onto the day, month, year and era\n * segments — `\"day,\"`, `\"month, \"`, `\"year, \"`, `\"era\"`, each with the spacing\n * of a string it meant to concatenate.\n *\n * There is no prop for any of them. A binding on Loom's side reaches the\n * segment as a fallthrough attribute, which Vue merges onto the rendered vnode\n * *after* Reka's own render function produced it, and `mergeProps` is\n * last-write-wins for everything that is not `class`, `style` or `on*` — so\n * these replace Reka's rather than competing with it. Leave one unset and the\n * segment is not unnamed, it is named in English, which is the failure this\n * seam exists to close.\n *\n * Loom's defaults differ from Reka's by their capitalisation, which is what\n * lets a test assert *whose* string reached the DOM rather than merely what it\n * said.\n */\nexport interface DateSegmentLabels {\n  /** The month segment of a date field. */\n  readonly month: string;\n  /** The day-of-month segment. */\n  readonly day: string;\n  /** The year segment. */\n  readonly year: string;\n  /**\n   * The era segment, which most locales never render — `ja-JP-u-ca-japanese`\n   * is the ordinary case that does.\n   */\n  readonly era: string;\n  /**\n   * What a segment with nothing in it yet reports as its value, replacing the\n   * `aria-valuetext=\"Empty\"` Reka writes on an unfilled day, month or year.\n   *\n   * A segment shows the locale's own placeholder — `mm`, `jj`, `aaaa` — while\n   * announcing this instead, so it is the one word standing between a fully\n   * localised date field and a reader who is told \"Empty\" in English.\n   *\n   * Present on this slice *and* on `TimeSegmentLabels` rather than shared\n   * between them, for the reason the slices exist at all: a `TimePicker`\n   * registers no `dateSegments`, and a key it could only reach through the\n   * date half would be a key it could not set.\n   */\n  readonly empty: string;\n  /**\n   * What a filled month segment announces as its value, replacing the\n   * `aria-valuetext` Reka builds inside `useDateField`.\n   *\n   * Reka writes `\"5 - May\"` — the numeric month, a hard-coded `\" - \"`, and\n   * the month name from `Intl.DateTimeFormat`. The name is locale-aware, but\n   * the format is not: Japanese writes `\"5月\"`, Vietnamese `\"tháng 5\"`, and\n   * neither separates the two parts with a hyphen. A `LabelOf` hands the\n   * host the month number and the locale so they can compose the string their\n   * language needs, using `Intl.DateTimeFormat` for the name and arranging the\n   * parts in the right order.\n   *\n   * A `LabelOf` rather than a plain string, for the same reason\n   * `RangeCellLabels.cell` is one: the month name depends on the locale, and\n   * a string that did not receive the locale could not produce it. The host\n   * decides the format — Loom's English default matches Reka's output so that\n   * nothing changes for a consumer who does not override it.\n   */\n  readonly filledMonth: LabelOf<{ value: number; locale: string }>;\n}\n\n/**\n * Loom's English for the date segments, co-located so it tree-shakes with the\n * controls that use it, and exported so a host can build a partial vocabulary\n * against the real thing rather than a transcription of it.\n */\nexport const DATE_SEGMENT_LABELS: DateSegmentLabels = {\n  month: \"Month\",\n  day: \"Day\",\n  year: \"Year\",\n  era: \"Era\",\n  // \"Not set\" rather than Reka's own \"Empty\", and the difference is load-bearing\n  // in the same way the capitalisation of the names above is: it is what lets a\n  // test assert whose string reached the DOM. It also reads better spoken — a\n  // reader is being told this field has no value yet, not that it is blank.\n  empty: \"Not set\",\n  // Matches Reka's `\"5 - May\"` format for English. The month name comes from\n  // `Intl.DateTimeFormat` via the cached `monthFormatters` map, which avoids\n  // reconstructing the formatter on every render. A host overrides this to\n  // change the format — Japanese `\"5月\"`, Vietnamese `\"tháng 5\"`, etc.\n  filledMonth: ({ value, locale }) => {\n    const name = monthName(locale, value);\n    return `${String(value)} - ${name}`;\n  },\n};\n\n/**\n * The same, for the clock half of a segmented field: Reka writes `\"hour, \"`,\n * `\"minute, \"`, `\"second, \"` and `\"AM/PM\"`, and offers a prop for none of them.\n *\n * `dayPeriod` is spelled `AM or PM` rather than `AM/PM` so that it reads as\n * words when it is spoken, and so the capitalisation trick above still works on\n * the one segment whose name Reka already capitalises.\n */\nexport interface TimeSegmentLabels {\n  /** The hour segment. */\n  readonly hour: string;\n  /** The minute segment. */\n  readonly minute: string;\n  /** The seconds segment, which only a control at second granularity renders. */\n  readonly second: string;\n  /** The AM/PM segment, which only a 12-hour field renders. */\n  readonly dayPeriod: string;\n  /** What an hour, minute or second with nothing in it yet reports. See `DateSegmentLabels.empty`. */\n  readonly empty: string;\n  /**\n   * What a filled day-period segment announces as its value, replacing the\n   * `aria-valuetext` Reka writes inside `useDateField`.\n   *\n   * Reka writes `segmentValues.dayPeriod ?? \"AM\"` — always `\"AM\"` or `\"PM\"`,\n   * produced by its own hour-cycle logic (`hour >= 12 ? \"PM\" : \"AM\"`) rather\n   * than by `Intl.DateTimeFormat`. A host who has localised every other string\n   * in the library still hears Latin-script \"AM\"/\"PM\" from this segment, which\n   * is the defect this key exists to close.\n   *\n   * A `LabelOf` rather than a plain string, because the period name depends on\n   * the locale: Arabic writes `\"ص\"`/`\"م\"`, Japanese `\"午前\"`/`\"午後\"`, and a\n   * plain string could not carry that decision. Loom's English default returns\n   * `dayPeriod` unchanged, which is correct for Latin-script locales.\n   */\n  readonly filledDayPeriod: LabelOf<{ dayPeriod: string }>;\n}\n\n/** Loom's English for the time segments. See `DATE_SEGMENT_LABELS`. */\nexport const TIME_SEGMENT_LABELS: TimeSegmentLabels = {\n  hour: \"Hour\",\n  minute: \"Minute\",\n  second: \"Second\",\n  dayPeriod: \"AM or PM\",\n  empty: \"Not set\",\n  // The identity function for English: Reka's `\"AM\"`/`\"PM\"` are correct for\n  // Latin-script locales. A host localising to Arabic, Japanese, etc. overrides\n  // this to return the locale's own period names.\n  filledDayPeriod: ({ dayPeriod }) => dayPeriod,\n};\n\n/**\n * The parts each slice actually names — every key of its bag except `empty`,\n * which is a message *about* a segment rather than the name of one.\n *\n * Both the type and the set below are written out rather than derived from the\n * bags, which is what they were before `empty` joined them. Derived, the guards\n * would answer `true` for `\"empty\"` and narrow a part to a key that names no\n * element, and `segmentLabel` would happily return the empty message as a\n * segment's accessible name.\n */\nexport type DateSegmentName = Exclude<keyof DateSegmentLabels, \"empty\" | \"filledMonth\">;\nexport type TimeSegmentName = Exclude<keyof TimeSegmentLabels, \"empty\" | \"filledDayPeriod\">;\n\nconst DATE_SEGMENT_PARTS = new Set<DateSegmentName>([\"month\", \"day\", \"year\", \"era\"]);\nconst TIME_SEGMENT_PARTS = new Set<TimeSegmentName>([\"hour\", \"minute\", \"second\", \"dayPeriod\"]);\n\n/**\n * The six segments Reka reports as `aria-valuetext=\"Empty\"` when they hold\n * nothing — and, not by coincidence, the six that render as digits when they\n * hold something. `dayPeriod` and `era` are absent because Reka never writes\n * \"Empty\" on either: an unset `dayPeriod` reads `AM` and an unset `era` reads\n * the placeholder's own era, both of which are already the locale's words.\n */\nconst EMPTIABLE_SEGMENT_PARTS = new Set<string>([\n  \"day\",\n  \"month\",\n  \"year\",\n  \"hour\",\n  \"minute\",\n  \"second\",\n]);\n\n/**\n * The `aria-valuetext` override for one segment, as an object to `v-bind`\n * rather than a string to bind directly — and that is the whole point of it.\n *\n * Reka writes `aria-valuetext=\"Empty\"` on an unfilled segment and the number\n * on a filled one, and only the first is a hard-coded English literal: the\n * second is `${valueNow}`, and the month's `\"3 - March\"` takes its month name\n * from the field's own `locale`. So this replaces exactly the empty case and\n * leaves the rest alone. Binding `:aria-valuetext` directly could not do that\n * — Vue merges a fallthrough `undefined` over Reka's value and *removes* the\n * attribute, so a filled segment would lose the number it is there to read\n * out. An absent key merges as nothing at all, which is what `optional()`\n * exists for elsewhere and what returning `{}` does here.\n *\n * Emptiness is read off the digits in the segment's own displayed value, which\n * is sound in both directions for these six parts: every locale's placeholder\n * for them is letters (`mm`, `jj`, `aaaa`) and every value they can hold is\n * digits. The two parts where that would not hold are the two excluded above.\n */\nexport function emptySegmentValueText(\n  part: string,\n  value: string,\n  empty: string,\n): { \"aria-valuetext\"?: string } {\n  return EMPTIABLE_SEGMENT_PARTS.has(part) && !/\\d/.test(value) ? { \"aria-valuetext\": empty } : {};\n}\n\n/**\n * Whether a part named by Reka's `segments` slot is one this slice names.\n *\n * A guard rather than an index, because the slot also yields `literal` — the\n * slashes and colons between the segments, which Reka renders `aria-hidden`\n * and which must stay unnamed — and `timeZoneName`, which none of these five\n * controls can produce: their values parse through `parseDate`, `parseTime` and\n * `parseDateTime`, none of which yields a zoned value, and no prop on any of\n * them accepts a zone. Reka's `\"timezone, \"` is therefore unreachable from\n * here, and a key for it would be a key nothing could ever render.\n */\nexport function isDateSegmentPart(part: string): part is DateSegmentName {\n  return DATE_SEGMENT_PARTS.has(part as DateSegmentName);\n}\n\n/** Whether a part named by Reka's `segments` slot belongs to the clock half. */\nexport function isTimeSegmentPart(part: string): part is TimeSegmentName {\n  return TIME_SEGMENT_PARTS.has(part as TimeSegmentName);\n}\n\n/**\n * Everything the calendar popover says that is not a date: the panel's own\n * name, the button that opens it, and the two that page the months.\n *\n * `calendar` is Reka's `CalendarRoot`/`RangeCalendarRoot` `calendarLabel` prop,\n * whose default is the string `\"Event Date\"` — a name for somebody else's\n * application, published both as the grid container's `aria-label` and inside a\n * visually-hidden live region that a screen reader reads on every month change.\n * It is a documented prop rather than a hard-coded literal, so it is the one\n * name in this file that is set rather than overridden.\n *\n * `previousMonth` and `nextMonth` do replace literals: Reka writes\n * `\"Previous page\"` and `\"Next page\"` on those two buttons, which is both\n * English and wrong — what they move is a month.\n */\nexport interface CalendarPanelLabels {\n  /** The calendar's own name, read before the month and year on entering it. */\n  readonly calendar: string;\n  /** The button in the field that opens the calendar popover. */\n  readonly openCalendar: string;\n  /** The button that pages the calendar back one month. */\n  readonly previousMonth: string;\n  /** The button that pages the calendar on one month. */\n  readonly nextMonth: string;\n}\n\n/** Loom's English for the calendar popover. See `DATE_SEGMENT_LABELS`. */\nexport const CALENDAR_PANEL_LABELS: CalendarPanelLabels = {\n  calendar: \"Calendar\",\n  openCalendar: \"Open calendar\",\n  previousMonth: \"Previous month\",\n  nextMonth: \"Next month\",\n};\n\n/**\n * Which part of a chosen span one calendar cell plays, handed to the cell's\n * label rather than resolved into words by the control.\n *\n * Four sibling keys and a joiner would be four phrases a translator cannot\n * reorder around the date they qualify — and in several languages the qualifier\n * does not follow the date at all. One argument carrying the variant is what\n * keeps the whole cell name one sentence the host writes.\n */\nexport type RangeCellPart = \"start\" | \"end\" | \"both\" | \"within\";\n\n/**\n * The accessible name of one day in a range calendar, shared by both range\n * controls because they say it identically and from identical facts — a day\n * and its part in the span. `DateTimeRangePicker`'s cells carry no time: the\n * cell *is* a day, and choosing it moves only the day.\n *\n * The two controls' other strings are not shared, because they differ in words\n * and in facts. This one does neither, and a translator writing it twice would\n * be writing it twice for no reason.\n */\nexport interface RangeCellLabels {\n  /**\n   * One calendar cell's accessible name, which replaces the one Reka writes\n   * rather than adding to it: a cell's part in the range has to arrive *with*\n   * the date, and an element has no second slot for a name.\n   *\n   * `part` is `undefined` for a day with no part in the range at all.\n   */\n  readonly cell: LabelOf<{\n    locale: string;\n    date: DateValue;\n    part: RangeCellPart | undefined;\n  }>;\n}\n\n/**\n * Loom's English for a range calendar's cells. The three fills that carry the\n * first day, the last and the ones between are three shades of one colour,\n * which survives neither a colour deficiency nor forced-colors mode — naming\n * the part is what tells them apart, and it is what makes a one-day span say so\n * once rather than announce itself twice as two different things.\n */\nexport const RANGE_CELL_LABELS: RangeCellLabels = {\n  cell: ({ locale, date, part }) => {\n    const full = formatFullDay(locale, date);\n    if (part === \"both\") return `${full}, the whole range, first and last day`;\n    if (part === \"start\") return `${full}, first day of the range`;\n    if (part === \"end\") return `${full}, last day of the range`;\n    return part === \"within\" ? `${full}, within the range` : full;\n  },\n};\n\n// One formatter per locale, kept, because a range calendar's cell label runs\n// forty-two to eighty-four times per render and `Intl.DateTimeFormat`'s\n// constructor is the expensive half of it. The map is bounded by the number of\n// locales an application actually renders, which is one in nearly every case.\nconst dayFormatters = new Map<string, Intl.DateTimeFormat>();\n\n// Same pattern, for the filled month segment's `aria-valuetext`. The default\n// `filledMonth` label calls this on every render, so caching the formatter\n// avoids the `Intl.DateTimeFormat` constructor cost each time.\nconst monthFormatters = new Map<string, Intl.DateTimeFormat>();\n\n/**\n * A month name in the control's locale, for use in `aria-valuetext`.\n *\n * Exported so a host building a partial vocabulary can call it from their own\n * `filledMonth` override rather than formatting from scratch — the same reason\n * `formatFullDay` is exported.\n */\nexport function monthName(locale: string, month: number): string {\n  let formatter = monthFormatters.get(locale);\n  if (!formatter) {\n    formatter = new Intl.DateTimeFormat(locale, { month: \"long\" });\n    monthFormatters.set(locale, formatter);\n  }\n  // `Date` months are 0-indexed; Loom months are 1-indexed (as in `DateValue.month`).\n  return formatter.format(new Date(2026, month - 1, 1));\n}\n\n/**\n * A whole day written out — weekday, day, month and year — in the control's\n * locale, which is the half of a range cell's name that is not a qualifier.\n *\n * Exported because both range controls' English defaults need it and neither\n * should own it; a host replacing those defaults formats with whatever their\n * own application already uses and never calls this.\n */\nexport function formatFullDay(locale: string, date: DateValue): string {\n  let formatter = dayFormatters.get(locale);\n  if (!formatter) {\n    formatter = new Intl.DateTimeFormat(locale, {\n      weekday: \"long\",\n      day: \"numeric\",\n      month: \"long\",\n      year: \"numeric\",\n    });\n    dayFormatters.set(locale, formatter);\n  }\n  return formatter.format(date.toDate(getLocalTimeZone()));\n}\n"],"mappings":";;;;;;;AAsGA,IAAa,sBAAyC;CACpD,OAAO;CACP,KAAK;CACL,MAAM;CACN,KAAK;CAKL,OAAO;CAKP,cAAc,EAAE,OAAO,aAAa;EAClC,MAAM,OAAO,UAAU,QAAQ,KAAK;EACpC,OAAO,GAAG,OAAO,KAAK,EAAE,KAAK;CAC/B;AACF;;AAwCA,IAAa,sBAAyC;CACpD,MAAM;CACN,QAAQ;CACR,QAAQ;CACR,WAAW;CACX,OAAO;CAIP,kBAAkB,EAAE,gBAAgB;AACtC;AAeA,IAAM,qCAAqB,IAAI,IAAqB;CAAC;CAAS;CAAO;CAAQ;AAAK,CAAC;AACnF,IAAM,qCAAqB,IAAI,IAAqB;CAAC;CAAQ;CAAU;CAAU;AAAW,CAAC;;;;;;;;AAS7F,IAAM,0CAA0B,IAAI,IAAY;CAC9C;CACA;CACA;CACA;CACA;CACA;AACF,CAAC;;;;;;;;;;;;;;;;;;;;AAqBD,SAAgB,sBACd,MACA,OACA,OAC+B;CAC/B,OAAO,wBAAwB,IAAI,IAAI,KAAK,CAAC,KAAK,KAAK,KAAK,IAAI,EAAE,kBAAkB,MAAM,IAAI,CAAC;AACjG;;;;;;;;;;;;AAaA,SAAgB,kBAAkB,MAAuC;CACvE,OAAO,mBAAmB,IAAI,IAAuB;AACvD;;AAGA,SAAgB,kBAAkB,MAAuC;CACvE,OAAO,mBAAmB,IAAI,IAAuB;AACvD;;AA6BA,IAAa,wBAA6C;CACxD,UAAU;CACV,cAAc;CACd,eAAe;CACf,WAAW;AACb;;;;;;;;AA6CA,IAAa,oBAAqC,EAChD,OAAO,EAAE,QAAQ,MAAM,WAAW;CAChC,MAAM,OAAO,cAAc,QAAQ,IAAI;CACvC,IAAI,SAAS,QAAQ,OAAO,GAAG,KAAK;CACpC,IAAI,SAAS,SAAS,OAAO,GAAG,KAAK;CACrC,IAAI,SAAS,OAAO,OAAO,GAAG,KAAK;CACnC,OAAO,SAAS,WAAW,GAAG,KAAK,sBAAsB;AAC3D,EACF;AAMA,IAAM,gCAAgB,IAAI,IAAiC;AAK3D,IAAM,kCAAkB,IAAI,IAAiC;;;;;;;;AAS7D,SAAgB,UAAU,QAAgB,OAAuB;CAC/D,IAAI,YAAY,gBAAgB,IAAI,MAAM;CAC1C,IAAI,CAAC,WAAW;EACd,YAAY,IAAI,KAAK,eAAe,QAAQ,EAAE,OAAO,OAAO,CAAC;EAC7D,gBAAgB,IAAI,QAAQ,SAAS;CACvC;CAEA,OAAO,UAAU,OAAO,IAAI,KAAK,MAAM,QAAQ,GAAG,CAAC,CAAC;AACtD;;;;;;;;;AAUA,SAAgB,cAAc,QAAgB,MAAyB;CACrE,IAAI,YAAY,cAAc,IAAI,MAAM;CACxC,IAAI,CAAC,WAAW;EACd,YAAY,IAAI,KAAK,eAAe,QAAQ;GAC1C,SAAS;GACT,KAAK;GACL,OAAO;GACP,MAAM;EACR,CAAC;EACD,cAAc,IAAI,QAAQ,SAAS;CACrC;CACA,OAAO,UAAU,OAAO,KAAK,OAAO,0CAAiB,CAAC,CAAC;AACzD"}

package/dist/lib/field-context.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"field-context.d.ts","sourceRoot":"","sources":["../../src/lib/field-context.ts"],"names":[],"mappings":"AAAA,OAAO,EAQL,KAAK,WAAW,EAEjB,MAAM,KAAK,CAAC;AAGb;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,WAAW,YAAY;IAC3B,kFAAkF;IAClF,QAAQ,CAAC,SAAS,EAAE,WAAW,CAAC,MAAM,GAAG,SAAS,CAAC,CAAC;IACpD,gGAAgG;IAChG,QAAQ,CAAC,UAAU,EAAE,WAAW,CAAC,MAAM,GAAG,SAAS,CAAC,CAAC;IACrD,sFAAsF;IACtF,QAAQ,CAAC,WAAW,EAAE,WAAW,CAAC,MAAM,GAAG,SAAS,CAAC,CAAC;IACtD,qDAAqD;IACrD,QAAQ,CAAC,IAAI,EAAE,WAAW,CAAC,MAAM,GAAG,SAAS,CAAC,CAAC;IAC/C,4EAA4E;IAC5E,QAAQ,CAAC,QAAQ,EAAE,WAAW,CAAC,OAAO,GAAG,SAAS,CAAC,CAAC;IACpD,oGAAoG;IACpG,QAAQ,CAAC,OAAO,EAAE,WAAW,CAAC,OAAO,GAAG,SAAS,CAAC,CAAC;IACnD,sDAAsD;IACtD,QAAQ,CAAC,QAAQ,EAAE,WAAW,CAAC,OAAO,GAAG,SAAS,CAAC,CAAC;IACpD,+DAA+D;IAC/D,QAAQ,CAAC,QAAQ,EAAE,WAAW,CAAC,OAAO,GAAG,SAAS,CAAC,CAAC;IACpD;;;;;;;;;;;;;OAaG;IACH,cAAc,IAAI,WAAW,CAAC,OAAO,CAAC,CAAC;CACxC;AAED;;;;;GAKG;AACH,MAAM,WAAW,kBAAkB;IACjC,SAAS,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;IACpC,UAAU,CAAC,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;IACtC,WAAW,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;IACtC,IAAI,EAAE,MAAM,MAAM,GAAG,SAAS,CAAC;IAC/B,QAAQ,EAAE,MAAM,OAAO,GAAG,SAAS,CAAC;IACpC,OAAO,EAAE,MAAM,OAAO,GAAG,SAAS,CAAC;IACnC,QAAQ,EAAE,MAAM,OAAO,GAAG,SAAS,CAAC;IACpC,QAAQ,EAAE,MAAM,OAAO,GAAG,SAAS,CAAC;CACrC;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,iBAAiB;IAChC,gGAAgG;IAChG,QAAQ,CAAC,EAAE,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IACjC,oEAAoE;IACpE,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAC1C,sHAAsH;IACtH,QAAQ,CAAC,cAAc,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAC7C,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IACnC,QAAQ,CAAC,QAAQ,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;IACxC,QAAQ,CAAC,OAAO,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;IACvC,QAAQ,CAAC,QAAQ,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;IACxC,QAAQ,CAAC,QAAQ,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;CACzC;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,EAAE,CAAC,EAAE,MAAM,CAAC;IACrB,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAIrC,QAAQ,CAAC,eAAe,CAAC,EAAE,MAAM,CAAC;IAClC,QAAQ,CAAC,cAAc,CAAC,EAAE,MAAM,CAAC;CAClC;AAED;;;;;;;;;;GAUG;AACH,MAAM,WAAW,YAAY;IAC3B,6FAA6F;IAC7F,QAAQ,CAAC,KAAK,EAAE,iBAAiB,CAAC;IAClC,QAAQ,CAAC,EAAE,EAAE,MAAM,GAAG,SAAS,CAAC;IAChC,QAAQ,CAAC,UAAU,EAAE,MAAM,GAAG,SAAS,CAAC;IACxC,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,CAAC;IAClC,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC;IAC3B,QAAQ,CAAC,OAAO,EAAE,OAAO,CAAC;IAC1B,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC;IAC3B,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAC;CAC5B;AASD;;;;;;;;;GASG;AACH,wBAAgB,oBAAoB,IAAI,YAAY,GAAG,SAAS,CAE/D;AAED,uEAAuE;AACvE,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,kBAAkB,GAAG,IAAI,CAwBpE;AAED;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,iBAAiB,GAAG,YAAY,CAyD1E"}

package/dist/lib/field-context.js

@@ -1,106 +0,0 @@
-import { optional } from "./props.js";
-import { computed, inject, onScopeDispose, provide, reactive, ref } from "vue";
-//#region src/lib/field-context.ts
-/**
-* A `Symbol`, and not exported from `src/index.ts`: a consumer pinned to the
-* key is pinned to a shape that moves whenever a wrapper does. `useFieldControl`
-* is the supported way in.
-*/
-var FIELD_CONTEXT = Symbol("loom.field");
-/**
-* The wrapper above this one, for a wrapper that composes over another.
-*
-* Only Field needs it, and only for `readonly`: Vue resolves `inject` to the
-* nearest provider **wholesale**, not per key, so a Field shadows the Fieldset
-* above it entirely. Any key both wrappers answer has to be merged by hand, and
-* reading the outer context here rather than merging inside
-* `provideFieldContext` keeps that decision visible in Field.vue, where the
-* reason for it lives.
-*/
-function useOuterFieldContext() {
-	return inject(FIELD_CONTEXT, void 0);
-}
-/** Called by a wrapper — Field and Fieldset — from its own `setup`. */
-function provideFieldContext(source) {
-	const claims = ref([]);
-	provide(FIELD_CONTEXT, {
-		controlId: computed(source.controlId),
-		labelledBy: computed(source.labelledBy ?? (() => void 0)),
-		describedBy: computed(source.describedBy),
-		name: computed(source.name),
-		required: computed(source.required),
-		invalid: computed(source.invalid),
-		disabled: computed(source.disabled),
-		readonly: computed(source.readonly),
-		claimControlId() {
-			const token = Symbol("loom.field.control");
-			claims.value = [...claims.value, token];
-			onScopeDispose(() => {
-				claims.value = claims.value.filter((held) => held !== token);
-			});
-			return computed(() => claims.value[0] === token);
-		}
-	});
-}
-/**
-* Opt a control into the wrapper around it. One call, one spread — see
-* `TextField.vue`, which is the worked example the rest of the family copies.
-*
-* **The rule is `own ?? wrapper ?? false`.** `??` and not `||`, so an explicit
-* `false` on the control beats a `true` from the wrapper: one control inside a
-* row that is showing an error can declare itself individually fine, and one
-* inside a clean row can declare itself individually invalid.
-*
-* That rule is worth nothing unless "unset" and "set to `false`" are still
-* different values by the time they arrive here, and by default they are not:
-* Vue resolves an absent `Boolean` prop with no declared default to `false`, so
-* `props.invalid ?? field` would short-circuit forever and the context would be
-* inert while looking perfectly wired. **Every participating prop must be
-* declared `boolean | undefined` with an explicit `undefined` default** — the
-* `| undefined` is what `exactOptionalPropertyTypes` needs to let `withDefaults`
-* take that default at all, and the default is what beats the Boolean cast.
-*
-* With no wrapper above, every chain falls through to the control's own props
-* and the `?? false` at the end is the same `false` the control's `withDefaults`
-* used to supply. Nothing about a control standing alone changes.
-*
-* The argument is a **getter**, not a props object, for the reason
-* `./attrs.ts` takes `useAttrs()` rather than a snapshot: a control feeds this a
-* mix of props and fallthrough attrs and both have to stay live.
-*/
-function useFieldControl(own) {
-	const field = inject(FIELD_CONTEXT, void 0);
-	const holdsControlId = field?.claimControlId();
-	const id = computed(() => own().id ?? (holdsControlId?.value === true ? field?.controlId.value : void 0));
-	const name = computed(() => own().name ?? field?.name.value);
-	const labelledBy = computed(() => own().ariaLabelledby ?? field?.labelledBy.value);
-	const describedBy = computed(() => {
-		const ids = [own().describedBy, field?.describedBy.value].filter((candidate) => candidate !== void 0 && candidate.length > 0);
-		return ids.length > 0 ? ids.join(" ") : void 0;
-	});
-	const required = computed(() => own().required ?? field?.required.value ?? false);
-	const invalid = computed(() => own().invalid ?? field?.invalid.value ?? false);
-	const disabled = computed(() => own().disabled ?? field?.disabled.value ?? false);
-	const readonly = computed(() => own().readonly ?? field?.readonly.value ?? false);
-	const attrs = computed(() => optional({
-		id: id.value,
-		name: name.value,
-		"aria-describedby": describedBy.value,
-		"aria-required": required.value ? "true" : void 0,
-		"aria-invalid": invalid.value ? "true" : void 0
-	}));
-	return reactive({
-		attrs,
-		id,
-		labelledBy,
-		name,
-		disabled,
-		invalid,
-		readonly,
-		required
-	});
-}
-//#endregion
-export { provideFieldContext, useFieldControl, useOuterFieldContext };
-
-//# sourceMappingURL=field-context.js.map

package/dist/lib/field-context.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"field-context.js","names":[],"sources":["../../src/lib/field-context.ts"],"sourcesContent":["import {\n  computed,\n  inject,\n  onScopeDispose,\n  provide,\n  reactive,\n  ref,\n  watchEffect,\n  type ComputedRef,\n  type InjectionKey,\n} from \"vue\";\nimport { optional } from \"./props\";\n\n/**\n * What a form-row wrapper (Field, Fieldset) knows about the control inside it.\n *\n * A wrapper renders a `<label for>` and a hint-or-error line, and it is the\n * only thing in the tree that knows the id it pointed that label at, the id of\n * the message, and whether the row is mandatory or in error. None of that can\n * reach a slotted control through props — the wrapper never rendered it — so\n * before this existed the caller copied three attributes by hand at every call\n * site, and forgetting one was a silent accessibility defect.\n *\n * Every member is a `ComputedRef` rather than a value. A row's `error` arrives\n * and clears while the control stays mounted, so the context has to move with\n * it; and a per-key ref is what lets one wrapper inherit a single key from\n * another (Field reads `readonly` off a Fieldset above it) without a hidden\n * whole-object merge.\n *\n * On the booleans, `undefined` means \"this wrapper has no opinion\" and never\n * \"false\". That is the whole precedence story — see `useFieldControl` — and it\n * is the same distinction `./props.ts` exists to explain, arriving from the\n * other side: there, a key is dropped so a child sees an absence; here, an\n * absence is a value a wrapper is allowed to hold.\n */\nexport interface FieldContext {\n  /** The id the primary control adopts, so the wrapper's `<label for>` names it. */\n  readonly controlId: ComputedRef<string | undefined>;\n  /** The id of the wrapper's `<label>`, for group controls to reference via `aria-labelledby`. */\n  readonly labelledBy: ComputedRef<string | undefined>;\n  /** The id of the hint-or-error line, and `undefined` while no message is rendered. */\n  readonly describedBy: ComputedRef<string | undefined>;\n  /** The form field name the control submits under. */\n  readonly name: ComputedRef<string | undefined>;\n  /** Whether the wrapper marks the row mandatory. Becomes `aria-required`. */\n  readonly required: ComputedRef<boolean | undefined>;\n  /** Whether the wrapper is showing an error, which is the same fact as the control being invalid. */\n  readonly invalid: ComputedRef<boolean | undefined>;\n  /** Whether the wrapper disables what is inside it. */\n  readonly disabled: ComputedRef<boolean | undefined>;\n  /** Whether the wrapper renders what is inside it read-only. */\n  readonly readonly: ComputedRef<boolean | undefined>;\n  /**\n   * Claims the row's single control id, and reports whether this control won it.\n   *\n   * `<Field><TextField /><TextField /></Field>` is a shape somebody will write,\n   * and without a claim both inputs adopt the same generated id — a duplicate\n   * id, and a `<label for>` that resolves to whichever the browser reaches\n   * first. The `axe` gate cannot be the backstop: `duplicate-id-active` is\n   * tagged `wcag2a-obsolete`/`deprecated` in axe-core, not `wcag2a`, so it does\n   * not match `WCAG_TAGS` and `e2e/accessibility.e2e.ts` never runs it.\n   *\n   * Reactive rather than a plain boolean because the claim can move: a `v-if`\n   * swapping the first control for the second must promote the second, or the\n   * label points at an id no longer in the document.\n   */\n  claimControlId(): ComputedRef<boolean>;\n}\n\n/**\n * What a wrapper hands `provideFieldContext`, as getters rather than values —\n * the wrapper writes plain expressions over its own props and this file does\n * the wrapping, so a wrapper never has to remember which of its answers are\n * derived.\n */\nexport interface FieldContextSource {\n  controlId: () => string | undefined;\n  labelledBy?: () => string | undefined;\n  describedBy: () => string | undefined;\n  name: () => string | undefined;\n  required: () => boolean | undefined;\n  invalid: () => boolean | undefined;\n  disabled: () => boolean | undefined;\n  readonly: () => boolean | undefined;\n}\n\n/**\n * The control's own side of the contract: what this control was told directly,\n * with `undefined` for everything the caller left unset.\n *\n * Each key is `?: T | undefined` rather than `?: T`. Under\n * `exactOptionalPropertyTypes` that is the form that accepts both an omitted\n * key and an explicit `undefined` — and an explicit `undefined` is exactly what\n * a control passes when its own prop is unset.\n */\nexport interface FieldControlProps {\n  /** The caller's `id`, which reaches a bare control as a fallthrough attr rather than a prop. */\n  readonly id?: string | undefined;\n  /** The caller's `aria-describedby`, likewise a fallthrough attr. */\n  readonly describedBy?: string | undefined;\n  /** The caller's `aria-labelledby`, for group controls that name themselves rather than being named by `label for`. */\n  readonly ariaLabelledby?: string | undefined;\n  readonly name?: string | undefined;\n  readonly required?: boolean | undefined;\n  readonly invalid?: boolean | undefined;\n  readonly disabled?: boolean | undefined;\n  readonly readonly?: boolean | undefined;\n}\n\n/**\n * The resolved attributes, ready to spread onto whichever node carries the\n * control's ARIA.\n *\n * A key whose value resolved to `undefined` is **absent**, not present-and-\n * undefined — `optional()` drops it. That is what makes the spread purely\n * additive: `v-bind=\"{ ...rest, ...field.attrs }\"` can never blank out an\n * attribute the caller passed through fallthrough, so a control renders exactly\n * what it renders today whenever there is no wrapper above it.\n *\n * `aria-required` and `aria-invalid` are omitted rather than set to `\"false\"`.\n * Both are legal and both say nothing, and the absent attribute already means\n * the same thing — the house `x || undefined` idiom, moved one layer in.\n */\nexport interface FieldControlAttrs {\n  readonly id?: string;\n  readonly name?: string;\n  readonly \"aria-describedby\"?: string;\n  // Narrowed to the literal rather than `string`: Vue types `aria-invalid` on a\n  // native element as `Booleanish | \"grammar\" | \"spelling\"`, so a widened\n  // `string` here fails to spread onto the very `<input>` this exists for.\n  readonly \"aria-required\"?: \"true\";\n  readonly \"aria-invalid\"?: \"true\";\n}\n\n/**\n * What `useFieldControl` resolved, after the control's own props won.\n *\n * Returned `reactive` rather than as a bag of refs, which is the one place in\n * `src/lib/` that does so. A template unwraps only a *top-level* ref, and a\n * control needs four of these at once under names — `disabled`, `invalid`,\n * `readonly`, `required` — that each shadow a prop of the same name. `reactive`\n * gives `field.invalid` in both the script and the template, and the shadowing\n * question never arises. Destructuring it does lose reactivity; read through\n * `field.` and there is nothing to get wrong.\n */\nexport interface FieldControl {\n  /** Spread onto the node that carries the control's ARIA, **after** the fallthrough attrs. */\n  readonly attrs: FieldControlAttrs;\n  readonly id: string | undefined;\n  readonly labelledBy: string | undefined;\n  readonly name: string | undefined;\n  readonly disabled: boolean;\n  readonly invalid: boolean;\n  readonly readonly: boolean;\n  readonly required: boolean;\n}\n\n/**\n * A `Symbol`, and not exported from `src/index.ts`: a consumer pinned to the\n * key is pinned to a shape that moves whenever a wrapper does. `useFieldControl`\n * is the supported way in.\n */\nconst FIELD_CONTEXT: InjectionKey<FieldContext> = Symbol(\"loom.field\");\n\n/**\n * The wrapper above this one, for a wrapper that composes over another.\n *\n * Only Field needs it, and only for `readonly`: Vue resolves `inject` to the\n * nearest provider **wholesale**, not per key, so a Field shadows the Fieldset\n * above it entirely. Any key both wrappers answer has to be merged by hand, and\n * reading the outer context here rather than merging inside\n * `provideFieldContext` keeps that decision visible in Field.vue, where the\n * reason for it lives.\n */\nexport function useOuterFieldContext(): FieldContext | undefined {\n  return inject(FIELD_CONTEXT, undefined);\n}\n\n/** Called by a wrapper — Field and Fieldset — from its own `setup`. */\nexport function provideFieldContext(source: FieldContextSource): void {\n  const claims = ref<symbol[]>([]);\n\n  provide(FIELD_CONTEXT, {\n    controlId: computed(source.controlId),\n    labelledBy: computed(source.labelledBy ?? (() => undefined)),\n    describedBy: computed(source.describedBy),\n    name: computed(source.name),\n    required: computed(source.required),\n    invalid: computed(source.invalid),\n    disabled: computed(source.disabled),\n    readonly: computed(source.readonly),\n    claimControlId() {\n      const token = Symbol(\"loom.field.control\");\n      claims.value = [...claims.value, token];\n      // The claiming scope is the control's, not the wrapper's, so this fires\n      // when that one control unmounts and the next in document order is\n      // promoted.\n      onScopeDispose(() => {\n        claims.value = claims.value.filter((held) => held !== token);\n      });\n      return computed(() => claims.value[0] === token);\n    },\n  });\n}\n\n/**\n * Opt a control into the wrapper around it. One call, one spread — see\n * `TextField.vue`, which is the worked example the rest of the family copies.\n *\n * **The rule is `own ?? wrapper ?? false`.** `??` and not `||`, so an explicit\n * `false` on the control beats a `true` from the wrapper: one control inside a\n * row that is showing an error can declare itself individually fine, and one\n * inside a clean row can declare itself individually invalid.\n *\n * That rule is worth nothing unless \"unset\" and \"set to `false`\" are still\n * different values by the time they arrive here, and by default they are not:\n * Vue resolves an absent `Boolean` prop with no declared default to `false`, so\n * `props.invalid ?? field` would short-circuit forever and the context would be\n * inert while looking perfectly wired. **Every participating prop must be\n * declared `boolean | undefined` with an explicit `undefined` default** — the\n * `| undefined` is what `exactOptionalPropertyTypes` needs to let `withDefaults`\n * take that default at all, and the default is what beats the Boolean cast.\n *\n * With no wrapper above, every chain falls through to the control's own props\n * and the `?? false` at the end is the same `false` the control's `withDefaults`\n * used to supply. Nothing about a control standing alone changes.\n *\n * The argument is a **getter**, not a props object, for the reason\n * `./attrs.ts` takes `useAttrs()` rather than a snapshot: a control feeds this a\n * mix of props and fallthrough attrs and both have to stay live.\n */\nexport function useFieldControl(own: () => FieldControlProps): FieldControl {\n  const field = inject(FIELD_CONTEXT, undefined);\n  const holdsControlId = field?.claimControlId();\n\n  const id = computed(\n    () => own().id ?? (holdsControlId?.value === true ? field?.controlId.value : undefined),\n  );\n  const name = computed(() => own().name ?? field?.name.value);\n  const labelledBy = computed(() => own().ariaLabelledby ?? field?.labelledBy.value);\n\n  // The one attribute whose rule is merge rather than replace, because\n  // `aria-describedby` is a token list: the row's message is additional to\n  // whatever else the caller pointed at, not an alternative to it. Replacing\n  // would silently drop the row's hint the moment a caller described their\n  // control for some other reason — which is the defect this file exists to\n  // remove, reintroduced from the other end. The control's own id reads first:\n  // a control that has something to say about itself is saying the more\n  // specific thing, and a screen reader reads the list in order.\n  const describedBy = computed(() => {\n    const ids = [own().describedBy, field?.describedBy.value].filter(\n      (candidate): candidate is string => candidate !== undefined && candidate.length > 0,\n    );\n    return ids.length > 0 ? ids.join(\" \") : undefined;\n  });\n\n  const required = computed(() => own().required ?? field?.required.value ?? false);\n  const invalid = computed(() => own().invalid ?? field?.invalid.value ?? false);\n  const disabled = computed(() => own().disabled ?? field?.disabled.value ?? false);\n  const readonly = computed(() => own().readonly ?? field?.readonly.value ?? false);\n\n  // A development-mode safety net for the one context key a control can\n  // deliberately decline. When a wrapper sets `readonly` but the control did\n  // not pass that key in its `FieldControlProps`, the wrapper's instruction is\n  // silently dropped — and without this warning the consumer has no signal\n  // that it was. The `\"readonly\" in own()` check distinguishes \"I defer to the\n  // wrapper\" (key present, value `undefined`) from \"I don't participate\" (key\n  // absent), which is the same distinction `exactOptionalPropertyTypes` makes\n  // at the type level.\n  if (import.meta.env.DEV && field) {\n    watchEffect(() => {\n      if (field.readonly.value && !(\"readonly\" in own())) {\n        console.warn(\"[Loom] readonly was set on the Field, but this control does not claim it.\");\n      }\n    });\n  }\n\n  const attrs = computed<FieldControlAttrs>(() =>\n    optional({\n      id: id.value,\n      name: name.value,\n      \"aria-describedby\": describedBy.value,\n      \"aria-required\": required.value ? (\"true\" as const) : undefined,\n      \"aria-invalid\": invalid.value ? (\"true\" as const) : undefined,\n    }),\n  );\n\n  return reactive({ attrs, id, labelledBy, name, disabled, invalid, readonly, required });\n}\n"],"mappings":";;;;;;;;AAkKA,IAAM,gBAA4C,OAAO,YAAY;;;;;;;;;;;AAYrE,SAAgB,uBAAiD;CAC/D,OAAO,OAAO,eAAe,KAAA,CAAS;AACxC;;AAGA,SAAgB,oBAAoB,QAAkC;CACpE,MAAM,SAAS,IAAc,CAAC,CAAC;CAE/B,QAAQ,eAAe;EACrB,WAAW,SAAS,OAAO,SAAS;EACpC,YAAY,SAAS,OAAO,qBAAqB,KAAA,EAAU;EAC3D,aAAa,SAAS,OAAO,WAAW;EACxC,MAAM,SAAS,OAAO,IAAI;EAC1B,UAAU,SAAS,OAAO,QAAQ;EAClC,SAAS,SAAS,OAAO,OAAO;EAChC,UAAU,SAAS,OAAO,QAAQ;EAClC,UAAU,SAAS,OAAO,QAAQ;EAClC,iBAAiB;GACf,MAAM,QAAQ,OAAO,oBAAoB;GACzC,OAAO,QAAQ,CAAC,GAAG,OAAO,OAAO,KAAK;GAItC,qBAAqB;IACnB,OAAO,QAAQ,OAAO,MAAM,QAAQ,SAAS,SAAS,KAAK;GAC7D,CAAC;GACD,OAAO,eAAe,OAAO,MAAM,OAAO,KAAK;EACjD;CACF,CAAC;AACH;;;;;;;;;;;;;;;;;;;;;;;;;;;AA4BA,SAAgB,gBAAgB,KAA4C;CAC1E,MAAM,QAAQ,OAAO,eAAe,KAAA,CAAS;CAC7C,MAAM,iBAAiB,OAAO,eAAe;CAE7C,MAAM,KAAK,eACH,IAAI,CAAC,CAAC,OAAO,gBAAgB,UAAU,OAAO,OAAO,UAAU,QAAQ,KAAA,EAC/E;CACA,MAAM,OAAO,eAAe,IAAI,CAAC,CAAC,QAAQ,OAAO,KAAK,KAAK;CAC3D,MAAM,aAAa,eAAe,IAAI,CAAC,CAAC,kBAAkB,OAAO,WAAW,KAAK;CAUjF,MAAM,cAAc,eAAe;EACjC,MAAM,MAAM,CAAC,IAAI,CAAC,CAAC,aAAa,OAAO,YAAY,KAAK,CAAC,CAAC,QACvD,cAAmC,cAAc,KAAA,KAAa,UAAU,SAAS,CACpF;EACA,OAAO,IAAI,SAAS,IAAI,IAAI,KAAK,GAAG,IAAI,KAAA;CAC1C,CAAC;CAED,MAAM,WAAW,eAAe,IAAI,CAAC,CAAC,YAAY,OAAO,SAAS,SAAS,KAAK;CAChF,MAAM,UAAU,eAAe,IAAI,CAAC,CAAC,WAAW,OAAO,QAAQ,SAAS,KAAK;CAC7E,MAAM,WAAW,eAAe,IAAI,CAAC,CAAC,YAAY,OAAO,SAAS,SAAS,KAAK;CAChF,MAAM,WAAW,eAAe,IAAI,CAAC,CAAC,YAAY,OAAO,SAAS,SAAS,KAAK;CAkBhF,MAAM,QAAQ,eACZ,SAAS;EACP,IAAI,GAAG;EACP,MAAM,KAAK;EACX,oBAAoB,YAAY;EAChC,iBAAiB,SAAS,QAAS,SAAmB,KAAA;EACtD,gBAAgB,QAAQ,QAAS,SAAmB,KAAA;CACtD,CAAC,CACH;CAEA,OAAO,SAAS;EAAE;EAAO;EAAI;EAAY;EAAM;EAAU;EAAS;EAAU;CAAS,CAAC;AACxF"}

package/dist/lib/icon-defaults.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"icon-defaults.d.ts","sourceRoot":"","sources":["../../src/lib/icon-defaults.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,qBAAqB,IAAI,IAAI,CAE5C"}

package/dist/lib/icon-defaults.js

@@ -1,32 +0,0 @@
-import { setLucideProps } from "@lucide/vue";
-//#region src/lib/icon-defaults.ts
-/**
-* Apply the Loom icon defaults once at a host's root: size 16, stroke 1.5 —
-* hairline-first, matching the 1px border language. Every `@lucide/vue` icon
-* rendered after this call inherits them, so an individual icon declares
-* `size` or `strokeWidth` only where it deliberately diverges.
-*
-* The one standing divergence: a glyph rendered at 12px or below declares
-* `stroke-width` 2.5 exactly. Stroke lives on the 24 grid and scales with
-* size, so 1.5 at 12px renders 0.75 device pixels against 1.0 at 16px; 2.5
-* restores the optical weight.
-*
-* The numbers live here, not in each host.
-*
-* Call it from the `setup()` of the host's root component — `App.vue`, or the
-* component a documentation theme wraps its layout in. It resolves to Vue's
-* `provide()`, so it needs an active component instance: called from a plain
-* entry module it silently provides nothing, and every icon keeps Lucide's own
-* 24/2 defaults. There is no app-level alternative, because the injection key
-* Lucide provides under is not part of its public surface.
-*/
-function applyLoomIconDefaults() {
-	setLucideProps({
-		size: 16,
-		strokeWidth: 1.5
-	});
-}
-//#endregion
-export { applyLoomIconDefaults };
-
-//# sourceMappingURL=icon-defaults.js.map

package/dist/lib/icon-defaults.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"icon-defaults.js","names":[],"sources":["../../src/lib/icon-defaults.ts"],"sourcesContent":["import { setLucideProps } from \"@lucide/vue\";\n\n/**\n * Apply the Loom icon defaults once at a host's root: size 16, stroke 1.5 —\n * hairline-first, matching the 1px border language. Every `@lucide/vue` icon\n * rendered after this call inherits them, so an individual icon declares\n * `size` or `strokeWidth` only where it deliberately diverges.\n *\n * The one standing divergence: a glyph rendered at 12px or below declares\n * `stroke-width` 2.5 exactly. Stroke lives on the 24 grid and scales with\n * size, so 1.5 at 12px renders 0.75 device pixels against 1.0 at 16px; 2.5\n * restores the optical weight.\n *\n * The numbers live here, not in each host.\n *\n * Call it from the `setup()` of the host's root component — `App.vue`, or the\n * component a documentation theme wraps its layout in. It resolves to Vue's\n * `provide()`, so it needs an active component instance: called from a plain\n * entry module it silently provides nothing, and every icon keeps Lucide's own\n * 24/2 defaults. There is no app-level alternative, because the injection key\n * Lucide provides under is not part of its public surface.\n */\nexport function applyLoomIconDefaults(): void {\n  setLucideProps({ size: 16, strokeWidth: 1.5 });\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;AAsBA,SAAgB,wBAA8B;CAC5C,eAAe;EAAE,MAAM;EAAI,aAAa;CAAI,CAAC;AAC/C"}

package/dist/lib/label-registry.d.ts

@@ -1,75 +0,0 @@
-import type { CalendarPanelLabels, DateSegmentLabels, RangeCellLabels, TimeSegmentLabels } from "./date-labels";
-import type { DateRangeLabels } from "../primitives/DateRangePicker/DateRangePicker.vue";
-import type { DateTimeRangeLabels } from "../primitives/DateTimeRangePicker/DateTimeRangePicker.vue";
-import type { ComboboxLabels } from "../primitives/Combobox/Combobox.vue";
-import type { EditableLabels } from "../primitives/Editable/Editable.vue";
-import type { FileUploadLabels } from "../primitives/FileUpload/FileUpload.vue";
-import type { NumberFieldLabels } from "../primitives/NumberField/NumberField.vue";
-import type { OtpInputLabels } from "../primitives/OtpInput/OtpInput.vue";
-import type { PaginationLabels } from "../primitives/Pagination/Pagination.vue";
-import type { RatingLabels } from "../primitives/Rating/Rating.vue";
-import type { WindowControlsLabels } from "../primitives/WindowControls/WindowControls.vue";
-import type { AvatarGroupLabels } from "../primitives/AvatarGroup/AvatarGroup.vue";
-import type { ColorPickerLabels } from "../primitives/ColorPicker/ColorPicker.vue";
-import type { IndicatorLabels } from "../primitives/Indicator/Indicator.vue";
-import type { ProgressLabels } from "../primitives/Progress/Progress.vue";
-import type { RadialProgressLabels } from "../primitives/RadialProgress/RadialProgress.vue";
-import type { AlertDialogLabels } from "../primitives/AlertDialog/AlertDialog.vue";
-import type { DialogLabels } from "../primitives/Dialog/Dialog.vue";
-import type { DrawerLabels } from "../primitives/Drawer/Drawer.vue";
-import type { StepperLabels } from "../primitives/Stepper/Stepper.vue";
-import type { ToastLabels } from "../primitives/Toast/Toast.vue";
-import type { TagsInputLabels } from "../primitives/TagsInput/TagsInput.vue";
-import type { TextFieldLabels } from "../primitives/TextField/TextField.vue";
-import type { TextareaLabels } from "../primitives/Textarea/Textarea.vue";
-/**
- * Every slot a host can localise, and nothing else. One line per component that
- * speaks; the keys themselves live with the component that says them.
- *
- * This file exists so that both halves of the seam can be true at once. The
- * *keys* belong beside the component — `PaginationLabels` is declared in
- * `Pagination.vue`, where its doc comments sit next to the markup that renders
- * them and where a component's whole contract can be read in one file. The
- * *namespace* has to be central, or `provideLoomLabels({ pagination: … })` could
- * not check a misspelled slot and a consumer would have no single place to see
- * what the library can be asked to say.
- *
- * Every import here is `import type`, so this module emits nothing and the
- * apparent cycle — component imports `useLabels`, `useLabels` imports this,
- * this imports the component — exists only in the type graph, where TypeScript
- * resolves it lazily. A value import in this file would turn the whole library
- * into one chunk and cost every consumer the components they did not use.
- *
- * Adding a component to the sweep is one line. Adding it in the wrong shape is
- * a compile error at that component's own `useLabels` call, not here.
- */
-export interface LoomLabels {
-    readonly pagination: PaginationLabels;
-    readonly windowControls: WindowControlsLabels;
-    readonly dateSegments: DateSegmentLabels;
-    readonly timeSegments: TimeSegmentLabels;
-    readonly calendarPanel: CalendarPanelLabels;
-    readonly rangeCell: RangeCellLabels;
-    readonly dateRange: DateRangeLabels;
-    readonly dateTimeRange: DateTimeRangeLabels;
-    readonly numberField: NumberFieldLabels;
-    readonly combobox: ComboboxLabels;
-    readonly otpInput: OtpInputLabels;
-    readonly fileUpload: FileUploadLabels;
-    readonly rating: RatingLabels;
-    readonly tagsInput: TagsInputLabels;
-    readonly editable: EditableLabels;
-    readonly textField: TextFieldLabels;
-    readonly textarea: TextareaLabels;
-    readonly dialog: DialogLabels;
-    readonly alertDialog: AlertDialogLabels;
-    readonly drawer: DrawerLabels;
-    readonly stepper: StepperLabels;
-    readonly toast: ToastLabels;
-    readonly indicator: IndicatorLabels;
-    readonly avatarGroup: AvatarGroupLabels;
-    readonly progress: ProgressLabels;
-    readonly radialProgress: RadialProgressLabels;
-    readonly colorPicker: ColorPickerLabels;
-}
-//# sourceMappingURL=label-registry.d.ts.map

package/dist/lib/label-registry.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"label-registry.d.ts","sourceRoot":"","sources":["../../src/lib/label-registry.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EACV,mBAAmB,EACnB,iBAAiB,EACjB,eAAe,EACf,iBAAiB,EAClB,MAAM,eAAe,CAAC;AACvB,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,mDAAmD,CAAC;AACzF,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,2DAA2D,CAAC;AACrG,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qCAAqC,CAAC;AAC1E,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qCAAqC,CAAC;AAC1E,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,yCAAyC,CAAC;AAChF,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,2CAA2C,CAAC;AACnF,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qCAAqC,CAAC;AAC1E,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,yCAAyC,CAAC;AAChF,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iCAAiC,CAAC;AACpE,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,iDAAiD,CAAC;AAC5F,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,2CAA2C,CAAC;AACnF,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,2CAA2C,CAAC;AACnF,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,uCAAuC,CAAC;AAC7E,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qCAAqC,CAAC;AAC1E,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,iDAAiD,CAAC;AAC5F,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,2CAA2C,CAAC;AACnF,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iCAAiC,CAAC;AACpE,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,iCAAiC,CAAC;AACpE,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,mCAAmC,CAAC;AACvE,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,+BAA+B,CAAC;AACjE,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,uCAAuC,CAAC;AAC7E,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,uCAAuC,CAAC;AAC7E,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qCAAqC,CAAC;AAE1E;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,WAAW,UAAU;IACzB,QAAQ,CAAC,UAAU,EAAE,gBAAgB,CAAC;IACtC,QAAQ,CAAC,cAAc,EAAE,oBAAoB,CAAC;IAM9C,QAAQ,CAAC,YAAY,EAAE,iBAAiB,CAAC;IACzC,QAAQ,CAAC,YAAY,EAAE,iBAAiB,CAAC;IACzC,QAAQ,CAAC,aAAa,EAAE,mBAAmB,CAAC;IAC5C,QAAQ,CAAC,SAAS,EAAE,eAAe,CAAC;IACpC,QAAQ,CAAC,SAAS,EAAE,eAAe,CAAC;IACpC,QAAQ,CAAC,aAAa,EAAE,mBAAmB,CAAC;IAI5C,QAAQ,CAAC,WAAW,EAAE,iBAAiB,CAAC;IACxC,QAAQ,CAAC,QAAQ,EAAE,cAAc,CAAC;IAClC,QAAQ,CAAC,QAAQ,EAAE,cAAc,CAAC;IAClC,QAAQ,CAAC,UAAU,EAAE,gBAAgB,CAAC;IACtC,QAAQ,CAAC,MAAM,EAAE,YAAY,CAAC;IAC9B,QAAQ,CAAC,SAAS,EAAE,eAAe,CAAC;IACpC,QAAQ,CAAC,QAAQ,EAAE,cAAc,CAAC;IAClC,QAAQ,CAAC,SAAS,EAAE,eAAe,CAAC;IAKpC,QAAQ,CAAC,QAAQ,EAAE,cAAc,CAAC;IAIlC,QAAQ,CAAC,MAAM,EAAE,YAAY,CAAC;IAC9B,QAAQ,CAAC,WAAW,EAAE,iBAAiB,CAAC;IACxC,QAAQ,CAAC,MAAM,EAAE,YAAY,CAAC;IAC9B,QAAQ,CAAC,OAAO,EAAE,aAAa,CAAC;IAChC,QAAQ,CAAC,KAAK,EAAE,WAAW,CAAC;IAM5B,QAAQ,CAAC,SAAS,EAAE,eAAe,CAAC;IACpC,QAAQ,CAAC,WAAW,EAAE,iBAAiB,CAAC;IAIxC,QAAQ,CAAC,QAAQ,EAAE,cAAc,CAAC;IAClC,QAAQ,CAAC,cAAc,EAAE,oBAAoB,CAAC;IAC9C,QAAQ,CAAC,WAAW,EAAE,iBAAiB,CAAC;CACzC"}

package/dist/lib/labels.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"labels.d.ts","sourceRoot":"","sources":["../../src/lib/labels.ts"],"names":[],"mappings":"AAAA,OAAO,EAA6B,KAAK,WAAW,EAAqB,MAAM,KAAK,CAAC;AAErF,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAEnD;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,MAAM,MAAM,OAAO,CAAC,IAAI,SAAS,MAAM,IAAI,CAAC,IAAI,EAAE,IAAI,KAAK,MAAM,CAAC;AAElE;;;;;;;;;;;;;;;GAeG;AACH,MAAM,MAAM,cAAc,CAAC,CAAC,SAAS,MAAM,IAAI;IAC7C,QAAQ,EAAE,CAAC,IAAI,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,GAAG,SAAS;CAC3C,CAAC;AAEF;;;;;;;;GAQG;AACH,MAAM,MAAM,kBAAkB,GAAG;IAC/B,QAAQ,EAAE,CAAC,IAAI,MAAM,UAAU,CAAC,CAAC,EAAE,cAAc,CAAC,UAAU,CAAC,CAAC,CAAC,CAAC,GAAG,SAAS;CAC7E,CAAC;AA4BF;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,MAAM,kBAAkB,GAAG,IAAI,CAMxE;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,wBAAgB,SAAS,CAAC,CAAC,SAAS,MAAM,UAAU,EAAE,CAAC,SAAS,UAAU,CAAC,CAAC,CAAC,EAC3E,IAAI,EAAE,CAAC,EACP,QAAQ,EAAE,CAAC,EACX,GAAG,CAAC,EAAE,MAAM,cAAc,CAAC,CAAC,CAAC,GAAG,SAAS,GACxC,WAAW,CAAC,UAAU,CAAC,CAAC,CAAC,CAAC,CAa5B"}

package/dist/lib/labels.js

@@ -1,84 +0,0 @@
-import { optional } from "./props.js";
-import { computed, inject, provide } from "vue";
-//#region src/lib/labels.ts
-/**
-* A `Symbol`, and not exported from `src/index.ts`, for the reason
-* `./field-context.ts` gives about its own: a consumer pinned to the key is
-* pinned to a shape that moves. `provideLoomLabels` is the supported way in.
-*/
-var LOOM_LABELS = Symbol("loom.labels");
-function mergeVocabularies(outer, inner) {
-	const merged = { ...outer };
-	const patches = inner;
-	for (const slot of Object.keys(patches)) {
-		const patch = patches[slot];
-		if (patch === void 0) continue;
-		merged[slot] = {
-			...merged[slot] ?? {},
-			...optional(patch)
-		};
-	}
-	return merged;
-}
-/**
-* Declare a host's vocabulary once, from the `setup` of its root component —
-* the same place, and for the same reason, as `applyLoomIconDefaults`. It
-* resolves to Vue's `provide()`, so called from a plain entry module it
-* silently provides nothing and every component keeps its English.
-*
-* A **getter**, not a value, for the reason `./attrs.ts` takes `useAttrs()`
-* rather than a snapshot: the getter runs inside the `computed` that
-* `useLabels` returns, which runs inside the render effect, so a host whose bag
-* reads `t("pager.next")` tracks their locale ref and every Loom component
-* repaints on a language switch with no work here at all. Snapshot the bag
-* instead and the first language renders correctly and every switch after it
-* does nothing — a failure with no error and no warning.
-*
-* **A nested call merges into the bag above it rather than replacing it**, and
-* that is a deliberate divergence from `./field-context.ts`, which documents
-* the opposite and hand-merges the single key that needs it. Vue resolves
-* `inject` wholesale to the nearest provider, so without this a host wrapping
-* one dialog in a second `provideLoomLabels` to change one string would lose
-* every other string in the application back to English. Hand-merging is right
-* for two wrappers and one key; it does not scale to a vocabulary this size at
-* an unknown depth.
-*/
-function provideLoomLabels(source) {
-	const outer = inject(LOOM_LABELS, void 0);
-	provide(LOOM_LABELS, computed(() => outer === void 0 ? source() : mergeVocabularies(outer.value, source())));
-}
-/**
-* Resolve one component's slot: **own prop, then the host's vocabulary, then
-* the component's own English** — key by key, never whole-object.
-*
-* Key by key is the whole point. A host providing `{ pagination: { next: "Sau" } }`
-* keeps English for the other seven rather than rendering a row of unnamed
-* buttons, and an instance overriding its own `nav` does not discard the host's
-* other six. `optional()` is what makes each spread purely additive: it drops
-* the `undefined`-valued keys, so an absent override cannot blank a present
-* default. Same function, same reasoning, as the attribute spread in
-* `./field-context.ts`.
-*
-* The prop beating the provider is not a preference. A page with two paginations
-* that need different names has no other way out, and an application-wide
-* vocabulary that could not be corrected per instance would force a host to
-* choose between localising and naming.
-*
-* `defaults` arrives from the component rather than from a central English
-* bundle, and that is what bounds the cost of the seam: a consumer importing
-* only `Button` ships no label bytes at all, and one importing `Pagination`
-* ships `Pagination`'s. A central `en` object would always ship whole.
-*
-* The result is typed from `defaults` rather than from `LoomLabels[K]`, with
-* the registry entry as a constraint on it. Structurally that is the same
-* check — a bag that does not match its registered slot does not compile — but
-* it keeps the resolved type nameable from the module that declared it.
-*/
-function useLabels(slot, defaults, own) {
-	const provided = inject(LOOM_LABELS, void 0);
-	return computed(() => Object.assign({}, defaults, optional(provided?.value[slot] ?? {}), optional(own?.() ?? {})));
-}
-//#endregion
-export { provideLoomLabels, useLabels };
-
-//# sourceMappingURL=labels.js.map

package/dist/lib/labels.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"labels.js","names":[],"sources":["../../src/lib/labels.ts"],"sourcesContent":["import { computed, inject, provide, type ComputedRef, type InjectionKey } from \"vue\";\nimport { optional } from \"./props\";\nimport type { LoomLabels } from \"./label-registry\";\n\n/**\n * A message the component cannot write on its own, because it depends on a\n * value only the render knows — a page number, a file name, a count.\n *\n * **The argument is one object, and every member is a raw value: a `number`, a\n * `Date`, a `File`. Never a string Loom has already formatted.** That is the\n * entire pluralisation answer, and it is why this library ships no\n * pluralisation engine and takes no i18n dependency. \"3 unread\" has one form in\n * Vietnamese, two in English, three in Russian and six in Arabic, and no\n * placeholder syntax Loom could invent would carry that. Loom hands over the\n * facts and receives a finished string; selecting the plural category, shaping\n * the digits and ordering the sentence all happen in the consumer's own\n * `Intl.PluralRules`, `Intl.NumberFormat`, vue-i18n, or hand-written `if`.\n *\n * Hand over the number and a consumer can reach `Intl.NumberFormat` for Eastern\n * Arabic digits. Hand over `\"3\"` and they cannot: the decision was already made,\n * in English, inside a component that had no business making it.\n *\n * One object rather than positional parameters, for two reasons. A bare\n * `(4, 12)` in a consumer's locale file says nothing about what either number\n * is. And a fact added later is a new key an existing override simply ignores,\n * where a new positional parameter would silently re-order every call site.\n *\n * There is deliberately no third kind. A message is a `string` or it is one of\n * these; a `string | (() => string)` union was considered and rejected, because\n * the reactivity it exists to buy is already bought by `provideLoomLabels`\n * taking a getter — and it would put a `resolve()` call around every binding in\n * every component for the rest of the library's life.\n */\nexport type LabelOf<Args extends object> = (args: Args) => string;\n\n/**\n * What a consumer may pass for one component's bag: any subset of it.\n *\n * **This, not the bag interface itself, is the type a consumer annotates their\n * own object with.** A bag typed `PaginationLabels` must answer every key, so a\n * key added in a later release breaks that consumer's build; a bag typed\n * `LabelOverrides<PaginationLabels>` does not, which is what makes growing the\n * vocabulary a `feat` rather than a `feat!`.\n *\n * `T[K] | undefined` rather than a plain `Partial<T>`, because\n * `exactOptionalPropertyTypes` is on: under it `Partial<T>` rejects an\n * explicitly-`undefined` value, and an explicit `undefined` is exactly what a\n * consumer's own conditional expression produces when its condition is unmet.\n * It has to mean \"no opinion\", never \"blank this out\" — the same distinction\n * `./props.ts` exists to explain, arriving one layer in.\n */\nexport type LabelOverrides<T extends object> = {\n  readonly [K in keyof T]?: T[K] | undefined;\n};\n\n/**\n * A whole vocabulary, as a host supplies it: any subset of any slot.\n *\n * Both levels are partial and both are checked. A misspelled slot and a\n * misspelled key inside a slot are each a compile error — on a fresh object\n * literal, which is the caveat the localisation guide documents and the reason\n * it tells a consumer to write `satisfies LoomLabelOverrides` on a bag they\n * hoist to a module.\n */\nexport type LoomLabelOverrides = {\n  readonly [K in keyof LoomLabels]?: LabelOverrides<LoomLabels[K]> | undefined;\n};\n\n/** The shape both merge steps work in, once the slot's identity has been checked. */\ntype AnyBag = Record<string, unknown>;\n\n/**\n * A `Symbol`, and not exported from `src/index.ts`, for the reason\n * `./field-context.ts` gives about its own: a consumer pinned to the key is\n * pinned to a shape that moves. `provideLoomLabels` is the supported way in.\n */\nconst LOOM_LABELS: InjectionKey<ComputedRef<LoomLabelOverrides>> = Symbol(\"loom.labels\");\n\nfunction mergeVocabularies(\n  outer: LoomLabelOverrides,\n  inner: LoomLabelOverrides,\n): LoomLabelOverrides {\n  const merged = { ...outer } as AnyBag;\n  const patches = inner as AnyBag;\n  for (const slot of Object.keys(patches)) {\n    const patch = patches[slot] as AnyBag | undefined;\n    if (patch === undefined) continue;\n    // Per key inside the slot as well as per slot: a nested provider changing\n    // one string must not blank the rest of that slot back to English.\n    merged[slot] = { ...((merged[slot] ?? {}) as AnyBag), ...optional(patch) };\n  }\n  return merged;\n}\n\n/**\n * Declare a host's vocabulary once, from the `setup` of its root component —\n * the same place, and for the same reason, as `applyLoomIconDefaults`. It\n * resolves to Vue's `provide()`, so called from a plain entry module it\n * silently provides nothing and every component keeps its English.\n *\n * A **getter**, not a value, for the reason `./attrs.ts` takes `useAttrs()`\n * rather than a snapshot: the getter runs inside the `computed` that\n * `useLabels` returns, which runs inside the render effect, so a host whose bag\n * reads `t(\"pager.next\")` tracks their locale ref and every Loom component\n * repaints on a language switch with no work here at all. Snapshot the bag\n * instead and the first language renders correctly and every switch after it\n * does nothing — a failure with no error and no warning.\n *\n * **A nested call merges into the bag above it rather than replacing it**, and\n * that is a deliberate divergence from `./field-context.ts`, which documents\n * the opposite and hand-merges the single key that needs it. Vue resolves\n * `inject` wholesale to the nearest provider, so without this a host wrapping\n * one dialog in a second `provideLoomLabels` to change one string would lose\n * every other string in the application back to English. Hand-merging is right\n * for two wrappers and one key; it does not scale to a vocabulary this size at\n * an unknown depth.\n */\nexport function provideLoomLabels(source: () => LoomLabelOverrides): void {\n  const outer = inject(LOOM_LABELS, undefined);\n  provide(\n    LOOM_LABELS,\n    computed(() => (outer === undefined ? source() : mergeVocabularies(outer.value, source()))),\n  );\n}\n\n/**\n * Resolve one component's slot: **own prop, then the host's vocabulary, then\n * the component's own English** — key by key, never whole-object.\n *\n * Key by key is the whole point. A host providing `{ pagination: { next: \"Sau\" } }`\n * keeps English for the other seven rather than rendering a row of unnamed\n * buttons, and an instance overriding its own `nav` does not discard the host's\n * other six. `optional()` is what makes each spread purely additive: it drops\n * the `undefined`-valued keys, so an absent override cannot blank a present\n * default. Same function, same reasoning, as the attribute spread in\n * `./field-context.ts`.\n *\n * The prop beating the provider is not a preference. A page with two paginations\n * that need different names has no other way out, and an application-wide\n * vocabulary that could not be corrected per instance would force a host to\n * choose between localising and naming.\n *\n * `defaults` arrives from the component rather than from a central English\n * bundle, and that is what bounds the cost of the seam: a consumer importing\n * only `Button` ships no label bytes at all, and one importing `Pagination`\n * ships `Pagination`'s. A central `en` object would always ship whole.\n *\n * The result is typed from `defaults` rather than from `LoomLabels[K]`, with\n * the registry entry as a constraint on it. Structurally that is the same\n * check — a bag that does not match its registered slot does not compile — but\n * it keeps the resolved type nameable from the module that declared it.\n */\nexport function useLabels<K extends keyof LoomLabels, T extends LoomLabels[K]>(\n  slot: K,\n  defaults: T,\n  own?: () => LabelOverrides<T> | undefined,\n): ComputedRef<LoomLabels[K]> {\n  const provided = inject(LOOM_LABELS, undefined);\n  // Read inside the `computed`, never above it: that is what puts the host's\n  // getter and this component's props inside the render effect, and it is the\n  // one line that decides whether a language switch repaints.\n  //\n  // `Object.assign` rather than an object spread, and that is a type-level\n  // choice rather than a stylistic one: spreading a generic `LoomLabels[K]`\n  // widens it to an index signature that no longer satisfies the return type,\n  // where `Object.assign` composes an intersection that does.\n  return computed(() =>\n    Object.assign({}, defaults, optional(provided?.value[slot] ?? {}), optional(own?.() ?? {})),\n  );\n}\n"],"mappings":";;;;;;;;AA4EA,IAAM,cAA6D,OAAO,aAAa;AAEvF,SAAS,kBACP,OACA,OACoB;CACpB,MAAM,SAAS,EAAE,GAAG,MAAM;CAC1B,MAAM,UAAU;CAChB,KAAK,MAAM,QAAQ,OAAO,KAAK,OAAO,GAAG;EACvC,MAAM,QAAQ,QAAQ;EACtB,IAAI,UAAU,KAAA,GAAW;EAGzB,OAAO,QAAQ;GAAE,GAAK,OAAO,SAAS,CAAC;GAAe,GAAG,SAAS,KAAK;EAAE;CAC3E;CACA,OAAO;AACT;;;;;;;;;;;;;;;;;;;;;;;;AAyBA,SAAgB,kBAAkB,QAAwC;CACxE,MAAM,QAAQ,OAAO,aAAa,KAAA,CAAS;CAC3C,QACE,aACA,eAAgB,UAAU,KAAA,IAAY,OAAO,IAAI,kBAAkB,MAAM,OAAO,OAAO,CAAC,CAAE,CAC5F;AACF;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA6BA,SAAgB,UACd,MACA,UACA,KAC4B;CAC5B,MAAM,WAAW,OAAO,aAAa,KAAA,CAAS;CAS9C,OAAO,eACL,OAAO,OAAO,CAAC,GAAG,UAAU,SAAS,UAAU,MAAM,SAAS,CAAC,CAAC,GAAG,SAAS,MAAM,KAAK,CAAC,CAAC,CAAC,CAC5F;AACF"}

package/dist/lib/motion.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"motion.d.ts","sourceRoot":"","sources":["../../src/lib/motion.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,eAAO,MAAM,oBAAoB,KAAK,CAAC;AACvC,eAAO,MAAM,gBAAgB,IAAI,CAAC;AAElC,8DAA8D;AAC9D,wBAAgB,gBAAgB,CAAC,CAAC,EAAE,MAAM,GAAG,MAAM,CAElD"}