[arzvaak]

Pairs Mobile with the existing Desktop sidecar through https://tunnel.bharatcode.ai, using matching-code approval and a separate revocable credential per phone.

Fixes native pairing intents, cold launcher routing, reconnect behavior and long-reply rendering. The physical-camera failure came from R8 removing ML Kit registrar constructors in expo-camera 58.0.12; The release uses 58.0.14, which retains the upstream 58.0.13 fix, with the current compatible Expo SDK 58 patch set and release optimization enabled. The mirrored Desktop integration also isolates storage failures, cancels pending pairing safely and preserves the QR clear border.

Verification:

• TypeScript, ESLint, 76 Mobile tests, 15 security tests, 52 connector tests and five generator/browser-helper tests passed. Expo compatibility and the high-severity audit gate pass; the audit retains 15 low-severity dependency findings.
• Physical OnePlus / Android 17: the user scanned the Desktop QR, checked and approved the matching code, and confirmed real Desktop conversations loaded. This used the optimized diagnostic QA APK, not a store-signed build.
• Earlier runtime qualification covers real streamed replies, network recovery, restart persistence and revocation; it is recorded separately from the latest camera test.

Current verification. No new tunnel-service deployment or one-time-code service flow is included.

Companion Desktop PR: BharatCode-ai/bharatcode-desktop#60

[shrey16]

Cross-repository reconciliation with Desktop PR60: mobile checks passed (76 Jest, 15 security, TypeScript and lint; connector 52 tests). Shared Desktop connector recovery still needs a fix: a corrupt admissions.json blocks pairing, while reset reports success without resolving it. Coordinate the fix with Desktop PR60 and preserve ambiguous-delivery protection rather than discarding the journal. No production or release changes made in this review.