docs: keep historical migration disposition in project authority

docs/releases/v0.5.12.md

@@ -109,10 +109,6 @@ those development judgments.
   recovery behavior, not a global latency guarantee or provider billing-token
   savings. A retained startup catalog-unavailable control also failed on its
   unchanged parent; the evidence is not an all-green test-suite claim.
-- Historical non-code layout judgments remain valid evidence. Their canonical
-  machine registration can remain deferred until a capable runtime is adopted
-  and the owning judge policy is selected; this is not implicit registration
-  or authority to backdate a receipt.
 - Whole-package substance review, exact-release verification and publication
   must still bind this prepared candidate. These notes do not announce an
   available npm release or authorize runtime adoption.