Designing a search endpoint in OpenAPI: q, filters, sorting, sparse fieldsets, and pagination codegen understands

Every list endpoint grows search until it becomes a dialect of its own. One team uses status_in=paid,refunded, another uses filter[status]=paid, a third invents statuses=...; sorting is a sort string