#4231 docs(help): route stale React Native state to reads, not UI navigation

Summary

• help react-native gains a short Stale state section and a routing line. When a wrong or stale value may come from app state or storage (AsyncStorage, MMKV, a feature flag), the agent reads the value instead of navigating the UI to infer it: agent-device cdp runtime eval --expr '<expression>' --await for JS state, and the AsyncStorage location on an iOS simulator or Android.
• Reason: in an external benchmark (Claude Code + Sonnet, React Native runtime bugs), agent-device was the slowest and costliest setup only on a stale-AsyncStorage bug (median 95 s, $0.32, 20 device calls vs 76 s, $0.17 for a bare shell that read the storage files). The capability exists through cdp; the routing was missing.
• Scope expansion: the react-native topic moves verbatim to src/commands/schema/cli-help-react-native.ts, because the addition pushed cli-help.ts past the 1000-line lint limit. Same pattern as the gestures and foldable topics.
• 3 files changed. No linked issue.

Validation

• Tested SHA: a5052c55736413293824cd8df58f057259d22fb1
• pnpm check:affected --run --head a5052c55736413293824cd8df58f057259d22fb1: format, lint, typecheck, layering, fallow, build, vitest-related and unit passed (exactCommit=true).
• cli-help-topics.test.ts asserts the new eval command and the AsyncStorage path.
• The moved topic text was diffed against origin/main: identical except the added lines.
• Help-text change only, so no device run. Not measured: whether the new routing shortens a stale-storage run. Self-review was a cold diff read, with no independent reviewer.

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}