docs: align compatibility tables with what CI actually verifies

[scrollDynasty]

The Expo SDK 54 row claimed coverage the example app never had - it is bare React Native, so Expo is not exercised in CI at all. Replace intent with the jobs that actually run, document the Expo prebuild path explicitly, advertise the zero-dependency tree, and flag that iOS via npm needs 0.3.1+ (0.2.4 and 0.3.0 shipped without the podspec).

Summary

What does this PR change and why?

Type of change

• Bug fix
• New feature
• Documentation
• Refactor / chore
• Native change (Android Kotlin / iOS Swift)
• Tests only

Checklist

• I read CONTRIBUTING.md
• I tested on Android and/or iOS (platforms I changed)
• I ran yarn lint, yarn build, yarn typecheck, and yarn test from the repo root
• I added or updated tests in the correct folder (see CONTRIBUTING.md — tests)
• I updated docs if the public API changed
• I committed yarn.lock if package.json dependencies changed
• I did not add unnecessary dependencies
• I removed debug logs from library code
• I did not hardcode demo values in src/, android/, or ios/ (example app only)
• For native changes: I considered memory leaks and scroll performance

CI

PRs to main run the full CI workflow automatically. New tests in standard locations are picked up without editing ci.yml.

Screenshots / recordings (UI changes)

If applicable, add before/after visuals.

Related issues

Fixes # (issue number)

[coderabbitai]

Warning

Review limit reached

@scrollDynasty, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8a43b9f4-f069-4129-b6d5-b325f55216b5

📥 Commits

Reviewing files that changed from the base of the PR and between 4cd7806 and 81b1f9b.

📒 Files selected for processing (1)

• README.md

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}