Feature
The client-side set listing comparators (ChecklistSearch on the home and checklists pages, and the Sets coverage table) now fall back to created_at for undated sets, matching the index SQL sort so newly-added sets surface by recency instead of sinking alphabetically.
Client Sort: Recency Fallback Everywhere
The SQL index sort already fell back to created_at for undated sets, but the client components re-sorted the results with the old "undated sets last" rule, overriding it. They now mirror the SQL exactly.
- ChecklistSearch (home page and
/checklists) and the Sets coverage table (/sets) now sort byrelease_date ?? created_atdescending, with name ascending as the tiebreaker. - No re-shuffle: the client order now matches
COALESCE(release_date, created_at) DESC, name ASC, so the ~776 sets without a release date surface by when they were added rather than sinking to the bottom alphabetically.