Library analyser, jobs and scheduled tasks

Why background work exists#

Discovery makes a title visible; deeper analysis makes it trustworthy. Finetic separates work classes so optional enrichment cannot monopolise resources needed for playback.

Scan flow#

1. Enumerate configured roots and identify candidate files.
2. Reconcile stable media identity with the catalogue.
3. Parse local metadata and publish usable cards.
4. Probe container and stream facts when missing or stale.
5. Queue artwork, metadata, subtitle and credits work.
6. Run maintenance and deep analysis at lower priority.

Routine scans do not enumerate every keyframe in every file. Random-access indexes are created lazily when remux or seek preparation genuinely needs them.

Job states#

Queued has not started. Running owns a worker. Waiting for resources is admitted but intentionally paused by playback or storage pressure. Failed contains an actionable category and retry policy. Complete records a result and duration.

Running status comes from the actual scheduler, not a hard-coded page label. Scheduled tasks display their next run and retain recent executions.

Progress#

Discovered totals can grow during enumeration, so the overall denominator can change. Within a stable set, completed units should never decrement. A progress indicator should state its phase and counts rather than presenting an unexplained percentage.

Concurrency#

Presentation work receives more parallelism than deep optional work. Active playback can reduce or pause probes, credits and enrichment. Storage pressure stops cache-growing work before the disk is exhausted.

Failed jobs#

Filter by kind and failure reason. A large cluster with the same provider response usually needs one configuration fix. Retry only after the cause changes; repeated blind retries create noise and rate-limit pressure.