Code Quality: Address minor gemini-code-assist suggestions (7 PRs)

[jmanhype]

Context

Gemini-code-assist reviews identified minor improvements across 7 PRs. These are low-priority code quality enhancements, not bugs.

Minor Issues to Address

1. PR #279 - ESLint Migration

File: frontend/eslint.config.js
Issue: Prettier configuration placement may not function as intended
Severity: Low (Configuration)

2. PR #271 - TypeScript Strict Null Checks

Issue: One minor cleanup suggestion
Severity: Low (Code Quality)

3. PR #260 - Logger Implementation

Issue: One minor consistency suggestion within logger module
Severity: Low (Code Quality)

4. PR #266 - Vitest Setup

Issue: Suggestions to improve long-term test suite maintainability
Severity: Low (Test Quality)

5. PR #263 - Code Splitting

Issue: Code repetition in route definitions
Severity: Low (Maintainability)
Quote: "Reduce some code repetition in the route definitions for better long-term maintainability"

6. PR #261 - Android JNI Concurrency

Issue: Documentation alignment with implementation
Severity: Low (Documentation)

7. PR #257 - Memory Leak Fixes

File: frontend/src/hooks/useDraftAutosave.ts
Issue: One redundant line to remove
Severity: Low (Code Clarity)

Recommendations

These can be addressed in a single batch cleanup PR when convenient. None are urgent.

Related

• Gemini code review feedback across PRs fix(frontend): fix memory leaks, unhandled promises, and add error bo… #257, feat: add Logger utility and clean up console.log statements #260, fix: resolve unsafe concurrency in Android JNI layer #261, perf: implement route-based code splitting with React.lazy() #263, feat(frontend): add Vitest testing infrastructure with React Testing … #266, fix: add TypeScript strict null checks to frontend hooks #271, feat: migrate ESLint 8 to ESLint 9 flat config for native ESM support #279
• All critical and performance issues have been addressed separately

Priority

Low (Code quality and maintainability improvements)