refactor(cookbooks): answer with the chat library

[vishxrad]

Stacked on #1258. The cookbooks' component libraries were built on the wrong base, so this switches all three to openuiChatLibrary.

Summary

• Chat library instead of an openuiLibrary subset. Each cookbook built its library from string lookups into openuiLibrary (["Stack", "Table", …].map((name) => openuiLibrary.components[name])), with a Stack root and FollowUpBlock/FollowUpItem borrowed from the chat library. The chat library is the one made for Agent Interface answers, and it already has every component the cookbooks picked.
  • Document comparison and conversational analytics export it unchanged: export { openuiChatLibrary as library } from "@openuidev/react-ui/genui-lib".
  • Booking assistant keeps its DatePicker override on top of it: Object.values({ ...openuiChatLibrary.components, DatePicker }), with the chat library's root and component groups.
• No custom Sources component. The chat Card takes sources ({ title, sourceName, url }[]) as its second argument and renders the same CardSourceProvider + Sources strip that sources.tsx wrapped, so sources.tsx is deleted.
• Prompts. Examples use root = Card([...]) (document comparison: Card([...], sources)), and the rules that named Stack or the Sources component now name the Card.
• Docs. Step 3 of each cookbook, the prompt bullets, the README file tables, and the References lists describe the chat library. Document comparison's step 3 shows the OpenUI Lang Card([...], sources) example in place of the sources.tsx sample. One line of that example is about 180 characters and scrolls sideways, since OpenUI Lang statements can't wrap.

Why

• String lookups aren't type-checked. components is a Record<string, …>, so a typo compiles and then throws Cannot read properties of undefined (reading 'props') when the module loads.
• Stack's children is any[]. The spec told the model nothing about what an answer can contain.
• Subsetting the chat library doesn't work cleanly. A subset still advertises all 38 child types in Card's signature, including components outside the subset. Keeping the chat library's component groups makes generateSystemPrompt({ cloud: true }) throw, because the groups name components outside the subset. So using the whole library is the clean option.

What changes in behavior

• Answers are one chat Card, not a bare Stack.
• Sources appear below the follow-ups. The Card always renders its sources strip last.
• Repeated pages are handled by the prompt. onePerPage merged two quotes from the same page because the strip keys its cards by URL. A prompt rule now asks for one item per page.
• Larger prompt. The library grows from 14 to 84 components. Gateway builds the system prompt from the spec that generateSystemPrompt({ cloud: true, library }) sends, and for a one-line question with no cookbook rules it reports 2,059 prompt tokens with the old document-comparison library and 7,249 with the chat library (usage.prompt_tokens). The spec sent with each request grows from about 6 KB to 55 KB. runTools() sends the system prompt with every completion, so a question that searches once pays the difference at least twice. The cookbook rules still name the components each answer uses and rule out forms and queries.

Test plan

• npm ci and npm run verify (spec generation and next build with type checking) in all three cookbooks at this PR's head, rebased on main
• Every prompt example parses against its library with no errors and a Card root, and generateSystemPrompt({ cloud: true, library }) accepts all three specs
• Document comparison, in the browser: “Compare revenue and growth” renders a Card with the table, two charts, the fiscal-year callout, follow-ups, and a sources strip with one card per page (NVIDIA p. 37, AMD p. 50, Intel p. 76). No console errors.
• Analytics, in the browser: the Norris/Verstappen starter renders the gap line chart, a fastest-lap table, and follow-ups. No console errors.
• Booking assistant, in the browser: the Goa starter renders the trip form with both dates prefilled (Fri Oct 2 to Sun Oct 4), so the DatePicker override still works. Submitting it renders the stay cards with photos. One transient src="" warning appeared while an Image streamed; both libraries use the same Image component, so it isn't from this change.
• Docs site, locally: the three cookbook pages render with no console or server errors, and only the OpenUI Lang line above scrolls sideways

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
openui-docs	Ready	Preview	Sep 30, 2026 2:07pm UTC

[bobo617]

Loku UF koquitelofqwuincyrt

[bobo617]

Asгнней