[XxUnkn0wnxX]

• PR is based on the DEVELOP branch
• Don't send big changes all at once. Split up big PRs into multiple smaller PRs that are easier to manage and review
• Read the contribution guide

Closes #12266

🎯 Why

History displays Medusa's show title, but the Episode filter previously searched only the stored release/resource text. A user could copy the title shown in the table and still get no result when the downloaded release used a Romaji, scene, or alternate title.

Testing that filtering path also exposed correctness gaps in the same History API, store, and layout flow. Detailed Provider sorting could fall back to natural database order, Compact sorting operated on raw rows instead of completed groups, malformed saved sorts could prevent the page from mounting, and live Compact events could not safely be inserted into aggregated rows.

This change keeps those related History behaviors together so title matching, filters, sorting, pagination, saved preferences, and live refreshes share one consistent request contract.

🛠️ What changed

🔎 Title and column filtering

• Episode searches match stored release text, the displayed show name, known aliases, canonical show identifiers, and rendered episode identifiers through the row's stored show identity.
• Matching remains case-insensitive and partial without hardcoding indexer prefixes.
• Episode, Action, Provider, Quality, Size, and Client Status continue to narrow the result together with AND behavior.
• Episode and Provider inputs normalize accidental outer whitespace while retaining intentional text inside matching quote or backtick wrappers.
• Size accepts strict < or > comparisons with unitless MB or explicit, case-insensitive MB/GB units and up to two decimal places. Invalid input does not replace the active filter.
• Client Status distinguishes a cleared field from zero-valued Snatched. Nonzero selections use contains-all bitmask matching while allowing additional stored states.
• Layout changes carry only compatible Episode, paging, and sort state; unsupported layout-specific filters and sorts return to safe defaults.

🔄 Sorting, grouping, and live updates

• Validates the one-field History sort shape and direction before constructing SQL, while preserving the existing forgiving fallback for malformed or unsupported sorts.
• Corrects the providerId mapping used by Detailed Provider sorting.
• Includes season-zero episodes in Compact grouping and derives each group's Time from its newest child event.
• Sorts Compact Time and Subtitled values after grouping and before pagination, with deterministic tie handling.
• Orders rendered Compact child events newest-first without mutating the API response array.
• Keeps Detailed and Compact visibility preferences layout-scoped, validates saved sort state, and carries only compatible sort state when switching layouts.
• Serializes zero-valued Snatched as [0] / ['Snatched'] in live History events while preserving None and composed masks.
• Refetches the exact active Compact query after a live event instead of inserting raw event data into an aggregated table.
• Ignores stale History responses, keeps loading attached to the newest request, and clamps/refetches pages when the result count shrinks.
• Detailed live updates reload the current server query so newly displayed rows still satisfy the active filters, sort, and page.

🧪 Expected filter behavior

Input	Expected result
Displayed English title	Rows for that show even when the stored release uses another known title
Romaji, scene, or known alias	The same show's rows through its stored identity
Partial or mixed-case title	Case-insensitive partial matching
Direct release fragment	Matching release/resource rows
Canonical show identifier	Rows for the exact supported indexer and show ID
Canonical rendered episode identifier	Rows for the exact show, season, and episode
Episode plus another column	A progressively narrower result set

Unquoted outer spaces are treated as accidental. Complete matching wrappers ('...', "...", or backticks) retain spaces inside the pair. Internal apostrophes and punctuation remain ordinary title text.

For Size, <300 and >400 continue to mean MB, while values such as >1.3gb, <900.45 MB, and >2.4GB use the requested unit. Incomplete or malformed text leaves the currently applied comparison unchanged until corrected or cleared.

Clearing Client Status applies no status predicate. Snatched matches the exact stored zero state, while one or more nonzero selections require those bits and still allow additional stored states.

✅ Validation

• Combined History API and websocket suite: 284 passed.
• Focused History frontend suites: passed.
• Full frontend Jest suite: 38/38 suites passed; 269 passed, 1 existing skip, and 82 snapshots passed.
• Full ESLint: zero errors and six existing warnings in untouched files.
• Stylelint and focused Flake8 E/F/W checks: passed.
• Development theme build/check: passed on a clean repeat; dark and light runtime bundles are byte-identical.
• Direct merge simulation into the current develop: passed with zero conflicts.
• Merge simulation with the independent table-row hover branch: passed with zero conflicts.
• Firefox Developer Edition integration QA passed across filtering, sorting, layout transitions, saved preferences, pagination, and Compact live refresh.
• Fork validation: all 26 GitHub Actions jobs and both Codecov coverage checks passed for the promoted feature head.
• git diff --check: passed.

Live data did not contain an exact zero-status Snatched row or a visible season-zero Compact group during the final browser pass. Both paths are covered by the in-memory API and websocket regression suites without manufacturing database rows.

📦 Scope

• Most of the diff size is regression coverage; production changes are confined to the History API, store, components, and generated runtime bundles.
• The only non-History change is a Generic Provider test fix. The larger suite can take longer than that test's 60-second collection-time tolerance on Windows, so it now compares against the parser's execution-time clock; provider behavior is unchanged.
• No database schema or migration changes.
• No dependency, logging, timezone, download-client, or scheduler changes.
• No table-hover styling changes; that was merged separately in table row hover colors.

🔗 Related issue

• Issue: pymedusa/Medusa#12266