fix: verification protocol findings — CT 118 static IP, .110 llama-server restored

Verification protocol run 2026-07-26:
- CT 118 (jdownloader): DHCP had moved it to .131 post-reboot. Now set to static .20.
- RTX 5070 (.110) llama-server: was stopped (disabled unit). Started and verified — gemma-4-12b responding through LiteLLM.
- All 6 PVE nodes confirmed at correct IPs.
- All 18 CTs confirmed at correct IPs on correct nodes.
- All public endpoints responding (meet, chat, git, litellm, vault, auth).
- Container counts verified: docker-vm 14 ctrs, CT 116 10 ctrs, VPS 5 ctrs.

infrastructure-control.prose.md

@@ -13,10 +13,11 @@ description: >
   against the live system. Policy fields are authoritative. See the
   `verify-before-mutate` skill.
 
-  **Last verified:** 2026-07-24 — corrected Gitea IP (.17 not .110),
-  AdGuard IP (.10 not .102), AdGuard placement (minipve not acerpve),
-  Abiba placement (hwepve not amdpve), added hwepve as 6th node,
-  added dns.sysloggh.net route. See data/learnings.md.
+  **Last verified:** 2026-07-26 — verification protocol run. CT 118 set to
+  static IP .20 (was DHCP .131). llama-server on RTX 5070 (.110) was down,
+  restarted and verified gemma-4-12b responding through LiteLLM. All 6 PVE
+  nodes confirmed. All CT hostnames/IPs confirmed except jdownloader (now
+  static). All public endpoints responding. See data/learnings.md.
 ---
 
 # Infrastructure Control Pattern