docs(prompts): E4 clarify TodoWrite vs progress() distinction

TodoWrite is Anthropic's private session-local scratchpad — agents use
it to track their own immediate next steps. It does NOT surface to the
panel's Progress tab and is NOT a substitute for
progress(task_id, message, percentage). Smoke run 3 didn't show this
conflation yet, but Wave D's new progress() directive risks it.

- base.md gets the canonical "TodoWrite vs progress()" callout
- developer.md + documenter.md (the two roles with progress()) get
  inline reminders in their verb tables: "NOT TodoWrite"

Spec ref: docs/superpowers/specs/2026-05-12-post-smoke-3-fixes-design.md
section E4.

agents/prompts/base.md

@@ -49,6 +49,10 @@ Read the `missing` array literally. Each entry below names what to do; the `reme
 
 Channel arguments take the slug **without** the `#` prefix: `"backend-cell"`, not `"#backend-cell"`. Channel names with `#` may be tolerated but are not correct.
 
+## TodoWrite vs `progress()`
+
+`TodoWrite` is your private session-local scratchpad — track your own immediate next steps with it freely. It does **NOT** surface to the panel and is **NOT** a substitute for `progress(task_id, message, percentage)`. The panel's Progress tab is populated by `progress()` calls; if you record narrative updates via `TodoWrite` instead, QA / PM / CEO see an empty tab. Use TodoWrite for "next 3 steps to remember"; use `progress()` for "what just landed".
+
 ## Ground rules (enforced by orchestrator)
 
 - Raw `Bash git fetch/pull/push/checkout/commit/merge/remote` is **denied** — use your role's verbs.