Page the moderation queue

Use moderation:read from a Project Backend to retrieve that Project Client's received and resolved reports. The queue is operational metadata: it never returns reporter identity or Comment body, and reading it never changes report or moderation state.

Shell example

: "${MINICENTER_URL:?set the Sandbox URL}"
: "${MINICENTER_PROJECT_CREDENTIAL:?set a Project Credential}"

curl --get --fail-with-body "${MINICENTER_URL}/api/v1/community/moderation/reports" \
  -H "Authorization: Bearer ${MINICENTER_PROJECT_CREDENTIAL}" \
  --data-urlencode 'resource_type=article' \
  --data-urlencode 'resource_id=article-42' \
  --data-urlencode 'limit=50'

Omit both resource fields to page the entire Project Client queue, or provide both to bind results to one exact opaque resource. Results are oldest-first and contain report ID, Comment ID, resource tuple, fixed report reason, received or resolved status, nullable decision and decision time, and current Comment moderation state.

When next_after is non-null, repeat with that report ID as after. Limits range from 1 to 100. A cursor outside the credential's client or selected resource returns 422. If MiniCenter is unavailable, retain the last observed queue locally for display only and retry the safe read; never infer a new moderation decision.