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

Comment:
**`close()` can silently discard in-flight pending text**

When `flushUpdate` has been called (either directly or by the timer firing) but its queued task hasn't yet executed, `close()` can lose that text. Here's the exact race:

1. `flushUpdate("X")` runs its synchronous setup — `this.pendingText = null`, `this.lastUpdateTime = now`, a task is chained on `this.queue`.
2. `close()` is called: sets `this.closed = true`, cancels the already-null `pendingTimer`, then does `await this.queue`.
3. The chained task checks `if (!this.state || this.closed) return` → **exits early without updating `state.currentText`**.
4. Back in `close()`: `this.pendingText` is already `null` (cleared in step 1's sync phase), and `this.state.currentText` still doesn't contain "X".
5. `pendingMerged = mergeStreamingText(state.currentText, undefined)` = stale `state.currentText` — "X" is gone.

This is harmless today because `closeStreaming()` in `reply-dispatcher.ts` always supplies a complete `finalText`, which acts as the authoritative override. However the public `close()` signature allows callers to omit `finalText`, at which point stale/incomplete content is silently shown.

To make this robust, you could await any in-flight flush before marking `closed`, or document the requirement that `finalText` must always be supplied when there could be in-flight updates:

```typescript
// Option A: flush before closing
async close(finalText?: string, options?: { note?: string }): Promise<void> {
  if (!this.state || this.closed) {
    return;
  }
  // Drain any pending flush before marking closed, so queue tasks see closed=false.
  await this.queue;
  this.closed = true;
  if (this.pendingTimer) {
    clearTimeout(this.pendingTimer);
    this.pendingTimer = null;
  }
  // ... rest of close
```

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: 352

Comment:
**`flushUpdate` declared `async` but never awaits**

`flushUpdate` is marked `async` but its body only does synchronous work (state mutations + chaining onto `this.queue`). It never `await`s anything directly. The `async` keyword makes the function return a `Promise<void>` that resolves immediately, which is then discarded via `void` at every call site. This could mislead readers into thinking there is asynchronous work happening inside the function body itself.

```suggestion
  private flushUpdate(text: string): void {
```

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