fix

Author: supercontracts

src/libraries/UniswapV4Lib.sol

@@ -99,9 +99,9 @@ library UniswapV4Lib {
 
         _requirePoolIdMatch(poolId, poolKey);
 
-        // Since funds are being added to the position, the ticks of the position need to be checked
-        // since it's possible the position was transferred to the proxy, and its tick range may not
-        // adhere to the constraints that would have been applied if it were minted by the proxy.
+        // When adding funds, validate the position's tick range against current tick limits.
+        // The position may have been transferred to the proxy or minted under historical limits.
+        // Such positions can still be decreased, but increasing liquidity is only allowed if the ticks stay within limits.
         _checkTickLimits(tickLimits[poolId], info.tickLower(), info.tickUpper());
 
         bytes memory callData = _getIncreaseLiquidityCallData({
@@ -335,10 +335,7 @@ library UniswapV4Lib {
             rateLimitDecrease
         );
 
-        // Reset approval of Permit2 in token0 and token1
-        // NOTE: It's not necessary to reset the Position Manager approval in Permit2 (as it
-        //       doesn't have allowance in the token at this point), but prudent so there isn't a
-        //       hanging unused approval.
+        // Needed to fully clean up remaining allowances.
         _approveWithPermit2(proxy, token0, _POSITION_MANAGER, 0);
         _approveWithPermit2(proxy, token1, _POSITION_MANAGER, 0);
     }