Improve frontend TypeScript types (replace `any`)

[sanmaxdev]

Background

The frontend has a number of @typescript-eslint/no-explicit-any warnings (run npm run lint in frontend/). Replacing any with real types improves safety and editor autocomplete. This is a great first contribution and can be done one file at a time.

Tasks

• Pick a file with any warnings (e.g. under frontend/lib/services/)
• Define proper interfaces/types for the API responses
• Confirm npm run lint shows fewer warnings and npm run build still passes

Acceptance criteria

• No new lint errors, build succeeds
• Scope each PR to one area so it is easy to review

Comment to claim a file so we do not overlap. See CONTRIBUTING.md.

[Brownteen18]

Hi!
I'd love to help clean up these TypeScript warnings.
I'll pick 'frontend/lib/services/api.ts' (or replace with the specific file you see in the repo) to define proper type interfaces and eliminate the explicit 'any' warnings there.
Please assign this area to me!

[sanmaxdev]

Thanks for jumping in! 🙌

Assigned this to you. Starting with the frontend service types is a good scope. Please keep the PR focused on replacing explicit any types with clear interfaces/types, and avoid unrelated formatting changes so it stays easy to review.