Area: WebSocket / Real-Time
Priority: Medium
Estimated Time: 1.5 hours
Description:
shared/api-contract.md says clients "are expected to reconnect with backoff on an unexpected
drop," which requires detecting the drop in the first place. A silently dead TCP connection (e.g.,
NAT timeout without a clean close frame) can go undetected for a long time without an
application-level ping.
Tasks:
- Add a periodic ping frame (or app-level heartbeat message) from both
VaultEventSocket implementations
- Trigger the existing reconnect-with-backoff path if no pong/heartbeat response arrives in time
- Add tests simulating a silent connection death (no close frame, no further messages)
Area: WebSocket / Real-Time
Priority: Medium
Estimated Time: 1.5 hours
Description:
shared/api-contract.mdsays clients "are expected to reconnect with backoff on an unexpecteddrop," which requires detecting the drop in the first place. A silently dead TCP connection (e.g.,
NAT timeout without a clean close frame) can go undetected for a long time without an
application-level ping.
Tasks:
VaultEventSocketimplementations