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.

zulip-mention-reliability.prose.md

@@ -1,13 +1,18 @@
 ---
 kind: responsibility
 name: zulip-mention-reliability
+status: retired
 description: >
-  Monitors whether Abiba Bot is correctly detecting and responding to
-  @mentions in Zulip stream topics. Tests periodically, diagnoses
-  failures, and attempts fixes. Same self-improving pattern as
-  litellm-self-heal.
+  RETIRED 2026-07-04 — Zulip extension decommissioned. Abiba now operates
+  exclusively through Telegram (@AbibaBot). This contract is kept for
+  historical reference only.
 ---
 
+> **⚠️ RETIRED** — The pi Zulip extension (`~/.pi/agent/extensions/zulip/`) and
+> PM2 process (`abiba-zulip`) have been decommissioned. All mention/reliability
+> monitoring now happens through Telegram. Hermes agents (Tanko, Mumuni) and
+> Agent Zero (kagentz) continue to use Zulip.
+
 ## Maintains
 
 - mention_response_rate: number — % of @mentions that get a response (target: >95%)