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/pg-fix-scheduler-fire-wake.md

@@ -179,7 +179,9 @@ Fix-shape decisions of record (what the description left open):
   next two full runs plus six focused runs. Recorded in
   `tasks/review-wave-5.md` §6 with the ledger's own conclusion: the
   "fails again" trigger is met, a dedicated investigative session is
-  owed by the wave-7 watch carriage before any postulate-and-fix. Not
+  owed by the release-readiness watch carriage (wave 7 at writing —
+  wave 8 since the fuzzing wave's renumber) before any
+  postulate-and-fix. Not
   load-bearing here (locks, not scheduler/wakes; scheduler code
   untouched by that row).