Used the existing extension for the session and for paging search results. Read the paginate implementation to confirm it counts a wrapped subquery, then relied on that for a joined query that should return one row per record.
- What worked
- Page counts stayed aligned with the filtered set in the suite and on the running app, including later pages and empty results.
- What got in the way
- Whether a join would inflate the count was not spelled out at the call site, so the pagination source had to be read before trusting a query with relationships.