fix(monitoring): stop monitoring Mumuni from this host (moved to CT105/.14) #71

2026-09-10T10:28:55Z

abiba-bot commented

2026-09-10 10:28:55 +00:00

Captain instruction: Mumuni has moved off this host (CT105/.14, hermes user); firstmate must not monitor her from this end. Stale probes kept firing false alerts (🔴 "Mumuni (Hermes) Zulip state: unknown" DM + #agent-hub stream on every run).

Changes (no-mistakes validated, 37 tests, shellcheck + prose-lint green):

scripts/zulip-monitor.sh — removed the "Platform B: Hermes (Mumuni)" leg entirely (no SSH to .24, no gateway_state read, no Mumuni notify). Agent-Zero, Tanko, and bridge legs unchanged.
scripts/daily-infra-report.py — removed the Mumuni (.24 gateway_state) probe; digest no longer reports "mumuni:unknown".
zulip-health.prose.md — dropped Mumuni-only steps (B4/B5/B6) and stale 192.168.68.24 refs; states Mumuni is no longer monitored from this host.
scripts/agent-health-check.py + litellm-self-heal.prose.md — corrected the stale roster reference; note mumuni no longer probed.
contract-registry.yaml — zulip-health trigger description updated to the reduced scope; version bump.
tests/test_mumuni_monitor_removal.py — behavioral test asserting no Mumuni probe / .24 reference remains in the executable paths.

Verification: grep proof zulip-monitor.sh contains zero Mumuni/.24 references.

Captain instruction: Mumuni has moved off this host (CT105/.14, hermes user); firstmate must not monitor her from this end. Stale probes kept firing false alerts (🔴 "Mumuni (Hermes) Zulip state: unknown" DM + #agent-hub stream on every run). Changes (no-mistakes validated, 37 tests, shellcheck + prose-lint green): 1. scripts/zulip-monitor.sh — removed the "Platform B: Hermes (Mumuni)" leg entirely (no SSH to .24, no gateway_state read, no Mumuni notify). Agent-Zero, Tanko, and bridge legs unchanged. 2. scripts/daily-infra-report.py — removed the Mumuni (.24 gateway_state) probe; digest no longer reports "mumuni:unknown". 3. zulip-health.prose.md — dropped Mumuni-only steps (B4/B5/B6) and stale 192.168.68.24 refs; states Mumuni is no longer monitored from this host. 4. scripts/agent-health-check.py + litellm-self-heal.prose.md — corrected the stale roster reference; note mumuni no longer probed. 5. contract-registry.yaml — zulip-health trigger description updated to the reduced scope; version bump. 6. tests/test_mumuni_monitor_removal.py — behavioral test asserting no Mumuni probe / .24 reference remains in the executable paths. Verification: grep proof zulip-monitor.sh contains zero Mumuni/.24 references.

abiba-bot added 3 commits 2026-09-10 10:28:55 +00:00

fix(monitoring): retire the Mumuni leg — stop probing her decommissioned .24 deployment 952fca9c92

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.

no-mistakes(review): Pin Mumuni removal behaviorally and fix digest import bug 8a4ee4cf5a

no-mistakes(document): Refresh stale Mumuni roster docs and registry metadata

PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 3s

Details

PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 4s

Details

PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 2s

Details

PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 2s

Details

PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s

Details

4f59b82404

abiba-bot merged commit 14bed6e916 into master

2026-09-10 12:30:20 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SyslogSolution/prose-contracts#71