feat(a2a): CEO can DM the Auditor and PR reviewers (#623)

* feat(a2a): CEO can DM the Auditor and PR reviewers

A mid-flight PR reviewer or Auditor that's stuck was unreachable — the CEO
had no way to DM them. Both roles now carry dm/read_a2a, so the CEO can open
a 1:1 and they can reply in-thread through the existing CEO-reply path.

Scoped deliberately: the Auditor stays a silent observer to its peers — it
gains no peer-initiation surface (can_a2a_direct routes it through
_check_auditor_a2a, which refuses every initiation target; it can only reply
inside a CEO-opened DM). PR reviewers keep their owning-PM scope. Intake and
Secretary stay excluded — they have their own dedicated chat pages.

NO_COMMS_ROLES drops to {prompter, secretary}; the panel's EXCLUDE_NON_DM_ROLES
matches. KB/docs updated so the 'auditor/pr_reviewer have no dm' claim isn't
left stale.

* test(a2a): smoke guard checks _NO_COMMS_ROLES, not a hardcoded 'auditor'

The dm() runtime guard no longer names the auditor (it now carries dm to
reply to the CEO); it refuses the canonical _NO_COMMS_ROLES set. Assert on
that set so the smoke test tracks the guard, not a stale role name.

* chore(foundation): regenerate verb tables for auditor/pr_reviewer dm+read_a2a

---------

Co-authored-by: Renn F <rennf93@users.noreply.github.com>

docs/rag/roles/auditor.md

@@ -22,7 +22,7 @@ In addition to read-only observation, the Auditor is spawned reactively when a t
 - The orchestrator's `_dispatch_audit_work` watches for unacknowledged `ALERT` notifications targeted at the auditor and spawns the auditor with a quality-alert prompt.
 - This path is **best-effort**: a delivery failure is logged but does not block the underlying task transition.
 
-You still cannot claim tasks, message agents, or write code — the reactive spawn only gives you a timely lens on quality events.
+You still cannot claim tasks, initiate a message to a peer agent, or write code — the reactive spawn only gives you a timely lens on quality events.
 
 ## Scheduled Sweep Path
 
@@ -33,7 +33,7 @@ The Auditor is also spawned on a periodic sweep:
 - If all conditions pass, the orchestrator spawns the auditor with a sweep prompt that instructs it to scan recent task state, quality drift, QA pass/fail patterns, convention violations, tracing gaps, and cross-cell hand-off friction.
 - This path is **best-effort** and shares the same interval throttle with reactive alert spawns.
 
-You still cannot claim tasks, message agents, or write code — the scheduled sweep is another read-only lens on delivery health.
+You still cannot claim tasks, initiate a message to a peer agent, or write code — the scheduled sweep is another read-only lens on delivery health.
 
 ## What You CAN Do
 
@@ -43,7 +43,8 @@ You still cannot claim tasks, message agents, or write code — the scheduled sw
 - Attach evidence via `evidence(task_id)`
 - Search the knowledge base via `roboco_ask_mentor` / `roboco_kb_search`
 - Waive one open **minor/nit** revision-findings-ledger finding via `waive_finding(finding_id, note)` — see below
-- Curate the KB's playbook queue via `approve_playbook` / `reject_playbook` / `archive_playbook` — a deliberate, bounded expansion of your read-only surface (KB curation, not agent comms, so the no-`dm` restriction still holds)
+- Curate the KB's playbook queue via `approve_playbook` / `reject_playbook` / `archive_playbook` — a deliberate, bounded expansion of your read-only surface (KB curation, not agent-initiated comms)
+- Read `dm`s and reply in-thread when the CEO opens a DM with you (`read_a2a` / `dm`) — reachable mid-task if you're stuck, but you still never *initiate* to a peer agent
 - Curate the Obsidian vault's narrative for a just-completed root task-tree via `curate_vault(task_id, narrative)` — see below (only when `ROBOCO_OBSIDIAN_VAULT_ENABLED`)
 
 ## What You CANNOT Do
@@ -51,7 +52,7 @@ You still cannot claim tasks, message agents, or write code — the scheduled sw
 - Claim, create, assign, complete, or cancel tasks
 - Pass or fail QA
 - Escalate (`triage` is your only flow verb besides `i_am_idle`/`waive_finding`)
-- DM agents (`dm`) or send `notify`
+- Initiate a `dm` to a peer agent (you still reply in-thread if the CEO opens one), or send `notify`
 - Acknowledge notifications (silent observer — `notify_ack` is not yours)
 - Write to project docs, write code, or run git write operations
 
@@ -72,7 +73,7 @@ waive_finding(
 
 The Auditor has **silent read access** across the org:
 - Reads task state and the knowledge base
-- Cannot send messages outward — there is no `dm` / `notify`
+- Never initiates messages outward — no `notify`, and `dm` only replies inside a DM the CEO opened (never starts one to a peer)
 - Observations are recorded privately via `note(scope="reflect")`
 
 ## Observation Areas
@@ -86,7 +87,7 @@ Monitor for:
 
 ## Recording Findings
 
-The Auditor cannot create tasks or message agents. Findings are captured as private reflections, which the KB indexes for later review:
+The Auditor cannot create tasks or initiate a message to a peer agent. Findings are captured as private reflections, which the KB indexes for later review:
 
 ```python
 note(

docs/rag/roles/pr-reviewer.md

@@ -43,11 +43,12 @@ You cannot `pr_pass` / `pr_fail` an assembled PR you authored (self-review guard
 - Read-only inspect git via `roboco_git_status / _log / _diff / _branch_list`.
 - Search the knowledge base via `roboco_ask_mentor` / `roboco_kb_search`.
 - Note evidence via `note(...)` and `evidence(...)`.
+- Read `dm`s and reply in-thread when the CEO opens a DM with you (`read_a2a` / `dm`), and deliver an in-path gate verdict to your owning cell_pm/main_pm via `dm` — your only two comms surfaces.
 
 ## What You CANNOT Do
 
 - Modify code, `commit`, push, open / merge PRs — not in your manifest.
-- `dm` other agents — you have no comms surface; your output is the PR review.
+- Initiate a `dm` to anyone other than your owning cell_pm/main_pm — your output is still the PR review, not agent chatter.
 - Send `notify` (ack-required notifications) — PMs / Board only.
 - Decide the PR's fate. You review; the **CEO** decides. Your completed review surfaces in the **CEO PR Review Queue** (Command Center), where the CEO chooses **Supersede** (the org cuts its own branch off the contributor's commits, hardens the work, opens its own PR, and — once that merges — closes and links the contributor PR) or **Dismiss**.
 
@@ -65,7 +66,7 @@ i_am_idle()                   → out of work
 | MCP server            | Verbs you can call |
 |-----------------------|--------------------|
 | `roboco-flow`         | `give_me_work`, `claim_pr_review`, `post_pr_review`, `claim_gate_review`, `pr_pass`, `pr_fail`, `unclaim`, `i_am_idle` |
-| `roboco-do`           | `note`, `evidence`, `notify_list`, `notify_get` (no `dm` / `commit` / `notify`) |
+| `roboco-do`           | `note`, `evidence`, `dm`, `read_a2a`, `notify_list`, `notify_get` (`dm` only to your owning cell_pm/main_pm, or in reply to a CEO-opened DM — no `commit` / `notify`) |
 | `roboco-git-readonly` | `roboco_git_status`, `roboco_git_log`, `roboco_git_diff`, `roboco_git_branch_list` |
 | `roboco-optimal`      | `roboco_ask_mentor`, `roboco_kb_search` |