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

Comment:
**`sendStructuredCardFeishu` removed from mock but still used in implementation**

`sendStructuredCardFeishu` has been removed from the `vi.mock("./send.js", ...)` factory, yet `reply-dispatcher.ts` (line 424) still calls it:

```ts
await sendStructuredCardFeishu({ cfg, to: chatId, text: chunk, ... });
```

Because the module mock now only exports `sendMessageFeishu` and `sendMarkdownCardFeishu`, `sendStructuredCardFeishu` will resolve to `undefined` in tests. Any test that hits a non-streaming card path — such as "passes replyInThread to sendMarkdownCardFeishu for card text" (`renderMode: "card", streaming: false`) and "disables streaming for thread replies and keeps reply metadata" (`threadReply: true`) — will throw `TypeError: sendStructuredCardFeishu is not a function`.

The test assertions expect `sendMarkdownCardFeishuMock` to have been called, but the production code hasn't been updated to call `sendMarkdownCardFeishu`. `reply-dispatcher.ts` needs to be updated alongside these test changes for them to pass.

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

---

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

Comment:
**Test assertions diverge from actual `streaming.start()` call arguments**

The test now asserts `streaming.start` is called with exactly `{ replyToMessageId, replyInThread, rootId }`, but `reply-dispatcher.ts` (lines 275–282) still passes `header` and `note` as well:

```ts
await streaming.start(chatId, resolveReceiveIdType(chatId), {
  replyToMessageId,
  replyInThread: effectiveReplyInThread,
  rootId,
  header: cardHeader,   // still present
  note: cardNote,       // still present (also removed from StreamingStartOptions)
});
```

`toHaveBeenCalledWith` uses deep equality, so these tests will fail because the actual third argument has two extra keys. The same mismatch applies to the "passes replyToMessageId and replyInThread to streaming.start()" test at line 691.

`reply-dispatcher.ts` must drop `header` and `note` from the `start()` call (matching the removed `StreamingCardOptions`) for these assertions to hold.

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

---

This is a comment left during a code review.
Path: extensions/feishu/src/streaming-card.ts
Line: 415-416

Comment:
**`this.state` not cleared after `close()` completes**

The previous code explicitly nulled `this.state` and `this.pendingText` at the end of `close()`:

```ts
// old
const finalState = this.state;
this.state = null;
this.pendingText = null;
this.log?.(`Closed streaming: cardId=${finalState.cardId}`);
```

The new code removed those assignments, so after `close()` returns the instance continues to hold `cardId`, `messageId`, `currentText`, and any remaining `pendingText` in memory indefinitely. `this.closed = true` correctly prevents any further API calls, but the heap references linger until the session object itself is GC'd. Consider adding `this.pendingText = null` (and optionally `this.state = null`) after the final log line so closed sessions release their data promptly.

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