api: a stream opened by password or a proxy's header ends with its user

Review 4, F11: only streams answered to a token ended with it (1273); one opened by
password (basic authentication) or a proxy's header went on after its user was
disabled or removed.

`streams_end` now wraps those too, by the user `basic_auth` leaves on the answer: such
a stream ends once the document no longer has its user, enabled
(`token::user_taken`, the part of a token's check about its user, which
`still_taken` uses too), looked at as the stream begins and as protocol data changes.
No expiry: a password has none.

1 files changed, 2 insertions, 1 deletions

diff --git a/docs/access.md b/docs/access.md
index 6422b51..3d4aeaf 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -133,7 +133,8 @@ curl -H "Authorization: Bearer ct1.…" http://other-node:3000/store
   session's tokens itself, until it restarts; others take them until they expire.
   A stream opened with a token (server-sent events, the store's streams) ends with it:
   when it expires, or once the node holds a change that revokes it (looked at as
-  protocol data changes), a session's end on the node itself included. A token of a node banned or forgotten by the swarm isn't
+  protocol data changes), a session's end on the node itself included. One opened by
+  password or a proxy's header ends once its user is disabled or removed. A token of a node banned or forgotten by the swarm isn't
   taken either. In a swarm without a registry, a token is taken until it expires. The
   user a logout names is its node's word, and a logout no deciding path, even under a
   strict policy: any member could log any user out. It ends sessions; and a value there