@fernado03/zoo-flow 0.7.7 → 0.7.8

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fernado03/zoo-flow",
   "description": "Workflow control plane for Zoo Code.",
-  "version": "0.7.7",
+  "version": "0.7.8",
   "type": "module",
   "bin": {
     "zoo-flow": "bin/zoo-flow.js"

package/templates/full/.roo/rules-code-tweaker/01-completion.md

@@ -20,7 +20,7 @@ Before any `attempt_completion`, re-read the command body and confirm no later p
 - remaining risk (what was not checked or is uncertain)
 - recommended next command (one only, no auto-launch)
 
-Before `attempt_completion`, present the full output to the user in a normal message if the work produced long results (verification report, diff summary). Then `attempt_completion` with only: brief status, file path if written to `.scratch/`, and recommended next command. The orchestrator summarizes completion messages — the user must see the full output first.
+Write long output (verification report, diff summary) to `.scratch/` with a descriptive path. `attempt_completion` must include: file path where output was saved, brief status, and recommended next command. The user will open the file to see full details.
 
 Before running `git commit` or `git push`, halt and wait for explicit user approval. Never push unless explicitly asked.
 

package/templates/full/.roo/rules-custom-orchestrator/00-routing.md

@@ -6,12 +6,10 @@ Router only. No reading implementation files, editing, shell, or answering imple
 
 After `attempt_completion` from a worker, the orchestrator must:
 
-1. Show the worker's completion message (brief status + file path + recommended next command).
+1. Show the worker's completion message to the user (file path + brief status + recommended next command).
 2. Stop and wait for user input.
 
-The worker already presented the full output in a normal message before `attempt_completion`. The orchestrator does not need to repeat it.
-
-Do not route a new user message until the completion message is fully presented.
+The full output is in the `.scratch/` file referenced by the worker. The orchestrator does not read it — the user opens it in the editor.
 
 ## Hard delegation boundary
 

package/templates/full/.roo/rules-system-architect/02-completion.md

@@ -11,7 +11,7 @@ If you entered this window via `switch_mode` (you are mid-chain, not the entry p
 
 Before any `attempt_completion`, re-read the command body and confirm no later phase is assigned to another mode. If one is, `switch_mode` instead.
 
-Do not use `attempt_completion` to avoid required implementation work. Before `attempt_completion`, present the full output to the user in a normal message so they see the complete details (review findings, exploration map, diagnosis, plan). Then `attempt_completion` with only: brief status, file path if written to `.scratch/`, and recommended next command. The orchestrator summarizes completion messages — the user must see the full output first.
+Do not use `attempt_completion` to avoid required implementation work. Write the full output (review findings, exploration map, diagnosis, plan) to `.scratch/` with a descriptive path. `attempt_completion` must include: file path where output was saved, brief status, and recommended next command. The user will open the file to see full details.
 
 Halt for explicit user approval before testing a bug hypothesis, finalizing an architecture plan, publishing issues, or making irreversible decisions.