Native app E2E (Android emulator, iOS simulator)

Two manual scripts drive the real app shells against the Cloud Studio page. They are NOT part of npm test, not referenced by any workflow, and not covered by CI. Nobody should read a green CI as “the native app was exercised”: it was not.

npm run e2e:native:android
npm run e2e:native:ios

Both run under bun (they import .ts files from the mcp-cloud repository).

What they serve

The scripts do not test the deployed Cloud Studio. They import the page builders from a local checkout of mcp-cloud (src/pages/cloud-studio-page.ts, src/pages/chat.ts, src/services/cloud-studio.ts, src/data/film-templates.ts), serve the resulting HTML from a local HTTP server, and point the app at it. The editor frame is served from a local build (PP_FX_EDITOR, default http://127.0.0.1:8088, a static server on this repo’s dist/ after npm run build). The only deployed-service step is the first one, which loads https://cloud.pinepaper.studio/templates to check the document-start guard.

What they need

Variable Needed by Meaning
PP_CLOUD_REPO both Absolute path of an mcp-cloud checkout. Unset: the script stops with an error.
ANDROID_SDK_ROOT Android Android SDK folder; adb is platform-tools/adb under it. Or set ADB_BIN to the adb binary.
IOS_SIM_UDID iOS UDID of a booted iOS Simulator (xcrun simctl list devices booted). No default.
PP_FX_EDITOR both Optional. Base URL of the local editor build. Default http://127.0.0.1:8088.
PP_NATIVE_E2E_OUT both Optional. Screenshot output folder. Default ./test-results/native.

Also: a booted Android emulator with studio.pinepaper.app installed (debug build), or an iOS Simulator with the Debug build (the iOS script uses the PP_E2E_CONTROL bridge that exists only in #if DEBUG, and the Debug-only Info-Debug.plist, which allows local networking). Android also needs Chromium WebView DevTools reachable through adb forward (the script does this).

What a pass does and does not show

It shows the injected scripts (cloud_safe_mo.js, cloud_studio_mobile_fix.js) and the shells’ back handling work against the page builders in that checkout, on that emulator or simulator. It does not show anything about the deployed Studio’s current build, real devices, release builds, or store behaviour.