fix(inmotion-v1): send max-speed little-endian so the wheel stores the right value

Tester set 39 km/h and the V8S recorded 23, and legal mode drifted. Cause: a
byte-order bug. setMaxSpeed encoded (kmh*1000) BIG-endian (HIGH byte at slot 4),
but the wheel reads the field LITTLE-endian. 39 km/h = 39000 = 0x9858 sent as
`98 58` is read back as 0x5898 = 22680 ~= 23 km/h - exactly the reported value.

The slow-info confirms LE: the wheel reports 41 km/h as 0xa028 on the wire (`28 a0`).
So the parser was already correct; only the write was wrong-endian. Swap to LE
(LOW byte slot 4, HIGH byte slot 5). Legal mode compares the written value to the
wheel readback, so this fixes that too. The old code comment even flagged this
("spec says LE but worked example takes precedence... verify against a real
capture") - the capture proved the worked example wrong.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GADLyChheAoMX9dQbRgRnH

Author: eried

app/src/main/java/com/eried/eucplanet/ble/InMotionV1Commands.kt

@@ -94,20 +94,22 @@ object InMotionV1Commands {
     // --- Ride mode group (CAN 0x0F550115) ---
 
     /**
-     * Set max speed (tiltback). Encoded as `(kmh * 1000)` u16 with HIGH byte
-     * at slot 4 and LOW byte at slot 5, opposite of the rest of the
-     * protocol's little-endian convention. Spec section 6.2 worked example
-     * is unambiguous: 30 km/h -> 30000 = 0x7530, wire = `75 30`. The spec's
-     * type annotation says `LE` but the worked example takes precedence
-     * here. Verify against a real BLE capture if behaviour looks wrong.
+     * Set max speed (tiltback). Encoded as `(kmh * 1000)` u16 LITTLE-endian:
+     * LOW byte at slot 4, HIGH byte at slot 5. A real V8S confirms LE (matching
+     * the spec's type annotation, NOT the old "worked example" that implied
+     * HIGH-then-LOW): sending 39 km/h big-endian (`98 58`) made the wheel store
+     * 0x5898 = 22680 ~= 23 km/h. The slow-info reads the field back LE too
+     * (41 km/h = 41000 = 0xa028, on the wire as `28 a0`), so write and read now
+     * agree. This also fixes legal-mode, which compares the written value to the
+     * wheel's readback.
      */
     fun setMaxSpeed(kmh: Float): ByteArray {
         val v = (kmh * 1000f).toInt() and 0xFFFF
-        val hi = ((v ushr 8) and 0xFF).toByte()
         val lo = (v and 0xFF).toByte()
+        val hi = ((v ushr 8) and 0xFF).toByte()
         return InMotionV1Protocol.buildFrame(
             CanId.RIDE_MODE,
-            byteArrayOf(0x01, 0, 0, 0, hi, lo, 0, 0)
+            byteArrayOf(0x01, 0, 0, 0, lo, hi, 0, 0)
         )
     }