openclaw - 💡(How to fix) Fix [Feature]: WhatsApp web idle watchdog should be configurable (30m no-message reconnect) [1 participants]

### Summary

The WhatsApp web runtime currently forces a reconnect after ~30 minutes with no inbound messages:

`No messages received in 30m - restarting connection`

This seems to be a fixed idle watchdog, not a user-configurable setting.

### Environment

- OpenClaw 2026.4.21
- WhatsApp web runtime
- 8GB VPS
- 12-14 WhatsApp groups
- `requireMention: true`
- `groupPolicy: "allowlist"`

### Actual behavior

During quiet periods (overnight / early morning), the runtime reconnects every ~30 minutes even when nothing is wrong.

Effects:
- per-connection counters like `messagesHandled` reset to `0`
- `connectionId` changes every cycle
- log-based monitoring/reporting becomes discontinuous
- reconnect does not appear to fully rehydrate missed group history for auto-reply context

### Expected behavior

Please expose the idle watchdog as a config value, or allow disabling it. Something alongside the existing WhatsApp `web.*` runtime settings would help:
- configurable idle timeout
- optional disable switch
- possibly account-scoped override

### Why this matters

For low-traffic deployments, "no inbound messages for 30m" is normal and should not automatically imply a stale connection. This creates false-positive reconnect churn and breaks monitoring pipelines that rely on connection continuity.

### Extra context

We initially thought this was related to a group-delivery issue, but that turned out to be separate OOM pressure. After increasing Node heap (`--max-old-space-size=4096`), the runtime became stable, and the remaining issue is this 30-minute idle reconnect behavior during quiet periods.

Happy to test a PR on our setup.

### Alternatives considered

_No response_

### Impact

Hardcoding a longer reconnect interval externally, but this is not exposed as a config option either.

### Evidence/examples

_No response_

### Additional information

_No response_