Please address the comments from this code review:

## Overall Comments
- The new adaptive rotation update condition `if float64(actualDeltaRot)+rotAdjState.deltaRot > param.RotationLowerThreshold` mixes signed deltas; consider using absolute values (e.g. `math.Abs`) or a clearer metric so that opposite‑direction rotations don't accidentally suppress or exaggerate the adjustment.
- `ROTATION_ADJUSTMENT_LOWER_BOUND` is no longer used after removing `calcAppliedDeltaRotation`; consider deleting this constant to avoid confusion about dead configuration knobs.
- `SwipeSync` now implements two `PostTouchMove` calls with sleeps but still takes a `durationMillis` parameter that no longer represents a swipe duration as before—consider renaming the function or parameter, or updating its behavior, so its semantics remain intuitive for callers.

## Individual Comments

### Comment 1
<location path="agent/go-service/map-tracker/move.go" line_range="236-239" />
<code_context>
-					if movement.Speed < MovementSprint.Speed {
-						aw.KeyTypeSync(KEY_SHIFT, 100)
-						movement = &MovementSprint
+			// Update adaptive rotation speed
+			if rotAdjState != nil {
+				// Check if last rotation adjustment is completed
+				if loopStartTime.Sub(rotAdjState.startTime) > rotAdjState.expectedElapsed {
+					// Check if player is moving and rotating sufficiently to trust rotation measurement
+					distTravel := math.Hypot(float64(curX-rotAdjState.fromPos[0]), float64(curY-rotAdjState.fromPos[1]))
</code_context>
<issue_to_address>
**issue (bug_risk):** Rotation adjustment state is never cleared after use, so the same measurement may be reused and applied repeatedly.

Because `rotAdjState` remains non-nil and unchanged after the elapsed-time check and adaptive update, the same `fromPos/fromRot/deltaRot/startTime/expectedElapsed` are re-applied on every subsequent loop. This turns a single adjustment into a repeated influence on `rotationSpeed`.

If each adjustment is meant to be one-shot, clear the state once it’s used (e.g. `rotAdjState = nil`) or update fields like `startTime`/`fromPos` so the measurement is not reused unchanged.
</issue_to_address>

### Comment 2
<location path="agent/go-service/map-tracker/move.go" line_range="243-245" />
<code_context>
+					// Check if player is moving and rotating sufficiently to trust rotation measurement
+					distTravel := math.Hypot(float64(curX-rotAdjState.fromPos[0]), float64(curY-rotAdjState.fromPos[1]))
+					if distTravel > rotAdjState.expectedElapsed.Seconds()*MovementWalk.Speed {
+						// Check if rotation difference is sufficient to consider adjusting rotation speed
+						actualDeltaRot := calcDeltaRotation(rotAdjState.fromRot, rot)
+						if float64(actualDeltaRot)+rotAdjState.deltaRot > param.RotationLowerThreshold {
+							idealRotSpeed := rotAdjState.deltaRot / (float64(actualDeltaRot) + 1e-6)
+							if idealRotSpeed >= ROTATION_MIN_SPEED && idealRotSpeed <= ROTATION_MAX_SPEED {
</code_context>
<issue_to_address>
**issue (bug_risk):** Rotation threshold check mixes signed deltas and may never trigger for certain directions.

`actualDeltaRot` and `rotAdjState.deltaRot` are signed, but their sum is compared to a positive `RotationLowerThreshold`. When one or both are negative, the sum can stay below the threshold even for large actual rotation, so the check may never pass for some directions. If the intent is to gate on rotation *magnitude*, this should use an absolute value (e.g., `math.Abs(...)`) rather than a signed sum, otherwise the adaptive update is biased to particular sign combinations.
</issue_to_address>