strafe: default range 200 -> 325 (mid of the owner's 300-350 band), with the j107 evidence noted

common_libs/movements/strafe.nim

@@ -142,7 +142,7 @@
 ##   TR_STRAFE_DWELL_MIN    6      min ticks before a re-pick
 ##   TR_STRAFE_DWELL_MAX    20     max ticks before a re-pick
 ##   TR_STRAFE_LOG          off    presence-based: echo one line per pick
-##   TR_STRAFE_RANGE        200.0  target enemy distance (px; == TR_POWER_FAR_DIST)
+##   TR_STRAFE_RANGE        325.0  target enemy distance (px); mid of the 300-350 band
 ##   TR_STRAFE_RANGE_TOL    25.0   dead-band half-width (px): tilt = 0 inside
 ##   TR_STRAFE_TILT_MAX     15.0   max line tilt off the perpendicular (deg)
 ##   TR_STRAFE_TILT_GAIN    0.10   deg of tilt per px of error BEYOND the band
@@ -251,10 +251,15 @@ const
   DefaultStrafeReach    = 144.0
   DefaultStrafeDwellMin = 6
   DefaultStrafeDwellMax = 20
-  ## Range control (j111). 200 px is NOT invented here: it is exactly
-  ## TR_POWER_FAR_DIST, the distance at which the bot's own power policy stops
-  ## treating the enemy as close, so the mover and the gun agree on "range".
-  DefaultStrafeRange    = 200.0
+  ## Range control (j111). Default = 325 px, the midpoint of the owner's
+  ## stated 300-350 px band, chosen after watching live battles.
+  ## History: j111 shipped 200.0 (= TR_POWER_FAR_DIST, where the power policy
+  ## stops treating the enemy as close). The owner moved it to 300-350, which is
+  ## also the direction the one piece of hard evidence points - j107 measured
+  ## that drifting 25-30 px CLOSER made damage/run AND round wins WORSE.
+  ## This is NOT a proven optimum: it is a knob with a band. A/B it before
+  ## claiming anything, because our hit rate actually PEAKS around 100-200 px.
+  DefaultStrafeRange    = 325.0
   DefaultStrafeRangeTol = 25.0
   DefaultStrafeTiltMax  = 15.0
   DefaultStrafeTiltGain = 0.10