@radhya/mach 2.0.41 → 2.0.43

package/README.md

@@ -145,15 +145,21 @@ mach ota rollback --update-id <updateId>
 mach ota promote --update-id <updateId>
 ```
 
-For Expo apps, `mach ota setup` writes `ota` config and wires `@radhya/mach/expo-plugin`. The plugin configures Expo Updates from `mach.config.json`, so updates are served from Mach instead of EAS Update. Install `expo-updates`, then create and install one new native build after the initial setup. Previously installed binaries keep the update URL embedded when they were built and cannot be retrofitted by an OTA publish.
+`mach ota setup` uses the open-source `expo-updates` runtime for both Expo and bare React Native apps while keeping publishing, manifests, assets, channels, metrics, and rollback on Mach. It writes the `ota` config, installs or refreshes the compatible project-local plugin when approved, and wires `@radhya/mach/expo-plugin`. Updates are served from Mach instead of EAS Update.
+
+For bare React Native, setup first installs Expo Modules when needed, then uses the installed `expo-updates configuration:syncnative` tool to update the committed Android and iOS projects. It does not run Expo prebuild or replace the native folders. Run setup from a clean branch so you can review the package and native integration changes.
+
+Create and install one new native build after the initial setup. Previously installed binaries keep the update URL embedded when they were built and cannot be retrofitted by an OTA publish.
 
 With the default `ON_LOAD` behavior, the first cold launch checks for and downloads a compatible update. The next cold launch runs it. Mach records unique downloaded, applied, and failed devices automatically from Expo Updates requests; app code does not call a metrics endpoint and never receives storage credentials.
 
 Command flags always win over config values. For example, `mach ota publish --channel staging --runtime-version 1.2.0` overrides `ota.channel` and `ota.runtimeVersion`.
 
-Runtime version is the OTA compatibility boundary. Mach resolves Expo-style `appVersion`, `sdkVersion`, and `nativeVersion` policies, stores the resolved runtime on each build, and serves OTA updates only to matching platform/channel/runtime combinations.
+Runtime precedence is `--runtime-version`, `ota.runtimeVersion`, `ota.runtimeVersionPolicy`, Expo config, then package version fallback. A configured Mach policy therefore replaces stale `runtimeVersion` values left in Expo config. Runtime version is the OTA compatibility boundary: Mach stores it on each build and serves updates only to matching platform/channel/runtime combinations. Build, verify, and publish commands stop when the project-local Expo plugin would embed a different runtime.
+
+Bare React Native uses the same Expo Updates protocol and the same Mach endpoint as Expo. `mach-react-native` remains reserved for a future Mach-owned native runtime and cannot currently be selected for publishing.
 
-Vanilla React Native uses the same command surface. The native OTA client and automatic native patching are intentionally guarded until the Mach RN client package is ready.
+See [OTA Updates](docs/ota.md) for setup behavior, bare React Native requirements, runtime matching, and validation.
 
 ## Deep Links