The gateway in jcode-base already speaks the full session protocol, but
nothing exercised it host-to-host, so it was unclear whether remote jcode
worked at all. It does: this adds a stdlib-only client and an end-to-end
check, validated driving a Windows 11 session (including remote bash tool
calls) from Linux over Tailscale.
- scripts/remote/gateway_client.py: minimal gateway WS client that answers
server pings, which is the non-obvious reason a naive client sees zero
events and appears to hang.
- scripts/remote/remote_check.py: health -> pair -> ws -> subscribe ->
get_history -> real agent turn, caching the token at mode 600.
- README documents the two traps that actually cost time: Windows
auto-created inbound *block* rules for jcode.exe that override any allow
rule, and history not being pushed on subscribe.
jeremy