create-claude-workspace 1.1.148 → 1.1.149

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

@@ -362,10 +362,11 @@ If `PLAN.md` exists in the project root, check whether it changed since the last
 - If new bugs are found with `critical` or `priority::high` label, they become the next task
 - Skip if no git integration or platform is unreachable
 
-### 13. One task per invocation
+### 13. One task per invocation — FULL CYCLE required
 - 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 9) and post-merge (STEP 10), EXIT. Do NOT update MEMORY.md after merge — it was already committed in STEP 9 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.
+- **CRITICAL: You MUST execute the FULL cycle: STEP 9 → STEP 9b → STEP 10 → EXIT.** Do NOT exit after STEP 9. Creating an MR/PR is NOT the end — you must watch the CI pipeline (9b), read MR/PR comments, fix issues, and merge (10). Only EXIT after STEP 10 is complete (merge done, worktree cleaned up).
+- After merge (STEP 10), EXIT. Do NOT update MEMORY.md after merge — it was already committed in STEP 9 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
@@ -692,8 +693,9 @@ To determine if a task is frontend, backend, or fullstack, use this heuristic:
   2. If merge conflict -> go to "Merge Conflicts" section
   3. If auth/network -> retry once, then log blocker
   4. Commit is still local and safe — do NOT reset or amend without reason
+- **→ PROCEED TO STEP 9b** (do NOT exit here — MR/PR creation is NOT the end of the cycle)
 
-**STEP 9b: CI PIPELINE WATCH** (only if git integration active AND remote push succeeded)
+**STEP 9b: CI PIPELINE WATCH & MR/PR REVIEW** (only if git integration active AND remote push succeeded)
 - Update MEMORY.md (on main): set `Current Step: 9b — CI WATCH`
 - **Skip conditions**: no remote, no push happened, local-only mode, team workflow (team doesn't merge — CI runs on MR/PR, reviewed by humans)
 - **Wait for pipeline to start** (max 60s polling):
@@ -728,7 +730,16 @@ To determine if a task is frontend, backend, or fullstack, use this heuristic:
     esac
   done
   ```
-- **If CI passes** → proceed to STEP 10
+- **If CI passes** → check MR/PR comments before proceeding:
+  ```bash
+  # GitHub — list PR comments (reviews + issue comments)
+  gh pr view --json reviews,comments --jq '.reviews[].body, .comments[].body'
+
+  # GitLab — list MR notes (comments from bots, reviewers, CI)
+  glab mr view --comments
+  ```
+  - If comments contain actionable feedback (code suggestions, requested changes, bot warnings): fix in worktree, amend commit, force-push, restart pipeline watch from the beginning
+  - If comments are informational only (CI passed, coverage report, etc.) or no comments exist: proceed to STEP 10
 - **If CI was canceled** → the pipeline was intentionally stopped (by a human or auto-canceled by a newer push). Do NOT treat as failure. If a newer push triggered it (from a fix attempt), restart polling for the new pipeline. Otherwise proceed to STEP 10.
 - **If CI fails** → diagnose and fix (max 3 attempts). Log CI fix attempt count in MEMORY.md Notes (e.g., `CI fix attempts: 1/3`):
   1. **Fetch CI logs**:
@@ -751,6 +762,7 @@ To determine if a task is frontend, backend, or fullstack, use this heuristic:
      - If architect confirms environment issue → proceed to STEP 10 with local merge fallback, log blocker
      - If still failing → proceed to STEP 10 with local merge fallback, log full details in MEMORY.md Blockers
 - **Note**: `--force-with-lease` is safe here because we own the branch and just pushed it. The MR/PR stays open and updates automatically.
+- **→ PROCEED TO STEP 10** (do NOT exit here — the MR/PR must be MERGED before exiting)
 
 **STEP 10: POST-MERGE & NEXT ITEM**
 - Everything was committed in STEP 9 inside the worktree. The project root (on main) has a clean working tree (tracking changes were discarded in STEP 9).
@@ -809,7 +821,7 @@ 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.
+- **→ EXIT NOW.** One task per invocation — STEP 10 is complete, 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 9 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):

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-workspace",
-  "version": "1.1.148",
+  "version": "1.1.149",
   "author": "",
   "repository": {
     "type": "git",