Rsc Streaming Ui

Operator's RSC streamUI tool `getWeather.generate` returns a plain object `{ temp: 72 }`. The page never renders the weather card.

In streamUI, each tool's `generate` (async generator or function) must yield and/or return a React node, not raw data. Wrap data in a server component (`<WeatherCard data={...} />`). The streamed result is then a React tree the client can render via useUIState.

Operator uses createAI({ actions: { submitMessage } }) and also exposes submitMessage as a `use server` action elsewhere, leading to duplicate request handlers.

Actions registered in createAI become available via useActions() on the client and execute on the server in the AI context. Choose one registration site — duplicating leads to inconsistent AIState updates and double-billed model calls.

Operator mutates `aiState.get()` directly via array.push to add a message; useUIState consumers don't re-render.

Treat AIState as immutable. Call `aiState.update(prev => [...prev, msg])` (or `.done(...)` at the end of the action) so consumers re-render. Pair AIState (server-persisted message log) with UIState (client-rendered tree) — do not collapse them into a single store.