---
id: release-renumber-sweep
name: Renumber sweep — historical "wave 7" references to the release pass
status: pending
depends_on: []
scope: narrow
risk: trivial
impact: isolated
level: implementation
tags: [wave-8, docs, records]
---

## Description

The plan's historical note (§Wave 8): records written before the
second renumber — review 001/002/003 and the wave-3..6 task files —
say "wave 7" where they mean the release pass, which is now wave 8.
Per the family's renumber-annotation precedent
(`tasks/review-wave-5.md`'s ADR-024 annotations), affected records get
swept (or annotated) when wave 8 decomposes — history is not rewritten
in place.

Sweep the corpus for the stale references and dispose each: annotate
in place (the precedent — a bracketed "(wave 8 since the fuzzing
wave's renumber)" style note) where the record is historical and its
wave-7 phrasing is load-bearing context; reword only where the
reference is a live pointer (e.g. a task's References section pointing
a future reader at the wrong wave). Known affected sites (start the
sweep from these, then grep for more):

- `docs/reviews/001-waves-1-2-general-review.md` (the header note's
  "release-readiness N-1 review — wave 7 since ADR-024's renumbering";
  §7's wave-6 release-review bullet)
- `docs/reviews/003-wave-5-general-review.md` (the Recommendation
  section's renumber trail; the flake-watch echo's "wave 7 since
  ADR-024's renumbering")
- `tasks/review-wave-5.md` (Notes §6's "flagged for watch in the next
  wave window (release readiness at gate time — since renumbered to
  wave 7…)" and the ledger update's "wave-7 watch carriage")
- `tasks/review-wave-6.md` (Findings 2–3 "parked for wave 7"; the
  recorded observations' "wave-7 pre-release pass" pointers)
- wave-3..6 task files whose Notes/Summary cite the release pass as
  wave 7 (grep `wave 7` / `wave-7` across `tasks/`, excluding the
  genuine wave-7 fuzz tasks — `fuzz-*` and `review-wave-7` — whose
  references are correct)

The distinguishing rule: a reference is stale only if it means the
*release pass*; references to the fuzzing wave (wave 7 since
2026-10-10) are correct and stay untouched.

## Acceptance Criteria

- [ ] Every stale "wave 7"-means-release-pass reference in
      `docs/reviews/` and `tasks/` annotated or reworded per the rule;
      genuine wave-7 (fuzzing) references untouched
- [ ] The sweep's grep command + hit disposition list recorded in
      Notes (so the next session doesn't re-derive the inventory)
- [ ] No historical record's meaning altered — annotations only where
      the phrasing is load-bearing
- [ ] `taskgraph validate` green after any task-file edits

## References

- docs/plans/implementation.md §Wave 8 (the historical note mandating
  this sweep)
- tasks/review-wave-5.md (the ADR-024 renumber-annotation precedent)
- docs/reviews/003-wave-5-general-review.md (the renumber trail
  example)

## Notes

> To be filled by implementation agent

## Summary

> To be filled on completion