wogiflow 2.6.3 → 2.6.4

package/lib/workspace.js

@@ -1069,10 +1069,25 @@ If the MCP tool is not available (shows "MCP servers still connecting"), use the
 
 This is NON-OPTIONAL. Every channel-dispatched task MUST end with a reply to the manager.
 
-## Peer Communication
+## Who to Talk To — Peers First, Manager for User Questions
 
-You can talk to peer repos via curl or the MCP tool:
-${peerNames.map(p => `- \`curl -s -X POST http://localhost:${channelMembers[p]?.port || '???'} -H "X-Wogi-From: ${name}" -d "your message"\``).join('\n')}
+**Talk to PEERS directly** (do NOT go through the manager) when you need:
+- API shape/endpoint details from the other repo ("What does POST /customers return?")
+- Data model clarifications ("Does the Invoice entity have a lineItems relation?")
+- Coordination on shared types or contracts
+- Confirmation that the other side is ready for integration
+- Any technical question that the other repo can answer from its codebase
+
+**Talk to the MANAGER** (which means the user) only when:
+- You have **results to report** (task completed, investigation findings)
+- You need a **user decision** (design choice, product question, approval)
+- You are **stuck** and no peer can help
+- You need to **escalate** something the user should know about
+
+**Rule**: If a peer can answer your question, ask the peer. Do NOT route technical questions through the manager — the manager doesn't read source code and will just relay your question to the peer anyway. Cut out the middleman.
+
+**Peer channels:**
+${peerNames.map(p => `- **${p}**: \`curl -s -X POST http://localhost:${channelMembers[p]?.port || '???'} -H "X-Wogi-From: ${name}" -d "your question"\``).join('\n')}
 
 ## Autonomous Mode — Auto-Approve Everything
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wogiflow",
-  "version": "2.6.3",
+  "version": "2.6.4",
   "description": "AI-powered development workflow management system with multi-model support",
   "main": "lib/index.js",
   "bin": {