docs: fix envoy scope misstatements and add scope boundary (Stories 82.1, 82.2)

agents/envoy.md

@@ -4,6 +4,12 @@ You are the project's community envoy — the go-between linking the public (iss
 
 Make every reporter feel heard. Relay their feedback to the right internal channels. Keep them informed of progress. You are a **screen and a relay**, not a decision-maker.
 
+## SCOPE BOUNDARY
+
+You manage the GitHub issues board ONLY. You screen, label, and relay. You do NOT create stories, run BMAD pipelines, write code, merge PRs, or authorize work of any kind.
+
+See the authority table later in this document for the full breakdown of CAN / CANNOT / ESCALATE.
+
 **Your rhythm:**
 1. **On startup:** Check for new or unacknowledged issues (`gh issue list --state open`). Then run a **catch-up scan** to find issues that went unlabeled during previous downtime:
    ```bash

agents/supervisor.md

@@ -66,7 +66,7 @@ A multi-agent system without coordination devolves into chaos: duplicate work, s
 
 ### With Envoy
 - Dispatch envoy for issue triage
-- Envoy runs the BMAD pipeline — you provide scope decisions
+- Envoy runs three-layer triage screening — you decide triage approach
 
 ### With Project Watchdog
 - Watchdog reports story completions and PRD drift

docs/architecture/governance-model.md

@@ -35,7 +35,7 @@ See individual agent files in `agents/` for specific authority definitions.
 |-------|--------|---------------|
 | merge-queue | PR merging | Merge when CI green + no blockers; halt on roadmap violations |
 | pr-shepherd | Fork PR management | Rebase and fix CI; cannot merge |
-| envoy | Community triage | Welcome, triage, create stories; cannot make scope decisions |
+| envoy | Community triage | Welcome, triage, label, relay; cannot make scope decisions or create stories |
 | arch-watchdog | Architecture compliance | Flag violations; cannot override human decisions |
 | project-watchdog | Planning doc health | Detect drift; allocate epic/story numbers (sole authority, INC-003); update story status and planning docs |
 

docs/stories/82.1.story.md

@@ -1,7 +1,7 @@
 # Story 82.1: Fix Envoy Scope Misstatements in Agent and Governance Docs
 
 **Epic:** 82 — Agent Definition Accuracy
-**Status:** Not Started
+**Status:** Done (PR #929)
 **Priority:** P1
 **Estimate:** S (< 1 hour)
 
@@ -48,3 +48,10 @@ These misstatements can cause:
 > [observation] 2026-04-02 — envoy.md already has comprehensive "What You Do NOT Do" (line 279) and "CANNOT (Forbidden)" (line 304) sections. The misstatements are in OTHER docs referencing envoy, not in envoy's own definition.
 
 > [decision] 2026-04-02 — Fix the two specific misstatements rather than doing a broader audit. Broader agent definition consistency audit would be a separate story if needed.
+
+> [observation] 2026-04-02 — `docs/remote-collaboration.md:238` also references envoy running "standard BMAD pipeline" — another misstatement, but out of scope for this story.
+
+## Provenance
+- **Autonomy Level:** L3 (AI-autonomous)
+- **Implementation Agent:** worker/kind-bear
+- **Review:** Human PR review required

docs/stories/82.2.story.md

@@ -1,7 +1,7 @@
 # Story 82.2: Add Explicit Scope Boundary Callout to Envoy Definition
 
 **Epic:** 82 — Agent Definition Accuracy
-**Status:** Not Started
+**Status:** Done (PR #929)
 **Priority:** P2
 **Estimate:** S (< 1 hour)
 
@@ -39,3 +39,8 @@ A prominent SCOPE BOUNDARY callout near the top of the file would reinforce envo
 ## Implementation Notes
 
 > [decision] 2026-04-02 — Place the scope boundary after "Your Mission" and before "Your rhythm" list. This position ensures it's read early in the context window before any operational instructions.
+
+## Provenance
+- **Autonomy Level:** L3 (AI-autonomous)
+- **Implementation Agent:** worker/kind-bear
+- **Review:** Human PR review required