Enable TypeScript no-explicit-any ESLint rule across the codebase

[robertocarlous]

Summary

@typescript-eslint/no-explicit-any is currently disabled in eslint.config.mjs. This allows silent type escapes that can mask bugs at the Stellar and agent boundaries.

Plan

1. Re-enable the rule in eslint.config.mjs
2. Run npx eslint src/ --rule '{"@typescript-eslint/no-explicit-any": "error"}' to enumerate violations
3. Fix each violation by:
   • Introducing a proper type/interface
   • Using unknown + a type guard where the value is truly unknown
   • Using Parameters<typeof fn>[0] to derive types from existing signatures
4. Do NOT use // eslint-disable-next-line as a workaround

Acceptance Criteria

• Rule enabled at error level in eslint.config.mjs
• npm run lint passes with zero any violations
• No eslint-disable comments introduced to suppress the rule

[oyinade247]

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

I would like to fix this ASAP

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

[drips-wave]

Congratulations, @oyinade247! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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