Runs and item history

Runs contains two related views.

Run overview

Newest run cards show run ID, profile name, source→target icons, full/ incremental/webhook type, manual/automatic trigger, live/dry-run mode, start time, change count, status, and Reverted/Partially reverted chips where applicable.

Selecting a run adds a removable filter to the global item panel. The run detail also shows progress/logs, fatal error, exports, cancel, and bulk Apply/Revert controls.

Global item history

The server pages grouped item cards from all runs, newest first. A card groups operations with the same run, profile lifecycle, source item, target item, and mapping segment. Each historical occurrence remains separate.

Filters include run, profile lifecycle, full/incremental/webhook, manual/ automatic, live/dry-run, run status, source/target provider and instance, changes/unmatched/skipped/errors, apply state, feature, mapping type, source or target title, and general contained text. Result filters combine with OR inside their group; different filter groups combine with AND. URL state preserves the selection.

Compact cards and details

The card shows source-first artwork, separate source and target titles, profile, providers, feature/result/apply badges, and concise before→after chips. Details load lazily and show:

• reasons, deduplicated when repeated;
• mapping provenance and identifiers;
• compact source observations and active rules;
• complete captured target state, with changed fields highlighted;
• planned/applied update and operation audit;
• suppressed Letterboxd bulk diary dates where relevant.

Historical operations created before complete target snapshot capture show a clear warning instead of implying the partial data is the whole target state.

Exports

JSON and CSV exports represent the selected run’s safe audit data. Treat exports as potentially sensitive because they may contain titles, IDs, progress, ratings, and dates even though credentials and opaque secrets are excluded.