Status Page

Render Warrant public system status page: honest up/down + component health only.

LATENCY-LEAK FIX (R4 verify, issue 2): this page used to also render the in-process latency reservoir's p50/p95/p99 percentiles per operation. app/routes/internal.py documents that same reservoir as internal-only — "VOICE forbids publishing latency to callers" — and gates read-back behind a dev-like environment or a configured X-Warrant-Internal-Token. Rendering it here, unauthenticated, on the PUBLIC status page defeated that gate entirely. The reservoir is no longer read or passed to the template at all; an operator who needs it already has GET /internal/slo, and this route does not duplicate it publicly. No consumer-subject dimension was ever involved either way (the reservoir is keyed by operation name only), so this is purely about WHO may see routing-overhead latency, not about consumer privacy.