Running-example consistency: paths, tasks.json, command collisions (#7,#10,#11) (#57)

Co-authored-by: claude <claude@jpaul.io> Co-committed-by: claude <claude@jpaul.io>
2026-06-22 15:35:51 -04:00
parent 848ad14e3c
commit 06b9f8f308
14 changed files with 192 additions and 136 deletions
@@ -294,10 +294,10 @@ normal question) and the attacker (you plant content the agent reads).
   # the tool it is NOT exposed (a write) — in a least-privilege setup this path is simply absent
   ```

-   Then clean up the planted task so your repo is honest again (Module 2):
+   Then clean up the planted state so your repo is honest again (Module 2):

   ```bash
-   git restore tasks.json      # or: python cli.py and delete it, then commit a clean state
+   rm tasks.json               # tasks.json is gitignored runtime state — nothing tracked to restore, so just delete it; the app recreates it empty on the next run
   ```

 ---