dashboard: the console in the order messages went

The console appended messages as their streams brought them, a
subscribed node's later than this node's by its path, each line with
its node's own clock's time: lines of one moment came apart, and their
times read out of order.

Each message is now listed by when its node logged it, on this node's
clock, as the map runs them (`aheadOf`): one a slower stream brought
late goes in among those of its moment. The time shown is on this
node's clock; a subscribed node's own clock's time is in its tooltip.

1 files changed, 7 insertions, 3 deletions

diff --git a/docs/dashboard.md b/docs/dashboard.md
index 72d77da..0d1500b 100644
--- a/docs/dashboard.md
+++ b/docs/dashboard.md
@@ -364,13 +364,17 @@ transport wouldn't send it), with whom, the type (`HELLO`, `SYNC`, `STATUS_REPLY
 `PING`, …, in its kind's colour, as on the map) and the size. The latest 500, the
 newest at the bottom; scrolled along while at the bottom, which `following…` beside the
 title says. `clear` empties it; what comes from then on fills it again. They arrive as
-they come (a tenth of a second after the first of a moment's). The PINGs the paths layer sends on its own, and the PONGs it answers
+they come (a tenth of a second after the first of a moment's), and are listed in the
+order they went, as the map runs them: each by when its node logged it, on this node's
+clock (a subscribed node's taken back by how far its clock is ahead, as the map chains
+the clocks; its own clock's time in the tooltip of the time), so one a slower stream
+brought late goes in among those of its moment, not at the bottom. The PINGs the paths layer sends on its own, and the PONGs it answers
 PINGs with, are listed too: under the node at the address they went to, where it is
 known, else under the address. Not listed: WHO and ME, which stay in the layers
 below the node (they are counted, [`measurements.md`](measurements.md), Traffic).
 
-A subscribed node's messages with its peers are listed too, as they come from it (every
-2 s): named by both ends, the receiver first (`b ← a`), each once, as on the map (those
+A subscribed node's messages with its peers are listed too, as they come from it:
+named by both ends, the receiver first (`b ← a`), each once, as on the map (those
 with this node only from this node, between two subscribed nodes from the sender); its
 tooltip names the node that logged it. Shown in the figures box, it says when, both
 ends, its type and size: the message itself is written out only on the node that