[Production MVP][P1] Validate injected wallet support on public wallets/devices

[knzeng-e]

Goal

Add production-grade injected EVM wallet support so external artists and listeners can use Dotify without dev-account signing.

Context

Dotify is not production-ready while public flows depend on demo/dev signing. The public MVP requires real wallet ownership for artist runtime creation, track registration, Classic unlock payments, and access checks.

Scope

• Add injected EVM wallet connection for public users.
• Detect Paseo Asset Hub EVM / chainId 420420417.
• Prompt users to switch or add the target chain when needed.
• Replace any dev-account fallback in public flows.
• Support artist runtime creation from the connected wallet.
• Support Classic unlock payment from the connected listener wallet.
• Display connected account, chain status, and actionable wallet errors.

Acceptance criteria

• External artist can connect a wallet and create a personal SmartRuntime.
• External artist can register a track from their own wallet.
• External listener can connect a wallet and pay for Classic access.
• Public flows do not silently fall back to a dev account.
• Wrong-chain and disconnected states are visible and recoverable.

Engineering bar

This is the sovereignty gate. If the wallet boundary is fake, artist-owned runtimes are theater.

[knzeng-e]

Backlog sync 2026-07-14: keep this open only for missing public injected-wallet evidence and wallet/device validation. Wallet support already has substantial delivered slices on main; avoid duplicating Product SDK/Host work from #85 or production env guards from #37.

[knzeng-e]

Project 5 triage 2026-07-17: narrowed this issue to public wallet/device validation evidence, not a blank implementation task. Current main already includes injected EVM wallet support via window.ethereum, eth_requestAccounts / eth_accounts restore, wallet_switchEthereumChain + wallet_addEthereumChain, accountsChanged / chainChanged / disconnect listeners, wrong-chain UI, and no public dev-account fallback outside explicit e2e modes. Remaining evidence to close this issue: validate MetaMask / Talisman EVM / SubWallet EVM where available on the public deploy, capture artist runtime/profile flow, Classic unlock payment flow, wrong-chain recovery, account-change handling, and disconnected/error states.

[knzeng-e]

wrong chain recovery validated

[knzeng-e]

Closing as completed after public validation evidence was attached on 2026-07-17. The remaining issue scope had already been narrowed to public injected-wallet/device validation evidence; manual validation now covers the EVM injected-wallet/deployment path, SmartRuntime publish flow, and wrong-chain detection/recovery. Evidence: #33 (comment)