Add User-Facing Upload And Location Freshness States

[TheSilkky]

Add User-Facing Upload And Location Freshness States

Priority

High

Type

Frontend state mapping

Labels

backlog, frontend, design, accessibility, testing

Branch Scope

Created from docs/end-user-product-design at d2c32a3.

Background

Current routes expose low-level evidence structures such as streams and chunks. The end-user design document recommends user-facing upload and location freshness states so users can understand whether information is current, delayed, stale, unavailable, or failed without reading technical metadata.

These states should be explicit and tested instead of scattered across route copy.

Proposed Scope

• Define a small state-mapping layer for upload freshness and location freshness.
• Confirm source fields and meanings against current API schemas and server docs.
• Add user-facing labels and helper text for current, stale, delayed, unavailable, failed, and unknown states as appropriate.
• Use the mapping consistently on dashboard, incident detail, future viewer, and future capture surfaces.
• Add focused tests for state mapping and route display behavior.

Acceptance Criteria

• Upload and location freshness states are defined in one reviewable place.
• User-visible copy avoids raw stream/chunk terminology in primary views.
• Unknown or missing data is represented clearly and does not imply hidden live tracking.
• Stale or unavailable states are visibly distinct without relying on color alone.
• Unit or route tests cover representative state combinations.

Out Of Scope

• Backend schema changes.
• Guaranteed real-time claims.
• Hidden diagnostics or debug-only fields in primary user views.
• Browser capture implementation.
• Browser decryption or raw key handling.

Suggested Validation

• npm run typecheck
• npm run lint
• npm run test
• npm run build
• npm run test:e2e
• git diff --check