ningyi-oai d5caceccb1 Track Code Mode tool call metadata completeness (#41058) ...

## Why

Executed-tool metadata for a Code Mode cell can span its `exec` and `wait`
outputs. Consumers need to know whether that metadata contains the cell's full
tool call inventory or only a partial record.

## What changed

- Associate recorded tool calls with the originating Code Mode cell across
  `exec` and `wait` outputs.
- Add a host-owned `tool_calls_complete` marker when recording finishes without
  dropped or truncated calls. The marker describes inventory completeness, not
  tool success.
- Preserve the cell metadata through replay and pruning, and clear the
  completeness marker when prompt budgeting makes the record incomplete.

## Testing

Add coverage for multi-wait cells, retries, interruptions, recording limits,
argument truncation, prompt budgeting, and rejection of input-forged metadata.

GitOrigin-RevId: 377014edec06aab42aadab78b8b5dccc0a1c83ba

2026-08-27 06:03:29 +00:00

..

common

Support standalone function outputs in turn routing (#40991)

2026-08-26 22:48:37 +00:00

remote_env_windows

Standardize shell execution on unified exec (#39772)

2026-08-20 18:29:35 +00:00

suite

Track Code Mode tool call metadata completeness (#41058)

2026-08-27 06:03:29 +00:00

all.rs

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

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

responses_headers.rs

Sanitize credentials from Git remote metadata (#40713)

2026-08-25 21:34:05 +00:00