Subdomain deployment, separate product surface

It is not inside my.fva70k.com. It is not inside bot.fva70k.com.

Anonymous Wallet alone lives on wallet.fva70k.com.

FVA70K own wallet is not moved to a subdomain.

One person can have as many wallets as they want.

This does not set any key.

This does not authorize a live push yet.

Does not authorize a live push yet.

Does not set any key.

Not inside my.fva70k.com. Not inside bot.fva70k.com.

Staff work stays in their Portal. This wallet does not replace Portal desk work.

Push ready checklist, fva-anonymous-wallet

Repo was empty at first push.

Muse GitHub App allowed on it.

Repo: fva-anonymous-wallet, under FVA70K-SERVICES, private, main branch. Repo created by the owner. No push in this job.

Android download

Not available yet.

Multiple wallets

As many wallets as they want.

Deployment checklist, in order

1. Step 1: Confirm the live repo name and live repo HEAD. No push starts until both are confirmed.
2. Step 2: Create or confirm the live repo and Pages project for wallet.fva70k.com.
3. Step 3: Push the app files with fresh HEAD re-derivation and byte-by-byte re-fetch, one repo at a time.
4. Step 4: Re-fetch every pushed file and compare it byte by byte. Stop and report any mismatch.
5. Step 5: Add key slots in the secure dashboard or Secure Vault only, crypto first, then other payment slots.
6. Step 6: Verify test mode refusal when a key slot is empty, with no live payment or transfer running.
7. Step 7: Verify provider connections in test mode only, with test accounts and testnet only.
8. Step 8: Run the live check in a live browser task, with test accounts only, at 375px and desktop.
9. Step 9: Mainnet only after step 8 passes, by owner decision only.