Use python3 as the canonical command name course-wide (#104)

Most current systems (default Debian/Ubuntu, recent macOS) install Python
only as `python3`, with no bare `python` on PATH, so learners who copied
`python cli.py ...` into their host shell hit "command not found".

Convert host-shell `python <cmd>` -> `python3 <cmd>` across module/lab
READMEs, lab `.py` docstrings & usage strings, blog posts, lab prompt and
instruction files, the M04 verify.sh message, and the M10/M24 lab patches.
Module 01's convention note (and its blog/02 mirror) is rewritten so
`python3` is canonical and `python` is the documented fallback.

Stop-lines respected: Docker image tags (`python:3.12-slim`), `.venv/.../python`
and `...\.venv\Scripts\python.exe` paths, the M20 `"command": "python"`
teaching example and surrounding venv prose, container-internal invocations
(M16/M18 Dockerfiles, M16 README `docker run` examples), and CI-workflow
`run:` steps fed by `actions/setup-python` / `image: python:3.12` are left
as `python` on purpose.

pip was left out of scope: most occurrences are prose or CI/container-internal,
and `pip3` does not fix the PEP 668 externally-managed-environment refusal that
the course already addresses with venvs. The M01 note is worded to stay
consistent with bare `pip` (use whichever pip pairs with your Python).

Build (tools/build_wiki.py) and tools/check.sh both pass.

Closes #104

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

modules/25-autonomous-agents/README.md

@@ -256,7 +256,7 @@ out of the agent's `git add -A`, so the change you review in Part B is clean. Th
 
 ```bash
 # Simulate an agent that produces a BROKEN change, then run the gate on it:
-python agent_runner.py issue-to-pr issue-delete-command.md --simulate bad
+python3 agent_runner.py issue-to-pr issue-delete-command.md --simulate bad
 ```
 
 The orchestrator creates and switches to its own `agent/issue-delete-command` branch first (the same
@@ -270,7 +270,7 @@ reached `main`.
 ### Part B: See a good change land as a PR proposal
 
 ```bash
-python agent_runner.py issue-to-pr issue-delete-command.md --simulate good
+python3 agent_runner.py issue-to-pr issue-delete-command.md --simulate good
 ```
 
 This time the planted change is correct. The gate passes, the script commits to the branch and prints
@@ -284,7 +284,7 @@ stops at a PR; it never merges.
 ### Part C: Run the self-healing loop
 
 ```bash
-python agent_runner.py self-heal --simulate bad
+python3 agent_runner.py self-heal --simulate bad
 ```
 
 The orchestrator switches to its own `agent/self-heal` branch (again, you direct the automation, not
@@ -302,7 +302,7 @@ Two ways to go from simulation to a genuine autonomous run:
 
    ```bash
    export AGENT_CMD='your-agent-cli --print --prompt-file {prompt_file}'   # your tool's one-shot mode
-   python agent_runner.py issue-to-pr issue-delete-command.md
+   python3 agent_runner.py issue-to-pr issue-delete-command.md
    ```
 
    The script builds the prompt from the issue **and** your committed config (Module 5), runs your

modules/25-autonomous-agents/lab/agent-job.yml

@@ -62,7 +62,7 @@ jobs:
           # In the triggered case, write the issue body to a file for the agent to read. Read it from
           # $BODY so the shell treats it as data, not as script text.
           printf '%s' "$BODY" > issue.md
-          python modules/25-autonomous-agents/lab/agent_runner.py issue-to-pr issue.md
+          python3 modules/25-autonomous-agents/lab/agent_runner.py issue-to-pr issue.md
 
       # The agent's output is a PROPOSAL. Open the PR; do NOT merge. CI + security + review decide.
       # (Use your forge's PR-creation step or CLI here; kept generic to stay vendor-neutral.)

modules/25-autonomous-agents/lab/agent_runner.py

@@ -14,10 +14,10 @@ not a human watching it type.
 Run it two ways:
 
   1. Simulated (no agent needed, fully deterministic); see the machinery and the gates:
-         python agent_runner.py issue-to-pr issue-delete-command.md --simulate good
-         python agent_runner.py issue-to-pr issue-delete-command.md --simulate bad
-         python agent_runner.py self-heal --simulate bad
-         python agent_runner.py self-heal --simulate stuck
+         python3 agent_runner.py issue-to-pr issue-delete-command.md --simulate good
+         python3 agent_runner.py issue-to-pr issue-delete-command.md --simulate bad
+         python3 agent_runner.py self-heal --simulate bad
+         python3 agent_runner.py self-heal --simulate stuck
 
      Simulation works on a SELF-CONTAINED demo target (agent_demo.py + test_agent_demo.py) so it is
      deterministic and never corrupts your real tasks-app files. The gate it runs (ruff + pytest) is
@@ -26,7 +26,7 @@ Run it two ways:
   2. Real agent: drives your own agentic tool against the actual issue. Point AGENT_CMD at your
      tool's non-interactive / one-shot mode, then drop --simulate:
          export AGENT_CMD='your-agent-cli --print --prompt-file {prompt_file}'
-         python agent_runner.py issue-to-pr issue-delete-command.md
+         python3 agent_runner.py issue-to-pr issue-delete-command.md
 
 Language: Python 3.10+. Standard library only.
 """

modules/25-autonomous-agents/lab/issue-delete-command.md

@@ -20,7 +20,7 @@ is a patterned change, not a design problem.
 
 ## Acceptance criteria
 
-- `python cli.py delete <index>` removes the task at that 0-based index and saves the list.
+- `python3 cli.py delete <index>` removes the task at that 0-based index and saves the list.
 - After deleting, the remaining tasks keep their relative order.
 - `delete` with an out-of-range or non-integer index prints a clear error (e.g.
   `no task at index 99`) and exits non-zero, instead of dumping a traceback.