pub async fn stream_parity(
handle: &PluginHandle,
body: Value,
want: &(dyn Fn(&str) -> bool + Sync),
timeout: Duration,
) -> CellExpand description
2026-09-26: The same request streamed and not streamed.
The blocking path builds its response separately (api/chat_blocking.rs),
so a server can stream correctly and assemble a blocking reply wrongly.
Both must answer correctly and agree on prompt_tokens: the request is
the same apart from stream, so a difference there means the two paths
built different prompts from it.