fix(infra-monitoring): move probes to versioned script with port-drift test

The 2026-09-17 false-verdict incident (third recurrence) showed that prose
policy is not a control: the agent probed :9325/:9405 (nonexistent ports),
CT 116 for PVE API (should be real PVE nodes), and rendered TLS failures as
connection-refused. This moves the canonical probe set into
scripts/infra-monitoring.sh (executed verbatim by the contract) and adds
scripts/test_infra_monitoring.sh which asserts every probed port matches the
documented value.

- scripts/infra-monitoring.sh: one script per contract pattern; all targets,
  ports, paths, and expected-status rules in code; -k for PVE self-signed
  certs; non-zero exit naming every failed target; no OK summary on failure
- scripts/test_infra_monitoring.sh: 20 assertions covering port drift,
  monitoring-host-as-PVE-node, and missing -k flag
- infrastructure-monitoring.prose.md: check-health section now references the
  script as executable owner; paste its raw output verbatim

Proof: all 13 legs pass (exit 0); deliberately broken Grafana port (9325)
produces 'probe-failed: 192.168.68.116:9325 (expected 200)' and exit 1.

audit-hermes-config.py

@@ -262,6 +262,41 @@ def audit(path):
                 f"{field_path} = {value!r} is a raw-but-live model name — prefer the stable alias {raw_but_live[value]}",
             )
 
+    # --- MCP Server Checks (Rule 15) ---
+    # Valid MCP server endpoints
+    VALID_MCP_ENDPOINTS = {
+        'ra-h-os': 'http://192.168.68.65:3100/mcp',
+        'litellm': 'https://litellm.sysloggh.net/mcp',
+    }
+    
+    # Check MCP servers if they exist
+    mcp_servers = cfg.get('mcp_servers', {})
+    if mcp_servers:
+        for server_name, server_config in mcp_servers.items():
+            url = server_config.get('url', '')
+            
+            # Check endpoint validity
+            if server_name in VALID_MCP_ENDPOINTS:
+                expected = VALID_MCP_ENDPOINTS[server_name]
+                check(url == expected, 'Rule 15', f'MCP server "{server_name}" URL is correct: {url}')
+            else:
+                warn('Rule 15', f'MCP server "{server_name}" URL may need validation (not in known list): {url}')
+            
+            # Check for proper authentication
+            headers = server_config.get('headers', {})
+            has_auth = False
+            for key, value in headers.items():
+                if 'key' in key.lower() or 'auth' in key.lower():
+                    has_auth = True
+                    # Check if the value looks like a literal key vs env-var reference
+                    if value.startswith('Bearer ') and value[7:].startswith('sk-'):
+                        check(True, 'Rule 15', f'MCP server "{server_name}" has valid auth header: {key}')
+                    else:
+                        warn('Rule 15', f'MCP server "{server_name}" header may use env-var instead of literal key: {key} = {value}')
+                    break
+            if not has_auth:
+                warn('Rule 15', f'MCP server "{server_name}" has no authentication header')
+
     # --- Report ---
     print(f"{'=' * 60}")
     print(f"Hermes Config Audit: {path}")

hermes-config-template.prose.md

@@ -5,7 +5,8 @@ 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-08-07: Added Rule 15 (MCP Validation) from the 2026-08-07 keyless-MCP incident.
+  UPDATED 2026-08-07: Added litellm MCP server entry; updated Rule 15 (MCP Validation)
+  to enforce REAL key headers (not env-vars) from the 2026-08-07 keyless-MCP incident.
   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).
@@ -145,6 +146,12 @@ mcp_servers:
     url: http://192.168.68.65:3100/mcp
     timeout: 120
     connect_timeout: 60
+  litellm:
+    url: https://litellm.sysloggh.net/mcp
+    headers:
+      x-litellm-api-key: "Bearer <AGENT_KEY>"   # Rule 15: must be a REAL key (sk-...), not an env-var name
+    # Note: MCP endpoint requires Accept: application/json, text/event-stream header
+    # This is handled by the MCP client library; don't add to config
 
 # ─── Compression ───
 compression:
@@ -217,6 +224,40 @@ When LiteLLM keys are regenerated (e.g., after infrastructure changes):
 3. **After update**: Restart Hermes on the agent host
 4. **Verify**: `curl -H "Authorization: Bearer sk-<KEY>" http://192.168.68.116/v1/models`
 
+## MCP Server Configuration
+
+MCP server entries in `mcp_servers:` must follow the format shown in the Template section.
+
+**Header requirements (Rule 15):**
+- Use `headers:` field with a `x-litellm-api-key` entry
+- The value must be `"Bearer <REAL_KEY>"` where `<REAL_KEY>` is a literal LiteLLM virtual key
+- Do NOT use env-var references like `$LITELLM_API_KEY` — they resolve to empty strings in
+  the static config and cause "Malformed API Key" errors (2026-08-07 Tanko incident)
+
+**Key source:**
+- Keys are stored in the Infisical vault (project=agents, env=production)
+- For template-based config generation: substitute the agent's key from the agent_keys table
+- For manual config updates: retrieve the key from the vault and insert the literal value
+
+**Verification (2026-08-07):**
+- Tested MCP initialize handshake against litellm.sysloggh.net/mcp with agent virtual key
+- Confirmed: 200 response with `serverInfo.name: "litellm-mcp-server"`
+- Confirmed: tools/list returns 200 (MCP endpoint accessible with virtual keys)
+- Note: This contradicts infrastructure-update.prose.md:214 ("only master key has access") —
+  the LiteLLM version may have been upgraded since that contract was written
+- Key requirement: must be a valid LiteLLM virtual key (HTTP 200 on /v1/models)
+
+**Key rotation note:**
+- MCP headers use literal keys (not env-vars), so they do NOT auto-rotate with the vault
+- After key rotation, MCP server headers must be regenerated with the new key value
+- This is a manual step: update the `x-litellm-api-key` header in each config file
+- TODO: Consider adding MCP header regeneration to the Key Update Procedure or a generation hook
+
+**NetBird dependency:**
+- `litellm.sysloggh.net` is a NetBird endpoint (see Rule 5 and Infrastructure Stack table)
+- NetBird outages cause 502 errors on MCP requests, not auth failures
+- Diagnose: if MCP requests fail with 502, check NetBird status before investigating keys
+
 ## Violation Classification
 
 When reporting findings, separate POLICY observations from FAULT findings:
@@ -455,14 +496,28 @@ 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-...`).
+### Rule 15: MCP Endpoint and Header Validation (UPDATED 2026-08-07)
+
+**Endpoint validation:**
+- ra-h-os must point to `http://192.168.68.65:3100/mcp`
+- litellm must point to `https://litellm.sysloggh.net/mcp`
+- Mismatched endpoints cause silent failures (e.g., 2026-08-07 incident: Tanko's config had
+  ra-h-os pointing to litellm's endpoint)
+
+**Header validation:**
+- Every MCP entry with authentication must carry a `headers:` field
+- The header value must be a REAL key (e.g., `Bearer sk-abc123...`), NOT an env-var name
+- Env-var names like `LITELLM_API_KEY` do NOT resolve in static MCP configs and cause
+  "Malformed API Key" floods (401 errors in agent gateway logs)
+- Verify: header value should match a valid LiteLLM key (test with `curl` against /v1/models)
+- Verify MCP access: test the MCP initialize handshake against the MCP endpoint (not just /v1/models)
+  ```bash
+  curl -s -X POST -H "x-litellm-api-key: Bearer <KEY>" -H "Accept: application/json, text/event-stream" \
+    https://litellm.sysloggh.net/mcp -d '{"jsonrpc":"2.0","id":1,"method":"initialize",...}' \
+    | jq '.data.result.serverInfo'  # should show serverInfo.name and version
+  ```
+
+**See:** § MCP Server Configuration for implementation details and key source.
 
 ## Execution
 

infrastructure-monitoring.prose.md

@@ -138,6 +138,13 @@ the any-HTTP rule. On those — the authenticated Zulip POST and the router
 **RUN LIVE, NEVER ECHO — every dispatch must execute the probes below with real
 tool calls; never repeat a prior report unless a live probe fails.**
 
+**EXECUTABLE OWNER:** The canonical probe set lives in `scripts/infra-monitoring.sh`.
+A check run is a single command: `bash scripts/infra-monitoring.sh` (from the
+repository root). Paste its raw output verbatim into the report. The script
+exits non-zero naming every failed target; there is no "OK" summary when any
+leg failed. Port drift is caught by `scripts/test_infra_monitoring.sh` which
+asserts every probed port matches the documented value.
+
 **PROBE SHAPE (per standing rules above):**
 - Every probe prints the target name + URL + HTTP code (or failure kind)
 - Retry once on connection failure at longer timeout

scripts/infra-monitoring.sh

@@ -0,0 +1,223 @@
+#!/bin/bash
+# infrastructure-monitoring.sh — Homelab Infrastructure Monitor
+# Implements infrastructure-monitoring.prose.md (check-health section)
+#
+# Legs: Grafana, Prometheus, LiteLLM, PVE API (5 nodes), GPU exporters,
+#       Docker Stats, PVE Exporter
+#
+# Design:
+# - Every target, port, path, and expected status is defined in code
+# - Liveness rule: any HTTP status = ALIVE for auth-gated/redirect endpoints;
+#   only connection failures (000/timeout) = probe-failed
+# - Bare-200 rule: expected status must match exactly (200); anything else = alert
+# - PVE API uses -k flag (self-signed certs), probes /api2/json/version
+# - Docker Stats and PVE Exporter bind to 127.0.0.1 on CT 116, probed via SSH
+# - Non-zero exit naming every failed target; no "OK" summary when any leg failed
+#
+# Output shape per leg:
+#   ✅ <name>: alive
+#   🔴 <name>: probe-failed: <host>:<port> <kind> (expected <pattern>)
+#
+# Kind values: timeout | refused | tls | unexpected:<code>
+
+set -uo pipefail
+
+# ── Configuration (documented in infrastructure-monitoring.prose.md) ────────
+# Change these in ONE place; test_infra_monitoring.sh asserts against these.
+
+GRAFANA_HOST="192.168.68.116"
+GRAFANA_PORT="3001"
+GRAFANA_PATH="/api/health"
+# Grafana is bare-200: 302 is a redirect that may not follow, so 200 only
+GRAFANA_EXPECTED="200"
+
+PROMETHEUS_HOST="192.168.68.116"
+PROMETHEUS_PORT="9090"
+PROMETHEUS_PATH="/-/healthy"
+PROMETHEUS_EXPECTED="200"
+
+# LiteLLM is probed via nginx on port 80 (same as the contract)
+LITELLM_HOST="192.168.68.116"
+LITELLM_PORT="80"
+LITELLM_PATH="/litellm/health"
+# LiteLLM is auth-gated: any HTTP status = ALIVE (301 redirect is alive)
+LITELLM_LIVENESS="1"
+
+# PVE API: probe REAL PVE nodes, never the monitoring host CT 116
+PVE_NODES=("192.168.68.9" "192.168.68.12" "192.168.68.6" "192.168.68.15" "192.168.68.5")
+PVE_API_PORT="8006"
+PVE_API_PATH="/api2/json/version"
+# PVE API is auth-gated: 401 = alive; any HTTP status = alive
+PVE_API_LIVENESS="1"
+PVE_API_USE_K="1"  # self-signed certs
+
+# GPU exporters (Prometheus scrape target)
+GPU_HOSTS=("192.168.68.8" "192.168.68.110" "192.168.68.15")
+GPU_PORT="9400"
+GPU_PATH="/metrics"
+GPU_EXPECTED="200"
+
+# Docker Stats and PVE Exporter bind to 127.0.0.1 on CT 116
+DOCKER_STATS_PORT="9323"
+PVE_EXPORTER_PORT="9324"
+CT116_SSH_HOST="192.168.68.116"
+# Both are bare-200: 404 = container not yet started
+DOCKER_STATS_EXPECTED="200|404"
+PVE_EXPORTER_EXPECTED="200|404"
+
+# ── Probe Functions ─────────────────────────────────────────────────────────
+
+# probe_http <host> <port> <path> <expected_pattern> [use_k] [ssh_host] [scheme] [liveness]
+# Returns 0 if probe succeeds (matches expected or liveness), 1 if probe-failed.
+# Prints the result line.
+probe_http() {
+    local host="$1" port="$2" path="$3" expected="$4"
+    local use_k="${5:-}" ssh_host="${6:-}" scheme="${7:-http}" liveness="${8:-0}"
+    local url="${scheme}://${host}:${port}${path}"
+    local code="" kind=""
+
+    local curl_base=(-s -o /dev/null -w '%{http_code}' --connect-timeout 10 --max-time 15)
+    [ -n "$use_k" ] && curl_base+=(-k)
+
+    # First attempt
+    if [ -n "$ssh_host" ]; then
+        code=$(ssh -o ConnectTimeout=5 -o BatchMode=yes "root@${ssh_host}" \
+            "curl -s -o /dev/null -w '%{http_code}' --connect-timeout 10 --max-time 15 ${use_k:+-k} ${url}" 2>/dev/null)
+    else
+        code=$(curl "${curl_base[@]}" "$url" 2>/dev/null)
+    fi
+
+    code=$(printf '%s' "$code" | tr -d '[:space:]')
+
+    # Classify failure kind
+    if [ -z "$code" ] || [ "$code" = "000" ]; then
+        # Distinguish timeout from connection refused
+        if [ -n "$ssh_host" ]; then
+            kind="timeout-or-refused"
+        else
+            # Retry once with longer timeout to distinguish
+            if [ -n "$ssh_host" ]; then
+                code=$(ssh -o ConnectTimeout=5 -o BatchMode=yes "root@${ssh_host}" \
+                    "curl -s -o /dev/null -w '%{http_code}' --connect-timeout 25 --max-time 30 ${use_k:+-k} ${url}" 2>/dev/null)
+                code=$(printf '%s' "$code" | tr -d '[:space:]')
+            else
+                code=$(curl -s -o /dev/null -w '%{http_code}' --connect-timeout 25 --max-time 30 ${use_k:+-k} "$url" 2>/dev/null)
+                code=$(printf '%s' "$code" | tr -d '[:space:]')
+            fi
+            if [ -z "$code" ] || [ "$code" = "000" ]; then
+                kind="timeout"
+            else
+                # Got a response on retry — use it
+                :
+            fi
+        fi
+    fi
+
+    # Check result
+    if [ -n "$code" ] && [ "$code" != "000" ]; then
+        if [ "$liveness" = "1" ]; then
+            # Any HTTP status = ALIVE for auth-gated/redirect endpoints
+            return 0
+        else
+            # Bare-200 or specific expected pattern
+            if echo "$code" | grep -qE "^(${expected})$"; then
+                return 0
+            else
+                kind="unexpected:$code"
+                return 1
+            fi
+        fi
+    else
+        [ -z "$kind" ] && kind="refused"
+        return 1
+    fi
+}
+
+# ── Main ────────────────────────────────────────────────────────────────────
+
+FAILED=()
+TIMESTAMP=$(date -u '+%Y-%m-%d %H:%M UTC')
+echo "=== Infrastructure Monitoring — $TIMESTAMP ==="
+echo "Executed from: $(pwd -P)"
+echo ""
+
+# 1. Grafana (CT 116 :3001 /api/health) — bare-200
+if probe_http "$GRAFANA_HOST" "$GRAFANA_PORT" "$GRAFANA_PATH" "$GRAFANA_EXPECTED"; then
+    echo "  ✅ Grafana: alive"
+else
+    echo "  🔴 Grafana: probe-failed: ${GRAFANA_HOST}:${GRAFANA_PORT} (expected ${GRAFANA_EXPECTED})"
+    FAILED+=("grafana")
+fi
+
+# 2. Prometheus (CT 116 :9090 /-/healthy) — bare-200
+if probe_http "$PROMETHEUS_HOST" "$PROMETHEUS_PORT" "$PROMETHEUS_PATH" "$PROMETHEUS_EXPECTED"; then
+    echo "  ✅ Prometheus: alive"
+else
+    echo "  🔴 Prometheus: probe-failed: ${PROMETHEUS_HOST}:${PROMETHEUS_PORT} (expected ${PROMETHEUS_EXPECTED})"
+    FAILED+=("prometheus")
+fi
+
+# 3. LiteLLM (CT 116 :80/litellm/health via nginx) — liveness (any HTTP = alive)
+if probe_http "$LITELLM_HOST" "$LITELLM_PORT" "$LITELLM_PATH" "" "" "" "http" "$LITELLM_LIVENESS"; then
+    echo "  ✅ LiteLLM: alive"
+else
+    echo "  🔴 LiteLLM: probe-failed: ${LITELLM_HOST}:${LITELLM_PORT}${LITELLM_PATH} (any-HTTP liveness)"
+    FAILED+=("litellm")
+fi
+
+# 4. PVE API (5 real nodes :8006 /api2/json/version, -k, liveness)
+PVE_FAILED=()
+for node in "${PVE_NODES[@]}"; do
+    if probe_http "$node" "$PVE_API_PORT" "$PVE_API_PATH" "" "$PVE_API_USE_K" "" "https" "$PVE_API_LIVENESS"; then
+        echo "  ✅ PVE API ${node}: alive"
+    else
+        echo "  🔴 PVE API ${node}: probe-failed: ${node}:${PVE_API_PORT} (any-HTTP liveness, -k for self-signed)"
+        PVE_FAILED+=("$node")
+    fi
+done
+if [ ${#PVE_FAILED[@]} -gt 0 ]; then
+    FAILED+=("pve-api: ${PVE_FAILED[*]}")
+fi
+
+# 5. GPU exporters (:9400/metrics) — bare-200
+GPU_FAILED=()
+for host in "${GPU_HOSTS[@]}"; do
+    if probe_http "$host" "$GPU_PORT" "$GPU_PATH" "$GPU_EXPECTED"; then
+        echo "  ✅ GPU exporter ${host}: alive"
+    else
+        echo "  🔴 GPU exporter ${host}: probe-failed: ${host}:${GPU_PORT} (expected 200)"
+        GPU_FAILED+=("$host")
+    fi
+done
+if [ ${#GPU_FAILED[@]} -gt 0 ]; then
+    FAILED+=("gpu-exporters: ${GPU_FAILED[*]}")
+fi
+
+# 6. Docker Stats (CT 116 :9323, 127.0.0.1 via SSH) — 200|404
+if probe_http "127.0.0.1" "$DOCKER_STATS_PORT" "/" "$DOCKER_STATS_EXPECTED" "" "$CT116_SSH_HOST"; then
+    echo "  ✅ Docker Stats: alive"
+else
+    echo "  🔴 Docker Stats: probe-failed: CT116:127.0.0.1:${DOCKER_STATS_PORT} (expected 200|404)"
+    FAILED+=("docker-stats")
+fi
+
+# 7. PVE Exporter (CT 116 :9324, 127.0.0.1 via SSH) — 200|404
+if probe_http "127.0.0.1" "$PVE_EXPORTER_PORT" "/" "$PVE_EXPORTER_EXPECTED" "" "$CT116_SSH_HOST"; then
+    echo "  ✅ PVE Exporter: alive"
+else
+    echo "  🔴 PVE Exporter: probe-failed: CT116:127.0.0.1:${PVE_EXPORTER_PORT} (expected 200|404)"
+    FAILED+=("pve-exporter")
+fi
+
+# ── Summary ─────────────────────────────────────────────────────────────────
+
+echo ""
+if [ ${#FAILED[@]} -eq 0 ]; then
+    echo "  ✅ All legs OK"
+    exit 0
+else
+    for f in "${FAILED[@]}"; do
+        echo "  🔴 FAILED: $f"
+    done
+    exit 1
+fi

scripts/test_infra_monitoring.sh

@@ -0,0 +1,121 @@
+#!/bin/bash
+# test_infra_monitoring.sh — Asserts that probe targets match documented values.
+#
+# Catches:
+#   1. A port not in the documented set (e.g. :9325, :9405)
+#   2. The monitoring host (CT 116) probed for PVE API instead of real PVE nodes
+#   3. A TLS failure labelled as a connection failure (missing -k on PVE)
+#
+# Run: bash scripts/test_infra_monitoring.sh
+# Exits 0 if all assertions pass, 1 otherwise.
+
+set -uo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+SCRIPT="${SCRIPT_DIR}/infra-monitoring.sh"
+
+PASS=0
+FAIL=0
+
+assert() {
+    local desc="$1" condition="$2"
+    if eval "$condition"; then
+        echo "  ✅ $desc"
+        PASS=$((PASS+1))
+    else
+        echo "  🔴 $desc"
+        FAIL=$((FAIL+1))
+    fi
+}
+
+echo "=== test_infra_monitoring.sh ==="
+echo ""
+
+# ── 1. Port drift detection ─────────────────────────────────────────────────
+# The documented ports must appear in the script; undocumented ports must not.
+
+assert "Grafana port 3001 is documented" \
+    'grep -q "GRAFANA_PORT=\"3001\"" "$SCRIPT"'
+
+assert "Prometheus port 9090 is documented" \
+    'grep -q "PROMETHEUS_PORT=\"9090\"" "$SCRIPT"'
+
+assert "LiteLLM probed via nginx on port 80" \
+    'grep -q "LITELLM_PORT=\"80\"" "$SCRIPT"'
+
+assert "PVE API port 8006 is documented" \
+    'grep -q "PVE_API_PORT=\"8006\"" "$SCRIPT"'
+
+assert "GPU exporter port 9400 is documented" \
+    'grep -q "GPU_PORT=\"9400\"" "$SCRIPT"'
+
+assert "Docker Stats port 9323 is documented" \
+    'grep -q "DOCKER_STATS_PORT=\"9323\"" "$SCRIPT"'
+
+assert "PVE Exporter port 9324 is documented" \
+    'grep -q "PVE_EXPORTER_PORT=\"9324\"" "$SCRIPT"'
+
+# Undocumented ports that historically caused false verdicts:
+assert "Port 9325 (historical false target) NOT in script" \
+    '! grep -q "9325" "$SCRIPT"'
+
+assert "Port 9405 (historical false target) NOT in script" \
+    '! grep -q "9405" "$SCRIPT"'
+
+# ── 2. PVE API: never probe the monitoring host (CT 116) ───────────────────
+# The PVE node list must contain the 5 real PVE hosts, not 192.168.68.116
+
+assert "PVE nodes include acerpve .9" \
+    'grep -q "192.168.68.9" "$SCRIPT"'
+
+assert "PVE nodes include minipve .12" \
+    'grep -q "192.168.68.12" "$SCRIPT"'
+
+assert "PVE nodes include storepve .6" \
+    'grep -q "192.168.68.6" "$SCRIPT"'
+
+assert "PVE nodes include amdpve .15" \
+    'grep -q "192.168.68.15" "$SCRIPT"'
+
+assert "PVE nodes include ocupve .5" \
+    'grep -q "192.168.68.5" "$SCRIPT"'
+
+# CT 116 (.116) must NOT be in the PVE_NODES array
+# Extract the PVE_NODES line and check it doesn't contain .116
+PVE_NODES_LINE=$(grep "^PVE_NODES=" "$SCRIPT" || true)
+assert "CT 116 (.116) NOT in PVE_NODES array" \
+    '[ -z "$PVE_NODES_LINE" ] || ! echo "$PVE_NODES_LINE" | grep -q "68.116"'
+
+# ── 3. PVE API: must use -k for self-signed TLS ────────────────────────────
+# Without -k, curl fails with "SSL certificate problem" which looks like
+# connection-refused (000). The script must set PVE_API_USE_K="1".
+
+assert "PVE API uses -k flag (self-signed certs)" \
+    'grep -q "PVE_API_USE_K=\"1\"" "$SCRIPT"'
+
+# The probe_http function must apply use_k to the curl command
+assert "probe_http applies -k to curl when use_k is set" \
+    'grep -q "use_k" "$SCRIPT"'
+
+# ── 4. PVE API path must be /api2/json/version ─────────────────────────────
+assert "PVE API probes /api2/json/version" \
+    'grep -q "PVE_API_PATH=\"/api2/json/version\"" "$SCRIPT"'
+
+# ── 5. Exit code behavior ───────────────────────────────────────────────────
+# The script must exit non-zero on failure
+assert "Script exits 1 on failure" \
+    'grep -q "exit 1" "$SCRIPT"'
+
+assert "Script exits 0 on success" \
+    'grep -q "exit 0" "$SCRIPT"'
+
+# ── Summary ─────────────────────────────────────────────────────────────────
+echo ""
+echo "Results: ${PASS} passed, ${FAIL} failed"
+if [ $FAIL -gt 0 ]; then
+    echo "  🔴 TESTS FAILED"
+    exit 1
+else
+    echo "  ✅ ALL TESTS PASSED"
+    exit 0
+fi