relay

Overview ¶

Package relay maintains fort serve's outbound tunnel to the 028 gateway: one WebSocket to the broker, per-client-session Noise IK handshakes (exec/relay/secure), and sealed HTTP/SSE service against an injected http.Handler — the transport never imports ui (seam: it moves bytes).

Config{URL, Token, Key, MinBackoff}; New(handler, cfg) *Transport; (t *Transport) Run(ctx) error — reconnect loop with exponential backoff (MinBackoff..30s, jittered) until ctx is done.

Per inbound frame:

hs1  -> NewResponder(cfg.Key) for that stream; ReadMessage(payload);
        WriteMessage -> reply kind hs2; store Session on completion.
req  -> sess.Open -> ReqPayload -> serve:
          non-stream: httptest.NewRecorder over the handler; reply res.
          stream (Accept: text/event-stream): spawn goroutine with a
          cancelable context; a streamWriter ResponseWriter seals+sends a
          res{Stream:true} on WriteHeader, then chunk frames on each
          Flush; register cancel under (stream,id) for "end".
end  -> sess.Open -> id -> cancel that request.
bye  -> drop the stream's session + cancel its in-flight requests.

Writes to the socket are serialized with a mutex — and, crucially, each Seal happens under that same lock immediately before its write, so the AEAD nonce order (per session) always matches wire order, which is what the peer decrypts in. A dropped socket cancels every in-flight request and re-dials.