test: add tests for NetworkMismatchBanner dismissal persistence

[misrasamuelisiguzor-oss]

Description

NetworkMismatchBanner warns when the wallet's network doesn't match the app's selected network. It's unclear whether dismissing the banner persists across a page reload or reappears immediately, which could be annoying if a user has a legitimate reason to stay mismatched temporarily.

This is part of the admin/governance dashboard under frontend/, used by signers, compliance officers, and protocol operators to manage settlements, disputes, thresholds, and compliance status rather than by end payers. Because the people using this surface are making decisions with real financial and compliance consequences (approving a settlement, voting on a dispute, rotating a signer), the bar for clarity and correctness here is arguably higher than on the consumer-facing app, since a confusing admin UI can lead directly to an operational mistake rather than just a frustrated user.

This dashboard is also the primary place multi-sig governance actually happens day to day; a signer who cannot clearly see quorum status, dispute state, or settlement history from this UI is forced to fall back on reading raw contract state or asking a teammate, which slows down exactly the kind of time-sensitive decisions (an on-hold settlement, an active dispute) that a governance dashboard exists to speed up.

Requirements and context

• Add a test for dismiss behavior and whether it persists via useNetwork's storage key

Suggested execution

1. Fork the repo and create a branch

   git checkout -b test/network-mismatch-banner-dismiss
   

2. Implement changes

• Update frontend/src/components/NetworkMismatchBanner.tsx if dismissal isn't persisted
• Add the test

3. Test and commit

• Run npm test

Example commit message

test: add dismissal-persistence test to NetworkMismatchBanner

Guidelines

• Assignment required before starting
• PR description must include: Closes #[issue_id]
• Keep PR description professional and detailed

[idrisososanwo]

@idrisososanwo has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @idrisososanwo to this issue.

[northvictor]

@northvictor has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer, can I be assigned to this issue please? ETA is less than 48hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @northvictor to this issue.

[Yemmy88]

@Yemmy88 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, Maintainer,

I’d be glad to contribute to this issue because it improves the clarity and usability of an important governance dashboard. I’d love to add the dismissal-persistence test and ensure the banner behaves reliably. I would be glad if you assigned this issue to me. Thank you for considering my application.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Yemmy88 to this issue.

[NancieDev]

@NancieDev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @NancieDev to this issue.

[drips-wave]

Congratulations, @NancieDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @NancieDev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊