[Magrexy]

Summary

Adds an error boundary around the WalletConnection component so an unexpected render failure in the wallet status UI degrades into a friendly, retryable fallback instead of unmounting the header that hosts it. This keeps the surrounding page usable when wallet state or a browser wallet provider misbehaves.

Problem

WalletConnector renders the connected and disconnected wallet views directly with no error boundary. Any exception thrown while rendering those views propagates upward and takes the whole layout down with it, leaving users without wallet controls and with no way to recover short of reloading the page.

Changes Made

• Wrapped the render output of src/components/WalletConnector.tsx in the existing ErrorBoundary component from src/components/ui/SimpleErrorBoundary.tsx.
• Kept the connected/disconnected branching logic unchanged; the boundary now covers both states.

Implementation Details

The existing ErrorBoundary already supplies a fallback panel with a "Try Again" button that resets its internal hasError state, so no new error handling code was introduced. Since ErrorBoundary is a client component, it composes cleanly inside the client-side WalletConnector, and the boundary sits high enough to catch failures from either view without altering their props.

Closes #1158

Closes #1157

Closes #1156

Closes #1155

[drips-wave]

@Magrexy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[nanaf6203-bit]

LGTM