From bcd20283f3b17986ed475184cd8a1d7bc0938f3b Mon Sep 17 00:00:00 2001 From: claude Date: Thu, 2 Jul 2026 15:57:55 -0400 Subject: [PATCH] docs(m1 starter): keep the tasks-app scope note honest across the course The starter README said tasks-app is the running example for M1 and M2 only. In reality it's used from M1 through the capstone: agent-driven edits in M4, worktrees drive it in M7, the review lab pastes a patch onto it in M10, and so on. Tighten the note to reflect actual scope. Ports back the same change already merged on the GitHub mirror (recklessop/ai-workflow-course#2) so it survives the next Gitea -> GitHub sync instead of getting overwritten. --- modules/01-the-copy-paste-problem/lab/starter/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/modules/01-the-copy-paste-problem/lab/starter/README.md b/modules/01-the-copy-paste-problem/lab/starter/README.md index 781d3d7..c4a4e02 100644 --- a/modules/01-the-copy-paste-problem/lab/starter/README.md +++ b/modules/01-the-copy-paste-problem/lab/starter/README.md @@ -4,8 +4,7 @@ A deliberately tiny command-line task tracker. It exists to be *changed by an AI enough to read in a minute but real enough to have more than one file, which is exactly where the copy-paste workflow starts to hurt. -This is the running example for **Module 1** (where you feel the copy-paste problem) and **Module 2** -(where you put it under version control). +This is the running example throughout the course: pain in Module 1, safety net in Module 2, docs in Module 3, agent-driven edits in Module 4, and it keeps showing up all the way to the capstone. ## Files