Returns every administrative row this tenant's use of an integration wrote,
newest first.

The query is keyed on the INTEGRATION, never on a live entity id — which is the whole point. A query keyed on an entity id can only be composed while the entity still exists, so a deletion became unreadable the moment it succeeded. Here the CREATE, the UPDATEs and the DELETE of a resource that no longer exists all come back.

The addressable slug set is the TENANT set, and it is narrower than the platform one on two independent counts: a platform-administered integration (licensing, geolocation, the RapidAPI gateway) is not addressable here at all, and an integration none of whose entity types is a disclosed governance family is not offered either — because a filter that can only ever answer with an empty page is the silent failure this feature exists to remove. Read the addressable set from GET /api/v3/audit/vocabulary; do not author one.

Evaluation order is 401 → 403 (scope) → 403 (tenant) → 404 (slug).

A caller refused at either 403 never reaches the slug, so it cannot learn the
deployment's integration inventory by comparing 404 against 403. A slug that
exists but is platform-administered receives the SAME 404 body as a nonsense
one.