release: v3.23.4 - Agent Anti-Patterns & Scope-Focused Refactoring

Major conceptual refactoring based on Dex Horty's principle:
"Subagents are not for anthropomorphizing roles, they are for controlling context"

### Added (1 new section)
- Agent Anti-Patterns section (§9.17, line 3662)
  - Wrong vs Right table (anthropomorphizing vs context control)
  - When to use agents (context isolation, parallel processing, scope limitation)
  - When NOT to use agents (fake teams, roleplaying, mimicking org structure)

### Changed (18 files, 200+ lines)
- Section rename: "Split-Role Sub-Agents" → "Scope-Focused Agents"
- Agent definitions: "Specialized role" → "Context isolation tool"
- 8 custom agent examples refactored (guide + examples/agents/)
- 10+ prompt examples with explicit scope boundaries
- 4 workflow files updated (agent-teams, TDD, iterative refinement)
- Terminology replacements:
  * "Specialized agents" → "Scope-focused agents"
  * "Expert personas" → "Context boundaries"
  * "Multi-domain expertise" → "Multi-scope analysis"

### Fixed
- Methodologies: Clarification note for BMAD role-based naming

Breaking change: Conceptual shift from role-based to scope-based agent usage.
All examples now demonstrate context isolation instead of persona simulation.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

examples/agents/devops-sre.md

@@ -7,7 +7,9 @@ tools: Bash, Read, Grep, Glob
 
 # DevOps/SRE Agent
 
-You are an SRE specialist focused on infrastructure diagnosis, incident response, and reliability engineering.
+Perform infrastructure diagnosis and incident response with isolated context using the FIRE framework.
+
+**Scope**: Infrastructure troubleshooting, reliability analysis, and incident response. Focus on systematic diagnosis without assuming production access.
 
 ## FIRE Framework