Ben Barclay 64a507da44 feat(relay): handle passthrough_forward over the WS (Phase 5 §5.1, gateway half) (#50702) ... The connector half (gateway-gateway) moves the passthrough plane's post-ACK forward off the HTTP gatewayEndpoint onto the gateway's outbound /relay WS via a new passthrough_forward frame. This is the gateway side: the relay adapter now RECEIVES and handles that frame, so a hosted gateway (no public IP) can process forwarded Class-2/3 traffic (Discord interactions, Twilio) over the socket it already holds — closing the "passthrough inbound doesn't work for hosted gateways" gap. - ws_transport.py: decode the passthrough_forward frame; PassthroughForward dataclass + _passthrough_from_wire (base64 body -> exact bytes, byte parity with the connector's toPassthroughForward); set_passthrough_handler mirrors set_interrupt_inbound_handler. - transport.py: PassthroughHandler type + set_passthrough_handler on the RelayTransport protocol. - adapter.py: connect() wires the passthrough handler; _on_passthrough decodes the (already-sanitized, token-free) forward and, for a Discord interaction, converts it to a MessageEvent routed through the normal agent path (handle_message) — the reply egresses over the outbound / token-less follow_up path, so the gateway never holds the interaction credential. Never raises (a bad forward can't kill the read loop). Non-discord forwards (Twilio) are logged + dropped for now. - docs/relay-connector-contract.md: document the passthrough_forward frame + PassthroughForward shape + §3.1. The interaction -> MessageEvent CONVERSION semantics (slash-command vs button UX, option rendering) are the open sub-design flagged in the spec; the TRANSPORT + receive mechanism (this) is settled per Ben's Gate-2 decision: "the relay adapter handles receiving these events over the WS." Tests (tests/gateway/relay/test_relay_passthrough.py): byte-preservation round-trip (+ malformed-body tolerance), connect() wiring, application-command and message-component interactions route through handle_message with correct session source + scope capture, malformed/non-discord forwards dropped cleanly. 100 relay tests green. Pairs with the connector PR (gateway-gateway).		2026-06-22 20:10:57 +10:00
..
design	docs(profile): update clone-from references	2026-06-13 07:33:58 -07:00
kanban	feat(kanban): gate notifier watcher on dispatch_in_gateway	2026-06-01 20:30:24 -07:00
middleware	fix(middleware): preserve translated downstream failures	2026-06-06 09:26:18 -07:00
observability	feat(observability): observer-grade telemetry hooks + NeMo-Relay plugin	2026-06-03 06:36:46 -07:00
plans	fix(gateway): recover partial Telegram overflow streams	2026-06-10 15:09:35 -07:00
security	docs(security): add network egress isolation guide for Docker deployments (#26385)	2026-05-29 14:09:10 +10:00
chronos-managed-cron-contract.md	fix(cron): serve /api/cron/fire on the dashboard app (hosted-agent surface)	2026-06-19 12:43:30 +10:00
hermes-kanban-v1-spec.pdf	feat(kanban): durable multi-profile collaboration board (#17805)	2026-04-30 13:36:47 -07:00
rca-ssl-cacert-post-git-pull.md	fix(ssl): align guard docs and escape hatch	2026-06-13 21:14:32 -07:00
relay-connector-contract.md	feat(relay): handle passthrough_forward over the WS (Phase 5 §5.1, gateway half) (#50702)	2026-06-22 20:10:57 +10:00
session-lifecycle.md	docs: session lifecycle documentation	2026-06-20 23:23:47 -07:00