Final PR of the post-migration contract sweep (ref #54, #55)
Independent review of #54 flagged that several Normal-sensitivity contracts (any registered agent may edit per AGENTS.md) still carried stale Mumuni CT100/.24 rows. All fixed here, all values verified live on kagentz:
Contract
Change
gpu-fleet
Key roster, Mumuni Agent Profile header + status table. (2026-07-02 thermal incident note left verbatim 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)
zulip-resilience-v3 line 423 historical audit row was annotated in #55
Open question flagged by reviewer (needs human/Abiba input)
zulip-health lists both 'Mumuni' and 'Agent Zero Docker host' as 192.168.68.14. Docker exists on kagentz but socket is not accessible to user hermes, so Agent Zero's presence there is unverified. Not changed in this PR.
Local lint: PASSED (same 15 pre-existing warnings).
## Final PR of the post-migration contract sweep (ref #54, #55)
Independent review of #54 flagged that several **Normal-sensitivity** contracts (any registered agent may edit per AGENTS.md) still carried stale Mumuni CT100/.24 rows. All fixed here, all values verified live on kagentz:
| Contract | Change |
|---|---|
| gpu-fleet | Key roster, Mumuni Agent Profile header + status table. (2026-07-02 thermal incident note left verbatim 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 | Gateway health-check target: root@.14 (kagentz CT105) |
| inference-optimization | `apply-agent-compression` host `.24` -> `.14`, config_path -> `/home/hermes/.hermes/config.yaml` |
### Still deliberately untouched (Abiba lane, per relay #739)
- `infrastructure-control.prose.md` (CRITICAL), `proxmox-monitor` (CRITICAL), `scripts/*.sh` (HIGH)
- Abiba-owned `.24` refs (pi agent, GPU monitor :9100, PM2)
- `zulip-resilience-v3` line 423 historical audit row was annotated in #55
### Open question flagged by reviewer (needs human/Abiba input)
`zulip-health` lists both 'Mumuni' and 'Agent Zero Docker host' as 192.168.68.14. Docker exists on kagentz but socket is not accessible to user hermes, so Agent Zero's presence there is **unverified**. Not changed in this PR.
Local lint: PASSED (same 15 pre-existing warnings).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Final PR of the post-migration contract sweep (ref #54, #55)
Independent review of #54 flagged that several Normal-sensitivity contracts (any registered agent may edit per AGENTS.md) still carried stale Mumuni CT100/.24 rows. All fixed here, all values verified live on kagentz:
/home/hermes/.hermes+ system unit/etc/systemd/system/hermes-gateway.service(was/root/.hermes+ user unit)apply-agent-compressionhost.24->.14, config_path ->/home/hermes/.hermes/config.yamlStill deliberately untouched (Abiba lane, per relay #739)
infrastructure-control.prose.md(CRITICAL),proxmox-monitor(CRITICAL),scripts/*.sh(HIGH).24refs (pi agent, GPU monitor :9100, PM2)zulip-resilience-v3line 423 historical audit row was annotated in #55Open question flagged by reviewer (needs human/Abiba input)
zulip-healthlists both 'Mumuni' and 'Agent Zero Docker host' as 192.168.68.14. Docker exists on kagentz but socket is not accessible to user hermes, so Agent Zero's presence there is unverified. Not changed in this PR.Local lint: PASSED (same 15 pre-existing warnings).