Ran the consolidated litellm-self-heal health check against production infra.
IP drift (pi is .24, not .65)
The pi host IP was inconsistently documented. gpu-fleet topology diagram correctly showed .24, but the config files table and gpu-monitor contract said .65 (which is actually ra-h-os bridge).
Container count (10, not 8)
CT 116 runs 10 Docker containers. The contract only listed 8 — missing harness-docker-stats and harness-pve-exporter (both Prometheus exporter sidecars).
Verified working
All 10 containers healthy
All 3 models inference-ready (gemma, qwen, ornith)
GPU monitor restarted on .24:9100
Grafana + Prometheus responding
## Found by live testing
Ran the consolidated litellm-self-heal health check against production infra.
### IP drift (pi is .24, not .65)
The pi host IP was inconsistently documented. gpu-fleet topology diagram correctly showed .24, but the config files table and gpu-monitor contract said .65 (which is actually ra-h-os bridge).
### Container count (10, not 8)
CT 116 runs 10 Docker containers. The contract only listed 8 — missing harness-docker-stats and harness-pve-exporter (both Prometheus exporter sidecars).
### Verified working
- All 10 containers healthy
- All 3 models inference-ready (gemma, qwen, ornith)
- GPU monitor restarted on .24:9100
- Grafana + Prometheus responding
Testing the consolidated litellm-self-heal contract against live infra found:
- IP drift: pi host is .24, not .65 (confused with ra-h-os bridge)
- Fixed gpu-monitor.prose.md: 192.168.68.65 → 192.168.68.24 (3 locations)
- Fixed gpu-fleet.prose.md: .65 → .24 in config files + agent keys tables
- Container count: 10 running on CT 116, not 8 as contract stated
- Added harness-docker-stats + harness-pve-exporter to litellm-self-heal
- Updated container health check list
Verified: GPU monitor restarted on .24:9100, ornith model inference working,
all 10 containers healthy.
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.
Found by live testing
Ran the consolidated litellm-self-heal health check against production infra.
IP drift (pi is .24, not .65)
The pi host IP was inconsistently documented. gpu-fleet topology diagram correctly showed .24, but the config files table and gpu-monitor contract said .65 (which is actually ra-h-os bridge).
Container count (10, not 8)
CT 116 runs 10 Docker containers. The contract only listed 8 — missing harness-docker-stats and harness-pve-exporter (both Prometheus exporter sidecars).
Verified working