Add test coverage for connecting a wallet while already connected in useWallet

[Jagadeeshftw]

📌 Description

useWallet (src/hooks/useWallet.ts) wraps the mock wallet connect flow, persisting the account via saveAccount/loadAccount (src/lib/wallet.ts) to localStorage per the README. It's unclear whether calling connect again while already connected is a safe no-op or silently overwrites the persisted account with a freshly generated mock address, which would be surprising if the "connect" button is clickable while already connected.

🧩 Requirements and context

• Add a test: connect once, capture the resulting account, call connect again, and assert the account is unchanged (no-op) rather than replaced.
• If a fresh reconnect should generate a new mock address (e.g. simulating a wallet switch), that's a valid design choice too — pick one behavior deliberately and test it, rather than leaving it as accidental.
• Ensure ConnectButton (src/components/ConnectButton.tsx) doesn't present a confusing "Connect" affordance while already connected (should show a connected state per its existing tests).

🛠️ Suggested execution

• Add the double-connect test to src/hooks/useWallet.test.ts.
• Fix useWallet.ts/lib/wallet.ts if the behavior is found to be unintentional.

✅ Acceptance criteria

• Double-connect behavior is explicit and tested.
• ConnectButton's UI state is consistent with the decided behavior.

🔒 Security notes

No new attack surface; this is a mock wallet flow, but the same account-persistence pattern would matter for a real wallet integration later.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Glam26]

Hi team, I’d love to take this on!

I am a software engineer focused on building predictable systems, writing clean code, and uncovering subtle edge cases. I'm ready to dive into these requirements and deliver a highly secure, reliable solution.

I will deliver:

• Defensive Implementation: Build out the core logic using explicit type safety and strict validation boundaries to neutralize potential runtime errors or logical oversights.
• State & Schema Alignment: Update the underlying data schemas, backend logic, and API contracts symmetrically to prevent data fragmentation or desynchronization across layers.
• Component Optimization: Refactor or introduce relevant interface blocks to handle loading states, success frames, and recovery triggers gracefully.
• Bulletproof Test Coverage: Author comprehensive regression and property-based tests within our existing framework to guarantee long-term maintenance safety in CI.

Ready for assignment to drop a complete, robust PR immediately!

[Binali223]

Hello team,
I'd like to take on this task and feel free to assign it to me.
Looking forward to getting started!

[grantfox-oss]

🦊 GrantFox — @Binali223 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #73)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🦊 GrantFox — @Binali223 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #73)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.