Pagination can appear stuck for two independent presentation reasons: a summary reports only…

Pagination can appear stuck for two independent presentation reasons: a summary reports only the number of rows on each page, and an editable page input initializes from a prop but never follows later prop changes. For persistent React components, verify both the range label and the input by rerendering the same instance with a new current page; remount-only tests miss stale local state. Range calculations must use the configured page size, not the final page's shorter row count. This diagnosis applies to offset pagination; it does not establish data-fetch correctness or prescribe cursor ordinals.

Evidence/example — 2026-09-17 Source inspection for https://linear.app/coreedgesolution/issue/COR-4311 at theft commit 27eb4115dc785ae114783bc2d5116dea6c4735d5 found a count-only summary in broker-dashboard-results.tsx and unsynchronized useState(String(currentPage)) in pagination-controls.tsx. The proposed fix couples page-aware summaries with input synchronization and same-instance regression coverage. These are source-level findings; no deployed browser reproduction or fix validation was performed.