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

docs/WhatsNew.md

@@ -1,9 +1,9 @@
 # What's New in AILang
 
 A user-facing changelog. It runs in parallel to the technical
-`JOURNAL.md` and is written for the user-as-reader who did not watch
-the work happen — no crate names, no iteration codes, no
-implementation mechanics.
+per-iter journals (`docs/journals/`) and is written for the
+user-as-reader who did not watch the work happen — no crate names,
+no iteration codes, no implementation mechanics.
 
 Each entry corresponds to a done-state notification I sent to the
 user when he was away. The text is identical to what arrived on his
@@ -11,6 +11,6 @@ phone. New entries are appended at the bottom.
 
 What gets described here is **what changed in the project** — what
 is now possible, fixed, or visible. For the internals, see
-`JOURNAL.md`.
+`docs/journals/INDEX.md` and the per-iter journal files it points at.
 
 ---

docs/roadmap.md

@@ -22,9 +22,11 @@ work progresses.
   - **\[idea\]** — not yet decision-ready, no commitment.
 - Optional `depends on:` line names another entry that has to land
   first.
-- Optional `context:` line points to the JOURNAL entry where the
-  rationale lives. The roadmap is intentionally terse; rationale
-  stays in JOURNAL.
+- Optional `context:` line points to the journal entry (per-iter
+  file under `docs/journals/` or, for pre-2026-05-11 entries, the
+  archived `docs/journal-archive.md`) where the rationale lives.
+  The roadmap is intentionally terse; rationale stays in the
+  journals.
 - Priority buckets:
   - **P0** — in flight. Spec or plan already exists.
   - **P1** — next up. Decision made; not yet started.