[WAL-1346] feat(wallet): add proximity presentation to wallet demos

[szijpeter]

Summary

This integrates holder-side proximity presentation into all three mobile wallet demos for WAL-1346: Compose Android, Compose iOS, and native SwiftUI. Each app gets a dedicated in-person entry below the existing online presentation action and keeps the complete journey inside the familiar Present-tab wallet shell.

This PR is stacked on the Wallet SDK contract in walt-id/waltid-identity#2159. The lower mobile BLE transport is provided by walt-id/waltid-identity#2157, the governing architecture is documented in walt-id/waltid-architecture#60, and exact-build physical evidence and the public ISO holder-test plan are tracked in WAL-1349 architecture PR #61.

This PR contains the complete reader-trust delta formerly carried by #2167, plus the Settings/public-file-import path across Compose Android, Compose iOS, and native SwiftUI. #2167 was closed as superseded after 4/4 exact transplant proof and is not a separate merge unit.

What Changed

Shared Compose journey

• Adds one shared Android/iOS controller and screen set for prerequisites, Device Engagement QR, connection progress, request review, holder choices, repeated requests, terminal states, cancellation, and recovery.
• Preflights the exact selected SDK configuration before session creation, executes runtime-permission remediation, rechecks after every host result, and blocks startup instead of silently falling back around a missing permission. On Android, permissions that the OS will no longer prompt for become an explicit Open app settings action; returning from Settings triggers a fresh capability check before session creation.
• Embeds QR, connection, review, and result states under the normal wallet toolbar and status message instead of replacing the host screen.
• Reuses the existing credential art, human-readable credential and claim labels, metadata sections, and review action layout so online and in-person presentation remain visually aligned.
• Renders the exact Wallet SDK review, including reader-authentication scope, signature validity, certificate path, revocation, optional RICAL evidence, product trust, asserted purpose, and retention intent.
• Renders reader information as an honest collapsed summary with expandable authentication/trust evidence when the request provides it; unsigned requests do not invent a reader identity or logo.
• Supports per-document credential alternatives and exact element disclosure choices, resetting consent for every repeated exchange.

Reader-trust configuration ownership

• Owns the cross-platform Settings surface for Reader CA anchors and optional RICAL trust sources, with add, inspect, remove, reset, and explicit session-snapshot behavior.
• Imports only public DER/PEM certificate material and a versioned walt.id trust-bundle format after validation and fingerprint preview; PKCS#12/PFX and private reader keys are rejected.
• Keeps trust material app-private and avoids logs, bundled production roots, or implicit network trust.

Platform integration

• Keeps runtime permission requests, Bluetooth settings actions, lifecycle interruption, keep-awake, temporary QR brightness, and platform accessibility behind Android and iOS host boundaries.
• Keeps the complete journey inside each host's Present-tab safe area and makes the native SwiftUI parent observe the child session directly, with one start owner and deterministic dismissal/restart behavior.
• Reuses the shared native iOS review components while keeping the SwiftUI journey a thin renderer over the Swift Wallet SDK session rather than reconstructing protocol state.
• Cancels the typed SDK session when the holder leaves the Present tab and restores screen policy on backgrounding, every terminal path, dismissal, wallet locking, and wallet reset.

QR, accessibility, and app wiring

• Pins the minimum proximity-only renderer dependencies directly in this PR: ZXing Java 3.5.4 on Android and ZXing-C++ 3.1.1 on Compose iOS and native SwiftUI.
• Accepts only bounded ASCII mdoc: Device Engagement text, uses low error correction with no ECI, fails closed instead of truncating oversized input, pins the Compose iOS/native SwiftUI module fingerprint, and renders an exact four-module quiet zone using whole physical-pixel modules.
• Uses a package-private Objective-C++ adapter in the native SwiftUI demo with a narrow proximity-only entry point because the pinned Swift wrapper does not expose no-ECI ASCII encoding; the adapter adds no second QR implementation or public module.
• Adds aligned cross-platform accessibility identifiers, privacy-safe QR labels, localization-ready shared strings, and focused controller/UI/view-model fixtures, including native presentation lifecycle and cross-tab layout regressions.
• Documents the supported journey, automatic permission preflight, and qualification boundary in both demo READMEs.

Architecture Notes

• Protocol state, trust, request meaning, legal actions, disclosure validation, and capability/remediation reporting remain owned by the Wallet SDK. Demo code owns holder UI choices and execution of platform actions such as permission prompts.
• Compose Android and Compose iOS share the journey semantics and rendering. Native SwiftUI shares the SDK contract, review primitives, and test identifiers while remaining platform-idiomatic.
• The normal UI does not expose BLE roles, UUIDs, transport internals, or protocol-version controls.
• QR encoding remains a demo-host concern outside the public Wallet SDK; the shared behavior is explicit without introducing a new published KMP module.

Caveats and Follow-Ups

• This proves the wallet-side app integration; it does not claim a qualified external-reader matrix, ISO conformance, or release readiness.
• On frozen pre-final-restack [WAL-1348] feat(mdoc): implement Wi-Fi Aware retrieval #2168 ae4efeb2dfaf60fa7daaab80db4415c4a63c57b0, the Android API 35 denial/settings/return recovery, Compose Android/Compose iOS/native SwiftUI QR-to-BLE canaries, and Android QR-to-NFC hybrid canary passed. The hybrid case proves NFC/HCE engagement and handover followed by BLE GATT retrieval, not direct-NFC retrieval. These results complete the bounded dependency-renderer smoke for that frozen build only; exact-head physical replay and broader qualification tracked by WAL-1349 architecture PR #61 remain open.
• The stack was refreshed parent first from Identity main 4d151a1bf43c45072d931f00f8418d50de20813c: [WAL-1344] feat(mdoc): add shared proximity protocol engine #2155 targets main and each child targets its immediate predecessor. This PR is 6407f3eb7928847770752463c98f68de5e216fe3; accumulated [WAL-1348] feat(mdoc): implement Wi-Fi Aware retrieval #2168 is c8226699039ec51b0eb4caf36cadccfd0c18b26b on current [WAL-1347] feat(wallet): integrate NFC proximity in demos #2166 571c0b9d8f308a8fa86a35b3d909be668020753a. Closed WAL-1376 PR [WAL-1376] feat(wallet): add full-screen image viewing and render QR claims #2176 is not a dependency.
• The public Appendix 2 baseline in WAL-1349 architecture PR #61 accounts for all 460 holder cases as 288 automated rows, 24 physical rows, and 148 explicit gaps. The 24 physical rows are consolidated into five reusable scenarios; cross-device and release qualification remain owned by WAL-1349.

Breaking

• No released API or persisted wallet data is migrated. The mobile demos consume the new unreleased SDK contract directly.

[linear-code]

WAL-1346

WAL-1376

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 678eb97a-f7d3-4ea9-88bd-95d5c0d7cd65

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud