[P2] Improve Frontend Error States And Result Consistency

[barvhaim]

Roadmap Item 12: Improve Frontend Error States And Result Consistency

Priority: P2
Area: Frontend, API contract
References: frontend/src/services/realScanService.js,
frontend/src/pages/AnalysisPage.jsx, frontend/src/components/TabbedResultsPanel.jsx

The frontend maps backend responses manually and has several fallback defaults. Once the
API exposes normalized findings and analyzer health, the UI should make partial scans,
cached scans, and failed analyzers understandable.

Scope:

• Show analyzer-level statuses and partial-result warnings.
• Distinguish scan queued/running/completed/failed/cached states.
• Use backend-provided normalized findings instead of duplicating risk calculations.
• Add retry and force-rescan actions where appropriate.

Acceptance criteria:

• Users can tell whether a result is fresh, cached, partial, or failed.
• Finding counts match API output exactly.
• Network, validation, LLM, and analyzer failures have specific user-facing messages.

Phase 4: Advanced Detection And Reporting

---

Created from docs/roadmap.md.