Ship: monitoring contract fixes (2026-08-09)

hermes-config-template.prose.md

@@ -5,8 +5,7 @@ description: >
   Standard Hermes configuration template for Syslog Solution LLC agents.
   Enforces shared infrastructure setup (Firecrawl, SearXNG, local models,
   RA-H OS MCP) while keeping agent-specific API keys and model choices.
-  UPDATED 2026-07-16: Compression model is the stable alias `strix-moe` (NOT `ornith-1.0-35b`,
+  UPDATED 2026-08-07: Added Rule 15 (MCP Validation) from the 2026-08-07 keyless-MCP incident.
-  which LiteLLM does not serve). All 3 GPUs verified at 128K (reduced from 256K 2026-07-17 for stability).
   Added Rule 12 (Context-Issue Diagnostic) + Rule 13 (.env fallback enforcement) from the
   2026-07-16 Mumuni root-cause investigation (WAL #1300).
   UPDATED 2026-07-12: GPU workload redistributed. Compression → Strix Halo. RTX 3090 context verified at 128K. Infisical .env fallback required (Rule 3/13).
@@ -101,6 +100,10 @@ model:
   api_key_env: LITELLM_API_KEY    # Injected via infisical run -- wrapper
   max_tokens: 4096                # ⚠️ CRITICAL: Prevents unbounded generation
   context_length: 131072          # For syslog-auto (all GPUs at 128K for stability).
+                                  # ⚠️ MANDATORY: Hermes probes unknown models from 256K
+                                  # and falls back to 256K when /v1/models lacks a context
+                                  # field (llama-server does). Without this override, agents
+                                  # silently run syslog-auto at 256K (verified 2026-08-09).
                                   # Set 65536 if using gemma-4-12b directly (tight VRAM).
 
 fallback_providers:
@@ -396,6 +399,15 @@ curl -s -o /dev/null -w '%{http_code}' -H "Authorization: Bearer $K" http://192.
 - **Audit script**: Run `python3 /root/prose-contracts/audit-hermes-config.py <config.yaml>`
   before and after any config change to catch this and all other rule violations.
 
+### Rule 15: MCP Endpoint and Header Validation (ADDED 2026-08-07)
+- Every MCP server entry must point at the correct endpoint:
+  - ra-h-os = http://192.168.68.65:3100/mcp
+  - litellm = https://litellm.sysloggh.net/mcp
+- MCP entries must carry a REAL key value in the header.
+  - Avoid using env-var names like LITELLM_API_KEY in the header; they do not resolve for MCP
+    endpoints and result in "Malformed API Key" floods.
+  - Ensure the header value is the actual key (e.g., `sk-...`).
+
 ## Execution
 
 1. **Check current config** — Read the target agent's config.yaml

hermes-key-enforcement.prose.md

@@ -190,10 +190,10 @@ litellm_settings:
 |-------|-----|-----|---------------|------------|--------|-----------------|---------------|
 | Tanko | 112 | .122 | `tanko` | Infisical vault | ✅ Fixed | `infisical run` | 20:17 UTC Jul 5 |
 | Mumuni | 100 (abiba) | .24 | `mumuni` | Infisical vault | ✅ Fixed | Pi Hermes gateway | 2026-07-27 |
-| Koby | 111 | ? | `koby` | Infisical vault | ✅ Fixed | `infisical run` | 23:30 UTC Jul 5 |
+| Koby | 111 | .129 | `koby` | Infisical vault | ✅ Fixed | `infisical run` | 23:30 UTC Jul 5 |
-| Koonimo | 113 | ? | `koonimo` | Infisical vault | ✅ Fixed | `infisical run` (migrated 2026-07-11) | 2026-07-11 |
+| Koonimo | 113 | .113 | `koonimo` | Infisical vault | ✅ Fixed | `infisical run` (migrated 2026-07-11) | 2026-07-11 |
 | Abiba | 100 | .65 | `abiba-pi` | Infisical vault | ✅ N/A (pi native) | — | 19:44 UTC Jul 5 |
-| Kagenz0 | 105 | ? | — | — | ❌ DOWN | — | 19:14 EDT Jul 4 |
+| Kagenz0 | 105 | .14 | — | — | ❌ DOWN | — | 19:14 EDT Jul 4 |
 
 > **Note**: CT hostnames (tdunna, baggy) differ from agent identities (koby, koonimo).
 > LiteLLM key aliases use agent identity, not CT hostname.

infrastructure-monitoring.prose.md

@@ -7,13 +7,15 @@ description: >
   from nvidia-smi (.8, .110) and amdgpu_top (.15). LiteLLM metrics
   via existing /metrics Prometheus endpoint.
   
-  DEPLOYMENT STATUS (2026-07-09):
+  DEPLOYMENT STATUS (2026-08-09):
   ✅ Core stack deployed: Prometheus + Grafana + pve/node/docker exporters
-     (via proxmox-monitor contract). Grafana at :3001, 5 scrape targets active.
+     (via proxmox-monitor contract). Grafana at :3001, all scrape targets active.
-  ❌ GPU exporters NOT deployed: gpu-exporter crash-loops on .15,
+  ✅ GPU exporters DEPLOYED: all 3 GPU hosts (.8/.110/.15) run exporters on
-     NVIDIA sidecar exporters (.8/.110:9400) never installed.
+     :9400 (nvidia_gpu_exporter / amdgpu exporter) — verified 200 on 2026-08-09.
-     Router falls back to direct GPU /health probes.
+  ✅ LiteLLM /metrics scraping live (success_callback: prometheus; auth via
-  ⚠️ This contract is target-state aspirational — not as-built.
+     master key) + Alertmanager + Zulip bridge (alerts-infra) added 2026-08-09.
+  ⚠️ This contract is target-state aspirational — but GPU export + alerting
+     are now as-built (verified 2026-08-09).
      As-built GPU monitoring is via gpu-monitor contract (port 9100 poll).
 version: 1.0.0
 ---

litellm-health.prose.md

@@ -18,6 +18,15 @@ description: >
   Designed as a reusable contract for any Syslog agent.
   
   Source of truth: gpu-fleet.prose.md
+
+  ## Monitoring / Alerting (as-built 2026-08-09)
+
+  - LiteLLM /metrics scrape job: requires `litellm_settings.success_callback: [prometheus]`
+    (failure_callback alone does NOT mount /metrics — verified 2026-08-09).
+    Scraped by Prometheus with Bearer master key; endpoint returns 307 → /metrics/.
+  - Alertmanager (harness-alertmanager :9093) + zulip-bridge (:9102) deliver
+    firing alerts to #agent-hub > alerts-infra via abiba-bot. Added 2026-08-09.
+  - Prometheus node job covers ALL 6 PVE nodes (.4/.5/.6/.9/.12/.15:9100).
 ---
 
 ## Architecture (v4.0.0 — Direct: nginx → LiteLLM → GPU)