Sterister
594992a183
Adds the bridge-connection-lifecycle signal that closes Prism's
~45s revoke window down to one server→client round-trip (~50ms).
Server (`@shade/inbox-server`):
- `inbox.peer_connected` / `inbox.peer_disconnected` events on the
0↔1 boundary across WS + SSE bridges. Long-poll deliberately not
tracked (every poll boundary would flap; push transports are also
the only ones where instant revoke matters).
- `PresenceTracker` collapses two parallel bridges (e.g. WS + SSE
during fallback handover) into one connect/disconnect pair.
- `GET /v1/bridge/presence` SSE endpoint: signed query with
`kind: 'presence'`, `watched: string[]`; on open streams a
per-address snapshot, then change frames filtered server-side.
MAX_WATCHED_ADDRESSES = 64. Subscribing does not itself count as
a peer-bridge connection.
- `createBridgeRoutes` now returns `{ app, websocket, presence }`.
Client (`@shade/transport-bridge`):
- `PresenceBridge.subscribe({ watch, onPresenceChange })` →
`{ addPeer, removePeer, watching, unsubscribe }`. addPeer/removePeer
mutate via reconnect with a fresh signed query.
- `signPresenceQuery` helper for non-PresenceBridge consumers.
Tests cover all four acceptance criteria from the Prism request:
server-event smoke, online→offline subscription, address scoping
(carol invisible to a [alice]-only sub), reconnect, plus an
addPeer/removePeer regression.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@shade/transport-webrtc
V3.11 — direct peer-to-peer chunk transport for Shade transfers via
RTCDataChannel. Plugs into @shade/transfer's ITransferTransport
contract and wires automatically into @shade/sdk via
shade.configureWebRTC().
import { createShade } from '@shade/sdk';
import { nativeRtcFactory } from '@shade/transport-webrtc';
const shade = await createShade({ prekeyServer });
shade.configureWebRTC({ factory: nativeRtcFactory() });
shade.configureTransfers({ resolveBaseUrl });
await shade.upload({ to: 'bob', input: file }); // → P2P when NAT allows,
// HTTP otherwise.
See docs/webrtc.md for the full guide: NAT-traversal realities, TURN config, glare resolution, wire format, diagnostics, and end-to-end test recipes.
What's inside
WebRtcConnection— one peer connection between two Shade endpoints, driving offer/answer/ICE through Shade's own ratchet.WebRtcConnectionManager— per-peer pool with deterministic glare resolution.WebRtcSignalingChannel— JSON signaling messages multiplexed overShade.send/Shade.onMessage.WebRtcTransferTransport— implementsITransferTransportover the managed DataChannel; ack-correlated by 16-byte requestId tokens.MemoryRtcFactory— in-process WebRTC simulator for tests.nativeRtcFactory()— adapter overglobalThis.RTCPeerConnection(browsers / Deno / Cloudflare Workers).
Adapters
@shade/transport-webrtc ships only the standard-API adapter
(nativeRtcFactory). For Bun / Node, wrap your library of choice
behind the IRtcFactory interface — only createPeerConnection,
createDataChannel, and standard addEventListener are required.
Recommended adapters: