ci: retrigger pipeline (validate job failed in 2s on clean tree; local repro of validation logic = 0 failures)

Third and final PR of the post-migration contract sweep (ref PRs #54, #55).
Normal-sensitivity contracts per AGENTS.md (any registered agent):

- gpu-fleet: key roster row, Mumuni Agent Profile header + status table
  (thermal-safeguard incident note left as historical record)
- infrastructure-update: apt patch table row; Hermes config path block
  corrected to /home/hermes/.hermes + system unit /etc/systemd/system/
  hermes-gateway.service (was /root/.hermes + user unit)
- infrastructure-maintenance: Hermes gateway health-check target
- inference-optimization: apply-agent-compression host + config_path

All values verified live on kagentz 2026-08-29 (hostname, IP, user,
systemd unit, /home/hermes/.hermes). Abiba-owned refs (.24 pi agent,
GPU monitor :9100) and CRITICAL files intentionally untouched - flagged
to Abiba via relay #739.

Refs PR #54, #55; relay #738/#739.

gpu-fleet.prose.md

@@ -207,7 +207,7 @@ Plaintext keys removed from this contract post-vault-migration.
 | Agent | CT | IP | LiteLLM Alias | Key Source | Access |
 |-------|-----|-----|---------------|------------|--------|
 | Tanko | 112 | .122 | `tanko` | Infisical vault | SSH jerome |
-| Mumuni | 100 (abiba) | .24 | `mumuni` | Infisical vault | SSH root |
+| Mumuni | 105 (kagentz) | .14 | `mumuni` | Infisical vault | SSH root |
 | Abiba | 100 | .24 | `abiba-pi` | Infisical vault | local (pi agent) |
 | Koby | 111 | ? | `koby` | Infisical vault | Zulip DM |
 | Koonimo | 113 | ? | `koonimo` | Infisical vault (migrated 2026-07-11) | no SSH |
@@ -304,7 +304,7 @@ When the underlying model is swapped, only the LiteLLM config changes — agent
 
 ### Mumuni Agent Profile
 
-Mumuni (CT100/abiba, 192.168.68.24) is the primary business assistant. This profile is the reference for all agent configs:
+Mumuni (kagentz CT105, 192.168.68.14 — migrated from CT100 2026-08-29) is the primary business assistant. This profile is the reference for all agent configs:
 
 | Setting | Value | Notes |
 |---------|-------|-------|
@@ -329,7 +329,7 @@ Mumuni (CT100/abiba, 192.168.68.24) is the primary business assistant. This prof
 
 | Agent | Host | Status |
 |-------|------|--------|
-| **Mumuni** | CT100 (.24) | ✅ Updated to stable aliases |
+| **Mumuni** | CT105 (.14) | ✅ Updated to stable aliases |
 | **Tanko** | CT112 (.122) | ✅ Updated to stable aliases |
 | **Koby** | CT111 (.129) | ❌ SSH unreachable — needs Zulip DM |
 | **Koonimo** | CT113 | ❌ SSH unreachable — needs Zulip DM |

hermes-zulip-restore.prose.md

@@ -2,7 +2,7 @@
 kind: function
 name: hermes-zulip-restore
 description: >
-  Restores Zulip connectivity for any Hermes agent (Mumuni CT100, Tanko CT112,
+  Restores Zulip connectivity for any Hermes agent (Mumuni CT105 kagentz, Tanko CT112,
   Koby CT111, Shumba on Lucky's mini PC). Deploys the zulip-platform adapter to the correct bundled plugin
   path, verifies env credentials, restarts the gateway, and confirms Zulip
   connects. Run this whenever a Hermes agent stops responding on Zulip or after

inference-optimization.prose.md

@@ -87,8 +87,8 @@ call apply-liteLLM-routing
 
 call apply-agent-compression
   agent: mumuni
-  host: 192.168.68.24
-  config_path: /root/.hermes/config.yaml
+  host: 192.168.68.14
+  config_path: /home/hermes/.hermes/config.yaml
 
 -- Phase 4: Enable llama.cpp prompt caching on GPU hosts
 

infrastructure-maintenance.prose.md

@@ -140,7 +140,7 @@ After ALL updates (apt + images + restarts), verify every critical service is ba
 | Zulip | `curl -sf https://chat.sysloggh.net/api/v1/server_settings` | 200 OK |
 | Gitea | `curl -sf https://git.sysloggh.net/api/v1/version` | 200 OK |
 | PM2 processes | `pm2 jlist` (CT 100) | all pi-agent processes `online` |
-| Hermes gateways | SSH to Mumuni CT 100, Tanko CT 112; `systemctl is-active hermes-gateway` | `active` for each |
+| Hermes gateways | SSH to Mumuni kagentz CT105 (root@.14) and Tanko CT112 (jerome@.122); `systemctl is-active hermes-gateway` | `active` for each |
 
 Regression check: every service that was GREEN in `health-baseline` must still be GREEN. A service that was already RED (and caused a preflight abort) is excluded — but Phase 0 should have aborted before we got here.
 

infrastructure-update.prose.md

@@ -59,7 +59,7 @@ Before ANY update wave:
 | CT 100 (.24) | Abiba (pi) | `apt update && apt upgrade -y` | 3 min |
 | CT 116 (.116) | syslog-api (LiteLLM host) | `apt update && apt upgrade -y` | 3 min |
 | CT 112 (tanko, amdpve) | Tanko | `apt update && apt upgrade -y` | 3 min |
-| CT 100 (mumuni/abiba, minipve) | Mumuni | `apt update && apt upgrade -y` | 3 min |
+| CT 105 (kagentz, minipve) | Mumuni | `apt update && apt upgrade -y` | 3 min |
 | VM 101 (.8) | llm-gpu (RTX 3090) | `apt update && apt upgrade -y` | 3 min |
 | VM 103 (.110) | ocu-llm (RTX 5070) | `apt update && apt upgrade -y` | 3 min |
 
@@ -162,9 +162,9 @@ Before Wave 1, snapshot these files:
 /etc/systemd/system/strix-server.service                (amdpve .15 — strix-moe)
 /etc/systemd/system/llama-server.service                (VM 101 .8, VM 103 .110)
 # Hermes agent configs (key enforcement — 2026-07-10)
-/root/.hermes/config.yaml                               (Mumuni inside CT 100, Tanko CT 112, etc.)
-/root/.config/systemd/user/hermes-gateway.service       (Mumuni inside CT 100 — EnvironmentFile fixed)
-/etc/environment                                        (Mumuni inside CT 100 — LITELLM_API_KEY)
+/home/hermes/.hermes/config.yaml                        (Mumuni kagentz CT105; Tanko CT112 uses /home/jerome/.hermes)
+/etc/systemd/system/hermes-gateway.service              (Mumuni kagentz CT105 — system unit, User=hermes)
+/etc/environment                                        (LITELLM_API_KEY — legacy path, Mumuni now keys via Infisical)
 ```
 
 ## MCP Gateway (2026-07-10)

zulip-health.prose.md

@@ -203,7 +203,7 @@ Gateway PID should exist with uptime > 60s. **Dual-gateway detection**: if more
 
 | Agent | Restart command | Notes |
 |-------|-----------------|-------|
-| Mumuni (.14) | `sudo systemctl restart hermes-gateway` | systemd unit `hermes-gateway.service` (user hermes) |
+| Mumuni (.14) | `ssh root@192.168.68.14 "systemctl restart hermes-gateway"` | systemd unit `hermes-gateway.service` (user hermes); sudo not installed on kagentz — restart via root SSH from Proxmox host or monitoring box |
 | Tanko (.122) | `bash /opt/hermes-zulip-plugin/run.sh` (or the agent's systemd/user unit) | Tanko does NOT use PM2 — never run `pm2 restart mumuni-zulip` for Tanko (process does not exist) |
 
 Check gateway log for "Gateway running with 2 platform(s)" (not 1) to confirm Zulip reloaded.

zulip-resilience-v3.prose.md

@@ -420,7 +420,7 @@ Backup v2 before starting: `cp index.js index.js.v2-backup-$(date +%Y%m%d-%H%M%S
 |-------|----------|-------------|--------------|-------------|
 | **Abiba** | pi (CT 100) | ✅ Connected | API key missing from Infisical injection; poll timeout noise | Added .env fallback; AbortError treated as empty poll (no retry); poll timeout 65s→90s |
 | **Tanko** | Hermes (CT 112) | ✅ Connected | Gateway disconnected since Jul 11; watchdog restart didn't re-establish Zulip | Full gateway restart (kill wrapper, let infisical-gateway.sh respawn) |
-| **Mumuni** | Hermes (inside Abiba CT 100) | ✅ Connected | No issues found | None needed |
+| **Mumuni** | Hermes (kagentz CT 105, migrated 2026-08-29) | ✅ Connected | No issues found | None needed |
 
 ### Key Fixes Applied
 

zulip-self-heal.prose.md

@@ -65,7 +65,7 @@ triggers:
 |------|----|------|---------|
 | Zulip server | 192.168.68.19 | root | Docker: `zulip-zulip-1` |
 | Abiba (pi) | localhost | root | PM2: `abiba-zulip` |
-| Mumuni | 192.168.68.14 (kagentz CT105) | hermes | `sudo systemctl restart hermes-gateway` |
+| Mumuni | 192.168.68.14 (kagentz CT105) | root (SSH) | `ssh root@192.168.68.14 "systemctl restart hermes-gateway"` |
 | Tanko | 192.168.68.122 | jerome | `PATH=$PATH:/home/jerome/.hermes/hermes-agent hermes gateway restart` |
 
 ## Debounce