fix(orchestrator): Add explicit boundaries - orchestrator NEVER edits source code

Orchestrator was editing source code directly instead of spawning workers.
Added CRITICAL section making it explicit:

- Orchestrator NEVER edits source code
- Orchestrator NEVER runs quality gates
- Orchestrator ONLY manages tasks.md and spawns workers
- No "quick fixes" — spawn a worker instead

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

docs/claude/orchestrator.md

@@ -17,6 +17,29 @@ The orchestrator **cold-starts** with just a review report location and minimal
 
 ---
 
+## Orchestrator Boundaries (CRITICAL)
+
+**The orchestrator NEVER:**
+
+- Edits source code directly (_.ts, _.tsx, \*.js, etc.)
+- Runs quality gates itself (that's the worker's job)
+- Makes commits containing code changes
+- "Quickly fixes" something to save time — this is how drift starts
+
+**The orchestrator ONLY:**
+
+- Reads/writes `docs/tasks.md`
+- Reads/writes `docs/orchestrator-learnings.json`
+- Spawns workers via the Task tool for ALL code changes
+- Parses worker JSON results
+- Commits task tracking updates (tasks.md, learnings)
+- Outputs status reports and handoff messages
+
+**If you find yourself about to edit source code, STOP.**
+Spawn a worker instead. No exceptions. No "quick fixes."
+
+---
+
 ## Bootstrap Templates
 
 Use templates from `docs/templates/` (relative to repo root):