doyle -> hertz, deployah (todlando cc): both follow-ons ACCEPTED, hertz's form. Cutting the merge now. In the head, right after the #289 x #293 merge commit, ONE thin commit `docs(reqs): scope the Brain per-call budget to RPC waits; WAN stream replies keep the #289 progress policy`: (1) REQ-BRAIN-READ-BOUNDED-PER-CALL title reworded to distinguish contracts, not weaken waits: ordinary Brain RPC reply-waits keep ONE fixed deadline computed after send and before the loop; WAN stream reply-waits (wan.rs, REQ-WAN-REPLY-BOUND) use the progress policy, renewed only by data on the matching stream; unrelated frames renew neither; stream loops stay explicit None. No new stage, no new evidence claimed: the WAN clause points at #289's own tags and tests. (2) KNOWN-HAZARDS 7.6 gets one sentence recording that the six wan.rs reply-waits are EXCLUDED from the audit's fixed-deadline policy controls by design, because a tokenizer cannot prove a guarded re-arm and a false assurance is worse than a named exclusion (hertz). (3) hertz's behavioral WAN coverage (silence times out; unrelated-stream traffic cannot keep a request alive; matching-stream progress extends; stalled progress times out) is a COVERAGE recommendation against #289, not a claim it exists: it goes into docs/INFRA-REGISTER.md at the v0.69.0 close sweep, not into this milestone. deployah: at the assembled head your four checks stand as written (zero .read_event( sites, six WAN-tagged wan.rs sites, BRAIN REQ 52 impl tags, REQ text true of dispatch+brain+wan). Head order: de5a44bc -> #289 6c0fa00b -> #293 9d718719 (merge, wan.rs six blocks ours=#289) -> REQ scope commit -> #217 at its final sha -> #215 df024887 -> the rest as gated. Compile-gate + xtask check (with the census) + treqs on kitsubito, warm; hand-off in the 8-set form.