Eddie Chen a037e65ead Preserve client metadata through queued submissions (#59826) ...

## Why

Queued inputs previously stored and dispatched without the submitting client's Responses API metadata, losing attribution such as `client_type` when the queued turn started.

## What changed

- Accept `responsesapiClientMetadata` when adding or updating queued submissions and expose it on returned queue items.
- Persist metadata with the input and forward it when starting a selected item or dispatching an idle queue, including after restoration.
- Preserve existing metadata when an update omits it or supplies an empty map; replace it when a non-empty map is supplied.
- Keep stored inputs readable by older queue workers and update generated protocol artifacts.

## Testing

Extend queue service and app-server tests to cover metadata round trips, preservation and replacement on edits, compatibility with older readers, and forwarding during selected, idle, and restored dispatch.

GitOrigin-RevId: 508043b1d3d0298c9af2be8e05b6999de46596a1

2026-11-06 05:10:44 +00:00

..

src

Preserve client metadata through queued submissions (#59826)

2026-11-06 05:10:44 +00:00

tests

Preserve client metadata through queued submissions (#59826)

2026-11-06 05:10:44 +00:00

BUILD.bazel

Add durable user-message queue dispatch (#37204)

2026-08-06 03:11:42 +00:00

Cargo.toml

Add durable user-message queue dispatch (#37204)

2026-08-06 03:11:42 +00:00