Abhinav 0182ff3480 Finalize model-specific tool plans in ToolRouter (#41195) ...

## Why

Planning tools for a candidate model must not change the selected model or its
Responses Lite tool inventory. Otherwise, preparing a fallback can overwrite
metadata before the current model's request is sent.

## What changed

- Build tool registries and visible specs from an explicit `ModelInfo`.
- Store the finalized tool mode, code-mode names, namespace inventory, and
  terminal and child-management capabilities on `ToolRouter`.
- Publish namespace inventory only after selecting the step's router, and use
  that router's mode when dispatching and recording tool calls.

## Testing

Added coverage for candidate-model isolation, fallback compaction metadata,
code-mode worker selection, normalized tool names, and router capabilities.

GitOrigin-RevId: 56df2de8f42c7e93a4c4dcd117720e40a0cca3db

2026-08-27 20:01:39 +00:00

..

common

Harden core test fixture startup assertions (#41194)

2026-08-27 19:58:09 +00:00

remote_env_windows

Standardize shell execution on unified exec (#39772)

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

suite

Finalize model-specific tool plans in ToolRouter (#41195)

2026-08-27 20:01:39 +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