Rework Incident List And Dashboard Language

[TheSilkky]

Rework Incident List And Dashboard Language

Priority

High

Type

Product design / frontend follow-up

Labels

backlog, frontend, design, accessibility, testing

Branch Scope

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

Background

The end-user design document calls for incident review language that starts from what the user needs to understand, not from API metadata. The current dashboard and incident list still surface incident identifiers and technical "record" language as primary labels.

This makes the app feel like a prototype console instead of an end-user safety product.

Proposed Scope

• Inventory all user-visible incident list and dashboard copy in src/routes/index.tsx and src/routes/incidents/.
• Replace primary "incident record" and raw identifier language with end-user incident review language.
• Keep raw incident identifiers available only where useful as an advanced or copyable reference.
• Make empty, loading, and error states match the same language rules.
• Update tests that assert current route copy.
• Keep public wording clear that the app is experimental and not for emergency reliance.

Acceptance Criteria

• The dashboard and incident list use plain-language labels for incident review, capture/upload status, and next actions.
• Raw incident IDs are no longer the main title or primary row label for normal users.
• Technical details remain available where needed for reviewers or local testers.
• Empty, loading, and error copy is consistent with the updated terminology.
• Playwright smoke coverage reflects the new primary copy.

Out Of Scope

• Backend route or schema changes.
• Browser capture, recording, decryption, raw key handling, or playable export.
• Production emergency-service promises.
• Hiding warnings, error states, or reviewer-useful technical references entirely.

Suggested Validation

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