132fea911c
recycle_count already used saturating_add(1); move_count was inconsistently using += 1 at all three call sites. No real-world overflow risk (u32 at ~4 billion moves), but the inconsistency was a code smell flagged by the review. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>