fix(voice/consistency): vary stock formulas, vendor-balance orient.py, unify the loop

- Vary 11 instances of two boilerplate openers ("A generic X course…" /
  "Strip away X…") across 10 modules so they read as distinct, concrete prose;
  kept the few deliberate, voice-distinct uses; locked exemplars untouched.
- M23 orient.py: detect a vendor-balanced set of AI-instruction filenames
  (AGENTS.md/CLAUDE.md/GEMINI.md/.cursorrules/.cursor/rules/copilot-instructions)
  instead of singling out one vendor. Still runs.
- Render the collaboration loop consistently as seven stations
  (issue->branch->implementation->PR->review->merge->closed) in M25/M26 to match
  M11 and the syllabus.

Closes #48
Closes #49
Closes #51

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT

modules/26-orchestrating-multiple-agents/README.md

@@ -16,9 +16,10 @@
 - **Module 25 — Autonomous agents** — you can hand an agent an issue and get a reviewable PR back,
   supervised. This module runs *several* of those at once. If you can't trust one unattended agent,
   you have no business running five.
-- **Module 11 — Collaboration: humans and agents on one repo** — the issue → branch → PR → review →
-  merge → close loop. Orchestration is that loop run N times in parallel and fanned back into one
-  `main`. Parallel agents are just contributors who happen to share a clock.
+- **Module 11 — Collaboration: humans and agents on one repo** — the issue → branch →
+  implementation → PR → review → merge → close loop. Orchestration is that loop run N times in
+  parallel and fanned back into one `main`. Parallel agents are just contributors who happen to
+  share a clock.
 - **Module 10 — Reviewing code you didn't write** — the skill that becomes the bottleneck. N agents
   produce N diffs; one human reviews them one at a time.
 - **Module 9 — Issues** — the unit of work you split across agents. A clean fan-out is a set of clean