Feature: Network graph visualization with duplicate-reception and bidirectional-confirmation data

[Yeraze]

Origin

This feature request came from Discord user NullVoid (username null_v0id) in #meshtastic, after discussion in the channel confirmed the scope below.

Request

Bundle the following three related capabilities into one issue:

A) Network graph visualization with live packet animation — a visual graph of the mesh network showing packets moving between nodes in real time.

B) Show duplicate receptions — surface when your radio hears a packet duplicate that it does not rebroadcast (not just currently-active routes).

Note: NullVoid flagged that this data (raw duplicate-reception / "heard but not rebroadcast" packets) could be useful as a reusable data source for other future features, not just the graph in (A). Worth keeping the implementation generalized/reusable rather than a hyper-specific one-off tied only to the graph view.

C) Confirm bidirectional comms — show which gateway/node is providing bidirectional confirmation for a given node.

Implementation note

(A) is likely the most novel and self-contained piece of the three, and could reasonably ship independently of (B)/(C) if useful for phasing the work. That said, the user wants this filed as one bundled issue for now rather than split into three.

Context

• PacketMonitorPanel.tsx currently renders a plain table with no graph or animation.
• No graph visualization library (d3, force-graph, cytoscape, etc.) is currently in package.json.
• MeshManager also has no network graph feature today.

Authored by NodeZero 0️⃣

[Yeraze]

Follow-up from NullVoid (null_v0id) in Discord #meshtastic:

• The network graph (part A) should reuse the existing recency-fade convention rather than inventing a new one — see src/utils/markerAgeOpacity.ts, already used for the Dashboard map and Map Analysis (from [FEAT] Fade map node markers by age instead of hard time-slider cutoff #3886) to fade node opacity by last-heard time.
• Beyond reusing the fade visually, NullVoid wants an explicit stale flag/filter for nodes (not just the opacity fade) — a way to directly tell "is this node stale" rather than inferring it from how faded a marker looks.
• This ties into Map Analysis more broadly — worth considering whether the graph view and Map Analysis should share a single staleness/recency utility rather than duplicating logic.

Authored by NodeZero 0️⃣