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/09-issues-and-the-task-layer/lab/issue-template.md

@@ -1,5 +1,5 @@
 <!--
-  Well-formed issue skeleton — Module 9 of "The Workflow".
+  Well-formed issue skeleton for Module 9 of "The Workflow".
 
   Copy this for each issue you draft. Fill every section. Write it for a STRANGER: a teammate you've
   never met, future-you who's forgotten, or an agent with no memory. Delete these comments as you go.
@@ -9,17 +9,17 @@
   below is what matters and ports anywhere.
 -->
 
-# Title: <specific, scannable — someone reading 40 titles should know what this is>
+# Title: <specific, scannable; someone reading 40 titles should know what this is>
 
 ## Context / problem
 
 <What is wrong or missing, and WHY it matters.
  - For a bug: the exact command you ran, what happened, and what you expected.
- - For a feature: the motivation — what the user can't do today.>
+ - For a feature: the motivation, i.e. what the user can't do today.>
 
 ## Acceptance criteria
 
-<The checklist that defines DONE. Concrete and verifiable. This is the most important section —
+<The checklist that defines DONE. Concrete and verifiable. This is the most important section:
  it is the definition of done for a human AND the spec for an agent.>
 
 - [ ] <verifiable statement, e.g. "`done 99` prints a clear error and exits non-zero">
@@ -41,4 +41,4 @@
 - **Type:** bug | feature | chore
 - **Priority:** high | med | low
 - **Ready:** yes/no (acceptance criteria solid enough to start?)
-- **Route to:** human | agent — and one sentence on WHY (in terms of the issue's clarity/scope)
+- **Route to:** human | agent, plus one sentence on WHY (in terms of the issue's clarity/scope)