fix(node): the answer log names its host addresses

aiortc ends a host candidate line at `typ host`, so the match on
" typ host " found none and logged `host: none` for every answer.

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

1 files changed, 0 insertions, 1 deletions

diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index 0160b97f..b720623a 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -4818,7 +4818,6 @@ process runs it — `systemctl --user` on Linux, Task Scheduler on Windows.
 | **A failed download leaves its in-flight chunks rejecting unhandled** | When `pipelinedDownload` throws, the other promises of its window are abandoned and each prints "Uncaught (in promise)" in the console. Noise, but in the log a dropped connection is read from |
 | **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 |
-| **The node logs `host: none` for every answer** | `webrtc_server.py` counts host candidates by `" typ host "` with a space after it, and aiortc ends those lines at `typ host`. Every answer in ten days of the test node's log read `host: none`, and it is the first thing read when a member reports "DataChannel closed": it sent the 2026-10-16 diagnosis the wrong way. A one-line fix and a test |
 | **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 |