@sitecoreai-labs/sitecoreai-cli 0.0.4

package/dist/recipe/compile/site-template.d.ts

@@ -0,0 +1,52 @@
+import { type OperationIr } from "../ir/operations";
+import { type SiteTemplateRecipe } from "../schema/recipe";
+import { type CompileContext } from "./shared";
+/**
+ * Compile a `SiteTemplateRecipe` to an Operation IR.
+ *
+ * Phase 5 Milestone C-extra refinement — emits the SiteTemplate item
+ * (a `Solution template`-typed item under `siteTemplatesRoot`) with
+ * the fields SXA's createSite flow actually reads: Name, Description,
+ * Enabled, Built-in template marker, plus stub ICON / DISPLAY_NAME.
+ *
+ * **Design gap (acknowledged, not closed by this commit):** the
+ * `SiteTemplateRecipe` schema models brand shape as direct lists of
+ * page templates, page designs, an insert-options matrix, a
+ * templates-to-designs mapping, dictionary entries, and taxonomy
+ * roots. SXA's Solution template doesn't carry any of those directly
+ * — it carries a `Site Modules` + `Tenant Modules` list of MODULE
+ * item refs, and modules hold the brand structure. Mapping the
+ * recipe schema's high-level fields to SXA modules is open work
+ * (probably needs a `ModuleRecipe` kind, or a "modules" array on
+ * SiteTemplateRecipe that resolves to existing module item GUIDs).
+ *
+ * Sandbox introspection (2026-05-01) confirmed:
+ *   - SXA "Site Template" = item conforming to `Solution template`
+ *     (templateId 1b2dfd3b-f2f2-4f40-a75c-f6c2490919c4)
+ *   - Built-in templates live at `/sitecore/system/Settings/Foundation/
+ *     JSS Experience Accelerator/Scaffolding/Templates`
+ *   - Field GUIDs captured in SITE_TEMPLATE_FIELDS (sitecore-templates.ts)
+ *
+ * What this commit emits:
+ *   - CreateItem with the correct `templateOf` GUID
+ *   - SetField for Name (Solution-template's `Name` field, not __Display Name)
+ *   - SetField for Description (when recipe.description is set)
+ *   - SetField for Enabled = "1"
+ *   - SetField for Built-in template = "0" (recipe-authored, not SXA-shipped)
+ *
+ * Deferred to a follow-up plan revision (because the recipe-schema-to-
+ * SXA-modules mapping needs design):
+ *   - Site Modules / Tenant Modules SetFields populated from the recipe's
+ *     pageTemplates / pageDesigns / etc. (currently they need to map to
+ *     existing module item GUIDs, which we don't yet)
+ *   - Dictionary subitems (live under <site>/Dictionary, not under
+ *     the site template; they're per-site, not per-template)
+ *   - Taxonomy: no per-site Taxonomy folder found on the sandbox; the
+ *     SXA convention may put taxonomy elsewhere or it may not be a
+ *     site-template concern
+ *
+ * Identity: `templateId(handle)` derives the SiteTemplate item's
+ * deterministic refKey.
+ */
+export declare function compileSiteTemplateRecipe(input: SiteTemplateRecipe, context: CompileContext): OperationIr;
+//# sourceMappingURL=site-template.d.ts.map

package/dist/recipe/compile/site-template.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"site-template.d.ts","sourceRoot":"","sources":["../../../src/recipe/compile/site-template.ts"],"names":[],"mappings":"AAEA,OAAO,EAGL,KAAK,WAAW,EAGjB,MAAM,kBAAkB,CAAC;AAQ1B,OAAO,EAAE,KAAK,kBAAkB,EAA4B,MAAM,kBAAkB,CAAC;AACrF,OAAO,EAAiD,KAAK,cAAc,EAAE,MAAM,UAAU,CAAC;AAE9F;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8CG;AACH,wBAAgB,yBAAyB,CACvC,KAAK,EAAE,kBAAkB,EACzB,OAAO,EAAE,cAAc,GACtB,WAAW,CA6Fb"}

package/dist/recipe/compile/site-template.js

@@ -0,0 +1,140 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.compileSiteTemplateRecipe = compileSiteTemplateRecipe;
+const errors_1 = require("../../shared/errors");
+const guids_1 = require("../guids");
+const operations_1 = require("../ir/operations");
+const policy_1 = require("../policy");
+const sitecore_templates_1 = require("../ir/sitecore-templates");
+const recipe_1 = require("../schema/recipe");
+const shared_1 = require("./shared");
+/**
+ * Compile a `SiteTemplateRecipe` to an Operation IR.
+ *
+ * Phase 5 Milestone C-extra refinement — emits the SiteTemplate item
+ * (a `Solution template`-typed item under `siteTemplatesRoot`) with
+ * the fields SXA's createSite flow actually reads: Name, Description,
+ * Enabled, Built-in template marker, plus stub ICON / DISPLAY_NAME.
+ *
+ * **Design gap (acknowledged, not closed by this commit):** the
+ * `SiteTemplateRecipe` schema models brand shape as direct lists of
+ * page templates, page designs, an insert-options matrix, a
+ * templates-to-designs mapping, dictionary entries, and taxonomy
+ * roots. SXA's Solution template doesn't carry any of those directly
+ * — it carries a `Site Modules` + `Tenant Modules` list of MODULE
+ * item refs, and modules hold the brand structure. Mapping the
+ * recipe schema's high-level fields to SXA modules is open work
+ * (probably needs a `ModuleRecipe` kind, or a "modules" array on
+ * SiteTemplateRecipe that resolves to existing module item GUIDs).
+ *
+ * Sandbox introspection (2026-05-01) confirmed:
+ *   - SXA "Site Template" = item conforming to `Solution template`
+ *     (templateId 1b2dfd3b-f2f2-4f40-a75c-f6c2490919c4)
+ *   - Built-in templates live at `/sitecore/system/Settings/Foundation/
+ *     JSS Experience Accelerator/Scaffolding/Templates`
+ *   - Field GUIDs captured in SITE_TEMPLATE_FIELDS (sitecore-templates.ts)
+ *
+ * What this commit emits:
+ *   - CreateItem with the correct `templateOf` GUID
+ *   - SetField for Name (Solution-template's `Name` field, not __Display Name)
+ *   - SetField for Description (when recipe.description is set)
+ *   - SetField for Enabled = "1"
+ *   - SetField for Built-in template = "0" (recipe-authored, not SXA-shipped)
+ *
+ * Deferred to a follow-up plan revision (because the recipe-schema-to-
+ * SXA-modules mapping needs design):
+ *   - Site Modules / Tenant Modules SetFields populated from the recipe's
+ *     pageTemplates / pageDesigns / etc. (currently they need to map to
+ *     existing module item GUIDs, which we don't yet)
+ *   - Dictionary subitems (live under <site>/Dictionary, not under
+ *     the site template; they're per-site, not per-template)
+ *   - Taxonomy: no per-site Taxonomy folder found on the sandbox; the
+ *     SXA convention may put taxonomy elsewhere or it may not be a
+ *     site-template concern
+ *
+ * Identity: `templateId(handle)` derives the SiteTemplate item's
+ * deterministic refKey.
+ */
+function compileSiteTemplateRecipe(input, context) {
+    const recipe = recipe_1.SiteTemplateRecipeSchema.parse(input);
+    if (!context.siteTemplatesRoot) {
+        throw (0, errors_1.createCliError)(`compileSiteTemplateRecipe requires context.siteTemplatesRoot; tenant-side path missing for recipe ${recipe.handle}`, "INPUT_INVALID");
+    }
+    const operations = [];
+    const policy = (0, policy_1.defaultPolicyForRecipe)(recipe.kind);
+    const itemRefKey = (0, guids_1.templateId)((0, shared_1.siteOf)(context), recipe.handle);
+    const itemPath = (0, shared_1.joinPath)(context.siteTemplatesRoot, recipe.name);
+    operations.push({
+        op: "CreateItem",
+        policy,
+        label: `site-template:${recipe.handle}`,
+        id: itemRefKey,
+        path: itemPath,
+        parent: { kind: "ref-path", value: context.siteTemplatesRoot },
+        templateOf: sitecore_templates_1.SITECORE_TEMPLATES.SITE_TEMPLATE,
+        name: recipe.name,
+        fields: [
+            (0, shared_1.sharedField)(sitecore_templates_1.SYSTEM_FIELDS.ICON, { kind: "string", value: recipe.icon ?? sitecore_templates_1.DEFAULT_ICON }),
+            (0, shared_1.versionedField)(sitecore_templates_1.SYSTEM_FIELDS.DISPLAY_NAME, { kind: "string", value: recipe.displayName }),
+        ],
+    });
+    // Solution template's own `Name` field — distinct from __Display Name.
+    // SXA's Sites UI reads this for the template chooser.
+    operations.push({
+        op: "SetField",
+        policy,
+        label: `site-template-name:${recipe.handle}`,
+        itemRefKey,
+        fieldId: sitecore_templates_1.SITE_TEMPLATE_FIELDS.NAME,
+        value: { kind: "string", value: recipe.displayName },
+    });
+    if (recipe.description) {
+        operations.push({
+            op: "SetField",
+            policy,
+            label: `site-template-description:${recipe.handle}`,
+            itemRefKey,
+            fieldId: sitecore_templates_1.SITE_TEMPLATE_FIELDS.DESCRIPTION,
+            value: { kind: "string", value: recipe.description },
+        });
+    }
+    // Available for site creation by default.
+    operations.push({
+        op: "SetField",
+        policy,
+        label: `site-template-enabled:${recipe.handle}`,
+        itemRefKey,
+        fieldId: sitecore_templates_1.SITE_TEMPLATE_FIELDS.ENABLED,
+        value: { kind: "string", value: "1" },
+    });
+    // "Built-in" is a marker for SXA-shipped templates — recipe-authored
+    // ones explicitly mark themselves as not built-in so the Sites UI can
+    // distinguish operator-authored brand templates from the canned ones.
+    operations.push({
+        op: "SetField",
+        policy,
+        label: `site-template-builtin:${recipe.handle}`,
+        itemRefKey,
+        fieldId: sitecore_templates_1.SITE_TEMPLATE_FIELDS.BUILT_IN_TEMPLATE,
+        value: { kind: "string", value: "0" },
+    });
+    // TODO (next plan revision — needs design):
+    //   - Module resolution. SXA stores brand structure in MODULES, not
+    //     directly on the Solution template. recipe.pageTemplates,
+    //     recipe.pageDesigns, recipe.insertOptionsMatrix,
+    //     recipe.templatesToDesigns map to module composition that this
+    //     compiler doesn't yet model. Site Modules + Tenant Modules
+    //     SetFields would carry pipe-separated module-item GUIDs once
+    //     the schema gains a module-references field (or a separate
+    //     ModuleRecipe kind that the compiler can resolve to GUIDs).
+    //   - Dictionary entries. Per-site Dictionary lives under
+    //     <site>/Dictionary, not under the site template. SiteRecipe
+    //     compile (Milestone D) is the right place to set those.
+    //   - Taxonomy. No per-site Taxonomy folder discovered on the
+    //     sandbox; the SXA convention isn't clear yet. Defer.
+    return operations_1.OperationIrSchema.parse({
+        schemaVersion: "1",
+        recipeHandle: recipe.handle,
+        operations,
+    });
+}

package/dist/recipe/compile/site.d.ts

@@ -0,0 +1,44 @@
+import { type OperationIr } from "../ir/operations";
+import { type SiteRecipe } from "../schema/recipe";
+import { type CompileContext } from "./shared";
+/**
+ * Compile a `SiteRecipe` to an Operation IR.
+ *
+ * Phase 5 Milestone E — emits a single `CreateSiteFromTemplate` op
+ * that the executor dispatches through the Sites API. The
+ * `SiteTemplateRecipe` it references is identified via deterministic
+ * `templateId(siteTemplate)`; the executor resolves that refKey to
+ * the SiteTemplate's actual Sitecore itemId via cross-recipe ref
+ * pre-seeding (push.ts walks every recipe's `CreateItem` ops and
+ * seeds `crossRecipeRefs[refKey] = path`, then the executor's
+ * `seedCrossRecipeRefs` calls `getItem({path})` once per push to
+ * populate `capturedItemIds`).
+ *
+ * **Validates** (compile-time, not zod-level):
+ *   - Exactly one of `collectionId` / `collectionName` is present.
+ *
+ * **Override emission (Milestone E v2):**
+ *   - Dictionary overrides emit one `SetField` op per phrase, targeting
+ *     `<collectionPath>/<siteName>/Dictionary/<phrase>`. Each op carries a
+ *     `latePath` so the executor's pre-switch lookup seeds the captured
+ *     itemId after `CreateSiteFromTemplate` materialises the site's
+ *     content tree (SXA's Site Wizard creates the Dictionary folder +
+ *     phrase items mid-push).
+ *   - Path composition needs the collection's content-tree path. The
+ *     compiler resolves it in this priority:
+ *       1. `recipe.collectionPath` (operator-supplied — explicit truth)
+ *       2. `/sitecore/content/<collectionName>` when only collectionName
+ *          is set (SXA default; new collections land at this path)
+ *     For `collectionId` callers without `collectionPath`, the compiler
+ *     CAN'T derive the path (would need a Sites API lookup at compile
+ *     time, which the compiler doesn't do). Override emission is
+ *     skipped silently — the site still gets created; operators add
+ *     `collectionPath` when they want overrides applied.
+ *
+ * **Still deferred (E v3+):**
+ *   - Taxonomy overrides as a mix of SetField (existing tags) and
+ *     CreateItem (new tags). The SXA taxonomy convention is still under
+ *     sandbox investigation; defer until verified.
+ */
+export declare function compileSiteRecipe(input: SiteRecipe, context: CompileContext): OperationIr;
+//# sourceMappingURL=site.d.ts.map

package/dist/recipe/compile/site.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"site.d.ts","sourceRoot":"","sources":["../../../src/recipe/compile/site.ts"],"names":[],"mappings":"AAEA,OAAO,EAGL,KAAK,WAAW,EAGjB,MAAM,kBAAkB,CAAC;AAG1B,OAAO,EAAE,KAAK,UAAU,EAAoB,MAAM,kBAAkB,CAAC;AACrE,OAAO,EAAU,KAAK,cAAc,EAAE,MAAM,UAAU,CAAC;AAEvD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsCG;AACH,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,UAAU,EAAE,OAAO,EAAE,cAAc,GAAG,WAAW,CAgEzF"}

package/dist/recipe/compile/site.js

@@ -0,0 +1,127 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.compileSiteRecipe = compileSiteRecipe;
+const errors_1 = require("../../shared/errors");
+const guids_1 = require("../guids");
+const operations_1 = require("../ir/operations");
+const policy_1 = require("../policy");
+const sitecore_templates_1 = require("../ir/sitecore-templates");
+const recipe_1 = require("../schema/recipe");
+const shared_1 = require("./shared");
+/**
+ * Compile a `SiteRecipe` to an Operation IR.
+ *
+ * Phase 5 Milestone E — emits a single `CreateSiteFromTemplate` op
+ * that the executor dispatches through the Sites API. The
+ * `SiteTemplateRecipe` it references is identified via deterministic
+ * `templateId(siteTemplate)`; the executor resolves that refKey to
+ * the SiteTemplate's actual Sitecore itemId via cross-recipe ref
+ * pre-seeding (push.ts walks every recipe's `CreateItem` ops and
+ * seeds `crossRecipeRefs[refKey] = path`, then the executor's
+ * `seedCrossRecipeRefs` calls `getItem({path})` once per push to
+ * populate `capturedItemIds`).
+ *
+ * **Validates** (compile-time, not zod-level):
+ *   - Exactly one of `collectionId` / `collectionName` is present.
+ *
+ * **Override emission (Milestone E v2):**
+ *   - Dictionary overrides emit one `SetField` op per phrase, targeting
+ *     `<collectionPath>/<siteName>/Dictionary/<phrase>`. Each op carries a
+ *     `latePath` so the executor's pre-switch lookup seeds the captured
+ *     itemId after `CreateSiteFromTemplate` materialises the site's
+ *     content tree (SXA's Site Wizard creates the Dictionary folder +
+ *     phrase items mid-push).
+ *   - Path composition needs the collection's content-tree path. The
+ *     compiler resolves it in this priority:
+ *       1. `recipe.collectionPath` (operator-supplied — explicit truth)
+ *       2. `/sitecore/content/<collectionName>` when only collectionName
+ *          is set (SXA default; new collections land at this path)
+ *     For `collectionId` callers without `collectionPath`, the compiler
+ *     CAN'T derive the path (would need a Sites API lookup at compile
+ *     time, which the compiler doesn't do). Override emission is
+ *     skipped silently — the site still gets created; operators add
+ *     `collectionPath` when they want overrides applied.
+ *
+ * **Still deferred (E v3+):**
+ *   - Taxonomy overrides as a mix of SetField (existing tags) and
+ *     CreateItem (new tags). The SXA taxonomy convention is still under
+ *     sandbox investigation; defer until verified.
+ */
+function compileSiteRecipe(input, context) {
+    const recipe = recipe_1.SiteRecipeSchema.parse(input);
+    const hasCollectionId = recipe.collectionId !== undefined;
+    const hasCollectionName = recipe.collectionName !== undefined;
+    if (hasCollectionId === hasCollectionName) {
+        throw (0, errors_1.createCliError)(`SiteRecipe '${recipe.handle}' must specify exactly one of collectionId / collectionName, not ${hasCollectionId ? "both" : "neither"}.`, "INPUT_INVALID");
+    }
+    const policy = (0, policy_1.defaultPolicyForRecipe)(recipe.kind);
+    const siteRefKey = (0, guids_1.siteId)(recipe.handle);
+    const templateRefKey = (0, guids_1.templateId)((0, shared_1.siteOf)(context), recipe.siteTemplate);
+    const operations = [
+        {
+            op: "CreateSiteFromTemplate",
+            policy,
+            label: `site:${recipe.handle}`,
+            siteRefKey,
+            siteName: recipe.name,
+            ...(recipe.displayName !== undefined && { displayName: recipe.displayName }),
+            ...(recipe.description !== undefined && { description: recipe.description }),
+            language: recipe.language,
+            ...(recipe.languages !== undefined && { additionalLanguages: recipe.languages }),
+            ...(recipe.siteGrouping?.hostName !== undefined && {
+                hostName: recipe.siteGrouping.hostName,
+            }),
+            templateRefKey,
+            ...(recipe.collectionId !== undefined && { collectionId: recipe.collectionId }),
+            ...(recipe.collectionName !== undefined && { collectionName: recipe.collectionName }),
+            ...(recipe.collectionDisplayName !== undefined && {
+                collectionDisplayName: recipe.collectionDisplayName,
+            }),
+            ...(recipe.collectionDescription !== undefined && {
+                collectionDescription: recipe.collectionDescription,
+            }),
+        },
+    ];
+    // Resolve the site's content-tree path for late-path composition on
+    // dictionary override ops. See docstring for resolution priority.
+    const sitePath = resolveSiteContentTreePath(recipe);
+    if (sitePath && recipe.dictionaryOverrides) {
+        for (const [phrase, value] of Object.entries(recipe.dictionaryOverrides)) {
+            operations.push({
+                op: "SetField",
+                policy,
+                label: `dictionary-override:${recipe.handle}/${phrase}`,
+                itemRefKey: (0, guids_1.dictionaryPhraseId)(recipe.handle, phrase),
+                fieldId: sitecore_templates_1.DICTIONARY_ENTRY_FIELDS.PHRASE,
+                value: { kind: "string", value },
+                latePath: `${sitePath}/Dictionary/${phrase}`,
+            });
+        }
+    }
+    return operations_1.OperationIrSchema.parse({
+        schemaVersion: "1",
+        recipeHandle: recipe.handle,
+        operations,
+    });
+}
+/**
+ * Resolve the Sitecore content-tree path of a SiteRecipe's site item.
+ * Returns `undefined` when no path can be derived — the caller should
+ * skip override emission rather than guess.
+ *
+ *   1. operator-supplied `recipe.collectionPath` (always wins)
+ *   2. `/sitecore/content/<collectionName>` when only collectionName is set
+ *   3. `undefined` for collectionId-only without collectionPath
+ *
+ * The trailing `/` is trimmed defensively from operator input.
+ */
+const resolveSiteContentTreePath = (recipe) => {
+    if (recipe.collectionPath) {
+        const trimmed = recipe.collectionPath.replace(/\/+$/, "");
+        return `${trimmed}/${recipe.name}`;
+    }
+    if (recipe.collectionName) {
+        return `/sitecore/content/${recipe.collectionName}/${recipe.name}`;
+    }
+    return undefined;
+};

package/dist/recipe/compile.d.ts

@@ -0,0 +1,93 @@
+import { type OperationIr } from "./ir/operations";
+import { type Recipe } from "./schema/recipe";
+import { compileComponentSectionRecipe } from "./compile/component-section";
+import { compileComponentTemplateRecipe } from "./compile/component-template";
+import { compileContentTemplateRecipe } from "./compile/content-template";
+import { compileParametersTemplateRecipe } from "./compile/parameters-template";
+import { compileSectionDefinitionRecipe } from "./compile/section-definition";
+import { compilePartialDesignRecipe } from "./compile/partial-design";
+import { compilePageDesignRecipe } from "./compile/page-design";
+import { compileContentItemRecipe } from "./compile/content-item";
+import { compileSiteTemplateRecipe } from "./compile/site-template";
+import { compileSiteRecipe } from "./compile/site";
+import { compileEnumerationRecipe } from "./compile/enumeration";
+import { type CompileContext } from "./compile/shared";
+export { compileComponentSectionRecipe, compileComponentTemplateRecipe, compileContentTemplateRecipe, compileParametersTemplateRecipe, compileSectionDefinitionRecipe, compilePartialDesignRecipe, compilePageDesignRecipe, compileContentItemRecipe, compileSiteTemplateRecipe, compileSiteRecipe, compileEnumerationRecipe, };
+export type { CompileContext } from "./compile/shared";
+/**
+ * Stable handle for the synthetic IR `compileRecipeSet` emits to write
+ * the cross-recipe `TemplatesMapping` aggregate. Not a real recipe — the
+ * leading double-underscore signals "compiler-synthesized" and avoids
+ * collision with any author-defined handle (recipe handles match
+ * `[a-z][a-z0-9-]*@\d+`, so a leading underscore is unrepresentable).
+ */
+export declare const TEMPLATES_MAPPING_AGGREGATE_HANDLE = "__templates-mapping__";
+/**
+ * Stable handle for the synthetic IR `compileRecipeSet` emits to
+ * materialise the per-section `Available Renderings` items. Same
+ * compiler-synthesized convention as `TEMPLATES_MAPPING_AGGREGATE_HANDLE`.
+ */
+export declare const AVAILABLE_RENDERINGS_AGGREGATE_HANDLE = "__available-renderings__";
+/**
+ * Stable handle for the synthetic IR `compileRecipeSet` emits to
+ * materialise SHARED Data Folder templates — one per `(site, subfolder)`
+ * targeted by ≥2 component-template recipes in the set. Each shared
+ * template's `__Standard Values` Insert Options is the union of every
+ * contributing recipe's datasource template, so a CMS author
+ * right-clicking → Insert in (e.g.) `Site Shared UI/Badges` sees the
+ * full set of legitimately-allowed shapes (Badge + StatusPill + Tag).
+ *
+ * Same `__…__` compiler-synthesized convention as the other aggregate
+ * handles in this file.
+ */
+export declare const SHARED_DATA_FOLDERS_AGGREGATE_HANDLE = "__shared-data-folders__";
+/**
+ * Stable handle for the synthetic IR `compileRecipeSet` emits to
+ * materialise the site Data folder ROOT's `__Standard Values` item +
+ * Insert Options aggregate. The SV restricts right-click → Insert at
+ * `<contentItemsRoot>` to: the generic Folder template, every
+ * per-recipe `<Component> Data Folder` template (singletons), and
+ * every shared `<subfolder> Data Folder` template (coalesced shared
+ * subfolders).
+ *
+ * Same `__…__` compiler-synthesized convention as the other aggregate
+ * handles in this file.
+ */
+export declare const SITE_DATA_ROOT_AGGREGATE_HANDLE = "__site-data-root__";
+/**
+ * Stable handle for the synthetic IR `compileRecipeSet` emits to
+ * materialise the enumerations root's `__Standard Values` item +
+ * Insert Options aggregate. The SV restricts right-click → Insert at
+ * `<enumerationsRoot>` to: the generic Folder template, plus every
+ * per-recipe enumeration folder template (which is the per-site
+ * `Enumerations Folder` template — but the aggregate lists each
+ * `enumerationFolderId(site, handle)` so the shape mirrors the site
+ * data root aggregator and stays consistent if we ever introduce
+ * per-recipe enumeration folder templates).
+ */
+export declare const ENUMERATIONS_ROOT_AGGREGATE_HANDLE = "__enumerations-root__";
+/**
+ * Compile a coherent set of recipes to a list of Operation IRs.
+ *
+ * Returns one IR per recipe (via `compileRecipe`), plus, when any
+ * `PageDesignRecipe` in the set declares `appliesTo`, a final synthetic
+ * IR whose only op is the combined `SetField(TemplatesMapping)` write
+ * on the Page Designs root.
+ *
+ * The TemplatesMapping field is cross-recipe by nature — every page
+ * design contributes one entry per applies-to template, and the field
+ * stores the union. Aggregating at compile time keeps the executor
+ * untouched (one full-replace write of the union) and gives reviewers
+ * a single combined op to inspect rather than N piecewise overwrites.
+ *
+ * Entries are sorted by `templateGuid` for deterministic output — the
+ * IR is the comparable artifact, so order must not depend on input
+ * recipe order. Within a single applies-to template, "last design
+ * wins" is enforced by sorting (later entries with the same key
+ * overwrite earlier ones), but that's a pathological config the
+ * cross-recipe validator should already flag.
+ */
+export declare function compileRecipeSet(recipes: readonly Recipe[], context: CompileContext): OperationIr[];
+/** Front-door dispatcher — accepts any registered recipe kind. */
+export declare function compileRecipe(input: Recipe, context: CompileContext): OperationIr;
+//# sourceMappingURL=compile.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"compile.d.ts","sourceRoot":"","sources":["../../src/recipe/compile.ts"],"names":[],"mappings":"AAcA,OAAO,EAGL,KAAK,WAAW,EAKjB,MAAM,iBAAiB,CAAC;AAWzB,OAAO,EAAE,KAAK,MAAM,EAAgB,MAAM,iBAAiB,CAAC;AAG5D,OAAO,EAAE,6BAA6B,EAAE,MAAM,6BAA6B,CAAC;AAC5E,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,4BAA4B,EAAE,MAAM,4BAA4B,CAAC;AAC1E,OAAO,EAAE,+BAA+B,EAAE,MAAM,+BAA+B,CAAC;AAChF,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,0BAA0B,EAAE,MAAM,0BAA0B,CAAC;AACtE,OAAO,EAAE,uBAAuB,EAAE,MAAM,uBAAuB,CAAC;AAChE,OAAO,EAAE,wBAAwB,EAAE,MAAM,wBAAwB,CAAC;AAClE,OAAO,EAAE,yBAAyB,EAAE,MAAM,yBAAyB,CAAC;AACpE,OAAO,EAAE,iBAAiB,EAAE,MAAM,gBAAgB,CAAC;AACnD,OAAO,EAAE,wBAAwB,EAAE,MAAM,uBAAuB,CAAC;AACjE,OAAO,EAAiC,KAAK,cAAc,EAAE,MAAM,kBAAkB,CAAC;AAKtF,OAAO,EACL,6BAA6B,EAC7B,8BAA8B,EAC9B,4BAA4B,EAC5B,+BAA+B,EAC/B,8BAA8B,EAC9B,0BAA0B,EAC1B,uBAAuB,EACvB,wBAAwB,EACxB,yBAAyB,EACzB,iBAAiB,EACjB,wBAAwB,GACzB,CAAC;AAIF,YAAY,EAAE,cAAc,EAAE,MAAM,kBAAkB,CAAC;AAEvD;;;;;;GAMG;AACH,eAAO,MAAM,kCAAkC,0BAA0B,CAAC;AAE1E;;;;GAIG;AACH,eAAO,MAAM,qCAAqC,6BAA6B,CAAC;AAEhF;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,oCAAoC,4BAA4B,CAAC;AAE9E;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,+BAA+B,uBAAuB,CAAC;AAEpE;;;;;;;;;;GAUG;AACH,eAAO,MAAM,kCAAkC,0BAA0B,CAAC;AAqgB1E;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAgB,gBAAgB,CAC9B,OAAO,EAAE,SAAS,MAAM,EAAE,EAC1B,OAAO,EAAE,cAAc,GACtB,WAAW,EAAE,CAwLf;AAED,kEAAkE;AAClE,wBAAgB,aAAa,CAAC,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,cAAc,GAAG,WAAW,CA0BjF"}