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/25-autonomous-agents/README.md

@@ -11,25 +11,25 @@
 This is the module the whole back half of the course was load-bearing for. It assumes a lot, on
 purpose; each piece is a wall the autonomous agent has to land behind.
 
-- **Module 24**: assistive agents, where the AI helped and *you* decided every step. This module is
-  the escalation: the agent now takes a step on its own. The only reason that's responsible is the
-  rest of this list.
+- **Module 5**: your committed AI instructions file: the agent's standing brief, the half of the
+  spec that isn't in the issue.
+- **Module 6**: branches. The agent's work goes on a branch, never straight onto `main`.
 - **Module 9**: issues as an agent's task specification, including the `ready` label and the idea of
   an agent as an *assignee*. An issue is the agent's input here.
-- **Module 6**: branches. The agent's work goes on a branch, never straight onto `main`.
 - **Modules 10 and 11**: the PR review gate and the full issue → branch → implementation → PR →
   review → merge → close loop. The PR *is* the unit of supervision in this module.
+- **Module 12**: revert, reset, recovery. The backstop for when a gate misses something.
 - **Modules 13 and 14**: tests and CI. The automated gate that runs on the agent's PR.
 - **Module 15**: security scanning as another gate on the same pushes. Autonomy makes this
   non-optional, not optional.
-- **Module 19**: runners. A triggered or scheduled agent is just a runner job; you need to know
-  what's executing it and whose compute it's burning.
-- **Module 12**: revert, reset, recovery. The backstop for when a gate misses something.
-- **Module 5**: your committed AI instructions file: the agent's standing brief, the half of the
-  spec that isn't in the issue.
 - **Modules 16, 17, 22**: containers (sandboxing), secrets (scoped credentials), and the prompt-
   injection attack surface. An unattended agent with a push token is a security boundary; these are
   why.
+- **Module 19**: runners. A triggered or scheduled agent is just a runner job; you need to know
+  what's executing it and whose compute it's burning.
+- **Module 24**: assistive agents, where the AI helped and *you* decided every step. This module is
+  the escalation: the agent now takes a step on its own. The only reason that's responsible is the
+  rest of this list.
 
 If you skipped straight here, the lesson will read as reckless, because without those gates, it
 *would* be.