Filament Table query limit() vs paginate() per-page behavior

Filament's Table component is documented to use Laravel's paginator for per-page controls, with a default of 25 items and a Table::paginate() method to change the page size.

A design goal is to bound the total result set of a large table for performance while keeping the pagination UI functional. The Table query() callback allows modifying the underlying query builder before pagination is applied.

It is unclear how a limit() applied in that query builder interacts with the paginator's per-page value, and whether the Table component reconciles the two or lets one override the other. Does a limit() in query() override Table::paginate()? What is the effective row count used for page 2 and later when both are present? Is there a documented supported pattern for bounding total rows without disabling pagination controls?