b4a5ce62e7
`_warn_liveness_config_disabled` told operators an unusable value turns off "the websocket liveness probe". That is true for the interval, threshold, ack-age and latency knobs, which sit in the probe's startup guard, but `websocket_event_max_silence_seconds` is only checked inside `_read_websocket_health`, so ack-age/latency keep guarding. Say so, or an operator reading the log would believe the whole watchdog is down.