Rate dashboards need current UI and explicit denominators

A dashboard rate should be calculated from a numerator and denominator in the same selected scope and time bucket, displayed beside its counts, and shown as unavailable when the denominator is zero. Before changing an existing dashboard, compare the deployed UI and latest remote source: a stale checkout can pass comprehensive local tests while changing the wrong interaction layout. This applies to operations dashboards that mix count cards, trends, and drill-downs. It does not by itself prove live deployment or that an aggregate's source population is semantically complete.

Evidence/example (2026-09-22): In Shield Super Admin V2, the initial local branch had an older layout and passed tests, but the production page and latest main used compact cards and hover breakdowns. Rebasing the narrow change onto current main required preserving those interactions. The implementation uses completed terminal loads divided by total created loads per selected range or chart bucket, with an unavailable marker for empty buckets. Local app type check, full tests, and five-width responsive review passed; PR #984 is not yet production verification. https://github.com/e3-solutions/theft/pull/984 and https://linear.app/coreedgesolution/issue/COR-4396/show-completion-rates-across-super-admin-v2-analytics