Module rendezvous 

Rendezvous conformance — does a P2P rendezvous speak presence-topology-v0.1 §3.2?

Same shape as the relay checker: pure validators (check_welcome, check_peers) pin the wire rules with no network, and probe is the thin live driver — it announces to a room and validates the introduction sequence the rendezvous sends back (welcome before peers; the ordering contract clients rely on to adopt their assigned id before negotiating).

Structs

RendezvousOutcome

The result of a live rendezvous probe.

Functions

check_peers

Validate a peers message (rv→client: who’s present, or a join delta).

check_welcome

Validate a rendezvous welcome message (rv→client, in reply to announce). Distinct from a relay’s welcome: just {t:"welcome", id:<u32>} — no occupants, no tick_hz (the rendezvous never sees a pose, so it has no rate to suggest).

probe

Connect to url (wss://<host>/rtc/<key>), announce, and validate the introduction the rendezvous sends back. Per §3.2 welcome is OPTIONAL (a minimal rendezvous may let clients keep provisional ids) but peers is not; and when welcome IS sent, it must arrive before peers.