QA clean-install unlock onboarding after setup changes

[zo-sol]

Context

The onboarding flow has changed since the earlier closed setup issues, especially #118, #6, #7, and #23. Chat now opens first, and wallet, cloud backup, and market RPC are handled through the progressive unlock tutorial instead of the old blocking onboarding sequence.

Please verify this from a truly clean mobile install, not from an already-configured test device.

Test setup

1. Delete all AgentNet app data from the device. Prefer uninstalling the app, then reinstalling the latest APK/app version.
2. Install the newest build from main or the latest Android artifact.
3. Launch AgentNet with no preserved wallet, Google Drive, Helius, Claude, Codex, session, or local app state.

Things to verify

1. The app can reach the initial chat shell on a clean install without requiring wallet, Google Drive, or Helius setup first.
2. Connecting only Claude and/or Codex at first-run is enough to pass the initial engine setup path and start using chat.
3. Locked product areas open the new unlock tutorial instead of sending the user back to the old onboarding screens.
4. The unlock tutorial starts from the pitch, then proceeds through app installed, wallet connect, cloud backup, market RPC, and access granted in the intended order.
5. The Cloud Backup step should not ask for a Google OAuth client ID in Android builds where native Google Drive auth is available. It should either show Connect Google Drive, complete if already connected, or let the user skip.
6. If Google Drive is already authorized by Google Play Services, the flow should still transition cleanly after the app records the Drive connection.
7. Market RPC should be clearly optional. A user should be able to continue with the default RPC and should not be blocked by Helius setup.

Report any failures

If any step does not work, please report:

• The exact screen and step where it stopped.
• Whether this was a clean install or a reused device state.
• Whether Google Drive had already been authorized on the Android account.
• Any visible error text, toast, or stuck button label.
• Relevant adb logcat snippets from AgentNet/Server, AgentNet/GoogleToken, and AgentNet/GoogleDrive.

Acceptance criteria

A fresh user can install the new app, connect Claude and/or Codex, reach chat, and later complete or skip the progressive unlock tutorial steps without being blocked by missing Google client IDs, stale Drive state, or mandatory Helius setup.