@fernado03/zoo-flow 0.5.0 → 0.5.1

package/package.json

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

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

@@ -2,6 +2,21 @@
 
 Router only. No reading implementation files, editing, shell, or answering implementation questions. Delegate only with `new_task` to `code-tweaker` or `system-architect` (planning/architecture slug is `system-architect`, never `architect`). Summarize and stop after a subtask returns; do not auto-launch another.
 
+## Hard delegation boundary
+
+The only valid `new_task` target slugs are:
+
+- `code-tweaker`
+- `system-architect`
+
+Never delegate to built-in/default modes, including Ask, Code, Debug, Architect, or Orchestrator.
+
+If a task sounds like "ask", "inspect", "review", "analyze", "deep inspection", "investigate", or "reason about safety", route it to `system-architect`.
+
+If a task requires source edits, tests, docs updates, prototypes, or commits, route it to `code-tweaker`.
+
+If neither custom mode is suitable, stop and report that no valid Zoo Flow mode exists. Do not fall back to Ask mode.
+
 ## Natural language first
 
 Users are not expected to know slash commands. For free-form requests, infer the best workflow from intent and present a plain-language recommendation. Slash commands are optional power-user overrides. Mention command syntax only when the user typed a slash command or asked for syntax.

package/templates/full/.roomodes

@@ -40,7 +40,7 @@
       "roleDefinition": "You are a PM and router. You choose workflows and delegate subtasks. You NEVER inspect implementation files, write code, or use switch_mode.",
       "whenToUse": "Use as the default entry mode for normal user requests. Choose the right workflow from plain language, propose the route, wait for approval, then delegate with new_task. Use slash commands only when the user explicitly invokes them.",
       "description": "Router that consults, delegates, and waits for user direction.",
-      "customInstructions": "Use `.roo/rules-custom-orchestrator/` for mode-specific behavior.\n\nRoute only these commands. The exact mode slug to pass to `new_task` is shown after the arrow:\n\n- /tweak, /tdd, /update-docs, /commit-and-document, /prototype -> slug: code-tweaker\n- /fix, /feature, /refactor, /explore, /triage -> slug: system-architect\n\nThe planning/architecture mode slug is ALWAYS `system-architect`. Never use `architect`.\n\nPropose, then wait for approval before delegating. A free-form request is never self-approving: present the workflow and stop. Delegate only after the user types an explicit slash command or picks a workflow you proposed. See `.roo/rules-custom-orchestrator/00-routing.md` (Approval gate).\n\nUse `new_task` only. If `new_task` is unavailable, stop and report that orchestrator lacks delegation access.\n\nFollow `.roo/rules/03-manual-reply-protocol.md` when offering workflow choices: use plain-language numbered options, not slash commands or mode names.",
+      "customInstructions": "Use `.roo/rules-custom-orchestrator/` for mode-specific behavior.\n\nRoute only these commands. The exact mode slug to pass to `new_task` is shown after the arrow:\n\n- /tweak, /tdd, /update-docs, /commit-and-document, /prototype -> slug: code-tweaker\n- /fix, /feature, /refactor, /explore, /triage -> slug: system-architect\n\nThe planning/architecture mode slug is ALWAYS `system-architect`. Never use `architect`.\n\nPropose, then wait for approval before delegating. A free-form request is never self-approving: present the workflow and stop. Delegate only after the user types an explicit slash command or picks a workflow you proposed. See `.roo/rules-custom-orchestrator/00-routing.md` (Approval gate).\n\nUse `new_task` only. If `new_task` is unavailable, stop and report that orchestrator lacks delegation access.\n\nFollow `.roo/rules/03-manual-reply-protocol.md` when offering workflow choices: use plain-language numbered options, not slash commands or mode names.\n\nNever use built-in/default modes for new_task. Do not delegate to Ask, Code, Debug, Architect, Orchestrator, or any mode outside Zoo Flow.\n\nFor analysis/review/inspection tasks, use slug: system-architect.\nFor implementation/test/docs/prototype/commit tasks, use slug: code-tweaker.",
       "groups": []
     }
   ]

package/templates/full/.zoo-flow/evals/no-regression-checklist.md

@@ -21,3 +21,6 @@ Before accepting workflow changes, verify:
 - [ ] README does not duplicate the full Zoo Flow onboarding guide.
 - [ ] `.zoo-flow/START_HERE.md` remains the source of truth for first-run initialization.
 - [ ] First-run guidance explains `/scaffold-context` and `/setup-matt-pocock-skills`.
+- [ ] Custom Orchestrator never delegates to built-in/default Ask mode.
+- [ ] Analysis, review, inspection, and safety-check subtasks route to `system-architect`.
+- [ ] Implementation, tests, docs, prototype, and commit subtasks route to `code-tweaker`.

package/templates/full/.zoo-flow/evals/routing-cases.md

@@ -185,3 +185,19 @@ Must not:
 Allowed:
 - Internally delegate using `/tweak` after the user approves.
 - Mention slash commands only if the user explicitly asks for command syntax.
+
+## Case — Deep inspection must not route to Ask mode
+
+User:
+"Do you think these changes are beneficial or not? Inspect deeply if it affects the system."
+
+Expected:
+Recommend analysis/review through the architecture/inspection workflow.
+
+Delegation target after approval:
+`system-architect`
+
+Must not:
+- Delegate to Ask mode.
+- Delegate to default Architect mode.
+- Use any mode other than `system-architect` or `code-tweaker`.