Cross-session connections that never send a full line are closed on a deadline.
What's wrong with this entry?
The local socket that carries messages between sessions now closes any connection that fails to send a complete line within a configured first-line deadline, so a stalled or probing peer no longer holds a slot open.
- Each connection arms a timer on accept, cleared on close or error; the timer does not keep the process alive.
- The drop is logged, and the first one in a session reports a cross-session inbox auth telemetry value.
[uds-messaging] Closing a connection that sent no complete line within
Strings lifted out of the shipped bundle, so the claim above can be checked against them.