@sitecoreai-labs/sitecoreai-cli 0.0.4

package/dist/recipe/compile/page-design.js

@@ -0,0 +1,93 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.compilePageDesignRecipe = compilePageDesignRecipe;
+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 emit_1 = require("../layout/emit");
+const shared_1 = require("./shared");
+/**
+ * Compile a `PageDesignRecipe` to an Operation IR.
+ *
+ * Emits up to three ops:
+ *   1. `CreateItem` for the page-design item (SXA Page Design template)
+ *   2. `SetField(PartialDesigns)` — pipe-separated GUID list of partials
+ *   3. `SetField(__Renderings)` — only when recipe.layout is non-empty
+ *
+ * The recipe's `appliesTo` contributions to the Page Designs root's
+ * `TemplatesMapping` field are NOT emitted here — that field is
+ * cross-recipe (every page design contributes a slice) and a per-recipe
+ * `kind: "string"` write would full-replace under the executor's write
+ * semantics, with each page design overwriting its siblings. Use
+ * `compileRecipeSet` (below) to compile a coherent set of recipes —
+ * it aggregates `appliesTo` contributions across every page-design
+ * recipe in the set into one combined IR.
+ */
+function compilePageDesignRecipe(input, context) {
+    const recipe = recipe_1.PageDesignRecipeSchema.parse(input);
+    if (!context.pageDesignsRoot) {
+        throw (0, errors_1.createCliError)(`compilePageDesignRecipe requires context.pageDesignsRoot; tenant-side path missing for recipe ${recipe.handle}`, "INPUT_INVALID");
+    }
+    const operations = [];
+    const policy = (0, policy_1.defaultPolicyForRecipe)(recipe.kind);
+    const site = (0, shared_1.siteOf)(context);
+    const itemRefKey = (0, guids_1.pageDesignId)(site, recipe.handle);
+    const itemPath = (0, shared_1.joinPath)(context.pageDesignsRoot, recipe.name);
+    operations.push({
+        op: "CreateItem",
+        policy,
+        label: `page-design:${recipe.handle}`,
+        id: itemRefKey,
+        path: itemPath,
+        parent: { kind: "ref-path", value: context.pageDesignsRoot },
+        templateOf: sitecore_templates_1.SITECORE_TEMPLATES.PAGE_DESIGN,
+        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 }),
+        ],
+    });
+    if (recipe.partials.length > 0) {
+        operations.push({
+            op: "SetField",
+            policy,
+            label: `page-design-partials:${recipe.handle}`,
+            itemRefKey,
+            fieldId: sitecore_templates_1.COMPOSITION_FIELDS.PARTIAL_DESIGNS,
+            value: {
+                kind: "ref-recipe-list",
+                refKeys: recipe.partials.map((handle) => (0, guids_1.partialDesignId)(site, handle)),
+            },
+        });
+    }
+    if (recipe.layout && Object.keys(recipe.layout.placeholders).length > 0) {
+        const layoutXml = (0, emit_1.emitLayoutXml)(recipe.layout, {
+            parentItemId: itemRefKey,
+            deviceId: sitecore_templates_1.DEFAULT_DEVICE_ID,
+            renderingIdFor: (handle) => (0, guids_1.renderingId)(site, handle),
+            contentItemIdFor: (handle) => (0, guids_1.contentItemId)(site, handle),
+            allowScoped: false,
+            // Page Design preserves canonical input on read-back — keep emitting
+            // canonical so the layout XML round-trips byte-for-byte.
+            mode: "canonical",
+        });
+        if (layoutXml.length > 0) {
+            operations.push({
+                op: "SetField",
+                policy,
+                label: `page-design-layout:${recipe.handle}`,
+                itemRefKey,
+                fieldId: sitecore_templates_1.LAYOUT_FIELDS.RENDERINGS,
+                value: { kind: "string", value: layoutXml },
+            });
+        }
+    }
+    return operations_1.OperationIrSchema.parse({
+        schemaVersion: "1",
+        recipeHandle: recipe.handle,
+        operations,
+    });
+}

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

@@ -0,0 +1,14 @@
+import { type OperationIr } from "../ir/operations";
+import { type ParametersTemplateRecipe } from "../schema/recipe";
+import { type CompileContext } from "./shared";
+/**
+ * Compile a standalone `ParametersTemplateRecipe` to an Operation IR.
+ *
+ * Lands at
+ * `<componentsRoot>/<section>/Presentation Parameters/<name>` —
+ * mirrors the layout that the synthesised inline parameters template
+ * uses, so a standalone recipe and an inline-hoisted one occupy the
+ * same Sitecore path.
+ */
+export declare function compileParametersTemplateRecipe(input: ParametersTemplateRecipe, context: CompileContext, emittedFolders?: Set<string>): OperationIr;
+//# sourceMappingURL=parameters-template.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"parameters-template.d.ts","sourceRoot":"","sources":["../../../src/recipe/compile/parameters-template.ts"],"names":[],"mappings":"AACA,OAAO,EAGL,KAAK,WAAW,EAGjB,MAAM,kBAAkB,CAAC;AAQ1B,OAAO,EAAE,KAAK,wBAAwB,EAAkC,MAAM,kBAAkB,CAAC;AACjG,OAAO,EAUL,KAAK,cAAc,EACpB,MAAM,UAAU,CAAC;AAElB;;;;;;;;GAQG;AACH,wBAAgB,+BAA+B,CAC7C,KAAK,EAAE,wBAAwB,EAC/B,OAAO,EAAE,cAAc,EACvB,cAAc,GAAE,GAAG,CAAC,MAAM,CAAa,GACtC,WAAW,CAuFb"}

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

@@ -0,0 +1,92 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.compileParametersTemplateRecipe = compileParametersTemplateRecipe;
+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 standalone `ParametersTemplateRecipe` to an Operation IR.
+ *
+ * Lands at
+ * `<componentsRoot>/<section>/Presentation Parameters/<name>` —
+ * mirrors the layout that the synthesised inline parameters template
+ * uses, so a standalone recipe and an inline-hoisted one occupy the
+ * same Sitecore path.
+ */
+function compileParametersTemplateRecipe(input, context, emittedFolders = new Set()) {
+    const recipe = recipe_1.ParametersTemplateRecipeSchema.parse(input);
+    const operations = [];
+    const policy = (0, policy_1.defaultPolicyForRecipe)(recipe.kind);
+    const icon = recipe.icon ?? sitecore_templates_1.DEFAULT_ICON;
+    const site = (0, shared_1.siteOf)(context);
+    (0, shared_1.ensureSectionFolder)(operations, context, recipe.section, emittedFolders);
+    const bucketRefKey = (0, shared_1.ensurePresentationParametersBucket)(operations, context, recipe.section, emittedFolders);
+    const parentPath = (0, shared_1.resolvePresentationParametersBucketPath)(context, recipe.section);
+    // The standalone parameters template lands at the same identity
+    // (paramsTemplateId) as inline-hoisted ones — keeps re-pushes
+    // idempotent if a recipe migrates from inline to standalone.
+    const tplRefKey = (0, guids_1.paramsTemplateId)(site, recipe.handle);
+    const tplPath = (0, shared_1.joinPath)(parentPath, recipe.name);
+    operations.push({
+        op: "CreateItem",
+        policy,
+        label: `parameters-template:${recipe.handle}`,
+        id: tplRefKey,
+        path: tplPath,
+        parent: { kind: "ref-recipe", refKey: bucketRefKey },
+        templateOf: sitecore_templates_1.SITECORE_TEMPLATES.TEMPLATE,
+        name: recipe.name,
+        fields: [
+            (0, shared_1.sharedField)(sitecore_templates_1.SYSTEM_FIELDS.ICON, { kind: "string", value: icon }),
+            (0, shared_1.versionedField)(sitecore_templates_1.SYSTEM_FIELDS.DISPLAY_NAME, { kind: "string", value: recipe.displayName }),
+        ],
+    });
+    operations.push({
+        op: "SetBaseTemplates",
+        policy,
+        label: `parameters-base-templates:${recipe.handle}`,
+        itemRefKey: tplRefKey,
+        // The SXA Headless params bases (BaseRenderingParameters +
+        // _PerSiteStandardValues + the other SXA Headless marker) are what
+        // make the Pages editor recognise this as a parameters shape and
+        // surface its fields in the rendering parameters dialog. Vanilla
+        // Sitecore's "Standard Rendering Parameters" doesn't work here —
+        // verified empirically on tenant introspection.
+        baseTemplates: [...sitecore_templates_1.SXA_HEADLESS_PARAMS_BASE_TEMPLATES],
+    });
+    const secRefKey = (0, guids_1.paramsSectionId)(site, recipe.handle, shared_1.PARAMS_SECTION_NAME);
+    const secPath = (0, shared_1.joinPath)(tplPath, shared_1.PARAMS_SECTION_NAME);
+    operations.push({
+        op: "CreateItem",
+        policy,
+        label: `parameters-section:${recipe.handle}/${shared_1.PARAMS_SECTION_NAME}`,
+        id: secRefKey,
+        path: secPath,
+        parent: { kind: "ref-recipe", refKey: tplRefKey },
+        templateOf: sitecore_templates_1.SITECORE_TEMPLATES.TEMPLATE_SECTION,
+        name: shared_1.PARAMS_SECTION_NAME,
+        fields: [],
+    });
+    recipe.params.forEach((param, index) => {
+        operations.push(...(0, shared_1.buildFieldOp)({
+            recipeHandle: recipe.handle,
+            fieldRefKey: (0, guids_1.paramsFieldId)(site, recipe.handle, param.name),
+            fieldPath: (0, shared_1.joinPath)(secPath, param.name),
+            parentRefKey: secRefKey,
+            labelPrefix: `parameters-field:${recipe.handle}`,
+            field: param,
+            zeroBasedIndex: index,
+            policy,
+            site,
+            context,
+        }));
+    });
+    return operations_1.OperationIrSchema.parse({
+        schemaVersion: "1",
+        recipeHandle: recipe.handle,
+        operations,
+    });
+}

package/dist/recipe/compile/partial-design.d.ts

@@ -0,0 +1,18 @@
+import { type OperationIr } from "../ir/operations";
+import { type PartialDesignRecipe } from "../schema/recipe";
+import { type CompileContext } from "./shared";
+/**
+ * Compile a `PartialDesignRecipe` to an Operation IR.
+ *
+ * Emits two ops:
+ *   1. `CreateItem` for the partial-design item (SXA Partial Design template)
+ *   2. `SetField` writing the layout XML to `__Renderings` (shared layout)
+ *
+ * The compiler resolves component / content-item handles in the layout
+ * to deterministic GUIDs at compile time — no executor-side handle
+ * resolution required for the layout body. (Page-template handles in
+ * `appliesTo` and partial handles in `partials[]` on `PageDesignRecipe`
+ * resolve the same way.)
+ */
+export declare function compilePartialDesignRecipe(input: PartialDesignRecipe, context: CompileContext): OperationIr;
+//# sourceMappingURL=partial-design.d.ts.map

package/dist/recipe/compile/partial-design.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"partial-design.d.ts","sourceRoot":"","sources":["../../../src/recipe/compile/partial-design.ts"],"names":[],"mappings":"AAEA,OAAO,EAGL,KAAK,WAAW,EAGjB,MAAM,kBAAkB,CAAC;AAS1B,OAAO,EAAE,KAAK,mBAAmB,EAA6B,MAAM,kBAAkB,CAAC;AAEvF,OAAO,EAAiD,KAAK,cAAc,EAAE,MAAM,UAAU,CAAC;AAE9F;;;;;;;;;;;;GAYG;AACH,wBAAgB,0BAA0B,CACxC,KAAK,EAAE,mBAAmB,EAC1B,OAAO,EAAE,cAAc,GACtB,WAAW,CA2Db"}

package/dist/recipe/compile/partial-design.js

@@ -0,0 +1,76 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.compilePartialDesignRecipe = compilePartialDesignRecipe;
+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 emit_1 = require("../layout/emit");
+const shared_1 = require("./shared");
+/**
+ * Compile a `PartialDesignRecipe` to an Operation IR.
+ *
+ * Emits two ops:
+ *   1. `CreateItem` for the partial-design item (SXA Partial Design template)
+ *   2. `SetField` writing the layout XML to `__Renderings` (shared layout)
+ *
+ * The compiler resolves component / content-item handles in the layout
+ * to deterministic GUIDs at compile time — no executor-side handle
+ * resolution required for the layout body. (Page-template handles in
+ * `appliesTo` and partial handles in `partials[]` on `PageDesignRecipe`
+ * resolve the same way.)
+ */
+function compilePartialDesignRecipe(input, context) {
+    const recipe = recipe_1.PartialDesignRecipeSchema.parse(input);
+    if (!context.partialDesignsRoot) {
+        throw (0, errors_1.createCliError)(`compilePartialDesignRecipe requires context.partialDesignsRoot; tenant-side path missing for recipe ${recipe.handle}`, "INPUT_INVALID");
+    }
+    const operations = [];
+    const policy = (0, policy_1.defaultPolicyForRecipe)(recipe.kind);
+    const site = (0, shared_1.siteOf)(context);
+    const itemRefKey = (0, guids_1.partialDesignId)(site, recipe.handle);
+    const itemPath = (0, shared_1.joinPath)(context.partialDesignsRoot, recipe.name);
+    operations.push({
+        op: "CreateItem",
+        policy,
+        label: `partial-design:${recipe.handle}`,
+        id: itemRefKey,
+        path: itemPath,
+        parent: { kind: "ref-path", value: context.partialDesignsRoot },
+        templateOf: sitecore_templates_1.SITECORE_TEMPLATES.PARTIAL_DESIGN,
+        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 }),
+        ],
+    });
+    const layoutXml = (0, emit_1.emitLayoutXml)(recipe.layout, {
+        parentItemId: itemRefKey,
+        deviceId: sitecore_templates_1.DEFAULT_DEVICE_ID,
+        renderingIdFor: (handle) => (0, guids_1.renderingId)(site, handle),
+        contentItemIdFor: (handle) => (0, guids_1.contentItemId)(site, handle),
+        allowScoped: false,
+        // SXA Partial Design's Layout pipeline normalizes canonical input
+        // into delta form on first write — emit delta directly so first
+        // push converges in one cycle (commit 6404024 documented the
+        // two-cycle workaround; this is its Phase 5 follow-up).
+        mode: "delta",
+    });
+    if (layoutXml.length > 0) {
+        operations.push({
+            op: "SetField",
+            policy,
+            label: `partial-design-layout:${recipe.handle}`,
+            itemRefKey,
+            fieldId: sitecore_templates_1.LAYOUT_FIELDS.RENDERINGS,
+            value: { kind: "string", value: layoutXml },
+        });
+    }
+    return operations_1.OperationIrSchema.parse({
+        schemaVersion: "1",
+        recipeHandle: recipe.handle,
+        operations,
+    });
+}

package/dist/recipe/compile/section-definition.d.ts

@@ -0,0 +1,18 @@
+import { type OperationIr } from "../ir/operations";
+import { type SectionDefinitionRecipe } from "../schema/recipe";
+import { type CompileContext } from "./shared";
+/**
+ * Compile a `SectionDefinitionRecipe` to an Operation IR.
+ *
+ * Section definitions are typically pre-existing tenant scaffolding —
+ * the compiler does NOT emit a CreateItem op for them. Instead, the
+ * recipe's `sitePath` is registered as a cross-recipe ref so the
+ * executor's `seedCrossRecipeRefs` can resolve the existing item's
+ * Sitecore itemId at apply time. For now this compiler returns an
+ * empty IR; downstream `compileRecipeSet` handles the cross-recipe
+ * ref pre-seeding via `extractCrossRecipeSeeds()` (separate plan).
+ *
+ * The recipe is still validated here so authors get schema feedback.
+ */
+export declare function compileSectionDefinitionRecipe(input: SectionDefinitionRecipe, _context: CompileContext): OperationIr;
+//# sourceMappingURL=section-definition.d.ts.map

package/dist/recipe/compile/section-definition.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"section-definition.d.ts","sourceRoot":"","sources":["../../../src/recipe/compile/section-definition.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,WAAW,EAAqB,MAAM,kBAAkB,CAAC;AACvE,OAAO,EAAE,KAAK,uBAAuB,EAAiC,MAAM,kBAAkB,CAAC;AAC/F,OAAO,EAAE,KAAK,cAAc,EAAE,MAAM,UAAU,CAAC;AAE/C;;;;;;;;;;;;GAYG;AACH,wBAAgB,8BAA8B,CAC5C,KAAK,EAAE,uBAAuB,EAC9B,QAAQ,EAAE,cAAc,GACvB,WAAW,CAOb"}

package/dist/recipe/compile/section-definition.js

@@ -0,0 +1,26 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.compileSectionDefinitionRecipe = compileSectionDefinitionRecipe;
+const operations_1 = require("../ir/operations");
+const recipe_1 = require("../schema/recipe");
+/**
+ * Compile a `SectionDefinitionRecipe` to an Operation IR.
+ *
+ * Section definitions are typically pre-existing tenant scaffolding —
+ * the compiler does NOT emit a CreateItem op for them. Instead, the
+ * recipe's `sitePath` is registered as a cross-recipe ref so the
+ * executor's `seedCrossRecipeRefs` can resolve the existing item's
+ * Sitecore itemId at apply time. For now this compiler returns an
+ * empty IR; downstream `compileRecipeSet` handles the cross-recipe
+ * ref pre-seeding via `extractCrossRecipeSeeds()` (separate plan).
+ *
+ * The recipe is still validated here so authors get schema feedback.
+ */
+function compileSectionDefinitionRecipe(input, _context) {
+    const recipe = recipe_1.SectionDefinitionRecipeSchema.parse(input);
+    return operations_1.OperationIrSchema.parse({
+        schemaVersion: "1",
+        recipeHandle: recipe.handle,
+        operations: [],
+    });
+}