fix(rees): investigate a REES /v1/ping 503 (7 Sentry events)

[JSONbored]

Summary

REES's /v1/ping health-check endpoint returned an unexpected 503.

Evidence (Sentry)

GITTENSORY-1J — rees_ping_error: REES /v1/ping returned an unexpected status (503). Check the REES service logs. 7 events, first/last seen 2026-07-09 (2 days before filing).

Requirements

1. Check REES service logs/health for 2026-07-09 to determine whether this was a real outage/restart window (in which case likely already resolved, just confirm) or a reproducible health-check gap.
2. Confirm whether this correlates in time with any of the other REES-side issues in this batch (GITTENSORY-15's TypeError, or the analyzer-timeout fingerprinting group) — a shared deploy/restart window would explain several of these at once.

Deliverables

• Root-cause finding, documented in the issue. Fix only if reproducible; otherwise close with the finding recorded.

[linear-code]

JSO-3623