Abhinav 205f3671e1 Use captured step settings for tool planning and execution (#44242) ...

## Why

After a model change within a turn, tools could still use the turn's original model capabilities, output limits, and telemetry attribution.

## What changed

- Build each step's tool plan from its captured model settings.
- Use those settings for image support and detail, command and MCP output truncation, extension metadata, and tool telemetry.
- Preserve the issuing step's model for delayed command completion events while allowing later `write_stdin` calls to use their own step's output limits.

## Testing

Add regression coverage for model changes within a turn, including tool replanning, Code Mode execution, image handling, MCP tool and resource output limits, extension settings, and delayed command completion.

GitOrigin-RevId: ef991598e89a846889baf770a0c9e12e56886d5d

2026-09-09 17:45:37 +00:00

..

account.rs

Honor explicit account selectors for Apps tool calls (#42054)

2026-09-01 13:29:18 +00:00

telemetry_tests.rs

…

telemetry.rs

Use captured step settings for tool planning and execution (#44242)

2026-09-09 17:45:37 +00:00