frontend: npm run lint fails on main — 39 lint errors in 3 recently-added test files, breaking Frontend CI

[gboigwe]

Summary

npm run lint currently fails with 39 errors (40 problems total) across 3 test files, meaning Frontend CI (a required auto-merge status check) is red on main right now.

Location

frontend/src/hooks/useTxNotifications.test.tsx, frontend/src/lib/tx-recovery.test.ts, frontend/src/lib/wallet.test.ts

Problem

These test files (added in earlier test-coverage fixes) use any extensively for mock typing, tripping @typescript-eslint/no-explicit-any dozens of times, plus at least one other lint rule. npm run lint currently exits non-zero.

Impact

Critical: Frontend CI failing on main blocks the whole CI-gated auto-merge premise for any PR depending on a clean baseline, and it's easy to miss since npm run typecheck and npm test can both pass while lint fails separately.

Acceptance Criteria

• npm run lint passes with zero errors in frontend/
• The fix replaces any with proper types (or narrowly-scoped unknown/generic mock types) rather than blanket-disabling the lint rule for these files
• npm test still passes after the type changes (verify mocks still behave correctly)

Suggested Approach

Go file by file — wallet.test.ts and tx-recovery.test.ts first (fewer errors likely), then useTxNotifications.test.tsx. Most fixes will be replacing any mock parameter/return types with the actual types being mocked.

[Nemenwq]

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

Hi maintainer, can you assign me this please? ETA: 5HOURS

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

[Devadakene]

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

I am experienced enough to implement this issue having worked on similar issues in the past. Please assign

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

[umohmila47-source]

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

Hi maintainer, I’d like to work on this issue. I have experience with TypeScript, React, frontend testing, ESLint, and strongly typed mocks. I can clean up the test files by replacing unsafe any usage with appropriate types, while preserving test behavior and getting the frontend lint and test suites back to a clean state. Please assign me to this work.

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

[iamcracked-dev]

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

Hi maintainers!
I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

[drips-wave]

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

🧑‍💻 @iamcracked-dev: 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 🌊