Clean up ESLint errors (frontend 77, backend 17) so CI lint gates can be enforced

[feyishola]

Context

When reviewing PR #898 (which tried to add npm run lint steps to CI), we found eslint --max-warnings 0 currently fails on the existing codebase, so the lint gates were deferred to keep CI green. This issue tracks clearing that lint debt so the gates can be re-added.

Reproduce:

(cd frontend && npm run lint)   # ✖ 77 problems (77 errors)
(cd backend && npm run lint)    # 17 errors

Frontend — 77 errors

Count	Rule	Notes
72	react-refresh/only-export-components	Files export both a component and non-component values (common in context/provider/util files). Either split non-component exports into separate modules, or scope/relax this rule for those files (it is an HMR-only concern).
5	react/no-unescaped-entities	Unescaped '/" in JSX text — replace with '/" or wrap in {'...'}.

Backend — 17 errors

Includes:

• @typescript-eslint/require-await (×4) — async functions with no await; drop async or add the awaited call.
• no-useless-escape (×3) — remove unnecessary escapes in regex/strings.
• @typescript-eslint/no-misused-promises (×2) — promises passed where a void-returning callback is expected; wrap/await appropriately.
• plus a few others (run the command above for the full list).

Definition of done

1. cd frontend && npm run lint and cd backend && npm run lint both pass with --max-warnings 0.
2. Re-add the Lint frontend / Lint backend steps to .github/workflows/ci.yml (the frontend and backend jobs) — these were intentionally left out of fix(ci): fix cache-dependency-paths and add lint and typecheck steps #898.

Note: the frontend react-refresh/only-export-components count is large but mostly mechanical / a lint-config decision; consider tackling it separately from the handful of genuine code fixes.

[CITYZEN-AL-MUSTAPHA]

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

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CITYZEN-AL-MUSTAPHA to this issue.

[oyeyemi01]

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

Hello, I’ve reviewed the issue and it aligns well with my skills and experience. I’m confident I can implement the required solution effectively. Please assign it to me.

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

[Niffy03]

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

Hi there, I'd like to work on this.

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

[attyolu]

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

Please Maintainer. Few hours left and i just have 150 points. Pls assign this issue to me. I'm begging

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

[solaawojobi00-bit]

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

I’ll take this on. In Servora/StellarCert, the CI lint gates (npm run lint with --max-warnings 0) are currently disabled because the codebase has accumulated 94 ESLint errors (77 in frontend and 17 in backend), blocking automated lint enforcement on pull requests.
I will implement:

• Frontend Lint Cleanup: Resolve all 77 ESLint errors in frontend/ (fixing unused imports, missing hook dependencies, improper type definitions, and formatting issues).
• Backend Lint Cleanup: Fix all 17 ESLint errors in backend/ (addressing strict type casting, explicit returns, unused parameters, and unhandled promises).
• CI Gate Enforcement: Re-enable or update the npm run lint check with zero allowed warnings (--max-warnings 0) in .github/workflows/ci.yml so all future PRs automatically enforce linting rules.
• Verification: Run npm run lint across both frontend/ and backend/ packages locally to guarantee clean output before re-enabling the CI check. Kindly assign it to me.

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

[Muyideen-js]

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

Hi, I can fix this

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

[CollinsKRO]

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

Hi, I can fix this

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

[drips-wave]

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

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