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.

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

docs/reviews/003-wave-5-general-review.md

@@ -233,19 +233,22 @@ explicitly here so the call is recorded rather than implicit.
   row's lapse assertions can only be delayed, never un-lapsed, by slow
   clocks. Supporting the gate's watch-not-block disposition; the
   watch flag stands (the release-readiness watch — wave 7 since
-  ADR-024's renumbering).
+  ADR-024's renumbering; wave 8 since the fuzzing wave's second
+  renumber, 2026-10-10).
 
 ## Recommendation
 
 No changes required to keep wave 5's verdict standing. For wave 6's
 window *(wave 6 at writing — release readiness; renumbered by
 ADR-024, with Finding 1 since routed to the new wave 6 — the mem
-engine — window, and Findings 2–3 to wave 7's pre-release pass, per
+engine — window, and Findings 2–3 to wave 7's pre-release pass,
+the release pass now wave 8 since the fuzzing wave's second
+renumber, 2026-10-10, per
 `docs/plans/implementation.md`'s wave-6 section)*: Finding 1 is a
 decomposable small task (transient-fault seam +
 retry/exhaustion pin); Findings 2–3 can ride the same task or be
 accepted with the code-read as their pin — either way the disposition
 should be recorded. Findings 4–5 need no work. The env-variable
 boundary section above folds into the release-readiness pass
-(wave 7) as a
+(wave 7 at writing — wave 8 since the fuzzing wave's renumber) as a
 verified-now / re-check-at-prepublish item.