[Bug]: ANSI color sequence appears as literal text in Codex prompt on Windows

### Operating system

Windows

### Orca version

1.4.201

### Details

#### Summary

A fragment of an ANSI SGR color sequence is displayed as literal text on the Codex prompt row in Orca's built-in terminal on Windows.

The observed screen shows this fragment immediately after the prompt marker:

```text
;130;130;48;2;41;41;41m
```

The Codex status line below it remains readable. This is a transcription of the relevant portion of the screenshot; the image itself is not attached.

#### Environment

- Windows 11 Pro, version 10.0.26200 (build 26200).
- Installed Orca desktop application: 1.4.201, verified from its packaged package.json.
- Running persistent daemon executable is under daemon-host/1.4.200. This version difference is recorded for context; it has not been established as a cause.
- Installed Codex CLI on PATH reports codex-cli 0.154.0.
- The affected Codex TUI status line shows gpt-6-astra with xhigh reasoning effort.

#### Observed behavior and reproduction status

The artifact was observed during an existing Codex terminal session in Orca. The exact triggering action and a reliable sequence to reproduce it have not yet been established. It is not known whether attaching/restoring a session, switching tabs, or resizing is required.

Actual: the color-control suffix is visibly printed on the prompt row.

Expected: ANSI SGR sequences should be interpreted as text styling and should not appear as visible characters in the terminal.

#### Local evidence

During the initial read-only investigation, the affected terminal's output.log contained this complete sequence (ESC is shown below as a textual escape):

```text
\x1b[38;2;130;130;130;48;2;41;41;41m
```

At that inspection, all 1,475 occurrences of the screenshot's suffix in that log had the expected preceding bytes, forming the complete sequence above. The visible suffix therefore also exists as part of valid color output in the saved stream; it was not found with a truncated prefix in that scan.

This suggests a possible issue in terminal output delivery, replay, or rendering, but does not establish the failing component or rule out other causes. No fix or workaround has been verified, and no comparison with another terminal has been performed.

Only the relevant control sequence and environment information are included here. Full terminal logs, local user paths, session IDs, and conversation contents are omitted.

Start with the affected Windows Codex terminal session and inspect output.log, comparing the complete ANSI sequence with what is rendered on the prompt row. Trace terminal output delivery, replay, and rendering to identify where valid SGR bytes become visible text. Done means the sequence remains styling and no color-control characters appear in the prompt.

Written by the indexing model from the issue text.