Check priority gaps in the page experiences
Priority compaction behavior for page experiences has been standardized: gaps between experience priority values are now compacted consistently across all ADD, UPDATE, and DELETE operations. Previously, adding a new experience did not compact priorities, which could leave numerical gaps (e.g., priorities 0, 1, 4 instead of 0, 1, 2). Now the ADD operation also compacts priorities to maintain a contiguous sequence. Any integration or automation that reads or sets experience priority values by absolute number — rather than by relative order — may see those values shift after this change and should be updated to rely on ordering rather than specific priority integers.