Greptile Summary

This PR removes the !threadReplyMode guard from streamingEnabled in reply-dispatcher.ts, enabling Feishu streaming card replies in topic/thread group mode (threadReply: true).

The change is safe for the most common scenario: when replyToMessageId is present, streaming-card.ts selects the reply send-mode with reply_in_thread: true, which the codebase already documents as the reliable routing path for cards in Feishu topics. The only edge case to be aware of is when replyToMessageId is absent but rootId is set — the root_create path is used, and streaming-card.ts explicitly notes that root_id may be silently ignored for card-id format references. The PR's new comment slightly overstates root_id reliability; a small documentation correction is suggested.

Confidence Score: 4/5

• This PR is safe to merge; the functional change is correct for the common reply-to-message scenario, with only a minor documentation inconsistency.
• The guard removal is minimal and well-scoped. The reply send-mode (triggered when replyToMessageId is present) reliably threads streaming cards in Feishu topics. The one-point deduction is for the inconsistency between the PR's new comment and the existing caveat in streaming-card.ts regarding root_id reliability in root_create mode — a non-critical documentation issue rather than a runtime risk.
• No files require special attention beyond the minor comment update suggested in reply-dispatcher.ts.

This is a comment left during a code review.
Path: extensions/feishu/src/reply-dispatcher.ts
Line: 139-141

Comment:
**New comment contradicts existing `streaming-card.ts` caveat**

The updated comment states _"Card streaming with rootId should route to topics correctly"_, but `streaming-card.ts` lines 221–224 contain an explicit, opposing note:

```
// Prefer message.reply when we have a reply target — reply_in_thread
// reliably routes streaming cards into Feishu topics, whereas
// message.create with root_id may silently ignore root_id for card
// references (card_id format).
```

The `root_create` send-mode (used when `rootId` is set but `replyToMessageId` is absent) may **silently drop the `root_id`**, meaning the streaming card won't be threaded under the correct topic in that scenario. The change is safe for the common case where `replyToMessageId` is present (which selects the `reply` send-mode with `reply_in_thread: true`), but the justification comment overstates the reliability of `root_id` routing.

Consider updating the comment to reflect the nuance:

```suggestion
  // reply_in_thread reliably routes cards into topics; root_create path may silently
  // drop root_id for card references — but replyToMessageId is typically always set
  // in thread contexts, making this safe in practice.
  const streamingEnabled =
    account.config?.streaming !== false && renderMode !== "raw";
```

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: 329bc5d}

Closing as superseded by #71542. The merged fix enables Feishu streaming cards for topic/thread replies and keeps the reply metadata (replyToMessageId, replyInThread, and rootId) covered by dispatcher tests.

Thanks for pushing the thread-mode path. If topic routing still misses affinity in a live Feishu room, reopen with the message/thread ids and we can narrow it to the send-mode layer.