@ecoma-io/loom 0.2.0 → 0.4.0

package/dist/layouts/MasterDetail/MasterDetail.vue_vue_type_script_setup_true_lang.js

@@ -1,42 +0,0 @@
-import { cn } from "../../lib/cn.js";
-import { createElementBlock, createElementVNode, defineComponent, normalizeClass, normalizeStyle, openBlock, renderSlot, unref } from "vue";
-//#region src/layouts/MasterDetail/MasterDetail.vue?vue&type=script&setup=true&lang.ts
-var gapClass = {
-	sm: "gap-2 sm:gap-3",
-	md: "gap-3 sm:gap-4",
-	lg: "gap-4 sm:gap-6"
-};
-var MasterDetail_vue_vue_type_script_setup_true_lang_default = /*@__PURE__*/ defineComponent({
-	__name: "MasterDetail",
-	props: {
-		minMasterWidth: { default: "14rem" },
-		gap: { default: "none" }
-	},
-	setup(__props) {
-		return (_ctx, _cache) => {
-			return openBlock(), createElementBlock("div", {
-				class: normalizeClass(unref(cn)("flex h-full", __props.gap !== "none" ? gapClass[__props.gap] : void 0)),
-				style: { flexWrap: "wrap" }
-			}, [createElementVNode("div", {
-				style: normalizeStyle({
-					flexBasis: __props.minMasterWidth,
-					flexGrow: 0,
-					flexShrink: 0
-				}),
-				class: normalizeClass(unref(cn)("bg-sunken w-full"))
-			}, [renderSlot(_ctx.$slots, "master")], 6), createElementVNode("div", {
-				style: {
-					flexBasis: 0,
-					flexGrow: 999,
-					flexShrink: 1,
-					minWidth: "50%"
-				},
-				class: normalizeClass(unref(cn)("bg-background overflow-y-auto px-4 sm:px-6 3xl:px-8"))
-			}, [renderSlot(_ctx.$slots, "default")], 2)], 2);
-		};
-	}
-});
-//#endregion
-export { MasterDetail_vue_vue_type_script_setup_true_lang_default as default, gapClass };
-
-//# sourceMappingURL=MasterDetail.vue_vue_type_script_setup_true_lang.js.map

package/dist/layouts/MasterDetail/MasterDetail.vue_vue_type_script_setup_true_lang.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"MasterDetail.vue_vue_type_script_setup_true_lang.js","names":[],"sources":["../../../src/layouts/MasterDetail/MasterDetail.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * MasterDetail — a master list panel and a detail panel side by side.\n *\n * The master/detail pattern is the layout that list-driven applications reach\n * for: a selectable list on one side, its content on the other. Mail clients,\n * file browsers, and settings pages all share this structure.\n *\n * The intrinsic collapse from the Split composition primitive is reused directly\n * — `flex-wrap` plus a `min-width: 50%` guard on the detail panel — so the\n * layout derives its own breakpoint from the container's width rather than a\n * viewport media query. Below the collapse width the panels stack vertically;\n * the master list sits above the detail area.\n *\n * The master panel does not shrink (`flex-shrink: 0`), unlike the AppShell\n * sidebar, because a master list whose column widths change under compression\n * is harder to scan than one that holds its shape and lets the detail panel\n * absorb the squeeze. The detail panel scrolls independently so long lists of\n * content never push the master list off-screen.\n */\nexport type MasterDetailMinMasterWidth = string;\n\nexport type MasterDetailGap = \"sm\" | \"md\" | \"lg\" | \"none\";\n\nconst gapClass: Record<Exclude<MasterDetailGap, \"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 \"../../lib/cn\";\n\nwithDefaults(\n  defineProps<{\n    /** Minimum width for the master panel (e.g. \"14rem\"). The detail area takes the rest. */\n    minMasterWidth?: MasterDetailMinMasterWidth;\n    /** Gap between master and detail panels. Tightens one notch below sm. */\n    gap?: MasterDetailGap;\n  }>(),\n  { minMasterWidth: \"14rem\", gap: \"none\" },\n);\n</script>\n\n<template>\n  <!--\n    `flex-wrap: wrap` is the intrinsic collapse mechanism. When the detail\n    panel cannot honour its `min-width: 50%`, both panels wrap to full-width —\n    the master list sits above the detail area. No media query; the layout\n    derives its own breakpoint from the container's width.\n  -->\n  <div\n    :class=\"cn('flex h-full', gap !== 'none' ? gapClass[gap] : undefined)\"\n    :style=\"{ flexWrap: 'wrap' }\"\n  >\n    <!--\n      The master panel holds a fixed basis and does not grow or shrink. It sits\n      on the sunken elevation so the detail area reads as the work surface\n      lifted above navigation chrome.\n    -->\n    <div\n      :style=\"{\n        flexBasis: minMasterWidth,\n        flexGrow: 0,\n        flexShrink: 0,\n      }\"\n      :class=\"cn('bg-sunken w-full')\"\n    >\n      <slot name=\"master\" />\n    </div>\n\n    <!--\n      The detail panel takes all remaining space (`flex-grow: 999`) when the\n      container is wide enough. Its `min-width: 50%` triggers wrapping below\n      tablet-like widths. It scrolls independently so long content never pushes\n      the master list off-screen. Gutters widen at wider breakpoints so\n      ultrawide viewports add whitespace rails rather than stretching lines.\n    -->\n    <div\n      :style=\"{\n        flexBasis: 0,\n        flexGrow: 999,\n        flexShrink: 1,\n        minWidth: '50%',\n      }\"\n      :class=\"cn('bg-background overflow-y-auto px-4 sm:px-6 3xl:px-8')\"\n    >\n      <slot />\n    </div>\n  </div>\n</template>\n"],"mappings":";;;AAwBA,IAAM,WAA6D;CACjE,IAAI;CACJ,IAAI;CACJ,IAAI;AACN;;;;;;;;;GA0BE,OAAA,UAAA,GAAA,mBAsCM,OAAA;IArCH,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,eAAgB,QAAA,QAAG,SAAc,SAAS,QAAA,OAAO,KAAA,CAAS,CAAA;IACnE,OAAO,EAAA,UAAA,OAAA;GAOR,GAAA,CAAA,mBASM,OAAA;IARH,OAAK,eAAA;KAAuB,WAAA,QAAA;;;;IAK5B,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,kBAAA,CAAA;GAEV,GAAA,CAAA,WAAsB,KAAA,QAAA,QAAA,CAAA,GAAA,CAAA,GAUxB,mBAUM,OAAA;IATH,OAAO;;;;;IAKP;IACA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,qDAAA,CAAA;GAEV,GAAA,CAAA,WAAQ,KAAA,QAAA,SAAA,CAAA,GAAA,CAAA,CAAA,GAAA,CAAA"}

package/dist/layouts/Reading/Reading.js

@@ -1,7 +0,0 @@
-import Reading_vue_vue_type_script_setup_true_lang_default from "./Reading.vue_vue_type_script_setup_true_lang.js";
-//#region src/layouts/Reading/Reading.vue
-var Reading_default = Reading_vue_vue_type_script_setup_true_lang_default;
-//#endregion
-export { Reading_default as default };
-
-//# sourceMappingURL=Reading.js.map

package/dist/layouts/Reading/Reading.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Reading.js","names":[],"sources":["../../../src/layouts/Reading/Reading.vue"],"sourcesContent":["<script setup lang=\"ts\">\nimport { cn } from \"../../lib/cn\";\n\nwithDefaults(\n  defineProps<{\n    /** Whether to add horizontal gutters that widen at wider breakpoints. */\n    gutter?: boolean;\n  }>(),\n  { gutter: true },\n);\n</script>\n\n<template>\n  <!--\n    Reading — a long-form reading layout that caps the content area at a\n    comfortable line length (~65ch). The header and footer span full-width\n    (site chrome, navigation, copyright), while only the reading content is\n    constrained to `max-w-prose` — the width that research identifies as the\n    fastest for sustained reading. Extra viewport on ultrawide monitors goes\n    to intentional whitespace, never to stretching lines.\n\n    The content wrapper is always prose-width with no prop: this layout exists\n    to enforce that cap. A reading layout that can go full-width is not a\n    reading layout. The `gutter` prop controls horizontal padding, not width.\n  -->\n  <div :class=\"cn('min-h-dvh flex flex-col')\">\n    <header v-if=\"$slots.header\" :class=\"cn(gutter ? 'px-4 sm:px-6 3xl:px-8' : undefined)\">\n      <slot name=\"header\" />\n    </header>\n\n    <div\n      :class=\"\n        cn(\n          'mx-auto w-full max-w-prose flex-1',\n          gutter ? 'px-4 sm:px-6 3xl:px-8' : undefined,\n          'py-8 sm:py-12',\n        )\n      \"\n    >\n      <slot />\n    </div>\n\n    <footer v-if=\"$slots.footer\" :class=\"cn(gutter ? 'px-4 sm:px-6 3xl:px-8' : undefined)\">\n      <slot name=\"footer\" />\n    </footer>\n  </div>\n</template>\n"],"mappings":""}

package/dist/layouts/Reading/Reading.vue.d.ts

@@ -1,24 +0,0 @@
-type __VLS_Props = {
-    /** Whether to add horizontal gutters that widen at wider breakpoints. */
-    gutter?: boolean;
-};
-declare var __VLS_1: {}, __VLS_3: {}, __VLS_5: {};
-type __VLS_Slots = {} & {
-    header?: (props: typeof __VLS_1) => any;
-} & {
-    default?: (props: typeof __VLS_3) => any;
-} & {
-    footer?: (props: typeof __VLS_5) => any;
-};
-declare const __VLS_base: import("vue").DefineComponent<__VLS_Props, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<__VLS_Props> & Readonly<{}>, {
-    gutter: boolean;
-}, {}, {}, {}, string, import("vue").ComponentProvideOptions, false, {}, any>;
-declare const __VLS_export: __VLS_WithSlots<typeof __VLS_base, __VLS_Slots>;
-declare const _default: typeof __VLS_export;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};
-//# sourceMappingURL=Reading.vue.d.ts.map

package/dist/layouts/Reading/Reading.vue.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"Reading.vue.d.ts","sourceRoot":"","sources":["../../../src/layouts/Reading/Reading.vue"],"names":[],"mappings":"AAoDA,KAAK,WAAW,GAAG;IACf,yEAAyE;IACzE,MAAM,CAAC,EAAE,OAAO,CAAC;CAClB,CAAC;AAqDJ,QAAA,IAAI,OAAO,IAAU,EAAE,OAAO,IAAU,EAAE,OAAO,IAAW,CAAE;AAC9D,KAAK,WAAW,GAAG,EAAE,GACnB;IAAE,MAAM,CAAC,EAAE,CAAC,KAAK,EAAE,OAAO,OAAO,KAAK,GAAG,CAAA;CAAE,GAC3C;IAAE,OAAO,CAAC,EAAE,CAAC,KAAK,EAAE,OAAO,OAAO,KAAK,GAAG,CAAA;CAAE,GAC5C;IAAE,MAAM,CAAC,EAAE,CAAC,KAAK,EAAE,OAAO,OAAO,KAAK,GAAG,CAAA;CAAE,CAAC;AAK9C,QAAA,MAAM,UAAU;YA/DH,OAAO;6EAkElB,CAAC;AACH,QAAA,MAAM,YAAY,EAAS,eAAe,CAAC,OAAO,UAAU,EAAE,WAAW,CAAC,CAAC;wBACtD,OAAO,YAAY;AAAxC,wBAAyC;AAWzC,KAAK,eAAe,CAAC,CAAC,EAAE,CAAC,IAAI,CAAC,GAAG;IAChC,QAAO;QACN,MAAM,EAAE,CAAC,CAAC;KACV,CAAA;CACD,CAAC"}

package/dist/layouts/Reading/Reading.vue_vue_type_script_setup_true_lang.js

@@ -1,29 +0,0 @@
-import { cn } from "../../lib/cn.js";
-import { createCommentVNode, createElementBlock, createElementVNode, defineComponent, normalizeClass, openBlock, renderSlot, unref } from "vue";
-//#region src/layouts/Reading/Reading.vue?vue&type=script&setup=true&lang.ts
-var Reading_vue_vue_type_script_setup_true_lang_default = /*@__PURE__*/ defineComponent({
-	__name: "Reading",
-	props: { gutter: {
-		type: Boolean,
-		default: true
-	} },
-	setup(__props) {
-		return (_ctx, _cache) => {
-			return openBlock(), createElementBlock("div", { class: normalizeClass(unref(cn)("min-h-dvh flex flex-col")) }, [
-				_ctx.$slots.header ? (openBlock(), createElementBlock("header", {
-					key: 0,
-					class: normalizeClass(unref(cn)(__props.gutter ? "px-4 sm:px-6 3xl:px-8" : void 0))
-				}, [renderSlot(_ctx.$slots, "header")], 2)) : createCommentVNode("", true),
-				createElementVNode("div", { class: normalizeClass(unref(cn)("mx-auto w-full max-w-prose flex-1", __props.gutter ? "px-4 sm:px-6 3xl:px-8" : void 0, "py-8 sm:py-12")) }, [renderSlot(_ctx.$slots, "default")], 2),
-				_ctx.$slots.footer ? (openBlock(), createElementBlock("footer", {
-					key: 1,
-					class: normalizeClass(unref(cn)(__props.gutter ? "px-4 sm:px-6 3xl:px-8" : void 0))
-				}, [renderSlot(_ctx.$slots, "footer")], 2)) : createCommentVNode("", true)
-			], 2);
-		};
-	}
-});
-//#endregion
-export { Reading_vue_vue_type_script_setup_true_lang_default as default };
-
-//# sourceMappingURL=Reading.vue_vue_type_script_setup_true_lang.js.map

package/dist/layouts/Reading/Reading.vue_vue_type_script_setup_true_lang.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Reading.vue_vue_type_script_setup_true_lang.js","names":["$slots"],"sources":["../../../src/layouts/Reading/Reading.vue"],"sourcesContent":["<script setup lang=\"ts\">\nimport { cn } from \"../../lib/cn\";\n\nwithDefaults(\n  defineProps<{\n    /** Whether to add horizontal gutters that widen at wider breakpoints. */\n    gutter?: boolean;\n  }>(),\n  { gutter: true },\n);\n</script>\n\n<template>\n  <!--\n    Reading — a long-form reading layout that caps the content area at a\n    comfortable line length (~65ch). The header and footer span full-width\n    (site chrome, navigation, copyright), while only the reading content is\n    constrained to `max-w-prose` — the width that research identifies as the\n    fastest for sustained reading. Extra viewport on ultrawide monitors goes\n    to intentional whitespace, never to stretching lines.\n\n    The content wrapper is always prose-width with no prop: this layout exists\n    to enforce that cap. A reading layout that can go full-width is not a\n    reading layout. The `gutter` prop controls horizontal padding, not width.\n  -->\n  <div :class=\"cn('min-h-dvh flex flex-col')\">\n    <header v-if=\"$slots.header\" :class=\"cn(gutter ? 'px-4 sm:px-6 3xl:px-8' : undefined)\">\n      <slot name=\"header\" />\n    </header>\n\n    <div\n      :class=\"\n        cn(\n          'mx-auto w-full max-w-prose flex-1',\n          gutter ? 'px-4 sm:px-6 3xl:px-8' : undefined,\n          'py-8 sm:py-12',\n        )\n      \"\n    >\n      <slot />\n    </div>\n\n    <footer v-if=\"$slots.footer\" :class=\"cn(gutter ? 'px-4 sm:px-6 3xl:px-8' : undefined)\">\n      <slot name=\"footer\" />\n    </footer>\n  </div>\n</template>\n"],"mappings":";;;;;;;;;;;GAyBE,OAAA,UAAA,GAAA,mBAoBM,OAAA,EApBA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,yBAAA,CAAA,EAAA,GAAA;IACCA,KAAAA,OAAO,UAArB,UAAA,GAAA,mBAES,UAAA;;KAFqB,OAAK,eAAE,MAAA,EAAA,CAAE,CAAC,QAAA,SAAM,0BAA6B,KAAA,CAAS,CAAA;IAClF,GAAA,CAAA,WAAsB,KAAA,QAAA,QAAA,CAAA,GAAA,CAAA,KAAA,mBAAA,IAAA,IAAA;IAGxB,mBAUM,OAAA,EATH,OAAK,eAAW,MAAA,EAAA,CAAE,CAAA,qCAA2D,QAAA,SAAM,0BAA6B,KAAA,GAAA,eAAA,CAAA,EAAA,GAAA,CAQjH,WAAQ,KAAA,QAAA,SAAA,CAAA,GAAA,CAAA;IAGIA,KAAAA,OAAO,UAArB,UAAA,GAAA,mBAES,UAAA;;KAFqB,OAAK,eAAE,MAAA,EAAA,CAAE,CAAC,QAAA,SAAM,0BAA6B,KAAA,CAAS,CAAA;IAClF,GAAA,CAAA,WAAsB,KAAA,QAAA,QAAA,CAAA,GAAA,CAAA,KAAA,mBAAA,IAAA,IAAA"}

package/dist/layouts/Settings/Settings.js

@@ -1,7 +0,0 @@
-import Settings_vue_vue_type_script_setup_true_lang_default from "./Settings.vue_vue_type_script_setup_true_lang.js";
-//#region src/layouts/Settings/Settings.vue
-var Settings_default = Settings_vue_vue_type_script_setup_true_lang_default;
-//#endregion
-export { Settings_default as default };
-
-//# sourceMappingURL=Settings.js.map

package/dist/layouts/Settings/Settings.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Settings.js","names":[],"sources":["../../../src/layouts/Settings/Settings.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * Settings — a settings/preferences page layout: navigation sidebar + content\n * sections.\n *\n * The layout uses the same intrinsic flex-wrap collapse as the Sidebar\n * composition primitive. The nav panel gets a fixed flex-basis and the content\n * area gets `flex-grow: 999`, so when the container cannot fit the content's\n * `min-width: 50%`, both panels wrap to full-width — the nav stacks above the\n * content. No media query, no JavaScript — the layout derives its own\n * breakpoint from the container's width.\n *\n * The nav panel recedes into the sunken elevation layer so the content reads as\n * the work surface. The content area scrolls independently so long settings\n * pages stay navigable without the nav scrolling out of view.\n */\nexport type SettingsNavWidth = string;\n</script>\n\n<script setup lang=\"ts\">\nimport { cn } from \"../../lib/cn\";\n\nwithDefaults(\n  defineProps<{\n    /** Width for the navigation panel (e.g. \"12rem\"). */\n    navWidth?: SettingsNavWidth;\n  }>(),\n  { navWidth: \"12rem\" },\n);\n</script>\n\n<template>\n  <div :class=\"cn('min-h-dvh flex flex-col')\">\n    <!--\n      The header is full-width and above the nav+content row, so a title bar\n      or breadcrumb never competes for horizontal space with the nav panel.\n    -->\n    <header v-if=\"$slots.header\">\n      <slot name=\"header\" />\n    </header>\n\n    <!--\n      `flex-wrap: wrap` is the intrinsic collapse mechanism. When the content\n      panel can't fit its `min-width: 50%`, both panels wrap to full-width —\n      the nav becomes a full-width section above the content. No media query;\n      the layout derives its own breakpoint from the container's width.\n    -->\n    <div :class=\"cn('flex flex-1 flex-row')\" :style=\"{ flexWrap: 'wrap' }\">\n      <!--\n        The nav panel: fixed-basis, no growth, no shrink. It does not yield\n        width to the content area — when the container is too narrow, it wraps\n        to full-width instead of compressing. Sunken elevation marks it as\n        chrome, not work surface.\n      -->\n      <nav\n        :style=\"{\n          flexBasis: navWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n        }\"\n        :class=\"cn('bg-sunken w-full p-2')\"\n      >\n        <slot name=\"nav\" />\n      </nav>\n\n      <!--\n        The content area takes all remaining space (`flex-grow: 999`) when the\n        container is wide enough. Its `min-width: 50%` triggers wrapping below\n        tablet-like widths. It scrolls independently so long settings pages\n        stay navigable without the nav scrolling out of view. Gutters widen at\n        wider breakpoints so ultrawide viewports add whitespace rails rather\n        than stretching lines.\n      -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n        :class=\"cn('bg-background min-w-0 flex-1 overflow-y-auto px-4 sm:px-6 3xl:px-8')\"\n      >\n        <slot />\n      </div>\n    </div>\n  </div>\n</template>\n"],"mappings":""}

package/dist/layouts/Settings/Settings.vue.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"Settings.vue.d.ts","sourceRoot":"","sources":["../../../src/layouts/Settings/Settings.vue"],"names":[],"mappings":"AA6FA;;;;;;;;;;;;;;GAcG;AACH,MAAM,MAAM,gBAAgB,GAAG,MAAM,CAAC;wBACjB,OAAO,YAAY;AAAxC,wBAAyC;AACzC,QAAA,MAAM,YAAY;IAEd,qDAAqD;eAC1C,gBAAgB;;IAD3B,qDAAqD;eAC1C,gBAAgB;;cAAhB,gBAAgB;;aA8DlB,CAAC,KAAK,IAAgB,KAAK,GAAG;;UACjC,CAAC,KAAK,IAAgB,KAAK,GAAG;;cAC1B,CAAC,KAAK,IAAgB,KAAK,GAAG;EAUxC,CAAC;AAWL,KAAK,eAAe,CAAC,CAAC,EAAE,CAAC,IAAI,CAAC,GAAG;IAChC,QAAO;QACN,MAAM,EAAE,CAAC,CAAC;KACV,CAAA;CACD,CAAC"}

package/dist/layouts/Settings/Settings.vue_vue_type_script_setup_true_lang.js

@@ -1,35 +0,0 @@
-import { cn } from "../../lib/cn.js";
-import { createCommentVNode, createElementBlock, createElementVNode, defineComponent, normalizeClass, normalizeStyle, openBlock, renderSlot, unref } from "vue";
-//#region src/layouts/Settings/Settings.vue?vue&type=script&setup=true&lang.ts
-var _hoisted_1 = { key: 0 };
-var Settings_vue_vue_type_script_setup_true_lang_default = /*@__PURE__*/ defineComponent({
-	__name: "Settings",
-	props: { navWidth: { default: "12rem" } },
-	setup(__props) {
-		return (_ctx, _cache) => {
-			return openBlock(), createElementBlock("div", { class: normalizeClass(unref(cn)("min-h-dvh flex flex-col")) }, [_ctx.$slots.header ? (openBlock(), createElementBlock("header", _hoisted_1, [renderSlot(_ctx.$slots, "header")])) : createCommentVNode("", true), createElementVNode("div", {
-				class: normalizeClass(unref(cn)("flex flex-1 flex-row")),
-				style: { flexWrap: "wrap" }
-			}, [createElementVNode("nav", {
-				style: normalizeStyle({
-					flexBasis: __props.navWidth,
-					flexGrow: 0,
-					flexShrink: 0
-				}),
-				class: normalizeClass(unref(cn)("bg-sunken w-full p-2"))
-			}, [renderSlot(_ctx.$slots, "nav")], 6), createElementVNode("div", {
-				style: {
-					flexBasis: 0,
-					flexGrow: 999,
-					flexShrink: 1,
-					minWidth: "50%"
-				},
-				class: normalizeClass(unref(cn)("bg-background min-w-0 flex-1 overflow-y-auto px-4 sm:px-6 3xl:px-8"))
-			}, [renderSlot(_ctx.$slots, "default")], 2)], 2)], 2);
-		};
-	}
-});
-//#endregion
-export { Settings_vue_vue_type_script_setup_true_lang_default as default };
-
-//# sourceMappingURL=Settings.vue_vue_type_script_setup_true_lang.js.map

package/dist/layouts/Settings/Settings.vue_vue_type_script_setup_true_lang.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"Settings.vue_vue_type_script_setup_true_lang.js","names":["$slots"],"sources":["../../../src/layouts/Settings/Settings.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * Settings — a settings/preferences page layout: navigation sidebar + content\n * sections.\n *\n * The layout uses the same intrinsic flex-wrap collapse as the Sidebar\n * composition primitive. The nav panel gets a fixed flex-basis and the content\n * area gets `flex-grow: 999`, so when the container cannot fit the content's\n * `min-width: 50%`, both panels wrap to full-width — the nav stacks above the\n * content. No media query, no JavaScript — the layout derives its own\n * breakpoint from the container's width.\n *\n * The nav panel recedes into the sunken elevation layer so the content reads as\n * the work surface. The content area scrolls independently so long settings\n * pages stay navigable without the nav scrolling out of view.\n */\nexport type SettingsNavWidth = string;\n</script>\n\n<script setup lang=\"ts\">\nimport { cn } from \"../../lib/cn\";\n\nwithDefaults(\n  defineProps<{\n    /** Width for the navigation panel (e.g. \"12rem\"). */\n    navWidth?: SettingsNavWidth;\n  }>(),\n  { navWidth: \"12rem\" },\n);\n</script>\n\n<template>\n  <div :class=\"cn('min-h-dvh flex flex-col')\">\n    <!--\n      The header is full-width and above the nav+content row, so a title bar\n      or breadcrumb never competes for horizontal space with the nav panel.\n    -->\n    <header v-if=\"$slots.header\">\n      <slot name=\"header\" />\n    </header>\n\n    <!--\n      `flex-wrap: wrap` is the intrinsic collapse mechanism. When the content\n      panel can't fit its `min-width: 50%`, both panels wrap to full-width —\n      the nav becomes a full-width section above the content. No media query;\n      the layout derives its own breakpoint from the container's width.\n    -->\n    <div :class=\"cn('flex flex-1 flex-row')\" :style=\"{ flexWrap: 'wrap' }\">\n      <!--\n        The nav panel: fixed-basis, no growth, no shrink. It does not yield\n        width to the content area — when the container is too narrow, it wraps\n        to full-width instead of compressing. Sunken elevation marks it as\n        chrome, not work surface.\n      -->\n      <nav\n        :style=\"{\n          flexBasis: navWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n        }\"\n        :class=\"cn('bg-sunken w-full p-2')\"\n      >\n        <slot name=\"nav\" />\n      </nav>\n\n      <!--\n        The content area takes all remaining space (`flex-grow: 999`) when the\n        container is wide enough. Its `min-width: 50%` triggers wrapping below\n        tablet-like widths. It scrolls independently so long settings pages\n        stay navigable without the nav scrolling out of view. Gutters widen at\n        wider breakpoints so ultrawide viewports add whitespace rails rather\n        than stretching lines.\n      -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n        :class=\"cn('bg-background min-w-0 flex-1 overflow-y-auto px-4 sm:px-6 3xl:px-8')\"\n      >\n        <slot />\n      </div>\n    </div>\n  </div>\n</template>\n"],"mappings":";;;;;;;;;GAgCE,OAAA,UAAA,GAAA,mBAqDM,OAAA,EArDA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,yBAAA,CAAA,EAAA,GAAA,CAKCA,KAAAA,OAAO,UAArB,UAAA,GAAA,mBAES,UAAA,YAAA,CADP,WAAsB,KAAA,QAAA,QAAA,CAAA,CAAA,KAAA,mBAAA,IAAA,IAAA,GASxB,mBAqCM,OAAA;IArCA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,sBAAA,CAAA;IAA2B,OAAO,EAAA,UAAA,OAAA;GAO/C,GAAA,CAAA,mBASM,OAAA;IARH,OAAK,eAAA;KAAyB,WAAA,QAAA;;;;IAK9B,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,sBAAA,CAAA;GAEV,GAAA,CAAA,WAAmB,KAAA,QAAA,KAAA,CAAA,GAAA,CAAA,GAWrB,mBAUM,OAAA;IATH,OAAO;;;;;IAKP;IACA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,oEAAA,CAAA;GAEV,GAAA,CAAA,WAAQ,KAAA,QAAA,SAAA,CAAA,GAAA,CAAA,CAAA,GAAA,CAAA,CAAA,GAAA,CAAA"}

package/dist/layouts/SplitLayout/SplitLayout.js

@@ -1,7 +0,0 @@
-import SplitLayout_vue_vue_type_script_setup_true_lang_default, { gapClass } from "./SplitLayout.vue_vue_type_script_setup_true_lang.js";
-//#region src/layouts/SplitLayout/SplitLayout.vue
-var SplitLayout_default = SplitLayout_vue_vue_type_script_setup_true_lang_default;
-//#endregion
-export { SplitLayout_default as default, gapClass };
-
-//# sourceMappingURL=SplitLayout.js.map

package/dist/layouts/SplitLayout/SplitLayout.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"SplitLayout.js","names":[],"sources":["../../../src/layouts/SplitLayout/SplitLayout.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * SplitLayout — full-page two-panel layout with intrinsic collapse.\n *\n * A SplitLayout extends the Split composition primitive's intrinsic collapse\n * into a full-page application shell: a side panel and a main content area,\n * with an optional full-width header above. It is the layout a two-column\n * application reaches for — a settings page with a nav rail, a documentation\n * site with a sidebar, a chat interface with a contact list.\n *\n * The intrinsic collapse from the Split composition primitive is reused\n * directly — `flex-wrap` plus a `min-width: 50%` guard on the content panel —\n * so the layout derives its own breakpoint from the container's width rather\n * than a viewport media query. Below the collapse width the panels stack\n * vertically; the side panel sits above the content when `side` is `\"left\"`,\n * below it when `side` is `\"right\"`.\n *\n * The header slot spans the full width, above the split row, so an application\n * header bar stays visible regardless of collapse state. Both panels carry\n * gutters that widen at wider breakpoints, so ultrawide viewports add\n * whitespace rails rather than stretching lines of text.\n */\nexport type SplitLayoutCollapseAt = string;\n\nexport type SplitLayoutGap = \"sm\" | \"md\" | \"lg\" | \"none\";\n\nconst gapClass: Record<Exclude<SplitLayoutGap, \"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 \"../../lib/cn\";\n\nwithDefaults(\n  defineProps<{\n    /** Which side the primary panel sits on. Controls stacking order when collapsed: \"left\" stacks the side panel above, \"right\" stacks it below. */\n    side?: \"left\" | \"right\";\n    /** Below this CSS width the two panels stack vertically instead of sitting side by side. Default: `\"48rem\"`. */\n    collapseAt?: SplitLayoutCollapseAt;\n    /** Minimum width for the side panel (e.g. \"16rem\"). The content area takes the rest. */\n    minSideWidth?: string;\n    /** Gap between panels. Tightens one notch below sm (except \"none\"). */\n    gap?: SplitLayoutGap;\n  }>(),\n  { side: \"left\", collapseAt: \"48rem\", minSideWidth: \"16rem\", gap: \"none\" },\n);\n</script>\n\n<template>\n  <!--\n    The root is a full-height column so the header can span the top while the\n    split row fills the rest. `min-h-dvh` makes the layout at least one\n    viewport tall even when content is short, so the side panel background\n    fills the screen rather than stopping at the content's natural height.\n  -->\n  <div :class=\"cn('min-h-dvh flex flex-col')\">\n    <!--\n      The header spans the full width, above the split row. It is not sticky\n      here — that is the host's decision, because whether an application\n      header pins depends on the content below it.\n    -->\n    <header v-if=\"$slots.header\">\n      <slot name=\"header\" />\n    </header>\n\n    <!--\n      `flex-wrap: wrap` is the intrinsic collapse mechanism. When the content\n      panel cannot honour its `min-width: 50%`, both panels wrap to full-width\n      — the side panel stacks above or below the content depending on `side`.\n      No media query; the layout derives its own breakpoint from the\n      container's width.\n    -->\n    <div\n      :class=\"\n        cn(\n          'flex flex-1',\n          side === 'right' ? 'flex-row-reverse' : 'flex-row',\n          gap !== 'none' ? gapClass[gap] : undefined,\n        )\n      \"\n      :style=\"{ flexWrap: 'wrap' }\"\n    >\n      <!--\n        The side panel holds a fixed basis and does not grow. It sits on the\n        sunken elevation so the content area reads as the work surface lifted\n        above navigation chrome. Gutters widen at wider breakpoints.\n      -->\n      <div\n        :style=\"{\n          flexBasis: minSideWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n          minWidth: minSideWidth,\n        }\"\n        :class=\"cn('bg-sunken w-full px-4 sm:px-6 3xl:px-8')\"\n      >\n        <slot name=\"side\" />\n      </div>\n\n      <!--\n        The content panel takes all remaining space (`flex-grow: 999`) when the\n        container is wide enough. Its `min-width: 50%` triggers wrapping below\n        tablet-like widths. It scrolls independently so long content never\n        pushes the side panel off-screen. Gutters widen at wider breakpoints so\n        ultrawide viewports add whitespace rails rather than stretching lines.\n      -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n        :class=\"cn('bg-background overflow-y-auto px-4 sm:px-6 3xl:px-8')\"\n      >\n        <slot />\n      </div>\n    </div>\n  </div>\n</template>\n"],"mappings":""}

package/dist/layouts/SplitLayout/SplitLayout.vue.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"SplitLayout.vue.d.ts","sourceRoot":"","sources":["../../../src/layouts/SplitLayout/SplitLayout.vue"],"names":[],"mappings":"AAmIA;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,MAAM,qBAAqB,GAAG,MAAM,CAAC;AAE3C,MAAM,MAAM,cAAc,GAAG,IAAI,GAAG,IAAI,GAAG,IAAI,GAAG,MAAM,CAAC;AAEzD,QAAA,MAAM,QAAQ,EAAE,MAAM,CAAC,OAAO,CAAC,cAAc,EAAE,MAAM,CAAC,EAAE,MAAM,CAIpD,CAAC;AAEX,OAAO,EAAE,QAAQ,EAAE,CAAC;wBACC,OAAO,YAAY;AAAxC,wBAAyC;AACzC,QAAA,MAAM,YAAY;IAEd,iJAAiJ;WAC1I,MAAM,GAAG,OAAO;IACvB,gHAAgH;iBACnG,qBAAqB;IAClC,wFAAwF;mBACzE,MAAM;IACrB,uEAAuE;UACjE,cAAc;;IAPpB,iJAAiJ;WAC1I,MAAM,GAAG,OAAO;IACvB,gHAAgH;iBACnG,qBAAqB;IAClC,wFAAwF;mBACzE,MAAM;IACrB,uEAAuE;UACjE,cAAc;;SAAd,cAAc;UANb,MAAM,GAAG,OAAO;gBAEV,qBAAqB;kBAEnB,MAAM;;aAwEZ,CAAC,KAAK,IAAgB,KAAK,GAAG;;WAChC,CAAC,KAAK,IAAgB,KAAK,GAAG;;cAC3B,CAAC,KAAK,IAAgB,KAAK,GAAG;EAUxC,CAAC;AAWL,KAAK,eAAe,CAAC,CAAC,EAAE,CAAC,IAAI,CAAC,GAAG;IAChC,QAAO;QACN,MAAM,EAAE,CAAC,CAAC;KACV,CAAA;CACD,CAAC"}

package/dist/layouts/SplitLayout/SplitLayout.vue_vue_type_script_setup_true_lang.js

@@ -1,46 +0,0 @@
-import { cn } from "../../lib/cn.js";
-import { createCommentVNode, createElementBlock, createElementVNode, defineComponent, normalizeClass, normalizeStyle, openBlock, renderSlot, unref } from "vue";
-//#region src/layouts/SplitLayout/SplitLayout.vue?vue&type=script&setup=true&lang.ts
-var _hoisted_1 = { key: 0 };
-var gapClass = {
-	sm: "gap-2 sm:gap-3",
-	md: "gap-3 sm:gap-4",
-	lg: "gap-4 sm:gap-6"
-};
-var SplitLayout_vue_vue_type_script_setup_true_lang_default = /*@__PURE__*/ defineComponent({
-	__name: "SplitLayout",
-	props: {
-		side: { default: "left" },
-		collapseAt: { default: "48rem" },
-		minSideWidth: { default: "16rem" },
-		gap: { default: "none" }
-	},
-	setup(__props) {
-		return (_ctx, _cache) => {
-			return openBlock(), createElementBlock("div", { class: normalizeClass(unref(cn)("min-h-dvh flex flex-col")) }, [_ctx.$slots.header ? (openBlock(), createElementBlock("header", _hoisted_1, [renderSlot(_ctx.$slots, "header")])) : createCommentVNode("", true), createElementVNode("div", {
-				class: normalizeClass(unref(cn)("flex flex-1", __props.side === "right" ? "flex-row-reverse" : "flex-row", __props.gap !== "none" ? gapClass[__props.gap] : void 0)),
-				style: { flexWrap: "wrap" }
-			}, [createElementVNode("div", {
-				style: normalizeStyle({
-					flexBasis: __props.minSideWidth,
-					flexGrow: 0,
-					flexShrink: 0,
-					minWidth: __props.minSideWidth
-				}),
-				class: normalizeClass(unref(cn)("bg-sunken w-full px-4 sm:px-6 3xl:px-8"))
-			}, [renderSlot(_ctx.$slots, "side")], 6), createElementVNode("div", {
-				style: {
-					flexBasis: 0,
-					flexGrow: 999,
-					flexShrink: 1,
-					minWidth: "50%"
-				},
-				class: normalizeClass(unref(cn)("bg-background overflow-y-auto px-4 sm:px-6 3xl:px-8"))
-			}, [renderSlot(_ctx.$slots, "default")], 2)], 2)], 2);
-		};
-	}
-});
-//#endregion
-export { SplitLayout_vue_vue_type_script_setup_true_lang_default as default, gapClass };
-
-//# sourceMappingURL=SplitLayout.vue_vue_type_script_setup_true_lang.js.map

package/dist/layouts/SplitLayout/SplitLayout.vue_vue_type_script_setup_true_lang.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"SplitLayout.vue_vue_type_script_setup_true_lang.js","names":["$slots"],"sources":["../../../src/layouts/SplitLayout/SplitLayout.vue"],"sourcesContent":["<script lang=\"ts\">\n/**\n * SplitLayout — full-page two-panel layout with intrinsic collapse.\n *\n * A SplitLayout extends the Split composition primitive's intrinsic collapse\n * into a full-page application shell: a side panel and a main content area,\n * with an optional full-width header above. It is the layout a two-column\n * application reaches for — a settings page with a nav rail, a documentation\n * site with a sidebar, a chat interface with a contact list.\n *\n * The intrinsic collapse from the Split composition primitive is reused\n * directly — `flex-wrap` plus a `min-width: 50%` guard on the content panel —\n * so the layout derives its own breakpoint from the container's width rather\n * than a viewport media query. Below the collapse width the panels stack\n * vertically; the side panel sits above the content when `side` is `\"left\"`,\n * below it when `side` is `\"right\"`.\n *\n * The header slot spans the full width, above the split row, so an application\n * header bar stays visible regardless of collapse state. Both panels carry\n * gutters that widen at wider breakpoints, so ultrawide viewports add\n * whitespace rails rather than stretching lines of text.\n */\nexport type SplitLayoutCollapseAt = string;\n\nexport type SplitLayoutGap = \"sm\" | \"md\" | \"lg\" | \"none\";\n\nconst gapClass: Record<Exclude<SplitLayoutGap, \"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 \"../../lib/cn\";\n\nwithDefaults(\n  defineProps<{\n    /** Which side the primary panel sits on. Controls stacking order when collapsed: \"left\" stacks the side panel above, \"right\" stacks it below. */\n    side?: \"left\" | \"right\";\n    /** Below this CSS width the two panels stack vertically instead of sitting side by side. Default: `\"48rem\"`. */\n    collapseAt?: SplitLayoutCollapseAt;\n    /** Minimum width for the side panel (e.g. \"16rem\"). The content area takes the rest. */\n    minSideWidth?: string;\n    /** Gap between panels. Tightens one notch below sm (except \"none\"). */\n    gap?: SplitLayoutGap;\n  }>(),\n  { side: \"left\", collapseAt: \"48rem\", minSideWidth: \"16rem\", gap: \"none\" },\n);\n</script>\n\n<template>\n  <!--\n    The root is a full-height column so the header can span the top while the\n    split row fills the rest. `min-h-dvh` makes the layout at least one\n    viewport tall even when content is short, so the side panel background\n    fills the screen rather than stopping at the content's natural height.\n  -->\n  <div :class=\"cn('min-h-dvh flex flex-col')\">\n    <!--\n      The header spans the full width, above the split row. It is not sticky\n      here — that is the host's decision, because whether an application\n      header pins depends on the content below it.\n    -->\n    <header v-if=\"$slots.header\">\n      <slot name=\"header\" />\n    </header>\n\n    <!--\n      `flex-wrap: wrap` is the intrinsic collapse mechanism. When the content\n      panel cannot honour its `min-width: 50%`, both panels wrap to full-width\n      — the side panel stacks above or below the content depending on `side`.\n      No media query; the layout derives its own breakpoint from the\n      container's width.\n    -->\n    <div\n      :class=\"\n        cn(\n          'flex flex-1',\n          side === 'right' ? 'flex-row-reverse' : 'flex-row',\n          gap !== 'none' ? gapClass[gap] : undefined,\n        )\n      \"\n      :style=\"{ flexWrap: 'wrap' }\"\n    >\n      <!--\n        The side panel holds a fixed basis and does not grow. It sits on the\n        sunken elevation so the content area reads as the work surface lifted\n        above navigation chrome. Gutters widen at wider breakpoints.\n      -->\n      <div\n        :style=\"{\n          flexBasis: minSideWidth,\n          flexGrow: 0,\n          flexShrink: 0,\n          minWidth: minSideWidth,\n        }\"\n        :class=\"cn('bg-sunken w-full px-4 sm:px-6 3xl:px-8')\"\n      >\n        <slot name=\"side\" />\n      </div>\n\n      <!--\n        The content panel takes all remaining space (`flex-grow: 999`) when the\n        container is wide enough. Its `min-width: 50%` triggers wrapping below\n        tablet-like widths. It scrolls independently so long content never\n        pushes the side panel off-screen. Gutters widen at wider breakpoints so\n        ultrawide viewports add whitespace rails rather than stretching lines.\n      -->\n      <div\n        :style=\"{\n          flexBasis: 0,\n          flexGrow: 999,\n          flexShrink: 1,\n          minWidth: '50%',\n        }\"\n        :class=\"cn('bg-background overflow-y-auto px-4 sm:px-6 3xl:px-8')\"\n      >\n        <slot />\n      </div>\n    </div>\n  </div>\n</template>\n"],"mappings":";;;;AA0BA,IAAM,WAA4D;CAChE,IAAI;CACJ,IAAI;CACJ,IAAI;AACN;;;;;;;;;;;GA8BE,OAAA,UAAA,GAAA,mBA+DM,OAAA,EA/DA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,yBAAA,CAAA,EAAA,GAAA,CAMCA,KAAAA,OAAO,UAArB,UAAA,GAAA,mBAES,UAAA,YAAA,CADP,WAAsB,KAAA,QAAA,QAAA,CAAA,CAAA,KAAA,mBAAA,IAAA,IAAA,GAUxB,mBA6CM,OAAA;IA5CH,OAAK,eAAW,MAAA,EAAA,CAAE,CAAA,eAAqC,QAAA,SAAI,UAAA,qBAAA,YAA0D,QAAA,QAAG,SAAc,SAAS,QAAA,OAAO,KAAA,CAAA,CAAA;IAOtJ,OAAO,EAAA,UAAA,OAAA;GAOR,GAAA,CAAA,mBAUM,OAAA;IATH,OAAK,eAAA;KAAyB,WAAA,QAAA;;;KAAkF,UAAA,QAAA;;IAMhH,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,wCAAA,CAAA;GAEV,GAAA,CAAA,WAAoB,KAAA,QAAA,MAAA,CAAA,GAAA,CAAA,GAUtB,mBAUM,OAAA;IATH,OAAO;;;;;IAKP;IACA,OAAK,eAAE,MAAA,EAAA,CAAE,CAAA,qDAAA,CAAA;GAEV,GAAA,CAAA,WAAQ,KAAA,QAAA,SAAA,CAAA,GAAA,CAAA,CAAA,GAAA,CAAA,CAAA,GAAA,CAAA"}

package/dist/lib/a11y-scope.d.ts

@@ -1,19 +0,0 @@
-/**
- * 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 documentation site's live
- * accessibility panel and the end-to-end gate that scans the built site. Both
- * import this. The list must never be restated, or the panel 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.
- */
-export declare const WCAG_TAGS: readonly ["wcag2a", "wcag2aa", "wcag21a", "wcag21aa"];
-//# sourceMappingURL=a11y-scope.d.ts.map

package/dist/lib/a11y-scope.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"a11y-scope.d.ts","sourceRoot":"","sources":["../../src/lib/a11y-scope.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,SAAS,uDAAwD,CAAC"}

package/dist/lib/a11y-scope.js

@@ -1,28 +0,0 @@
-//#region src/lib/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 documentation site's live
-* accessibility panel and the end-to-end gate that scans the built site. Both
-* import this. The list must never be restated, or the panel 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.
-*/
-var WCAG_TAGS = [
-	"wcag2a",
-	"wcag2aa",
-	"wcag21a",
-	"wcag21aa"
-];
-//#endregion
-export { WCAG_TAGS };
-
-//# sourceMappingURL=a11y-scope.js.map

package/dist/lib/a11y-scope.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"a11y-scope.js","names":[],"sources":["../../src/lib/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 documentation site's live\n * accessibility panel and the end-to-end gate that scans the built site. Both\n * import this. The list must never be restated, or the panel a contributor\n * reads and the gate that blocks the merge drift into disagreeing about what\n * 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 */\nexport const WCAG_TAGS = [\"wcag2a\", \"wcag2aa\", \"wcag21a\", \"wcag21aa\"] as const;\n"],"mappings":";;;;;;;;;;;;;;;;;;AAiBA,IAAa,YAAY;CAAC;CAAU;CAAW;CAAW;AAAU"}

package/dist/lib/ancestor-disabled.d.ts

@@ -1,35 +0,0 @@
-import { type Ref } from "vue";
-/**
- * Whether an enclosing `<fieldset disabled>` has made this control unavailable
- * — read off the element itself, not off anything a wrapper told us.
- *
- * The platform already answers this for `<input>`, `<button>`, `<select>` and
- * `<textarea>`: a disabled fieldset makes every such descendant *actually
- * disabled*, so `:disabled` matches, the tab stop goes and the control refuses
- * input. Nothing in Loom has to help. It stops at the boundary of that list,
- * and Reka builds several controls out of elements that are not on it — a
- * `<span role="slider">`, a `<div role="spinbutton">`. Those keep their
- * `tabindex="0"` and their arrow-key handlers inside a disabled group: measured
- * in jsdom, a Slider in a `<fieldset disabled>` still took Home/End and moved
- * its value, and a DatePicker segment still typed. A control that looks
- * unavailable and still answers the keyboard is worse than one that looks
- * available, so the appearance cannot be fixed on its own.
- *
- * **This is a read of the native attribute, not a second copy of it.**
- * `Fieldset.vue`'s docblock rules out publishing `disabled` through the Field
- * context, and the reason is precedence: a context is a claim a control may
- * beat with `:disabled="false"`, while the native attribute disables it anyway,
- * leaving a control that renders enabled and silently refuses input. Nothing
- * here can drift that way, because there is nothing to beat — the answer is
- * recomputed from the same DOM the browser is reading, so a control cannot
- * disagree with the fieldset it is standing in. It also needs no Loom wrapper
- * at all: a raw `<fieldset disabled>` a consumer wrote works exactly as one of
- * ours does.
- *
- * The result is `false` on the server and until the effect first runs, which is
- * deliberate. `watchPostEffect` does not run during SSR, so the markup a server
- * emits matches the markup the client hydrates and the state settles in the
- * same tick as mount — a hydration-time correction rather than a mismatch.
- */
-export declare function useAncestorDisabled(target: () => Element | null | undefined): Readonly<Ref<boolean>>;
-//# sourceMappingURL=ancestor-disabled.d.ts.map

package/dist/lib/ancestor-disabled.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ancestor-disabled.d.ts","sourceRoot":"","sources":["../../src/lib/ancestor-disabled.ts"],"names":[],"mappings":"AAAA,OAAO,EAAkD,KAAK,GAAG,EAAE,MAAM,KAAK,CAAC;AAE/E;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AACH,wBAAgB,mBAAmB,CACjC,MAAM,EAAE,MAAM,OAAO,GAAG,IAAI,GAAG,SAAS,GACvC,QAAQ,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAmCxB"}

package/dist/lib/ancestor-disabled.js

@@ -1,86 +0,0 @@
-import { onScopeDispose, readonly, ref, watchPostEffect } from "vue";
-//#region src/lib/ancestor-disabled.ts
-/**
-* Whether an enclosing `<fieldset disabled>` has made this control unavailable
-* — read off the element itself, not off anything a wrapper told us.
-*
-* The platform already answers this for `<input>`, `<button>`, `<select>` and
-* `<textarea>`: a disabled fieldset makes every such descendant *actually
-* disabled*, so `:disabled` matches, the tab stop goes and the control refuses
-* input. Nothing in Loom has to help. It stops at the boundary of that list,
-* and Reka builds several controls out of elements that are not on it — a
-* `<span role="slider">`, a `<div role="spinbutton">`. Those keep their
-* `tabindex="0"` and their arrow-key handlers inside a disabled group: measured
-* in jsdom, a Slider in a `<fieldset disabled>` still took Home/End and moved
-* its value, and a DatePicker segment still typed. A control that looks
-* unavailable and still answers the keyboard is worse than one that looks
-* available, so the appearance cannot be fixed on its own.
-*
-* **This is a read of the native attribute, not a second copy of it.**
-* `Fieldset.vue`'s docblock rules out publishing `disabled` through the Field
-* context, and the reason is precedence: a context is a claim a control may
-* beat with `:disabled="false"`, while the native attribute disables it anyway,
-* leaving a control that renders enabled and silently refuses input. Nothing
-* here can drift that way, because there is nothing to beat — the answer is
-* recomputed from the same DOM the browser is reading, so a control cannot
-* disagree with the fieldset it is standing in. It also needs no Loom wrapper
-* at all: a raw `<fieldset disabled>` a consumer wrote works exactly as one of
-* ours does.
-*
-* The result is `false` on the server and until the effect first runs, which is
-* deliberate. `watchPostEffect` does not run during SSR, so the markup a server
-* emits matches the markup the client hydrates and the state settles in the
-* same tick as mount — a hydration-time correction rather than a mismatch.
-*/
-function useAncestorDisabled(target) {
-	const disabled = ref(false);
-	let observer;
-	function sync() {
-		const start = target();
-		if (!start) {
-			observer?.disconnect();
-			disabled.value = false;
-			return;
-		}
-		const fieldsets = enclosingFieldsets(start);
-		observer ??= new MutationObserver(sync);
-		observer.disconnect();
-		for (const fieldset of fieldsets) observer.observe(fieldset, {
-			attributes: true,
-			attributeFilter: ["disabled"]
-		});
-		disabled.value = fieldsets.some((fieldset) => fieldset.disabled);
-	}
-	watchPostEffect(sync);
-	onScopeDispose(() => {
-		observer?.disconnect();
-	});
-	return readonly(disabled);
-}
-/**
-* The `<fieldset>` ancestors whose `disabled` would reach `start`, outermost
-* last, whether or not any of them currently carries the attribute — they are
-* what has to be watched for the attribute arriving.
-*
-* The walk climbs child-by-child rather than calling `closest("fieldset")`
-* because of the exemption in the "actually disabled" rule: controls inside a
-* disabled fieldset's **first** `<legend>` stay available, which is what makes
-* a switch in the legend that re-enables its own group possible. Reaching a
-* fieldset through that legend is reaching a fieldset that does not disable
-* you, so it is skipped — and the walk continues past it, since a fieldset
-* further out may still disable the legend itself.
-*/
-function enclosingFieldsets(start) {
-	const found = [];
-	let node = start;
-	while (node) {
-		const parent = node.parentElement;
-		if (parent instanceof HTMLFieldSetElement && node !== parent.querySelector(":scope > legend")) found.push(parent);
-		node = parent;
-	}
-	return found;
-}
-//#endregion
-export { useAncestorDisabled };
-
-//# sourceMappingURL=ancestor-disabled.js.map

package/dist/lib/ancestor-disabled.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ancestor-disabled.js","names":[],"sources":["../../src/lib/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. It stops at the boundary of that 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":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAkCA,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/lib/attrs.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"attrs.d.ts","sourceRoot":"","sources":["../../src/lib/attrs.ts"],"names":[],"mappings":"AAAA,OAAO,EAAsB,KAAK,WAAW,EAAE,MAAM,KAAK,CAAC;AAE3D;;;;;;;;;;;GAWG;AACH,wBAAgB,aAAa,IAAI;IAC/B,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC/B,IAAI,EAAE,WAAW,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,CAAC;CAC5C,CAOA"}

package/dist/lib/attrs.js

@@ -1,28 +0,0 @@
-import { computed, useAttrs } from "vue";
-//#region src/lib/attrs.ts
-/**
-* Split `useAttrs()` into the raw fallthrough attributes — read `.class` off
-* `attrs` for a `cn()` merge — and the same attributes minus `class` (`rest`,
-* for `v-bind` onto whichever node is not the `class` target).
-*
-* Every caller pairs this with `defineOptions({ inheritAttrs: false })`.
-* NumberField's input, Slider's thumb and Select's trigger each route `class`
-* onto one specific rendered node rather than taking Vue's default
-* single-root fallthrough, because `class` needs a Tailwind-aware merge while
-* the rest of the fallthrough — aria-*, data-testid — only needs to land
-* somewhere real.
-*/
-function useSplitAttrs() {
-	const attrs = useAttrs();
-	return {
-		attrs,
-		rest: computed(() => {
-			const { class: _class, ...others } = attrs;
-			return others;
-		})
-	};
-}
-//#endregion
-export { useSplitAttrs };
-
-//# sourceMappingURL=attrs.js.map

package/dist/lib/attrs.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"attrs.js","names":[],"sources":["../../src/lib/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/lib/cn.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"cn.d.ts","sourceRoot":"","sources":["../../src/lib/cn.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,UAAU,EAAQ,MAAM,MAAM,CAAC;AAqF7C;;;;;GAKG;AACH,wBAAgB,EAAE,CAAC,GAAG,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,CAElD"}

package/dist/lib/cn.js

@@ -1,61 +0,0 @@
-import { clsx } from "clsx";
-import { extendTailwindMerge } from "tailwind-merge";
-//#region src/lib/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/lib/cn.js.map

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