Run 54 React Native and Expo libraries on macOS, and add real pointer input to the e2e driver

ARCHITECTURE.md

@@ -72,7 +72,7 @@ The current distribution mechanism is local tarballs. `scripts/pack.ts` writes c
 
 `~/.spark` is the default global registry; `SPARK_HOME` overrides it. SDK records are versioned. Runtime registration records a path rather than copying an application. The managed prebuilt build project is created under the spark home unless a project is supplied explicitly. App-local `.spark` data and the global spark home are different scopes.
 
-The template manifests and `scripts/prepare-runtimes.ts` are the authoritative pins. We remain on Expo Desktop `1.0.0` and native template `54.81.1`, with Expo 54.0.37, React Native 0.81.6, React Native macOS 0.81.7, and React Native Windows 0.81.35. Creation uses a subprocess-scoped npm 11 executable because Expo Desktop misreads npm 12's local-tarball metadata. The selected package manager installs dependencies. This compatibility adapter does not patch upstream or change the host npm installation.
+The template manifests and `scripts/prepare-runtimes.ts` are the authoritative pins. We use Expo Desktop `1.0.6` and native template `55.83.10`, with Expo 55.0.32, React Native 0.83.10, React Native macOS 0.83.0, and React Native Windows 0.83.2. Creation uses a subprocess-scoped npm 11 executable because Expo Desktop misreads npm 12's local-tarball metadata. The selected package manager installs dependencies. This compatibility adapter does not patch upstream or change the host npm installation.
 
 Windows uses its own complete application template, with no runtime removal/replacement of macOS source files. SDK packing prepares the pinned Runtimes archive and Windows Nitro, OP-SQLite, and WebView adapters on either host OS. Patch application uses JavaScript; consumers receive ordinary dependency archives.
 
@@ -233,7 +233,7 @@ For a missing runtime, inspect SDK registration and binary metadata. For an inco
 
 Windows support is part of the existing framework. `spark create --platform windows`, `spark sdk build-runner --platform windows`, `spark dev`, and `spark build --dev` share project discovery, runtime metadata, registry, compatibility policy, Metro gating, terminal actions, and build records with macOS. There is no second session implementation or external source kit. See the [Windows guide](docs/windows-slice.md) for commands and prerequisites.
 
-The development targets are Windows 11 x64 and ARM64, RNW 0.81.35, New Architecture/Hermes, and the pinned Expo Desktop template. That RNW template uses MSVC v145 / Visual Studio 2026. The minimal starter provides the native host; the SDK prebuilt profile adds the desktop SDK and external libraries. Universal projects preserve configuration and generated projects across platform switches. Windows architecture defaults to the OS CPU (including ARM64 when the CLI is emulated) and can be overridden with `SPARK_WINDOWS_ARCH=x64|arm64`. It participates in the native fingerprint and product path. Build records retain the latest build per mode; registered binaries for the other architecture remain intact. Expo Desktop beta owns generation and RNW receives the corresponding `--arch x64` or `--arch ARM64`.
+The development targets are Windows 11 x64 and ARM64, RNW 0.83.2, New Architecture/Hermes, and the pinned Expo Desktop template. That RNW template uses MSVC v145 / Visual Studio 2026. The minimal starter provides the native host; the SDK prebuilt profile adds the desktop SDK and external libraries. Universal projects preserve configuration and generated projects across platform switches. Windows architecture defaults to the OS CPU (including ARM64 when the CLI is emulated) and can be overridden with `SPARK_WINDOWS_ARCH=x64|arm64`. It participates in the native fingerprint and product path. Build records retain the latest build per mode; registered binaries for the other architecture remain intact. Expo Desktop beta owns generation and RNW receives the corresponding `--arch x64` or `--arch ARM64`.
 
 Windows signatures include Windows native sources/project files and host/config integration; generated build outputs and NuGet lockfiles do not invalidate the source signature. Framework/runtime version changes participate in the mandatory host signature. Directly installed native packages without a Windows implementation fail clearly. This remains a constrained development graph, not acceptance of every third-party dependency arrangement or custom native project modification.
 

README.md

@@ -142,7 +142,7 @@ Packaging requires signing credentials and a notarization profile. It signs a st
 
 Windows uses the same CLI, starter, prebuilt registry, native compatibility checks, and managed Metro session. The Windows starter includes the native host; the SDK prebuilt profile includes the desktop modules and external integrations. Their Windows source implementations are ready for native acceptance. There is no separate source kit to install.
 
-On Windows 11 x64 or ARM64 (including Parallels), install the prerequisites in the [Windows guide](docs/windows-slice.md), including Visual Studio 2026 / MSVC v145 for the pinned RNW 0.81.35 template. Then run from the framework checkout:
+On Windows 11 x64 or ARM64 (including Parallels), install the prerequisites in the [Windows guide](docs/windows-slice.md), including Visual Studio 2026 / MSVC v145 for the pinned RNW 0.83.2 template. Then run from the framework checkout:
 
 ```powershell
 bun install
@@ -316,7 +316,7 @@ macOS 14+ (Apple Silicon) supported; Windows preview, not yet verified
 
 This is a prerelease; APIs and tooling may change. Intel macOS has architecture selection tooling but no verified native build/runtime support; see [Intel macOS](docs/macos-intel.md). Windows currently covers development builds, with details in the [Windows guide](docs/windows-slice.md). Linux and Mac App Store distribution are unsupported. Mobile/web development delegates to Expo.
 
-The checkout uses Expo SDK 54, React Native 0.81, and Expo Desktop 1.0.0. See the [integration boundary](docs/expo-desktop-integration.md) for upstream requirements.
+The checkout uses Expo SDK 55, React Native 0.83, and Expo Desktop 1.0.6. See the [integration boundary](docs/expo-desktop-integration.md) for upstream requirements.
 
 Use the [Mac and Windows manual acceptance checklist](docs/desktop-manual-acceptance.md)
 to validate a checkout on real machines, including runtime rebuilds and OS interactions.