Waseel: driver capture, chat/calls, dispatch, and session fixes

Driver onboarding now photographs the licence, ID card and vehicle
registration and reads the credential fields off them, plus a camera-only
profile selfie riders check the arriving driver against. Adds in-app chat
and WebRTC calls, push-backed ride offers, ratings, cancellation and
payment sheets, settlement, and the owner dashboard endpoints behind them.

Camera permission on Android:
  - Declare CAMERA and READ_MEDIA_IMAGES in the manifest. expo-image-picker's
    own plugin never declares CAMERA, and Android denies a request for an
    undeclared permission instantly and silently — no dialog is ever shown,
    which is indistinguishable from the app not asking at all.
  - Handle canAskAgain: once Android stops showing the dialog, repeating why
    we need it is a dead end, so offer Open Settings instead (lib/capture-
    permission.ts), matching what the location flow already did.

Session: a 401 on a request that carried a token now ends the session
instead of being reinterpreted per-screen — driver-home had been reading it
as "this user has no driver profile" and showing an onboarding form to an
already-onboarded driver. Requests without a token are exempt so a failed
sign-in doesn't sign you out, and the notification is latched per token so
concurrent polls tear the session down once. (root) gains the auth guard
that turns that into the sign-in screen; app/index.tsx only guarded the way
in, leaving a session that ended mid-screen with nowhere to go.

Also ignore .uploads/ — it holds driver licence, ID and vehicle scans plus
profile photos, which are personal data and must not be committed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

lib/session.tsx

@@ -9,9 +9,11 @@ import {
   type ReactNode,
 } from "react";
 
-import { setAuthToken, clearAuthToken } from "./fetch";
+import { setAuthToken, clearAuthToken, setUnauthorizedHandler } from "./fetch";
+import { stopBackgroundTracking } from "./location-task";
+import { releaseCurrentPush } from "./notifications";
+import { TOKEN_KEY } from "./token-store";
 
-const TOKEN_KEY = "waseel_auth_token";
 const USER_KEY = "waseel_auth_user";
 const REMEMBERED_EMAIL_KEY = "waseel_remembered_email";
 const DEFAULT_TOKEN_TTL_SECONDS = 30 * 24 * 60 * 60;
@@ -171,6 +173,17 @@ export const SessionProvider = ({ children }: { children: ReactNode }) => {
   );
 
   const signOut = useCallback(async () => {
+    // Hand the device back before the token goes away — the release call needs
+    // to authenticate as the account that currently holds it. Phones get
+    // shared, and without this the previous account keeps receiving ride
+    // offers on a phone someone else is now signed in on.
+    await releaseCurrentPush();
+
+    // A driver who signs out is off shift: tear down the location foreground
+    // service too, or they're left with a "you're online" notification and a
+    // GPS drain for a session that has ended.
+    await stopBackgroundTracking();
+
     clearAuthToken();
     setUser(null);
 
@@ -178,6 +191,18 @@ export const SessionProvider = ({ children }: { children: ReactNode }) => {
     await SecureStore.deleteItemAsync(USER_KEY);
   }, []);
 
+  // The other half of the bargain struck in restore(): a token we cannot prove
+  // is expired stays in use until the server rejects it, and this is what
+  // happens when it does. Without it the app kept the dead token and every
+  // screen behind the session had to invent its own meaning for the resulting
+  // 401 — driver-home read it as "this user has no driver profile" and showed
+  // an onboarding form to a driver who had finished onboarding weeks ago.
+  useEffect(() => {
+    setUnauthorizedHandler(() => void signOut());
+
+    return () => setUnauthorizedHandler(null);
+  }, [signOut]);
+
   const value = useMemo<SessionContextValue>(
     () => ({
       isLoaded,