The SDK's query() and remote/bridge session IO now support a distinct stdin lane apart from the initial prompt
What
The class driving a remote (bridge/cloud) session's stream-json IO now accepts a new stdinLane constructor option, alongside the existing streamUrl, initialPrompt, sessionState, and similar options. The SDK's query() function, which builds either a local or remote-controlled query stream, now keeps the initial string prompt separate from a raw async-iterable/generator input, passing the latter through as this new stdinLane rather than always coercing all input into a single combined async generator.
Why
Separating the initial prompt from ongoing stdin input lets remote/bridge sessions handle streamed input more flexibly instead of forcing everything through one merged stream.
What `stdinLane` does and how it affects remote session behavior is not specified in the finding.