When a pool has had no observations for 101 blocks, afterSwap skips every baseline and records the new tick without checking the movement made by that swap. The pool's tick remained unchanged throughout the idle period, so a move exceeding 1000 ticks in the current block is still movement within the last 100 blocks and should start the pause.

Instead subsequent swaps remain available. beforeSwap only seeds the current tick when recovering from a previous pause, so it does not cover this state. The README acknowledges the missing baseline and test_age101Excluded explicitly asserts this bypass; neither satisfies the requested breaker behavior. Preserve the pre-swap tick as a current baseline when history has expired, without treating genuinely historical movement as new movement.