fix(spa): a reconnect refused the local network says so

Each failed attempt reaches the group page, which shows the same message
and buttons as at opening while the reconnect goes on. Try now gives up
an attempt still waiting on ICE and starts the next at once.

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

1 files changed, 9 insertions, 1 deletions

diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index b720623a..1480cd57 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -4179,6 +4179,15 @@ narrow bridge — and Android has all three:
   while Android will still ask, then the application's settings. Moving to
   SDK 37 also took the permission back from an installed application, which
   had it implied before: the first group opened after the update asks.
+  A phone connected on mobile data that walks onto the node's Wi-Fi without
+  the permission, in the application or in Chrome, loses its connection and
+  is refused on every reconnect attempt: each refusal reaches the group page
+  (`addReconnectFailureListener`), which says the same as at opening over the
+  view it had, while the reconnect goes on. The page's buttons ask that
+  reconnect to try now rather than tear it down, so a download or a film
+  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.
 - **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
@@ -4819,7 +4828,6 @@ process runs it — `systemctl --user` on Linux, Task Scheduler on Windows.
 | **A queued transfer logs "no answer" every minute** | The lease watchdog re-asks after 60 s of silence whatever the last answer was, so a lease the node has answered `queued` and that has not moved prints "no answer for transfer ... asking again" once a minute for as long as it waits, which reads as a fault |
 | **"Prune stale entries" does not touch the index** | The Node page's maintenance button runs `prune_index_cache`, which drops rows of the hash cache and nothing else. An operator who sees a deleted file still listed reaches for it, and nothing changes: only the reconcile removes an index entry, and nothing lets the operator ask for one |
 | **Only the group page explains a refused local network** | `transport.js` names it (`local_network_blocked`, Android 17 and Chrome 155), and `group-page.js` says what to change. Search and the other screens that open a connection show it as a node that cannot be reached |
-| **A reconnect refused the local network says nothing** | A phone connected on mobile data that walks onto the node's Wi-Fi without the permission loses the connection when Android drops mobile data, and `_reconnectLoop` retries with the reason in the console and nowhere else |
 
 ---