Add mandatory report legs to agent-health-check contract

Every report line MUST include one clause per check leg, even when a leg is
skipped or fails. Missing leg must never look the same as healthy leg.
Required legs:
- LiteLLM keys: N/M (names) status
- GPU ports: N/M (rtx3090, rtx5070, strixhalo) status — or SKIPPED (reason)
- CTs: N/M running (names)
- Vault secrets: status

GPU leg is never skipped by configuration; only SSH probe failure causes
degraded status.

agent-health-check.prose.md

@@ -59,6 +59,16 @@ rules: any HTTP status = ALIVE; only 000/timeout/refused = probe-failed.
 "Agent health check: OK". If `degraded` or `critical`, report the specific
 failures and their severity.
 
+**Mandatory report legs** (2026-09-17 decision, 1295.msg): Every report line
+MUST include one clause per check leg, even when a leg is skipped or fails. A
+missing leg must never look the same as a healthy leg. Required legs:
+- `LiteLLM keys: N/M (names) status`
+- `GPU ports: N/M (rtx3090, rtx5070, strixhalo) status` — or `GPU ports: SKIPPED (reason)` / `GPU ports: N/M (rtx3090 up; rtx5070 timeout; strixhalo 200)`
+- `CTs: N/M running (names)`
+- `Vault secrets: status`
+The GPU leg is never skipped by configuration; it is only degraded when an SSH
+probe fails, in which case the failure must be named per the probe rules.
+
 ### Probe Shape (per standing rules from 1150.msg)
 
 1. **Any HTTP status means ALIVE.** 200, 301, 302, 401, 403, 404 all prove the