release-renumber-sweep: annotate stale wave-7 release-pass references

Sweep of docs/reviews/ and tasks/ per the plan's §Wave 8 historical
note: 'wave 7'-means-release-pass references annotated or reworded
per the review-wave-5.md renumber-annotation precedent; genuine
fuzzing-wave/review-7 references untouched. Out-of-scope
architecture-doc trail records documented in the task's Notes.
12 annotated, 1 reworded (live pointer); taskgraph validate green.

docs/reviews/002-wave-4-general-review.md

@@ -247,8 +247,9 @@ covers it, but say so.
   visibility-budgeting one) would prevent surprise.
 - `eprintln!` diagnostics at the swallowed-wake/lag sites match the
   SQLite twin's posture; the logging story is a wave-7 item (a wave-6
-  item when recorded — renumbered by ADR-024; already recorded by the
-  wave-4 gate).
+  item when recorded — renumbered by ADR-024; the release pass, since
+  renumbered again to wave 8 by the fuzzing wave, 2026-10-10; already
+  recorded by the wave-4 gate).
 - F-2..F-4 from `tasks/review-wave-4.md` stand as recorded there.
 
 ## Recommended sequencing