3 Commits

Include renames

Author	SHA1	Message	Date
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
root	0c976ddbf7	feat: add 2 new failure modes — rate limiting and streaming fallback ... - Rate limiting during reconnection (429): honor retry-after headers - Placeholder edit fails silently: fallback to sending as new message - Both fixes deployed to pi Zulip extension	2026-06-30 22:56:09 +00:00
root	4ee441f622	feat: zulip-adapter-lessons — document 8 known failure modes + deployment checklist ... Documents lessons from building pi Zulip extension and Hermes Zulip plugin: 1. Queue registration content-type 2. Missing bot_user_id for @mentions 3. Zero stream subscriptions 4. Stale errors never cleared 5. Stuck detection too aggressive 6. Env var name mismatch 7. Poll interval too aggressive 8. A2A port conflict Also: fixed Hermes adapter to clear stale errors on successful poll	2026-06-29 22:22:52 +00:00