@sitecoreai-labs/sitecoreai-cli 0.0.4

package/dist/recipe/guids.d.ts

@@ -0,0 +1,400 @@
+/**
+ * Frozen at v1. Hardcoded literal so repo edits to derivation logic can't
+ * silently re-namespace existing tenants. The `__namespace_root_is_frozen`
+ * test asserts this matches `uuidv5(DNS, "registry.sitecoreai.dev")`.
+ */
+export declare const NAMESPACE_ROOT = "d6c28e9f-21f3-56ee-ada3-f2a947c3d475";
+export declare const NAMESPACE_TEMPLATE: string;
+export declare const NAMESPACE_RENDERING: string;
+export declare const NAMESPACE_PARTIAL_DESIGN: string;
+export declare const NAMESPACE_PAGE_DESIGN: string;
+export declare const NAMESPACE_SITE_BRANCH: string;
+export declare const NAMESPACE_CONTENT_ITEM: string;
+export declare const NAMESPACE_SITE: string;
+export declare const NAMESPACE_ENUMERATION: string;
+/** Internal: lets the test prove `NAMESPACE_ROOT` matches its derivation. */
+export declare const _deriveNamespaceRoot: () => string;
+export declare const templateId: (site: string, handle: string) => string;
+export declare const renderingId: (site: string, handle: string) => string;
+export declare const paramsTemplateId: (site: string, handle: string) => string;
+export declare const partialDesignId: (site: string, handle: string) => string;
+export declare const pageDesignId: (site: string, handle: string) => string;
+export declare const siteBranchId: (handle: string) => string;
+export declare const contentItemId: (site: string, handle: string) => string;
+/**
+ * Recipe-internal refKey for a `SiteRecipe`'s site item. The actual
+ * Sitecore site itemId is server-assigned by the Sites API at
+ * `createSite` time; this refKey is the IR's identity for cross-op
+ * resolution (dictionary phrases, taxonomy tags scoped under the site
+ * inherit it).
+ */
+export declare const siteId: (handle: string) => string;
+/**
+ * Recipe-internal refKey for a dictionary phrase item under a site.
+ * SXA's Site Wizard materialises `<site>/Dictionary/<phraseName>` based
+ * on the SiteTemplate's dictionary defaults; SiteRecipe's
+ * `dictionaryOverrides` writes the Phrase field on those existing
+ * items. The executor seeds this refKey via cross-recipe path lookup
+ * after `CreateSiteFromTemplate` materialises the site.
+ */
+export declare const dictionaryPhraseId: (siteHandle: string, phraseName: string) => string;
+/**
+ * Recipe-internal refKey for a taxonomy folder (root) under a site.
+ * Mirror of `dictionaryPhraseId` for the taxonomy tree — late-seeded
+ * after the site materialises.
+ */
+export declare const taxonomyFolderId: (siteHandle: string, rootName: string) => string;
+/**
+ * Recipe-internal refKey for a taxonomy tag item under a site's
+ * taxonomy folder. Used when a SiteRecipe override list adds tags
+ * beyond the SiteTemplate defaults — those become CreateItem ops
+ * parented to the late-seeded taxonomy folder refKey.
+ */
+export declare const taxonomyTagId: (siteHandle: string, rootName: string, tagName: string) => string;
+/**
+ * Stable refKey for the SXA Page Designs root item (the tenant-existing
+ * item that holds the `TemplatesMapping` field). The orchestrator
+ * pipeline-step seeds `crossRecipeRefs[<this>] = pageDesignsRoot` at
+ * execute time so SetField ops targeting the mapping resolve correctly.
+ *
+ * Not a Sitecore concept — purely a refKey our IR uses to coordinate
+ * with the executor's pre-seed mechanism.
+ */
+export declare const PAGE_DESIGNS_ROOT_REF_KEY: string;
+/** Sections are scoped under their (site-scoped) template; seed `section:<name>`. */
+export declare const sectionId: (site: string, handle: string, sectionName: string) => string;
+/** Fields are scoped under their (site-scoped) template; the seed is the field name. */
+export declare const fieldId: (site: string, handle: string, fieldName: string) => string;
+/** Sections of the parameters template scope under (site-scoped) `paramsTemplateId`. */
+export declare const paramsSectionId: (site: string, handle: string, sectionName: string) => string;
+/** Fields of the parameters template scope under (site-scoped) `paramsTemplateId`. */
+export declare const paramsFieldId: (site: string, handle: string, fieldName: string) => string;
+/**
+ * Per-rendering Headless Variants folder. Lives at
+ * `<headlessVariantsRoot>/<section>/<RenderingName>/` and conforms to
+ * SXA's `HeadlessVariants` template. The refKey seed is unchanged
+ * from the legacy "under the rendering item" location (`__variants`
+ * scoped to the rendering's id) so existing caches continue to
+ * resolve — only the path/template changed.
+ */
+export declare const variantsFolderId: (site: string, handle: string) => string;
+/**
+ * Each Variant Definition item lives under the per-rendering
+ * Headless Variants folder. Conforms to SXA's `Variant Definition`
+ * template.
+ */
+export declare const variantId: (site: string, handle: string, variantName: string) => string;
+/**
+ * Standard values is a child of the template whose template-of is the
+ * template's own ID. The GUID is derived from the (site-scoped) template
+ * ID with the `__standard-values` seed.
+ */
+export declare const standardValuesId: (site: string, handle: string) => string;
+/**
+ * Standard values for a parameters template. Same `__standard-values`
+ * seed pattern as `standardValuesId` but scoped under
+ * `paramsTemplateId(site, handle)` so params-template SV items don't
+ * collide with the component-template SV under the same handle.
+ */
+export declare const paramsStandardValuesId: (site: string, handle: string) => string;
+/**
+ * Enumeration root item — backs an `EnumerationRecipe`. Lives at
+ * `<enumerationsRoot>/<EnumName>` per-site. Children are the enum's
+ * value items (see `enumValueId`). Site-scoped seed `<site>::<handle>`
+ * matches the rest of the per-component derivations so cross-site
+ * pushes don't collide.
+ */
+export declare const enumerationFolderId: (site: string, handle: string) => string;
+/**
+ * Deterministic refKey for a single enumeration value item. Scopes
+ * under the EnumerationRecipe's `enumerationFolderId(site, handle)` so
+ * the same value name (`primary`, `default`, etc.) produces distinct
+ * GUIDs across enums.
+ */
+export declare const enumValueId: (parentRefKey: string, valueName: string) => string;
+/**
+ * Per-site `Enumerations Folder` template. The folder layers in an
+ * enumeration tree (root, per-section grouping, per-enum) all conform
+ * to this template instead of Sitecore's generic Folder, so the SXA
+ * editor recognises the layout and stamps the right icon. Site-scoped
+ * because each site owns its own per-Project templates tree.
+ */
+export declare const enumerationsFolderTemplateId: (site: string) => string;
+/**
+ * Deterministic refKey for one segment of an
+ * `EnumerationRecipe.location.folder` grouping path under
+ * `<enumerationsRoot>/<…segments…>`. Conforms to the per-site
+ * `Enumerations Folder` template. Site-scoped + keyed on the segment's
+ * cumulative path so two recipes in the same push pointing at
+ * `folder: "Theme/Color"` reuse the `Theme` and `Theme/Color` folders
+ * rather than colliding.
+ *
+ * Pass the cumulative path (e.g. `"Theme"` then `"Theme/Color"`) — not
+ * just the leaf segment — so each level gets its own GUID seeded by its
+ * full position in the tree. This keeps two folders named `Color`
+ * (one under `Theme`, one under `Layout`) distinct.
+ *
+ * Same `NAMESPACE_PROJECT` family as section folders / Component
+ * Folders buckets — all "site organisational folders" with the same
+ * identity model.
+ */
+export declare const enumerationsGroupingFolderId: (site: string, cumulativePath: string) => string;
+/**
+ * Per-site `Enumeration` template. The per-enum container items
+ * (`Color Scheme`, `Heading Size`, `Background Themes`, etc.) conform
+ * to this template — i.e. each enumeration is itself an `Enumeration`,
+ * and its leaf values live below it as `Enumeration Value` children.
+ * Carries an inner `Enumeration` Section + `Value` Single-Line Text
+ * shared field so each per-enum container item can store its
+ * canonical default (driven by `EnumerationRecipe.default`). Site-
+ * scoped for the same reason as `enumerationsFolderTemplateId`.
+ */
+export declare const enumerationTemplateId: (site: string) => string;
+/**
+ * The single Template Section under the per-site `Enumeration`
+ * template, named `"Enumeration"` (mirrors the Enumeration Value
+ * template's inner section so the field path on both templates is
+ * structurally identical: `<template>/Enumeration/Value`).
+ */
+export declare const enumerationContainerSectionId: (site: string) => string;
+/**
+ * The `Value` Template Field under the per-site `Enumeration` template's
+ * `Enumeration` section. Stores each per-enum container item's default
+ * value (`"primary"` for Color Scheme, `"md"` for Heading Size, etc.) —
+ * driven by `EnumerationRecipe.default` at compile time. Edge consumers
+ * reading the container directly resolve the default via this field.
+ */
+export declare const enumerationContainerValueFieldId: (site: string) => string;
+/**
+ * Per-site `__Standard Values` item under the `Enumeration` template
+ * definition. Linked via `SetStandardValues` so its Insert Options
+ * propagate to every per-enum container item conforming to the
+ * Enumeration template — authors can right-click `Color Scheme` →
+ * Insert → Enumeration Value to add a new value without picking
+ * templates from a long list.
+ */
+export declare const enumerationTemplateStandardValuesId: (site: string) => string;
+/**
+ * Per-site `Enumeration Value` template. The leaf value items (like
+ * `primary`, `accent`, `lg`, `shooting-star`) conform to this template,
+ * NOT to the `Enumeration` template — `Enumeration` is for the per-enum
+ * container; `Enumeration Value` is for the leaves. Carries the inner
+ * `Enumeration` Template Section + `Value` Template Field (defined
+ * below) so each value item stores its actual enumeration string on
+ * the `Value` shared field. Site-scoped.
+ */
+export declare const enumerationValueTemplateId: (site: string) => string;
+/**
+ * The single Template Section under the per-site `Enumeration Value`
+ * template, named `"Enumeration"` (matches the canonical
+ * `click-click-launch/Presentation/Enumeration Value/Enumeration`).
+ * Holds the `Value` field below. Scoped under
+ * `enumerationValueTemplateId(site)` so the GUID is stable per-site
+ * without colliding across sites.
+ *
+ * Function name retained for backwards compatibility with the prior
+ * (broken) layout where this section lived under the Enumeration
+ * template; the GUID it derives is now under the value template.
+ */
+export declare const enumerationTemplateSectionId: (site: string) => string;
+/**
+ * The `Value` Template Field under the per-site `Enumeration Value`
+ * template's `Enumeration` section. Stores the actual enumeration
+ * value (`"primary"`, `"shooting-star"`, etc.) on every value item
+ * conforming to the Enumeration Value template. Scoped under
+ * `enumerationValueTemplateId(site)` for stability.
+ *
+ * Function name retained for backwards compatibility — see
+ * `enumerationTemplateSectionId` note above.
+ */
+export declare const enumerationTemplateValueFieldId: (site: string) => string;
+/**
+ * Datasource items are scoped to a page recipe's id, keyed on slot path —
+ * redeploys with regenerated mock content overwrite the same item.
+ * Phase 1 doesn't emit these; defined here for forward-compat parity with
+ * the planning doc.
+ */
+export declare const datasourceId: (pageItemId: string, slotPath: string) => string;
+/**
+ * Project namespace — used for site-scoped folder identities (section
+ * folders under `Components/<site>/Components/<section>`, etc.). Distinct
+ * from the per-template namespaces because section folders are owned by
+ * the *site*, not by any single template.
+ */
+export declare const NAMESPACE_PROJECT: string;
+/**
+ * Deterministic refKey for a section folder under a site's
+ * `Components/` bucket. Emitted as a `CreateOnly` `CreateItem` so
+ * re-pushing a recipe set materialises the section once and is a
+ * no-op thereafter. Identity scheme follows
+ * `plans/recipe-site-folder-layout.md` § "Deterministic GUID
+ * extensions".
+ */
+export declare const sectionFolderId: (site: string, section: string) => string;
+/**
+ * Deterministic refKey for the renderings-side section folder under
+ * `<renderingsRoot>/<section>/`. Distinct seed from the templates-side
+ * section folder so the two don't share an identity (they are separate
+ * Sitecore items in separate trees).
+ */
+export declare const renderingsSectionFolderId: (site: string, section: string) => string;
+/**
+ * Deterministic refKey for an SXA Headless Variants section grouping
+ * under `<headlessVariantsRoot>/<section>/`. Distinct from the
+ * templates-side and renderings-side section folder seeds — separate
+ * tree, separate Sitecore items, separate identity. Conforms to the
+ * `HeadlessVariantsGrouping` template.
+ */
+export declare const headlessVariantsSectionFolderId: (site: string, section: string) => string;
+/**
+ * Deterministic refKey for an SXA Available Renderings section item
+ * (`<availableRenderingsRoot>/<section>`). Conforms to the
+ * `AVAILABLE_RENDERINGS` template; aggregates every component-template
+ * recipe in the section into one Renderings field. Idempotent across
+ * runs — same `(site, section)` → same refKey forever.
+ */
+export declare const availableRenderingsSectionId: (site: string, section: string) => string;
+/**
+ * Deterministic refKey for a "Component Folders" subfolder under a
+ * site's `Components/<section>/` — an idempotent parent for the
+ * generated `<Component> Folder` templates.
+ */
+export declare const componentFoldersBucketId: (site: string, section: string) => string;
+/**
+ * Deterministic refKey for a "Presentation Parameters" subfolder under
+ * a site's `Components/<section>/` — an idempotent parent for
+ * standalone (and synthesised) Parameters templates.
+ */
+export declare const presentationParametersBucketId: (site: string, section: string) => string;
+/**
+ * Deterministic refKey for a `<Component> Folder` template emitted when
+ * a `ComponentTemplateRecipe` declares `children:`. The Sitecore item
+ * lands at `Components/<section>/Component Folders/<Component> Folder`;
+ * the seed is `<componentHandle>::folder`, namespaced under
+ * `NAMESPACE_TEMPLATE` so it shares the template-id family without
+ * colliding with the component's own template id.
+ */
+export declare const componentFolderTemplateId: (site: string, componentHandle: string) => string;
+/**
+ * Standard-values item refKey for a component folder template. Same
+ * derivation pattern as `standardValuesId` (seed `__standard-values`,
+ * scope under the folder template's id) but differentiated by the
+ * folder template's distinct namespace.
+ */
+export declare const componentFolderStandardValuesId: (site: string, componentHandle: string) => string;
+/**
+ * Deterministic refKey for a Content Models group folder under a
+ * site's `Content Models/<group>/`. Materialised once via a CreateOnly
+ * CreateItem when any content template in the recipe set carries
+ * `meta.tax.group` matching this name.
+ */
+export declare const contentModelsGroupFolderId: (site: string, group: string) => string;
+/**
+ * Per-site shared Data Folder under `<contentItemsRoot>/<subfolder>`.
+ * Emitted as a CreateOnly item by `compileComponentTemplateRecipe` when
+ * a recipe declares a `site`-scoped datasource location with a
+ * `subfolder`. Multiple recipes with the same subfolder share the
+ * folder (idempotent emission via the `emittedFolders` set).
+ */
+export declare const siteDataFolderId: (site: string, subfolder: string) => string;
+/**
+ * Per-component Data Folder TEMPLATE emitted when a recipe declares a
+ * site-scoped datasource location. Lands at
+ * `Components/<section>/Data Folders/<Component> Data Folder`. The
+ * Sitecore folder ITEM(s) at `<contentItemsRoot>/<subfolder>` conform
+ * to this template (instead of the generic `Folder`) so its
+ * `__Standard Values`'s Insert Options can restrict children to the
+ * component's own datasource template — i.e. a "Badges" folder only
+ * accepts Badge datasources when an author right-clicks → Insert.
+ *
+ * One template per recipe-handle (idempotent across multiple
+ * site-scoped subfolders that share the same recipe). Mirrors
+ * `componentFolderTemplateId` for `children:` declarations, but
+ * keyed under a distinct seed so the two templates don't collide.
+ */
+export declare const siteDataFolderTemplateId: (site: string, recipeHandle: string) => string;
+/**
+ * Standard-values item refKey for a per-component Data Folder template.
+ * Same derivation pattern as `standardValuesId` and
+ * `componentFolderStandardValuesId` — seed `__standard-values` under
+ * the folder template's own id.
+ */
+export declare const siteDataFolderStandardValuesId: (site: string, recipeHandle: string) => string;
+/**
+ * SHARED Data Folder template — keyed on `(site, subfolder)` instead of
+ * `(site, recipeHandle)`. Emitted by `compileRecipeSet` when two or
+ * more recipes target the same site-scoped `subfolder` (the shared-
+ * pool design-system pattern: Badge + StatusPill + Tag all populating
+ * `Site Shared UI/Badges`). The shared template's `__Standard Values`
+ * Insert Options field aggregates every contributing recipe's
+ * datasource template, so a CMS author right-clicking → Insert sees
+ * all the shapes that legitimately belong in that pool.
+ *
+ * Per-recipe `siteDataFolderTemplateId` stays in use for the
+ * SINGLETON case (one recipe → one subfolder). The choice between the
+ * two is made by the cross-recipe coalescer in `compileRecipeSet`:
+ * count refs per `(site, subfolder)`; ≥2 → shared template;
+ * exactly 1 → per-recipe template.
+ */
+export declare const sharedDataFolderTemplateId: (site: string, subfolder: string) => string;
+/**
+ * Standard-values item refKey for a shared per-subfolder Data Folder
+ * template. Same `__standard-values` seed pattern as the rest of the
+ * SV family.
+ */
+export declare const sharedDataFolderStandardValuesId: (site: string, subfolder: string) => string;
+/**
+ * Recipe-internal refKey for the site Data folder ROOT's
+ * `__Standard Values` item (one per site). The ITEM at
+ * `<contentItemsRoot>` itself is tenant-pre-existing or
+ * lazy-created; scai writes the SV directly under it via a
+ * CreateOnly CreateItem op.
+ */
+export declare const siteDataRootStandardValuesId: (site: string) => string;
+/**
+ * Recipe-internal refKey for the enumerations root ITEM (one per site
+ * — the `<enumerationsRoot>` content tree node, e.g.
+ * `<site>/Presentation/Enumerations`). The path-walker would otherwise
+ * auto-create this as the generic `Folder` template with the default
+ * folder icon when child ops first land; scai emits an explicit
+ * CreateAndUpdate CreateItem against this refKey so the item exists
+ * with the enumeration glyph icon, matching the per-site enumeration
+ * templates' icon.
+ */
+export declare const enumerationsRootId: (site: string) => string;
+/**
+ * Recipe-internal refKey for the enumerations root's
+ * `__Standard Values` item (one per site). Mirror of
+ * `siteDataRootStandardValuesId` for the enumerations tree — scai
+ * writes the SV directly under the root via a CreateOnly CreateItem op
+ * so authors' right-click → Insert UX is restricted to enumeration
+ * folders + the generic Folder template.
+ */
+export declare const enumerationsRootStandardValuesId: (site: string) => string;
+/**
+ * Per-site `__Standard Values` item under the `Enumerations Folder`
+ * template definition (NOT under each data folder). Linked to the
+ * template via `SetStandardValues` so its `Insert Options` propagates
+ * to every item conforming to Enumerations Folder — both the
+ * grouping-folder items under `<enumerationsRoot>` and the per-enum
+ * data folders themselves get the same Insert UX without an SV item
+ * polluting each data folder's children.
+ *
+ * Replaces the old `enumerationFolderStandardValuesId` (per-recipe SV
+ * under each data folder), which was non-functional anyway — it set
+ * Insert Options on the SV item without `SetStandardValues` linking,
+ * so the field had no effect, but the SV item itself appeared in the
+ * Droplink picker as a sibling of the enum value items.
+ */
+export declare const enumerationsFolderTemplateStandardValuesId: (site: string) => string;
+/**
+ * Deterministic refKey for a `SectionDefinitionRecipe` — the SXA
+ * Available Rendering Section Definition item the registry's
+ * `availableIn` bindings target. The section definition is typically
+ * pre-existing on the tenant; the GUID is used as the cross-recipe
+ * refKey so `AppendToMultiList` ops can resolve via the executor's
+ * captured-itemId map.
+ */
+export declare const NAMESPACE_SECTION_DEFINITION: string;
+export declare const sectionDefinitionId: (handle: string) => string;
+//# sourceMappingURL=guids.d.ts.map

package/dist/recipe/guids.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"guids.d.ts","sourceRoot":"","sources":["../../src/recipe/guids.ts"],"names":[],"mappings":"AAqCA;;;;GAIG;AACH,eAAO,MAAM,cAAc,yCAAyC,CAAC;AAErE,eAAO,MAAM,kBAAkB,QAAqC,CAAC;AACrE,eAAO,MAAM,mBAAmB,QAAsC,CAAC;AACvE,eAAO,MAAM,wBAAwB,QAA2C,CAAC;AACjF,eAAO,MAAM,qBAAqB,QAAwC,CAAC;AAC3E,eAAO,MAAM,qBAAqB,QAAwC,CAAC;AAC3E,eAAO,MAAM,sBAAsB,QAAyC,CAAC;AAC7E,eAAO,MAAM,cAAc,QAAiC,CAAC;AAC7D,eAAO,MAAM,qBAAqB,QAAwC,CAAC;AAE3E,6EAA6E;AAC7E,eAAO,MAAM,oBAAoB,QAAO,MAA0D,CAAC;AAEnG,eAAO,MAAM,UAAU,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACR,CAAC;AAEnD,eAAO,MAAM,WAAW,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACR,CAAC;AAEpD,eAAO,MAAM,gBAAgB,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACN,CAAC;AAE3D,eAAO,MAAM,eAAe,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACP,CAAC;AAEzD,eAAO,MAAM,YAAY,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACP,CAAC;AAEtD,eAAO,MAAM,YAAY,GAAI,QAAQ,MAAM,KAAG,MAA+C,CAAC;AAE9F,eAAO,MAAM,aAAa,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACP,CAAC;AAEvD;;;;;;GAMG;AACH,eAAO,MAAM,MAAM,GAAI,QAAQ,MAAM,KAAG,MAAwC,CAAC;AAEjF;;;;;;;GAOG;AACH,eAAO,MAAM,kBAAkB,GAAI,YAAY,MAAM,EAAE,YAAY,MAAM,KAAG,MACpB,CAAC;AAEzD;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,GAAI,YAAY,MAAM,EAAE,UAAU,MAAM,KAAG,MACpB,CAAC;AAErD;;;;;GAKG;AACH,eAAO,MAAM,aAAa,GAAI,YAAY,MAAM,EAAE,UAAU,MAAM,EAAE,SAAS,MAAM,KAAG,MACpB,CAAC;AAEnE;;;;;;;;GAQG;AACH,eAAO,MAAM,yBAAyB,QAA8C,CAAC;AAErF,qFAAqF;AACrF,eAAO,MAAM,SAAS,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,EAAE,aAAa,MAAM,KAAG,MAClB,CAAC;AAE7D,wFAAwF;AACxF,eAAO,MAAM,OAAO,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,EAAE,WAAW,MAAM,KAAG,MAC7B,CAAC;AAE9C,wFAAwF;AACxF,eAAO,MAAM,eAAe,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,EAAE,aAAa,MAAM,KAAG,MAClB,CAAC;AAEnE,sFAAsF;AACtF,eAAO,MAAM,aAAa,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,EAAE,WAAW,MAAM,KAAG,MAC7B,CAAC;AAEpD;;;;;;;GAOG;AACH,eAAO,MAAM,gBAAgB,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACf,CAAC;AAElD;;;;GAIG;AACH,eAAO,MAAM,SAAS,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,EAAE,aAAa,MAAM,KAAG,MACzB,CAAC;AAEtD;;;;GAIG;AACH,eAAO,MAAM,gBAAgB,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACT,CAAC;AAExD;;;;;GAKG;AACH,eAAO,MAAM,sBAAsB,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACT,CAAC;AAE9D;;;;;;GAMG;AACH,eAAO,MAAM,mBAAmB,GAAI,MAAM,MAAM,EAAE,QAAQ,MAAM,KAAG,MACd,CAAC;AAEtD;;;;;GAKG;AACH,eAAO,MAAM,WAAW,GAAI,cAAc,MAAM,EAAE,WAAW,MAAM,KAAG,MACrB,CAAC;AAElD;;;;;;GAMG;AACH,eAAO,MAAM,4BAA4B,GAAI,MAAM,MAAM,KAAG,MACS,CAAC;AAEtE;;;;;;;;;;;;;;;;;GAiBG;AACH,eAAO,MAAM,4BAA4B,GAAI,MAAM,MAAM,EAAE,gBAAgB,MAAM,KAAG,MACf,CAAC;AAEtE;;;;;;;;;GASG;AACH,eAAO,MAAM,qBAAqB,GAAI,MAAM,MAAM,KAAG,MACQ,CAAC;AAE9D;;;;;GAKG;AACH,eAAO,MAAM,6BAA6B,GAAI,MAAM,MAAM,KAAG,MACD,CAAC;AAE7D;;;;;;GAMG;AACH,eAAO,MAAM,gCAAgC,GAAI,MAAM,MAAM,KAAG,MACZ,CAAC;AAErD;;;;;;;GAOG;AACH,eAAO,MAAM,mCAAmC,GAAI,MAAM,MAAM,KAAG,MACU,CAAC;AAE9E;;;;;;;;GAQG;AACH,eAAO,MAAM,0BAA0B,GAAI,MAAM,MAAM,KAAG,MACS,CAAC;AAEpE;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,4BAA4B,GAAI,MAAM,MAAM,KAAG,MACK,CAAC;AAElE;;;;;;;;;GASG;AACH,eAAO,MAAM,+BAA+B,GAAI,MAAM,MAAM,KAAG,MACN,CAAC;AAE1D;;;;;GAKG;AACH,eAAO,MAAM,YAAY,GAAI,YAAY,MAAM,EAAE,UAAU,MAAM,KAAG,MACtC,CAAC;AAE/B;;;;;GAKG;AACH,eAAO,MAAM,iBAAiB,QAAoC,CAAC;AAEnE;;;;;;;GAOG;AACH,eAAO,MAAM,eAAe,GAAI,MAAM,MAAM,EAAE,SAAS,MAAM,KAAG,MACJ,CAAC;AAE7D;;;;;GAKG;AACH,eAAO,MAAM,yBAAyB,GAAI,MAAM,MAAM,EAAE,SAAS,MAAM,KAAG,MACd,CAAC;AAE7D;;;;;;GAMG;AACH,eAAO,MAAM,+BAA+B,GAAI,MAAM,MAAM,EAAE,SAAS,MAAM,KAAG,MACd,CAAC;AAEnE;;;;;;GAMG;AACH,eAAO,MAAM,4BAA4B,GAAI,MAAM,MAAM,EAAE,SAAS,MAAM,KAAG,MACR,CAAC;AAEtE;;;;GAIG;AACH,eAAO,MAAM,wBAAwB,GAAI,MAAM,MAAM,EAAE,SAAS,MAAM,KAAG,MACK,CAAC;AAE/E;;;;GAIG;AACH,eAAO,MAAM,8BAA8B,GAAI,MAAM,MAAM,EAAE,SAAS,MAAM,KAAG,MACK,CAAC;AAErF;;;;;;;GAOG;AACH,eAAO,MAAM,yBAAyB,GAAI,MAAM,MAAM,EAAE,iBAAiB,MAAM,KAAG,MACf,CAAC;AAEpE;;;;;GAKG;AACH,eAAO,MAAM,+BAA+B,GAAI,MAAM,MAAM,EAAE,iBAAiB,MAAM,KAAG,MACT,CAAC;AAEhF;;;;;GAKG;AACH,eAAO,MAAM,0BAA0B,GAAI,MAAM,MAAM,EAAE,OAAO,MAAM,KAAG,MACX,CAAC;AAE/D;;;;;;GAMG;AACH,eAAO,MAAM,gBAAgB,GAAI,MAAM,MAAM,EAAE,WAAW,MAAM,KAAG,MACF,CAAC;AAElE;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,wBAAwB,GAAI,MAAM,MAAM,EAAE,cAAc,MAAM,KAAG,MACA,CAAC;AAE/E;;;;;GAKG;AACH,eAAO,MAAM,8BAA8B,GAAI,MAAM,MAAM,EAAE,cAAc,MAAM,KAAG,MACT,CAAC;AAE5E;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,0BAA0B,GAAI,MAAM,MAAM,EAAE,WAAW,MAAM,KAAG,MACK,CAAC;AAEnF;;;;GAIG;AACH,eAAO,MAAM,gCAAgC,GAAI,MAAM,MAAM,EAAE,WAAW,MAAM,KAAG,MACT,CAAC;AAE3E;;;;;;GAMG;AACH,eAAO,MAAM,4BAA4B,GAAI,MAAM,MAAM,KAAG,MACK,CAAC;AAElE;;;;;;;;;GASG;AACH,eAAO,MAAM,kBAAkB,GAAI,MAAM,MAAM,KAAG,MACO,CAAC;AAE1D;;;;;;;GAOG;AACH,eAAO,MAAM,gCAAgC,GAAI,MAAM,MAAM,KAAG,MACS,CAAC;AAE1E;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,0CAA0C,GAAI,MAAM,MAAM,KAAG,MACW,CAAC;AAEtF;;;;;;;GAOG;AACH,eAAO,MAAM,4BAA4B,QAA+C,CAAC;AAEzF,eAAO,MAAM,mBAAmB,GAAI,QAAQ,MAAM,KAAG,MACP,CAAC"}