Bug Report: Reply routing fails when session.dmScope is "main"

Summary

When session.dmScope is configured to "main" to unify DM sessions, replies to messages originating from a secondary channel (e.g., Telegram) are not routed back to that channel. The inbound message is correctly ingested into the main session, but the outbound reply is not sent back to the originating user on the secondary channel.

Steps to Reproduce

1. Set up a standard OpenClaw instance with a primary web chat session and a configured Telegram channel.
2. Initially, session.dmScope defaults to "per-channel-peer". Observe that messages from Telegram correctly create a separate session.
3. Edit ~/.openclaw/openclaw.json and change the session scope to unify sessions:

   "session": {
     "dmScope": "main"
   }

4. Restart the OpenClaw gateway for the change to take effect (openclaw gateway restart).
5. Send a message from the paired user on Telegram to the OpenClaw bot.

Expected Behavior

The message from Telegram is received by the agent in the main, unified session. The agent's reply is successfully sent back to the user on Telegram.

Actual Behavior

The message from Telegram is correctly received and processed in the main session. The agent generates a reply. However, the reply is never delivered to the user on Telegram. The user can only see that a reply was generated by observing the session's history through the web UI. The outbound routing path appears to be broken in this specific configuration.

Environment

• OpenClaw Version: 2026.2.26
• Platform: macOS (Darwin)
• Installation Method: Homebrew