docs(ai): correct structured-output streaming guidance

Author: kolaworld

docs/structured-outputs/streaming.md

@@ -2,7 +2,7 @@
 title: Streaming Structured Output UIs
 id: structured-outputs-streaming
 order: 3
-description: "Build a UI that fills in field by field as the model streams structured JSON. chat({ outputSchema, stream: true }) on the server, useChat({ outputSchema }) on the client — progressive partial state plus a validated terminal object."
+description: "Build a UI that fills in field by field as the model streams structured JSON. chat({ outputSchema, stream: true }) on the server, useChat({ outputSchema }) on the client — progressive partial state plus a typed terminal object."
 keywords:
   - tanstack ai
   - structured outputs
@@ -16,7 +16,7 @@ keywords:
 
 You have an existing chat-style endpoint and you want the structured response to populate a UI _while_ the model is generating — a form filling in field by field, a card whose ingredients list grows as JSON streams in, a typewriter preview of a JSON-typed report. Blocking on `await chat({ outputSchema })` would leave the UI dark until the whole object is ready; this guide is the alternative.
 
-By the end you'll have a server endpoint streaming structured JSON as Server-Sent Events, and a client that reads a typed `partial` (progressive object) and `final` (validated terminal object) from `useChat`.
+By the end you'll have a server endpoint streaming structured JSON as Server-Sent Events, and a client that reads a typed `partial` (progressive object) and `final` (completed terminal object) from `useChat`.
 
 > **Note:** This is the streaming counterpart of [One-Shot Extraction](./one-shot). If you don't need progressive UI updates, the one-shot path is simpler. If you want users to iterate on the object across multiple turns and keep history, see [Multi-Turn Chat](./multi-turn).
 
@@ -48,11 +48,11 @@ export async function POST(request: Request) {
 }
 ```
 
-That's the entire server side. `chat({ outputSchema, stream: true })` returns a `StructuredOutputStream<InferSchemaType<typeof PersonSchema>>` — an `AsyncIterable` of standard streaming events plus a terminal `structured-output.complete` event carrying the validated object. `toServerSentEventsResponse` knows what to do with it.
+That's the entire server side. `chat({ outputSchema, stream: true })` returns a `StructuredOutputStream<InferSchemaType<typeof PersonSchema>>` — an `AsyncIterable` of standard streaming events plus a terminal `structured-output.complete` event carrying the completed object. `toServerSentEventsResponse` knows what to do with it.
 
 ## Client with `useChat`
 
-Pass the same schema to `useChat`. The hook gives you a progressively-parsed `partial` and a validated `final`:
+Pass the same schema to `useChat`. The hook gives you a progressively-parsed `partial` and a typed `final`:
 
 ```tsx
 import { useChat, fetchServerSentEvents } from "@tanstack/ai-react";
@@ -82,7 +82,7 @@ function PersonExtractor() {
       <p>Name: {partial.name ?? "…"}</p>
       <p>Age: {partial.age ?? "…"}</p>
       <p>Email: {partial.email ?? "…"}</p>
-      {final && <pre>Validated: {JSON.stringify(final, null, 2)}</pre>}
+      {final && <pre>Completed: {JSON.stringify(final, null, 2)}</pre>}
     </form>
   );
 }
@@ -91,8 +91,8 @@ function PersonExtractor() {
 What the hook does for you:
 
 - **`partial`** is `DeepPartial<z.infer<typeof PersonSchema>>` — every property optional, every nested array element optional. Updated from `TEXT_MESSAGE_CONTENT` deltas via the runtime's partial-JSON parser. The hook derives it from the latest assistant message's `structured-output` part (see [Multi-Turn Chat](./multi-turn) for why that distinction matters), so it reads `{}` between `sendMessage()` and the first chunk without any extra reset state.
-- **`final`** is `z.infer<typeof PersonSchema> | null` — the validated terminal payload from the `structured-output.complete` event. `null` until the run completes successfully.
-- **`outputSchema`** is used purely for client-side TypeScript inference. Validation still runs on the server against the schema you pass to `chat({ outputSchema })` on the server route — the client doesn't re-validate.
+- **`final`** is `z.infer<typeof PersonSchema> | null` — the completed terminal payload from the `structured-output.complete` event. `null` until the run completes successfully.
+- **`outputSchema`** is used purely for client-side TypeScript inference. The streaming path does not run Standard Schema validation; validate the completed object in the consumer when required.
 - The same shape works for **non-streaming adapters too**. If an adapter (Anthropic, Gemini, Ollama) returns a single `structured-output.complete` event with no incremental deltas, `partial` stays `{}` and `final` populates when the event arrives. Same consumer code.
 
 `outputSchema` is optional: omit it and `useChat` returns its standard shape without `partial` / `final`.
@@ -144,7 +144,7 @@ return (
   type: "CUSTOM",
   name: "structured-output.complete",
   value: {
-    object: T;          // validated, parsed, typed
+    object: T;          // completed, parsed, typed
     raw: string;        // full accumulated JSON text
     reasoning?: string; // present only for thinking/reasoning models
   },
@@ -164,6 +164,8 @@ Streaming structured output works with **every adapter**, but only some support
 | `@tanstack/ai-openrouter` | Native single-request stream (`response_format: json_schema`) |
 | `@tanstack/ai-grok` | Native single-request stream (Chat Completions, `response_format: json_schema`) |
 | `@tanstack/ai-groq` | Native single-request stream (Chat Completions, `response_format: json_schema`) |
+| `@tanstack/ai-bedrock` | Native stream through Converse or an OpenAI-compatible API |
+| `@tanstack/ai-byteplus` | Native single-request stream on supported models; unsupported models emit `RUN_ERROR` |
 | Other adapters (anthropic, gemini, ollama, …) | Fallback: runs non-streaming `structuredOutput` and emits the final object as one `structured-output.complete` event |
 
 The fallback path keeps the consumer code identical across providers — you always read the final object off `structured-output.complete` — but you won't see incremental deltas unless the adapter implements `structuredOutputStream` natively.
@@ -192,7 +194,7 @@ const stream = chat({
 
 for await (const chunk of stream) {
   if (chunk.type === "CUSTOM" && chunk.name === "structured-output.complete") {
-    // Validated and typed against PersonSchema.
+    // Typed against PersonSchema. Validate here when required.
     console.log(chunk.value.object.name);
     console.log(chunk.value.object.age);
   }

packages/ai/skills/ai-core/structured-outputs/SKILL.md

@@ -189,6 +189,8 @@ The terminal event is a `CUSTOM` chunk: `{ type: 'CUSTOM', name: 'structured-out
 | `@tanstack/ai-grok` (Grok 4 family only)                        | **Native combined mode (#605)** — `response_format: json_schema` + `tools`. Grok 2 / 3 fall back                                                      |
 | `@tanstack/ai-openrouter`                                       | Native single-request stream (legacy `structuredOutputStream` path; per-call combined-mode lookup is a follow-up)                                     |
 | `@tanstack/ai-groq`                                             | Legacy `structuredOutputStream` only (no tools — Groq's API rejects schema + tools + stream)                                                          |
+| `@tanstack/ai-bedrock`                                          | Separate native `structuredOutputStream` finalization through Converse or an OpenAI-compatible API                                                     |
+| `@tanstack/ai-byteplus`                                         | Native combined mode on supported models; unsupported models emit `RUN_ERROR`                                                                        |
 | All other adapters (ollama, older Claude, Gemini 2.x, Grok 2/3) | Fallback: runs non-streaming `structuredOutput`, emits one `structured-output.complete` event                                                         |
 
 **Native combined mode vs fallback** is signaled by the adapter's