Correct the doc claims the prose sweep falsified, and file the rest

AGENTS.md

@@ -318,7 +318,7 @@ the file.
 
 ### [Internals and tests](docs/decisions.md#internals-and-tests)
 
-- #30 and #46 merged under the comprehension floor, and Locality is the next work.
+- #30 merged under the comprehension floor, and Locality is the next work.
 - A listener that rejects is routed by Node's `captureRejections`, not by hand-dispatching.
 - The four-line abort dance is copied across `LinkGate`, `IdleWaiters`, `PendingRequests` and
   `SendWindow` rather than extracted.

docs/decisions.md

@@ -773,13 +773,12 @@ rule and an index of the titles below.
 
 ## Internals and tests
 
-- **#30 and #46 merged under the comprehension floor, and Locality is the next work.** Maintainer's call,
+- **#30 merged under the comprehension floor, and Locality is the next work.** Maintainer's call,
   2026-09-27. A four-seat scoring run, depth 1, read the project at 6, 6, 7 and 6 (mean 6.25), every
   seat capped by Locality in the held-message and shutdown code #30 does not touch, where the floor
   is 7.0. The chunks after #30 lift Locality to 7 before any other work. Serves goal 8's
   reshapeable internals, which a reader has to understand before reshaping. Valid until a scoring
-  run reads 7.0 or above. #46, maintainer's call 2026-09-28, merged as a step of that work at 6, 6, 7
-  and 7, Locality 5, 5, 6 and 6, up from 6, 6, 7 and 6 and Locality 5, 5, 6 and 5 the same day.
+  run reads 7.0 or above.
 
 - **A listener that rejects is routed by Node's `captureRejections`, not by hand-dispatching.** Both
   emitters construct with `captureRejections: true` and implement

todo.md

@@ -203,7 +203,7 @@ A second four-seat run on 2026-09-28, after #35–#40, read 6, 6, 7 and 6 again,
 and 5. Every seat ranked the session's lifecycle hardest and least wanted to modify it.
 
 - [ ] **Lift Locality to 7, and confirm it with a scoring run.** A run reading 7.0 or above also
-      retires the #30 and #46 decision. The sub-items are what the 2026-09-28 run named, most seats first.
+      retires the #30 decision. The sub-items are what the 2026-09-28 run named, most seats first.
 - [ ] **Give the link's liveness one owner.** A third run the same day, after #46, read 6, 6, 7 and
       7, Locality 5, 5, 6 and 6; all four seats ranked `drain()`/`end()`/`teardown()`/`retrying()`
       in `session.ts` hardest, because whether the link lives is kept in `Session.lifecycle`,