Leonardo Di Donato 9b738582b1 Expose originating tool call metadata in command environments (#52119) ...

## Why

Command processes need thread and tool call labels for correlation, without stale values from inherited environments or cached shell snapshots.

## What changed

- Export the originating `exec_command` call ID as `CODEX_TOOL_CALL_ID`; later `write_stdin` calls leave it unchanged.
- Apply executor metadata as `CODEX_THREAD_ID` and `CODEX_TOOL_CALL_ID` after environment policies, overlays, and snapshot replay. Clear omitted fields when metadata is present; without metadata, preserve thread context and remove the call ID.
- Exclude both IDs from newly captured snapshots and omit the call ID from capture and validation helpers.
- Preserve empty call IDs, omit NUL-containing IDs, and handle case-insensitive environment names on Windows. Document that these labels support correlation, not authorization.

## Testing

Add regression coverage for metadata precedence, missing and invalid IDs, snapshot capture and replay, local and remote execution with pipes and TTYs, sandboxed remote execution, and preservation of the originating call ID across later input.

GitOrigin-RevId: 1027212b5d495d8e7cfac0f498c3134e060aa897

2026-10-08 13:45:19 +00:00

..

src

Expose originating tool call metadata in command environments (#52119)

2026-10-08 13:45:19 +00:00

BUILD.bazel

protocol: separate app and exec RPC ownership (#29714)

2026-06-23 22:37:31 +00:00

Cargo.toml

Carry shell invocation metadata and report executor PATH directories (#49360)

2026-09-29 20:40:21 +00:00