disk-gc report-only verification — CT 111 / tdunna / 192.168.68.129 date: 2026-09-12T19:11:36Z host: abiba (this scanner runs INSIDE CT 100 / abiba) branch head: 6e612ce37b1b9a9688b04e7f816848e7a4185fca command: scripts/disk-gc-plan.py --scan PURPOSE: prove that on a REAL fleet scan, CT 111 is alerted and NO gc-executor action is emitted for it at any level. No GC command was executed against .129. --- live fleet scan (df -P / via scripts/pct-run.sh for LXC, direct SSH for hosts) --- tdunna 84% acerpve 192.168.68.9 77% amdpve 192.168.68.15 76% ocu-llm 192.168.68.110 69% storepve 192.168.68.6 65% kagentz 61% tanko 56% minipve 192.168.68.12 49% authentik 45% infisical-vault 39% adguard 38% ocupve 192.168.68.5 38% scottdenya 35% syslog-api 34% llm-gpu 192.168.68.8 25% abiba 23% baggy 22% jdownloader 21% gitea 16% ra-h-os 13% zulip 12% docker-vm 192.168.68.7 11% adguard2 10% media 9% proxmox-backup-server 4% --- planner output (action plan) --- 111 AMBER 84.0% -> REPORT-ONLY (no GC) — Theo's box — captain ruling 2026-08-17, re-confirmed 2026-09-10 acerpve AMBER 77.0% -> gc-executor amdpve AMBER 76.0% -> gc-executor --- verdict --- CT 111 (tdunna) 84% AMBER -> report-only; no gc-executor row emitted; no GC run on .129. Owned hosts acerpve .9 (77%) and amdpve .15 (76%) -> gc-executor (ours).