docs(wallets): add end-user troubleshooting for common unanswered assistant questions

[GigaHierz]

Refs #2314, #2320, #2324, #2343

Each weekly assistant report lists readers' questions that returned no citation. The recurring in-scope ones were wallet and funds basics: connecting MetaMask, finding an address, signing in, tokens not showing, moving money in or out.

What changed

• home/wallets.mdx: new ## Troubleshooting (five short entries, each linking an existing page) and ## Related; description rewritten to use the words readers ask with. No new addresses, numbers or availability claims.
• Edited in place, so no page moves (story: Split wallet docs into an end-user page and a developer wallet-integration page #2256 will split this page later; this keeps the edit small).

Deliberately not written (need an owner's input)

• Country availability (e.g. "can I use it in Nigeria"): needs a statement from the wallet/ramp owners; the page only says availability depends on the provider.
• Official partnership contact/form, and whether any rewards/points program exists.
• Questions about a specific "relayer" or third-party tokens: ambiguous or not Celo docs.
• Probe/injection and off-topic questions: no doc change.

Verification

$ mint broken-links
success no broken links found
$ bash scripts/check-orphans.sh
No orphan pages found.

🤖 Generated with Claude Code

[palango]

Good scope: the questions picked are the ones readers keep asking, and leaving availability, partnerships and rewards out is the right call. All internal links resolve, and the description and section order follow AGENTS.md.

Two entries send readers to the wrong place, though, and I'd fix those before merge (inline comments). The recovery one matters most because of the scam risk. The other two inline comments are smaller.

One thing I couldn't check: whether current MetaMask builds already list Celo among their built-in networks. If they do, "MetaMask does not show Celo until the network is added" needs softening.

[palango]

This is wrong for every wallet on this page, and the wording is risky. They are all non-custodial: whoever holds the recovery phrase or private key controls the wallet, not the app. If the phrase is lost, the wallet's support team can't recover the funds either. Telling stuck users to "contact support" is how the fake-support scam usually starts.

Suggested direction:

Celo has no usernames or passwords. A wallet is controlled by its recovery phrase (seed phrase) or private key. To restore a wallet, import the recovery phrase into a wallet app. Without it, no one can recover the funds: not Celo, and not the wallet's maker. Never share your recovery phrase with anyone, including people who say they are support.

("No accounts" is also loose, since an address is an account, so I'd say "usernames or passwords" instead.)

[palango]

/home/manage/self-custody doesn't match this description. It is a Celo CLI + Ledger guide for ReleaseGold beneficiaries who gave their address to cLabs. It doesn't explain how to keep control of your own funds. I'd drop this bullet.

[palango]

/tooling/wallets/metamask/setup is the developer page ("Programmatic Setup", a wallet_addEthereumChain JS snippet). An end user is better served by the one-click AddNetworkButton on /build-on-celo/network-overview, or you could embed it here as home/celo.mdx does (import { AddNetworkButton } from '/snippets/AddNetworkButton.jsx'). The mislabel came from tooling/wallets/metamask/use.mdx, which lists the same page under "For end users". That one is a separate fix.

[palango]

The stablecoin contracts table puts mainnet and Celo Sepolia addresses side by side, so a reader can easily copy the testnet one. Worth adding "use the Celo Mainnet column".