Problem
Inbound whispers can be injected manually as client-* events, but this is undocumented. Outbound whispers initiated by the page are not observable because the real Pusher connection is disconnected.
Proposed direction
Document inbound whisper injection and record outbound client events at the Pusher channel boundary.
Acceptance criteria
- A first-class API can emit an inbound whisper without manually prefixing
client-.
- Whispers sent by application code through Echo are recorded while simulated.
- Tests can inspect and assert channel, whisper name, and payload.
- Only valid private and presence client events are recorded.
- Real Echo/Pusher browser coverage exercises both inbound and outbound whispers.
Problem
Inbound whispers can be injected manually as
client-*events, but this is undocumented. Outbound whispers initiated by the page are not observable because the real Pusher connection is disconnected.Proposed direction
Document inbound whisper injection and record outbound client events at the Pusher channel boundary.
Acceptance criteria
client-.