Unexpected sort order in moderation queue when "Priority" order is used

You’re correct that when selecting “Priority” order, they appear to be sorted by their score in descending order, then by created_at in ascending order.

On the other hand, I still consider this to be unexpected behavior. Unless I’m missing something, a reviewable’s score is only available via database access (whether direct access or via the data-explorer plugin)?