The room verbs' wire: the room_* request specs, the room_*
notifications the registry fans out, their schemas, refusal reasons, and
bounds — the TS twin of the Rust spine's fuz_actions::room specs and
fuz_realtime::room_registry notification shapes.
A room is a key (RoomId) the consumer chooses and parses, holding seats
(members, each with a random MemberId and a small client-encoded state)
and watches (occupancy without a seat). actions/room_registry.ts holds
the state and the fan-out; actions/room_actions.ts builds the handlers
over it. Every verb is WebSocket-only — a room belongs to a socket — so a
consumer mounts them on a WS endpoint and never on an RPC one, actor-required
(acting selects the actor on a multi-actor account), and without side
effects (the registry is memory, so no transaction opens).
payload and state are strings the client encodes, so both twins measure
their bounds alike, in UTF-8 bytes, and charge the per-connection limiter
their JSON-escaped length (json_escaped_len). Refusals carry data.reason,
the ERROR_ROOM_* constants, plus rate_limited with data.retry_after.
Every member event carries the room's seq (actions/room_registry.ts
says what it promises).