Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Keep this PR open. It is maintainer-authored (MEMBER) and carries the protected maintainer label, so it needs explicit maintainer handling. Current main also does not yet expose or pass the proposed WhatsApp/Baileys socket timing settings, so the PR is still an active implementation candidate for #56365 rather than obsolete cleanup.

Best possible solution:

Keep the PR open for maintainer review. The likely best path is to validate the Baileys timing contract, review the chosen OpenClaw defaults and web.whatsapp.* config shape, run the targeted WhatsApp/config checks plus the appropriate changed gate, then land or request revisions. After merge, #56365 can be closed for the timing portion or narrowed to any remaining non-timing socket-config needs.

What I checked:

• Protected maintainer item: The provided GitHub context lists the PR author association as MEMBER and labels include maintainer; this workflow must not auto-close maintainer-owned or protected-label items. (189c91eae6e1)
• Current socket boundary lacks timing passthrough: createWaSocket currently accepts only authDir and onQr, then calls makeWASocket without keepAliveIntervalMs, connectTimeoutMs, or defaultQueryTimeoutMs. (extensions/whatsapp/src/session.ts:126, 189c91eae6e1)
• Current config schema lacks web.whatsapp: WebConfig and the runtime zod schema currently expose enabled, heartbeatSeconds, and reconnect, but no web.whatsapp timing object. (src/config/types.base.ts:293, 189c91eae6e1)
• Reconnect/login paths do not preserve timing today: Current reconnect-after-515 and normal controller socket creation call createWaSocket with only authDir plus QR callback where relevant, so even a future call-site option would not currently flow through these paths. (extensions/whatsapp/src/connection-controller.ts:197, 189c91eae6e1)
• Docs do not yet document the proposed settings: The WhatsApp docs mention the reconnect watchdog and existing operations keys, but not web.whatsapp.* socket timing tuning on current main. Public docs: docs/channels/whatsapp.md. (docs/channels/whatsapp.md:148, 189c91eae6e1)
• Dependency contract supports the intended options: The pinned WhatsApp dependency is @whiskeysockets/baileys@7.0.0-rc.9; upstream SocketConfig includes connectTimeoutMs, defaultQueryTimeoutMs, and keepAliveIntervalMs, and upstream defaults are 20000, 60000, and 30000 respectively. (extensions/whatsapp/package.json:7, 189c91eae6e1)

Remaining risk / open question:

• Because this changes a bundled channel's liveness behavior and public config schema, it still needs normal maintainer review and CI/Testbox validation before merge.
• The linked WhatsApp bridge: makeWASocket config passthrough — expose Baileys socket timing and proxy options #56365 also discussed broader arbitrary socket config/proxy passthrough; this PR intentionally covers the timing subset, while current main already has ambient proxy handling.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 189c91eae6e1.

Greptile Summary

This PR exposes three Baileys socket timing parameters (keepAliveIntervalMs, connectTimeoutMs, defaultQueryTimeoutMs) through a new socket-timing.ts module and threads them into every WhatsApp Web socket creation path — monitor, login, QR login, reconnect, and direct inbox. The new config fields are wired through the type system, Zod schema, generated schema, labels, help text, and documentation.

Confidence Score: 5/5

This PR is safe to merge — well-structured, fully tested, and no correctness issues found.

All socket creation paths receive explicitly resolved timing values via resolveWhatsAppSocketTiming, which validates inputs with positiveInteger. The Zod schema, TypeScript types, generated schema, labels, help text, docs, and changelog are all consistently updated. Tests cover the default, config-override, and call-site-override cases. No logic bugs, data-loss paths, or security concerns identified.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix: expose WhatsApp Baileys socket timi..." | Re-trigger Greptile}

Merged via squash.

• Prepared head SHA: d34755262f8e543cc50a88acb48391a9bda2c42a
• Merge commit: dd643c82b55efef49787568e946816ecabb6215e

Thanks @velvet-shark!