Abhinav 8ff4aa8ee4 Use captured step model settings for extension context (#44202) ...

## Why

Model switches within a turn can leave extension context using stale model metadata. Skill catalogs, context windows, and metric attribution need to match the model captured for each sampling step.

## What changed

- Pass captured model metadata and step-specific telemetry to world-state contributors.
- Use that metadata for skill catalog budgets and usage instructions, preserving configured budget overrides.
- Supply the captured model's usable context window to turn-context contributors, including when rebuilding context.

## Testing

Add regression coverage for model switches during skill discovery, catalog budgets and metric attribution, and extension context windows after `new_context` and retained-step context rebuilds.

GitOrigin-RevId: c51b40b739a380b9767a54ea8c8ee6de45bf01c8

2026-09-09 16:48:49 +00:00

..

examples

Require content kinds for extension prompt fragments (#40177)

2026-08-23 03:12:58 +00:00

src

Use captured step model settings for extension context (#44202)

2026-09-09 16:48:49 +00:00

tests

Discount an approval's own code-mode wrapper from Guardian score lag (#43527)

2026-09-07 17:35:23 +00:00

BUILD.bazel

extension: add initial typed extension API (#21736)

2026-05-11 11:06:24 +02:00

Cargo.toml

Preserve verified answers across history compaction (#42293)

2026-09-02 15:07:11 +00:00

notes.md

extension: add initial typed extension API (#21736)

2026-05-11 11:06:24 +02:00