[cerebrate]

Why

On Home Assistant installations with entity counts in the thousands, the management card's Throttled/Accepted tabs (which list every matching entity with no cap at all) and even the Unthrottled tab become unwieldy — everything renders as one long, unbroken list. This PR adds a live sort toggle and pagination so the card stays usable at that scale.

A related pain point on the same large installations: once you throttle an entity it moves into the (now paginated) Throttled tab, and there was no quick way to find it again to mark it accepted without paging through everything already reviewed.

This is a small, self-contained addition scoped entirely to the card (no backend/service changes), so I went straight to a PR rather than opening an issue first. Hope that's OK.

What changed

• Throttled/Accepted tabs get a live sort-order toggle (Entity ID / Friendly name), sharing one setting between the two tabs. The initial default is settable via a new sort card option.
• All three tabs (Unthrottled, Throttled, Accepted) are now paginated client-side via a new page_size card option (default 50), instead of rendering as one long list.
• Unthrottled keeps its existing write-rate-first order from the backend top_writers response and hides the sort toggle, since it doesn't apply there.
• The existing limit option is unchanged — it still only bounds how many writers the backend returns for Unthrottled; page_size is a new, independent, purely client-side display setting.
• Bulk "set all to X" on Unthrottled still targets the full matching set, not just the visible page.
• Fixed a UX issue found during testing: navigating to a page with fewer rows than page_size shrank the card, which could trigger a Lovelace masonry reflow and move the card unexpectedly on screen. The row-list container now reserves a full page's worth of height once pagination is active, so the card's footprint stays constant across pages.
• The Throttled tab gets a live All/Unaccepted filter (next to the sort toggle), so an entity you've just throttled — which moves it out of Unthrottled — is easy to find and accept without paging through everything already reviewed. Unthrottled and Accepted tabs are unaffected.
• The Throttled tab's count badge shows "shown/total" (e.g. Throttled (88/767)) while the filter is narrowing the view, so it's clear you're looking at a subset rather than the full list.
• The toolbar (sort + filter) stays visible even when the current tab has zero rows — filtering Throttled down to nothing no longer hides the control needed to switch back to "All".
• Version bump to 1.1, a CHANGELOG.md entry, README documentation for the two new options, and the card's console-banner version kept in sync via scripts/sync_card_version.py.

Card-only change (recorder-throttle-card.js, manifest.json, CHANGELOG.md, README.md); no backend/service changes.

Testing

• node --check on the card file (syntax; no local build/test harness in this repo).
• python3 scripts/sync_card_version.py --check passes.
• Manually verified on a live Home Assistant instance with a large real-world entity count: sort toggle behavior on Throttled/Accepted (hidden on Unthrottled); independent per-tab pagination at the configured page size; prev/next boundary disabling; sort-change page reset; bulk action still affecting the full Unthrottled set; the height fix confirmed to eliminate the masonry-reflow jump; the filter correctly narrows the Throttled tab to unaccepted entities only; the tab badge switches to "shown/total" while filtering and back to a plain count when off; the toolbar remains visible and usable when the filtered view is empty; accepting an entity drops it out of the filtered view on the next refresh.

[pos-ei-don]

Thanks a lot for this, and apologies for the long silence — notifications for this repo weren't reaching me.

The feature set is exactly what large installations need, and I'd like to merge it. Release 1.1 landed in the meantime and touches the same card (the Unthrottled list now asks top_writers with exclude_throttled: true, so throttled entities no longer crowd it out before the limit; rates for the other tabs come from a second call). Could you:

1. rebase onto current master (the card merges cleanly; CHANGELOG.md conflicts),
2. drop the CLAUDE.md from the PR — it's a local working file, not something I want to ship in the repo,
3. leave the version in manifest.json (and the card banner) as it is — I'll bump it when releasing.

After that I'll review and test it on a large instance. Thanks again!

[cerebrate]

This should do it.

(I think at this point it's messy enough to really deserve a squash merge, heh.)

[pos-ei-don]

Thanks — tested with a large entity set and squash-merged. It shipped in 1.2, together with three small follow-ups from review: the sort/filter toolbar wraps on narrow cards, the reserved page height no longer shrinks after a one-row last page (the last row's border is now transparent instead of removed), and page_size/limit are parsed as numbers (a quoted "50" used to concatenate when paging).