@sitecoreai-labs/sitecoreai-cli 0.0.4

package/dist/recipe/guids.js

@@ -0,0 +1,488 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.componentFolderTemplateId = exports.presentationParametersBucketId = exports.componentFoldersBucketId = exports.availableRenderingsSectionId = exports.headlessVariantsSectionFolderId = exports.renderingsSectionFolderId = exports.sectionFolderId = exports.NAMESPACE_PROJECT = exports.datasourceId = exports.enumerationTemplateValueFieldId = exports.enumerationTemplateSectionId = exports.enumerationValueTemplateId = exports.enumerationTemplateStandardValuesId = exports.enumerationContainerValueFieldId = exports.enumerationContainerSectionId = exports.enumerationTemplateId = exports.enumerationsGroupingFolderId = exports.enumerationsFolderTemplateId = exports.enumValueId = exports.enumerationFolderId = exports.paramsStandardValuesId = exports.standardValuesId = exports.variantId = exports.variantsFolderId = exports.paramsFieldId = exports.paramsSectionId = exports.fieldId = exports.sectionId = exports.PAGE_DESIGNS_ROOT_REF_KEY = exports.taxonomyTagId = exports.taxonomyFolderId = exports.dictionaryPhraseId = exports.siteId = exports.contentItemId = exports.siteBranchId = exports.pageDesignId = exports.partialDesignId = exports.paramsTemplateId = exports.renderingId = exports.templateId = exports._deriveNamespaceRoot = exports.NAMESPACE_ENUMERATION = exports.NAMESPACE_SITE = exports.NAMESPACE_CONTENT_ITEM = exports.NAMESPACE_SITE_BRANCH = exports.NAMESPACE_PAGE_DESIGN = exports.NAMESPACE_PARTIAL_DESIGN = exports.NAMESPACE_RENDERING = exports.NAMESPACE_TEMPLATE = exports.NAMESPACE_ROOT = void 0;
+exports.sectionDefinitionId = exports.NAMESPACE_SECTION_DEFINITION = exports.enumerationsFolderTemplateStandardValuesId = exports.enumerationsRootStandardValuesId = exports.enumerationsRootId = exports.siteDataRootStandardValuesId = exports.sharedDataFolderStandardValuesId = exports.sharedDataFolderTemplateId = exports.siteDataFolderStandardValuesId = exports.siteDataFolderTemplateId = exports.siteDataFolderId = exports.contentModelsGroupFolderId = exports.componentFolderStandardValuesId = void 0;
+const uuid_1 = require("uuid");
+/**
+ * Deterministic GUID derivation for recipe-emitted Sitecore items.
+ *
+ * Every item GUID is a uuidv5 hash of (a kind-namespace, a stable seed).
+ * Same recipe inputs produce the same GUIDs forever — that's how recipe
+ * pushes are idempotent without server-side state.
+ *
+ * The namespacing tree is:
+ *
+ *   DNS                      RFC 4122 DNS namespace
+ *     └── NAMESPACE_ROOT     uuidv5(DNS, "registry.sitecoreai.dev")
+ *           ├── TEMPLATE         uuidv5(ROOT, "template")
+ *           ├── RENDERING        uuidv5(ROOT, "rendering")
+ *           ├── PARTIAL_DESIGN   uuidv5(ROOT, "partial-design")
+ *           ├── PAGE_DESIGN      uuidv5(ROOT, "page-design")
+ *           ├── SITE_BRANCH      uuidv5(ROOT, "site-branch")
+ *           └── CONTENT_ITEM     uuidv5(ROOT, "content-item")
+ *
+ * The `handle` of a recipe (e.g. `cta-button@1`) is load-bearing forever:
+ * a different handle = a different template. Versioning is pinned;
+ * `cta-button@1` → `cta-button@2` is a *new* template.
+ *
+ * Component-shape items (templates, renderings, params templates, partial /
+ * page / content items, component-folder templates and everything chained
+ * off them — fields, sections, variants, standard-values) are also
+ * **site-scoped**. The seed is `<site>::<handle>`, so the same recipe
+ * pushed to two sites produces two distinct sets of items at distinct
+ * paths under each site's `Project/<site>/` subtree. Without this scoping
+ * a second site's push would collide on Sitecore's globally-unique GUID
+ * constraint with the first site's items.
+ */
+/** RFC 4122 DNS namespace. */
+const DNS_NAMESPACE = "6ba7b810-9dad-11d1-80b4-00c04fd430c8";
+/**
+ * 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")`.
+ */
+exports.NAMESPACE_ROOT = "d6c28e9f-21f3-56ee-ada3-f2a947c3d475";
+exports.NAMESPACE_TEMPLATE = (0, uuid_1.v5)("template", exports.NAMESPACE_ROOT);
+exports.NAMESPACE_RENDERING = (0, uuid_1.v5)("rendering", exports.NAMESPACE_ROOT);
+exports.NAMESPACE_PARTIAL_DESIGN = (0, uuid_1.v5)("partial-design", exports.NAMESPACE_ROOT);
+exports.NAMESPACE_PAGE_DESIGN = (0, uuid_1.v5)("page-design", exports.NAMESPACE_ROOT);
+exports.NAMESPACE_SITE_BRANCH = (0, uuid_1.v5)("site-branch", exports.NAMESPACE_ROOT);
+exports.NAMESPACE_CONTENT_ITEM = (0, uuid_1.v5)("content-item", exports.NAMESPACE_ROOT);
+exports.NAMESPACE_SITE = (0, uuid_1.v5)("site", exports.NAMESPACE_ROOT);
+exports.NAMESPACE_ENUMERATION = (0, uuid_1.v5)("enumeration", exports.NAMESPACE_ROOT);
+/** Internal: lets the test prove `NAMESPACE_ROOT` matches its derivation. */
+const _deriveNamespaceRoot = () => (0, uuid_1.v5)("registry.sitecoreai.dev", DNS_NAMESPACE);
+exports._deriveNamespaceRoot = _deriveNamespaceRoot;
+const templateId = (site, handle) => (0, uuid_1.v5)(`${site}::${handle}`, exports.NAMESPACE_TEMPLATE);
+exports.templateId = templateId;
+const renderingId = (site, handle) => (0, uuid_1.v5)(`${site}::${handle}`, exports.NAMESPACE_RENDERING);
+exports.renderingId = renderingId;
+const paramsTemplateId = (site, handle) => (0, uuid_1.v5)(`${site}::${handle}::params`, exports.NAMESPACE_TEMPLATE);
+exports.paramsTemplateId = paramsTemplateId;
+const partialDesignId = (site, handle) => (0, uuid_1.v5)(`${site}::${handle}`, exports.NAMESPACE_PARTIAL_DESIGN);
+exports.partialDesignId = partialDesignId;
+const pageDesignId = (site, handle) => (0, uuid_1.v5)(`${site}::${handle}`, exports.NAMESPACE_PAGE_DESIGN);
+exports.pageDesignId = pageDesignId;
+const siteBranchId = (handle) => (0, uuid_1.v5)(handle, exports.NAMESPACE_SITE_BRANCH);
+exports.siteBranchId = siteBranchId;
+const contentItemId = (site, handle) => (0, uuid_1.v5)(`${site}::${handle}`, exports.NAMESPACE_CONTENT_ITEM);
+exports.contentItemId = contentItemId;
+/**
+ * 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).
+ */
+const siteId = (handle) => (0, uuid_1.v5)(handle, exports.NAMESPACE_SITE);
+exports.siteId = siteId;
+/**
+ * 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.
+ */
+const dictionaryPhraseId = (siteHandle, phraseName) => (0, uuid_1.v5)(`dictionary:${phraseName}`, (0, exports.siteId)(siteHandle));
+exports.dictionaryPhraseId = dictionaryPhraseId;
+/**
+ * Recipe-internal refKey for a taxonomy folder (root) under a site.
+ * Mirror of `dictionaryPhraseId` for the taxonomy tree — late-seeded
+ * after the site materialises.
+ */
+const taxonomyFolderId = (siteHandle, rootName) => (0, uuid_1.v5)(`taxonomy:${rootName}`, (0, exports.siteId)(siteHandle));
+exports.taxonomyFolderId = taxonomyFolderId;
+/**
+ * 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.
+ */
+const taxonomyTagId = (siteHandle, rootName, tagName) => (0, uuid_1.v5)(`tag:${tagName}`, (0, exports.taxonomyFolderId)(siteHandle, rootName));
+exports.taxonomyTagId = taxonomyTagId;
+/**
+ * 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.
+ */
+exports.PAGE_DESIGNS_ROOT_REF_KEY = (0, uuid_1.v5)("page-designs-root", exports.NAMESPACE_ROOT);
+/** Sections are scoped under their (site-scoped) template; seed `section:<name>`. */
+const sectionId = (site, handle, sectionName) => (0, uuid_1.v5)(`section:${sectionName}`, (0, exports.templateId)(site, handle));
+exports.sectionId = sectionId;
+/** Fields are scoped under their (site-scoped) template; the seed is the field name. */
+const fieldId = (site, handle, fieldName) => (0, uuid_1.v5)(fieldName, (0, exports.templateId)(site, handle));
+exports.fieldId = fieldId;
+/** Sections of the parameters template scope under (site-scoped) `paramsTemplateId`. */
+const paramsSectionId = (site, handle, sectionName) => (0, uuid_1.v5)(`section:${sectionName}`, (0, exports.paramsTemplateId)(site, handle));
+exports.paramsSectionId = paramsSectionId;
+/** Fields of the parameters template scope under (site-scoped) `paramsTemplateId`. */
+const paramsFieldId = (site, handle, fieldName) => (0, uuid_1.v5)(fieldName, (0, exports.paramsTemplateId)(site, handle));
+exports.paramsFieldId = paramsFieldId;
+/**
+ * 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.
+ */
+const variantsFolderId = (site, handle) => (0, uuid_1.v5)("__variants", (0, exports.renderingId)(site, handle));
+exports.variantsFolderId = variantsFolderId;
+/**
+ * Each Variant Definition item lives under the per-rendering
+ * Headless Variants folder. Conforms to SXA's `Variant Definition`
+ * template.
+ */
+const variantId = (site, handle, variantName) => (0, uuid_1.v5)(variantName, (0, exports.variantsFolderId)(site, handle));
+exports.variantId = variantId;
+/**
+ * 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.
+ */
+const standardValuesId = (site, handle) => (0, uuid_1.v5)("__standard-values", (0, exports.templateId)(site, handle));
+exports.standardValuesId = standardValuesId;
+/**
+ * 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.
+ */
+const paramsStandardValuesId = (site, handle) => (0, uuid_1.v5)("__standard-values", (0, exports.paramsTemplateId)(site, handle));
+exports.paramsStandardValuesId = paramsStandardValuesId;
+/**
+ * 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.
+ */
+const enumerationFolderId = (site, handle) => (0, uuid_1.v5)(`${site}::${handle}`, exports.NAMESPACE_ENUMERATION);
+exports.enumerationFolderId = enumerationFolderId;
+/**
+ * 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.
+ */
+const enumValueId = (parentRefKey, valueName) => (0, uuid_1.v5)(`enum-value:${valueName}`, parentRefKey);
+exports.enumValueId = enumValueId;
+/**
+ * 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.
+ */
+const enumerationsFolderTemplateId = (site) => (0, uuid_1.v5)(`${site}::enumerations-folder-template`, exports.NAMESPACE_TEMPLATE);
+exports.enumerationsFolderTemplateId = enumerationsFolderTemplateId;
+/**
+ * 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.
+ */
+const enumerationsGroupingFolderId = (site, cumulativePath) => (0, uuid_1.v5)(`${site}:Enumerations:${cumulativePath}`, exports.NAMESPACE_PROJECT);
+exports.enumerationsGroupingFolderId = enumerationsGroupingFolderId;
+/**
+ * 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`.
+ */
+const enumerationTemplateId = (site) => (0, uuid_1.v5)(`${site}::enumeration-template`, exports.NAMESPACE_TEMPLATE);
+exports.enumerationTemplateId = enumerationTemplateId;
+/**
+ * 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`).
+ */
+const enumerationContainerSectionId = (site) => (0, uuid_1.v5)("section:Enumeration", (0, exports.enumerationTemplateId)(site));
+exports.enumerationContainerSectionId = enumerationContainerSectionId;
+/**
+ * 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.
+ */
+const enumerationContainerValueFieldId = (site) => (0, uuid_1.v5)("field:Value", (0, exports.enumerationTemplateId)(site));
+exports.enumerationContainerValueFieldId = enumerationContainerValueFieldId;
+/**
+ * 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.
+ */
+const enumerationTemplateStandardValuesId = (site) => (0, uuid_1.v5)(`${site}::enumeration-template-standard-values`, exports.NAMESPACE_TEMPLATE);
+exports.enumerationTemplateStandardValuesId = enumerationTemplateStandardValuesId;
+/**
+ * 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.
+ */
+const enumerationValueTemplateId = (site) => (0, uuid_1.v5)(`${site}::enumeration-value-template`, exports.NAMESPACE_TEMPLATE);
+exports.enumerationValueTemplateId = enumerationValueTemplateId;
+/**
+ * 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.
+ */
+const enumerationTemplateSectionId = (site) => (0, uuid_1.v5)("section:Enumeration", (0, exports.enumerationValueTemplateId)(site));
+exports.enumerationTemplateSectionId = enumerationTemplateSectionId;
+/**
+ * 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.
+ */
+const enumerationTemplateValueFieldId = (site) => (0, uuid_1.v5)("field:Value", (0, exports.enumerationValueTemplateId)(site));
+exports.enumerationTemplateValueFieldId = enumerationTemplateValueFieldId;
+/**
+ * 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.
+ */
+const datasourceId = (pageItemId, slotPath) => (0, uuid_1.v5)(slotPath, pageItemId);
+exports.datasourceId = datasourceId;
+/**
+ * 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.
+ */
+exports.NAMESPACE_PROJECT = (0, uuid_1.v5)("project", exports.NAMESPACE_ROOT);
+/**
+ * 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".
+ */
+const sectionFolderId = (site, section) => (0, uuid_1.v5)(`${site}:Components:${section}`, exports.NAMESPACE_PROJECT);
+exports.sectionFolderId = sectionFolderId;
+/**
+ * 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).
+ */
+const renderingsSectionFolderId = (site, section) => (0, uuid_1.v5)(`${site}:Renderings:${section}`, exports.NAMESPACE_PROJECT);
+exports.renderingsSectionFolderId = renderingsSectionFolderId;
+/**
+ * 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.
+ */
+const headlessVariantsSectionFolderId = (site, section) => (0, uuid_1.v5)(`${site}:HeadlessVariants:${section}`, exports.NAMESPACE_PROJECT);
+exports.headlessVariantsSectionFolderId = headlessVariantsSectionFolderId;
+/**
+ * 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.
+ */
+const availableRenderingsSectionId = (site, section) => (0, uuid_1.v5)(`${site}:AvailableRenderings:${section}`, exports.NAMESPACE_PROJECT);
+exports.availableRenderingsSectionId = availableRenderingsSectionId;
+/**
+ * Deterministic refKey for a "Component Folders" subfolder under a
+ * site's `Components/<section>/` — an idempotent parent for the
+ * generated `<Component> Folder` templates.
+ */
+const componentFoldersBucketId = (site, section) => (0, uuid_1.v5)(`${site}:Components:${section}:Component Folders`, exports.NAMESPACE_PROJECT);
+exports.componentFoldersBucketId = componentFoldersBucketId;
+/**
+ * Deterministic refKey for a "Presentation Parameters" subfolder under
+ * a site's `Components/<section>/` — an idempotent parent for
+ * standalone (and synthesised) Parameters templates.
+ */
+const presentationParametersBucketId = (site, section) => (0, uuid_1.v5)(`${site}:Components:${section}:Presentation Parameters`, exports.NAMESPACE_PROJECT);
+exports.presentationParametersBucketId = presentationParametersBucketId;
+/**
+ * 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.
+ */
+const componentFolderTemplateId = (site, componentHandle) => (0, uuid_1.v5)(`${site}::${componentHandle}::folder`, exports.NAMESPACE_TEMPLATE);
+exports.componentFolderTemplateId = componentFolderTemplateId;
+/**
+ * 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.
+ */
+const componentFolderStandardValuesId = (site, componentHandle) => (0, uuid_1.v5)("__standard-values", (0, exports.componentFolderTemplateId)(site, componentHandle));
+exports.componentFolderStandardValuesId = componentFolderStandardValuesId;
+/**
+ * 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.
+ */
+const contentModelsGroupFolderId = (site, group) => (0, uuid_1.v5)(`${site}:Content Models:${group}`, exports.NAMESPACE_PROJECT);
+exports.contentModelsGroupFolderId = contentModelsGroupFolderId;
+/**
+ * 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).
+ */
+const siteDataFolderId = (site, subfolder) => (0, uuid_1.v5)(`${site}::data-folder::${subfolder}`, exports.NAMESPACE_PROJECT);
+exports.siteDataFolderId = siteDataFolderId;
+/**
+ * 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.
+ */
+const siteDataFolderTemplateId = (site, recipeHandle) => (0, uuid_1.v5)(`${site}::${recipeHandle}::data-folder-template`, exports.NAMESPACE_TEMPLATE);
+exports.siteDataFolderTemplateId = siteDataFolderTemplateId;
+/**
+ * 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.
+ */
+const siteDataFolderStandardValuesId = (site, recipeHandle) => (0, uuid_1.v5)("__standard-values", (0, exports.siteDataFolderTemplateId)(site, recipeHandle));
+exports.siteDataFolderStandardValuesId = siteDataFolderStandardValuesId;
+/**
+ * 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.
+ */
+const sharedDataFolderTemplateId = (site, subfolder) => (0, uuid_1.v5)(`${site}::shared-data-folder-template::${subfolder}`, exports.NAMESPACE_TEMPLATE);
+exports.sharedDataFolderTemplateId = sharedDataFolderTemplateId;
+/**
+ * Standard-values item refKey for a shared per-subfolder Data Folder
+ * template. Same `__standard-values` seed pattern as the rest of the
+ * SV family.
+ */
+const sharedDataFolderStandardValuesId = (site, subfolder) => (0, uuid_1.v5)("__standard-values", (0, exports.sharedDataFolderTemplateId)(site, subfolder));
+exports.sharedDataFolderStandardValuesId = sharedDataFolderStandardValuesId;
+/**
+ * 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.
+ */
+const siteDataRootStandardValuesId = (site) => (0, uuid_1.v5)(`${site}::data-root-standard-values`, exports.NAMESPACE_PROJECT);
+exports.siteDataRootStandardValuesId = siteDataRootStandardValuesId;
+/**
+ * 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.
+ */
+const enumerationsRootId = (site) => (0, uuid_1.v5)(`${site}::enumerations-root`, exports.NAMESPACE_PROJECT);
+exports.enumerationsRootId = enumerationsRootId;
+/**
+ * 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.
+ */
+const enumerationsRootStandardValuesId = (site) => (0, uuid_1.v5)(`${site}::enumerations-root-standard-values`, exports.NAMESPACE_PROJECT);
+exports.enumerationsRootStandardValuesId = enumerationsRootStandardValuesId;
+/**
+ * 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.
+ */
+const enumerationsFolderTemplateStandardValuesId = (site) => (0, uuid_1.v5)(`${site}::enumerations-folder-template-standard-values`, exports.NAMESPACE_TEMPLATE);
+exports.enumerationsFolderTemplateStandardValuesId = enumerationsFolderTemplateStandardValuesId;
+/**
+ * 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.
+ */
+exports.NAMESPACE_SECTION_DEFINITION = (0, uuid_1.v5)("section-definition", exports.NAMESPACE_ROOT);
+const sectionDefinitionId = (handle) => (0, uuid_1.v5)(handle, exports.NAMESPACE_SECTION_DEFINITION);
+exports.sectionDefinitionId = sectionDefinitionId;

package/dist/recipe/index.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Public recipe API — `import { ... } from "@sitecoreai-labs/sitecoreai-cli/recipe"`.
+ *
+ * The registry (and any other consumer) imports recipe types and the
+ * compiler from this entry. Internal CLI plumbing (config loading,
+ * commander wiring, GraphQL transport bound to scai's environment shape)
+ * stays in `src/recipe/{tasks,api/graphql,api/authoring-client,io}.ts`
+ * and is NOT re-exported here.
+ *
+ * Stability contract: the surface in this file is the public contract.
+ * Anything not exported here is internal and may move between scai
+ * versions without notice.
+ */
+export { ComponentPlacementSchema, ComponentTemplateRecipeSchema, ContentFieldValueSchema, ContentItemRecipeSchema, ContentTemplateRecipeSchema, FieldDefinitionSchema, LayoutSchema, PageDesignRecipeSchema, ParamDefinitionSchema, ParametersTemplateRecipeSchema, PartialDesignRecipeSchema, PlaceholderDefinitionSchema, RecipeMetaSchema, RecipeSchema, RecipeDatasourceSchema, RenderingDatasourceLocationSchema, RenderingVariantDefinitionSchema, SectionDefinitionRecipeSchema, SiteGroupingSchema, SiteRecipeSchema, SiteTemplateDictionaryEntrySchema, SiteTemplateRecipeSchema, SiteTemplateTaxonomyEntrySchema, SitecoreFieldAugmentSchema, type ComponentPlacement, type ComponentTemplateRecipe, type ContentFieldValue, type ContentItemRecipe, type ContentTemplateRecipe, type FieldDefinition, type Layout, type PageDesignRecipe, type ParamDefinition, type ParametersTemplateRecipe, type PartialDesignRecipe, type PlaceholderDefinition, type Recipe, type RecipeMeta, type RecipeDatasource, type RenderingDatasourceLocation, type RenderingVariantDefinition, type SectionDefinitionRecipe, type SiteGrouping, type SiteRecipe, type SiteTemplateDictionaryEntry, type SiteTemplateRecipe, type SiteTemplateTaxonomyEntry, type SitecoreFieldAugment, } from "./schema/recipe";
+export { FIELD_SHAPES, FieldShapeSchema, SITECORE_FIELD_TYPES, SitecoreFieldTypeSchema, defaultSitecoreFieldType, sitecoreFieldTypeLabel, type FieldShape, type SitecoreFieldType, } from "./schema/field-types";
+export { compileComponentTemplateRecipe, compileContentItemRecipe, compileContentTemplateRecipe, compilePageDesignRecipe, compileParametersTemplateRecipe, compilePartialDesignRecipe, compileRecipe, compileRecipeSet, compileSectionDefinitionRecipe, compileSiteRecipe, compileSiteTemplateRecipe, TEMPLATES_MAPPING_AGGREGATE_HANDLE, type CompileContext, } from "./compile";
+export { emitLayoutXml } from "./layout/emit";
+export type { ComponentPlacementInput, LayoutEmitContext, LayoutInput } from "./layout/emit";
+export { encodeTemplatesMapping, type TemplatesMappingEntry } from "./layout/templates-mapping";
+export { NAMESPACE_CONTENT_ITEM, NAMESPACE_PAGE_DESIGN, NAMESPACE_PARTIAL_DESIGN, NAMESPACE_PROJECT, NAMESPACE_RENDERING, NAMESPACE_ROOT, NAMESPACE_SECTION_DEFINITION, NAMESPACE_SITE_BRANCH, NAMESPACE_TEMPLATE, PAGE_DESIGNS_ROOT_REF_KEY, componentFolderStandardValuesId, componentFolderTemplateId, componentFoldersBucketId, contentItemId, contentModelsGroupFolderId, datasourceId, fieldId, pageDesignId, paramsFieldId, paramsSectionId, paramsTemplateId, partialDesignId, presentationParametersBucketId, renderingId, renderingsSectionFolderId, sectionDefinitionId, sectionFolderId, sectionId, siteBranchId, siteDataFolderId, standardValuesId, templateId, variantId, variantsFolderId, } from "./guids";
+export { AppendToMultiListOpSchema, CreateItemOpSchema, FieldValueSchema, OperationIrSchema, OperationSchema, PushPolicySchema, RefValueSchema, SetBaseTemplatesOpSchema, SetFieldOpSchema, SetStandardValuesOpSchema, type AppendToMultiListOp, type CreateItemOp, type FieldValue, type Operation, type OperationIr, type PushPolicy, type RefValue, type SetBaseTemplatesOp, type SetFieldOp, type SetStandardValuesOp, } from "./ir/operations";
+export { COMPOSITION_FIELDS, DEFAULT_DEVICE_ID, DEFAULT_ICON, DEFAULT_LANGUAGE, DEFAULT_VERSION, LAYOUT_FIELDS, RENDERING_FIELDS, SECTION_DEFINITION_FIELDS, SITE_FIELDS, SITE_TEMPLATE_FIELDS, SITECORE_TEMPLATES, STANDARD_TEMPLATE_ID, SYSTEM_FIELDS, TEMPLATE_FIELD_FIELDS, } from "./ir/sitecore-templates";
+export { buildPlan } from "./plan";
+export type { FieldDiffEntry, Plan, PlanEvent, PlanOptions, PlanSummary, PlannedAction, } from "./plan";
+export { executeIr } from "./execute";
+export type { ExecuteOptions, ExecutionEvent, ExecutionMode, ExecutionResult } from "./execute";
+export type { AuthoringApiClient, CreateItemInput, RemoteFieldValue, RemoteItem, UpdateItemInput, } from "./api/client";
+export { renderRefValue } from "./api/ref-encoding";
+export { renderSourceFields, sourceFieldsNeedHandleResolution, type SourceFields, } from "./schema/source-fields";
+export { defaultPolicyForRecipe, policyFor, policyForOp, purposeForRecipe, type OpPurpose, } from "./policy";
+export { formatValidationErrors, isValid, validateRecipeSet, validateRecipeSetOrThrow, type CyclicReference, type DuplicateHandle, type FieldShapeError, type RecipeKind, type UnresolvedHandle, type ValidationResult, } from "./validate";
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/recipe/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAGH,OAAO,EACL,wBAAwB,EACxB,6BAA6B,EAC7B,uBAAuB,EACvB,uBAAuB,EACvB,2BAA2B,EAC3B,qBAAqB,EACrB,YAAY,EACZ,sBAAsB,EACtB,qBAAqB,EACrB,8BAA8B,EAC9B,yBAAyB,EACzB,2BAA2B,EAC3B,gBAAgB,EAChB,YAAY,EACZ,sBAAsB,EACtB,iCAAiC,EACjC,gCAAgC,EAChC,6BAA6B,EAC7B,kBAAkB,EAClB,gBAAgB,EAChB,iCAAiC,EACjC,wBAAwB,EACxB,+BAA+B,EAC/B,0BAA0B,EAC1B,KAAK,kBAAkB,EACvB,KAAK,uBAAuB,EAC5B,KAAK,iBAAiB,EACtB,KAAK,iBAAiB,EACtB,KAAK,qBAAqB,EAC1B,KAAK,eAAe,EACpB,KAAK,MAAM,EACX,KAAK,gBAAgB,EACrB,KAAK,eAAe,EACpB,KAAK,wBAAwB,EAC7B,KAAK,mBAAmB,EACxB,KAAK,qBAAqB,EAC1B,KAAK,MAAM,EACX,KAAK,UAAU,EACf,KAAK,gBAAgB,EACrB,KAAK,2BAA2B,EAChC,KAAK,0BAA0B,EAC/B,KAAK,uBAAuB,EAC5B,KAAK,YAAY,EACjB,KAAK,UAAU,EACf,KAAK,2BAA2B,EAChC,KAAK,kBAAkB,EACvB,KAAK,yBAAyB,EAC9B,KAAK,oBAAoB,GAC1B,MAAM,iBAAiB,CAAC;AAEzB,OAAO,EACL,YAAY,EACZ,gBAAgB,EAChB,oBAAoB,EACpB,uBAAuB,EACvB,wBAAwB,EACxB,sBAAsB,EACtB,KAAK,UAAU,EACf,KAAK,iBAAiB,GACvB,MAAM,sBAAsB,CAAC;AAG9B,OAAO,EACL,8BAA8B,EAC9B,wBAAwB,EACxB,4BAA4B,EAC5B,uBAAuB,EACvB,+BAA+B,EAC/B,0BAA0B,EAC1B,aAAa,EACb,gBAAgB,EAChB,8BAA8B,EAC9B,iBAAiB,EACjB,yBAAyB,EACzB,kCAAkC,EAClC,KAAK,cAAc,GACpB,MAAM,WAAW,CAAC;AAEnB,OAAO,EAAE,aAAa,EAAE,MAAM,eAAe,CAAC;AAC9C,YAAY,EAAE,uBAAuB,EAAE,iBAAiB,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAE7F,OAAO,EAAE,sBAAsB,EAAE,KAAK,qBAAqB,EAAE,MAAM,4BAA4B,CAAC;AAGhG,OAAO,EACL,sBAAsB,EACtB,qBAAqB,EACrB,wBAAwB,EACxB,iBAAiB,EACjB,mBAAmB,EACnB,cAAc,EACd,4BAA4B,EAC5B,qBAAqB,EACrB,kBAAkB,EAClB,yBAAyB,EACzB,+BAA+B,EAC/B,yBAAyB,EACzB,wBAAwB,EACxB,aAAa,EACb,0BAA0B,EAC1B,YAAY,EACZ,OAAO,EACP,YAAY,EACZ,aAAa,EACb,eAAe,EACf,gBAAgB,EAChB,eAAe,EACf,8BAA8B,EAC9B,WAAW,EACX,yBAAyB,EACzB,mBAAmB,EACnB,eAAe,EACf,SAAS,EACT,YAAY,EACZ,gBAAgB,EAChB,gBAAgB,EAChB,UAAU,EACV,SAAS,EACT,gBAAgB,GACjB,MAAM,SAAS,CAAC;AAGjB,OAAO,EACL,yBAAyB,EACzB,kBAAkB,EAClB,gBAAgB,EAChB,iBAAiB,EACjB,eAAe,EACf,gBAAgB,EAChB,cAAc,EACd,wBAAwB,EACxB,gBAAgB,EAChB,yBAAyB,EACzB,KAAK,mBAAmB,EACxB,KAAK,YAAY,EACjB,KAAK,UAAU,EACf,KAAK,SAAS,EACd,KAAK,WAAW,EAChB,KAAK,UAAU,EACf,KAAK,QAAQ,EACb,KAAK,kBAAkB,EACvB,KAAK,UAAU,EACf,KAAK,mBAAmB,GACzB,MAAM,iBAAiB,CAAC;AAEzB,OAAO,EACL,kBAAkB,EAClB,iBAAiB,EACjB,YAAY,EACZ,gBAAgB,EAChB,eAAe,EACf,aAAa,EACb,gBAAgB,EAChB,yBAAyB,EACzB,WAAW,EACX,oBAAoB,EACpB,kBAAkB,EAClB,oBAAoB,EACpB,aAAa,EACb,qBAAqB,GACtB,MAAM,yBAAyB,CAAC;AAGjC,OAAO,EAAE,SAAS,EAAE,MAAM,QAAQ,CAAC;AACnC,YAAY,EACV,cAAc,EACd,IAAI,EACJ,SAAS,EACT,WAAW,EACX,WAAW,EACX,aAAa,GACd,MAAM,QAAQ,CAAC;AAEhB,OAAO,EAAE,SAAS,EAAE,MAAM,WAAW,CAAC;AACtC,YAAY,EAAE,cAAc,EAAE,cAAc,EAAE,aAAa,EAAE,eAAe,EAAE,MAAM,WAAW,CAAC;AAGhG,YAAY,EACV,kBAAkB,EAClB,eAAe,EACf,gBAAgB,EAChB,UAAU,EACV,eAAe,GAChB,MAAM,cAAc,CAAC;AAGtB,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AAGpD,OAAO,EACL,kBAAkB,EAClB,gCAAgC,EAChC,KAAK,YAAY,GAClB,MAAM,wBAAwB,CAAC;AAGhC,OAAO,EACL,sBAAsB,EACtB,SAAS,EACT,WAAW,EACX,gBAAgB,EAChB,KAAK,SAAS,GACf,MAAM,UAAU,CAAC;AAGlB,OAAO,EACL,sBAAsB,EACtB,OAAO,EACP,iBAAiB,EACjB,wBAAwB,EACxB,KAAK,eAAe,EACpB,KAAK,eAAe,EACpB,KAAK,eAAe,EACpB,KAAK,UAAU,EACf,KAAK,gBAAgB,EACrB,KAAK,gBAAgB,GACtB,MAAM,YAAY,CAAC"}