Bug Description

After updating from 2026.2.9 to 2026.2.23, all outbound Telegram API calls fail with TypeError: fetch failed. Inbound polling continues to work (messages are received), but the bot cannot send replies, typing indicators, or any outbound requests.

Steps to Reproduce

1. Have a working OpenClaw setup with Telegram channel on version 2026.2.9
2. Update to 2026.2.23 via npm i -g openclaw@latest
3. Gateway restarts automatically
4. Telegram inbound messages still arrive, but all outbound calls fail

Error Logs

[openclaw] Non-fatal unhandled rejection (continuing): TypeError: fetch failed
    at node:internal/deps/undici/undici:14902:13
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
[telegram] sendChatAction failed: Network request for 'sendChatAction' failed!
[telegram] sendMessage failed: Network request for 'sendMessage' failed!
[telegram] final reply failed: HttpError: Network request for 'sendMessage' failed!
[telegram] deleteMyCommands failed: Network request for 'deleteMyCommands' failed!
[telegram] setMyCommands failed: Network request for 'setMyCommands' failed!

openclaw doctor reports:

Telegram: failed (unknown) - This operation was aborted

Environment

• OS: macOS (Darwin 25.2.0 arm64)
• Node: v22.22.0
• Working version: 2026.2.9
• Broken version: 2026.2.23
• Telegram provider log: [telegram] autoSelectFamily=false (default-node22) — this may be relevant; Node 22's undici/fetch may handle connections differently in the new version

Notes

• Network connectivity to api.telegram.org is fine (curl works from the same machine)
• Multiple gateway restarts did not resolve the issue
• Rolling back to 2026.2.9 immediately fixed Telegram outbound
• The autoSelectFamily=false flag logged by the Telegram provider suggests a possible IPv4/IPv6 issue with Node 22's fetch in the updated dependencies (660 packages changed, 36 added, 10 removed)