Docs: shared checkout model, /etc/vanlink.conf references

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KqhjP7nud5gdBg25zCiRk9

ap/50-van-wan.yaml

@@ -10,7 +10,7 @@ network:
   version: 2
   ethernets:
     # Starlink dish uplink (RTL8153 USB NIC, MAC-named — travels with the
-    # adapter, see STARLINK_IFACE in deploy.conf). The /32 link route keeps the
+    # adapter, see STARLINK_IFACE in /etc/vanlink.conf). The /32 link route keeps the
     # dish's management address reachable no matter which WAN holds the
     # default route: the dish answers on 192.168.100.1 (gRPC :9200) even while
     # the uplink sits behind CGNAT.

ap/99-van-router-dns.conf

@@ -1,4 +1,4 @@
-# Fixed upstream resolvers for this router — see deploy.conf's DNS_RESOLVERS.
+# Fixed upstream resolvers for this router — see /etc/vanlink.conf's DNS_RESOLVERS.
 # Never the WAN-provided ones: the failover/60-van-wan-dns NM dispatcher
 # strips each WAN's DHCP/RA-provided DNS from resolved as soon as it appears
 # (NM's own ipv4/ipv6.ignore-auto-dns can't be set as a config-file default —

ap/hostapd-2g.service

@@ -1,5 +1,5 @@
 [Unit]
-Description=VanLink 2.4GHz AP (hostapd on @WIFI_2G_IFACE@ — see deploy.conf for current hardware)
+Description=VanLink 2.4GHz AP (hostapd on @WIFI_2G_IFACE@ — see /etc/vanlink.conf for current hardware)
 # Same USB re-enumeration hazards as the 5GHz AP (see hostapd-restart.conf for the
 # full story): never stop retrying, and back off a few seconds so the USB device can
 # re-enumerate before the next attempt.