dashboard: without LINKS; LINKS removed

The dashboard reads every member's links from the members themselves;
LINKS and LINKS_REPLY, swarm::links and their wire tags go (wire
version bumped). Nodes the browser can't reach are drawn from what the
reachable ones measure.

Auth plan M3.

1 files changed, 2 insertions, 3 deletions

diff --git a/docs/peers.md b/docs/peers.md
index 85d65a9..4aa1334 100644
--- a/docs/peers.md
+++ b/docs/peers.md
@@ -246,7 +246,7 @@ stateDiagram-v2
 - Dormancy is only judged while the node is ready, so joining nodes keep fast retries.
   A peer's farewell (it is shutting down: a STATUS with `leaving`) makes it dormant at
   once, whatever our phase; it isn't counted as an incident (`dormancies`). What that
-  run still sends while it stops (sync messages, PINGs, a LINKS_REPLY) doesn't make it
+  run still sends while it stops (sync messages, PINGs) doesn't make it
   active again: only a HELLO or HELLO_REPLY from its next run does.
 - **A suspended machine** (a laptop asleep) counts its peers as silent for as long as it
   slept: the monotonic clock the timers run on stops meanwhile, so without that every
@@ -376,8 +376,7 @@ what they know, contacting nobody: an active session that answers; a session tha
 doesn't, held dormant or unanswered HELLOs; or can't tell): if some don't and none does, the member is away and nothing is recorded
 (asked again after another hold); otherwise, or with no answer within 10 s, the link
 is recorded. A node that reaches nobody at all is the one away, and
-records nothing. PROBEs are their own message, apart from the dashboard's
-LINKS, which a node may leave unanswered.
+records nothing.
 
 A writer's changes pass on along its tree ([`swarm/tree.rs`](../src/swarm/tree.rs)), the same on every node:
 built on the graph the member list gives (as if every member reached every other), less