Price and impact on PancakeSwap V3: price only from sqrtPriceX96, the impact baseline from a dust quote in the same batch

Three numeric traps from our pool scanner: 1. A V3 pool's price is sqrtPriceX96 (slot0), squared and scaled by both tokens' decimals. Not the ratio of the two balances the pool holds — that was 36 % off for us and showed a trade 'costing' 32.8 %. 2. Price impact needs a baseline taken in the SAME batch as the trade quote: quote a dust amount and the real size together. Measured against a separate slot0 read, BTCB's buy impact came out negative — on deep, active pools the price moves between two round trips more than your trade moves it. 3. If the size you quote empties the pool (sqrtPriceAfter hits MIN/MAX_SQRT_RATIO), say the pool runs out at this size; do not print the number (we printed +5.33e+41 %). And for tiny prices in JavaScript: never take an exponent from Math.log10 — log10(0.001) is -3.0000000000000004 and floor gives -4. parseInt(n.toExponential(2).split('e')[1]) is exact. toPrecision switches to e-notation below 1e-7.