alkstore/tasks/release-renumber-sweep.md

id, name, status, depends_on, scope, risk, impact, level, tags

id	name	status	depends_on	scope	risk	impact	level	tags
release-renumber-sweep	Renumber sweep — historical "wave 7" references to the release pass	completed		narrow	trivial	isolated	implementation	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

Filled by implementation agent (2026-10-10).

Sweep command (what found the inventory):

grep -rn "wave. 7\|wave-7" docs/reviews/ tasks/

filtered by hand against the distinguishing rule (a reference is stale only if it means the release pass; fuzzing-wave and review-wave-7 references are correct).

Hit disposition list — every non-excluded hit and how it was disposed. Annotation style throughout: the bracketed parenthetical wave note (the review-wave-5.md ADR-024 precedent's shape, applied to the second renumber — "wave 8 since the fuzzing wave's renumber (2026-10-10)"), appended to the historical phrasing, which is kept verbatim:

• docs/reviews/001-waves-1-2-general-review.md header note ("release-readiness N-1 review — wave 7 since ADR-024's renumbering") — annotated (added the wave-8 note; historical, load-bearing).
• docs/reviews/001-waves-1-2-general-review.md §7's "Wave 6 release review" bullet — annotated (this one is double-removed: wave 6 at §7's writing, wave 8 now; the historical wave-6 label kept, parenthetical trail note added).
• docs/reviews/002-wave-4-general-review.md security-posture bullet ("the logging story is a wave-7 item (a wave-6 item when recorded — renumbered by ADR-024; …)") — annotated (a third-generation trail annotation: wave 6 → 7 by ADR-024 → 8 by the fuzzing wave; not in the task's original site list — found by the grep-for-more).
• docs/reviews/003-wave-5-general-review.md flake-watch echo ("the release-readiness watch — wave 7 since ADR-024's renumbering") — annotated.
• docs/reviews/003-wave-5-general-review.md Recommendation's renumber-trail parenthetical ("Findings 2–3 to wave 7's pre-release pass") — annotated (the parenthetical was itself one renumber old; extended to the second).
• docs/reviews/003-wave-5-general-review.md Recommendation's closing ("folds into the release-readiness pass (wave 7)") — annotated.
• tasks/review-wave-5.md AC list ("since renumbered to wave 7 when the mem engine inserted at wave 6, ADR-024") — annotated.
• tasks/review-wave-5.md §6 watch flag ("since renumbered to wave 7, ADR-024") — annotated.
• tasks/review-wave-5.md ledger update ("owed by the wave-7 watch carriage") — annotated (carriage named as the release-readiness watch, wave-8 note attached; historical wave-7 phrasing kept).
• tasks/review-wave-6.md References ("Findings 2–3's wave-7 park") — reworded (live pointer pointing a future reader at the wrong wave — now "pre-release-pass park" with the wave-8 note).
• tasks/review-wave-6.md Finding (wake-ordering, "recorded for the wave-7 pre-release pass") — annotated.
• tasks/review-wave-6.md Summary ("dispositions for the wave-7 pre-release pass") — annotated.
• tasks/review-wave-4.md gate record ("the logging story is a wave-7 item (release readiness)") — annotated (not in the original site list — found by the grep-for-more).
• tasks/pg-fix-scheduler-fire-wake.md flake-ledger note ("owed by the wave-7 watch carriage") — annotated (not in the original site list — found by the grep-for-more; mirrors the wave-5 ledger wording it echoes).

Untouched, verified correct (the distinguishing rule's exception arm): the fuzz-* tasks and tasks/review-wave-7.md (genuine fuzzing-wave/review references — wave 7 since 2026-10-10 is those waves' correct number); tasks/release-publish-prep.md (points at tasks/review-wave-7.md, a genuine wave-7 record pointer, not a release-pass number); tasks/review-wave-8.md ("stale wave-7 references gone or spot-checked" — a wave-8 record auditing this sweep, correct as written).

Found outside scope, left untouched: docs/architecture/README.md ("wave 6 — release readiness renumbered to wave 7") and docs/architecture/decisions/024-mem-engine.md ("release readiness renumbered to wave 7"). Both are historical renumber-trail records accurate at their writing (the fuzz renumber was later the same day), and ADR-024 is an accepted immutable ADR — history is not rewritten in place. Recorded here so the residue doesn't re-derive; the task's mandate and the plan's §Wave 8 historical note cover docs/reviews/ and tasks/ only. If anyone wants these swept too, it's a deliberate record-hygiene call, not a loose end from this task.

Word-variant sweep: case-insensitive wave-7|wave 7|wave7 checked; no additional phrasings beyond the inventory above.

Summary

Filled on completion (2026-10-10).

All stale "wave 7"-means-release-pass references in docs/reviews/ (001 header + §7 bullet, 002 security bullet, 003 flake-watch echo + Recommendation trail + closing) and tasks/ (review-wave-5 AC + §6 watch flag + ledger update, review-wave-6 References + Finding + Summary, review-wave-4 gate record, pg-fix-scheduler-fire-wake ledger note) disposed: 12 annotated in place, 1 References entry reworded (live pointer), zero meaning-altering edits — every historical "wave-7" phrasing kept and the wave-8 note attached per the renumber-annotation precedent. Genuine fuzzing-wave/review-7 references untouched; two out-of-scope architecture-doc trail records left and documented in Notes. taskgraph validate green; no code touched, so build/test/clippy/fmt gates unaffected (docs + task-file edits only).