[Bug]: Feishu oc_ (OpenChat) chats create duplicate group/direct sessions — outbound vs inbound chatType mismatch

Bug type

Bug

Summary

When OpenClaw proactively sends messages to a Feishu OpenChat (oc_ prefix) via message send or cron delivery, the outbound path creates a direct session key (e.g. agent:main:feishu:direct:oc_xxxx). However, when a user sends a message in the same chat, the inbound webhook path creates a group session key (agent:main:feishu:group:oc_xxxx). This results in two separate sessions for the same chat, with conversation context split between them.

Related: #52342 fixes the inbound isGroup detection for oc_ chats, but the outbound routing (buildChannelOutboundSessionRoute / resolveSessionKey) still uses the default chatType inference, which doesn't apply the same oc_ → group correction. Even after #52342 merges, the outbound path will continue creating direct sessions for oc_ chats.

Steps to reproduce

1. Configure a Feishu OpenChat (话题群, chat_id starts with oc_)
2. Have OpenClaw proactively send a message to the chat (e.g., via heartbeat, cron, or message send tool)
3. Observe sessions.json — a feishu:direct:oc_xxxx entry is created
4. Send a message as a user in the same chat
5. Observe sessions.json — a feishu:group:oc_xxxx entry is created
6. Now two sessions exist for the same chat, with different conversation histories

Expected behavior

A single session per chat_id, regardless of whether messages are inbound or outbound-initiated.

Actual behavior

Two sessions created:

• agent:main:feishu:direct:oc_xxxx (from outbound/cron delivery)
• agent:main:feishu:group:oc_xxxx (from inbound webhook)

The AI loses context between the two, and replies may route to the wrong session.

Suggested fix

1. Apply #52342's isFeishuGroupChat logic to the outbound path — buildChannelOutboundSessionRoute and related functions should use the same oc_ prefix check
2. Session key dedup on creation — Before creating a new session, check if sessions.json already has an entry with the same chat_id (ignoring the group/direct prefix). If so, reuse the existing session instead of creating a duplicate
3. Gateway restart reconciliation — On startup, scan for duplicate group/direct session keys pointing to the same chat_id and merge or deduplicate them

Environment

• OpenClaw version: 2026.3.28
• Channel: Feishu (WebSocket mode)
• OS: Ubuntu on WSL2
• Affected chat_ids: oc_ prefixed OpenChat/topic groups

Workaround

Manually merge the duplicate session .jsonl files and update sessions.json to remove the stale key.