@sitecoreai-labs/sitecoreai-cli 0.2.2 → 0.2.3

package/dist/brand/index.d.ts

@@ -31,4 +31,4 @@ export { listBrandKits, getBrandKit, type BrandKitSummary, type ListBrandKitsRes
 export { listBrandKitSections, listBrandKitFields, updateBrandKitField, type BrandKitSectionSummary, type BrandKitFieldSummary, type BrandKitFieldType, type BrandKitFieldValue, type BrandKitArrayEntry, type BrandKitRichArrayEntry, type ListBrandKitSectionsOptions, type ListBrandKitFieldsOptions, type UpdateBrandKitFieldOptions, } from "./kits/sections";
 export { createBrandKit, publishBrandKit, deleteBrandKit, type CreateBrandKitOptions, type PublishBrandKitOptions, type DeleteBrandKitOptions, } from "./kits/create";
 export { listDocuments, getDocument, deleteDocument, type DocumentSummary, type ListDocumentsResponse, type ListDocumentsOptions, type GetDocumentOptions, type DeleteDocumentOptions, } from "./documents/list";
-export { seedBrandKit, type SeedBrandKitOptions, type SeedBrandKitResult, type SeedProgressEvent, type SeedStage, } from "./seed";
+export { seedBrandKit, enrichBrandKitWithDocuments, type SeedBrandKitOptions, type SeedBrandKitResult, type SeedProgressEvent, type SeedStage, type EnrichExistingKitOptions, type EnrichExistingKitResult, } from "./seed";

package/dist/brand/index.js

@@ -16,7 +16,7 @@
  * change in any release without a major bump or a changeset.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.seedBrandKit = exports.deleteDocument = exports.getDocument = exports.listDocuments = exports.deleteBrandKit = exports.publishBrandKit = exports.createBrandKit = exports.updateBrandKitField = exports.listBrandKitFields = exports.listBrandKitSections = exports.getBrandKit = exports.listBrandKits = exports.PIPELINE_BASE_PATH = exports.runEnrichSectionsPipeline = exports.runBrandIngestionPipeline = exports.LOCAL_UPLOAD_UNSUPPORTED_HINT = exports.LOCAL_UPLOAD_UNSUPPORTED_MESSAGE = exports.DOCUMENTS_BASE_PATH = exports.uploadDocument = exports.formatTextSummary = exports.formatTextRow = exports.buildTextReport = exports.buildSarifReport = exports.buildJsonReport = exports.summarizeOutcomes = exports.scoreToSarifLevel = exports.computeExitCode = exports.detectInputFormat = exports.resolveReviewInputs = exports.runBrandReview = exports.runBrandLogin = exports.generateBrandReview = exports.BRAND_REVIEW_BASE_PATH = exports.BRAND_MANAGEMENT_BASE_PATH = exports.BRAND_API_HOST = exports.requestBrandApi = exports.extractScopes = exports.hasBrandScopes = exports.acquireBrandToken = exports.BRAND_REQUIRED_SCOPES = void 0;
+exports.enrichBrandKitWithDocuments = exports.seedBrandKit = exports.deleteDocument = exports.getDocument = exports.listDocuments = exports.deleteBrandKit = exports.publishBrandKit = exports.createBrandKit = exports.updateBrandKitField = exports.listBrandKitFields = exports.listBrandKitSections = exports.getBrandKit = exports.listBrandKits = exports.PIPELINE_BASE_PATH = exports.runEnrichSectionsPipeline = exports.runBrandIngestionPipeline = exports.LOCAL_UPLOAD_UNSUPPORTED_HINT = exports.LOCAL_UPLOAD_UNSUPPORTED_MESSAGE = exports.DOCUMENTS_BASE_PATH = exports.uploadDocument = exports.formatTextSummary = exports.formatTextRow = exports.buildTextReport = exports.buildSarifReport = exports.buildJsonReport = exports.summarizeOutcomes = exports.scoreToSarifLevel = exports.computeExitCode = exports.detectInputFormat = exports.resolveReviewInputs = exports.runBrandReview = exports.runBrandLogin = exports.generateBrandReview = exports.BRAND_REVIEW_BASE_PATH = exports.BRAND_MANAGEMENT_BASE_PATH = exports.BRAND_API_HOST = exports.requestBrandApi = exports.extractScopes = exports.hasBrandScopes = exports.acquireBrandToken = exports.BRAND_REQUIRED_SCOPES = void 0;
 var auth_1 = require("./api/auth");
 Object.defineProperty(exports, "BRAND_REQUIRED_SCOPES", { enumerable: true, get: function () { return auth_1.BRAND_REQUIRED_SCOPES; } });
 Object.defineProperty(exports, "acquireBrandToken", { enumerable: true, get: function () { return auth_1.acquireBrandToken; } });
@@ -75,3 +75,4 @@ Object.defineProperty(exports, "getDocument", { enumerable: true, get: function
 Object.defineProperty(exports, "deleteDocument", { enumerable: true, get: function () { return list_2.deleteDocument; } });
 var seed_1 = require("./seed");
 Object.defineProperty(exports, "seedBrandKit", { enumerable: true, get: function () { return seed_1.seedBrandKit; } });
+Object.defineProperty(exports, "enrichBrandKitWithDocuments", { enumerable: true, get: function () { return seed_1.enrichBrandKitWithDocuments; } });

package/dist/brand/recipe/synthesize-doc.d.ts

@@ -0,0 +1,59 @@
+/**
+ * Synthesize a minimal stub PDF to drive the Sitecore EnrichSections
+ * pipeline when a brand-kit recipe declares section content but ships
+ * no source document.
+ *
+ * Why this exists: the Sitecore Brand Management API has no "create
+ * section" endpoint — sections only appear as a side effect of
+ * `EnrichSectionsPipeline` running over an uploaded document. A
+ * recipe that wants to push field values into the canonical 7
+ * sections (Global Goals, Brand Context, Tone of Voice, Do's and
+ * Don'ts, Visual Guidelines, Grammar Checklists, Glossary and
+ * Localization) must therefore feed the pipeline *something*. When
+ * the operator has no real brand-guidelines PDF to upload, we
+ * synthesize one: a single-page PDF naming each declared section so
+ * enrichment produces the matching section structure. The actual
+ * field values converge via `updateBrandKitField` PATCH calls
+ * immediately after — the stub's content is throwaway scaffolding.
+ *
+ * The PDF is hand-rolled (no `pdf-lib` dependency). The format we
+ * emit is a minimal, valid PDF 1.4 document with:
+ *   - one Catalog → Pages → Page → Contents chain
+ *   - one Helvetica font (built-in, no embedded data)
+ *   - a single text stream with section names line-broken
+ *
+ * Sitecore's Documents API accepts `data:application/pdf;base64,…`
+ * URLs in the v2 form-urlencoded create-request flow (verified in
+ * [[project-scai-documents-api-v1-vs-v2]]), with a ~1MB limit from
+ * the form-urlencoded body cap. Our synthesized PDF is well under
+ * 1KB even for kits with the full canonical section list.
+ */
+export interface SynthesizedStubDocument {
+    /** Data URL (`data:application/pdf;base64,…`) ready for `BrandDocument.url`. */
+    url: string;
+    /** Display title used when uploading. */
+    title: string;
+    /** Tags applied to the synthesized document. Distinguishes it from
+     *  operator-supplied docs for downstream filtering. */
+    tags: string[];
+    /** Byte length of the underlying PDF — useful for tests / logging. */
+    byteLength: number;
+}
+export interface SynthesizeStubDocumentOptions {
+    /** Brand-kit display name; used in the doc title + PDF body. */
+    brandKitName: string;
+    /** Section names declared in the recipe — one PDF line per name. */
+    sectionNames: readonly string[];
+}
+/**
+ * Build a stub brand-document for a recipe that has section data but
+ * no source PDF. The synthesized doc has just enough structure for
+ * Sitecore's BrandIngestion + EnrichSections pipelines to produce
+ * the canonical section set; the field values declared in the recipe
+ * overwrite enrichment's output via `updateBrandKitField`.
+ *
+ * Throws when `sectionNames` is empty — a stub doc with no section
+ * names defeats the purpose, and callers should have gated on
+ * "recipe has sections" before reaching here.
+ */
+export declare const synthesizeBrandStubDocument: (options: SynthesizeStubDocumentOptions) => SynthesizedStubDocument;

package/dist/brand/recipe/synthesize-doc.js

@@ -0,0 +1,140 @@
+"use strict";
+/**
+ * Synthesize a minimal stub PDF to drive the Sitecore EnrichSections
+ * pipeline when a brand-kit recipe declares section content but ships
+ * no source document.
+ *
+ * Why this exists: the Sitecore Brand Management API has no "create
+ * section" endpoint — sections only appear as a side effect of
+ * `EnrichSectionsPipeline` running over an uploaded document. A
+ * recipe that wants to push field values into the canonical 7
+ * sections (Global Goals, Brand Context, Tone of Voice, Do's and
+ * Don'ts, Visual Guidelines, Grammar Checklists, Glossary and
+ * Localization) must therefore feed the pipeline *something*. When
+ * the operator has no real brand-guidelines PDF to upload, we
+ * synthesize one: a single-page PDF naming each declared section so
+ * enrichment produces the matching section structure. The actual
+ * field values converge via `updateBrandKitField` PATCH calls
+ * immediately after — the stub's content is throwaway scaffolding.
+ *
+ * The PDF is hand-rolled (no `pdf-lib` dependency). The format we
+ * emit is a minimal, valid PDF 1.4 document with:
+ *   - one Catalog → Pages → Page → Contents chain
+ *   - one Helvetica font (built-in, no embedded data)
+ *   - a single text stream with section names line-broken
+ *
+ * Sitecore's Documents API accepts `data:application/pdf;base64,…`
+ * URLs in the v2 form-urlencoded create-request flow (verified in
+ * [[project-scai-documents-api-v1-vs-v2]]), with a ~1MB limit from
+ * the form-urlencoded body cap. Our synthesized PDF is well under
+ * 1KB even for kits with the full canonical section list.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.synthesizeBrandStubDocument = void 0;
+/**
+ * Reduce arbitrary input text to printable ASCII for safe embedding
+ * in a PDF content stream that uses Helvetica + WinAnsiEncoding.
+ *
+ * Non-ASCII bytes would either (a) get truncated by
+ * `Buffer.from(..., "binary")` to garbage codepoints, or (b) render
+ * as the wrong glyph through the font's encoding map. Since this PDF
+ * is throwaway scaffolding the Sitecore pipeline parses for section
+ * names — not something a human reads — a lossy ASCII coercion is
+ * the right tradeoff. Operators who care about display content
+ * should ship a real document instead.
+ */
+const toPrintableAscii = (input) => input
+    .normalize("NFKD")
+    .replace(/[‐-―]/g, "-") // dashes
+    .replace(/[‘’‚‛]/g, "'") // single quotes
+    .replace(/[“”„‟]/g, '"') // double quotes
+    .replace(/…/g, "...") // ellipsis
+    .replace(/[^\x20-\x7E]/g, "?");
+/**
+ * Escape a string for inclusion inside a PDF string literal — the
+ * `(...)` form. Per PDF 1.4 §3.2.3, the backslash escape applies to
+ * `(`, `)`, and `\`. Newlines are emitted as actual newlines in the
+ * stream via separate Td positioning, so they never appear inside
+ * a literal here. Caller is responsible for ASCII-sanitizing the
+ * input first (see `toPrintableAscii`).
+ */
+const escapePdfLiteral = (input) => input.replace(/\\/g, "\\\\").replace(/\(/g, "\\(").replace(/\)/g, "\\)");
+/**
+ * Build a single-page PDF whose content stream lists the given lines,
+ * one line per row in 12pt Helvetica. Returns the raw bytes.
+ *
+ * Byte-offset bookkeeping: PDF's `xref` table demands the exact byte
+ * offset of each object's first byte from the start of the file. We
+ * concatenate object bodies into a running buffer and record each
+ * object's position before appending it; the final `startxref` value
+ * is the position of the `xref` keyword itself.
+ */
+const buildMinimalPdf = (lines) => {
+    // PDF 1.4 binary-tag comment — the four high-bit bytes mark the
+    // file as binary so naive ASCII-only tools don't truncate it.
+    const header = "%PDF-1.4\n%\xe2\xe3\xcf\xd3\n";
+    // Content stream — BT/ET wraps the text-rendering block; Td moves
+    // the text cursor. 72,720 is roughly 1in from top-left on letter.
+    const streamLines = ["BT", "/F1 12 Tf", "72 720 Td"];
+    for (let i = 0; i < lines.length; i += 1) {
+        if (i > 0)
+            streamLines.push("0 -16 Td");
+        streamLines.push(`(${escapePdfLiteral(lines[i] ?? "")}) Tj`);
+    }
+    streamLines.push("ET");
+    const stream = streamLines.join("\n");
+    // 5 indirect objects: Catalog, Pages, Page, Contents (text stream),
+    // Font. Order matters — refs (e.g. /Pages 2 0 R) point at the
+    // numbered indirect object below.
+    const objects = [
+        "<< /Type /Catalog /Pages 2 0 R >>",
+        "<< /Type /Pages /Kids [3 0 R] /Count 1 >>",
+        "<< /Type /Page /Parent 2 0 R /MediaBox [0 0 612 792] " +
+            "/Resources << /Font << /F1 5 0 R >> >> /Contents 4 0 R >>",
+        `<< /Length ${Buffer.byteLength(stream, "binary")} >>\nstream\n${stream}\nendstream`,
+        "<< /Type /Font /Subtype /Type1 /BaseFont /Helvetica /Encoding /WinAnsiEncoding >>",
+    ];
+    let body = header;
+    const offsets = [];
+    for (let i = 0; i < objects.length; i += 1) {
+        offsets.push(Buffer.byteLength(body, "binary"));
+        body += `${i + 1} 0 obj\n${objects[i]}\nendobj\n`;
+    }
+    const xrefStart = Buffer.byteLength(body, "binary");
+    let xref = `xref\n0 ${objects.length + 1}\n0000000000 65535 f \n`;
+    for (const off of offsets) {
+        xref += `${String(off).padStart(10, "0")} 00000 n \n`;
+    }
+    xref +=
+        `trailer\n<< /Size ${objects.length + 1} /Root 1 0 R >>\n` + `startxref\n${xrefStart}\n%%EOF\n`;
+    return Buffer.from(body + xref, "binary");
+};
+/**
+ * Build a stub brand-document for a recipe that has section data but
+ * no source PDF. The synthesized doc has just enough structure for
+ * Sitecore's BrandIngestion + EnrichSections pipelines to produce
+ * the canonical section set; the field values declared in the recipe
+ * overwrite enrichment's output via `updateBrandKitField`.
+ *
+ * Throws when `sectionNames` is empty — a stub doc with no section
+ * names defeats the purpose, and callers should have gated on
+ * "recipe has sections" before reaching here.
+ */
+const synthesizeBrandStubDocument = (options) => {
+    if (options.sectionNames.length === 0) {
+        throw new Error("synthesizeBrandStubDocument requires at least one section name; " +
+            "callers should check `Object.keys(recipe.sections).length > 0` first.");
+    }
+    const headline = toPrintableAscii(`${options.brandKitName} - brand kit scaffold (synthesized by scai).`);
+    const sectionLines = options.sectionNames.map((name) => toPrintableAscii(`Section: ${name}`));
+    const lines = [headline, "", ...sectionLines];
+    const pdf = buildMinimalPdf(lines);
+    const base64 = pdf.toString("base64");
+    return {
+        url: `data:application/pdf;base64,${base64}`,
+        title: `${options.brandKitName} brand kit scaffold`,
+        tags: ["scai-synthesized", "stub"],
+        byteLength: pdf.byteLength,
+    };
+};
+exports.synthesizeBrandStubDocument = synthesizeBrandStubDocument;

package/dist/brand/seed.d.ts

@@ -61,6 +61,40 @@ export interface SeedBrandKitResult {
     /** Total wall-clock seconds spent. */
     elapsedSec: number;
 }
+export interface EnrichExistingKitOptions {
+    client: BrandApiClientOptions;
+    /** Brand kit id (the API uuid, not the display name). */
+    brandKitId: string;
+    /** Display name — used only for default upload metadata and log lines. */
+    name: string;
+    /** One or more documents to upload before the ingest+enrich cycle. */
+    documents: BrandDocument[];
+    pollIntervalSec?: number;
+    timeoutSec?: number;
+    onProgress?: (event: SeedProgressEvent) => void;
+    signal?: AbortSignal;
+}
+export interface EnrichExistingKitResult {
+    document: UploadedDocument;
+    sections: BrandKitSectionSummary[];
+    elapsedSec: number;
+}
+/**
+ * Run the upload → publish → ingest → enrich → poll pipeline against
+ * an EXISTING brand kit. Mirrors steps 2-6 of `seedBrandKit` without
+ * creating a new kit — the self-heal path for bare kits that were
+ * previously created without documents (and therefore have zero
+ * sections).
+ *
+ * Why this exists: `scai brand sync push` would historically call
+ * `createBrandKit` (no documents) when the operator's recipe shipped
+ * no source PDF, leaving the kit with zero sections forever. The
+ * synthesize-stub-PDF feature fixed initial creation; this function
+ * unblocks the kits already stuck in that state — calling
+ * `apply()` against the existing kit now produces a stub doc and
+ * runs enrichment, so field writes have somewhere to land.
+ */
+export declare const enrichBrandKitWithDocuments: (options: EnrichExistingKitOptions) => Promise<EnrichExistingKitResult>;
 /**
  * The headline composite — drive a brand kit from "doesn't exist" to
  * "has populated sections and is ready for Brand Review" in one call.

package/dist/brand/seed.js

@@ -1,12 +1,126 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.seedBrandKit = void 0;
+exports.seedBrandKit = exports.enrichBrandKitWithDocuments = void 0;
 const create_1 = require("./kits/create");
 const sections_1 = require("./kits/sections");
 const upload_1 = require("./documents/upload");
 const run_1 = require("./pipeline/run");
 const errors_1 = require("../shared/errors");
 const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms));
+/**
+ * Run the upload → publish → ingest → enrich → poll pipeline against
+ * an EXISTING brand kit. Mirrors steps 2-6 of `seedBrandKit` without
+ * creating a new kit — the self-heal path for bare kits that were
+ * previously created without documents (and therefore have zero
+ * sections).
+ *
+ * Why this exists: `scai brand sync push` would historically call
+ * `createBrandKit` (no documents) when the operator's recipe shipped
+ * no source PDF, leaving the kit with zero sections forever. The
+ * synthesize-stub-PDF feature fixed initial creation; this function
+ * unblocks the kits already stuck in that state — calling
+ * `apply()` against the existing kit now produces a stub doc and
+ * runs enrichment, so field writes have somewhere to land.
+ */
+const enrichBrandKitWithDocuments = async (options) => {
+    const start = Date.now();
+    const pollIntervalSec = options.pollIntervalSec ?? 15;
+    const timeoutSec = options.timeoutSec ?? 900;
+    const emit = (event) => {
+        options.onProgress?.({
+            ...event,
+            elapsedSec: Math.round((Date.now() - start) / 1000),
+        });
+    };
+    // Validate the document list — same registry-file guard seedBrandKit
+    // applies; keeps the rejection contract consistent across the two
+    // entry points.
+    for (const doc of options.documents) {
+        if (doc.kind === "registry-file") {
+            throw (0, errors_1.createScaiError)(`Brand document "${doc.path}" is a registry-file path; scai cannot upload local bytes.`, "INPUT_INVALID", {
+                hint: 'Host the file at an HTTPS URL Sitecore\'s edge can reach (S3, GitHub raw, a CDN) and pass it as a `{ kind: "url", url }` document.',
+            });
+        }
+    }
+    if (options.documents.length === 0) {
+        throw (0, errors_1.createScaiError)("enrichBrandKitWithDocuments requires at least one document.", "INPUT_INVALID");
+    }
+    // Upload docs
+    const documents = [];
+    for (const [index, doc] of options.documents.entries()) {
+        if (doc.kind !== "url") {
+            throw (0, errors_1.createScaiError)("Unreachable: non-URL document survived the registry-file guard.", "INPUT_INVALID");
+        }
+        emit({
+            stage: "uploadDocument",
+            message: `Uploading source document ${index + 1}/${options.documents.length}…`,
+        });
+        const uploaded = await (0, upload_1.uploadDocument)({
+            client: options.client,
+            brandKitId: options.brandKitId,
+            source: { url: doc.url },
+            title: doc.title ?? `${options.name} Brand Guidelines`,
+            summary: doc.summary ?? `Source doc for ${options.name} brand kit (seeded via scai)`,
+            type: "brand guidelines",
+            fileType: "application/pdf",
+        });
+        documents.push(uploaded);
+        emit({ stage: "uploadDocument", message: `Uploaded document ${uploaded.id}` });
+    }
+    // Publish kit (idempotent — already-published kits accept the PATCH).
+    emit({ stage: "publishKit", message: "Publishing kit…" });
+    await (0, create_1.publishBrandKit)({ client: options.client, brandKitId: options.brandKitId });
+    emit({ stage: "publishKit", message: "Kit published" });
+    // Ingest + enrich
+    emit({ stage: "runIngestion", message: "Triggering BrandIngestionPipeline…" });
+    const ingestionRun = await (0, run_1.runBrandIngestionPipeline)({
+        client: options.client,
+        brandKitId: options.brandKitId,
+        populateSections: true,
+        documentIds: documents.map((doc) => doc.id),
+    });
+    emit({ stage: "runIngestion", message: `Ingestion run started: ${ingestionRun.id}` });
+    emit({ stage: "runEnrichment", message: "Triggering EnrichSectionsPipeline…" });
+    const enrichmentRun = await (0, run_1.runEnrichSectionsPipeline)({
+        client: options.client,
+        brandKitId: options.brandKitId,
+    });
+    emit({ stage: "runEnrichment", message: `Enrichment run started: ${enrichmentRun.id}` });
+    // Poll until sections appear
+    const deadline = Date.now() + timeoutSec * 1000;
+    let sections = [];
+    while (Date.now() < deadline) {
+        if (options.signal?.aborted) {
+            throw new Error("enrichBrandKitWithDocuments aborted by signal");
+        }
+        sections = await (0, sections_1.listBrandKitSections)({
+            client: options.client,
+            brandKitId: options.brandKitId,
+        });
+        emit({
+            stage: "pollSections",
+            message: `Sections: ${sections.length}`,
+            sectionCount: sections.length,
+        });
+        if (sections.length > 0)
+            break;
+        await sleep(pollIntervalSec * 1000);
+    }
+    if (sections.length === 0) {
+        throw new Error(`Timed out after ${timeoutSec}s waiting for sections to populate on kit ${options.brandKitId}.`);
+    }
+    emit({
+        stage: "done",
+        message: `Enriched kit ${options.brandKitId} with ${sections.length} sections`,
+        sectionCount: sections.length,
+    });
+    return {
+        document: documents[0],
+        sections,
+        elapsedSec: Math.round((Date.now() - start) / 1000),
+    };
+};
+exports.enrichBrandKitWithDocuments = enrichBrandKitWithDocuments;
 /**
  * The headline composite — drive a brand kit from "doesn't exist" to
  * "has populated sections and is ready for Brand Review" in one call.

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

@@ -448,19 +448,33 @@ function emitRendering(operations, recipe, context, icon, hasParams, policy, emi
     const sectionName = resolveSectionName(recipe, context);
     const renderingParentPath = (0, shared_1.resolveRenderingParent)(context, sectionName);
     const renderingPath = (0, shared_1.joinPath)(renderingParentPath, recipe.name);
-    // Datasource template ref: prefer the explicit `datasource.template`
-    // ref when present (separate ContentTemplateRecipe under Content
-    // Models/); otherwise the component template itself is the datasource
-    // template (inline `fields:` pattern).
+    // Datasource template ref. Three cases:
+    //   1. Explicit `datasource.template` handle → reference the separate
+    //      ContentTemplateRecipe (compatible-data-source pattern).
+    //   2. Inline `fields:` (recipe has ≥ 1 field) → the component template
+    //      IS the datasource template (legacy inline-fields pattern).
+    //   3. Neither — a pure-layout rendering (Container, ColumnSplitter,
+    //      RowSplitter, …). Emit no Datasource Template field at all so
+    //      the rendering item's shared field stays empty. Sitecore Pages
+    //      gates its "create or pick a datasource" prompt on this field
+    //      being non-empty, so an empty value is what makes a layout-only
+    //      rendering droppable without an authoring prompt.
+    const hasInlineFields = (recipe.fields?.length ?? 0) > 0;
     const datasourceRefKey = recipe.datasource?.template
         ? (0, guids_1.templateId)(site, recipe.datasource.template.handle)
-        : (0, guids_1.templateId)(site, recipe.handle);
+        : hasInlineFields
+            ? (0, guids_1.templateId)(site, recipe.handle)
+            : undefined;
     const fields = [
         (0, shared_1.sharedField)(sitecore_templates_1.RENDERING_FIELDS.COMPONENT_NAME, { kind: "string", value: recipe.name }),
-        (0, shared_1.sharedField)(sitecore_templates_1.RENDERING_FIELDS.DATASOURCE_TEMPLATE, {
-            kind: "ref-recipe",
-            refKey: datasourceRefKey,
-        }),
+        ...(datasourceRefKey
+            ? [
+                (0, shared_1.sharedField)(sitecore_templates_1.RENDERING_FIELDS.DATASOURCE_TEMPLATE, {
+                    kind: "ref-recipe",
+                    refKey: datasourceRefKey,
+                }),
+            ]
+            : []),
         (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 }),
     ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sitecoreai-labs/sitecoreai-cli",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "SitecoreAI developer toolkit — a native TypeScript CLI, SDK, and MCP server for deploy, serialization, recipes, publishing, and content operations.",
   "license": "MIT",
   "type": "commonjs",