Plain stdin sessions now declare they are not remote, so remote-only delivery acks and one auto-mode capability skip out.
What's wrong with this entry?
The plain stdin transport declares that it is not a remote transport, that the host owns the origin of anything arriving on stdin (used to decide whether an inbound message counts as user-driven), and that a confirmed flush always succeeds. Remote-session code branches on that: delivery acks bail out with "not-remote-session", and one auto-mode capability requires a remote transport plus the remote session id.
hostOwnsStdinOrigin
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.
-
v2.1.225
Streaming read index no longer skips messages
Both mention transport
-
v2.1.225
Unknown control messages complete their command lifecycle
Both mention transport
-
v2.1.248
Undelivered events can be handed to a replacement connection
Both mention transport