Pagination dont work

Expected behavior
Clicking pagination links inside the configured results container should update only that container via AJAX (same as filtering), while URL changes to /page/2/, etc.

Actual behavior
A full page reload occurs. No preloader/overlay from the plugin appears and no XHR request is sent.

Environment

• WordPress: 6.6.x (latest stable)
• Filter Everything: Free, latest from wp.org
• Theme: custom; archive template archive-news.php for CPT news (has_archive = true)
• Cache/JS/CSS optimizers: none
• On your public demo I observe the same (pagination does a full reload).

Filter Everything settings

• Use AJAX for filters: enabled
• HTML id or class of Posts Container: #newsess
• Debug mode: enabled
• Filter widget [fe_widget id="5155"] is rendered outside the results container

Template markup (simplified)

<?php echo do_shortcode('[fe_widget id="5155"]'); ?>

<?php if (have_posts()) : ?>
  <div id="newsess">
    <div class="cards-grid">
      <?php while (have_posts()) : the_post(); endwhile; ?>
    </div>

    <?php the_posts_pagination([
      'mid_size'  => 1,
      'prev_text' => '←',
      'next_text' => '→',
    ]); ?>
  </div>
<?php else: ?>
  <p>Post's not found</p>
<?php endif; ?>

What I already tried

1. Ensured the container #newsess wraps both the posts list and the pagination; filters are outside this container.
2. Removed my outer <nav class="pagination"> wrapper and kept the raw the_posts_pagination() output to avoid duplicate .pagination elements.
3. Confirmed id="newsess" is unique on the page.
4. Browser console: no errors. Network panel: clicking a page number triggers a Document request; no XHR with FE params appears.
5. Tested clicking pagination with active filters and without — full reload in both cases.
6. No JS defer/delay and no performance plugins.

Questions

1. Should standard the_posts_pagination() work in AJAX mode whenever AJAX is enabled and the container is correct, or is AJAX pagination supposed to work only after at least one filter/sort is active?
2. Are there any required classes/selectors in the pagination markup that FE relies on?
3. Is an additional shortcode/widget needed for AJAX pagination in the Free version, or should the current setup work?
4. If this is a bug, could you suggest a temporary workaround (e.g., a hook or explicit selector) to force AJAX handling of pagination links?

Happy to provide the full rendered pagination HTML, a system report, or access to a staging site if that helps. Thanks!