Problem

During Telegram recovery testing, sending /reset through openclaw agent --channel telegram did not rotate the live Telegram direct session. The gateway path failed with missing operator.admin, then the CLI fell back to the local embedded path and appended Reset acknowledged. into the same poisoned session.

Impact

A user can believe a bad session was reset while the runtime is still reading the same poisoned transcript. That makes stale-answer and tool-confusion recovery unreliable.

Acceptance

• /reset from Telegram/direct chat must call the gateway sessions.reset path with the required authority or return a visible failure.
• No local fallback may claim success unless the live gateway session was actually rotated.
• Add a test that verifies session id changes for agent:main:telegram:direct:<user> and old transcript is archived.
• Include the reset result in operator logs with old session id, new session id, key, and caller channel.