ryan-crabbe-berri 97d986377c feat(proxy): add /team/daily/activity/aggregated and use it in the Usage UI ... The Team Usage tab drained row-paginated pages client side, which painted newest days first and drew duplicate bars when a day's rows straddled a page boundary. Serve the whole range in one SQL GROUPING SETS pass instead: the aggregated query gains optional per-entity rollup levels (entity as the most-significant GROUPING bit) so breakdown.entities keeps per-team spend, aliases, and per-key splits. The endpoint shares the paginated route's scoping via _resolve_team_daily_activity_scope, accepts the timezone the UI already sends, and the api_key filter now takes a list so non-admin member scoping works. The dashboard tries the aggregated endpoint first and falls back to page draining on failure.		2026-08-11 11:16:41 -07:00
..
management	feat(proxy): add /team/daily/activity/aggregated and use it in the Usage UI	2026-08-11 11:16:41 -07:00
spend	test: repair stale CircleCI contracts	2026-08-08 12:19:29 -07:00
__init__.py	feat(tests): behavior-pinning harness + Key Tier-1 matrix (#28321)	2026-05-20 19:27:44 -07:00