executant 1.4.2 → 1.4.3

package/dist/index.js

@@ -1292,6 +1292,21 @@ async function runPass3Judge(description, workflow2) {
     return { pass: true, feedback: "", skipped: true };
   }
 }
+function isNumericSequence(arr) {
+  return arr.every((item, i) => item === String(i + 1));
+}
+function normalizeWorkflow(workflow2) {
+  return {
+    ...workflow2,
+    steps: workflow2.steps.map((step) => {
+      if (Array.isArray(step.forEach) && isNumericSequence(step.forEach)) {
+        const { forEach, ...rest } = step;
+        return { ...rest, repeat: forEach.length };
+      }
+      return step;
+    })
+  };
+}
 async function* streamPlan(args) {
   const { description, taskFile } = args;
   const skipResearch = args.fast || isSimpleRequest(description);
@@ -1414,7 +1429,7 @@ ${issues}` };
     if (!judgeResult.pass) {
       yield { type: "plan:warn", message: `Judge rejected plan but retries exhausted: ${judgeResult.feedback}` };
     }
-    const { goal, vars, steps, ...rest } = zodResult.data;
+    const { goal, vars, steps, ...rest } = normalizeWorkflow(zodResult.data);
     const ordered = { goal, ...vars && { vars }, steps, ...rest };
     const yamlContent = dumpYaml(ordered, {
       lineWidth: -1,

package/dist/prompts/plan-decompose.txt

@@ -97,6 +97,11 @@ Before finalising your JSON, scan every `prompt` and `command` field you wrote.
 For each field, ask: "Does this contain a file path or directory path as a string literal?"
 If yes, extract it to `vars` and replace with `{{var_name}}`.
 
+**Pre-Output Self-Review — Repeat (MANDATORY):**
+Scan every `forEach` field you wrote.
+Ask: "Is this array just sequential numbers like `["1","2","3"]` with no meaningful items?"
+If yes, replace the entire `forEach` with `repeat: N` where N is the count. Sequential-number forEach arrays are ALWAYS wrong — they are a misuse of forEach and must be converted to `repeat: N`.
+
 ## When to Use Each Step Type
 
 **Use `prompt` steps (AI-assisted) for:**

package/dist/prompts/plan-judge.txt

@@ -59,6 +59,13 @@ Are all file paths declared in `vars`?
 - Do any `prompt` or `command` fields contain hardcoded file paths or directory paths?
 - Hardcoded paths in steps (not in `vars`) are a violation
 
+### 5. Repeat Misuse (if applicable)
+If the user's goal mentions "N times", "repeat N", "N iterations", or "N passes":
+
+- Does any step use `forEach` with a sequential numeric array like `["1","2","3","4","5"]`?
+- This is always wrong — `repeat: N` must be used instead of a numeric forEach array
+- Reject and require the offending step be converted to `repeat: N`
+
 ## Output Format
 
 Respond with ONLY a JSON object in this exact shape:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "executant",
-  "version": "1.4.2",
+  "version": "1.4.3",
   "description": "Harness for YAML-defined workflows that enables stepping through Claude sessions and bash commands",
   "repository": {
     "type": "git",