Status: IN
In-place mutation of input arguments (sorting, element swaps, pointer reassignment) has no observable effect beyond the current call because LeetCode's judge invokes each solution exactly once per test case, making aliasing and input reuse irrelevant under the submission model.
Mutation is invisible in LeetCode's single-call model, but the documented sort-mutations would surprise any caller that reads the input after the call
Depends on (SL): in-place-mutation-with-return-convention, no-validation-is-deliberate-contract
Unless: max-distance-mutates-input, distance-value-mutates-arr2