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/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.