docs: R-66 shipped (ROADMAP + NAS naming caveat); mint R-64 pairing-blessed + R-65 buddy-box replication

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UuFPHmHNrCJj1VhY6QdDMU

documentation/controller/network-storage-nas.md

@@ -107,6 +107,16 @@ with a hint; the rollback still runs.
   unmapped and fails on others-perms. The consumer recipe REQUIRES the map-ALL-users mode; an
   anonymous-uid field alone does nothing. The UI's `not_writable` message and the guidance block
   tell this same story.
+- **Naming caveat (R-66, controller v0.159.0): Windows network names („FELHOM") generally do NOT
+  resolve here.** The Szerver field takes an IP or a DNS name; NetBIOS/WSD flat-name resolution is
+  Windows machinery the guest deliberately does not run (the R-6 LAN-discovery spike: the docker
+  bridge is deaf, and nothing NetBIOS-resolves on the mount path). The add form's helper text says
+  so under the field, and an `unreachable`-class failure for a single-label non-IP server appends a
+  purely lexical hint („Tipp: a(z) »FELHOM« Windows-hálózati névnek tűnik — használja az eszköz
+  IP-címét") — no NetBIOS/mDNS resolution is ever attempted. Where the customer FINDS the peer
+  Felhom box's address: the serving box's **Megosztás** page („közvetlen cím" row) or its
+  **Beállítások → Rendszer → „Hálózat"** card (Helyi cím) — both live-computed per render, never
+  stored (S-5), so they are current by construction.
 
 ## Health model