Root cause: _animate_unit_move computed unit_above by subtracting from_tile_top from body.position.y. If a state update arrived before the board rebuilt (body still mid-tween), that subtraction produced a value > 0.28 which then compounded each successive move. Secondary: from_tile_top was typed :int, silently truncating the float sum of tile_base + tile_h. Fix: store above_tile as body metadata in _add_unit_mesh (0.28/0.4/0.5 per card type). _animate_unit_move reads the stored constant directly — it is immune to board rebuild timing. Generated with [Claude Code](https://claude.ai/code) via [Happy](https://happy.engineering) Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: Happy <yesreply@happy.engineering>