docs: audit June 23 scaling roadmap ownership

docs/design/2026_06_12_proposed_scaling_roadmap.md

@@ -4,22 +4,25 @@
 **Author:** bootjp
 **Date:** 2026-06-12
 
+> **Superseded roadmap index:**
 > This document is retained as the original sequencing and SLO record. It is
 > not an implementation specification and must not be used as the scope for a
 > combined implementation PR. The
 > [2026-06-23 roadmap](2026_06_23_proposed_scaling_roadmap.md) audits the current
 > implementation, closes completed prerequisites, and tracks the remaining
-> work as separate design documents and milestone PRs.
-
+> work as separate design documents and milestone PRs. It is the current
+> ownership and sequencing authority; this historical document does not
+> describe the current implementation status of its milestones.
+>
 > This roadmap captures the scaling work elastickv needs across four
 > subsystems that today have known ceilings and have not yet been
 > designed past those ceilings. The roadmap itself is not a single
 > milestone — it sequences the work and points each subsystem at a
 > sibling `*_proposed_*.md` design that will land later as its own PR.
 > Per CLAUDE.md the design-doc-first workflow applies: each milestone
 > below ships its own `*_proposed_*` doc before its implementation
-> starts; this file is the shared north star and the sequencing
-> constraint between them.
+> starts. The June 23 ownership index now records the authoritative
+> requirement-by-requirement disposition and sequencing constraints.
 
 ## 1. Motivation