Android's Score Home card now requests /score/open through the same single-use authenticated handoff. The server selects the guardian Score editor for an account with owned participants, otherwise the read-only /me/score recipient view when an accepted participant link exists. New users still reach the ordinary Score workspace. The selected destination never grants extra rights or carries an embedded credential.
After normal Android account sign-in, ToolsAPI returns a dedicated mobile_web_token when sync_mobile_web_token=true is requested. Android encrypts this owner-bound credential using Android Keystore and never persists the account JWT.
Before opening a first-party Tools WebView, Android POSTs to /api/mobile/web-session/handoff with Authorization: Bearer <mobile_web_token> and JSON {"path":"/score"} (or another allowlisted first-party path). The response contains url, a 120-second single-use URL. The WebView opens that URL; ToolsAPI atomically consumes the SHA-256-hashed secret, regenerates a Laravel web session for the owner, and redirects to the destination. Existing web permissions and CSRF remain in effect. Sign-out clears the encrypted credential and WebView cookies.
The endpoint rejects missing, invalid, inactive or incorrectly scoped credentials and destinations outside the allowlist. A previously linked Android installation must sign in again to provision the additional credential. The dedicated credential grants no general API permissions.