What's wrong with this entry?
The byte-stream watchdog in remote sessions now distinguishes "the network really went idle" from "your laptop went to sleep". When the wall-clock idle exceeds the expected interval by enough to look like a system suspend, it logs Stream watchdog fired after suspend (actual idle <ms> ms (sleep/suspend), re-arming and re-arms instead of declaring the stream dead. Late watchdog suppressions are also logged as [byte-watchdog] suppressed: late=.
Watchdog re-arm (search for "Stream watchdog fired after suspend" and "[byte-watchdog] suppressed:").
Strings lifted out of the shipped bundle, so the claim above can be checked against them.