iter or.1.tidy: audit-driven sweep of stale JOURNAL.md references in live docs

CLAUDE.md

@@ -105,8 +105,8 @@ not as immutable scripture.
   use approach X or Y?") — that is orchestrator work.
 - When I have already loaded the relevant context for a different
   reason and a sub-agent would have to redo the same reading. In
-  that case I do the small change inline and note in the JOURNAL
-  why I bypassed the agent.
+  that case I do the small change inline and note in the per-iter
+  journal why I bypassed the agent.
 
 ### Design rationale ≠ implementation effort
 
@@ -264,7 +264,7 @@ Existing entries are not retroactively renamed.
   current: adding new entries, reprioritising, removing items
   that are done or dropped. Entries are checkbox lines; finished
   items get checked off, then removed (with a one-line mirror in
-  JOURNAL) once they stop being interesting context.
+  the per-iter journal) once they stop being interesting context.
 
 - **`docs/specs/<milestone>.md`** (since 2026-05-09): per-milestone
   design spec produced by `skills/brainstorm`. Hard-gate before any
@@ -282,6 +282,7 @@ Existing entries are not retroactively renamed.
   rules (in particular: no internals, lead with the change).
 
 Together these answer three questions: "what is the language right
-now?" (DESIGN), "how did we get here?" (JOURNAL, specs, plans),
-and "what's next?" (roadmap). `WhatsNew.md` is the user-facing
-mirror of the JOURNAL — the same history, told without internals.
+now?" (DESIGN), "how did we get here?" (per-iter journals, specs,
+plans), and "what's next?" (roadmap). `WhatsNew.md` is the
+user-facing mirror of the journals — the same history, told without
+internals.