testing/cross_backend/ws_round_trip.ts

Cross-process WebSocket round-trip suite — the cross-process counterpart to the in-process testing/ws_round_trip.ts harness.

Where the in-process harness drives register_action_ws against a fake Hono upgrade (no wire), this suite performs a real WebSocket upgrade against a spawned backend via create_ws_transport (the ws npm package), so the actual upgrade handshake + per-connection auth + JSON-RPC dispatch over the socket are exercised end-to-end. It is the only coverage of the spawned binary's live WS path — the standard cross-process bundle (describe_standard_cross_process_tests) omits WS by design, so consumers call this alongside it.

Consumer-agnostic. Every case drives the heartbeat protocol action, which assert_ws_endpoints_include_protocol_actions guarantees is present on every WS endpoint — so the suite needs no knowledge of a consumer's domain WS methods. It validates the transport, not the domain.

The first three cases mirror the upgrade stack register_ws_endpoint wires (origin check → require_auth → dispatch): an authenticated upgrade round-trips heartbeat; an anonymous upgrade is refused; a disallowed-origin upgrade is refused. Per-connection auth is enforced at upgrade time (not per message), so the negative cases assert the upgrade itself rejects rather than a per-message error frame.

A fourth case (gated on rpc_path) covers server-initiated close: an authenticated socket is dropped when the account's sessions are revoked mid-connection. Per-message dispatch never re-checks credential validity, so the live socket survives on the audit-fed create_ws_auth_guard seam — firing account_session_revoke_all over the keeper's session channel emits session_revoke_all, which closes the socket. Omit rpc_path to skip it (consumers without the standard account actions on their RPC endpoint).

Gated on capabilities.ws — backends without an end-to-end WS transport skip (the cases still surface as .skip in the report). Cross-process only: create_ws_transport needs a real bound socket, so wire it from a *.cross.test.ts file, never an in-process setup.