@ecoma-io/loom 0.5.0 → 0.6.0

package/dist/packages/composition/sidebar/src/Sidebar.vue_vue_type_script_setup_true_lang.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Sidebar.vue_vue_type_script_setup_true_lang.js","names":[],"sources":["../../../../../packages/composition/sidebar/src/Sidebar.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * Sidebar — content + sidebar with intrinsic CSS collapse.\n *\n * The Every Layout \"Sidebar\" pattern: the sidebar gets a fixed `flex-basis`\n * and the content gets `flex-grow: 999`, so the layout wraps and both panels\n * go full-width the moment the content can't fit its `contentMin` percentage.\n * No media query, no JavaScript — the layout derives its own breakpoint from\n * the container's width.\n *\n * A Sidebar is a component because the `calc()` technique for intrinsic\n * sidebar width is non-obvious and easy to get wrong, and Loom wrapping it\n * prevents footguns. It differs from Split in that the content area is the\n * star — it grows to fill all available space — and the sidebar has a\n * preferred, not a minimum, width.\n */\nexport type SidebarSide = \"left\" | \"right\";\n</script>\n\n<script setup lang=\"ts\">\nimport { cn } from \"@ecoma-io/loom-core\";\n\nwithDefaults(\n  defineProps<{\n    /** Which side the sidebar sits on. Controls flex direction and stacking order. */\n    side?: SidebarSide;\n    /** Preferred width for the sidebar (e.g. \"16rem\"). The sidebar does not grow. */\n    sideWidth?: string;\n    /** Minimum percentage of the container the content demands before the layout wraps. Default: `\"50%\"`. */\n    contentMin?: string;\n    /** Whether to add a gap between the two panels. Default: `true`. */\n    gap?: boolean;\n  }>(),\n  { side: \"left\", sideWidth: \"16rem\", contentMin: \"50%\", gap: true },\n);\n</script>\n\n<template>\n  <!--\n    `flex-wrap: wrap` is the intrinsic collapse mechanism. When the content\n    can't fit its `contentMin`, it wraps to a new line and both panels take\n    full width — the sidebar becomes a full-width section above or below the\n    content, depending on `side`.\n\n    The sidebar's `flex-basis` is its preferred width. The content's\n    `flex-grow: 999` ensures it takes all remaining space when there is room,\n    but its `flex-basis: 0` and `min-width: contentMin` trigger wrapping\n    when there isn't.\n  -->\n  <div\n    :class=\"cn('flex flex-row', gap ? 'gap-3 sm:gap-4' : undefined)\"\n    :style=\"{ flexWrap: 'wrap' }\"\n  >\n    <!--\n      Document order follows `side`, so the wrapped stack never contradicts\n      the side-by-side row and screen-reader order matches the visual one:\n      content first when `side=\"right\"`, sidebar first when `side=\"left\"`.\n      flex-row (never reverse) plus this ordering is what makes the wrap\n      produce content-above-sidebar for `side=\"right\"`.\n    -->\n    <template v-if=\"side === 'right'\">\n      <!-- Content: fills all remaining space (flex-grow: 999), but its\n           min-width: contentMin triggers wrapping when there isn't room. -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: contentMin,\n        }\"\n      >\n        <slot />\n      </div>\n      <!-- Sidebar: preferred width as flex-basis, does not grow. -->\n      <div\n        :style=\"{\n          flexBasis: sideWidth,\n          flexGrow: 0,\n          flexShrink: 1,\n        }\"\n      >\n        <slot name=\"side\" />\n      </div>\n    </template>\n    <template v-else>\n      <!-- Sidebar: preferred width as flex-basis, does not grow. -->\n      <div\n        :style=\"{\n          flexBasis: sideWidth,\n          flexGrow: 0,\n          flexShrink: 1,\n        }\"\n      >\n        <slot name=\"side\" />\n      </div>\n      <!-- Content: fills all remaining space (flex-grow: 999), but its\n           min-width: contentMin triggers wrapping when there isn't room. -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: contentMin,\n        }\"\n      >\n        <slot />\n      </div>\n    </template>\n  </div>\n</template>\n"],"mappings":";;;;;;;;;;;;;;;;;GAiDE,OAAA,UAAA,GAAA,mBA2DM,OAAA;IA1DH,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,iBAAkB,QAAA,MAAG,mBAAsB,KAAA,CAAS,CAAA;IAC7D,OAAO,EAAA,UAAA,OAAA;GASQ,GAAA,CAAA,QAAA,SAAI,WAApB,UAAA,GAAA,mBAuBW,UAAA,EAAA,KAAA,EAAA,GAAA,CApBT,mBASM,OAAA,EARH,OAAK,eAAA;;;;IAAkG,UAAA,QAAA;GAOxG,CAAA,EAAA,GAAA,CAAA,WAAQ,KAAA,QAAA,SAAA,CAAA,GAAA,CAAA,GAGV,mBAQM,OAAA,EAPH,OAAK,eAAA;IAAyB,WAAA,QAAA;;;GAM/B,CAAA,EAAA,GAAA,CAAA,WAAoB,KAAA,QAAA,MAAA,CAAA,GAAA,CAAA,CAAA,GAAA,EAAA,MAGxB,UAAA,GAAA,mBAuBW,UAAA,EAAA,KAAA,EAAA,GAAA,CArBT,mBAQM,OAAA,EAPH,OAAK,eAAA;IAAyB,WAAA,QAAA;;;GAM/B,CAAA,EAAA,GAAA,CAAA,WAAoB,KAAA,QAAA,MAAA,CAAA,GAAA,CAAA,GAItB,mBASM,OAAA,EARH,OAAK,eAAA;;;;IAAkG,UAAA,QAAA;GAOxG,CAAA,EAAA,GAAA,CAAA,WAAQ,KAAA,QAAA,SAAA,CAAA,GAAA,CAAA,CAAA,GAAA,EAAA,EAAA,GAAA,CAAA"}

package/dist/packages/composition/split/src/Split.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Split.js","names":[],"sources":["../../../../../packages/composition/split/src/Split.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * Split — two-panel layout with intrinsic collapse.\n *\n * A flex row that places a side panel and a content area side by side, and\n * stacks them vertically once the container is too narrow for both. The side\n * panel gets a fixed minimum width; the content area grows to fill the\n * remaining space.\n *\n * This is the Every Layout \"Sidebar\" pattern, simplified for the common\n * two-panel case. The intrinsic collapse — panels stack when the container is\n * too narrow — avoids a breakpoint per viewport, and works identically inside\n * a sidebar-narrowed workspace and full-bleed on an ultra-wide monitor.\n *\n * A Split is a component, not a hand-rolled flex row with a media query,\n * because the wrap-and-floor technique is non-obvious and easy to get wrong,\n * and the stacking order (side above or below) is an intent the `side` prop\n * expresses.\n */\nexport type SplitSide = \"left\" | \"right\";\n\nexport type SplitGap = \"sm\" | \"md\" | \"lg\" | \"none\";\n\nconst gapClass: Record<Exclude<SplitGap, \"none\">, string> = {\n  sm: \"gap-2 sm:gap-3\",\n  md: \"gap-3 sm:gap-4\",\n  lg: \"gap-4 sm:gap-6\",\n} as const;\n\nexport { gapClass };\n</script>\n\n<script setup lang=\"ts\">\nimport { cn } from \"@ecoma-io/loom-core\";\n\nwithDefaults(\n  defineProps<{\n    /** The side the panel sits on. Controls stacking order when collapsed: \"left\" stacks the panel above, \"right\" stacks it below. */\n    side?: SplitSide;\n    /** Minimum width for the side panel (e.g. \"16rem\"). The content area takes the rest. */\n    minSideWidth?: string;\n    /** Gap between the two panels. Tightens one notch below `sm` (except \"none\"). */\n    gap?: SplitGap;\n  }>(),\n  { side: \"left\", minSideWidth: \"16rem\", gap: \"md\" },\n);\n</script>\n\n<template>\n  <!--\n    `flex-wrap` is the intrinsic collapse mechanism: when the combined\n    `min-width` of both panels exceeds the container, the second panel wraps\n    to a new line. Where that happens is decided by the panels' own minimum\n    widths — there is no breakpoint prop to set it with.\n  -->\n  <div\n    :class=\"cn('flex flex-row', gap !== 'none' ? gapClass[gap] : undefined)\"\n    :style=\"{\n      flexWrap: 'wrap',\n    }\"\n  >\n    <!--\n      Document order follows `side`, so the wrapped stack never contradicts\n      the side-by-side row and screen-reader order matches the visual one:\n      content first when `side=\"right\"`, side first when `side=\"left\"`.\n      flex-row (never reverse) plus this ordering is what makes the wrap\n      produce content-above-panel for `side=\"right\"`.\n    -->\n    <template v-if=\"side === 'right'\">\n      <!-- Content area: fills remaining space, but demands at least 50% of\n           the container before wrapping. When collapsed it also takes full\n           width. -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n      >\n        <slot />\n      </div>\n      <!-- Side panel: fixed minimum width, does not grow. When collapsed the\n           panel takes full width (flex-basis: 100%). -->\n      <div\n        :style=\"{\n          flexBasis: minSideWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n          minWidth: minSideWidth,\n        }\"\n      >\n        <slot name=\"side\" />\n      </div>\n    </template>\n    <template v-else>\n      <!-- Side panel: fixed minimum width, does not grow. When collapsed the\n           panel takes full width (flex-basis: 100%). -->\n      <div\n        :style=\"{\n          flexBasis: minSideWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n          minWidth: minSideWidth,\n        }\"\n      >\n        <slot name=\"side\" />\n      </div>\n      <!-- Content area: fills remaining space, but demands at least 50% of\n           the container before wrapping. When collapsed it also takes full\n           width. -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n      >\n        <slot />\n      </div>\n    </template>\n  </div>\n</template>\n"],"mappings":""}

package/dist/packages/composition/split/src/Split.vue_vue_type_script_setup_true_lang.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Split.vue_vue_type_script_setup_true_lang.js","names":[],"sources":["../../../../../packages/composition/split/src/Split.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * Split — two-panel layout with intrinsic collapse.\n *\n * A flex row that places a side panel and a content area side by side, and\n * stacks them vertically once the container is too narrow for both. The side\n * panel gets a fixed minimum width; the content area grows to fill the\n * remaining space.\n *\n * This is the Every Layout \"Sidebar\" pattern, simplified for the common\n * two-panel case. The intrinsic collapse — panels stack when the container is\n * too narrow — avoids a breakpoint per viewport, and works identically inside\n * a sidebar-narrowed workspace and full-bleed on an ultra-wide monitor.\n *\n * A Split is a component, not a hand-rolled flex row with a media query,\n * because the wrap-and-floor technique is non-obvious and easy to get wrong,\n * and the stacking order (side above or below) is an intent the `side` prop\n * expresses.\n */\nexport type SplitSide = \"left\" | \"right\";\n\nexport type SplitGap = \"sm\" | \"md\" | \"lg\" | \"none\";\n\nconst gapClass: Record<Exclude<SplitGap, \"none\">, string> = {\n  sm: \"gap-2 sm:gap-3\",\n  md: \"gap-3 sm:gap-4\",\n  lg: \"gap-4 sm:gap-6\",\n} as const;\n\nexport { gapClass };\n</script>\n\n<script setup lang=\"ts\">\nimport { cn } from \"@ecoma-io/loom-core\";\n\nwithDefaults(\n  defineProps<{\n    /** The side the panel sits on. Controls stacking order when collapsed: \"left\" stacks the panel above, \"right\" stacks it below. */\n    side?: SplitSide;\n    /** Minimum width for the side panel (e.g. \"16rem\"). The content area takes the rest. */\n    minSideWidth?: string;\n    /** Gap between the two panels. Tightens one notch below `sm` (except \"none\"). */\n    gap?: SplitGap;\n  }>(),\n  { side: \"left\", minSideWidth: \"16rem\", gap: \"md\" },\n);\n</script>\n\n<template>\n  <!--\n    `flex-wrap` is the intrinsic collapse mechanism: when the combined\n    `min-width` of both panels exceeds the container, the second panel wraps\n    to a new line. Where that happens is decided by the panels' own minimum\n    widths — there is no breakpoint prop to set it with.\n  -->\n  <div\n    :class=\"cn('flex flex-row', gap !== 'none' ? gapClass[gap] : undefined)\"\n    :style=\"{\n      flexWrap: 'wrap',\n    }\"\n  >\n    <!--\n      Document order follows `side`, so the wrapped stack never contradicts\n      the side-by-side row and screen-reader order matches the visual one:\n      content first when `side=\"right\"`, side first when `side=\"left\"`.\n      flex-row (never reverse) plus this ordering is what makes the wrap\n      produce content-above-panel for `side=\"right\"`.\n    -->\n    <template v-if=\"side === 'right'\">\n      <!-- Content area: fills remaining space, but demands at least 50% of\n           the container before wrapping. When collapsed it also takes full\n           width. -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n      >\n        <slot />\n      </div>\n      <!-- Side panel: fixed minimum width, does not grow. When collapsed the\n           panel takes full width (flex-basis: 100%). -->\n      <div\n        :style=\"{\n          flexBasis: minSideWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n          minWidth: minSideWidth,\n        }\"\n      >\n        <slot name=\"side\" />\n      </div>\n    </template>\n    <template v-else>\n      <!-- Side panel: fixed minimum width, does not grow. When collapsed the\n           panel takes full width (flex-basis: 100%). -->\n      <div\n        :style=\"{\n          flexBasis: minSideWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n          minWidth: minSideWidth,\n        }\"\n      >\n        <slot name=\"side\" />\n      </div>\n      <!-- Content area: fills remaining space, but demands at least 50% of\n           the container before wrapping. When collapsed it also takes full\n           width. -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n      >\n        <slot />\n      </div>\n    </template>\n  </div>\n</template>\n"],"mappings":";;;;;;;;;;;;;;;;AAuBA,IAAM,WAAsD;CAC1D,IAAI;CACJ,IAAI;CACJ,IAAI;AACN;;;;;;;;;;GA4BE,OAAA,UAAA,GAAA,mBAmEM,OAAA;IAlEH,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,iBAAkB,QAAA,QAAG,SAAc,SAAS,QAAA,OAAO,KAAA,CAAS,CAAA;IACrE,OAAO,EAAA,UAAA,OAEP;GASe,GAAA,CAAA,QAAA,SAAI,WAApB,UAAA,GAAA,mBA0BW,UAAA,EAAA,KAAA,EAAA,GAAA,CAtBT,mBASM,OATN,YASM,CADJ,WAAQ,KAAA,QAAA,SAAA,CAAA,CAAA,GAIV,mBASM,OAAA,EARH,OAAK,eAAA;IAAyB,WAAA,QAAA;;;IAAkF,UAAA,QAAA;GAOjH,CAAA,EAAA,GAAA,CAAA,WAAoB,KAAA,QAAA,MAAA,CAAA,GAAA,CAAA,CAAA,GAAA,EAAA,MAGxB,UAAA,GAAA,mBA0BW,UAAA,EAAA,KAAA,EAAA,GAAA,CAvBT,mBASM,OAAA,EARH,OAAK,eAAA;IAAyB,WAAA,QAAA;;;IAAkF,UAAA,QAAA;GAOjH,CAAA,EAAA,GAAA,CAAA,WAAoB,KAAA,QAAA,MAAA,CAAA,GAAA,CAAA,GAKtB,mBASM,OATN,YASM,CADJ,WAAQ,KAAA,QAAA,SAAA,CAAA,CAAA,CAAA,GAAA,EAAA,EAAA,GAAA,CAAA"}

package/dist/packages/composition/stack/src/Stack.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Stack.js","names":[],"sources":["../../../../../packages/composition/stack/src/Stack.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * Stack — vertical flow with consistent, responsive gap.\n *\n * A flex column that tightens its gutter one step below the `sm` breakpoint,\n * where stacked items have no room to waste on air. The gap steps mirror\n * DashboardGrid's: the value each step names applies from `sm` up, and drops\n * one notch below it.\n *\n * A Stack is a component, not `flex flex-col gap-4`, for three reasons: the\n * responsive gap is the component's job (not every call site's), the\n * `separator` slot avoids a repeated `v-for` + `v-if` pattern, and the\n * `align` prop maps cross-axis intent to a Tailwind class without the caller\n * remembering which flex utility is which.\n */\nexport type StackGap = \"sm\" | \"md\" | \"lg\";\n\nexport type StackAlign = \"start\" | \"center\" | \"end\" | \"stretch\";\n\nconst gapClass: Record<StackGap, string> = {\n  sm: \"gap-2 sm:gap-3\",\n  md: \"gap-3 sm:gap-4\",\n  lg: \"gap-4 sm:gap-6\",\n} as const;\n\nconst alignClass: Record<StackAlign, string> = {\n  start: \"items-start\",\n  center: \"items-center\",\n  end: \"items-end\",\n  stretch: \"items-stretch\",\n} as const;\n\nexport { gapClass, alignClass };\n</script>\n\n<script setup lang=\"ts\">\nimport { cn } from \"@ecoma-io/loom-core\";\n\nwithDefaults(\n  defineProps<{\n    /** Vertical gap step — mirrors DashboardGrid's scale. Tightens one notch below `sm`. */\n    gap?: StackGap;\n    /** Cross-axis alignment of children. */\n    align?: StackAlign;\n  }>(),\n  { gap: \"md\", align: \"stretch\" },\n);\n</script>\n\n<template>\n  <div :class=\"cn('flex flex-col', gapClass[gap], alignClass[align])\">\n    <!-- Each direct child is a stack item. The separator slot, if filled,\n         is rendered between every pair of children — a <Separator /> or a\n         thin <div class=\"border-t border-border\">, for example. -->\n    <slot />\n  </div>\n</template>\n"],"mappings":""}

package/dist/packages/composition/stack/src/Stack.vue_vue_type_script_setup_true_lang.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Stack.vue_vue_type_script_setup_true_lang.js","names":[],"sources":["../../../../../packages/composition/stack/src/Stack.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * Stack — vertical flow with consistent, responsive gap.\n *\n * A flex column that tightens its gutter one step below the `sm` breakpoint,\n * where stacked items have no room to waste on air. The gap steps mirror\n * DashboardGrid's: the value each step names applies from `sm` up, and drops\n * one notch below it.\n *\n * A Stack is a component, not `flex flex-col gap-4`, for three reasons: the\n * responsive gap is the component's job (not every call site's), the\n * `separator` slot avoids a repeated `v-for` + `v-if` pattern, and the\n * `align` prop maps cross-axis intent to a Tailwind class without the caller\n * remembering which flex utility is which.\n */\nexport type StackGap = \"sm\" | \"md\" | \"lg\";\n\nexport type StackAlign = \"start\" | \"center\" | \"end\" | \"stretch\";\n\nconst gapClass: Record<StackGap, string> = {\n  sm: \"gap-2 sm:gap-3\",\n  md: \"gap-3 sm:gap-4\",\n  lg: \"gap-4 sm:gap-6\",\n} as const;\n\nconst alignClass: Record<StackAlign, string> = {\n  start: \"items-start\",\n  center: \"items-center\",\n  end: \"items-end\",\n  stretch: \"items-stretch\",\n} as const;\n\nexport { gapClass, alignClass };\n</script>\n\n<script setup lang=\"ts\">\nimport { cn } from \"@ecoma-io/loom-core\";\n\nwithDefaults(\n  defineProps<{\n    /** Vertical gap step — mirrors DashboardGrid's scale. Tightens one notch below `sm`. */\n    gap?: StackGap;\n    /** Cross-axis alignment of children. */\n    align?: StackAlign;\n  }>(),\n  { gap: \"md\", align: \"stretch\" },\n);\n</script>\n\n<template>\n  <div :class=\"cn('flex flex-col', gapClass[gap], alignClass[align])\">\n    <!-- Each direct child is a stack item. The separator slot, if filled,\n         is rendered between every pair of children — a <Separator /> or a\n         thin <div class=\"border-t border-border\">, for example. -->\n    <slot />\n  </div>\n</template>\n"],"mappings":";;;;AAmBA,IAAM,WAAqC;CACzC,IAAI;CACJ,IAAI;CACJ,IAAI;AACN;AAEA,IAAM,aAAyC;CAC7C,OAAO;CACP,QAAQ;CACR,KAAK;CACL,SAAS;AACX;;;;;;;;;GAoBE,OAAA,UAAA,GAAA,mBAKM,OAAA,EALA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,iBAAkB,SAAS,QAAA,MAAM,WAAW,QAAA,MAAK,CAAA,EAAA,GAAA,CAI9D,WAAQ,KAAA,QAAA,SAAA,CAAA,GAAA,CAAA"}

package/dist/packages/core/src/a11y-scope.js

@@ -1,149 +0,0 @@
-//#region packages/core/src/a11y-scope.ts
-/**
-* The WCAG scope Loom holds itself to: the assistive-technology and keyboard
-* rules, not axe's SEO and document-structure best-practice set. A component
-* library cannot know what document it will be rendered into, so a rule about
-* the document is the consumer's to answer, not ours.
-*
-* Single source for every axe run against this package, and there is more
-* than one, in different processes: the jsdom demo sweep, the harness gate,
-* the root gate that scans the built site, and the pin tests that hold the
-* partition exact. All import this. The list must never be restated, or the
-* tier a contributor reads and the gate that blocks the merge drift into
-* disagreeing about what counts as a violation.
-*
-* Exported from the narrow `@ecoma-io/loom/a11y` entry so a tool that only
-* needs this array — a Playwright run, a CI script — can read it without
-* pulling in a single Vue component.
-*
-* The array is partitioned into BROWSERLESS_RULES, BROWSER_REQUIRED_RULES, and
-* TAGGED_BUT_DISABLED_RULES. The split line between the first two is whether a rule's
-* checks read layout geometry, hit-testing, pseudo-element or computed-color resolution,
-* cascade-dependent font metrics, canvas, or media state — none of which the jsdom demo
-* tier provides. TAGGED_BUT_DISABLED holds the WCAG-tagged rules that axe-core 4.12.1
-* ships with enabled:false; a tag-type runOnly (the old gate: withTags([...WCAG_TAGS]))
-* excludes them, so they were never part of the tag-selected rule set. A rule-type
-* runOnly (the gates that consume these lists: withRules([...list])) RUNS any named
-* rule regardless of enabled status.
-*
-* Loom's bar is that a rule mapping to a Level A or AA success criterion stays out of
-* the runtime tiers only when it is SUPERSEDED (another rule in the tiers already
-* judges the same criterion) or OUT-OF-REACH (the criterion needs something this
-* repository cannot supply) — "axe ships it disabled" is not a reason. The partition
-* below is the result of that review, 2026-08-26: of the 7 disabled rules, 5 were
-* adopted (aria-roledescription browserless; label-content-name-mismatch, p-as-heading,
-* table-fake-caption and td-has-header browser-required — the findings on loom's own
-* markup were fixed in the same change) and 2 remain out, each with its criterion and
-* its reason written below.
-*
-* The runtime tiers hold 68 of the 70 WCAG-tagged rules: BROWSERLESS_RULES (51) ∪
-* BROWSER_REQUIRED_RULES (17). The union of all three sets equals the full 70, which
-* is pinned by packages/core/tests/a11y-scope.test.ts.
-*/
-var WCAG_TAGS = [
-	"wcag2a",
-	"wcag2aa",
-	"wcag21a",
-	"wcag21aa",
-	"wcag22aa"
-];
-/**
-* Rules that can be judged in jsdom — semantic checks that read only the DOM,
-* attributes, and cascade (no layout geometry, hit-testing, pseudo-elements,
-* computed colors, canvas, or media state).
-*
-* These 51 rules are verified to produce identical verdicts in jsdom 30 and
-* Chromium on violation fixtures, and to agree on all 94 demos. Each entry
-* was classified by scanning its check helpers for browser-API dependencies;
-* the partition is pinned by packages/core/tests/a11y-scope.test.ts.
-*/
-var BROWSERLESS_RULES = [
-	"area-alt",
-	"aria-allowed-attr",
-	"aria-braille-equivalent",
-	"aria-command-name",
-	"aria-conditional-attr",
-	"aria-deprecated-role",
-	"aria-hidden-body",
-	"aria-input-field-name",
-	"aria-meter-name",
-	"aria-progressbar-name",
-	"aria-prohibited-attr",
-	"aria-required-attr",
-	"aria-required-children",
-	"aria-required-parent",
-	"aria-roledescription",
-	"aria-roles",
-	"aria-tab-name",
-	"aria-toggle-field-name",
-	"aria-tooltip-name",
-	"aria-valid-attr",
-	"aria-valid-attr-value",
-	"autocomplete-valid",
-	"blink",
-	"button-name",
-	"definition-list",
-	"dlitem",
-	"document-title",
-	"duplicate-id-aria",
-	"form-field-multiple-labels",
-	"frame-title",
-	"frame-title-unique",
-	"html-has-lang",
-	"html-lang-valid",
-	"html-xml-lang-mismatch",
-	"image-alt",
-	"input-button-name",
-	"input-image-alt",
-	"label",
-	"link-name",
-	"list",
-	"listitem",
-	"meta-refresh",
-	"meta-viewport",
-	"nested-interactive",
-	"role-img-alt",
-	"select-name",
-	"server-side-image-map",
-	"summary-name",
-	"svg-img-alt",
-	"valid-lang",
-	"video-caption"
-];
-/**
-* Rules that require a rendering engine — their checks (or, for the table
-* rules, their `matches` predicate) read layout geometry, hit-test results,
-* pseudo-element styles, computed color pipelines, cascade-dependent font
-* metrics, canvas, or media state (src, currentSrc, plays), which jsdom does
-* not provide — or which the jsdom demo tier cannot judge because it mounts
-* demos with no stylesheet loaded.
-*
-* These 17 rules are what the browser gates run. The split is:
-* - 11 rendering-dependent (geometry, hit-testing, computed colors, canvas, media, iframe content)
-* - 2 conservative-partial (table rules whose `matches` predicate uses border
-*   geometry; kept in browser until Table semantic markup is pinned)
-* - 4 adopted 2026-08-26 from TAGGED_BUT_DISABLED (see their own comments)
-*/
-var BROWSER_REQUIRED_RULES = [
-	"aria-hidden-focus",
-	"avoid-inline-spacing",
-	"bypass",
-	"color-contrast",
-	"frame-focusable-content",
-	"link-in-text-block",
-	"marquee",
-	"no-autoplay-audio",
-	"object-alt",
-	"scrollable-region-focusable",
-	"target-size",
-	"td-headers-attr",
-	"th-has-data-cells",
-	"label-content-name-mismatch",
-	"p-as-heading",
-	"table-fake-caption",
-	"td-has-header"
-];
-//#endregion
-export { BROWSERLESS_RULES, BROWSER_REQUIRED_RULES, WCAG_TAGS };
-
-//# sourceMappingURL=a11y-scope.js.map

package/dist/packages/core/src/a11y-scope.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"a11y-scope.js","names":[],"sources":["../../../../packages/core/src/a11y-scope.ts"],"sourcesContent":["/**\n * The WCAG scope Loom holds itself to: the assistive-technology and keyboard\n * rules, not axe's SEO and document-structure best-practice set. A component\n * library cannot know what document it will be rendered into, so a rule about\n * the document is the consumer's to answer, not ours.\n *\n * Single source for every axe run against this package, and there is more\n * than one, in different processes: the jsdom demo sweep, the harness gate,\n * the root gate that scans the built site, and the pin tests that hold the\n * partition exact. All import this. The list must never be restated, or the\n * tier a contributor reads and the gate that blocks the merge drift into\n * disagreeing about what counts as a violation.\n *\n * Exported from the narrow `@ecoma-io/loom/a11y` entry so a tool that only\n * needs this array — a Playwright run, a CI script — can read it without\n * pulling in a single Vue component.\n *\n * The array is partitioned into BROWSERLESS_RULES, BROWSER_REQUIRED_RULES, and\n * TAGGED_BUT_DISABLED_RULES. The split line between the first two is whether a rule's\n * checks read layout geometry, hit-testing, pseudo-element or computed-color resolution,\n * cascade-dependent font metrics, canvas, or media state — none of which the jsdom demo\n * tier provides. TAGGED_BUT_DISABLED holds the WCAG-tagged rules that axe-core 4.12.1\n * ships with enabled:false; a tag-type runOnly (the old gate: withTags([...WCAG_TAGS]))\n * excludes them, so they were never part of the tag-selected rule set. A rule-type\n * runOnly (the gates that consume these lists: withRules([...list])) RUNS any named\n * rule regardless of enabled status.\n *\n * Loom's bar is that a rule mapping to a Level A or AA success criterion stays out of\n * the runtime tiers only when it is SUPERSEDED (another rule in the tiers already\n * judges the same criterion) or OUT-OF-REACH (the criterion needs something this\n * repository cannot supply) — \"axe ships it disabled\" is not a reason. The partition\n * below is the result of that review, 2026-08-26: of the 7 disabled rules, 5 were\n * adopted (aria-roledescription browserless; label-content-name-mismatch, p-as-heading,\n * table-fake-caption and td-has-header browser-required — the findings on loom's own\n * markup were fixed in the same change) and 2 remain out, each with its criterion and\n * its reason written below.\n *\n * The runtime tiers hold 68 of the 70 WCAG-tagged rules: BROWSERLESS_RULES (51) ∪\n * BROWSER_REQUIRED_RULES (17). The union of all three sets equals the full 70, which\n * is pinned by packages/core/tests/a11y-scope.test.ts.\n */\nexport const WCAG_TAGS = [\"wcag2a\", \"wcag2aa\", \"wcag21a\", \"wcag21aa\", \"wcag22aa\"] as const;\n\n/**\n * Rules that can be judged in jsdom — semantic checks that read only the DOM,\n * attributes, and cascade (no layout geometry, hit-testing, pseudo-elements,\n * computed colors, canvas, or media state).\n *\n * These 51 rules are verified to produce identical verdicts in jsdom 30 and\n * Chromium on violation fixtures, and to agree on all 94 demos. Each entry\n * was classified by scanning its check helpers for browser-API dependencies;\n * the partition is pinned by packages/core/tests/a11y-scope.test.ts.\n */\nexport const BROWSERLESS_RULES = [\n  \"area-alt\",\n  \"aria-allowed-attr\",\n  \"aria-braille-equivalent\",\n  \"aria-command-name\",\n  \"aria-conditional-attr\",\n  \"aria-deprecated-role\",\n  \"aria-hidden-body\",\n  \"aria-input-field-name\",\n  \"aria-meter-name\",\n  \"aria-progressbar-name\",\n  \"aria-prohibited-attr\",\n  \"aria-required-attr\",\n  \"aria-required-children\",\n  \"aria-required-parent\",\n  // Adopted 2026-08-26 from TAGGED_BUT_DISABLED. Deprecated by axe-core\n  // 4.7.0 with NO successor — the axe-core change that deprecated it states\n  // there is no other rule testing aria-roledescription usage — so WCAG 4.1.2\n  // (Level A) had nothing judging it.\n  // The check reads only the element's role (axe commons getRole), no\n  // browser API: identical verdicts measured jsdom vs Chromium on five\n  // fixtures including two violations (aria-roledescription on a roleless\n  // div, and on role=\"presentation\"), and clean on all 94 demos in both\n  // engines. Loom ships this attribute through Reka (NumberField's\n  // spinbutton, ColorPicker's slider surfaces) — all on roled elements,\n  // which the rule passes.\n  \"aria-roledescription\",\n  \"aria-roles\",\n  \"aria-tab-name\",\n  \"aria-toggle-field-name\",\n  \"aria-tooltip-name\",\n  \"aria-valid-attr\",\n  \"aria-valid-attr-value\",\n  \"autocomplete-valid\",\n  \"blink\",\n  \"button-name\",\n  \"definition-list\",\n  \"dlitem\",\n  \"document-title\",\n  \"duplicate-id-aria\",\n  \"form-field-multiple-labels\",\n  \"frame-title\",\n  \"frame-title-unique\",\n  \"html-has-lang\",\n  \"html-lang-valid\",\n  \"html-xml-lang-mismatch\",\n  \"image-alt\",\n  \"input-button-name\",\n  \"input-image-alt\",\n  \"label\",\n  \"link-name\",\n  \"list\",\n  \"listitem\",\n  \"meta-refresh\",\n  \"meta-viewport\",\n  \"nested-interactive\",\n  \"role-img-alt\",\n  \"select-name\",\n  \"server-side-image-map\",\n  \"summary-name\",\n  \"svg-img-alt\",\n  \"valid-lang\",\n  \"video-caption\",\n] as const;\n\n/**\n * Rules that require a rendering engine — their checks (or, for the table\n * rules, their `matches` predicate) read layout geometry, hit-test results,\n * pseudo-element styles, computed color pipelines, cascade-dependent font\n * metrics, canvas, or media state (src, currentSrc, plays), which jsdom does\n * not provide — or which the jsdom demo tier cannot judge because it mounts\n * demos with no stylesheet loaded.\n *\n * These 17 rules are what the browser gates run. The split is:\n * - 11 rendering-dependent (geometry, hit-testing, computed colors, canvas, media, iframe content)\n * - 2 conservative-partial (table rules whose `matches` predicate uses border\n *   geometry; kept in browser until Table semantic markup is pinned)\n * - 4 adopted 2026-08-26 from TAGGED_BUT_DISABLED (see their own comments)\n */\nexport const BROWSER_REQUIRED_RULES = [\n  // Rendering-dependent (11): each checks geometry/hit-test/computed styles/canvas/media/iframe\n  \"aria-hidden-focus\", // isModalOpen → elementsFromPoint, cantTell in jsdom\n  \"avoid-inline-spacing\", // letter-spacing unresolved + Range.getClientRects gate → false-pass\n  \"bypass\", // same modal-open throw; also pageLevel (page-scoped, wrong in component harness)\n  \"color-contrast\", // computed color pipeline — jsdom cantTell on every node\n  \"frame-focusable-content\", // iframe content inspection — requires browser to load frame\n  \"link-in-text-block\", // innerText + color + rects\n  \"marquee\", // jsdom default overflow:hidden + zero rect → false-pass\n  \"no-autoplay-audio\", // currentSrc empty → never runs\n  \"object-alt\", // matches throws on getClientRects\n  \"scrollable-region-focusable\", // content-vs-container rects zero → never matches, silent false-pass\n  \"target-size\", // zero rects read compliant — silent false-pass on real violations\n  // Conservative-partial (2): table rules using border geometry; jsdom skips border-only tables\n  \"td-headers-attr\", // border heuristic (offsetWidth !== clientHeight)\n  \"th-has-data-cells\", // same border heuristic\n  // Adopted 2026-08-26 (4), each with the measured reason jsdom cannot judge it:\n  \"label-content-name-mismatch\", // WCAG 2.5.3 (A). Measured: 12 violations on\n  // the stepper demo in Chromium, incomplete in jsdom — the visible-text half\n  // of the check reads on-screen geometry (axe's hiddenMethods: opacity, clip,\n  // coords) and icon-ligature detection needs a 2d canvas context, which jsdom\n  // returns null without the `canvas` package. Its stepper/app-header findings\n  // were fixed in the same change as this adoption.\n  \"p-as-heading\", // WCAG 1.3.1 (A). The check reads computed font-weight/-size/\n  // font-style; the jsdom demo tier mounts demos with no stylesheet, so\n  // class-styled emphasis reads as default weight there — the card/empty-state\n  // findings existed only in Chromium. Theme-invariant (font metrics do not\n  // depend on data-theme), so the dark pass gains nothing from re-running it.\n  \"table-fake-caption\", // WCAG 1.3.1 (A). The check itself is DOM-only (toGrid),\n  // but data-table-matches → isDataTable classifies border-only tables through\n  // offsetWidth/clientWidth geometry. Measured: a border-only table whose\n  // first row is one colspanning cell violates in Chromium and never matches\n  // in jsdom — same conservative-partial profile as td-headers-attr above.\n  \"td-has-header\", // WCAG 1.3.1 (A). Same isDataTable dependency. Measured:\n  // a 3x3 border-only table violates in Chromium and never matches in jsdom —\n  // a silent false-pass if this were browserless.\n] as const;\n\n/**\n * WCAG-tagged rules that axe-core 4.12.1 ships with enabled: false and that\n * stay OUT of the runtime tiers — each with its success criterion and the\n * OUT-OF-REACH reason, per the review of 2026-08-26. A disabled rule may only\n * sit here if the criterion needs something this repository cannot supply;\n * \"axe ships it disabled\" is not a reason, and neither is a finding on loom's\n * own markup (that gets fixed and the rule adopted — the other five disabled\n * rules went exactly that way).\n *\n * Naming one of these in a rule-type runOnly would run it anyway (enabled\n * status does not gate withRules), which is why they live in their own list\n * rather than being deleted: the union pin in packages/core/tests/\n * a11y-scope.test.ts keeps the 70-rule partition exact, and a future\n * component that reaches one of these criteria re-adjudicates here.\n */\nexport const TAGGED_BUT_DISABLED_RULES = [\n  // WCAG 1.2.1 (Audio-only and Video-only, Level A). OUT-OF-REACH: the\n  // criterion needs real audio media — loom ships no <audio> element in any\n  // component, demo or docs page (zero grep hits in packages/ and docs/),\n  // and a component library supplies structure, not media. Even if one\n  // appeared, this rule could never redden a gate: its caption check\n  // (axe-core 4.12.1 source) returns false when a captions track exists and\n  // void 0 otherwise — pass or incomplete, never a violation. axe-core\n  // deprecated it in 3.1.0 because WebVTT caption tracks on <audio> do not\n  // function in any browser (\"Audio captions do not work\", per the\n  // deprecation change itself); the text alternative 1.2.1 actually asks for\n  // is host content, not markup.\n  \"audio-caption\",\n  // WCAG 1.3.4 (Orientation, Level AA). OUT-OF-REACH: the criterion needs an\n  // orientation-locked app shell — CSS orientation media queries with fixed\n  // extents, or the Screen Orientation API — and loom ships neither in any\n  // component, demo, docs page or the harness's own stylesheet (zero grep\n  // hits; theme.css is orientation-agnostic by design, tokens not layout).\n  // Locking orientation is the host application's decision; measured 2026-08-26\n  // the rule passes every one of the 94 demos in Chromium, where it reads the\n  // preloaded CSSOM jsdom does not provide.\n  \"css-orientation-lock\",\n] as const;\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAyCA,IAAa,YAAY;CAAC;CAAU;CAAW;CAAW;CAAY;AAAU;;;;;;;;;;;AAYhF,IAAa,oBAAoB;CAC/B;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CAYA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;AACF;;;;;;;;;;;;;;;AAgBA,IAAa,yBAAyB;CAEpC;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CAEA;CACA;CAEA;CAMA;CAKA;CAKA;AAGF"}

package/dist/packages/core/src/attrs.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"attrs.js","names":[],"sources":["../../../../packages/core/src/attrs.ts"],"sourcesContent":["import { computed, useAttrs, type ComputedRef } from \"vue\";\n\n/**\n * Split `useAttrs()` into the raw fallthrough attributes — read `.class` off\n * `attrs` for a `cn()` merge — and the same attributes minus `class` (`rest`,\n * for `v-bind` onto whichever node is not the `class` target).\n *\n * Every caller pairs this with `defineOptions({ inheritAttrs: false })`.\n * NumberField's input, Slider's thumb and Select's trigger each route `class`\n * onto one specific rendered node rather than taking Vue's default\n * single-root fallthrough, because `class` needs a Tailwind-aware merge while\n * the rest of the fallthrough — aria-*, data-testid — only needs to land\n * somewhere real.\n */\nexport function useSplitAttrs(): {\n  attrs: Record<string, unknown>;\n  rest: ComputedRef<Record<string, unknown>>;\n} {\n  const attrs = useAttrs();\n  const rest = computed(() => {\n    const { class: _class, ...others } = attrs;\n    return others;\n  });\n  return { attrs, rest };\n}\n"],"mappings":";;;;;;;;;;;;;;AAcA,SAAgB,gBAGd;CACA,MAAM,QAAQ,SAAS;CAKvB,OAAO;EAAE;EAAO,MAJH,eAAe;GAC1B,MAAM,EAAE,OAAO,QAAQ,GAAG,WAAW;GACrC,OAAO;EACT,CACgB;CAAK;AACvB"}

package/dist/packages/core/src/cn.js

@@ -1,61 +0,0 @@
-import { clsx } from "clsx";
-import { extendTailwindMerge } from "tailwind-merge";
-//#region packages/core/src/cn.ts
-var twMerge = extendTailwindMerge({ extend: { classGroups: {
-	"font-size": [
-		"text-display",
-		"text-heading",
-		"text-title",
-		"text-body",
-		"text-small",
-		"text-micro"
-	],
-	animate: [
-		"animate-fade",
-		"animate-fade-rise",
-		"animate-fade-out",
-		"animate-fade-fall",
-		"animate-scale-in",
-		"animate-scale-out",
-		"animate-shimmer",
-		"animate-progress-indeterminate",
-		"animate-toast-in",
-		"animate-slide-out-to-left",
-		"animate-slide-out-to-right",
-		"animate-slide-out-to-top",
-		"animate-slide-out-to-bottom"
-	],
-	duration: [
-		"duration-instant",
-		"duration-fast",
-		"duration-slow",
-		"duration-slower"
-	],
-	ease: ["ease-spring"],
-	z: [
-		"z-raised",
-		"z-sticky",
-		"z-chrome",
-		"z-overlay",
-		"z-toast"
-	],
-	opacity: [
-		"opacity-disabled",
-		"opacity-scrim",
-		"opacity-scrim-light"
-	],
-	scale: ["scale-press"]
-} } });
-/**
-* Merge conditional class names, resolving Tailwind conflicts so the last
-* utility in a group wins. Every component routes its `class` through this,
-* which is what lets a consumer override any utility from the outside without
-* reaching for `!important`.
-*/
-function cn(...inputs) {
-	return twMerge(clsx(inputs));
-}
-//#endregion
-export { cn };
-
-//# sourceMappingURL=cn.js.map

package/dist/packages/core/src/cn.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"cn.js","names":[],"sources":["../../../../packages/core/src/cn.ts"],"sourcesContent":["import { type ClassValue, clsx } from \"clsx\";\nimport { extendTailwindMerge } from \"tailwind-merge\";\n\n/**\n * Loom's named type scale, as tailwind-merge knows it.\n *\n * `theme.css` declares the scale under Tailwind's `--text-*` namespace, which\n * makes `text-body` a font-size utility exactly like `text-sm`. tailwind-merge\n * cannot see that: it resolves conflicts from a static table of Tailwind's own\n * value names, and every unrecognised `text-<x>` falls through to the colour\n * group. So `text-micro` and `text-primary-foreground` looked like two colours,\n * the later one won, and the size was dropped on the floor.\n *\n * The failure is silent and it is not hypothetical — Indicator's count pill was\n * shipping without its 11px size, and it was found by reading a diff rather\n * than by anything failing. It also reached further than any one component:\n * `cn()` is the documented way a consumer overrides a class from outside, so\n * `<PageHeader class=\"text-small\">` had its size swallowed by the component's\n * own `text-foreground` and there was nothing to notice.\n *\n * Registering the six names restores the property they actually set. Both\n * directions then merge correctly against Tailwind's built-ins, because they\n * are one group rather than two: `text-xs text-body` keeps `text-body`, and\n * `text-body text-xs` keeps `text-xs`.\n */\nconst TYPE_SCALE = [\n  \"text-display\",\n  \"text-heading\",\n  \"text-title\",\n  \"text-body\",\n  \"text-small\",\n  \"text-micro\",\n];\n\n/**\n * The rest of the named vocabulary, registered for the same reason and found by\n * probing rather than by reading — every one of these was returning *both*\n * classes, leaving the winner to stylesheet order instead of to what the\n * component wrote.\n *\n * A registration here is the precondition for adding a name to `theme.css`, not\n * a follow-up to it. Anything Loom names under a namespace tailwind-merge\n * resolves by value table — durations, easings, animations — is invisible to it\n * until it appears below, and the defect it produces is the silent one this\n * file already exists to document.\n */\nconst ANIMATIONS = [\n  \"animate-fade\",\n  \"animate-fade-rise\",\n  \"animate-fade-out\",\n  \"animate-fade-fall\",\n  \"animate-scale-in\",\n  \"animate-scale-out\",\n  \"animate-shimmer\",\n  \"animate-progress-indeterminate\",\n  \"animate-toast-in\",\n  \"animate-slide-out-to-left\",\n  \"animate-slide-out-to-right\",\n  \"animate-slide-out-to-top\",\n  \"animate-slide-out-to-bottom\",\n];\n\n// The four `@utility` blocks at the foot of `theme.css`. They exist because\n// Tailwind's generated `duration-*` takes a millisecond count and not a token\n// name, which is the same reason tailwind-merge cannot see them either.\nconst DURATIONS = [\"duration-instant\", \"duration-fast\", \"duration-slow\", \"duration-slower\"];\n\n// `ease-out`, `ease-in` and `ease-in-out` are Tailwind's own names and already\n// resolve; only the restrained overshoot is ours.\nconst EASINGS = [\"ease-spring\"];\n\nconst twMerge = extendTailwindMerge({\n  extend: {\n    classGroups: {\n      \"font-size\": TYPE_SCALE,\n      animate: ANIMATIONS,\n      duration: DURATIONS,\n      ease: EASINGS,\n      z: [\"z-raised\", \"z-sticky\", \"z-chrome\", \"z-overlay\", \"z-toast\"],\n      opacity: [\"opacity-disabled\", \"opacity-scrim\", \"opacity-scrim-light\"],\n      scale: [\"scale-press\"],\n    },\n  },\n});\n\n/**\n * Merge conditional class names, resolving Tailwind conflicts so the last\n * utility in a group wins. Every component routes its `class` through this,\n * which is what lets a consumer override any utility from the outside without\n * reaching for `!important`.\n */\nexport function cn(...inputs: ClassValue[]): string {\n  return twMerge(clsx(inputs));\n}\n"],"mappings":";;;AAuEA,IAAM,UAAU,oBAAoB,EAClC,QAAQ,EACN,aAAa;CACX,aAAa;EAhDjB;EACA;EACA;EACA;EACA;EACA;CA2CiB;CACb,SAAS;EA5Bb;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;CAgBa;CACT,UAAU;EAXG;EAAoB;EAAiB;EAAiB;CAWzD;CACV,MAAM,CARK,aAQL;CACN,GAAG;EAAC;EAAY;EAAY;EAAY;EAAa;CAAS;CAC9D,SAAS;EAAC;EAAoB;EAAiB;CAAqB;CACpE,OAAO,CAAC,aAAa;AACvB,EACF,EACF,CAAC;;;;;;;AAQD,SAAgB,GAAG,GAAG,QAA8B;CAClD,OAAO,QAAQ,KAAK,MAAM,CAAC;AAC7B"}

package/dist/packages/core/src/icon-defaults.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"icon-defaults.js","names":[],"sources":["../../../../packages/core/src/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/packages/core/src/index.js

@@ -1,8 +0,0 @@
-import { cn } from "./cn.js";
-import { optional } from "./props.js";
-import { useSplitAttrs } from "./attrs.js";
-import { listStaggerDelay, smoothScrollBehavior } from "./motion.js";
-import { BROWSERLESS_RULES, BROWSER_REQUIRED_RULES, WCAG_TAGS } from "./a11y-scope.js";
-import { themeScript, useTheme } from "./theme.js";
-import { applyLoomIconDefaults } from "./icon-defaults.js";
-export { BROWSERLESS_RULES, BROWSER_REQUIRED_RULES, WCAG_TAGS, applyLoomIconDefaults, cn, listStaggerDelay, optional, smoothScrollBehavior, themeScript, useSplitAttrs, useTheme };

package/dist/packages/core/src/motion.js

@@ -1,27 +0,0 @@
-/** The inline `animation-delay` for the i-th revealed row. */
-function listStaggerDelay(i) {
-	return `${String(Math.min(i, 5) * 24)}ms`;
-}
-/**
-* The behaviour a scripted scroll should ask for, given the reader's motion
-* preference: `"smooth"` normally, `"auto"` under
-* `prefers-reduced-motion`.
-*
-* It has to exist because the stylesheet's kill-switch cannot reach this
-* path: an explicit `"smooth"` in a `scrollTo` dictionary *overrides* the
-* CSS `scroll-behavior` property — that is what the spec defines a
-* non-`"auto"` behaviour value to mean. Every component that scrolls by
-* script (ScrollReel, Carousel) asks this instead of deciding alone, which
-* is why it lives here and not in either of them.
-*/
-function smoothScrollBehavior() {
-	try {
-		return window.matchMedia("(prefers-reduced-motion: reduce)").matches ? "auto" : "smooth";
-	} catch {
-		return "smooth";
-	}
-}
-//#endregion
-export { listStaggerDelay, smoothScrollBehavior };
-
-//# sourceMappingURL=motion.js.map

package/dist/packages/core/src/motion.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"motion.js","names":[],"sources":["../../../../packages/core/src/motion.ts"],"sourcesContent":["/**\n * The list-reveal stagger vocabulary — one source for every overlay that\n * reveals rows (DropdownMenu, Menubar, Select) and for the Motion\n * documentation page. Each revealed row is delayed one step after the\n * previous, capped so a long list does not tail off indefinitely.\n *\n * It lives here rather than in each template because it was written into\n * three of them independently once, which is how the three drifted.\n */\nexport const LIST_STAGGER_STEP_MS = 24;\nexport const LIST_STAGGER_CAP = 5;\n\n/** The inline `animation-delay` for the i-th revealed row. */\nexport function listStaggerDelay(i: number): string {\n  return `${String(Math.min(i, LIST_STAGGER_CAP) * LIST_STAGGER_STEP_MS)}ms`;\n}\n\n/**\n * The behaviour a scripted scroll should ask for, given the reader's motion\n * preference: `\"smooth\"` normally, `\"auto\"` under\n * `prefers-reduced-motion`.\n *\n * It has to exist because the stylesheet's kill-switch cannot reach this\n * path: an explicit `\"smooth\"` in a `scrollTo` dictionary *overrides* the\n * CSS `scroll-behavior` property — that is what the spec defines a\n * non-`\"auto\"` behaviour value to mean. Every component that scrolls by\n * script (ScrollReel, Carousel) asks this instead of deciding alone, which\n * is why it lives here and not in either of them.\n */\nexport function smoothScrollBehavior(): \"auto\" | \"smooth\" {\n  try {\n    return window.matchMedia(\"(prefers-reduced-motion: reduce)\").matches ? \"auto\" : \"smooth\";\n  } catch {\n    // matchMedia may be unavailable; smooth is the behaviour being replaced.\n    return \"smooth\";\n  }\n}\n"],"mappings":";AAaA,SAAgB,iBAAiB,GAAmB;CAClD,OAAO,GAAG,OAAO,KAAK,IAAI,GAAA,CAAmB,IAAA,EAAwB,EAAE;AACzE;;;;;;;;;;;;;AAcA,SAAgB,uBAA0C;CACxD,IAAI;EACF,OAAO,OAAO,WAAW,kCAAkC,CAAC,CAAC,UAAU,SAAS;CAClF,QAAQ;EAEN,OAAO;CACT;AACF"}

package/dist/packages/core/src/props.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"props.js","names":[],"sources":["../../../../packages/core/src/props.ts"],"sourcesContent":["/**\n * Drops the keys whose value is `undefined`, so a `v-bind` passes only the\n * props that were actually set.\n *\n * Two rules collide to make this necessary, and neither is avoidable.\n *\n * Vue treats a prop that is absent and a prop explicitly set to `undefined` as\n * the same thing — both resolve to the child's default. TypeScript, under\n * `exactOptionalPropertyTypes`, does not: passing `undefined` to a `foo?: T` is\n * an error, because the flag exists precisely to tell \"missing\" apart from\n * \"present and undefined\". A Vue template always emits every key it binds, so\n * forwarding an optional prop straight through (`:open=\"open\"`) hands a child's\n * `open?: boolean` an explicit `undefined` and fails to compile, while behaving\n * correctly at run time.\n *\n * That distinction is not academic for the components underneath. Reka reads\n * `undefined` as \"no value supplied — manage this yourself\", and any concrete\n * value, `false` included, as \"the host owns this\". So a control whose\n * `modelValue` is coerced to `false` on its way through stops being\n * uncontrolled and becomes permanently, silently off: it still emits its update\n * event, and its rendered state never moves. That failure has no error and no\n * warning; it looks like a component that ignores clicks.\n *\n * A cast (`open as boolean`) silences the compiler and is the reason to prefer\n * this: it states that a value is there when the whole point is that one may\n * not be. Omitting the key says what is true.\n */\nexport function optional<T extends Record<string, unknown>>(\n  values: T,\n): { [K in keyof T]?: Exclude<T[K], undefined> } {\n  const set: Record<string, unknown> = {};\n  for (const key of Object.keys(values)) {\n    if (values[key] !== undefined) set[key] = values[key];\n  }\n  return set as { [K in keyof T]?: Exclude<T[K], undefined> };\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;AA2BA,SAAgB,SACd,QAC+C;CAC/C,MAAM,MAA+B,CAAC;CACtC,KAAK,MAAM,OAAO,OAAO,KAAK,MAAM,GAClC,IAAI,OAAO,SAAS,KAAA,GAAW,IAAI,OAAO,OAAO;CAEnD,OAAO;AACT"}

package/dist/packages/core/src/theme.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"theme.js","names":[],"sources":["../../../../packages/core/src/theme.ts"],"sourcesContent":["/**\n * Theme switching for Loom.\n *\n * The single source of truth is the `data-theme` attribute on `<html>`.\n * This composable reads and writes it, persists the preference to\n * `localStorage`, and resolves `\"system\"` mode from the OS preference.\n *\n * SSR-safe: every DOM access is guarded. On the server, `theme` returns\n * the persisted or default preference, `resolvedTheme` resolves `\"system\"`\n * to `\"light\"` (the only safe default without a DOM), and the setter and\n * toggler are no-ops.\n *\n * Flash prevention: `themeScript` is a string of inline JavaScript that\n * reads `localStorage` and sets `data-theme` before the first paint.\n * Consumers rendering SSR inject it into `<head>`:\n *\n *   <script>${themeScript}</script>\n */\n\nimport { type Ref, EffectScope, computed, getCurrentScope, onScopeDispose, ref, watch } from \"vue\";\n\n/** The preference a user expresses — `\"system\"` defers to the OS. */\nexport type ThemePreference = \"light\" | \"dark\" | \"system\";\n\n/** The actual theme applied — `\"system\"` is resolved away. */\nexport type ResolvedTheme = \"light\" | \"dark\";\n\nconst STORAGE_KEY = \"loom:theme\";\nconst DATA_ATTR = \"data-theme\";\nconst MEDIA_QUERY = \"(prefers-color-scheme: dark)\";\n\n/** Default preference when nothing is stored and no OS signal exists. */\nconst DEFAULT_PREFERENCE: ThemePreference = \"system\";\n\n// --- Shared state (one per Vue app, not one per composable call) ---------\n\ninterface ThemeState {\n  preference: Ref<ThemePreference>;\n  systemIsDark: Ref<boolean>;\n  mediaQuery: MediaQueryList | null;\n  listener: ((e: MediaQueryListEvent) => void) | null;\n  /** Consumers that can be released — see `useTheme` for who does not count. */\n  scopeCount: number;\n  /**\n   * The detached scope that owns the apply/persist watcher below. The side\n   * effects are the shared state's, not the first consumer's: owned by a\n   * consumer's scope they would die the day that component unmounted while\n   * later ones stayed mounted, leaving an app whose theme button had gone\n   * silent. Detached so creation inside a component setup does not link it\n   * into that component's own scope.\n   */\n  owner: EffectScope;\n  /**\n   * The preference last written to `localStorage`. `\"system\"` resolves away,\n   * so OS dark-mode flips fire the watcher with a preference that has not\n   * changed — without this, every flip rewrites storage with the same value.\n   */\n  lastPersisted: ThemePreference;\n}\n\n/**\n * Reactive shared state, lazily initialised on the first `useTheme()` call\n * and torn down with the effect scope that owns it. Multiple components\n * calling `useTheme()` in the same app share the same refs and the same\n * `matchMedia` listener.\n */\nlet sharedState: ThemeState | null = null;\n\n/** Fired once, at the first `useTheme()` call made outside any active effect scope. */\nlet warnedOutsideScope = false;\n\n/**\n * Reset the shared state. Intended for test isolation only — a real app\n * never needs this because the state lives for the app's lifetime.\n */\nexport function _resetThemeState(): void {\n  if (sharedState) {\n    sharedState.owner.stop();\n    if (sharedState.mediaQuery && sharedState.listener) {\n      sharedState.mediaQuery.removeEventListener(\"change\", sharedState.listener);\n    }\n  }\n  sharedState = null;\n  warnedOutsideScope = false;\n}\n\nfunction getSharedState(): ThemeState {\n  // A consumer is released by the effect scope it was called from, so a call\n  // from outside any scope is one that could never be released — counting it\n  // would pin the matchMedia listener open forever. It still gets the state,\n  // but it does not count toward teardown, and development is told once so\n  // the eventual leak is attributed to a call site instead of discovered as\n  // an immortal listener.\n  const scoped = getCurrentScope() !== undefined;\n  if (!scoped && !warnedOutsideScope) {\n    warnedOutsideScope = true;\n    console.warn(\n      \"[loom] useTheme() called outside an active effect scope; the shared theme state can never be released. Call it from setup() or inside an effectScope().\",\n    );\n  }\n\n  if (sharedState) {\n    if (scoped) sharedState.scopeCount++;\n    return sharedState;\n  }\n\n  // Read the stored preference, defaulting to \"system\".\n  let stored: ThemePreference = DEFAULT_PREFERENCE;\n  try {\n    const raw = localStorage.getItem(STORAGE_KEY);\n    if (raw === \"light\" || raw === \"dark\" || raw === \"system\") {\n      stored = raw;\n    }\n  } catch {\n    // localStorage may be unavailable (SSR, private browsing).\n  }\n\n  // Apply the initial theme to the DOM so the very first render is correct.\n  const initial = resolveTheme(stored, getSystemIsDark());\n  applyToDOM(initial);\n\n  const preference = ref<ThemePreference>(stored);\n  const systemIsDark = ref<boolean>(getSystemIsDark());\n\n  // Listen for OS dark-mode changes.\n  let mediaQuery: MediaQueryList | null = null;\n  let listener: ((e: MediaQueryListEvent) => void) | null = null;\n\n  try {\n    mediaQuery = window.matchMedia(MEDIA_QUERY);\n    listener = (e: MediaQueryListEvent) => {\n      systemIsDark.value = e.matches;\n    };\n    mediaQuery.addEventListener(\"change\", listener);\n  } catch {\n    // matchMedia may be unavailable.\n  }\n\n  const owner = new EffectScope(true);\n  const state: ThemeState = {\n    preference,\n    systemIsDark,\n    mediaQuery,\n    listener,\n    scopeCount: scoped ? 1 : 0,\n    owner,\n    lastPersisted: stored,\n  };\n  sharedState = state;\n\n  // The apply/persist watcher is created exactly once, here in the detached\n  // scope that owns the shared state — never per consumer. N components\n  // calling `useTheme()` must not mean N writes to `data-theme` and\n  // `localStorage` on every change.\n  owner.run(() => {\n    watch([preference, systemIsDark], () => {\n      // Applied even when the preference itself has not moved: an OS flip\n      // under `\"system\"` resolves differently without any user action.\n      applyToDOM(resolveTheme(preference.value, systemIsDark.value));\n      if (preference.value !== state.lastPersisted) {\n        state.lastPersisted = preference.value;\n        persist(state.lastPersisted);\n      }\n    });\n  });\n\n  return state;\n}\n\nfunction releaseSharedState(): void {\n  if (!sharedState) return;\n  sharedState.scopeCount--;\n  if (sharedState.scopeCount > 0) return;\n\n  // Last counted consumer gone — stop the side effects, then the listener.\n  sharedState.owner.stop();\n  if (sharedState.mediaQuery && sharedState.listener) {\n    sharedState.mediaQuery.removeEventListener(\"change\", sharedState.listener);\n  }\n  sharedState = null;\n}\n\n// --- DOM helpers --------------------------------------------------------\n\nfunction getSystemIsDark(): boolean {\n  try {\n    return window.matchMedia(MEDIA_QUERY).matches;\n  } catch {\n    return false;\n  }\n}\n\nfunction resolveTheme(pref: ThemePreference, systemDark: boolean): ResolvedTheme {\n  return pref === \"system\" ? (systemDark ? \"dark\" : \"light\") : pref;\n}\n\nfunction applyToDOM(theme: ResolvedTheme): void {\n  try {\n    document.documentElement.setAttribute(DATA_ATTR, theme);\n  } catch {\n    // document may be unavailable (SSR).\n  }\n}\n\nfunction persist(preference: ThemePreference): void {\n  try {\n    localStorage.setItem(STORAGE_KEY, preference);\n  } catch {\n    // localStorage may be unavailable.\n  }\n}\n\n// --- Public API ---------------------------------------------------------\n\n/**\n * Read and control the active Loom theme.\n *\n * Call it from a component `setup()` or inside an `effectScope()` — that\n * scope is what releases the shared state when its last real consumer\n * unmounts. A call from outside any effect scope still works, but it can\n * never be released, so it is not counted and development warns once; the\n * shared state simply lives as long as whatever creates it next counts for.\n * The DOM-apply and persistence side effects are created once per app in a\n * detached scope of their own — never once per consumer — and storage is\n * only written when the stored preference actually changes.\n *\n * @example\n * ```vue\n * <script setup>\n * import { useTheme } from \"@ecoma-io/loom/theme\"\n * const { theme, resolvedTheme, setTheme, toggleTheme } = useTheme()\n * </script>\n *\n * <template>\n *   <button @click=\"toggleTheme\">\n *     {{ resolvedTheme === \"dark\" ? \"☀️\" : \"🌙\" }}\n *   </button>\n * </template>\n * ```\n */\nexport function useTheme(): {\n  readonly theme: Ref<ThemePreference>;\n  readonly resolvedTheme: Readonly<Ref<ResolvedTheme>>;\n  readonly setTheme: (preference: ThemePreference) => void;\n  readonly toggleTheme: () => void;\n} {\n  const state = getSharedState();\n\n  // Clean up the shared state when the consuming scope disposes. Only a call\n  // from inside an active scope is registered — and only such a call was\n  // counted by `getSharedState()` in the first place; outside one,\n  // `onScopeDispose` would silently do nothing and the count would never\n  // come back down.\n  if (getCurrentScope() !== undefined) onScopeDispose(releaseSharedState);\n\n  /** The user's preference — `\"system\"` defers to the OS. */\n  const theme = computed<ThemePreference>({\n    get: () => state.preference.value,\n    set: (value: ThemePreference) => {\n      state.preference.value = value;\n    },\n  });\n\n  /** The actual active theme, with `\"system\"` resolved to `\"light\"` or `\"dark\"`. */\n  const resolvedTheme = computed<ResolvedTheme>(() =>\n    resolveTheme(state.preference.value, state.systemIsDark.value),\n  );\n\n  /** Set the theme preference explicitly. */\n  function setTheme(preference: ThemePreference): void {\n    state.preference.value = preference;\n  }\n\n  /** Toggle between light and dark. System preference stays system. */\n  function toggleTheme(): void {\n    if (state.preference.value === \"system\") {\n      // Toggle the resolved theme and lock to it, so the user can override\n      // the OS preference with one click.\n      state.preference.value = resolvedTheme.value === \"dark\" ? \"light\" : \"dark\";\n    } else {\n      state.preference.value = state.preference.value === \"dark\" ? \"light\" : \"dark\";\n    }\n  }\n\n  return { theme, resolvedTheme, setTheme, toggleTheme } as const;\n}\n\n/**\n * Inline script to prevent flash-of-wrong-theme on SSR pages.\n *\n * Paste it into `<head>` before any stylesheet links:\n *\n * ```html\n * <script><%= themeScript %></script>\n * ```\n *\n * It reads `localStorage` and sets `data-theme` on `<html>` synchronously,\n * before the browser paints, so the first frame is already in the right\n * theme. When no preference is stored, it follows the OS preference.\n *\n * The script is deliberately tiny and has no dependencies.\n */\nexport const themeScript = `(() => {\n  const t = localStorage.getItem(\"${STORAGE_KEY}\");\n  const d = window.matchMedia(\"${MEDIA_QUERY}\").matches;\n  document.documentElement.setAttribute(\"${DATA_ATTR}\", (t === \"dark\" || (!t && d)) ? \"dark\" : \"light\");\n})()`;\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AA2BA,IAAM,cAAc;AACpB,IAAM,YAAY;AAClB,IAAM,cAAc;;AAGpB,IAAM,qBAAsC;;;;;;;AAkC5C,IAAI,cAAiC;;AAGrC,IAAI,qBAAqB;AAiBzB,SAAS,iBAA6B;CAOpC,MAAM,SAAS,gBAAgB,MAAM,KAAA;CACrC,IAAI,CAAC,UAAU,CAAC,oBAAoB;EAClC,qBAAqB;EACrB,QAAQ,KACN,yJACF;CACF;CAEA,IAAI,aAAa;EACf,IAAI,QAAQ,YAAY;EACxB,OAAO;CACT;CAGA,IAAI,SAA0B;CAC9B,IAAI;EACF,MAAM,MAAM,aAAa,QAAQ,WAAW;EAC5C,IAAI,QAAQ,WAAW,QAAQ,UAAU,QAAQ,UAC/C,SAAS;CAEb,QAAQ,CAER;CAIA,WADgB,aAAa,QAAQ,gBAAgB,CAC1C,CAAO;CAElB,MAAM,aAAa,IAAqB,MAAM;CAC9C,MAAM,eAAe,IAAa,gBAAgB,CAAC;CAGnD,IAAI,aAAoC;CACxC,IAAI,WAAsD;CAE1D,IAAI;EACF,aAAa,OAAO,WAAW,WAAW;EAC1C,YAAY,MAA2B;GACrC,aAAa,QAAQ,EAAE;EACzB;EACA,WAAW,iBAAiB,UAAU,QAAQ;CAChD,QAAQ,CAER;CAEA,MAAM,QAAQ,IAAI,YAAY,IAAI;CAClC,MAAM,QAAoB;EACxB;EACA;EACA;EACA;EACA,YAAY,SAAS,IAAI;EACzB;EACA,eAAe;CACjB;CACA,cAAc;CAMd,MAAM,UAAU;EACd,MAAM,CAAC,YAAY,YAAY,SAAS;GAGtC,WAAW,aAAa,WAAW,OAAO,aAAa,KAAK,CAAC;GAC7D,IAAI,WAAW,UAAU,MAAM,eAAe;IAC5C,MAAM,gBAAgB,WAAW;IACjC,QAAQ,MAAM,aAAa;GAC7B;EACF,CAAC;CACH,CAAC;CAED,OAAO;AACT;AAEA,SAAS,qBAA2B;CAClC,IAAI,CAAC,aAAa;CAClB,YAAY;CACZ,IAAI,YAAY,aAAa,GAAG;CAGhC,YAAY,MAAM,KAAK;CACvB,IAAI,YAAY,cAAc,YAAY,UACxC,YAAY,WAAW,oBAAoB,UAAU,YAAY,QAAQ;CAE3E,cAAc;AAChB;AAIA,SAAS,kBAA2B;CAClC,IAAI;EACF,OAAO,OAAO,WAAW,WAAW,CAAC,CAAC;CACxC,QAAQ;EACN,OAAO;CACT;AACF;AAEA,SAAS,aAAa,MAAuB,YAAoC;CAC/E,OAAO,SAAS,WAAY,aAAa,SAAS,UAAW;AAC/D;AAEA,SAAS,WAAW,OAA4B;CAC9C,IAAI;EACF,SAAS,gBAAgB,aAAa,WAAW,KAAK;CACxD,QAAQ,CAER;AACF;AAEA,SAAS,QAAQ,YAAmC;CAClD,IAAI;EACF,aAAa,QAAQ,aAAa,UAAU;CAC9C,QAAQ,CAER;AACF;;;;;;;;;;;;;;;;;;;;;;;;;;;AA8BA,SAAgB,WAKd;CACA,MAAM,QAAQ,eAAe;CAO7B,IAAI,gBAAgB,MAAM,KAAA,GAAW,eAAe,kBAAkB;;CAGtE,MAAM,QAAQ,SAA0B;EACtC,WAAW,MAAM,WAAW;EAC5B,MAAM,UAA2B;GAC/B,MAAM,WAAW,QAAQ;EAC3B;CACF,CAAC;;CAGD,MAAM,gBAAgB,eACpB,aAAa,MAAM,WAAW,OAAO,MAAM,aAAa,KAAK,CAC/D;;CAGA,SAAS,SAAS,YAAmC;EACnD,MAAM,WAAW,QAAQ;CAC3B;;CAGA,SAAS,cAAoB;EAC3B,IAAI,MAAM,WAAW,UAAU,UAG7B,MAAM,WAAW,QAAQ,cAAc,UAAU,SAAS,UAAU;OAEpE,MAAM,WAAW,QAAQ,MAAM,WAAW,UAAU,SAAS,UAAU;CAE3E;CAEA,OAAO;EAAE;EAAO;EAAe;EAAU;CAAY;AACvD;;;;;;;;;;;;;;;;AAiBA,IAAa,cAAc;oCACS,YAAY;iCACf,YAAY;2CACF,UAAU"}

package/dist/packages/labels/src/ancestor-disabled.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ancestor-disabled.js","names":[],"sources":["../../../../packages/labels/src/ancestor-disabled.ts"],"sourcesContent":["import { onScopeDispose, readonly, ref, watchPostEffect, type Ref } from \"vue\";\n\n/**\n * Whether an enclosing `<fieldset disabled>` has made this control unavailable\n * — read off the element itself, not off anything a wrapper told us.\n *\n * The platform already answers this for `<input>`, `<button>`, `<select>` and\n * `<textarea>`: a disabled fieldset makes every such descendant *actually\n * disabled*, so `:disabled` matches, the tab stop goes and the control refuses\n * input. Nothing in Loom has to help — native roots inherit a fieldset's\n * disabling and composites call this composable instead, which is the house\n * rule stated in CONTRIBUTING.md's accessibility section.\n *\n * That answer stops at the boundary of that short list,\n * and Reka builds several controls out of elements that are not on it — a\n * `<span role=\"slider\">`, a `<div role=\"spinbutton\">`. Those keep their\n * `tabindex=\"0\"` and their arrow-key handlers inside a disabled group: measured\n * in jsdom, a Slider in a `<fieldset disabled>` still took Home/End and moved\n * its value, and a DatePicker segment still typed. A control that looks\n * unavailable and still answers the keyboard is worse than one that looks\n * available, so the appearance cannot be fixed on its own.\n *\n * **This is a read of the native attribute, not a second copy of it.**\n * `Fieldset.vue`'s docblock rules out publishing `disabled` through the Field\n * context, and the reason is precedence: a context is a claim a control may\n * beat with `:disabled=\"false\"`, while the native attribute disables it anyway,\n * leaving a control that renders enabled and silently refuses input. Nothing\n * here can drift that way, because there is nothing to beat — the answer is\n * recomputed from the same DOM the browser is reading, so a control cannot\n * disagree with the fieldset it is standing in. It also needs no Loom wrapper\n * at all: a raw `<fieldset disabled>` a consumer wrote works exactly as one of\n * ours does.\n *\n * The result is `false` on the server and until the effect first runs, which is\n * deliberate. `watchPostEffect` does not run during SSR, so the markup a server\n * emits matches the markup the client hydrates and the state settles in the\n * same tick as mount — a hydration-time correction rather than a mismatch.\n */\nexport function useAncestorDisabled(\n  target: () => Element | null | undefined,\n): Readonly<Ref<boolean>> {\n  const disabled = ref(false);\n\n  // Kept rather than chained off the constructor: an observer holds a strong\n  // reference to everything it watches, and `disconnect()` is the only thing\n  // that releases them.\n  let observer: MutationObserver | undefined;\n\n  function sync(): void {\n    const start = target();\n    if (!start) {\n      observer?.disconnect();\n      disabled.value = false;\n      return;\n    }\n\n    const fieldsets = enclosingFieldsets(start);\n    observer ??= new MutationObserver(sync);\n    // Re-observed wholesale rather than diffed. The set is an element's\n    // ancestor fieldsets — one or two of them in any real form — and the\n    // attribute filter means nothing else in the document wakes this up.\n    observer.disconnect();\n    for (const fieldset of fieldsets) {\n      observer.observe(fieldset, { attributes: true, attributeFilter: [\"disabled\"] });\n    }\n\n    disabled.value = fieldsets.some((fieldset) => fieldset.disabled);\n  }\n\n  watchPostEffect(sync);\n  onScopeDispose(() => {\n    observer?.disconnect();\n  });\n\n  return readonly(disabled);\n}\n\n/**\n * The `<fieldset>` ancestors whose `disabled` would reach `start`, outermost\n * last, whether or not any of them currently carries the attribute — they are\n * what has to be watched for the attribute arriving.\n *\n * The walk climbs child-by-child rather than calling `closest(\"fieldset\")`\n * because of the exemption in the \"actually disabled\" rule: controls inside a\n * disabled fieldset's **first** `<legend>` stay available, which is what makes\n * a switch in the legend that re-enables its own group possible. Reaching a\n * fieldset through that legend is reaching a fieldset that does not disable\n * you, so it is skipped — and the walk continues past it, since a fieldset\n * further out may still disable the legend itself.\n */\nfunction enclosingFieldsets(start: Element): HTMLFieldSetElement[] {\n  const found: HTMLFieldSetElement[] = [];\n  let node: Element | null = start;\n\n  while (node) {\n    const parent: Element | null = node.parentElement;\n    if (parent instanceof HTMLFieldSetElement && node !== parent.querySelector(\":scope > legend\")) {\n      found.push(parent);\n    }\n    node = parent;\n  }\n\n  return found;\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAsCA,SAAgB,oBACd,QACwB;CACxB,MAAM,WAAW,IAAI,KAAK;CAK1B,IAAI;CAEJ,SAAS,OAAa;EACpB,MAAM,QAAQ,OAAO;EACrB,IAAI,CAAC,OAAO;GACV,UAAU,WAAW;GACrB,SAAS,QAAQ;GACjB;EACF;EAEA,MAAM,YAAY,mBAAmB,KAAK;EAC1C,aAAa,IAAI,iBAAiB,IAAI;EAItC,SAAS,WAAW;EACpB,KAAK,MAAM,YAAY,WACrB,SAAS,QAAQ,UAAU;GAAE,YAAY;GAAM,iBAAiB,CAAC,UAAU;EAAE,CAAC;EAGhF,SAAS,QAAQ,UAAU,MAAM,aAAa,SAAS,QAAQ;CACjE;CAEA,gBAAgB,IAAI;CACpB,qBAAqB;EACnB,UAAU,WAAW;CACvB,CAAC;CAED,OAAO,SAAS,QAAQ;AAC1B;;;;;;;;;;;;;;AAeA,SAAS,mBAAmB,OAAuC;CACjE,MAAM,QAA+B,CAAC;CACtC,IAAI,OAAuB;CAE3B,OAAO,MAAM;EACX,MAAM,SAAyB,KAAK;EACpC,IAAI,kBAAkB,uBAAuB,SAAS,OAAO,cAAc,iBAAiB,GAC1F,MAAM,KAAK,MAAM;EAEnB,OAAO;CACT;CAEA,OAAO;AACT"}

package/dist/packages/labels/src/count-labels.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"count-labels.js","names":[],"sources":["../../../../packages/labels/src/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"}