[oliverlaz]

Why

stream-chat-react v15 and Stream Chat React Native v10 (both on stream-chat v10) change how an app reads state, lays out channels and threads, and configures the client. The skills sent agents to the unversioned docs id, which is whichever major is "Latest", and the RN Chat blueprints (mandatory on every turn) are v9 code. In a baseline test on a v10 RN project, an agent detected 10.0.0-rc.5 but still wrote v9 code (ChannelList filters/sort, object sorts, <Channel thread threadList>) because the v9 docs were "the closest documented API".

What changes

Version routing, without naming a "current" major

• New skills/stream-react/chat-versions.md and skills/stream-react-native/references/CHAT-VERSIONS.md:
  • pin the installed major; the installed stream-chat must satisfy the SDK's own stream-chat range;
  • read only that major's docs (chat-sdk/<sdk>/v<major>, or the site's v<major>/llms.txt when the CLI doesn't list it), and stop if none exist;
  • find the AI migration guide for a pair through the SDK repo's ai-docs/ (GitHub API listing; the title names the pair; release branch for unreleased majors);
  • read the guide's old -> new reference and its list of changes that still compile before writing Chat code.
• SKILL.md, RULES.md, migrate.md, DOCS.md, the blueprints and the Sendbird files route through these files instead of naming v14/v15 or v9/v10. Files compiled against a specific version (Sendbird mapping, design cheat-sheet, RN blueprints) say so in their first lines.

AI guidance

• The AI components ship in the SDKs: stream-chat-react/ai-components, stream-chat-react-native/ai-components, stream-chat-expo/ai-components. The standalone @stream-io/chat-react-ai and @stream-io/chat-react-native-ai are marked deprecated, with a pointer to the docs' migration sections; guidance that only applied to them is removed.
• React: new "Generative UI: A2UI and OpenUI" section (renderer entry points, pinned peer versions, telling the model what the app can show, the backend moving UI into the message field, one host per conversation, untrusted UI, errors, theming).
• RN: generative UI is docs-gated; RN has no renderer today, so the skill says so instead of porting web code.

Testing

Subagent runs (Sonnet) on small v15 React / v10 RN fixtures, before and after (no install, no type-check):

Scenario	Before	After
RN v10: channel list, thread screen, offline	v9 API throughout	v10 manifest and quick start, ChannelPaginator, <Thread thread> beside Channel, enableOfflineSupport on Chat
React v15: archived list, header, send handler	no v15 docs found, custom field at the top level	v15 manifest only, slot layout, handler on client.config, custom.client_tag
RN v10: AI screen with dictation, A2UI	-	stream-chat-expo/ai-components, dictation via the Expo config plugin, StreamTheme; reports A2UI as unavailable on RN
React v15: AI view with A2UI / OpenUI	-	ai-components + a2ui / openui entry points, pinned peers, one host, backend contract, sendMessage({ message })

The React custom-field and sendMessage({ message }) fixes depend on a companion change to the v15 AI migration guide in GetStream/stream-chat-react: GetStream/stream-chat-react#3415

claude plugin validate . --profile directory --strict passes. All added text is ASCII; local links resolve.

Known gaps

• Agents follow "read the guide's old -> new reference first" loosely when writing new code on a project already on the new major; the docs carried them in the tests.
• The docs' upgrade pages don't link the AI migration guides; a link there would make the GitHub API discovery step unnecessary.