Expansion

New Discord capabilities should follow the existing layers:

1. Add a narrow REST method to DiscordClient.
2. Apply guild and channel scope in ScopePolicy.
3. Normalize Discord data in the service layer.
4. Register an accurately annotated MCP tool.
5. Add transport, policy, service, and MCP contract tests.

Remaining channel and role mutation should reuse the reviewed-plan core but remain separate from exact metadata changes, reviewed channel placement, additive creation, and exact permission-overwrite changes so assignment, deletion, broader topology changes, and bulk reconciliation receive distinct policy and confirmation gates. Further application-command mutation should remain separate from the read-only exposure audit and the fixed managed native Interaction command. Any externally hosted Discord Interaction endpoint must verify Discord signatures with the application public key and remain separate from the local stdio process.

Canonical source: docs/reference.md