q-table server pagination limits without built-in query bounding

Goal is to present a large dataset in q-table with server-side pagination enabled via the server prop. The component is expected to emit pagination-change events containing page and rowsPerPage values, and the application is responsible for constructing the remote request payload such as limit/offset or cursor.

The documented capability does not include built-in query bounding. Validation of rowsPerPage, maximum page size, and construction of the request parameters are left to the application data layer. Loading state and error boundaries also need to be managed by the consumer.

Uncertainty remains about the component behavior during rapid pagination interactions and the contract for the pagination object. Does q-table enforce a maximum rowsPerPage when server is true, or is validation entirely application-side? Is there any built-in debouncing or cancellation of pagination-change events when navigation occurs quickly? What is the expected shape and update contract for the pagination object returned by the component when using server-side mode.