ssh session has no response

The input in the ssh session has no response. In another cloned session with the same session, commands can be input and executed. Similarly, after reconnecting to this session, commands can be input and executed. This indicates that the problem does not lie with the ssh server but with Windterm.

No source file, test, or entry point is named. Start by reproducing the unresponsive input in one SSH session while comparing a cloned or reconnected session, then trace the session input path. Done means input is accepted and commands execute reliably without requiring reconnection.

Written by the indexing model from the issue text.