Ankush Gupta 88235f881d Retain confirmed Code Mode messages for Guardian reviews (#48725) ...

## Why

Guardian needs the assistant's delivered question to interpret a user's reply. Messages sent through nested Code Mode tools must remain available as review context, and approvals based on earlier context must become stale when a new delivery is confirmed. Assistant messages do not themselves grant authorization.

## What changed

- Capture successful hosted User Messaging sends after input rewriting and before result callbacks or post-tool hooks.
- Retain bounded delivery text in acceptance order, persist it through cancellation and shutdown, and preserve it across compaction and resume with an older-client-compatible rollout encoding.
- Track assistant review context separately from user authorization, invalidating pending and cached approvals for both local and worker reviews when that context changes.
- Associate retained deliveries with the correct instruction or communication boundary during rollback.

## Testing

Add coverage for nested messaging review context, fast replies and communication ordering, shutdown persistence, stale local and worker approvals, rollout compatibility, and rollback retention.

GitOrigin-RevId: 1bc1ec9e8947560b99f4b39a42ddb9f2099f519b

2026-09-27 15:03:38 +00:00

..

examples

Require content kinds for extension prompt fragments (#40177)

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

src

Retain confirmed Code Mode messages for Guardian reviews (#48725)

2026-09-27 15:03:38 +00:00

tests

Bind Guardian async scores to target environment permissions (#47830)

2026-09-24 12:34:04 +00:00

BUILD.bazel

extension: add initial typed extension API (#21736)

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

Cargo.toml

Bind Guardian async scores to target environment permissions (#47830)

2026-09-24 12:34:04 +00:00

notes.md

extension: add initial typed extension API (#21736)

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