Status: IN
Solutions systematically choose integer operations — math.isqrt over math.sqrt, integer division over float division, sum comparison over average comparison — to avoid floating-point precision loss that could produce incorrect results for large inputs.
four independent solutions independently chose integer arithmetic to dodge the same class of bug (float precision near integer boundaries), indicating a deliberate defensive pattern
Depends on (SL): isqrt-over-sqrt-for-large-inputs, pivot-integer-isqrt-not-sqrt, sum-substitution-avoids-float-precision, percentage-floor-integer-arithmetic