De-slop: remove every em-dash + banned words across all modules + capstone (#94)

Co-authored-by: claude <claude@jpaul.io>
Co-committed-by: claude <claude@jpaul.io>

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

@@ -1,6 +1,6 @@
 <!--
   The agent's INPUT for Module 25. This is a well-formed issue in the Module 9 format: title,
-  context, acceptance criteria, scope. It is deliberately a good candidate for an agent — well-
+  context, acceptance criteria, scope. It is deliberately a good candidate for an agent: well-
   scoped, concrete, and it mirrors a pattern already in the codebase (the existing `done` command).
 
   The orchestrator (agent_runner.py) reads this file and pairs it with your committed AI config
@@ -15,7 +15,7 @@
 
 `tasks-app` can `add`, `list`, and mark a task `done`, but there's no way to remove a task. Once a
 task is added by mistake it stays forever. The `done` command already takes an index and mutates the
-list through a method on `TaskList`, so a `delete` command should follow the exact same shape — this
+list through a method on `TaskList`, so a `delete` command should follow the exact same shape. This
 is a patterned change, not a design problem.
 
 ## Acceptance criteria
@@ -25,7 +25,7 @@ is a patterned change, not a design problem.
 - `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.
 - The logic lives on `TaskList` (a `remove(index)` method or equivalent), mirroring how `complete`
-  works — `cli.py` only parses arguments and calls it.
+  works; `cli.py` only parses arguments and calls it.
 - A test covers: a successful delete removes the right task, and an out-of-range delete is handled.
 
 ## Out of scope