fix(spa): search hears a refused local network from the connection

On a Pixel, Chrome still lists the refused address when search gives
up, so nothing tells it from a silent node. The connection given up on
now runs to its own verdict and the refusal is reported then.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 6 insertions, 4 deletions

diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index 01555804..e89623b4 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -4188,10 +4188,12 @@ narrow bridge — and Android has all three:
   under way resumes once the permission is granted or mobile data is back;
   an attempt still waiting on ICE is given up for a new one, since Chrome
   keeps refusing what it dropped when that attempt began. Search gives up on
-  a node long before ICE does, so it reads the refusal from the connection
-  when it gives up (`localNetworkRefused()`), tries the group's other nodes,
-  and names the groups refused, each a link to its page, apart from those
-  that did not answer.
+  a node after ten seconds without progress, and until ICE gives up Chrome
+  lists the refused address like any other: nothing tells the two apart
+  then. So a connection search gave up on is left to reach its own verdict
+  out of the walk, and the groups it finds refused are named, each a link to
+  its page, apart from those that did not answer; the message comes about
+  thirty seconds into the pass.
 - **The page hears when the phone changes network** (`meshbay-default-network`,
   from the default network callback), mobile data to Wi-Fi or back, and checks
   the connection it holds (transport.js `onNetworkChange`). The event carries