Eric Traut dbf478850f Make TUI async question replies compatible with desktop (#46486) ...

## Why

Async questions answered on another client should disappear from the TUI without losing drafts for other questions, even when questions have identical titles.

## What changed

- Send answers using the desktop reply envelope with stable per-question IDs, and resolve matching questions from committed messages and replayed history.
- Render replies as readable question-and-answer text in transcripts, queue previews, and input history.
- Preserve separate reply envelopes and message order when retrying rejected or interrupted input.
- Account for JSON escaping in input limits and fall back to plain text for oversized question IDs.

## Testing

Add regression coverage for cross-client dismissal, draft preservation, replay ordering, reply parsing, IDE context, distinct replies with identical text, and retry ordering. Update the async question scenario to use the reply envelope.

GitOrigin-RevId: 9b9e4b1e140508590401622d96cfc16fc192eb7c

2026-09-18 22:40:37 +00:00

..

common

Add opt-in overhead timing to code-mode responses (#46288)

2026-09-17 19:34:45 +00:00

remote_env_windows

Apply remote platform semantics to exec safety checks (#42113)

2026-09-01 18:24:56 +00:00

suite

Make TUI async question replies compatible with desktop (#46486)

2026-09-18 22:40:37 +00:00

all.rs

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

responses_headers.rs

Handle unknown error classifications and configure gateway OAuth (#46482)

2026-09-18 22:29:16 +00:00