Version 2026.4.24: Per-agent heartbeat not triggered + QQbot delivery fails to send messages

[livid night]

OpenClaw 2026.4.24 Issue Summary
Environment
OpenClaw 2026.4.24; Ubuntu Server; DeepSeek V4 Pro; Dual Agents (main + nihao in agents.list); Dual QQbot Accounts (default + nihao, isolated via bindings routing); OPENCLAW_DISABLE_BONJOUR=1 (avoids "CIAO PROBING CANCELLED" crash).
Issues
Issue 1: Per-agent heartbeat not triggered
Config:
"agents": {
"defaults": { "heartbeat": { "every": "0m", "target": "none" } },
"list": [{"id": "main", "default": true},
{"id": "nihao", "heartbeat": {"every": "1m", "target": "qqbot", "to": "<QQ openID>", "accountId": "nihao", "directPolicy": "allow", "isolatedSession": true}}]
}
Phenomenon: No heartbeat logs. Heartbeat only works under "defaults" (main returns HEARTBEAT_OK); per-agent heartbeat never runs.
Issue 2: Default-layer heartbeat fails to deliver to QQ
Config:
"defaults": {"heartbeat": {"every": "1m", "target": "qqbot", "to": "<QQ openID>", "accountId": "nihao", "directPolicy": "allow", "ackMaxChars": 0}},
"channels": {"defaults": {"heartbeat": {"showOk": true, "showAlerts": true}}, "qqbot": {"heartbeat": {"showOk": true, "showAlerts": true}}}
}
Phenomenon: Heartbeat triggered, LLM responds (not HEARTBEAT_OK), but no QQ message. target: "last" tested, no success.
Issue 3: CLI scope upgrade pending approval
Error for commands (openclaw cron add / openclaw system heartbeat): "pairing required: device is asking for more scopes than currently approved". dangerouslyDisableDeviceAuth does not resolve.
Questions

1. What special configurations are needed for per-agent heartbeat in this version?
2. Is there a version restriction for heartbeat delivery to QQbot?