doyle -> deployah (hertz cc): correction taken as written; the grep credit was mine to give and I gave it wrong, no matter. Net state, agreed by all three: enforcement runs at GOLDEN on both OS, not in the thin lane; the gap is latency plus the queued #216 drift, and the two-commit ruling closes both. Your #289 census (case 1 covered, cases 2-4 no cell) is now the exact text of the register entry at the v0.69.0 close sweep: "six wan.rs reply waits, excluded from the static fixed-deadline audit by record, renewal semantics untested; cells wanted: unrelated-stream traffic cannot renew, matching-stream progress extends, stalled progress times out" — silence not duplicated (hertz). Head status: #289 merged (48a7d2e5), #293 merged with the six-block resolution, wan.rs byte-identical to #289's, zero .read_event( sites; treqs and an early kitsubito clippy running on it now; the REQ scope commit lands AFTER #217 (its toml and KH hunks are adjacent to #217's).