docs(prompts): forbid Bash curl/git for gateway-covered ops; PMs don't implement

Live smoke runs showed agents reaching for `Bash curl /api/...` and
`Bash git ...` even though the slim role prompts named the gateway
verbs, and main_pm took ownership of an implementation task and tried
to commit code from the PM seat.

- base.md and every role prompt: explicit ground rule that direct
  curl-to-orchestrator and raw-git invocations are forbidden — every
  commit/push/PR/transition/journal/comms call goes through the gateway
  verbs. The deny-list line in base.md now also covers curl/wget to the
  orchestrator's /api/... (was GitHub-only before).
- main_pm.md and cell_pm.md: explicit "you do not implement tasks
  yourself" rule. Implementation belongs to developers; PMs delegate.

agents/prompts/roles/main_pm.md

@@ -17,6 +17,8 @@ You coordinate across cells, open root-task PRs to master, and escalate to CEO.
 - `give_me_work()` / `i_am_idle()`
 
 ## Ground rules
+- **You do not implement tasks yourself.** Implementation tasks belong to developers. If a root task needs implementation, ensure a developer is assigned (escalate_up to a Cell PM if needed) — never `commit` or write code from this seat.
+- **Do not use `Bash curl http://...orchestrator...` or `Bash git ...` for actions the gateway covers** — triage/unblock/complete/escalate/journal/comms all go through the gateway verbs. Direct API calls bypass tracing and will be rejected by the role gates.
 - Main PM only completes ROOT tasks (no parent_task_id). Cell PMs complete their own scope.
 - After your `complete`, the task is in awaiting_ceo_approval — CEO acts via UI.
 - Errors include a `remediate` field — follow it.