New tweaks

[heymelcheng]

No description provided.

[sentry]

Bug: TextDecoder is used on a streaming response without the { stream: true } option, which can corrupt multi-byte characters if they are split across data chunks.
_{Severity: MEDIUM}

Suggested Fix

When decoding chunks from a streaming response, pass the { stream: true } option to the decode method. This allows the decoder to buffer incomplete multi-byte sequences until the next chunk arrives. The fix is to change decoder.decode(value) to decoder.decode(value, { stream: true }).

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/components/desktop/apps/TranscriptAnalyzer.tsx#L103

Potential issue: The code initializes `TextDecoder` without the `{ stream: true }`
option when processing streaming API responses. When a multi-byte UTF-8 character, such
as an emoji or non-ASCII character, is split across two or more data chunks in the
stream, the decoder will fail to interpret it correctly. This results in silent data
corruption, displaying garbled characters to the user instead of the intended content.
This issue affects streaming logic in `TranscriptAnalyzer.tsx`,
`CompetitiveResearch.tsx`, and `Chat.tsx`.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: TextDecoder.decode(value) is used without the { stream: true } option, which can corrupt multibyte characters like emojis if they are split across streamed response chunks.
_{Severity: HIGH}

Suggested Fix

When decoding streamed data, call decoder.decode(value, { stream: true }) for all intermediate chunks. This ensures that incomplete multibyte characters at the end of a chunk are correctly buffered and handled with the subsequent chunk. The final chunk can be decoded without the stream option.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/components/desktop/apps/TranscriptAnalyzer.tsx#L110

Potential issue: The code uses `TextDecoder.decode(value)` to process streamed
Server-Sent Events (SSE) without the `{ stream: true }` option. When a multibyte UTF-8
character, such as an emoji or non-ASCII text, is split across network chunks, this will
cause it to be decoded incorrectly. The incomplete character sequence will be replaced
with a replacement character (), leading to corrupted text being displayed in the user
interface. This is a known issue with streaming data, as documented in a similar fix in
Next.js PR #35724.

_{Did we get this right? 👍 / 👎 to inform future reviews.}