The app's statement for a billing period.

Inverts the People surface: instead of listing participants and the roles each one carries, this lists every roster role in the Network and, for each, who holds it and which agent contacts defer to it. A holder is reported with every tier that grants the role — `EXPERTISE` for a tenant-level expertise tag that applies everywhere, `EDGE_ROLE` for a tag on a member edge in this Network — and an edge-granted holder names the agents whose edge grants it, since that is the only place the tag can be removed. `consultable` reports whether a consult-allowed member edge exists: a holder without one is still reachable for delivery through a role-bound contact but is refused for `consult_for_role`. A role with references and no holders is the actionable gap this surface exists to expose — deliveries and consults to it refuse at runtime. Roles group case-insensitively and are reported using the tenant capability catalog's casing; `inCatalog` distinguishes a catalog role from one that exists only as an ad-hoc tag. Read-only and fully derived from existing expertise, member-edge, and contact-slot state — it adds no storage of its own, so nothing here can drift from the People surface. The whole role vocabulary is projected in memory before paging — it is tens of names, not thousands (participants are paged on the People surface, not here) — so a page is a slice of the complete, fully ordered result and omitting `pageSize` returns everything.