@fernado03/zoo-flow 0.7.1 → 0.7.3

package/package.json

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

package/templates/full/.roo/rules/04-context-economy.md

@@ -10,7 +10,7 @@ Batch related small reads when useful.
 
 Do not re-read unchanged files unless needed.
 
-For long command output, summarize or search the output instead of dumping everything.
+For long shell command output (tests, builds, lint), summarize or search the output instead of dumping everything. This is about context window management, not about hiding results from the user.
 
 ## Domain-doc read gate
 

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

@@ -20,7 +20,9 @@ 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)
 
-The orchestrator forwards your output to the user. Include enough detail that the user can act on it without re-running commands.
+The orchestrator forwards your output to the user. Include enough detail that the user can act on it without re-running commands.
+
+If the output is long (multi-file diff summary, full test output, verification report), write it to `.scratch/` first and reference the path in `attempt_completion`. The extension may truncate long completion messages, so files ensure nothing is lost.
 
 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,9 +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 full output to the user without truncating or summarizing.
-2. Add one line: recommended next command (if any).
-3. Stop and wait for user input.
+1. If the completion message references a `.scratch/` file, read and present that file's content.
+2. Show the worker's full output to the user without truncating or summarizing.
+3. Add one line: recommended next command (if any).
+4. Stop and wait for user input.
 
 Do not route a new user message until the previous subtask result is fully presented. If the user sends a new message before the result was shown, finish presenting the result first, then route the new message.
 

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

@@ -13,6 +13,8 @@ Before any `attempt_completion`, re-read the command body and confirm no later p
 
 Do not use `attempt_completion` to avoid required implementation work. Every `attempt_completion` must include the full output the user needs to see (review findings, exploration map, diagnosis, plan), not just summaries. The orchestrator will forward your output to the user; if you summarize, the user loses detail.
 
+If the output is long (multi-page review, full exploration map, detailed diagnosis), write it to `.scratch/` first and reference the path in `attempt_completion`. The extension may truncate long completion messages, so files ensure nothing is lost.
+
 Halt for explicit user approval before testing a bug hypothesis, finalizing an architecture plan, publishing issues, or making irreversible decisions.
 
 For non-trivial completed plans or reviews, recommend the next command only. Typical chain: implementation command -> `/verify` -> `/review` -> `/commit-and-document`. Do not auto-launch those commands.

package/templates/full/.roo/skills/engineering/grill-with-docs/CONTEXT-FORMAT.md

@@ -32,5 +32,4 @@ _Avoid_: Purchase, transaction
 ## Discovery rule
 
 1. If the file exists, read it.
-2. If the file is missing, that is **not an error**. Do not invent content.
-3. For commands that depend on populated context, surface once: "No CONTEXT.md or ADRs found yet. Run /grill-with-docs or /scaffold-context to fill, or continue without."
+2. If the file is missing, that is **not an error**. Do not invent content. Surface once: "No CONTEXT.md found. Run /scaffold-context to fill, or continue without."