[Frontend] — Connect Wallet Modal Error and Retry States

[Olowodarey]

Problem
ConnectWalletModal assumes a happy path; when a wallet extension is missing or rejects the request, the modal gives no actionable feedback.

Requirements

• Detect missing extension and link to install instructions.
• Distinct messaging for user-rejected vs. timeout vs. network errors.
• Retry button that re-attempts the last connection method.
• Tests: each error branch renders the correct message and retry affordance.

Acceptance Criteria

• Users get a clear reason and a retry path for every failure. Covered by tests.

Files

• frontend/src/component/ConnectWalletModal.tsx
• frontend/src/context/WalletContext.tsx
• frontend/src/hooks/useHookErrorMessage.ts

[bilhokista]

I have opened #1797 for this issue.

The modal turned out to be further along than the issue suggests: detecting a missing extension, linking to the install page, and a Retry button that re-attempts the last selected wallet were all already in place. I left those alone. What I found instead were two defects and one gap.

A declined request showed nothing at all. user_rejected was declared in the ErrorType union but never assigned — the rejection branch called resetModal() and returned, dropping the user back at the wallet list with no message. Pressing Cancel in the extension was indistinguishable from a misclick. It is now a first-class state, worded as a choice rather than a fault.

Connectivity failures were reported as the wrong Stellar network. The rule was msg.includes("network") || msg.includes("testnet") || msg.includes("public"), and "Network request failed", "NetworkError when attempting to fetch" and net::ERR_INTERNET_DISCONNECTED all contain "network" — so a user whose connection was down was told to switch chains. The wrong-network rule now requires a chain-specific token and never bare "network", and real connectivity failures are matched first with their own message.

No timeout. If the extension never answered, fetchAddress() hung and the modal sat on "connecting" with no escape but closing it. There is now a 30s race that surfaces as its own state suggesting the user check for a pending prompt in the extension.

Classification moved into a pure frontend/src/lib/wallet-errors.ts returning { type, title, message, hint, canRetry }, so each branch is testable directly. canRetry is false only for a missing extension, where the panel offers the install link rather than a button that cannot succeed.

One scope note: WalletContext.tsx and useHookErrorMessage.ts are in the issue's file list but did not need changes — the failure surfaces entirely inside the modal, and useHookErrorMessage is a logging helper for hooks rather than a classifier. I left them untouched rather than editing them just to match the list.