Digesta needs to see what the fleet is doing, not only what it costs: how
many pods are running, where, and which model. The spend endpoint already
carried the pod rows, but a pod did not report its placement and there was
no roll-up to read at a glance.

A pod now carries and reports its data_center, cloud_type and gpu_count,
plus the pool and engine it belongs to. GET /v1/runpod/status (an alias of
/v1/runpod/spend, one implementation so the two can never disagree) adds a
`summary`: pods_total/ready/booting/unhealthy, gpus_in_use, inflight,
spot_pods, hourly_usd, and tallies by model, region, GPU and cloud type.

Same gate as the spend figures — an admin-scoped API key, 403 otherwise.

Three deliberate distinctions, documented: summary.hourly_usd counts only
pods actually serving (a booting pod bills but answers nothing, so counting
it would overstate capacity); pods_unhealthy is the alert-worthy number, a
pod past boot that is costing money and serving nothing; and gpus_in_use
counts cards, so a gpu_count:2 pod counts twice. An unknown region or GPU is
labelled "unknown" rather than dropped, so the tallies always sum to
pods_total.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>