List Identity Cases

The collision queue: cases waiting on a human decision, oldest first.

status and reason_code are ENUMS, so a value outside them is a 422 rather than an empty page. Typed as a free string, status answered a misspelling with "no cases", which on a queue reads as "the queue is clear" — the one wrong answer an operator has no reason to question.

reason_code narrows in SQL, before the limit applies: filtering a mixed page client-side would hide one kind of case behind whatever else happened to fill the limit.

This is the route that discloses the captured address, so it is the route that pays for it. no_store keeps a cross-tenant page of addresses out of every shared cache, and one platform read-audit row is COMMITTED before any content is returned — the writer propagates its failures, so a queue this process could not record is a queue it does not serve. The row is written on every request, including the empty page: a recorder that fired only when an address came back would leave "nobody looked" and "the reader looked and the queue was clear" as the same silence.