diff --git a/README.md b/README.md
index 750b344..7e78e10 100644
--- a/README.md
+++ b/README.md
@@ -251,6 +251,24 @@ It also has a weekly job that checks out Paseo main, sets `PASEO_SOURCE` and run
Verified on macOS with Paseo 0.12.0 (desktop app and CLI). CI runs on Linux without Paseo, where daemon tests skip and `ppd check` runs as an approximation.
+### React Native, React and Dependabot
+
+Paseo supplies React Native, React, the plugin SDK, TanStack Query and Zod at runtime. A plugin's development dependencies provide local types and tooling; upgrading them does not upgrade the app's renderer. Keep their versions aligned with the oldest Paseo app you support. `requirements.paseo` declares supported app and daemon versions; there is no separate React Native requirement in the plugin manifest. An SDK peer range is an installation constraint, not a tested runtime compatibility matrix.
+
+Do not automatically merge React Native minor-series upgrades. React Native can introduce breaking changes in `0.x` minor releases. Review React, React Native and SDK updates together, run an ordinary dependency install without bypassing peers, then typecheck, test, compile against the supported host and exercise the changed UI. Passing `ppd check` alone does not establish matching types or renderer compatibility. Use the oldest supported host's Hermes binaries through `HERMESC` and `HERMES` when validating that host; a newer development dependency's engine is not equivalent.
+
+Exact pins do not stop Dependabot from proposing manifest changes. To keep automated version PRs within the current React Native series, add this under the relevant npm entry in `dependabot.yml`:
+
+```yaml
+ignore:
+ - dependency-name: react-native
+ update-types:
+ - version-update:semver-minor
+ - version-update:semver-major
+```
+
+Review a series upgrade explicitly when the supported host and its React/SDK constraints permit it. This snippet does not configure auto-merge. See the [compatibility guide](https://paseo-plugin-devkit.pages.dev/docs/compatibility#host-dependencies) for the dependency experiment and evidence limits.
+
`ppd` relies on parts of Paseo that are not a public API. When one of them moves in a new Paseo release, `ppd` says what it expected instead of blaming your plugin:
| Relies on | Used by | When it changes |
diff --git a/docs-site/src/routes/(docs)/docs/compatibility/+page.svx b/docs-site/src/routes/(docs)/docs/compatibility/+page.svx
index f5e4a49..de86150 100644
--- a/docs-site/src/routes/(docs)/docs/compatibility/+page.svx
+++ b/docs-site/src/routes/(docs)/docs/compatibility/+page.svx
@@ -29,6 +29,61 @@ Paseo that are not a public API, and says so when one of them moves instead of b
macOS and Linux. On Linux (CI), there is no Paseo app: daemon tests skip and `ppd check` is an approximation.
Windows is not supported.
+
React Native, React and dependency updates
+
+Paseo supplies React Native, React, the plugin SDK, TanStack Query and Zod at runtime. Their development
+dependencies give your editor and TypeScript a local API surface. Updating them does not replace the app's
+runtime or renderer. Match the oldest Paseo app you support, rather than selecting the newest React Native
+release independently. The manifest's `requirements.paseo` covers both the daemon and each connected app;
+it has no separate React Native key. SDK peer ranges constrain package installation, not verified host/API
+compatibility.
+
+React Native's [versioning policy](https://reactnative.dev/releases/versioning-policy) permits breaking changes
+in `0.x` minor releases. Treat a new minor series as a migration. Review React, React Native and SDK versions
+together; do not bypass conflicting peers to make CI green. Exact package pins do not stop Dependabot from
+proposing new versions. This optional rule keeps automated version PRs within the current React Native series:
+
+```yaml
+# Under the relevant npm entry in updates:
+ignore:
+ - dependency-name: react-native
+ update-types:
+ - version-update:semver-minor
+ - version-update:semver-major
+```
+
+This is a version-update policy, not an auto-merge rule. See
+[Dependabot's ignore options](https://docs.github.com/en/code-security/reference/supply-chain-security/dependabot-options-reference#ignore).
+Review series upgrades separately when the supported host and its React/SDK requirements permit them.
+
+For a candidate update, run ordinary `npm ci`, `npm run typecheck`, the plugin tests, and `ppd check` against
+the supported Paseo host. Then install into an isolated daemon and exercise the actual UI. Check a native
+client for changes to native components or behavior. `ppd check` includes compilation and load checks; it
+does not run TypeScript or prove every render path works. When targeting an older host, set `HERMESC` and
+`HERMES` to that host's engine: discovery otherwise prefers binaries shipped with the plugin's local React
+Native dependency.
+
+### Observed upgrade experiment
+
+On 2026-10-22, an isolated copy of Paseo Plans (`8bbe518`) was tested against the pinned Paseo 0.12.0
+host (`cafe4b0`), which uses React 19.1.0 and React Native 0.81.5:
+
+| Experiment | Result |
+| --- | --- |
+| Minimal dependency example: RN 0.87.1 with React 19.2.3 | Ordinary lockfile resolution passed |
+| The same example with only RN changed to 0.88.0 | Resolution failed: RN requires React `^19.3.0` |
+| Plans with RN 0.88.0 and its original React 19.1.0 | Ordinary installation failed with `ERESOLVE` |
+| Diagnostic copy with peers bypassed and required test-tooling peers restored | Typecheck failed on changed RN `View` and `ScrollView` ref types, including `focus` and `scrollTo`; 255 tests passed, one approximation test skipped |
+| Same diagnostic copy, pinned host compiler and target-host Hermes | 13 checks passed; client and server bundle hashes were unchanged by the RN development dependency bump |
+
+The bypass was an experiment, not an accepted dependency configuration. An initial bypass also removed
+automatically installed SDK and Vitest peers; those missing tooling dependencies were restored before
+attributing the remaining type errors to React Native. The test shows why passing unit tests and host
+compilation cannot replace ordinary dependency resolution and TypeScript. It does not establish RN 0.88
+runtime compatibility: the host renderer remained RN 0.81.5, no native host upgrade was attempted, and
+no user daemon or production dependency tree was changed. This experiment does not cover other plugins
+already adapted to RN 0.87.1 or newer host versions, and is not a universal RN compatibility range.
+
What ppd relies on
| Relies on | Used by | When it changes |
diff --git a/skills/paseo-plugin-dev/references/host-contract.md b/skills/paseo-plugin-dev/references/host-contract.md
index 4e9eca9..cd4e831 100644
--- a/skills/paseo-plugin-dev/references/host-contract.md
+++ b/skills/paseo-plugin-dev/references/host-contract.md
@@ -5,6 +5,7 @@ What Paseo 0.11 and 0.12 actually give a plugin at runtime. `ppd check` tests th
| Area | Contract | What to do |
| --- | --- | --- |
| Client modules (checked) | Only `react`, `react/jsx-runtime`, `react-native`, `@tanstack/react-query`, `zod`, `@getpaseo/plugin`, `@getpaseo/plugin/client`, `/client/ui`, `/client/react-native`. Any other runtime require throws `Module "" is not available in plugin client code`. Other npm packages are fine only if esbuild bundles them fully. | Keep host modules in `devDependencies`. |
+| Host module versions | The app supplies React and its paired React Native renderer. Local development versions provide types; an SDK peer range is not a runtime compatibility guarantee. React Native minor-series updates can break APIs. | Match the oldest supported host, review React/RN/SDK updates together, and run ordinary dependency resolution and typecheck before host checks. Do not auto-merge a new RN series or bypass peers to call it compatible. |
| Gestures (checked) | No `react-native-gesture-handler` or `react-native-reanimated`. | Build pinch and double tap from `onResponder*` / `PanResponder` and `Animated`. |
| Safe area (checked) | Plugin panels get no safe-area insets (getpaseo/paseo#5866, PR #5867). The Android nav bar can cover the last rows. | Pad the bottom yourself; runtime-detect a host `useSafeAreaInsets` export if one appears. |
| Horizontal scroll | A plugin horizontal `ScrollView` is not registered with the host, so a fast right swipe on a zoomed page opens the mobile sidebar. | Known limit; keep horizontal panning short or behind a mode. |
@@ -21,3 +22,7 @@ What Paseo 0.11 and 0.12 actually give a plugin at runtime. `ppd check` tests th
| MIME and previews | The daemon labels many binaries `application/octet-stream`; the Files tree has no previewer hook for plugins (getpaseo/paseo#3109, #5930). | Detect formats by magic bytes; provide your own entry points (panel, Command Center item, slash command). |
| Media | No native video primitive (#4562). Host `playAudio` exists from 0.11.2. | Plan media features around what the host exposes. |
| Theme and layout | Color every `Text` from `theme.colors`; size layout from `layout.compact`. No HTML elements, no `className`. | Test both `ppd web` viewports. |
+
+`ppd check` does not run TypeScript. Its successful compiler and Hermes checks do not prove that newer local
+types describe the supported host. Hermes discovery prefers the plugin's local React Native package before
+`PASEO_SOURCE`; use explicit `HERMESC` and `HERMES` from the target host when checking an older native runtime.