S7.14 — Settle needs NEAR testnet for nothing; pin the wallet network #157

Question from the human: go through all the NEAR material and check whether any part of Settle needs testnet.

Finding (live, 2026-11-10): no judged path can run on testnet. The hackathon still answers Q-007 "Testnet for Intents? None exists or is planned", and the vendor docs say "There is no testnet deployment and no plans for one. We recommend testing on NEAR mainnet using separate dev/test NEAR accounts."

Per path:

• 1Click quotes/deposits/payouts: mainnet only. The live /v0/tokens has 216 assets; every near entry is a mainnet NEP-141 contract (the only "test" id is a mainnet sub-account, test-token.highdome3013.near).
• NEP-413 sign-in: network-agnostic, but wallet network and NEAR_RPC_URL must agree. Testnet wallet + mainnet RPC would accept alice.testnet as a payout address and 1Click would attempt a mainnet delivery to an account that does not exist.
• Storage check / payer: reads the real USDC contract; a test FT proves nothing.
• Demo mode and dry-run quotes: already the no-funds paths.
• Hosted deploy: real mode, mainnet, no network variable set.
• Prize payout: mainnet account, human-only.

Change: remove the untested NEXT_PUBLIC_NEAR_NETWORK switch; NEAR_NETWORK is the literal "mainnet". Record the decision in ARCHITECTURE §11, ESSENTIALS, README and LAUNCH §1.

Landing note: merged via PR (issues stay open as the roadmap).