d568800942
The full pagination fix (ddad80a,e772001) caused history retrieval to fetch up to 50 pages sequentially, taking 10-40 seconds instead of ~200ms. Changes: - Add maxPages parameter to getHistory() with default of 1 page - Update poller to fetch 50 records (up from 10) in a single API call - historyFetcher retains 100 records per page for UI display This provides 5x more history for matching than before while keeping the fast single-request performance. Refs: develop-merge pagination performance issue