10 Commits

Include renames

Author	SHA1	Message	Date
root	287657a77a	Merge remote-tracking branch 'origin/master' into update/docker-ecosystems-20260908	2026-09-10 23:01:32 +00:00
root	21f9073e0b	fix(daily-infra-report): use pve_probe_status in render + add regression tests (PR #64 round 2)	2026-09-10 23:01:18 +00:00
root	32fe7c0652	fix(daily-infra-report): complete Zulip nested-key fix + Proxmox port/auth fix (PR #64 review fix 1-2)	2026-09-10 22:03:48 +00:00
root	25cf2f5eef	fix(daily-infra-report): read Zulip state from nested 'zulip' key (PR #64 fix 3a)	2026-09-10 20:55:17 +00:00
abiba-bot	8a4ee4cf5a	no-mistakes(review): Pin Mumuni removal behaviorally and fix digest import bug	2026-09-10 10:18:38 +00:00
abiba	952fca9c92	fix(monitoring): retire the Mumuni leg — stop probing her decommissioned .24 deployment ... Captain ruling 2026-09-10: Mumuni moved off this host onto her own container (kagentz CT 105 on minipve, 192.168.68.14, dedicated `hermes` user) and is monitored from her side. This host must not monitor anything Mumuni. The stale probes fired false alerts repeatedly: * scripts/zulip-monitor.sh ssh'd to root@192.168.68.24 for the decommissioned deployment's ~/.hermes/gateway_state.json, read "unknown" on every run, and posted a 🔴 "Mumuni (Hermes) Zulip state: unknown" DM + #agent-hub stream alert each cycle. * scripts/daily-infra-report.py published a matching "mumuni:unknown" row in every digest. Changes: * zulip-monitor.sh: delete the "Platform B: Hermes (Mumuni)" leg and its notify; keep the Zulip-server, Platform A pi/Abiba (bridge), Platform B Tanko and Platform C Agent Zero legs. A comment records why the leg is retired so it is not re-added. Also fixes SC2155 so shellcheck is clean. * daily-infra-report.py: delete the .24 ~/.hermes/gateway_state.json agent probe, its hermes --version probe, and the now-dead mumuni render branch. Abiba (CT 100, its own .24 address) and Tanko legs unchanged; the PVE API token name is untouched. * zulip-health.prose.md (v3.1.0): drop the Mumuni-only B4 gateway-process, B5 heartbeat and B6 response-delivery steps and the stale 192.168.68.24 references; state explicitly that Mumuni is not monitored from this host. Tanko/Agent-Zero/bridge steps retained. * agent-health-check.py: correct the v2 changelog roster comment that still placed mumuni at .24/CT100. No behavior change — the mumuni probe was already absent from the AGENTS dict; v5 changelog notes the correction. Tests: tests/test_mumuni_monitor_removal.py pins the removal structurally and behaviorally — the shipped zulip-monitor.sh is run in a sandbox (only its LOG constant rewritten) with stub ssh/curl on PATH; the ssh stub records every target host, so "never reaches .24" and "no Mumuni notify even on the alert path" are asserted from observed behavior. A mutation check (re-inject the old leg) fails the suite, so the guarantee is not vacuous.	2026-09-10 10:11:19 +00:00
root	79af0ae7a3	Merged PR #52: fix/tanko-runtime	2026-08-30 12:16:28 +00:00
Agent Zero	19a67c6815	fix: align mumuni ct field to 100 in daily-infra-report.py	2026-08-15 20:12:09 -04:00
root	b3193e5e1b	fix(agent-health): 14 stale-reference fixes (Mumuni CT100/.24, Koby .129, Koonimo CT113, wrapper paths)	2026-08-01 14:10:52 +00:00
root	90e074dbcc	feat(zulip-health): monitor script + infra report — cron-ready implementations of prose contracts	2026-06-27 19:22:53 +00:00