Continue the approved connected-investigation roadmap from packet evidence #83: selecting a saved route should offer a shareable full-route view and bounded retained report pages, with packet/report and observer-dashboard links.
Use the planned server route-evidence endpoint keyed by IATA and stable pathKey. Clearly label complete saved-prefix matches, hash width, time window, raw-retention limits and missing/unclassified/TRACE exclusions. Search may return a subsegment; the evidence view must identify the full saved route instead of implying that the subsegment is the stored identity. Preserve the directory's search/sort/scroll during inspection and keep English/French controls. No per-report detail fetch loop or arbitrary node-identity inference.
This follows #83 and the new server contract; the existing review stack remains in the Pi preview. Run native/full browser/source/changelog checks and retain rollback. Related #12 stays open; broader overlay return navigation remains a separate slice.
Continue the approved connected-investigation roadmap from packet evidence #83: selecting a saved route should offer a shareable full-route view and bounded retained report pages, with packet/report and observer-dashboard links.
Use the planned server route-evidence endpoint keyed by IATA and stable pathKey. Clearly label complete saved-prefix matches, hash width, time window, raw-retention limits and missing/unclassified/TRACE exclusions. Search may return a subsegment; the evidence view must identify the full saved route instead of implying that the subsegment is the stored identity. Preserve the directory's search/sort/scroll during inspection and keep English/French controls. No per-report detail fetch loop or arbitrary node-identity inference.
This follows #83 and the new server contract; the existing review stack remains in the Pi preview. Run native/full browser/source/changelog checks and retain rollback. Related #12 stays open; broader overlay return navigation remains a separate slice.