mobile: report bundle identity in OTA manifest requests

Stamp git-hash, native-version, and native-build into the Expo-Extra-Params
header via Updates.setExtraParamAsync so the manifest server can identify the
running bundle in human-readable terms. The standard expo-current-update-id
and expo-runtime-version headers are opaque (UUID / fingerprint hash) by
design.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: aapeliv

app/mobile/app/_layout.tsx

@@ -1,6 +1,7 @@
 import "react-native-reanimated";
 import "@/i18n";
 import "@/service/sentry";
+import "@/service/updateExtraParams";
 
 import {
   Ubuntu_300Light,

app/mobile/service/updateExtraParams.ts

@@ -0,0 +1,43 @@
+import * as Sentry from "@sentry/react-native";
+import * as Application from "expo-application";
+import Constants from "expo-constants";
+import * as Updates from "expo-updates";
+
+// Stamp the running bundle's identity into the manifest request via the
+// Expo-Extra-Params header (Updates.setExtraParamAsync persists natively and
+// the native client serializes the dictionary on every update check). This is
+// the protocol's intended escape hatch for human-readable client identifiers —
+// the standard expo-current-update-id / expo-runtime-version headers are
+// opaque UUIDs / fingerprint hashes by design.
+//
+// Steady-state accuracy: a bundle sets its own values on first launch, so
+// every later check reports them. The only stale check is the very first
+// launch after an OTA applies, because expo-updates fires the check before
+// JS runs setExtraParamAsync (checkAutomatically=ON_LOAD); from the next
+// launch onward it's accurate.
+
+const extra = Constants.expoConfig?.extra as
+  | { gitHash?: string; appVariant?: string }
+  | undefined;
+const gitHash = extra?.gitHash ?? "unknown";
+const appVariant = extra?.appVariant ?? "unknown";
+
+// Only the store-distributed staging and production apps talk to the OTA
+// manifest server. The dev tool loads bundles via the dev-launcher deep link
+// and local dev has no manifest server, so setting params there is a no-op
+// at best.
+const enabled = appVariant === "production" || appVariant === "staging";
+
+if (enabled) {
+  (async () => {
+    await Updates.setExtraParamAsync("git-hash", gitHash);
+    await Updates.setExtraParamAsync(
+      "native-version",
+      Application.nativeApplicationVersion ?? null,
+    );
+    await Updates.setExtraParamAsync(
+      "native-build",
+      Application.nativeBuildVersion ?? null,
+    );
+  })().catch((err) => Sentry.captureException(err));
+}