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.

tasks/review-wave-4.md

@@ -224,7 +224,8 @@ acceptance criteria — not test-name-trust):
   file holds; `#[non_exhaustive]` policy respected (none on `PgOpts`);
   core has no driver deps; `eprintln!` diagnostics at the five
   swallowed-wake/lag sites match the SQLite twin's posture (the
-  logging story is a wave-7 item (release readiness), not a wave-4 defect).
+  logging story is a wave-7 item (release readiness) — wave 8 since
+  the fuzzing wave's renumber — not a wave-4 defect).
 - **Gates**: `cargo build`, `cargo test` server-less (25 core + 188
   sqlite + 111 pg-skip + 10 + 10 suite + 3 + 9 harness), clippy
   `-D warnings`, fmt — all green; the pg lib suite 111/111 green