dashboard: show eager links on the map

2 files changed, 9 insertions, 4 deletions

diff --git a/docs/dashboard.md b/docs/dashboard.md
index 1fe51dc..70397a0 100644
--- a/docs/dashboard.md
+++ b/docs/dashboard.md
@@ -99,6 +99,9 @@ else the fresher. Then:
 * **Dotted**: one end reports no links: what is drawn may be out of date.
 * **Narrow, over a red band**: either end holds the other dormant, or the path in use
   is down (no path to the peer answers; `/peers` shows its connection as `null`).
+* **A chevron on the line in use**: the link is eager that way ([`peers.md`](peers.md)):
+  the end it points away from sends the other its changes as soon as it applies them,
+  rather than announcing them; one each way if both. Shown if either end says so.
 
 Messages this node exchanges run along its links as dots, from sender to receiver, all
 at one speed: over a longer link they arrive later.
@@ -327,7 +330,7 @@ another version of it (the state's `page`).
 member (`swarm::topology`), as this node computes them. The measured one is every
 member's links as it reports them in reply to a LINKS (sent to every member, at most
 512, while the producer runs). The LINKS subscribes: the member replies again whenever
-its links change (a peer, a transport, relayed, dormant, or a round trip moved by a
+its links change (a peer, a transport, relayed, dormant, eager, or a round trip moved by a
 fifth; it looks every 2 s), for 90 s, renewed every 30 s (each renewal answered), and
 ended when the producer stops; a node that is gone stops it by not renewing. A reply
 older than 90 s is left out. A member keeps 64 subscribers at most. With `links: every
@@ -364,7 +367,8 @@ every way has failed, all are tried again. Every hop does the same for what it a
 The links a member reports: its neighbours and the peers it holds dormant (a neighbour
 that goes dormant is one no more, but stays listed until it is heard from again), by
 which transport, whether only through a relay, the round trip (as the paths layer
-measures it), whether it holds the peer dormant or the path is down, the peer's other
+measures it), whether it holds the peer dormant or the path is down, which way the link
+is eager, the peer's other
 transports with a path up (each with its fastest path's round trip, and whether it goes
 only through a relay), and the peer's clock against the member's ([`measurements.md`](measurements.md),
 Per peer, `clock`). A member answers a LINKS from members only, at most every 5 s, and
diff --git a/docs/openapi.yaml b/docs/openapi.yaml
index c925dde..8205845 100644
--- a/docs/openapi.yaml
+++ b/docs/openapi.yaml
@@ -753,8 +753,9 @@ paths:
         those of the member list, and any a link reported goes to: `alias`, `self`,
         `dashboard`: its `--dashboard-url`), `intended` (by node ID: the neighbours the member list gives
         it, as this node computes them), `measured` (by node ID: `secsAgo` and
-        `links`, each with `peer`, `transport`, `relayed`, `down`, `rttMs`, `dormant` and
-        `others` (the peer's other transports: `transport`, `rttMs`, `relayed`), as the member
+        `links`, each with `peer`, `transport`, `relayed`, `down`, `rttMs`, `dormant`,
+        `eagerTo` and `eagerFrom` (the member sends the peer its changes as it applies
+        them, and the peer the member: eager links) and `others` (the peer's other transports: `transport`, `rttMs`, `relayed`), as the member
         answered a LINKS; ours always, the others' while fresh) and `live` (whether the
         members' links are subscribed to, `/admin/dashboard/links`). One producer
         per node makes it every 2 s while anyone looks (and for a minute after this