[P6.8.4] frontend lint: resolve 7 react-hooks/exhaustive-deps warnings

[frankbria]

Context

Follow-up from #646 (PR #681), which re-enabled frontend lint in CI. ESLint exits 0 on warnings (no --max-warnings), so lint is green, but 7 react-hooks/exhaustive-deps warnings remain in pre-existing components and should not silently accumulate.

Warnings

• src/app/proof/[req_id]/page.tsx:88 — missing dep reqId
• src/components/execution/BatchExecutionMonitor.tsx:105 — missing dep batch
• src/components/prd/DiscoveryPanel.tsx:83 — missing dep startNewSession
• src/components/prd/StressTestModal.tsx:75 — ambiguities logical expr (×2, useMemo deps)
• src/components/tasks/GitHubIssueImportModal.tsx:94 — issues logical expr (×2, useMemo/useCallback deps)

Why deferred

Each fix is behavioral (changing hook deps can alter render/effect timing) and out of scope for the CI-hardening issue #646. Resolving them needs per-component verification, not a blanket autofix.

Acceptance criteria

• All 7 warnings resolved without regressions (verify each component's behavior)
• Optionally consider --max-warnings 0 in the lint step once clean, to prevent regressions

[coderabbitai]

🔗 Related PRs

#76 - Add dismissible warning banner to QualityGateStatus component [merged]
#211 - feat(dashboard): Add PhaseProgress component for phase visualization [merged]
#236 - fix(ui): complete late-joining user bug fix for TaskStats and TaskReview [merged]
#584 - fix(pr-status): address claude-review feedback post-merge (#571 follow-up) [merged]
#681 - ci(frontend): add npm run build + re-enable frontend lint (#646) [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[frankbria]

Prioritization: P6.8.4 (phase-6.8, P3-post-beta).

• Non-blocking: lint is green ([P6.5.1] frontend-tests CI: add npm run build + re-enable frontend lint #646 shipped); these are warnings, not errors — no CI/beta impact, so it sits below all P0–P2 beta work.
• Sequence after [P6.8.2] Frontend major-dependency upgrades: jest 30, jsdom 30, eslint 10, tailwind 4 #658 (frontend major-dep upgrades, incl. eslint 10 + react-hooks plugin): doing this first risks rework since rule defaults/auto-fixes may shift which warnings fire.
• Hard-depends on [P6.5.1] frontend-tests CI: add npm run build + re-enable frontend lint #646 (merged, re-enabled lint).
• Within phase-6.8: [P6.8.3] Reconcile CI -m v2 blind spot: ~535 tests (40% of files) never run in CI #669 (P1) → [P6.8.1] Add tests for untested core modules: artifacts.py, review.py, api_key_service.py #654 (P2) → [P6.8.2] Frontend major-dependency upgrades: jest 30, jsdom 30, eslint 10, tailwind 4 #658 (P2) → [P6.8.4] frontend lint: resolve 7 react-hooks/exhaustive-deps warnings #682 (P3).