feat(collections): playlist auto-creation, position ordering, hide_finished, Up Next, dashboard eligibility

Phase 2b + 3 of the metadata overhaul (plan §2.4, §3.1-3.7).

Auto-playlist collections (§2.4): the scanner turns obviously-playlist
sidecar series (explicit '(Reading Order)'/chronological/publication/
in-order/timeline markers only — precision over recall) into curated
static collections: upsert by view_settings.imported_from_series then
name (rename-safe), position set ONLY on insert (clean integers; 1.5/1a
stay unpositioned rather than guessing), membership add-if-missing,
never removed or re-ordered by rescans, provenance in description +
view_settings, show_on_dashboard true (dashboard-eligible by design),
'scanner.auto_playlist_collections' setting (default on, Settings
Registry + schema seed).

Ordering (§3.1-3.2): collection listings order position ASC NULLS LAST
then added_at ASC (was added_at DESC — walked playlists backwards);
PUT /api/collections/:id/items/order applies full-order rewrites
(owner-only, service-gated).

hide_finished + Up Next (§3.3-3.4): GetCollectionItemsForDashboard
gains viewer_user_id + hide_finished (LEFT JOIN reading_progress,
COALESCE percentage < 0.999) and viewer_percentage rides the row for
card graying; GetCollectionUpNext serves the collection's reading-queue
head with the family-lens visible-library array enforced.

Dashboard (§3.5): user collections are dashboard-ELIGIBLE BY DEFAULT —
the show_on_dashboard gate (never writable for user rows since the
column shipped) is gone from GetUserCollectionsForDashboard; hiding
stays dashboard-prefs (hidden_collections) territory; hide_finished
filtered-everything now emits a Complete section instead of silently
vanishing; sections JSON carries is_playlist/complete.

Series page ordering hardening (§3.6): GetSeriesBooks tiebreaks by
title ASC — NULL/tied numbers previously returned heap (scan) order,
which is what the user saw.

Frontend custom-section-builder note: the builder has sent
show_on_dashboard: true since its creation; the API never bound it.
User-row visibility is now intentionally prefs-governed, so the field
stays unbound by design (documented in code).

Pins widened (docs/contract_pins.md): collection detail + up_next;
dashboard sections + is_playlist/complete; new reorder endpoint
recorded.

Verified: TestPlaylistCollectionsEndToEnd (new, full e2e: sidecar
series split, collection auto-creation with position 7, rescan
idempotency, owner-only reorder, finished-filter + completion marker +
Up Next drain) plus the full affected integration sweep green.

docs/contract_pins.md

@@ -136,3 +136,19 @@ cover_image_path, has_conflict, format_group, badge`.
   still accepted (arrays win when both present).
 - Override keys unchanged: `author`/`publisher` override names are preserved
   for existing rows and now protect the arrays.
+
+## 2026-10-19 — A2c: collections/playlists phase
+
+- `GET /api/collections/:id` gained ADDITIVE `up_next` (array of
+  `{id, title, author, cover, format, progress}` — the static collection's
+  reading queue head in position order, viewer-progress-aware; empty array
+  for smart collections).
+- `GET /api/dashboard/sections` rows gained ADDITIVE `is_playlist` (bool —
+  collection was imported from a sidecar ordering construct) and
+  `complete` (bool — hide_finished filtered every item out of a non-empty
+  collection; render "playlist complete").
+- `PUT /api/collections/:id/items/order` is a NEW endpoint (owner-only,
+  full ordered id list → positions 1..n).
+- User collections are dashboard-eligible by default (the
+  show_on_dashboard gate is gone from GetUserCollectionsForDashboard);
+  hiding stays dashboard-prefs (`hidden_collections`) territory.