2 Commits

Include renames

Author	SHA1	Message	Date
abiba	672bf8a912	docs(disk-gc): attach real fleet-run verification for the CT 111 report-only gate ... Intent requires a production run log, not only the unit-level dry run. This is a real scan of the live 25-entry fleet through scripts/disk-gc-plan.py: CT 111 (tdunna) at 84% AMBER is alerted as report-only and no gc-executor row is emitted for it; the owned hosts acerpve .9 (77%) and amdpve .15 (76%) still receive gc-executor. No GC command was run against 192.168.68.129.	2026-09-12 19:11:36 +00:00
root	253e19f680	prose: review, fix, and consolidate infrastructure contracts ... - DELETE infrastructure-monitoring.prose.md (redundant — proxmox-monitor already deployed this) - FIX infrastructure-control.prose.md: remove /grafana/ nginx route (reverted Jul 2, broke gpu-fleet) - FIX infrastructure-update.prose.md: wrong CT IDs (122→112 Tanko, 123→114 Mumuni, .19→storepve Zulip) - FIX infrastructure-update.prose.md: Strix Halo :8080→router health check (firewalled to .116 only) - FIX proxmox-monitor.prose.md: stale /grafana/ URLs→:3001 (post-revert cleanup) - ADD disk-gc-threat-response.prose.md: verified run (2026-07-04, reclaimed 35.67GB from kagentz) - ADD infrastructure-update.prose.md, pi-approval-architecture.prose.md, zulip-approval-fix.prose.md, zulip-self-heal.prose.md - UPDATE hermes-config, litellm-health/self-heal, pm2-self-heal, zulip-* contracts - ADD runs/20260704-005804-51f9a9 (disk-gc-threat-response run artifacts) All contracts verified against live PVE API, nginx config, and firewall state.	2026-07-04 21:47:33 +00:00