docs: what the review found that stays

Review findings 10 and 12, and 3.1/3.3: what stays as it is, said.

* Any member can log any user out: the user a logout names is its
  node's word, and a logout is no deciding path, even under strict.
* Used challenges are remembered in memory: after a restart, one
  captured within its five minutes could be taken once more.
* A registry turns strict as it is: whatever it holds then counts,
  plain values and envelopes, checked or not. Look it over first.
* A value that isn't an envelope starts its chain anew (prev empty).
* A strict registry whose only manager lost its keys changes no more:
  keep two managers, or two keys.
* The handed-over token stays in the address bar and history where the
  other dashboard never loads, for its five minutes.

1 files changed, 4 insertions, 1 deletions

diff --git a/docs/dashboard.md b/docs/dashboard.md
index db599fb..1a0ae86 100644
--- a/docs/dashboard.md
+++ b/docs/dashboard.md
@@ -209,7 +209,10 @@ measured.
   member list only, for five minutes, enough for the map: where the browser has no
   session at the other dashboard, its login page begins one with it (log in there to
   see more), unless its proxy asks for credentials of its own. Whoever publishes the
-  dashboard (a member writes its own URL) gets that token, no more. It opens as this one was left: the map's nodes where
+  dashboard (a member writes its own URL) gets that token, no more. It goes in the
+  address's fragment, which the other page takes out at once; where that page never
+  loads (an error, a proxy's own login), it stays in the address bar and the history,
+  for its five minutes. It opens as this one was left: the map's nodes where
   they were (on a dynamic map they then move to their places among the other node's
   links, smoothly; new ones are placed among them), the view, the pins, what is in
   focus, the legend shown or hidden, what is open in the figures and in the document,