Renn F 33464a207a 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.

2026-05-02 04:45:23 +02:00

..

board.md

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

2026-05-02 04:45:23 +02:00

cell_pm.md

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

2026-05-02 04:45:23 +02:00

developer.md

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

2026-05-02 04:45:23 +02:00

documenter.md

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

2026-05-02 04:45:23 +02:00

main_pm.md

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

2026-05-02 04:45:23 +02:00

qa.md

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

2026-05-02 04:45:23 +02:00