teddywyly-oai a6fdb11eda Preserve metadata in native user verification requests (#46952) ...

## Why

Native `openai/userVerification` requests need to carry optional `_meta` to clients for extension-specific presentation.

## What changed

- Accept optional metadata objects with the same validation as MCP elicitation.
- Restore metadata from the MCP request context, excluding `progressToken`, and forward it through `mcpServer/elicitation/request`.
- Update protocol types, schemas, and documentation while retaining support for requests without metadata. Challenge bytes and acceptance proofs remain unchanged.

## Testing

Add coverage for metadata validation, transport context restoration, and protocol round trips. Extend MCP integration tests to check that verification metadata reaches the client.

GitOrigin-RevId: 5d04004244cf33effac675c19e543157c48d1504

2026-09-21 07:01:52 +00:00

..

src

Preserve metadata in native user verification requests (#46952)

2026-09-21 07:01:52 +00:00

tests

Preserve metadata in native user verification requests (#46952)

2026-09-21 07:01:52 +00:00

BUILD.bazel

[3/4] Add executor-backed RMCP HTTP client (#18583)

2026-04-22 17:38:04 -07:00

Cargo.toml

Close MCP stderr readers on client teardown (#43870)

2026-09-08 17:42:14 +00:00