feat: per-type search filters on list pages (closes #25)

[mforce]

Closes #25. Adds a faceted-filter layer on every list page, end to end. URL-synced so deep-linking + browser back/forward work, AND across distinct filters and OR within multi-value filters per the issue spec.

Summary

Backend

Each list endpoint gains the missing filter params (existing ones — format, year, platform, digital — stay for back-compat):

	New params
GET /api/movies	yearFrom, yearTo, director, studio, genre, status, watchStatus, ratingMin, tag (repeatable)
GET /api/music	yearFrom, yearTo, artist, label, genre, status, ratingMin, tag
GET /api/games	yearFrom, yearTo, publisher, developer, status, completionStatus, digitalStore, ratingMin, tag

• Semantics: AND across distinct filters, OR within the multi-value tag filter (item matches if any of its tags are in the requested set). Per the issue: "OR semantics within multi-value filters."
• Tag values are lower-cased before the predicate runs (matches TagResolver), so the URL doesn't have to care about case.
• Predicates are explicit per type — three endpoints don't justify a generic builder.

Frontend

• services/filters.ts — per-type Filters interfaces, filtersToParams() / paramsToFilters() round-trip via URLSearchParams, and a useFiltersState(type) hook that bidirectionally syncs filters with the URL ?search. Unrelated params (e.g. the search input's q if you wire one up) are preserved on every update.
• services/collection.ts — useList(type, query, filters?) serializes filters into the request URL and folds them into the TanStack query key so a filter change refetches deterministically.
• components/FiltersPanel.tsx — collapsible disclosure with an active-count + Clear all; opens to a grid of fields appropriate to the type (year range, free-text substring inputs, enum selects, digital/physical toggle, min-rating select). Active filters render as removable chips above the panel body so users can drop one at a time.
• CollectionList wires the panel above the search input and threads the filters into useList.

Test plan

CI

• dotnet test — server 286/286 (was 278; +8).
• npm test -- --run — client 73/73 (was 66; +7).
• Server + Vite builds clean.

Backend (per-type filter tests)

• Movies: year range inclusive, director/studio/genre substring, status+watch+rating, tag OR semantics, AND combination (director=Nolan&yearFrom=2015).
• Music: year range + artist/label/genre/status/rating.
• Games: year range + publisher / developer / completionStatus / rating. Existing platform + digital tests stay green.

Frontend (filters.test.ts)

• filtersToParams: omits undefined / null / empty / NaN; repeats array values; stringifies booleans + numbers; drops empty strings inside arrays.
• activeFilterCount: counts set scalars, treats empty arrays as inactive, ignores empty strings.

Manual

• Open /movies, click Filters, set Director: Nolan + Year range: 2015–. List narrows to a single row. URL shows ?director=Nolan&yearFrom=2015. Browser back undoes filters one step.
• Refresh the page after deep-linking that URL: filters re-hydrate, list stays narrowed.
• Click the chip for Director: Nolan ✕ → removed from URL + list reflows.
• Clear all wipes every filter but leaves the search input's q alone.
• Repeat the smoke on /music and /games.

Out of scope

• Saved filter presets / "smart playlists" — listed in the issue, deferred.
• Sort options — separate enhancement; default OrderByDescending(AddedAt) stays.
• Server-side fuzzy / typo tolerance — LIKE %x% is enough at our cardinality.
• Multi-value enum filters (e.g. ?platform=Ps5&platform=Switch) — single-value selects today; documented as a future enhancement if the URL parameter starts feeling cramped. The server already accepts repeated tag so the same shape will plug in.

---

🤖 Generated with Claude Code

---

Generated by Claude Code