Align Route And Page Labels With Product Language

[TheSilkky]

Align Route And Page Labels With Product Language

Priority

Medium

Type

Frontend copy / navigation alignment

Labels

backlog, frontend, design, accessibility, testing

Branch Scope

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

Background

The design document recommends product-language labels for core journeys such as home, incident review, trusted contacts, viewer links, and account access. Current routes and navigation still reflect the prototype's technical shape in places, including records and contact-key terminology.

This should align page labels and navigation with the product language without changing route paths unless separately scoped.

Proposed Scope

• Inventory navigation labels, page titles, breadcrumbs or page headings, button labels, and tab labels.
• Align labels with the product terms in docs/end-user-web-client-design.md.
• Keep route paths stable unless a separate migration issue scopes URL changes.
• Ensure labels fit on supported desktop and mobile widths.
• Update Playwright route smoke assertions that depend on current labels.

Acceptance Criteria

• Primary navigation and page titles use consistent product-language terms.
• Technical labels such as contact key, incident token, chunk, stream, grant, and metadata are not primary navigation terms for normal users.
• Route URLs are unchanged unless explicitly approved in a separate issue.
• Labels remain accessible, concise, and responsive.
• Tests are updated for the new labels.

Out Of Scope

• Directly cloning any design file or redistributing Catalyst-derived components as a standalone asset set.
• Backend behavior changes.
• Large route restructuring or URL migration without a separate issue.
• Browser capture, decryption, recording, or notification delivery.

Suggested Validation

• npm run typecheck
• npm run lint
• npm run test
• npm run build
• npm run test:e2e
• Responsive visual spot check for navigation labels
• git diff --check