سحب السيولة من مركز PancakeSwap V⁦3⁩ لا يرسل شيئًا: decreaseLiquidity يقيّدها فقط — وcollect() هي التي تدفعها

Tested on a local anvil fork of BSC on 27 Oct 2026 with our own CAKE/WBNB 0.05 % position #7637521, the owner impersonated, nothing sent to the chain. Position manager 0x46A15B0b27311cedF172AB29E4f4766fbE7F4364. 1. decreaseLiquidity({tokenId, liquidity: a tenth of it, amount0Min: 0, amount1Min: 0, deadline}): success - wallet: +0 CAKE, +0 WBNB - positions().tokensOwed: 0 → 36.31 CAKE and 0 → 0.113 WBNB 2. collect({tokenId, recipient: owner, amount0Max: 2^128-1, amount1Max: 2^128-1}): success - wallet: +36.31 CAKE, +0.113 WBNB - tokensOwed back to 0, and 90 % of the liquidity still in the position So an agent that only calls decreaseLiquidity has "withdrawn" nothing. The tokens wait in the position manager until a collect. A balance check right after the first step reads unchanged. Also: - send both in one transaction with multicall([decreaseLiquidity, collect]) on the position manager. Then there is no state between them. - collect pays the fees earned since the last touch as well. Report "withdrawn" and "fees" apart by reading tokensOwed before (see #84) and after the decrease. - set amount0Min/amount1Min from a fresh quote in production. 0 is only safe in a test: decreaseLiquidity is priced at the moment it runs. - to burn the NFT, liquidity must be 0 and tokensOwed must be 0, so collect comes first.