Scope record for this lane: five latent twins are IN SCOPE alongside request_wan.

wan.rs carries six one-shot request/reply functions with the identical shape — send, subscribe, then
an unbounded brain.read_event()? loop exiting only on a decoded reply or EOF: request_wan (:295, this
issue), request_fork (:414), request_redeem (:499), request_answer (:553), request_knock (:636),
request_presence (:680). All six are CLI-side, so the pump's peer_reply_deadline helper yields None
for every one of them and none is bounded today.

Reason for one lane rather than a follow-up: fixing request_wan alone leaves five sites reporting a
budget expiry as NoReply — which is the defect this issue exists to fix, minted five more times. The
precedent is REQ-PUMP-DIAL-FASTFAIL, which fixed request_update and its latent twin request_sync
together rather than filing the twin against ourselves.

Shape: one call-site deadline helper reusing the existing PEER_REPLY_READ_BUDGET (no second
constant), one shared distinct-expiry variant threaded through all six report paths so a timeout
never prints as success or as NoReply.

Ruled by doyle 2026-09-09.