docs: sort Prerequisites lists numerically ascending (#100)

Reorder the `## Prerequisites` bullets in 9 modules so prior modules
are listed lowest number first instead of by pedagogical importance or
at random. A trailing "Helpful but not required" group stays last and
is sorted within itself; multi-module bullets sort by their lowest
number. Intro/closing paragraphs are left in place. Prose is unchanged;
only bullet order moves.

Modules touched: 7, 9, 14, 15, 22, 24, 25, 26, 27. The other 18 modules
were already ascending (or have one/zero prereqs) and are untouched.
Module 19's "Helpful but not required: Module 16" correctly trails its
ascending 8/14/18 main list, so it stays as is.

Closes #100

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

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

@@ -9,27 +9,27 @@
 
 ## Prerequisites
 
+- **Modules 2, 5, 6.** Durable memory per worktree, the committed AI config every agent inherits,
+  and conflict resolution for the inevitable merge.
 - **Module 7, Worktrees.** The primitive everything here rests on. One repo, many working directories, each on
   its own branch, each safe for an agent to edit without touching the others. Module 7 proved this on
   *two* agents and told you the scale-up lived here. This is here. If `git worktree add` /
   `list` / `remove` aren't muscle memory yet, go back; everything below is that, multiplied.
-- **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 8, Remotes.** The PRs in this lab live on a forge. (A local-only fallback is given.)
+- **Module 9, Issues.** The unit of work you split across agents. A clean fan-out is a set of clean
+  issues.
+- **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 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
-  issues.
 - **Module 14, Continuous integration.** The automated gate every parallel branch passes through
   before it's yours to review. With many agents, CI stops being a nicety and becomes the only thing
   keeping the merge queue honest.
-- **Module 8, Remotes.** The PRs in this lab live on a forge. (A local-only fallback is given.)
-- **Modules 2, 5, 6.** Durable memory per worktree, the committed AI config every agent inherits,
-  and conflict resolution for the inevitable merge.
+- **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.
 
 If you parachuted in: you minimally need worktrees, the PR loop, and one agent you'd let run on its
 own. This module is about coordinating many of those, not about any one of them.