Will Emmanuel 031829da6a Carry per-input extension data to user message completion callbacks (#59455) ...

## What changed

Add `user_input_extension_data` to `TurnInputRequest` and carry it with each queued user input through completion, including inputs that steer an active turn. Expose the data to lifecycle contributors through `on_item_completed_with_metadata`, whose default implementation forwards to `on_item_completed` for compatibility. Keep this data out of model input and preserve the existing serialized input shape when no extension data is present.

## Testing

Add serialization round-trip coverage and extend the concurrent submission test to verify that inputs sharing a client ID retain their own metadata, report completion in the accepting turn, and omit extension data from model requests.

GitOrigin-RevId: f880cf812994a030cb1be9418280ba69e2885808

2026-11-04 17:13:00 +00:00

..

examples

Require content kinds for extension prompt fragments (#40177)

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

src

Carry per-input extension data to user message completion callbacks (#59455)

2026-11-04 17:13:00 +00:00

tests

Use serving assessments for adaptive Guardian review (#58075)

2026-10-29 12:54:39 +00:00

BUILD.bazel

extension: add initial typed extension API (#21736)

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

Cargo.toml

Back off failed cloud skill and plugin catalog refreshes (#55968)

2026-10-21 19:22:57 +00:00

notes.md

Normalize formatting in docs, web assets, and sample scripts (#52256)

2026-10-08 20:11:43 +00:00