Remove 4 explicit `any` across 4 test files

[Omoboi-dev]

Description

npm run lint reports 4 @typescript-eslint/no-explicit-any warnings in the files below:

• test/admin-dispute-resolution.e2e-spec.ts — 1 occurrence
• test/unit/dlq.service.spec.ts — 1 occurrence
• test/unit/stellar-webhook.service.spec.ts — 1 occurrence
• test/unit/tracking-poll.worker.spec.ts — 1 occurrence

any in a test defeats the point of the test: it lets a mock drift out of shape with the real type and still compile, so the suite keeps passing while the thing it mocks has changed. Issue #416 was closed for this and 88 occurrences remain across 15 files, so this is a real remainder rather than a duplicate.

Location

• test/admin-dispute-resolution.e2e-spec.ts
• test/unit/dlq.service.spec.ts
• test/unit/stellar-webhook.service.spec.ts
• test/unit/tracking-poll.worker.spec.ts

Example commits

refactor(tests): replace explicit any with real types in admin-dispute-resolution.e2e-spec.ts

Acceptance Criteria

• No @typescript-eslint/no-explicit-any warnings remain in the listed files.
• Replacements are real types, not unknown casts or eslint-disable comments.
• Mocks are typed with jest.Mocked<T> or an explicit interface so a signature change breaks compilation.
• No new tests required, but every existing test in the listed files must still pass.
• npx tsc --noEmit and npm test both pass.

Technical Notes

jest.Mocked<T> and Partial<T> cover most cases. Where a mock only needs a few methods, type it as an explicit interface rather than casting the whole object.

Out of scope: files not listed above, and changing what the tests assert.

Before you start

Setup, including the Node 22 requirement and the prisma generate step, is in
CONTRIBUTING.md. Authenticated requests in tests
use the bearer() helper in test/auth-helper.ts rather than hand-built
tokens. Branch from dev and open the pull request against dev.

[rajiabdulrahmon2020-ui]

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

I’ve reviewed the issue and have a solid understanding of what needs to be addressed. I’d like to take responsibility for the implementation and ensure the resulting changes are reliable, well-tested, and easy to maintain.

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

[malahk001]

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

Hello Maintainer, I have reviewed the issue and its requirements. I'm ready to take on the task and make a swift, meaningful impact.

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

[NEA-DEV-coder]

@NEA-DEV-coder 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 @NEA-DEV-coder to this issue.

[Ukorstack]

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

I’m ready to handle this issue efficiently and ensure the final PR meets the project standards. Kindly assign it to me.

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

[raihanmd]

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

Hi, I'd like to take this issue.

Problem: 4 explicit any usages remain across admin-dispute-resolution.e2e-spec.ts, dlq.service.spec.ts, stellar-webhook.service.spec.ts, and tracking-poll.worker.spec.ts, each letting a mock silently drift out of sync with the real type it stands in for while the suite keeps passing.

Approach:

1. For each file, identify what the any is standing in for (a mocked service, a request/response object, a worker dependency) and find or define the real corresponding type/interface.
2. Type mocks with jest.Mocked where mocking a full service/class, or an explicit interface when only a few methods are actually used, per the issue's own guidance, avoiding blanket Partial casts that would hide missing methods.
3. Replace each any with the correct typed version, no unknown casts or eslint-disable comments.
4. Confirm each fix actually catches drift: e.g. temporarily change the real type's signature to verify the now-typed mock fails to compile, then revert, so I know the fix is doing its job and not just cosmetic.
5. Run npx tsc --noEmit and npm test to confirm everything still passes with no new type errors, using the bearer() helper from test/auth-helper.ts for any authenticated request in the e2e spec, per CONTRIBUTING.md.
6. Branch from dev, open PR against dev.

Why me: Backend engineer, 2+ years TypeScript, comfortable making mock types actually enforce contract correctness rather than just silencing lint warnings.

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

[Smartdevs17]

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

can I work on this?

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @Smartdevs17 as part of the Stellar Wave Program's 8th Wave 🥳

😎 @Smartdevs17: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.