The pending-hash-conflict walk existed twice (JSON admin API emitting numeric counts, SSR page emitting a formatted summary) — deliberately different shapes, but both duplicated the counts-or-zero lookup and the five-field total. MediaItemUsageCountsTotal is the shared read; the per-surface shaping stays local on purpose.