Status: IN
The sort-then-two-pointer pipeline's primary side effect — in-place sort mutation of the input array — has zero observable consequence because the single-call LeetCode context ensures no caller ever inspects the mutated ordering, making the most prevalent form of input modification in the entire codebase functionally invisible.
The most common pipeline's most impactful side effect (sort mutation) is invisible in the single-call evaluation context
Depends on (SL): sort-then-two-pointer-dominant-pair-pipeline, mutation-invisible-in-single-call-context