The watchlist catalog page silently returned the stored list order while
its sort dropdown claimed "Date Added", and mirroring a provider's list
order (e.g. MDBList) was off by default, so synced watchlists appeared
in first-sync-time order with no way to tell what was happening.
- Web: the watchlist source now uses the same source-order sentinel as
collections — the dropdown shows "List Order" as the default, and an
explicit "Date Added" pick sends sort=added_at instead of being
stripped (previously indistinguishable from the default).
- Server: on personal lists (watchlist/favorites) an explicit added_at
sort now takes the source-order path, where added_at means "date
added to the list"; the query executor path sorted by the library's
created_at instead. History keeps the executor path since its ID
loading ignores the sort.
- watchsync: new connections default sync_watchlist_order_enabled to
true, with a migration flipping existing rows to match. Providers
without the provides_watchlist_order capability ignore the flag at
sync time.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
