fbec36cb67
Scaffold the course repo and author the full curriculum in dependency-chain order, following the settled build decisions in handoff.md. - Scaffold: course README, vendor-neutral AGENTS.md (dogfoods Module 5), _TEMPLATE.md (the fixed 9-section module shape), root .gitignore, ship config. - Modules 1-2: reference exemplars (locked for tone/depth/lab style). - Modules 3-27: full lessons + runnable labs, each following the template, respecting the chain, vendor/model-agnostic, with "feel the pain" labs. - Module 8 hosting comparison web-researched and date-stamped (as of 2026-06-22), not written from memory; expansion-zone modules carry Verify-before-publish. - Capstone: the full loop end to end on the running tasks-app example. Lab code syntax-checked (Python/shell/YAML); every module has the 7 core template sections. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
1.1 KiB
1.1 KiB
Agent prompt — issue #44, branch feature/44-clear
Run this in the tasks-app-44-clear worktree. This agent deliberately collides with #42. Both
add a new elif to the same dispatch chain in cli.py — same file, same region. That's the
agent-vs-agent merge conflict the lab wants you to predict in Part A and resolve in Part C. It is not
a mistake in the lab; it is the lesson. Two agents on the same file is a joint, not a seam.
You are working in this worktree only. Do not touch any other folder.
Task: Add a clear command to cli.py that removes all tasks.
- Add a new
elif command == "clear":branch to the dispatch inmain()incli.py. - It should empty the task list and save, then print
cleared. - Reuse the existing
load()/save()helpers. Do not changetasks.py.
Acceptance criteria:
python cli.py clearremoves all tasks and printscleared.python cli.py listafterward shows(no tasks yet).
When done, stop. The human commits, pushes, and opens the PR — and should expect a conflict against
feature/42-count at merge.