docs(rag): rewrite the KB docs to the real gateway verb surface

The RAG knowledge base (indexed and queried by agents at runtime)
described entire fictional MCP tool surfaces — roboco_task_*,
roboco_journal_*, roboco_message_send, roboco_notify_send, roboco_agent_*,
roboco_session_*, roboco_workspace_*, roboco_project_* — that don't exist,
so agents searching the KB were handed invented tool names.

Rewrite every affected doc (tools, roles, workflows, troubleshooting, and
the stale architecture snippets) to the real surface: the gateway intent
verbs (give_me_work, i_will_work_on, open_pr, i_am_done, claim_review,
pass, fail, claim_doc_task, i_documented, triage, delegate, i_will_plan,
unblock, complete, escalate_up, escalate_to_ceo, ...) and content tools
(commit, note(scope=...), say, dm, evidence, notify*, open_session,
channels). Also reconcile the access-control docs to code: CEO can cancel
(Board/Auditor cannot); the management-channel membership and the
Auditor's silent-but-present status now match communications.py.

docs/rag/roles/product-owner.md

@@ -11,52 +11,58 @@
 
 1. Product strategy and direction
 2. Clarify requirements
-3. Approve feature implementations
-4. Handle escalations from Main PM
+3. Review and approve feature direction
+4. Handle escalations from Main PM, escalate to CEO
 
 ## What You CAN Do
 
-- View ALL tasks organization-wide
-- Create and assign tasks
-- Cancel tasks
-- Send notifications
-- Index documentation
-- Access management channels
+- Triage actionable tasks in your scope via `triage()`
+- Escalate tasks to the CEO via `escalate_to_ceo(task_id, reason)`
+- Communicate: `say` (channel), `dm` (A2A), `notify` (ack-required signal)
+- Open strategic sessions via `open_session`
+- Read project docs via `roboco_docs_read` / `roboco_docs_list`
+- Search the knowledge base via `roboco_ask_mentor` / `roboco_kb_search`
 
 ## What You CANNOT Do
 
-- Claim tasks (board observes/approves)
-- Clear/refresh KB indexes
+- Claim tasks (the Board observes and approves — it does not execute work)
+- Create or assign tasks (PM roles delegate; the Board does not)
+- Complete or cancel tasks (PM/CEO only)
+- Pass or fail QA
+- Run native git commands
 
-## Tool Note
+## Tool Surface (per-spawn manifest)
 
-Use `roboco_git_*` MCP tools, not native git commands.
+| MCP server            | Verbs you can call |
+|-----------------------|--------------------|
+| `roboco-flow`         | `triage`, `escalate_to_ceo`, `i_am_idle` |
+| `roboco-do`           | `note`, `say`, `dm`, `notify`, `evidence`, `open_session` |
+| `roboco-docs`         | `roboco_docs_read`, `roboco_docs_list` |
+| `roboco-git-readonly` | `roboco_git_status`, `roboco_git_log`, `roboco_git_diff`, `roboco_git_branch_list` |
+| `roboco-optimal`      | `roboco_ask_mentor`, `roboco_kb_search` |
 
-## Key Permissions
-
-| Permission | Access |
-|------------|--------|
-| VIEW_ALL tasks | Yes |
-| CREATE tasks | Yes |
-| ASSIGN tasks | Yes |
-| CANCEL tasks | Yes |
-| CLOSE tasks | Yes |
-| INDEX_DOCS | Yes |
+Your flow surface is deliberately narrow: the Board steers and approves,
+it does not claim, create, or complete tasks.
 
 ## Escalation
 
-Receives escalations from Main PM.
-Escalates to CEO for final authority.
+Receives escalations from Main PM. Escalates to CEO for final authority.
 
 ```
 Main PM → Product Owner → CEO
 ```
 
+```python
+escalate_to_ceo(task_id, reason="Strategic direction needed on the roadmap")
+```
+
+The CEO acts via the panel/UI; you idle until the CEO decides.
+
 ## A2A
 
 ```python
-roboco_agent_request("main-pm", "coordination", "...", task_id)
-roboco_a2a_check()  # Check inbox
+dm(recipient="main-pm", text="Coordinating the roadmap — ...", task_id="...")
+channels()  # discover channels you can post to
 ```
 
 Skills: requirements_clarification, feature_approval
@@ -68,4 +74,4 @@ Access to:
 - #board-private
 - #announcements (write)
 
-Can notify: Main PM, Head Marketing, Auditor, CEO
+Can `notify`: Main PM, Head Marketing, Auditor, CEO