Preserve pending realtime speech when a call ends (#62299)

## Why

A realtime call can end with completed speech that has yet to reach a
Codex turn. The next turn needs that context even if the call's transport
has already disconnected.

## What changed

- For V3 calls with realtime frame history enabled, save pending speech
  as context for the next turn. Restore it on thread reload and exclude
  it from the turn count used by rollback.
- Drain already received transcript events and settle pending handoffs
  before saving the call's closing marker. Report recovery required if
  shutdown cannot confirm that history was saved.
- Keep transport detach separate from ending a call. Reattaching restores
  saved pending speech, and an open call can be ended from persisted
  history after a reload. Use the call ID for TUI attachments so successive
  calls on one thread have distinct history.

## Testing

Add coverage for queued speech at hangup, reconnect and stop after
reload, retries after an uncertain write, and rollback across saved
session-end context.

GitOrigin-RevId: 657491f1d7e446a1a48e22189758810c8bdd82cb
This commit is contained in:
Zahan Malkani
2026-11-18 15:24:29 +00:00
committed by copyberry
parent bd3eaf7829
commit bd00a8a42e
39 changed files with 3687 additions and 256 deletions
@@ -0,0 +1,35 @@
---
source: core/tests/suite/scenarios.rs
assertion_line: 4337
expression: "context_snapshot::format_request_history_snapshot(\"A realtime handoff consumes the exact sealed transcript referenced by its durable acceptance.\",\n&requests, &ContextSnapshotOptions::default().rewrite_known_segments(),)"
---
Scenario: A realtime handoff consumes the exact sealed transcript referenced by its durable acceptance.
## Window 1
-- request 1 (turn) --
00:message/developer:
<MODEL_INSTRUCTIONS>
01:message/developer[3]:
[01] <realtime_conversation>
Realtime conversation started.
You are operating as a backend executor behind an intermediary. The user does not talk to you directly. ...ediary and may be summarized before the user sees it. [hash=5114d16b52865327]
When invoked, you receive the latest conversation transcript and any relevant mode or metadata. The inte...void verbose responses that add user-visible latency. [hash=e229c6c9120dff28]
When user text is routed from realtime, treat it as a transcript. It may be unpunctuated or contain recognition errors.
- Keep responses concise and action-oriented. Your updates should help the intermediary respond to the user.
</realtime_conversation>
[02] <PERMISSIONS_INSTRUCTIONS>
[03] <tools>
Deferred tool namespaces:
- multi_agent_v1: Tools for spawning and managing sub-agents.
</tools>
02:message/user:
<ENVIRONMENT_CONTEXT>
03:message/user:
<realtime_delegation>
<input>text from realtime</input>
<transcript_delta>user: text from realtime</transcript_delta>
</realtime_delegation>