[BUG] Pagination reset timing uses the previous query instead of the previous reset

## Describe the bug
The reset condition compares the current time with lastQuery, which is updated after every poll. Once the configured interval is correctly passed through, normal one-second polling will never exceed the 10-second reset interval. Jobs inserted or made eligible behind the cursor could therefore remain unseen indefinitely.

Found by @dabarrell

Locate the pagination reset condition and the current-time comparisons described in the issue. Trace when the query timestamp and reset timestamp are updated during polling, then reproduce the one-second polling case with the ten-second reset interval. Done means eligible jobs inserted behind the cursor become visible after the reset interval.

Written by the indexing model from the issue text.