@agimon-ai/po-native 0.0.0-stage → 0.0.1-alpha.4

package/LICENSE

@@ -0,0 +1,149 @@
+License text copyright © 2017 MariaDB Corporation Ab, All Rights Reserved.
+"Business Source License" is a trademark of MariaDB Corporation Ab.
+
+Parameters
+
+Licensor:             Agimon Pty Ltd
+Licensed Work:        Po, the software in the Po source repository and the
+                      packages released from it, in each version released by
+                      the Licensor.
+                      The Licensed Work is (c) 2026 Agimon Pty Ltd.
+                      Material identified as third-party in the "Third-party
+                      components" section at the end of this file or in a
+                      NOTICE file, and any package or directory whose own
+                      license file grants a different license, is not part of
+                      the Licensed Work and remains under its own license.
+Additional Use Grant: You may make production use of the Licensed Work if
+  your use is Eligible Use. "Eligible Use" is production use that falls
+  within at least one of the following:
+
+  (a) Personal Use. Use by an individual for their own personal purposes,
+      and not on behalf of, or for the benefit of, an employer, client, or
+      other Organization. Use by an individual in the course of employment
+      or engagement by an Organization is use by that Organization.
+
+  (b) Small Organization Use. Use by or on behalf of an Organization whose
+      Annual Revenue is less than USD 1,000,000.
+
+  (c) Non-profit, Education and Research Use. Use, regardless of Annual
+      Revenue, by (i) an Organization registered or recognized as a
+      non-profit or charitable organization under the laws of its
+      jurisdiction, for its non-profit purposes; (ii) an accredited school,
+      college, or university, for teaching, learning, or academic research;
+      or (iii) a publicly funded research institution, for its research.
+
+  (d) Service Provider Use. Use by a consultant, contractor, agency, or other
+      service provider, regardless of its own Annual Revenue, solely to
+      build, deploy, host, operate, or support the Licensed Work for a client
+      whose own use would be Eligible Use under (a), (b), or (c). A service
+      provider's use for its own purposes is Eligible Use only if the service
+      provider itself qualifies under (b) or (c).
+
+
+  Hosted services. Offering the Licensed Work to third parties as a hosted
+  or managed service whose primary value is the Licensed Work is Eligible
+  Use only if each such third party's own use would be Eligible Use.
+
+  Definitions. "Organization" means any company, partnership, sole
+  proprietorship, trust, association, government body, or other entity, and
+  includes an individual acting in a business or professional capacity.
+  "Affiliate" means any entity that directly or indirectly controls, is
+  controlled by, or is under common control with an Organization, where
+  "control" means ownership of more than 50% of the voting interests of an
+  entity or the power to direct its management and policies by contract or
+  otherwise. "Annual Revenue" means the total gross revenue of an
+  Organization and all of its Affiliates combined, from all sources and
+  whether or not related to the Licensed Work, for its most recently
+  completed fiscal year, or, if it has not completed a fiscal year, for the
+  twelve months before the use (or since its formation, if shorter),
+  converted into US dollars at the average exchange rate for that period.
+  Proceeds of equity or debt financing are not revenue.
+
+  Threshold. If an Organization stops qualifying under (b), its existing
+  production use remains Eligible Use for 90 days after it stops
+  qualifying, after which it must obtain a commercial license or stop
+  production use. Use that was Eligible Use when it occurred never requires
+  a commercial license after the fact.
+Change Date:          Four years from the date a version of the Licensed Work
+                      is first publicly released by the Licensor.
+Change License:       Apache License, Version 2.0
+
+For information about alternative licensing arrangements for the Licensed
+Work, please visit: https://agimon.ai/licensing
+
+Notice
+
+The Business Source License (this document, or the "License") is not an Open
+Source license. However, the Licensed Work will eventually be made available
+under an Open Source License, as stated in this License.
+
+-----------------------------------------------------------------------------
+
+Business Source License 1.1
+
+Terms
+
+The Licensor hereby grants you the right to copy, modify, create derivative
+works, redistribute, and make non-production use of the Licensed Work. The
+Licensor may make an Additional Use Grant, above, permitting limited
+production use.
+
+Effective on the Change Date, or the fourth anniversary of the first publicly
+available distribution of a specific version of the Licensed Work under this
+License, whichever comes first, the Licensor hereby grants you rights under
+the terms of the Change License, and the rights granted in the paragraph
+above terminate.
+
+If your use of the Licensed Work does not comply with the requirements
+currently in effect as described in this License, you must purchase a
+commercial license from the Licensor, its affiliated entities, or authorized
+resellers, or you must refrain from using the Licensed Work.
+
+All copies of the original and modified Licensed Work, and derivative works
+of the Licensed Work, are subject to this License. This License applies
+separately for each version of the Licensed Work and the Change Date may vary
+for each version of the Licensed Work released by Licensor.
+
+You must conspicuously display this License on each original or modified copy
+of the Licensed Work. If you receive the Licensed Work in original or
+modified form from a third party, the terms and conditions set forth in this
+License apply to your use of that work.
+
+Any use of the Licensed Work in violation of this License will automatically
+terminate your rights under this License for the current and all other
+versions of the Licensed Work.
+
+This License does not grant you any right in any trademark or logo of
+Licensor or its affiliates (provided that you may use a trademark or logo of
+Licensor as expressly required by this License).
+
+TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON
+AN “AS IS” BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS,
+EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND
+TITLE.
+
+MariaDB hereby grants you permission to use this License’s text to license
+your works, and to refer to it using the trademark “Business Source License”,
+as long as you comply with the Covenants of Licensor below.
+
+Covenants of Licensor
+
+In consideration of the right to use this License’s text and the “Business
+Source License” name and trademark, Licensor covenants to MariaDB, and to all
+other recipients of the licensed work to be provided by Licensor:
+
+1. To specify as the Change License the GPL Version 2.0 or any later version,
+   or a license that is compatible with GPL Version 2.0 or a later version,
+   where “compatible” means that software provided under the Change License can
+   be included in a program with software provided under GPL Version 2.0 or a
+   later version. Licensor may specify additional Change Licenses without
+   limitation.
+
+2. To either: (a) specify an additional grant of rights to use that does not
+   impose any additional restriction on the right granted in this License, as
+   the Additional Use Grant; or (b) insert the text “None”.
+
+3. To specify a Change Date.
+
+4. Not to modify this License in any other way.

package/README.md

@@ -1,3 +1,162 @@
-# Temporary Holding Version
+# Po Native
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The Po phone app for iOS and Android, built with Expo 57 and React Native 0.86. App name "Po", company iOS bundle id `ai.po.app`, Android package `ai.agimon.po`. It is private, experimental (`stage:experimental`), and built locally only: no EAS or other cloud build.
+
+The app pairs with one Po host over its remote-access tunnel, lists that host's sessions, shows a session transcript with a composer, and runs the host's native plugin contributions (for example po-task's task tool renderer and task graph channel) from a signed composition it downloads.
+
+## How it works
+
+- **Pairing.** Scan the host's pairing QR with the camera, or paste the URL. The host approves the request on its own screen. The app then registers device keys (see the trust model) and keeps the host record.
+- **Connection.** Remote HTTP with the device cookie, three sealed channels (session, protocol, HTTP), the Pi `Client` over the protocol socket, and the hub socket. A dropped hub signs in again with the device key and rebuilds the connection.
+- **Session state.** `@agimon-ai/po-web-dashboard/core` supplies the session, transcript, and plugin registry stores, the same ones the browser cockpit uses, without any DOM dependency.
+- **Plugins.** The host advertises native compositions through `nativeGlobal` and `workspaces[].nativeComposition` on `/api/compositions` and `nativeComposition` on a session summary. For each mount the app loads the composition through its verified cache, evaluates it, keeps only the plugin ids the descriptor admits, installs them in the plugin registry, and starts them. Channel frames reach plugins through `dispatchChannelFrame`. A newer load for a mount makes older ones stale.
+- **Navigation.** `App` registers screens by phase (reconnecting, pairing, ready) in a React Navigation native stack, inside `SafeAreaProvider > PoNativeProvider > KeyboardProvider > NavigationContainer`. Native headers own back navigation and swipe back; Sessions has a large title and a Settings action. A session opens in the live runtime on focus and closes on blur; Settings reloads trusted devices on focus.
+- **Lists and content.** Sessions and transcripts use the component library's FlashList-backed `List`; the transcript uses `startAtBottom`. Assistant text uses `Markdown`; tool entries use the plugin `sessionToolRenderer`, falling back to `MessageItem` and `CodeBlock`.
+- **Sheets.** `PoNativeProvider` supplies the shared gesture root and bottom sheet host for plugin detail sheets and action menus. The composer's decision prompts stay inline as gentle rose panels, not modal sheets. `SettingsScreen` lists trusted devices, revokes one through biometric step-up, and forgets the host.
+- **Styling.** `react-native-unistyles` 3.5.2 with Po's `light` and `dark` themes from `@agimon-ai/po-web-components/nativeTheme`, registered in `src/unistyles.ts` with adaptive themes. Every screen and component keeps its `StyleSheet.create` in its own file so the Unistyles Babel plugin rewrites it.
+
+## Trust model
+
+The full model is in [Security model](../../../docs/securities.md#trusted-native-devices). In short:
+
+- **Pairing needs host approval and biometrics.** If the phone has no Face ID, Touch ID, or fingerprint enrolled, pairing stops with "Set up Face ID or a fingerprint to pair this phone."
+- **Two device keys.** After approval the app generates two P-256 keys and registers them through the sealed gateway: an identity key for silent sign-in, and a step-up key that only biometrics unlock. They live in `expo-secure-store` as `po.device.identity.v1` and `po.device.stepup.v1`; the host record (origin, trusted device id, pinned signer key and revision, label) is `po.host.v1`. All three are `WHEN_UNLOCKED_THIS_DEVICE_ONLY`.
+- **Reconnect.** On start the app signs in with the identity key, no QR and no host approval. It trusts the host's fresh tunnel key only after the bundle signer it pinned from the QR attests that key over the app's own nonce. A changed signer fails closed and Home shows the connect card again.
+- **Step-up.** Every gated action from a device-key session needs a biometric signature, on every tunnel. `fetchWithStepUp` retries a request once after a 401 that names an action.
+- **Revocation.** From the host UI, or from a paired phone after step-up (`device.revoke`). A quick-tunnel browser cannot revoke. Forget host requires successful remote revocation before deleting local keys; failure retains them for retry. A confirmed revocation is checkpointed so interrupted local cleanup can finish after restart. A biometric change invalidates the step-up key; pair again by QR.
+- **Keys are software keys.** They are decrypted into JS memory to sign. They are not Secure Enclave or StrongBox keys.
+
+### Trusted compositions are not sandboxed
+
+A native composition is host code, one CommonJS module per plugin. The app verifies each module before running it: on every load, cached or downloaded, it checks the signed manifest against the pinned signer with the `native` bundle profile (top-level `.js` modules, each at most 4 MiB), requires the exact advertised revision, and checks that module's hash. The same revision with a different hash is refused, a signer change clears the cache, and the cache keeps at most 64 modules under `Paths.cache/po/compositions/`. It then evaluates each module with `new Function` against a frozen map of host modules (`NATIVE_HOST_MODULE_IDS` from `@agimon-ai/po-core/native`); any other `require` throws. A module that fails to load, verify, or evaluate is left out with a warning and the rest still run. That map is a compatibility boundary, not a sandbox: a verified module runs with the app's full JavaScript privileges.
+
+## Local checks
+
+```sh
+pnpm install
+pnpm nx run-many -t lint typecheck build test -p @agimon-ai/po-native --parallel=2
+```
+
+`build` runs the proof fixture builder and `expo export --platform all` into `dist/shell`. `build:proof` (`scripts/buildProof.mjs`) builds a small counter composition and signs it with the `native` profile; tests use it as a fixture. Node tests do not exercise native crypto, Hermes, or native modules.
+
+## Running on a device
+
+```sh
+pnpm nx run @agimon-ai/po-native:prebuild
+pnpm --filter @agimon-ai/po-native ios:setup
+pnpm nx run @agimon-ai/po-native:ios
+JAVA_HOME=$(/usr/libexec/java_home -v 17) pnpm nx run @agimon-ai/po-native:android
+```
+
+`ios` and `android` are local Release builds. `ios:setup` installs CocoaPods 1.16.2 under `.build/gems` and the iOS commands set `GEM_HOME`, `GEM_PATH`, and `PATH` for that process only; system gems and shell configuration are untouched. The generated `ios/` and `android/` folders, Expo state, and `.build/` are gitignored and never edited by hand; signing changes come from `@agimon-ai/po-expo-signing` during prebuild.
+
+The company iOS build requires an `ai.po.app` provisioning profile with Push Notifications. Previous
+`ai.agimon.po` iOS installs are a separate app identity; rebuild and pair the company app. Native push
+checks the installed iOS application ID before enrollment and reads its provisioning-profile APNs
+environment, with a production fallback for App Store/TestFlight installs.
+Android remains `ai.agimon.po` with FCM. See [push setup](../../foundations/po-notification/README.md#native-push-server-credentials).
+
+## Ad hoc builds
+
+```sh
+pnpm nx run @agimon-ai/po-native:ios:adhoc
+pnpm nx run @agimon-ai/po-native:android:adhoc
+```
+
+Both run `scripts/buildAdHoc.mjs`, which fails before touching earlier outputs when a required variable is missing. Every command runs through `spawnSync` with an argument array, and secret values are redacted from console output and logs.
+
+- **iOS** (macOS with Xcode): build the proof fixture, `expo prebuild --clean --platform ios`, `pod install`, `xcodebuild archive`, then `-exportArchive` with a temporary `ExportOptions.plist` (`method: release-testing`, manual signing) that is deleted afterwards. Run `ios:setup` first.
+- **Android**: build the proof fixture, `expo prebuild --clean --platform android`, then `./gradlew assembleRelease` under JDK 17.
+
+| Variable                              | Platform | Required | Meaning                                                                         |
+| ------------------------------------- | -------- | -------- | ------------------------------------------------------------------------------- |
+| `APPLE_TEAM_ID`                       | iOS      | yes      | Team id for `appleTeamId`, `DEVELOPMENT_TEAM`, and the export plist             |
+| `PO_NATIVE_IOS_PROFILE`               | iOS      | yes      | Provisioning profile name; the Release target switches to manual signing        |
+| `PO_NATIVE_IOS_CODE_SIGN_IDENTITY`    | iOS      | no       | `CODE_SIGN_IDENTITY` and export `signingCertificate`, e.g. `Apple Distribution` |
+| `PO_NATIVE_ANDROID_KEYSTORE`          | Android  | yes      | Path to the release keystore, made absolute before Gradle runs                  |
+| `PO_NATIVE_ANDROID_KEYSTORE_PASSWORD` | Android  | yes      | Keystore password                                                               |
+| `PO_NATIVE_ANDROID_KEY_ALIAS`         | Android  | yes      | Key alias                                                                       |
+| `PO_NATIVE_ANDROID_KEY_PASSWORD`      | Android  | yes      | Key password                                                                    |
+| `JAVA_HOME`                           | Android  | no       | JDK 17; on macOS it defaults to `/usr/libexec/java_home -v 17`                  |
+
+Secrets come only from these variables or the keychain. Gradle reads the Android values at build time, so none is written into the generated project.
+
+**Output.** `.build/adhoc/po-native.ipa` or `.build/adhoc/po-native.apk`, plus `.build/adhoc/SHA256SUMS` covering whichever artifacts exist. Per-step logs (mode `0600`) go to `.build/adhoc/logs/<platform>/`, and intermediate files to `.build/adhoc/work/<platform>/`.
+
+## TestFlight archive and export
+
+Use an installed **App Store Connect distribution profile** for `ai.po.app`, with Push Notifications,
+and the matching **Apple Distribution certificate and private key** in the local keychain. A development
+or ad hoc profile is not interchangeable. Run `ios:setup` first. No App Store Connect API key is needed
+for this local export.
+
+```sh
+export APPLE_TEAM_ID="RYQ366PW4R"
+export PO_NATIVE_IOS_PROFILE="YOUR_APP_STORE_CONNECT_PROFILE"
+export PO_NATIVE_IOS_CODE_SIGN_IDENTITY="Apple Distribution"
+export PO_NATIVE_IOS_BUILD_NUMBER="42"
+export PO_NATIVE_APNS_ENVIRONMENT="production"
+pnpm nx run @agimon-ai/po-native:ios:testflight
+```
+
+The same command is available as `pnpm --filter @agimon-ai/po-native ios:testflight`. It reuses the
+local iOS archive script, defaults the signing identity to `Apple Distribution`, and supplies production
+APNs to prebuild. An explicitly configured sandbox environment is rejected before building.
+`PO_NATIVE_IOS_BUILD_NUMBER` is required, becomes Expo's `ios.buildNumber`, and must increase for each
+submitted build. Use a valid `CFBundleVersion`, for example `42` or `1.2.3` (first component 1-9999,
+remaining components 0-99). The marketing version remains `version` in `app.config.ts`.
+
+Before export, the script verifies the archive's bundle ID, build number and signed production APNs
+entitlement. It exports with `method: app-store-connect`, `destination: export`, manual signing, and
+`manageAppVersionAndBuildNumber: false`. It does not upload, submit, install, create credentials, or
+modify the Apple portal. Upload remains a separate, explicitly approved action.
+
+TestFlight installs have no embedded provisioning profile. When the profile environment is unavailable,
+the app checks the native release type and registers `production` only for App Store/TestFlight builds.
+Other release types still require an explicit profile environment. After pairing and allowing notifications,
+open the app and verify `nativePush.environment: "production"` on its trusted device record in the
+server's `~/.po/web/trusted-devices.json`. Do not print or share the token. This confirms enrollment,
+not APNs delivery.
+
+**Output:** `.build/testflight/po-native.ipa` and `.build/testflight/SHA256SUMS`. The archive and dSYMs
+remain under `.build/testflight/work/ios/`, with private per-step logs under `.build/testflight/logs/ios/`.
+Existing ad hoc and Android commands keep their methods and `.build/adhoc/` outputs. A failed build
+keeps the previous final IPA/APK. Command/configuration tests do not verify real signing, App Store
+Connect acceptance, or TestFlight push delivery.
+
+## Native stories
+
+Each screen has a story beside it (`src/screens/*.stories.tsx`), and po-task has three `*.native.stories.tsx` stories for its native task UI. They are tagged `style-system`, `mockup`, and `native`. They render through `@agimon-ai/style-system`'s native mode: this package's `style-system.config.yaml` extends the root `native-app` preset (`bundler: vite-react-native`, `unistylesConfig: src/unistyles.ts`, dark scheme, 393 by 852 viewport). Whether style-system accepts po-task's stories, which live in another package, when rendered against this app path is unverified.
+
+## Not yet
+
+- **Activity groups are not rendered.** Only the plain host `activity` slot is; `activity.<group>` fills such as po-task's task section do not appear.
+- **Threads, transient tabs, and composer context are inert placeholders.** The slot props the app passes to plugins stub `renderThread`, `openTransientTab`, `closeTransientTab`, `appendComposerDraft`, `attachComposerContext`, and `attachComposerCapture`; `sendSessionFrame`, `renderSlot`, and `slotData` are inert there too.
+- **A session's composition mounts only if its summary is loaded when the session is opened.** A summary that arrives later does not mount it.
+- **Not ported from po-web:** alerts, voice handoff, dormant transcripts, thread frames, and held channels.
+- **`po doctor` does not show the native build.** `po sync --check` does.
+- **Device runtime is unverified.** No release-mode device run has confirmed that Hermes runs `new Function`, that `react-native-quick-crypto` WebCrypto ECDSA produces the P1363 signatures the host verifies, that `expo-secure-store` biometric items prompt and invalidate as expected, or that the `expo-camera` scanner works.
+- **Visual fidelity is BLOCKED.** The screens and stories are mockups (`mockup` tag). Rendered appearance needs human approval of the native stories before it can be claimed.
+- **One paired host per phone.**
+
+## Phase 3 native grants
+
+`accountGrants` exposes `onSessionStart` and `onJobCreated` typed hooks. Same-host work returns
+no grant and does not contact the account service. Cross-host work gets a 30-day, non-redelegable
+C5 signed by the account device key with the issuer's current revocation epoch. SecureStore keeps
+envelopes in issuer-specific namespaces. Opening or foregrounding the app renews unexpired grants
+only inside the seven-day window. An epoch change never silently renews old consent. An explicit
+renew action may obtain new consent after refreshing account trust.
+
+`receiveGrantPause` accepts the typed work-paused event plus the authenticated reporting host id,
+matches it to saved work, and supplies Home's gentle rose notice. `startLiveRuntime` accepts an
+optional network-authenticated `federationHostId`. The local pairing record id is not that id.
+
+Cross-host session/job creation and network host-id mapping are pending phases 5 and 7. Those
+callers must pass the returned envelopes to the calling host, which stores them and refreshes
+delegated tokens. App-open renewal currently updates the phone's saved envelopes only; host
+handoff and automatic job resume are not mounted yet. No public host upload route is invented.
+The notice deliberately says permission was renewed on this phone, not that a job resumed.
+
+Notice targets: `Native/Design/Grants`, Playground, Dark, Renewing and Retry. These remain mockups.
+Visual fidelity is BLOCKED pending explicit user approval, and native device behavior is unverified.

package/app.config.ts

@@ -0,0 +1,84 @@
+import type { ExpoConfig } from 'expo/config';
+
+const apnsEnvironment = process.env.PO_NATIVE_APNS_ENVIRONMENT ?? 'development';
+if (apnsEnvironment !== 'development' && apnsEnvironment !== 'production') {
+  throw new Error('PO_NATIVE_APNS_ENVIRONMENT must be development or production.');
+}
+
+const iosBuildNumber = process.env.PO_NATIVE_IOS_BUILD_NUMBER?.trim();
+if (iosBuildNumber !== undefined && !/^[1-9]\d{0,3}(?:\.\d{1,2}){0,2}$/u.test(iosBuildNumber)) {
+  throw new Error('PO_NATIVE_IOS_BUILD_NUMBER must be a valid CFBundleVersion (for example 42).');
+}
+// A production build must name its identity home explicitly; the default issuer is for development only.
+if (apnsEnvironment === 'production' && !process.env.PO_NATIVE_IDENTITY_ISSUER?.trim()) {
+  throw new Error('PO_NATIVE_IDENTITY_ISSUER must be set when PO_NATIVE_APNS_ENVIRONMENT is production.');
+}
+const identityIssuer = new URL(process.env.PO_NATIVE_IDENTITY_ISSUER ?? 'https://po.agimon.win');
+if (
+  identityIssuer.protocol !== 'https:' ||
+  identityIssuer.username ||
+  identityIssuer.password ||
+  identityIssuer.pathname !== '/' ||
+  identityIssuer.search ||
+  identityIssuer.hash
+) {
+  throw new Error('PO_NATIVE_IDENTITY_ISSUER must be an HTTPS origin.');
+}
+const config: ExpoConfig = {
+  name: 'Po',
+  slug: 'po',
+  scheme: 'po',
+  extra: { identityIssuer: identityIssuer.origin },
+  version: '0.0.1',
+  icon: './assets/icon.png',
+  orientation: 'portrait',
+  platforms: ['ios', 'android'],
+  ios: {
+    bundleIdentifier: 'ai.po.app',
+    usesAppleSignIn: true,
+    // Export compliance answer on App Store Connect: no non-exempt encryption.
+    config: { usesNonExemptEncryption: false },
+    ...(iosBuildNumber ? { buildNumber: iosBuildNumber } : {}),
+    ...(process.env.APPLE_TEAM_ID ? { appleTeamId: process.env.APPLE_TEAM_ID } : {}),
+  },
+  android: {
+    package: 'ai.agimon.po',
+    ...(process.env.PO_NATIVE_ANDROID_GOOGLE_SERVICES_FILE
+      ? { googleServicesFile: process.env.PO_NATIVE_ANDROID_GOOGLE_SERVICES_FILE }
+      : {}),
+    blockedPermissions: ['android.permission.READ_EXTERNAL_STORAGE', 'android.permission.WRITE_EXTERNAL_STORAGE'],
+  },
+  plugins: [
+    'expo-apple-authentication',
+    ['expo-notifications', { mode: apnsEnvironment, defaultChannel: 'po-notifications' }],
+    ['expo-secure-store', { faceIDPermission: 'Confirm it is you before Po does something important.' }],
+    ['expo-camera', { cameraPermission: 'Scan a Po pairing QR code.' }],
+    [
+      'expo-image-picker',
+      {
+        photosPermission: 'Attach photos to your message for Po.',
+        cameraPermission: false,
+      },
+    ],
+    [
+      'react-native-audio-api',
+      {
+        iosMicrophonePermission: 'Record your voice for Po while you choose to record.',
+        iosBackgroundMode: true,
+        androidPermissions: [
+          'android.permission.RECORD_AUDIO',
+          'android.permission.FOREGROUND_SERVICE',
+          'android.permission.FOREGROUND_SERVICE_MICROPHONE',
+          'android.permission.POST_NOTIFICATIONS',
+        ],
+        androidForegroundService: true,
+        androidFSTypes: ['microphone'],
+        disableFFmpeg: true,
+      },
+    ],
+    '@config-plugins/react-native-webrtc',
+    '@agimon-ai/po-expo-signing',
+  ],
+};
+
+export default config;

package/babel.config.cjs

@@ -0,0 +1,8 @@
+// babel-preset-expo already registers the react-native-worklets plugin; do not add it here.
+module.exports = function babelConfig(api) {
+  api.cache(true);
+  return {
+    presets: ['babel-preset-expo'],
+    plugins: [['react-native-unistyles/plugin', { root: 'src' }]],
+  };
+};