Admin socket specification notes

The captured staff console has no WebSocket, Socket.IO or staff-wide event-stream endpoint. Its implemented interface is request/response HTTP. Refresh the relevant HTTP view to obtain current ticket, audit, usage or job state; do not connect a customer document room to monitor staff operations.

The document collaboration service on live.handwrites.io is a separate binary WebSocket contract. The Regular Accounts socket specification documents its Yjs/lib0 frames, document-specific admission, presence and persistence. A staff cookie, customer-inspection reason, elevated support role or staff-hook secret is not a room token and does not grant document collaboration access.

Staff security/retention hooks are outbound signed HTTP deliveries, not sockets. Their registration, deletion and test actions are covered by the Admin HTTP reference; delivery internals are documented in the Internal runbooks. Likewise, the Email Routing Worker and SNS delivery callback use private service authentication, not a socket session.

No speculative socket protocol is defined here. Adding one requires a separate reviewed authentication, authorization, event, reconnect and retention contract before it can become a supported console interface.