QA: verify Android build after targetSdk 35 update (#110)

[zo-sol]

What changed

The public Android build was updated in #110 (with the earlier #109). Net effect now live in app-debug.apk:

• targetSdk 28 -> 35 (single variant now; the legacy flavor is gone). The guest still runs under proot. Validated on Seeker (Android 16 + pointer tagging), but we need coverage on other devices/vendors.
• claude launch fix: a rootfs hardlink was being turned into a host-absolute symlink that dangled inside the guest, so claude failed with spawn ENOENT. It now resolves to the real binary.
• Install marker bumped (v2 -> v3): the first launch after updating re-extracts the rootfs once (~1 GB, a few minutes). This is expected and one-time.
• appId + signing unchanged -> installing over an existing build is an in-place update (no data wipe).

Build

• APK: https://github.com/IQCoreTeam/AgentNet/releases/download/android-latest/app-debug.apk
• PR: Adopt targetSdk 35 as standard + Play release AAB pipeline #110

QA checklist (please test on your device)

A. Update over an existing install

• Installs over the previous version with no data-wipe / uninstall prompt
• First launch re-extracts the rootfs (may take a few min) and completes without error
• Server boots — WebView reaches the app UI (localhost HTTP 200)
• claude responds (this was broken before the update)
• codex responds
• Wallet connect screen reachable / MWA sign works
• Google Drive login works
• Nothing behaves differently vs the previous build

B. Fresh install (uninstall first, then install)

• Full install + rootfs extraction completes
• All checks above pass

On any failure, please report

• Device model + Android version
• Which step failed and what you saw on screen
• adb logcat | grep -iE "avc|AgentNet" around the failure

Context: this is the targetSdk 35 cross-vendor check — your device is exactly the coverage we need beyond Seeker.