Matt Mabrey
8e863ae7d0
GET /api/usage/summary: active-user counts by day/week/month, per-user last-active, per-tool breakdown. Filters (from/to/project_id/username/ tool) combine. Gated by require_user_manager - same boundary as the User Directory. A project_super_user is scoped to events tied to projects they manage plus their own activity (managed_project_ids), never another user's suite-wide activity outside that; an app admin sees everything. _usage_query() factored out so T11.4's export can never disagree with what this endpoint counted - same filtered row set, not two derivations. Verified: admin sees all seeded events; a project_super_user scoped to one of two projects correctly sees only that project's events plus their own account-wide activity, and specifically does NOT see the admin's other-project or no-project activity; date/tool/project filters each narrow results correctly and combine.