12 Commits

Include renames

Author	SHA1	Message	Date
abiba-bot	c66d9c1e20	fix: probe-drift round 2 — stale monitoring expectations (health check, PVE API, GPU port 80, report provenance) ... Second probe-drift correction pass after #65/#66/#68. All four legs were stale consumer expectations, not live faults. 1. scripts/agent-health-check.py (v4) - abiba declared pi-only runtime (harness purge): Hermes-era gateway, config and wrapper legs are skipped instead of failing. - koby declared report_only (captain ruling 2026-08-17, Rule 17): every koby leg is detected and reported, never counted as a fleet failure or repaired. - koby's CT 111 mapping corrected to storepve (.6); the old amdpve mapping made `pct status 111` fail and read as ct-unreachable. - wrapper check no longer FAILs .env-based wrappers that legitimately never invoke infisical (koonimo). - keys load in main() (load_agent_keys) so the module is importable/testable. - every run prints absolute execution provenance (script + cwd), in the header and in --json. Before: 6 FAILURE(S). After: 0 failures, koby reported read-only. 2. infrastructure-monitoring.prose.md - PVE API probe repointed from CT 116 (no pveproxy, 000) to the five real nodes on https://<node>:8006/api2/json/version, all 401 = alive. - any-HTTP-response liveness rule added (401/3xx alive; 000/timeout = DOWN). - LiteLLM health documented as 301 -> /litellm/health/liveliness, not bare 200. 3. gpu-monitor.prose.md - GPU health probes on :8080 (or router /health/unified); bare port 80 on a GPU host is forbidden (no listener -> false DEGRADED). - router /health/unified 301 -> /gpu/gpu-data documented as alive. - port-discipline + liveness rule + direct-fallback execution step. 4. Report provenance (all contracts) - docs/AUTHORING-GUIDE.md documents the rule; scripts/prose-lint.sh enforces that any **Report format** contract states an absolute path (pwd -P). - provenance added to gpu-monitor, infrastructure-monitoring, proxmox-monitor. Tests: tests/test_probe_drift.py (23 passed); prose-lint.sh clean + shellcheck clean; CI frontmatter validation passes. Evidence with per-leg before/after and absolute paths: docs/probe-drift-round2-evidence.md.	2026-09-10 01:23:54 +00:00
root	801de0a25c	fix: correct proxmox-monitor probe endpoints to use localhost for exporters ... Docker Stats and PVE Exporter are bound to 127.0.0.1 (localhost-only), not 0.0.0.0. They must be probed from .116 via SSH. Prometheus and Grafana remain 0.0.0.0 (LAN-reachable). Fixes false alarm from remote probe showing connection-refused (by design for localhost binds).	2026-09-08 08:41:21 +00:00
root	36ae464f59	fix: probe alignment across multiple monitoring contracts ... - infra-monitoring: Added Router+LiteLLM+PVE API probes with expected HTTP codes (200/401/500) - gpu-monitor: Added explicit check-health section with Router+LiteLLM probe commands - proxmox-monitor: Added check-health section for Prometheus/Grafana/exporters (all bound to 0.0.0.0) - zulip-health: Fixed A2A port from :8001 to :50080 and added auth-gated expectation (401) Closes: infra-monitoring-probe-alignment, gpu-monitor-probe-alignment, proxmox-monitor-probe-alignment, zulip-health-probe-alignment	2026-09-08 07:20:41 +00:00
kagentz-bot	44f7008302	docs: reflect hwepve removal from Tabiri cluster (5 nodes + standalone London node) ... - Remove hwepve from cluster member lists/diagrams in infrastructure-control, proxmox-monitor, infrastructure-update, litellm-health, mumuni-delegation - CTs 100 (abiba) and 105 (kagentz) moved to minipve; CT 114 (mumuni) no longer exists (Mumuni runs inside Abiba CT 100) - Add standalone London role + NetBird routing peer description for hwepve - Update scripts: agent-health-check.py, pct-run.sh, prose-ai-review.sh - Update disk-gc CT access table, hermes baselines/restore host references	2026-08-15 20:03:02 -04:00
root	7d1db62a8e	no-mistakes(document): Fix stale CT placements across 5 docs matching infrastructure-control updates	2026-07-24 20:21:03 +00:00
root	767ab25128	merge: resolve PR #26 conflict — keep qwen model ref + add hwepve node	2026-07-23 18:10:18 +00:00
root	1c44bf1259	contract updates: ornith decommissioned, 256K→128K context, Mumuni Discord disabled ... Change 1: Strix Halo — ornith decommissioned - gpu-fleet: Genesis Hermes V3 APEX → qwen3.6-35B-udq4 throughout - inference-optimization: ornith→strix-moe/qwen3.6-35B-udq4 - gpu-monitor: ornith status → Strix Halo status - infrastructure-control: Strix Halo — ornith → qwen3.6-35B-udq4 - infrastructure-update: ornith→strix-moe via router - proxmox-monitor: Strix Halo LLM (ornith) → (qwen3.6-35B-udq4, strix-moe) Change 2: GPU context 256K→128K fleet-wide - hermes-agent-baseline: frontmatter description updated - litellm-health: GPU Fleet Topology table 256K→128K - litellm-self-heal: GPU Fleet Topology, engine flags, VRAM alert - inference-optimization: compress threshold 256K→128K compact at 85K - gpu-fleet: instability note updated Change 3: Mumuni Discord platform disabled - gpu-fleet: Mumuni platforms: removed discord	2026-07-23 09:00:42 +00:00
root	9f0e04f22c	fix: update contracts for hwepve 6th node + Mumuni migration (lxc/114 on hwepve) ... - proxmox-monitor: 5→6 nodes, add hwepve (.4, Huawei Matebook 16), note Mumuni (lxc/114) placement - zulip-health: add dual-gateway collision detection to B2, note Mumuni on hwepve - hermes-agent-baseline: fix Mumuni node minipve→hwepve - hermes-zulip-restore: add hwepve Proxmox column for Mumuni - mumuni-delegation: fix CT 118/storepve/.6 → lxc/114/hwepve/.123, 5→6 nodes - pm2-self-heal: verified — no Mumuni references, no changes needed Post-migration discoveries: - Mumuni container migrated from minipve to hwepve (6th node, 192.168.68.4) - IP preserved (192.168.68.123), hostname 'mumuni' unchanged - Dual gateway collision (PID 1442 --replace + PID 2924 --force) resolved by container restart at 10:07; gateway restarted clean at 13:06 with fresh Zulip queue (errors=0, reconnects=0)	2026-07-20 17:08:58 +00:00
root	79d4a73895	docs: lessons learned from 2026-07-12 session ... - gpu-fleet: Corrected architecture (direct GPU, no router in path). Updated context values (RTX 3090=256K, not 128K). Added api-key standardization requirement. - gpu-self-heal: Added Lessons Learned section with 5 critical findings: L1: API key standardization (RTX 5070 sk-loc...5678 vs not-needed) L2: Fallback chain cascading failure loop detection L3: Verify running state, not documentation L4: Infisical fallback requirement (.env must have uncommented key) L5: Zulip event queue can silently die after ~40 reconnects - litellm-self-heal: Updated status manual-only→deployed, cron schedule - litellm-api-keys: Added Infisical token expiry warning + .env fallback - hermes-config-template: Rule 3 updated with .env fallback requirement	2026-07-12 22:49:39 +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
root	3700b3bf46	prose: fix proxmox-monitor access to direct :3001 (revert sub-path) ... Revert the /grafana/ nginx sub-path I wrongly added — it broke the existing http://192.168.68.116:3001/d/gpu-fleet URL. Restored direct 0.0.0.0:3001 LAN access. Contract is now the source of truth: no GF_SERVER_SERVE_FROM_SUB_PATH, no nginx /grafana/ route. gpu-fleet + 3 new dashboards all at :3001.	2026-07-02 02:56:27 +00:00
root	4df2fa8329	prose: add proxmox-monitor contract (Grafana Pulse replacement) ... - New proxmox-monitor.prose.md: pve-exporter + node_exporter(5) + docker-stats-exporter - Replaces Pulse with file-provisioned Grafana dashboards (cluster/node/docker) - Documents cAdvisor/Docker-29 incompatibility + custom exporter workaround - PVE API token, access URL, config file map, operations	2026-07-02 02:50:59 +00:00