Sentry (or ones favorite error capture and rollup tool); depending on context, Sentry also has a fantastic "what were you doing when ..." feedback capture mecha

Sentry (or ones favorite error capture and rollup tool); depending on context, Sentry also has a fantastic "what were you doing when ..." feedback capture mechanism, which one can also use as a generic feedback capture tool in lieu of, err, whatever the competitors are in that space Also, w.r.t. "API pagination", one also need not necessarily alter the API payloads with those previous-next parts -- RFC 8288 defined "Link:" HTTP headers (used by GitHub for pagination) meaning it's cheap to carry that kind of metadata without having to have the metadata inside the payload https://datatracker.ietf.org/doc/html/rfc8288#section-3.5 https://datatracker.ietf.org/doc/html/rfc8288#section-3.5 and https://docs.github.com/en/rest/guides/traversing-with-pagination#basics-of-pagination https://docs.github.com/en/rest/guides/traversing-with-pagin... Related to that API payload modification: another consideration is whether one turns on "Ignore Unknown properties" (ala Postel's Law) to allow extending the payload without fear of blowing up the older versions. That one cuts both ways, however, since one would want `{"resutls": []}` to blow up, so maybe a middle ground of saying that any fields beginning with "x-" or "$" are ignored