Device testing: link the app to an EAS project so CI produces installable builds (today every EAS run skips) #183

Context

Nothing that landed in 2.0 has run on a device yet:

• the hybrid shell (feat!: rebuild as a hybrid shell around the web Console (v2.0) #144);
• the server probe (Private servers: probe with the anonymous discovery endpoints and confirm the server's identity before connecting #154);
• QR connect (Connect by QR code: objectos://connect?server=… links and the native scanner screen #156);
• saved connections (Saved connections and the native "切换组织" switcher (organizations and company servers) #152);
• MDM (Managed deployment: read the server URL (and an optional lock) from MDM managed app configuration #157);
• the IdP sign-in bar (External sign-in bar: let enterprise IdP pages load in the WebView during sign-in, behind a native bar showing the IdP's domain #155);
• the bridge methods (Bridge: scan() — barcode / QR scanning for Console fields #146, Bridge: pickImage(), openFile() and share() — reliable photo capture, attachment download and sharing #147, Bridge: stable install id and pushTokenChanged for device registration; document the no-Service-Worker rule #163);
• the ten locales (Languages: follow the phone's language in the platform's 11 locales (ruling F of objectstack#29349) #159).

The seat post #160 also records "Native rebuild owed": expo-camera, the cookie-manager module and modules/managed-config have never been compiled.

Measured on main at ddcf2d5:

• CI builds nothing. Every EAS Build and EAS Update run on main finishes in 6–17 s, for example run 41569850272. Each step is gated on env.EXPO_TOKEN != '', so the runs are green but empty: the EXPO_TOKEN secret is not set.
• The app is not linked to an EAS project. app.config.ts has no extra.eas.projectId, no owner, no updates.url and no runtimeVersion. So eas build would prompt to create a project, and eas update cannot publish. The slug is objectos-mobile (Rebrand the app to ObjectOS: app name, URL scheme objectos, bundle id / package ai.objectos.mobile #151).
• The preview profile pre-fills a stale server. eas.json build.preview.env.EXPO_PUBLIC_DEFAULT_SERVER_URL is https://staging.objectstack.com.

Ask

Maintainer only (needs the Expo account; a seat cannot do it):

1. In the Expo account or organization that should own the app, run eas init once in this repo. That creates the objectos-mobile project and prints its projectId.
2. Add a GitHub Actions secret EXPO_TOKEN: an Expo robot or personal access token for that account.
3. For iOS device builds: an Apple Developer team, and eas credentials (or let eas build manage them). For Android, EAS generates the keystore.

Code (seat, one PR after step 1):

1. Write the printed projectId and owner into app.config.ts.
2. Add updates.url (https://u.expo.dev/<projectId>) and runtimeVersion: { policy: "fingerprint" }. An OTA update must never reach a binary whose native modules differ; the fingerprint policy guarantees that.
3. Change the preview profile's EXPO_PUBLIC_DEFAULT_SERVER_URL to "", or to the staging environment the maintainer names.
4. Add a preview channel, plus development-device (a development client with ios.simulator: false), so a phone can install a dev build.
5. Update docs/DEVICE-TESTING.md with the install paths:
   • Android: the APK link or QR from EAS;
   • iOS: register the device with eas device:create, then an internal-distribution build.

Then add a short smoke checklist per landed card, built from each card's manual check.

Acceptance

• A push to main (or a manual workflow_dispatch with profile preview) produces an installable Android build and an iOS build on EAS. The run logs show the build steps executing, not skipped.
• docs/DEVICE-TESTING.md lets someone with only a phone install the preview build and connect to a server.

Note: once EXPO_TOKEN is set, every merge to main starts real EAS builds and an OTA publish. That is the "publishes on merge" condition in the lane charter, and the seat's landing guard (#160) then hands merges back to the maintainer.