docs: top-10 fixes (PORTMAP, storage truth, banners, AdGuard scrub, zoraxy UCI removed, CT 111 section, Daytona purge)

services/adguard-dns.md

@@ -5,7 +5,7 @@ AdGuard DNS at `192.168.1.2` can handle internal domain resolution, eliminating
 
 ## Current Setup
 - **AdGuard URL**: `http://192.168.1.2`
-- **Status**: Running on Proxmox VM 102
+- **Status**: Running on Proxmox **LXC 102** (`dns`, 192.168.1.2)
 - **Homepage widget**: Configured
 
 ## AI Service DNS Entries
@@ -48,7 +48,8 @@ Add these static DNS entries in AdGuard to resolve AI services locally:
 # Get session token first
 curl -c /tmp/cookies.txt -k -X POST http://192.168.1.2:3000/ \
   -H "Content-Type: application/json" \
-  -d '{"username": "root", "password": "tapirnase"}'
+  -d "{\"username\": \"root\", \"password\": \"${ADGUARD_PASSWORD}\"}"
+# Export ADGUARD_PASSWORD from your shell env or a `.env` file — never hardcode.
 
 # Add static DNS entry
 curl -s -k -c /tmp/cookies.txt -b /tmp/cookies.txt \
@@ -115,8 +116,8 @@ echo "✅ Done! Add these in AdGuard UI manually."
 - `pp-api.nuclide.systems` → `192.168.1.40:8000` (Paperless API)
 
 ### Home Assistant
-- `ha.nuclide.systems` → `192.168.1.10` (Home Assistant)
-- `homeassistant.local` → `192.168.1.10` (mDNS fallback)
+- `ha.nuclide.systems` → `192.168.1.60` (Home Assistant OS VM 100)
+- `homeassistant.local` → `192.168.1.60` (mDNS fallback)
 
 ## Internal DNS Server Setup
 
@@ -200,7 +201,7 @@ S3_ENDPOINT=https://s3.nuclide.systems
 
 ## Notes
 
-- AdGuard runs on VM 102 at `192.168.1.2`
+- AdGuard runs on **LXC 102** at `192.168.1.2`
 - All AI services run on `192.168.1.40`
 - Using same IP for all domains is intentional (single endpoint)
 - SSL certs are issued by Zoraxy (public domain validation)