docs(lxc110): incident DNS/OOM 2026-07-31 + zram pe pve1 + limite TTS

LXC 110 (moltbot) a picat dupa un OOM local containerului urmat de reboot:
tailscaled a ramas delogat, iar containerul mostenea resolv.conf-ul Tailscale
de la host-ul pve1 (doar MagicDNS 100.100.100.100) -> rezolutie DNS zero desi
L3 era functional -> echo-core in crash-loop pe telegram.error.TimedOut.

Fixuri aplicate:
- pct set 110 --nameserver '10.0.20.1 1.1.1.1' (elimina dependenta de Tailscale)
- zram-tools pe pve1 (8G zstd, prio 100) - `swap: 4096` din config era fictiv,
  host-ul nu avea niciun swap; root pe ZFS deci zram, nu swapfile
- MemoryHigh/MemoryMax pe pocket-tts + supertonic-tts - toate serviciile user
  rulau cu limite `infinity`, de unde OOM-uri recurente (Apr 25, May 28 x4)
  cu victime aleatorii alese dupa oom_score_adj

Documentatie:
- nou post-mortem in cluster/incidents/, adaugat in indexuri
- README lxc110: host corectat pveelite -> pve1 (+ RAM/CPU/storage reale),
  comenzile pct redirectionate spre nodul corect
- README lxc171: tabel cu starea swap pe cele 3 noduri (pveelite are zvol,
  nu zram - nu necesita acelasi fix)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

proxmox/README.md

@@ -10,7 +10,9 @@ proxmox/
 │   ├── README.md                      # Ghid SSH, HA, corosync tuning, diagnostic tools, mail relay, OOM alert
 │   ├── cluster-ha-monitor.sh          # Script monitorizare HA
 │   ├── incidents/                     # Post-mortems incidente cluster
-│   │   └── 2026-04-20-cluster-outage.md  # Cascadă OOM pveelite + USB LAN watchdog
+│   │   ├── 2026-04-20-cluster-outage.md  # Cascadă OOM pveelite + USB LAN watchdog
+│   │   ├── 2026-04-30-pvemini-backup-ssd-hang.md  # Kingston SSD hang → emergency mode
+│   │   └── 2026-07-31-lxc110-dns-tailscale-oom.md # DNS mort (Tailscale logout) + zram pe pve1
 │   └── ups/                           # Sistem UPS pentru cluster
 │       ├── README.md
 │       ├── docs/