create-claude-workspace 1.1.36 → 1.1.37

package/dist/template/.claude/agents/orchestrator.md

@@ -151,7 +151,7 @@ If no remote, skip this step.
 ### 10. One task per invocation
 - Complete exactly ONE task per invocation, then end the session cleanly.
 - The external loop (`autonomous.mjs` or ralph-loop) handles iteration control — you do NOT need to manage capacity, iteration counters, or session bounds.
-- After committing the task (STEP 11) and post-merge (STEP 12), update MEMORY.md and EXIT. Do NOT ask whether to continue, do NOT wait for confirmation, do NOT start another task.
+- After committing the task (STEP 11) and post-merge (STEP 12), EXIT. Do NOT update MEMORY.md after merge — it was already committed in STEP 11 and arrived on main via merge. Do NOT ask whether to continue, do NOT wait for confirmation, do NOT start another task. Do NOT create any commits after merge.
 - Track complexity in MEMORY.md `Complexity This Session` for informational purposes only (S=1, M=2, L=4).
 
 ## Task Type Detection
@@ -482,7 +482,8 @@ To determine if a task is frontend, backend, or fullstack, use this heuristic:
     ```
     Note the stacking in MEMORY.md. When the previous MR/PR is merged: `git -C .worktrees/feat/{next} rebase --onto main feat/{previous}`
 - **If no `[ ]` tasks remain in current phase AND at least one `[~]` exists** (all remaining were skipped): do NOT auto-advance. Delegate to `product-owner`: "All tasks in Phase [N] are blocked/skipped. The autonomous loop cannot proceed. Options: (1) ADD replacement tasks that unblock progress, (2) REPRIORITIZE to skip this phase entirely and move to next, (3) declare a BLOCKER requiring human intervention." If product-owner returns only CONFIRM with no actionable changes, STOP the autonomous loop and log: "Phase [N] fully blocked — requires human intervention. Run orchestrator manually after resolving blockers."
-- One task per invocation — after post-merge, end session. The external loop will start the next invocation. Do NOT update MEMORY.md here (already done in STEP 11).
+- One task per invocation — after post-merge, end session. The external loop will start the next invocation.
+- **CRITICAL: ZERO commits after merge.** MEMORY.md and TODO.md are already on main (they came from the merge). Do NOT `git add`, do NOT `git commit`, do NOT create `chore:` commits. If you see tracking files as "modified" after merge, that is IMPOSSIBLE if STEP 11 was done correctly — investigate, do NOT blindly commit.
 - **If no `[ ]` tasks remain in current phase AND zero `[~]` exist** (all completed) -> phase transition (handled at start of STEP 1)
 - **If no `[ ]` tasks remain in ALL phases AND zero `[~]` exist** (everything completed) -> final completion sequence:
   1. Delegate to `product-owner` agent:
@@ -598,7 +599,7 @@ Examples:
 - NEVER implement without architect plan (STEP 2) or skip code review (STEP 7)
 - Each commit = 1 logical unit
 - Conventional commits: feat/fix/refactor/chore/docs
-- **NEVER create commits that only change MEMORY.md or TODO.md** — tracking file updates MUST be included in the same commit as the implementation they track (STEP 11). After merge (STEP 12), do NOT commit anything. No `chore: update progress tracking`, no `chore: update MEMORY.md`, no `chore: log hotfix`. If you feel the urge to commit tracking-only changes, STOP — you missed including them in STEP 11.
+- **ABSOLUTE BAN: NEVER create commits that only change MEMORY.md or TODO.md.** Tracking files are committed WITH implementation code in STEP 11. After merge (STEP 12), ZERO commits — tracking files arrive on main via the merge itself. Forbidden patterns: `chore: update progress tracking`, `chore: update MEMORY.md`, `chore: update MEMORY.md tracking after ...`, `chore: log hotfix`. If tracking files show as modified after merge, something went wrong in STEP 11 — investigate and fix, do NOT create a band-aid commit.
 - All files in ENGLISH
 - TODO.md + MEMORY.md are your tracking system — keep them PRECISE and CURRENT
 - If deviating from plan, LOG the reason in MEMORY.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-workspace",
-  "version": "1.1.36",
+  "version": "1.1.37",
   "description": "Scaffold a project with Claude Code agents for autonomous AI-driven development",
   "type": "module",
   "bin": {