pub fn api_visibility_reviews_for_resource(
knowledge: &KnowledgeBase,
resource_scope: &EntityId,
query: &ApiVisibilityReviewQuery,
) -> ApiVisibilityReviewPageExpand description
Projects canonical API visibility comparisons associated with one resource.
The query clones at most its explicit relation limit; whether another page exists is checked against the borrowed relation index without cloning the look-ahead record. Referenced evidence and hypotheses are also inspected while borrowed and cloned only after their variable review fields satisfy compiled byte ceilings. Results are ordered by stable relation identity. Structurally unrelated or forged-looking incoming relations consume scan budget but are omitted. These checks are a read-model hygiene boundary, not cryptographic attestation.
Pagination is not a database snapshot. Concurrent inserts sort according to their stable relation IDs; a new ID at or before an already consumed cursor is not returned by later pages. Hosts that require a frozen export must provide an external snapshot or quiesce writes for that resource.