docs(cb-z719.3): the guide and the consumer template tell a navigator how to choose their involvement

[rmstdope]

Bead cb-z719.3, last child of cb-z719. Stacked on the cb-z719.2 PR. Prose only.

• docs/agent-workflow.md: a How involved you are section under Starting producers: the three gates, what each asks of you and what it costs, that a gate waits like a question with no clock, the two presets, and the bugfixer's reading. The phase list names the three gate words.
• templates/consumer-instructions.md: the Producer review section points at navigator_gates.
• CLAUDE.md: this repository's own Producer review says it declares no gates.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GKiLr59caM9f6DxkrsDYR8

[Copilot]

Copilot review overview

🟢 Approval recommended

The changes are prose-only documentation that I verified as accurate and internally consistent with the already-implemented and tested navigator_gates behavior.

Review effort: Balanced
Findings: None

What changed in this PR

This PR adds contributor-facing documentation for the already-implemented navigator_gates feature, which lets a consumer project opt a navigator into any of a producer's plan, review, or merge decisions. It closes out bead cb-z719.3 (last child of cb-z719, stacked on cb-z719.2) by explaining, at the operating-guide and template level, what each gate asks, what it costs, and that a gate blocks like a question with no clock. It complements the executable pieces added in the earlier stacked PRs (preflight validation, the gate phases, and the produce-bead/fix-bug skill steps).

Changes:

• Adds a How involved you are section to docs/agent-workflow.md describing the three gates, their costs, the two presets, the bugfixer's reading, and names the three gate phase words in the State-column phase list.
• Updates the Producer review section of templates/consumer-instructions.md to point navigators at navigator_gates in .cerebro/project.conf ("absent means none").
• Updates CLAUDE.md's Producer review to state this repository declares no navigator_gates, so its producers plan, review, and merge on their own.

File	Description
docs/​agent-workflow.md	New How involved you are section explaining the three gates plus phase-list update naming plan-gate/review-gate/merge-gate.
templates/​consumer-instructions.md	Points consumers at navigator_gates for controlling navigator involvement in plan/review/merge.
CLAUDE.md	Declares this repository uses no navigator_gates, keeping its own consumer declaration consistent.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.