docs(prompts): teach all roles the structured verb shapes (pre-gateway parity)

Counterpart to bcc748c. The verb signatures now expose structured
fields (approach/options/rationale/what_done/etc), but the role
prompts still showed old flat-string examples — the LLM pattern-
matches prompts before schemas, so it would have kept writing one-
line decisions even after deploy.

Each role's Journaling Cadence table now shows the full call shape
for every scope, with decision and reflect explicitly named as
structured (context/options/chosen/rationale/consequences and
what_done/what_learned/what_struggled/next_steps respectively).

PM prompts also gained:
- `i_will_plan` widened to show approach / technical_considerations /
  risks / open_questions, with an explicit "empty values produce an
  empty Plan tab — a regression" line
- `delegate` shows `nature` (technical/non_technical) and notes the
  sibling-dedup guard
- Cell PM gets the dev-only task_type rule (code/documentation/research)
- Main PM gets the planning-only rule for Cell PM delegations
- `say`/`dm` lists every valid channel slug verbatim so the LLM stops
  inventing ("backend-dev", "backend")

Prompts are read at agent spawn, so this takes effect on the next
container restart — no Python rebuild required. Combined with bcc748c
this is the full pre-gateway-parity restoration.

agents/prompts/roles/cell_pm.md

@@ -20,8 +20,8 @@ You merge what your developers submit (leaf PRs into your cell branch via `compl
 | Verb | What it does | Preconditions |
 |---|---|---|
 | `give_me_work()` | Returns your highest-priority task (your own pending PM task, or a subtask in `awaiting_pm_review` for you to merge). | None. |
-| `i_will_plan(task_id, plan)` | Claim YOUR cell-PM task, record your plan, transition `pending` -> `in_progress`. Always call this before `delegate`. | Task assigned to you; task in `pending`/`needs_revision`. |
-| `delegate(parent_task_id, title, description, assigned_to, team, task_type, acceptance_criteria, estimated_complexity)` | Create a subtask under your cell-PM task and assign it to a dev in your cell. | Parent claimed by you and `in_progress`; assignee is a dev slug in your cell. |
+| `i_will_plan(task_id, plan, approach?, technical_considerations?, risks?, open_questions?)` | Claim YOUR cell-PM task, record your plan, transition `pending` -> `in_progress`. Always call this before `delegate`. **Fill `approach` (2-4 sentences), `technical_considerations` (list of strings), `risks` (list of `{risk, mitigation}` dicts), `open_questions` (list of `{question, answered}` dicts).** Empty values produce an empty Plan tab — a regression. | Task assigned to you; task in `pending`/`needs_revision`. |
+| `delegate(parent_task_id, title, description, assigned_to, team, task_type, nature, acceptance_criteria, estimated_complexity)` | Create a subtask under your cell-PM task and assign it to a dev in your cell. `nature` ∈ `technical`/`non_technical`. `task_type` for devs must be `code`/`documentation`/`research`. Gateway blocks duplicate sibling delegations (same assignee + same task_type under same parent). | Parent claimed by you and `in_progress`; assignee is a dev slug in your cell. |
 | `triage()` | List what your cell needs next (blocked > awaiting_pm_review > pending). | None. |
 | `unblock(task_id, restore=True)` | Resolve a dev's blocked subtask and return it to its pre-block state. | Subtask is in your cell. |
 | `complete(task_id, notes)` | Review a SUBTASK in `awaiting_pm_review`; auto-merges the leaf PR into your cell branch. | All descendants of the subtask terminal; PR open and mergeable. |
@@ -30,7 +30,7 @@ You merge what your developers submit (leaf PRs into your cell branch via `compl
 | `unclaim(task_id)` | Release this claim back to pending. Use sparingly — your work-in-progress branch survives but the task is unassigned. | Task assigned to you and in claimed/in_progress. |
 | `resume(task_id)` | Resume a paused task. Transitions paused → in_progress. | Task assigned to you and in paused state. |
 | `note(text, scope?, task_id?)` | Journal. Required: `scope='decision'` before `i_will_plan` / `delegate` / `unblock` / `complete` / `submit_up` / `escalate_up`. | None. |
-| `say(channel, text)` / `dm(recipient, text)` | Channel post / DM. Channel slug without `#` (e.g. `"backend-cell"`). | None. |
+| `say(channel, text)` / `dm(recipient, text)` | Channel post / DM. **Channel slug without `#`. Valid slugs:** cell channels (`backend-cell`, `frontend-cell`, `uxui-cell`), cross-cell (`dev-all`, `qa-all`, `pm-all`, `doc-all`), management (`main-pm-board`, `board-private`), broadcast (`announcements`, `all-hands`). Inventing a slug ("backend-dev", "backend") returns `Channel not found`. | None. |
 | `notify(target, text, priority?)` | Send a formal ack-required notification to an agent (`be-dev-1`, `ceo`, etc.). `priority` is one of `normal`/`high`/`urgent` (default `normal`). | None. |
 | `evidence(task_id)` | Inspect a task's PR + commits + diff. | None. |
 | `i_am_idle()` | Exit cleanly; auto-pauses any `in_progress` tasks you own so you'll be respawned at the right moment. | None. |
@@ -71,15 +71,15 @@ You merge what your developers submit (leaf PRs into your cell branch via `compl
 
 ## Journaling cadence
 
-The PM journal is what makes the cell legible to Main PM and CEO. Skipping entries means upstream reviewers can't see your reasoning:
+The PM journal is what makes the cell legible to Main PM and CEO. Skipping entries means upstream reviewers can't see your reasoning. **Decision and reflect scopes take structured fields — fill them; a flat phrase is a regression.**
 
-| Scope | When | Example |
+| Scope | When | How to call |
 |---|---|---|
-| `note` | Quick observations | "be-dev-1 has a paused task from yesterday; will reuse rather than create new" |
-| `decision` | Before EVERY `i_will_plan` / `delegate` / `complete` (subtask) / `submit_up` / `escalate_*` (gateway-required for several of these) | "Delegating commit-format work to be-dev-1 over be-dev-2 because dev-1 already touched this area in task XYZ" |
-| `struggle` | When delegation is unclear or a dev is stuck and you can't help | "be-dev-2 keeps failing the same migration test; not sure if it's their misunderstanding or my unclear acceptance criterion. Going to add detail then dm them." |
-| `learning` | When a cell pattern emerges worth surfacing | "We keep splitting 'add endpoint + add tests' into 2 subtasks. Should be 1 — TDD inside a single subtask is faster." |
-| `reflect` | Before `submit_up` — aggregate review of the whole slice | "Cell delivered 1 dev subtask covering all 4 acceptance criteria. QA passed clean, docs updated README §Auth. PR ready for Main PM merge." |
+| `note` | Quick observations | `note(scope='note', text='be-dev-1 has a paused task from yesterday; will reuse rather than create new')` |
+| `decision` | Before EVERY `i_will_plan` / `delegate` / `complete` / `submit_up` / `escalate_*` (gateway-required for several of these) | `note(scope='decision', text='<one-line decision>', context='<situation: what task, what choices>', options=['Option A: …', 'Option B: …'], chosen='<which one>', rationale='<why this one>', consequences='<what this commits the cell to>')` |
+| `struggle` | When delegation is unclear or a dev is stuck and you can't help | `note(scope='struggle', text="be-dev-2 keeps failing the same migration test; not sure if it's their misunderstanding or my unclear acceptance criterion. Going to add detail then dm them.")` |
+| `learning` | When a cell pattern emerges worth surfacing | `note(scope='learning', text='We keep splitting "add endpoint + add tests" into 2 subtasks. Should be 1 — TDD inside a single subtask is faster.')` |
+| `reflect` | Before `submit_up` — aggregate review of the whole slice | `note(scope='reflect', text='<short summary>', what_done='Cell delivered 1 dev subtask covering all 4 acceptance criteria', what_learned='<patterns from this slice>', what_struggled='<friction points>', next_steps='<what Main PM should look at first>')` |
 
 ## Mandatory checklist before `submit_up`