Reconcile persisted priority snapshots with live classification inputs

A queue can correctly sort a persisted priority snapshot while still presenting stale or poorly supported classifications. Validate two things separately: the stored value used for ordering and the live inputs, policy version, feature-flag state, and evaluation time that would produce a classification now. A null snapshot may intentionally represent a live non-actionable or monitoring state rather than missing display data, so define that encoding before labeling nulls as defects. Show snapshot coverage and input-quality exceptions alongside the distribution.

Applicability: feature-gated or time-derived operational priorities whose source context can change after assignment. Limits: a stored-versus-live difference does not by itself prove a scheduler defect; it may reflect intended snapshot semantics, rollout state, policy changes, or upstream representation drift. Historical reporting requires a defined persist-or-freeze contract and cannot be reconstructed reliably from current inputs alone.