@sitecoreai-labs/sitecoreai-cli 0.1.0 → 0.1.1

package/dist/commands/recipe/index.js

@@ -14,10 +14,11 @@ const addRequiredInputOption = (command, label) => command.addOption(new command
 const addOutputOption = (command) => command.addOption(new commander_1.Option("-o, --output <path>", "Path to write the output file"));
 // All flags are optional. Each falls back to the matching field on
 // envProfiles[<name>] in sitecoreai.cli.json. resolveRecipeRoots() throws
-// `INPUT_INVALID` for the two required ones (templatesRoot, renderingsRoot)
-// when neither source is set; the Phase 4 composition roots are optional
-// and only surface errors when their corresponding recipe kinds are
-// being compiled.
+// `INPUT_INVALID` for templatesRoot / renderingsRoot when neither source
+// is set AND the recipe set contains a kind that creates template or
+// rendering items; a workflow- / webhook-authorization-only set needs
+// neither. The Phase 4 composition roots are optional and only surface
+// errors when their corresponding recipe kinds are being compiled.
 const addRecipeRootOptions = (command) => command
     .addOption(new commander_1.Option("--templates-root <path>", "Sitecore parent path for template items. Falls back to envProfiles[<name>].templatesRoot."))
     .addOption(new commander_1.Option("--renderings-root <path>", "Sitecore parent path for rendering items. Falls back to envProfiles[<name>].renderingsRoot."))

package/dist/recipe/tasks/compile.js

@@ -24,10 +24,21 @@ const shared_1 = require("./shared");
 const runRecipeCompile = async (options) => {
     const logger = (0, shared_1.toLogger)(options);
     const root = (0, root_config_1.readRootConfiguration)(options.config ?? process.cwd(), options.environmentName);
-    // Resolve parent paths from CLI flags or active env profile (when given).
     const envName = options.environmentName ?? root.defaultEnvironment;
     const environment = envName ? root.environments[envName] : undefined;
-    const { templatesRoot, renderingsRoot } = (0, shared_1.resolveRecipeRoots)(options, environment, envName ?? "(no environment)");
+    const { files, source } = await (0, shared_1.resolveRecipeInputs)(options, root);
+    if (options.output && files.length > 1) {
+        throw (0, errors_1.createScaiError)("--output cannot be combined with multi-file compile.", "INPUT_INVALID", {
+            hint: "Compile a single recipe with --input <file> --output <ir>, or omit --output to write per-recipe IRs to <dir>/<handle>.ir.json.",
+        });
+    }
+    // Load every recipe up front so the templatesRoot / renderingsRoot
+    // requirement can be scoped to what the set actually compiles — a
+    // workflow- / webhook-authorization-only set creates its items under
+    // hardcoded /sitecore/system roots and needs neither.
+    const loaded = await Promise.all(files.map(async (file) => ({ file, recipe: await (0, io_1.loadRecipe)(file) })));
+    // Resolve parent paths from CLI flags or active env profile (when given).
+    const { templatesRoot, renderingsRoot } = (0, shared_1.resolveRecipeRoots)(options, environment, envName ?? "(no environment)", (0, shared_1.recipeSetNeedsRoots)(loaded.map((entry) => entry.recipe)));
     // Phase 2 per-site folder layout roots — optional. When unset the
     // compiler falls back to `templatesRoot` for both, which means
     // section-aware components nest under templatesRoot (mid-migration
@@ -51,15 +62,8 @@ const runRecipeCompile = async (options) => {
     const pageTemplatesRoot = environment?.pageTemplatesRoot;
     const placeholderSettingsRoot = environment?.placeholderSettingsRoot;
     const pagesRoot = environment?.pagesRoot;
-    const { files, source } = await (0, shared_1.resolveRecipeInputs)(options, root);
-    if (options.output && files.length > 1) {
-        throw (0, errors_1.createScaiError)("--output cannot be combined with multi-file compile.", "INPUT_INVALID", {
-            hint: "Compile a single recipe with --input <file> --output <ir>, or omit --output to write per-recipe IRs to <dir>/<handle>.ir.json.",
-        });
-    }
     const results = [];
-    for (const file of files) {
-        const recipe = await (0, io_1.loadRecipe)(file);
+    for (const { file, recipe } of loaded) {
         const ir = (0, compile_1.compileRecipe)(recipe, {
             templatesRoot,
             renderingsRoot,

package/dist/recipe/tasks/push.js

@@ -97,7 +97,6 @@ const runRecipePush = async (options) => {
     // logger on first write — successful pushes leave no file behind.
     const rollbackRunId = (0, node_crypto_1.randomUUID)();
     const rollbackLog = (0, rollback_log_1.createRollbackLogger)(rollbackRunId);
-    const { templatesRoot, renderingsRoot } = (0, shared_1.resolveRecipeRoots)(options, tenant.environment, tenant.envName);
     // Phase 2 per-site folder layout roots — optional at the envProfile
     // level. When unset the compiler falls back to `templatesRoot` for
     // both, which means section-aware components nest under templatesRoot
@@ -160,6 +159,12 @@ const runRecipePush = async (options) => {
         }
     }
     const recipes = await (0, cli_tasks_1.mapWithConcurrency)(recipeFiles, (f) => (0, io_1.loadRecipe)(f));
+    // Resolve templatesRoot / renderingsRoot now that the recipe kinds are
+    // known: a set built only from workflow / webhook-authorization recipes
+    // — which create items under hardcoded /sitecore/system roots — needs
+    // neither. An IR-only push has an empty `recipes` and skips the
+    // requirement too; pre-compiled IRs carry their roots baked in.
+    const { templatesRoot, renderingsRoot } = (0, shared_1.resolveRecipeRoots)(options, tenant.environment, tenant.envName, (0, shared_1.recipeSetNeedsRoots)(recipes));
     const compiled = (0, compile_1.compileRecipeSet)(recipes, {
         templatesRoot,
         renderingsRoot,

package/dist/recipe/tasks/shared.d.ts

@@ -126,6 +126,19 @@ export interface ResolvedTenant {
 export declare const resolveTenant: (options: RecipeTenantOptions, clientOptions?: {
     pathItemIdCache?: Map<string, string>;
 }) => ResolvedTenant;
+/**
+ * Whether a recipe set needs `templatesRoot` / `renderingsRoot` resolved.
+ *
+ * True when at least one recipe creates template / rendering items —
+ * every kind except `ROOTLESS_RECIPE_KINDS`. An empty set (e.g. a push
+ * fed only pre-compiled `.ir.json` inputs, which carry their roots baked
+ * in) needs neither. New recipe kinds default to *needing* roots; add a
+ * kind to `ROOTLESS_RECIPE_KINDS` only once its compiler is confirmed to
+ * ignore both roots.
+ */
+export declare const recipeSetNeedsRoots: (recipes: readonly {
+    kind: string;
+}[]) => boolean;
 /**
  * Resolve the recipe parent paths that the compiler will use for top-level
  * template + rendering items.
@@ -136,7 +149,13 @@ export declare const resolveTenant: (options: RecipeTenantOptions, clientOptions
  *      sitecoreai.cli.json (env-overrides via
  *      `SITECOREAI_ENV_<NAME>_TEMPLATES_ROOT` / `_RENDERINGS_ROOT` apply
  *      at config-load time before this helper runs)
- *   3. Throws `INPUT_INVALID` with a hint pointing at the envProfile shape
+ *   3. When `required`, throws `INPUT_INVALID` with a hint pointing at
+ *      the envProfile shape. When not required (a workflow- /
+ *      webhook-authorization-only set, or an IR-only push), missing
+ *      roots resolve to `""` — the compilers in play never read them.
+ *
+ * Pass `required` from `recipeSetNeedsRoots(recipes)` once the set's
+ * recipe kinds are known.
  *
  * Tenant-specific because each site has its own
  * `/sitecore/templates/Project/<site>/Components` location. Putting roots
@@ -146,7 +165,7 @@ export declare const resolveTenant: (options: RecipeTenantOptions, clientOptions
 export declare const resolveRecipeRoots: (options: {
     templatesRoot?: string;
     renderingsRoot?: string;
-}, environment: EnvironmentConfiguration | undefined, envName: string) => {
+}, environment: EnvironmentConfiguration | undefined, envName: string, required?: boolean) => {
     templatesRoot: string;
     renderingsRoot: string;
 };

package/dist/recipe/tasks/shared.js

@@ -3,7 +3,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.ensureAllowWrite = exports.resolveRecipeInputs = exports.resolveRecipeRoots = exports.resolveTenant = exports.toLogger = void 0;
+exports.ensureAllowWrite = exports.resolveRecipeInputs = exports.resolveRecipeRoots = exports.recipeSetNeedsRoots = exports.resolveTenant = exports.toLogger = void 0;
 const node_path_1 = __importDefault(require("node:path"));
 const fast_glob_1 = __importDefault(require("fast-glob"));
 const logger_1 = require("../../shared/logger");
@@ -28,6 +28,29 @@ const resolveTenant = (options, clientOptions) => {
     return { envName, environment, root, client };
 };
 exports.resolveTenant = resolveTenant;
+/**
+ * Recipe kinds whose compilers create items under hardcoded
+ * `/sitecore/system/*` roots and never read `templatesRoot` /
+ * `renderingsRoot`:
+ *   - `workflow`              → `/sitecore/system/Workflows`
+ *   - `webhook-authorization` → `/sitecore/system/Settings/Webhooks/Authorizations`
+ *
+ * A recipe set built only from these kinds can compile, plan, and push
+ * with neither root configured — see `recipeSetNeedsRoots`.
+ */
+const ROOTLESS_RECIPE_KINDS = new Set(["workflow", "webhook-authorization"]);
+/**
+ * Whether a recipe set needs `templatesRoot` / `renderingsRoot` resolved.
+ *
+ * True when at least one recipe creates template / rendering items —
+ * every kind except `ROOTLESS_RECIPE_KINDS`. An empty set (e.g. a push
+ * fed only pre-compiled `.ir.json` inputs, which carry their roots baked
+ * in) needs neither. New recipe kinds default to *needing* roots; add a
+ * kind to `ROOTLESS_RECIPE_KINDS` only once its compiler is confirmed to
+ * ignore both roots.
+ */
+const recipeSetNeedsRoots = (recipes) => recipes.some((recipe) => !ROOTLESS_RECIPE_KINDS.has(recipe.kind));
+exports.recipeSetNeedsRoots = recipeSetNeedsRoots;
 /**
  * Resolve the recipe parent paths that the compiler will use for top-level
  * template + rendering items.
@@ -38,16 +61,28 @@ exports.resolveTenant = resolveTenant;
  *      sitecoreai.cli.json (env-overrides via
  *      `SITECOREAI_ENV_<NAME>_TEMPLATES_ROOT` / `_RENDERINGS_ROOT` apply
  *      at config-load time before this helper runs)
- *   3. Throws `INPUT_INVALID` with a hint pointing at the envProfile shape
+ *   3. When `required`, throws `INPUT_INVALID` with a hint pointing at
+ *      the envProfile shape. When not required (a workflow- /
+ *      webhook-authorization-only set, or an IR-only push), missing
+ *      roots resolve to `""` — the compilers in play never read them.
+ *
+ * Pass `required` from `recipeSetNeedsRoots(recipes)` once the set's
+ * recipe kinds are known.
  *
  * Tenant-specific because each site has its own
  * `/sitecore/templates/Project/<site>/Components` location. Putting roots
  * in config keeps the orchestrator's `recipe push` invocation
  * config-driven (no plan-schema fields, no extra arg plumbing).
  */
-const resolveRecipeRoots = (options, environment, envName) => {
+const resolveRecipeRoots = (options, environment, envName, required = true) => {
     const templatesRoot = options.templatesRoot ?? environment?.templatesRoot;
     const renderingsRoot = options.renderingsRoot ?? environment?.renderingsRoot;
+    if (!required) {
+        // The recipe set in play never reads these roots — pass through
+        // whatever's configured, or "" so the requirement doesn't block a
+        // set that doesn't need it.
+        return { templatesRoot: templatesRoot ?? "", renderingsRoot: renderingsRoot ?? "" };
+    }
     if (!templatesRoot || !renderingsRoot) {
         const missing = !templatesRoot && !renderingsRoot
             ? "both roots"

package/package.json

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