Give twelve modules' connection absence the reason that holds, which is the library and not the tree

src/artwork/address.rs

@@ -32,8 +32,16 @@ use crate::server::address::BaseAddress;
 /// constructed, so there is no call site at which one could be caught.
 ///
 /// Which kinds a given server actually holds is a claim in 0049 rather than a
-/// measurement. Nothing in this tree contacts a server, and #104 is the route by
-/// which that claim becomes measured or is contradicted.
+/// measurement. No code the library ships contacts a server, and #104 is the
+/// route by which that claim becomes measured or is contradicted.
+///
+/// THAT SENTENCE READ "NOTHING IN THIS TREE CONTACTS A SERVER", AND THE TREE
+/// DID. `tests/fake_server/` binds a loopback listener and
+/// `tests/fake_server/client.rs` sends requests to it, from 2026-08-28, which is
+/// older than this file. The claim was therefore refuted before it was written,
+/// and what holds is the narrower statement above. #104 is unmoved: the library
+/// has no transport to ask a server with, which is #27. #440 is where it was
+/// found.
 ///
 /// Thread safety, from 0009: a plain value, safe from any thread.
 #[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)]

src/artwork/announced.rs

@@ -17,13 +17,21 @@
 //! which announcements are sharing a fetch, and which withdrawal is the one that
 //! abandons it.
 //!
-//! WHAT IS NOT HERE IS THE FETCH. Nothing in this tree opens a connection, for
-//! the reason [`crate::server::transport`] gives about itself, so nothing is
-//! fetched, nothing is decoded and nothing is abandoned. This module holds the
+//! WHAT IS NOT HERE IS THE FETCH. The library opens no socket, for the reason
+//! [`crate::server::transport`] gives about itself, so nothing is fetched,
+//! nothing is decoded and nothing is abandoned. This module holds the
 //! bookkeeping such a fetch would be started and stopped from. #53's three
 //! conditions announce two hundred tiles against a running core, and none of
 //! them is met by anything here.
 //!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", WHICH IS ONE
+//! SCOPE WIDER THAN THE REASON IT CITES. [`crate::server::transport`] says of
+//! itself that nothing in that MODULE reads or writes a byte, and
+//! `tests/fake_server/` has bound a loopback listener since 2026-08-28, two days
+//! before this file landed, so the wider claim was refuted before it was
+//! written. #53's conditions stay unmet either way, and what they wait on is a
+//! core that connects, which is #27. #440 is where it was found.
+//!
 //! WHAT IS ALSO NOT HERE IS A CAP ON OUTSTANDING REQUESTS, and its absence is
 //! 0053's own sentence rather than an omission. The cap #53 asks for is not a
 //! number that record adds: 0027 holds at most six requests outstanding to one

src/artwork/presence.rs

@@ -69,8 +69,16 @@
 //! in a tree that fetches nothing.
 //!
 //! There is also no request made for the answer that carries one. The transport
-//! is #27 and nothing in this tree opens a connection, so a caller receiving
+//! is #27 and the library opens no socket, so a caller receiving
 //! [`WhatTheItemHas::AnImage`] receives an address and nothing has been fetched.
+//!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", AND THE TREE
+//! DID. `tests/fake_server/` binds a loopback listener and
+//! `tests/fake_server/client.rs` sends requests to it, from 2026-08-28, which is
+//! older than this file, so the claim was refuted before it was written. What
+//! holds is the narrower statement above, and it is the one the sentence needs:
+//! the address this type hands back is not fetched because the library cannot
+//! fetch it. #440 is where it was found.
 
 use super::address::{ArtworkRequest, DrawnSize, ImageKind, ImageTag, ItemId, NotUsableInARequest};
 

src/playback/report.rs

@@ -44,14 +44,21 @@
 //! What is here is the reporting: on which occasions a report is made, what it
 //! carries, and that it goes through the queue and nowhere else.
 //!
-//! WHAT IS NOT HERE IS THE DELIVERY. Nothing in this tree opens a connection,
-//! so no report leaves the device and no drain runs. The queue is 0047's, the
-//! drain runs on 0045's recovery report, and which request carries a report is
-//! 0272's table met by #27's transport. 0057's honest statement about the report
-//! a person most expects to have landed applies to every report here: durable
-//! rather than delivered, and today the queue is not durable either, which
+//! WHAT IS NOT HERE IS THE DELIVERY. The library opens no socket, so no report
+//! leaves the device and no drain runs. The queue is 0047's, the drain runs on
+//! 0045's recovery report, and which request carries a report is 0272's table
+//! met by #27's transport. 0057's honest statement about the report a person
+//! most expects to have landed applies to every report here: durable rather
+//! than delivered, and today the queue is not durable either, which
 //! [`crate::server::write_queue`] says of itself.
 //!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", AND THE TREE
+//! DID. `tests/fake_server/` binds a loopback listener and
+//! `tests/fake_server/client.rs` sends requests to it, from 2026-08-28, which is
+//! older than this file, so the claim was refuted before it was written. No
+//! report leaves the device for the narrower reason above, and the transport
+//! that would carry one is #27. #440 is where it was found.
+//!
 //! WHAT IS ALSO NOT HERE IS THE PLAYER. 0003 puts decoding and presenting
 //! outside the core, so the core never sees a stream and never learns a position
 //! by itself. A client tells it: the five events as they happen, and the

src/server/certificate.rs

@@ -19,12 +19,21 @@
 //! for want of time. 0029 puts the chain, the name and the validity window with
 //! the platform in so many words - the core validates "using the platform's own
 //! trust store and the platform's own path building" and "does not reimplement
-//! it" - and nothing in this tree reaches a platform. There is no socket either,
-//! for the reason [`super::transport`] gives about itself. So no value of
-//! [`CertificateReason`] is produced here by judging a certificate; the six
-//! classes are what a platform's refusal is mapped onto, and that mapping
+//! it" - and nothing in this tree reaches a platform. The library opens no
+//! socket either, for the reason [`super::transport`] gives about itself. So no
+//! value of [`CertificateReason`] is produced here by judging a certificate; the
+//! six classes are what a platform's refusal is mapped onto, and that mapping
 //! arrives with the connection in #27 and with #29's second condition.
 //!
+//! THAT CLAUSE READ "THERE IS NO SOCKET EITHER", TAKING ITS SUBJECT FROM THE
+//! CLAUSE BEFORE IT, AND SO SAID THERE IS NO SOCKET IN THIS TREE.
+//! `tests/fake_server/` has bound a loopback listener since 2026-08-28, which is
+//! older than this file, so the clause was refuted before it was written. The
+//! reason it cites is narrower and correct - the transport says nothing in that
+//! MODULE reads or writes a byte - and the narrower form is what stands above.
+//! The platform half of the sentence is a different absence and is untouched.
+//! #440 is where it was found.
+//!
 //! What follows from that, said once so a later reading does not take it for
 //! more: nothing below decides that a certificate is acceptable. It decides that
 //! a certificate an operator already asserted is theirs is the one that

src/server/library.rs

@@ -20,13 +20,23 @@
 //! the fourth derived from them, and which of 0010's library reads accepts a
 //! page request at all.
 //!
-//! WHAT IS NOT HERE IS A READ. Nothing in this tree makes a request, for the
-//! reason [`crate::server::transport`] gives about itself, so nothing here asks
-//! a server anything and nothing here receives a page from one. This module
-//! holds the shape such an answer is handed back in. #39's three conditions are
-//! a test per call against a recorded fixture, paging proven across a boundary,
+//! WHAT IS NOT HERE IS A READ. The library makes no request, for the reason
+//! [`crate::server::transport`] gives about itself, so nothing here asks a
+//! server anything and nothing here receives a page from one. This module holds
+//! the shape such an answer is handed back in. #39's three conditions are a
+//! test per call against a recorded fixture, paging proven across a boundary,
 //! and one item type across the calls, and none of them is met by anything here.
 //!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE MAKES A REQUEST", WHICH IS ONE
+//! SCOPE WIDER THAN THE REASON IT CITES. [`crate::server::transport`] says of
+//! itself that nothing in that MODULE reads or writes a byte, and
+//! `tests/fake_server/client.rs` has sent requests to a loopback listener since
+//! 2026-08-28, three days before this file landed, so the wider claim was
+//! refuted before it was written. #39's conditions stay unmet either way: what
+//! they wait on is a core that reaches a server, which is #27, and a recording,
+//! which `tests/recorded/README.md` describes and this tree does not hold. #440
+//! is where it was found.
+//!
 //! WHAT IS NOT HERE IS THE ITEM'S FIELDS, and that absence is 0039's own
 //! sentence rather than an omission. The record fixes that every read answers
 //! with ONE item type and says in the same paragraph that which fields a given
@@ -326,7 +336,14 @@ mod tests {
     //!
     //! What these cannot ask is any of #39's three conditions. Each of those
     //! needs a request to have been made and a recording of one to exist, and
-    //! nothing in this tree makes a request.
+    //! the library makes no request.
+    //!
+    //! THAT REASON READ "NOTHING IN THIS TREE MAKES A REQUEST", AND IT WAS
+    //! ALREADY FALSE WHEN IT WAS WRITTEN. `tests/fake_server/client.rs` has sent
+    //! requests to a loopback listener since 2026-08-28. So the apparatus is
+    //! here and the reason was the wrong one: what is missing is a core to drive
+    //! it with, which is #27, and the recording the conditions also ask for. The
+    //! three conditions stay unasked either way. #440 is where it was found.
 
     use super::{
         LibraryRead, NotAPagedRead, Page, PageRequest, THE_TOTAL_IS_ALWAYS_ASKED_FOR,

src/server/recovery.rs

@@ -28,12 +28,21 @@
 //! each failure, when the ceiling has been reached, when the hour is up, and
 //! what a client's attempt-now does to both.
 //!
-//! WHAT IS NOT HERE IS THE PROBE. Nothing in this tree opens a connection, for
-//! the reason [`super::transport`] gives about itself, so nothing calls a
-//! server, nothing declares one unreachable, and nothing reports a recovery.
-//! This module holds the schedule such a thing would run on. #45's three
-//! conditions are about a fake server being taken away and put back, and none of
-//! them is met by anything here.
+//! WHAT IS NOT HERE IS THE PROBE. The library opens no socket, for the reason
+//! [`super::transport`] gives about itself, so nothing calls a server, nothing
+//! declares one unreachable, and nothing reports a recovery. This module holds
+//! the schedule such a thing would run on. #45's three conditions are about a
+//! fake server being taken away and put back, and none of them is met by
+//! anything here.
+//!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", AND THE FAKE
+//! SERVER ITS CONDITIONS NAME IS IN THIS TREE. `tests/fake_server/` binds a
+//! loopback listener and `tests/fake_server/client.rs` sends requests to it,
+//! from 2026-08-28, which is older than this file. The reason it cites is
+//! narrower and correct - the transport says nothing in that MODULE reads or
+//! writes a byte - and the narrower form is what stands above. #45's conditions
+//! wait on a core that probes, which is #27, rather than on a server to probe.
+//! #440 is where it was found.
 //!
 //! WHAT IS ALSO NOT HERE IS THE DRAW. 0045 applies the spread 0038 defines, and
 //! 0038 fixes it as a wait drawn uniformly at random from zero to the computed

src/server/retry.rs

@@ -56,10 +56,17 @@
 //! own hint replaces that draw, and whether there is enough deadline left to
 //! begin an attempt at all.
 //!
-//! WHAT IS NOT HERE IS THE REQUEST. Nothing in this tree opens a connection, for
-//! the reason [`super::transport`] gives about itself, so nothing here sends an
-//! attempt, waits, or observes a second one succeed. This module holds the
-//! policy such a loop would run under.
+//! WHAT IS NOT HERE IS THE REQUEST. The library opens no socket, for the reason
+//! [`super::transport`] gives about itself, so nothing here sends an attempt,
+//! waits, or observes a second one succeed. This module holds the policy such a
+//! loop would run under.
+//!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", WHICH IS ONE
+//! SCOPE WIDER THAN THE REASON IT CITES. The transport says of itself that
+//! nothing in that MODULE reads or writes a byte, and `tests/fake_server/` has
+//! bound a loopback listener since 2026-08-28, which is older than this file, so
+//! the wider claim was refuted before it was written. What is absent is a core
+//! that sends an attempt, which is #27. #440 is where it was found.
 //!
 //! WHAT IS ALSO NOT HERE IS THE ABANDONMENT COUNT. 0038 decides that a call
 //! spending all three attempts is one abandonment rather than three, because

src/server/states.rs

@@ -16,12 +16,20 @@
 //! abandonments with no success between them make a server unreachable rather
 //! than a request unlucky.
 //!
-//! WHAT IS NOT HERE IS THE REQUEST. Nothing in this tree opens a connection, for
-//! the reason [`super::transport`] gives about itself, so nothing here starts a
-//! request, waits on one, cancels one or hears an answer. This module holds the
-//! states such a loop would report from. #44's own condition drives the fake
-//! server at several delays and asserts the sequence, and none of it is met by
-//! anything here.
+//! WHAT IS NOT HERE IS THE REQUEST. The library opens no socket, for the reason
+//! [`super::transport`] gives about itself, so nothing here starts a request,
+//! waits on one, cancels one or hears an answer. This module holds the states
+//! such a loop would report from. #44's own condition drives the fake server at
+//! several delays and asserts the sequence, and none of it is met by anything
+//! here.
+//!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", AND THE FAKE
+//! SERVER THE NEXT SENTENCE NAMES IS IN THIS TREE. `tests/fake_server/` binds a
+//! loopback listener and moves a clock for two integration tests, from
+//! 2026-08-28, which is older than this file. The reason it cites is narrower
+//! and correct - the transport says nothing in that MODULE reads or writes a
+//! byte - and the narrower form is what stands above. #44 waits on a core that
+//! starts a request, which is #27. #440 is where it was found.
 //!
 //! WHAT IS ALSO NOT HERE IS THE CACHED ANSWER EACH REPORT CARRIES. 0007 has the
 //! report at nought carry whether a cached answer exists and its age, and the
@@ -360,8 +368,15 @@ mod tests {
     //! Every case moves a clock rather than waiting on one, which is what 0102
     //! requires of the suite and what makes a five second threshold cost
     //! microseconds. What these cannot ask is #44's own condition, which drives
-    //! the fake server at several delays; nothing in this tree makes a request
-    //! for a delay to answer.
+    //! the fake server at several delays; the library makes no request for a
+    //! delay to answer.
+    //!
+    //! THAT REASON READ "NOTHING IN THIS TREE MAKES A REQUEST", IN THE SAME
+    //! SENTENCE THAT NAMES THE FAKE SERVER. `tests/fake_server/` has been in
+    //! this tree since 2026-08-28 and `tests/fake_server/client.rs` sends
+    //! requests to it. So the apparatus is here and the reason was the wrong
+    //! one: what is missing is a core to drive it with, which is #27. #44's
+    //! condition stays unasked either way. #440 is where it was found.
 
     use super::{
         A_REQUEST_IS_LATE_AFTER, ABANDONMENTS_BEFORE_A_SERVER_IS_GONE, AgingRequest,

src/server/write_queue.rs

@@ -29,11 +29,19 @@
 //! which entry an overflow drops, what the queue reports afterwards, and the
 //! order a drain walks in.
 //!
-//! WHAT IS NOT HERE IS THE DELIVERY. Nothing in this tree opens a connection,
-//! for the reason [`super::transport`] gives about itself, so nothing is sent,
-//! nothing is acknowledged and no drain runs. This module holds the queue such a
-//! drain would walk. #47's two conditions restart the core and restore a server,
-//! and neither is met by anything here.
+//! WHAT IS NOT HERE IS THE DELIVERY. The library opens no socket, for the
+//! reason [`super::transport`] gives about itself, so nothing is sent, nothing
+//! is acknowledged and no drain runs. This module holds the queue such a drain
+//! would walk. #47's two conditions restart the core and restore a server, and
+//! neither is met by anything here.
+//!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", WHICH IS ONE
+//! SCOPE WIDER THAN THE REASON IT CITES. The transport says of itself that
+//! nothing in that MODULE reads or writes a byte, and `tests/fake_server/` has
+//! bound a loopback listener since 2026-08-28, which is older than this file, so
+//! the wider claim was refuted before it was written. #47's conditions wait on a
+//! core that restarts and sends, which is #115 and #27. #440 is where it was
+//! found.
 //!
 //! WHAT IS ALSO NOT HERE IS DURABILITY. 0047 puts the bytes in the store 0040
 //! defines, keyed under #41, and neither the store interface's caller nor that

src/session/password.rs

@@ -373,8 +373,14 @@ mod tests {
     //! 0030's password and its answer, asked of the values.
     //!
     //! What these cannot ask is #30's own condition. It is a sign-in against the
-    //! fake server, and nothing in this tree opens a connection to drive one
-    //! over.
+    //! fake server, and the library opens no socket to drive one over.
+    //!
+    //! THAT REASON READ "NOTHING IN THIS TREE OPENS A CONNECTION", IN THE SAME
+    //! SENTENCE THAT NAMES THE FAKE SERVER. `tests/fake_server/` has been in
+    //! this tree since 2026-08-28 and `tests/fake_server/client.rs` opens a
+    //! connection to it. So the apparatus is here and the reason was the wrong
+    //! one: what is missing is a core to sign in with, which is #27. #30's
+    //! condition stays unasked either way. #440 is where it was found.
 
     use super::{
         AccountName, AnswerRead, FactNotCarried, FactsASessionNeeds, Password,

src/session/quick_connect.rs

@@ -14,12 +14,20 @@
 //! poll that failed does to the schedule, which of the four endings is a failure
 //! and which three are answers, and which value a client is handed.
 //!
-//! WHAT IS NOT HERE IS THE POLL. Nothing in this tree opens a connection, for
-//! the reason [`crate::server::transport`] gives about itself, so nothing asks a
-//! server anything, nothing starts an exchange and nothing receives a code.
-//! This module holds the schedule such a thing would run on and the shape of
-//! what it would return. #31's three conditions are about requests made against
-//! the fake server, and none of them is met by anything here.
+//! WHAT IS NOT HERE IS THE POLL. The library opens no socket, for the reason
+//! [`crate::server::transport`] gives about itself, so nothing asks a server
+//! anything, nothing starts an exchange and nothing receives a code. This
+//! module holds the schedule such a thing would run on and the shape of what it
+//! would return. #31's three conditions are about requests made against the
+//! fake server, and none of them is met by anything here.
+//!
+//! THAT SENTENCE READ "NOTHING IN THIS TREE OPENS A CONNECTION", AND THE FAKE
+//! SERVER ITS CONDITIONS NAME IS IN THIS TREE. `tests/fake_server/` binds a
+//! loopback listener and `tests/fake_server/client.rs` sends requests to it,
+//! from 2026-08-28, which is older than this file. The reason it cites is
+//! narrower and correct - the transport says nothing in that MODULE reads or
+//! writes a byte - and the narrower form is what stands above. #31's conditions
+//! wait on a core that polls, which is #27. #440 is where it was found.
 //!
 //! WHAT IS ALSO NOT HERE IS THE ROUTE'S OWN DETECTION. 0031 says the core asks
 //! the configured server and never guesses, and that where the server states