Remote input is written straight through, dropping the guard for writes after close.
What's wrong with this entry?
The remote transport now pushes received server events and piped stdin straight into the input stream. The wrapper that guarded against writes arriving after the stream closed, and the telemetry event it fired once per lane when that happened, are both gone.
[remote-io] keep_alive sent
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.