docs: what is postponed or rejected stays in its own two files

Docs and comments outside future-work.md and review-rejections.md say what the code
does, and point nowhere else for what it doesn't: the architecture page's map, the
transports' forwarders, keys with `/`, a strict swarm's registry, trust.md's "Not yet"
(now saying what isn't protected, in a sentence), the topology bench, and the comments
of the change benchmarks, capabilities' grantor, tokens, dissemination, refusals and
topology.

2 files changed, 2 insertions, 4 deletions

diff --git a/src/access/mod.rs b/src/access/mod.rs
index f3e5f80..e223756 100644
--- a/src/access/mod.rs
+++ b/src/access/mod.rs
@@ -68,8 +68,7 @@ pub(crate) struct Capability {
     /// nothing here.
     pub(crate) rights: BTreeSet<String>,
     /// Who granted it: a user (`user:<name>`), or for those the genesis node records, the
-    /// node (its node ID). Kept so that granting on, by delegation, can come later
-    /// without a new format (`future-work.md`, Authentication across nodes).
+    /// node (its node ID), kept with the capability.
     #[serde(default)]
     pub(crate) by: String,
     /// When it was granted (Unix ms).
diff --git a/src/access/token.rs b/src/access/token.rs
index 153737e..51c2449 100644
--- a/src/access/token.rs
+++ b/src/access/token.rs
@@ -11,8 +11,7 @@
 //!
 //! Not Biscuit or UCAN (November 2026): a token only names a user, narrowing is asked
 //! of a node (which issues a narrower one), and Biscuit would bring about a hundred
-//! crates, older versions of several of ours among them (Ed25519, SHA-2, protobuf):
-//! `future-work.md`, Authentication across nodes.
+//! crates, older versions of several of ours among them (Ed25519, SHA-2, protobuf).
 
 use base64::{Engine, engine::general_purpose::URL_SAFE_NO_PAD as BASE64URL};
 use serde::{Deserialize, Serialize};