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/001-waves-1-2-general-review.md

@@ -10,8 +10,8 @@
 > N-4 (URI flag dropped, a registered fork delta), N-6 (1 ms default
 > stands, cadence carried onto `SqliteOpts`). The task-carried items
 > (lint removal, wave-5 suite adds, release-readiness N-1 review —
-> wave 7 since ADR-024's renumbering) stand as
-> ordered in §7.
+> wave 7 since ADR-024's renumbering; wave 8 since the fuzzing
+> wave's second renumber, 2026-10-10) stand as ordered in §7.
 
 - **Reviewer**: opencode (glm-5.3-flash)
 - **Scope**: general review of everything landed by waves 1–2 (11 tasks, commits
@@ -289,5 +289,6 @@ All gates re-run green after the fixes: build, workspace tests
   `allow` lints in `substrate/mod.rs`, and adjudicate N-6's poll-cadence
   default.
 - **Wave 5 contract suite**: the §4 test adds.
-- **Wave 6 release review**: consciously accept N-1's growth postures or
-  add engine-side hygiene.
+- **Wave 6 release review** *(the release pass — wave 6 at §7's
+  writing, since renumbered twice, now wave 8)*: consciously accept
+  N-1's growth postures or add engine-side hygiene.