The approved connected-investigation phase starts with a packet's retained reports: group equal raw path prefixes, show reporting observers, inspect a selected report, and open its map/observer context. Grouped prefixes must not be presented as confirmed identical physical routes.
Proposed focused web slice after #81:
- Add a compact reception-evidence section to the existing analyzer, using its already-fetched detail; no per-report request loop.
- Separate retained reports, distinct reporting observers, usable path variants and unavailable paths. Zero-hop and malformed/missing paths are distinct; TRACE intended-route semantics are explicit.
- Preserve a selected report in copied packet links and browser return navigation; keep quick observer inspection and its Open dashboard action.
- Open a specific report on the existing path map. Do not choose an arbitrary ambiguous node or connect across unresolved/unlocated gaps; explain unmappable reports and translate revised controls in English/French.
- Verify Windows regression/build/lint, full native Pi tests, desktop/phone/keyboard/locale flows, source/changelog and rollback. Keep current review candidates in the preview.
Known-route-to-retained-packet/report links need a separate bounded API contract and remain the following slice. This work relates to #12 without closing broader translations. It adds no dependencies or server migration.
The approved connected-investigation phase starts with a packet's retained reports: group equal raw path prefixes, show reporting observers, inspect a selected report, and open its map/observer context. Grouped prefixes must not be presented as confirmed identical physical routes.
Proposed focused web slice after #81:
Known-route-to-retained-packet/report links need a separate bounded API contract and remain the following slice. This work relates to #12 without closing broader translations. It adds no dependencies or server migration.