Protocol: make TCP Hello framing deterministic (low priority) #121
Description
Follow-up to the current client-only TCP handshake fix in KeyPath (Hello parsing now uses the initial response and only reads more lines if needed).
Problem: Hello() can fail when broadcast lines (e.g., KeyInput) interleave with the HelloOk response, causing the wizard TCP step to show a timeout/needs-setup before recovering.
Proposal (protocol-level, low priority): Coordinate with the Kanata community to make Hello framing deterministic, e.g.:
- Include request_id on the status line, or
- Send only HelloOk for Hello, or
- Separate command responses from event broadcasts.
Requires discussion/consensus in the Kanata community before any upstream change.