fix(gateway): stream consumer first message drops thread context

[hrygo]

Problem

When a user @mentions the bot inside a group topic thread (Feishu group topic / Slack thread / Telegram forum), the first streamed message chunk is sent via message.create with receive_id=chat_id (the main group) instead of being threaded into the topic. The response — including any visible thinking/reasoning — appears in the main group chat rather than the topic thread.

This is a cross-platform architecture defect in GatewayStreamConsumer that has been reported multiple times across different platforms:

• Feishu topic progress messages create new topics instead of staying in the original topic #6969 — Feishu: progress messages create new topics instead of staying in original topic
• Feishu: Bot replies leak out of P2P topic thread into main chat #9916 — Feishu: bot replies leak out of P2P topic thread into main chat
• Telegram: Final response chunks lose thread_id, breaking forum topic routing #7355 — Telegram: final response chunks lose thread_id, breaking forum topic routing

Root Cause

Two bugs:

Bug 1: GatewayStreamConsumer sends first chunk without reply_to

gateway/stream_consumer.py — _send_or_edit() first-message path:

# BEFORE — no reply_to passed
result = await self.adapter.send(
    chat_id=self.chat_id,
    content=text,
    metadata=self.metadata,
)

self._message_id is None on the first send, and no fallback reply_to is provided. The adapter receives reply_to=None → falls to message.create with receive_id=chat_id → message lands in main chat.

Meanwhile, the non-streaming path in base.py has always correctly passed reply_to=event.message_id. This is why short answers work fine — only streaming (long answers / tool-heavy responses) triggers the bug.

Bug 2: FeishuAdapter._send_raw_message fallback loses thread context

When message.reply fails (e.g. message withdrawn, error codes in _FEISHU_REPLY_FALLBACK_CODES) and falls back to message.create, the fallback uses receive_id=chat_id even though metadata.thread_id is available — as independently identified in #9916.

Fix (3 files)

File	Change
gateway/stream_consumer.py	__init__ accepts optional initial_reply_to_id; _send_or_edit passes it as reply_to on first send
gateway/platforms/feishu.py	_send_raw_message fallback checks metadata.thread_id, uses receive_id_type="thread_id" instead of "chat_id"
gateway/run.py	Both GatewayStreamConsumer creation sites (proxy path L8000 + local path L8575) pass initial_reply_to_id=event_message_id

Affected Platforms

Any platform using topic/thread routing:

• Feishu — group topics (群主题), P2P topic threads
• Telegram — forum topics
• Slack — thread replies
• Discord — thread messages
• Mattermost — per-issue Mattermost adapter ignores metadata.thread_id, so gateway thread replies post to channel root #12063

Reproduction

1. Create a group chat topic in Feishu (or forum topic in Telegram)
2. @mention the bot inside the topic thread
3. Ask something that triggers a long response or tool use (streaming)
4. Observe: the streamed response appears in the main group chat, not in the topic thread
5. Short non-streaming answers work correctly

Backward Compatibility

initial_reply_to_id defaults to None — no impact on existing code or platforms without thread routing.

Closes

Closes #6969
Closes #9916
Closes #7355

[teknium1]

Merged via salvage PR #23437 (#23437). Your two commits were cherry-picked onto current main with your authorship preserved (re-attributed from the bot-authored commit on your branch to hrygo). We added a test compat fix so the new Feishu fallback test runs in environments without the lark SDK installed, plus an AUTHOR_MAP entry. Conflict against PR #23420 (just-landed #10748 fix) was resolved by merging both fixes in the same chunk loop. Thanks for the fix — this also closes paths #6969 and #9916 as a side effect.