docs(hermes): document namespace addressability and fix stale claims

New page Architecture/Container Network Namespaces.md: which local services are
addressable from which Podman network namespace on Dankclaw (rootless podman +
netavark). Verified live 2026-09-02: gateway/webui/CDP run in the host netns and
dial loopback; hermes-dashboard is the only Hermes container on a bridge network
(dankclaw_default, 10.89.1.0/24 gw 10.89.1.1) and can dial published ports only —
unpublished host-netns listeners (signal-cli :8080, webui :8787) are refused from
that namespace even though both bind 0.0.0.0.

Corrected while verifying the above:
- Hermes.md: data root is /home/dank/Containers/hermes/data (not the retired
  /home/dank/hermes-data); gateway dials the Signal daemon on loopback; the
  daemon itself is a host user unit (signal-cli-daemon.service) bound to
  0.0.0.0:8080, so the Signal HTTP API is LAN-reachable.
- Hermes-Dashboard.md: it is a Quadlet unit (Network=dankclaw_default), not a
  compose service; data root + /opt/data anonymous volume corrected.
- Hermes-WebUI.md: binds 0.0.0.0:8787 in the host netns (verified: unauthenticated
  GET /health from another LAN machine returned 200) — the SSH tunnel is an access
  path, not a containment boundary; HealthCmd and data-path corrections.
- Network Architecture.md: no hermes vhost exists in either the tracked or the live
  Caddyfile (hermes.franksdank.cloud resolves but routes nowhere); SearXNG exits the
  tunnel via the shared named network searxng.network, not service:gluetun.

Docs only — deploy is a no-op for this change.

serverAppConfigs-docs/Architecture/Network Architecture.md

@@ -28,7 +28,6 @@ graph TB
         AUTH -->|session valid, provider internal_host| POST[Caddy post-auth listener :8017]
         POST --> HOME[Homepage file_server]
         POST --> SEARCH[SearXNG via Gluetun netns :8081]
-        POST --> HERMES[Hermes :8090]
         POST --> PROM[Prometheus :9090]
         DIRECT -->|3000 + ssh 2222| GITEA[Gitea]
         DIRECT -->|3005| OWEBUI[OpenWebUI]
@@ -56,7 +55,7 @@ graph TB
     DIRECT --> ARR
 ```
 
-Guarded (through Anubis): homepage, search, hermes, prometheus, romm, files.
+Guarded (through Anubis): homepage, search, prometheus, romm, files.
 Exempt by construction: `auth.` (the IdP login itself), plex (plain HTTP),
 gitea (git smart-HTTP clients cannot solve JS challenges — `/info/refs` and
 `git-*-pack` pass unchallenged), grafana (own auth).
@@ -78,7 +77,14 @@ Caddy holds one Let's Encrypt certificate per vhost, issued and renewed through
 
 ## Gluetun Path (SearXNG only)
 
-SearXNG attaches to the Gluetun network namespace (`network_mode: service:gluetun`). Only SearXNG shares the tunnel. Everything else on Dankclaw uses the normal LAN route. This matches KB Pattern 2 in [[Gluetun]].
+`gluetun.container`, `searxng.container` and `searxng-valkey.container` all set
+`Network=searxng.network` in their Quadlet sources (runtime network
+`systemd-searxng`); only those three share the tunnel. The old compose idiom
+(`network_mode: service:gluetun`) is gone — a shared named network is what
+carries SearXNG's outbound traffic through the VPN exit. Everything else on
+Dankclaw uses the normal LAN route. This matches KB Pattern 2 in [[Gluetun]].
+See [[Container Network Namespaces]] for which addresses are reachable from that
+namespace (none of the unpublished host-netns listeners).
 
 ## Access Policy
 
@@ -92,4 +98,5 @@ SearXNG attaches to the Gluetun network namespace (`network_mode: service:gluetu
 - [[Caddy]] — vhost map, TLS, basic auth
 - [[Dankserver Stack]], [[Dankclaw Stack]]
 - [[Gluetun]]
-- Knowledge base: [[Gluetun]], [[SearXNG]]
+- Knowledge base: [[Gluetun]], [[SearXNG]]
+- [[Container Network Namespaces]] — who can dial what on Dankclaw (host netns vs bridge nets)