List my person verifications

The caller's person-level verifications (KYC packets, attestations), cross-tenant by construction because they hang off the person, not the account. Self-scoped: a filter narrows this set and can never reach another person's rows. With NO query string the response is the legacy {success, data:[...], count} shape, every row, submitted_at DESC — unchanged. With limit or offset the response is the ADR 0003 envelope {success, data:{items, total, filtered, limit, offset}}; limit=0 returns counts alone. Filters or a sort WITHOUT limit/offset return the legacy shape over the filtered, sorted rows. status/kind/issuer are comma-separated ORs; an unrecognised member matches nothing. q is a case-insensitive substring over id, issuer and decision_reason — the row only; the person is not searched because the list is already one person's. from/to bound the column named by date_field (default submitted_at): YYYY-MM-DD is an inclusive whole UTC day, RFC3339 an exact instant (to exclusive); a row with no value in that column is excluded when a bound is set and included otherwise. since/until and created_after/created_before are aliases. Nullable sort columns (decided, expires) order NULLS LAST in both directions; every sort tiebreaks on id. An unknown query KEY is 400 unknown_param.