Give the held-message flow one owner

2026-09-29 11:03:02 +02:00
parent 57f53d56f1
commit cc18569a05
6 changed files with 107 additions and 83 deletions
@@ -209,14 +209,6 @@ hardest, and the held-message flow across `incoming-requests.ts`, `held-messages
 - [ ] **Lift Locality to 7, and confirm it with a scoring run.** A run reading 7.0 or above also
      retires the #30, #46 and #48 decision.

- [ ] **Give the held-message flow one owner — next, the condition #48 merged under.** Whether a
-      message is still held, and so whether its receipt may pass the drain, is decided across
-      `IncomingRequests.emitSms()`, `HeldMessages.offer()`/`MessageHold`, `createSms()`'s handlers in
-      `sms.ts` and `Session`'s rejection handler, which finds the hold again through a `WeakMap`
-      keyed on the `Sms`; `MessageHold.answered()` defers its release a `setImmediate` so a
-      `sendDlr()` straight after `sendResp()` still counts as held. All four seats of the #48 run
-      ranked it second hardest; the inherited architect put it at about two days.
-
 ### Correctness

 - [ ] **Refuse to open a link that dropped while its rebind was answered.** A peer sending