test: add streaming or chunked runtime-path validation where integration behavior depends on it

[rlippmann]

Proposed enforcement point

runtime response-path validation

Domain

streaming and chunked integration behavior

Runtime or framework

LiteLLM Proxy / Open WebUI / other runtime-backed integrations as applicable

Why existing examples do not cover it

Current runtime coverage focuses mainly on request routing, startup/teardown, local-state handling, and non-streaming forwarded requests. The repository does not yet validate streaming or chunked response paths where runtime behavior might differ materially from the non-streaming path.

This gap should cover only integrations where streaming or chunked behavior is part of the meaningful runtime boundary. Likely checks include:

• whether the integration forwards streaming responses correctly
• whether chunked/streaming callbacks affect enforcement behavior
• whether response-shaping or local interception differs under streaming
• whether a given integration can be explicitly documented as not depending on streaming semantics

This should be tracked separately from the remaining Open WebUI loading/registration gap.

Where does this belong?

context-compiler-example-integrations