Don't let the body-location probe's detail line contradict its own verdict (#690)

Packages/WhoopProtocol/Sources/WhoopProtocol/BodyLocationProbe.swift

@@ -99,7 +99,7 @@ public enum BodyLocationProbe {
                 sb += "Δ vs previous capture: first capture — probe again in another position to diff"
             }
         } else {
-            sb += "\nNo payload beyond the command byte (bare stub) — no body-location data on this firmware"
+            sb += "\nNo payload beyond the command byte (bare stub) — this reply carried no body-location data, which is not the same as the firmware having none (see the Verdict above)"
         }
         return (sb, payloadHex)
     }

Packages/WhoopProtocol/Tests/WhoopProtocolTests/BodyLocationProbeTests.swift

@@ -64,6 +64,12 @@ final class BodyLocationProbeTests: XCTestCase {
         let (text, payHex) = BodyLocationProbe.format(frame: hexToBytes("aa0700fa24005446758858"), cmdOff: 6, isWhoop5: false, prevPayloadHex: nil)
         XCTAssertTrue(text.contains("bare stub"))
         XCTAssertNil(payHex)
+        // A bare stub is one reply, not a firmware capability. The Verdict line already calls it
+        // "ambiguous"; the detail line used to contradict it with "no body-location data on this
+        // firmware", which is the conclusion a reader would quote. Neither line may say it. (#914 class)
+        XCTAssertTrue(text.contains("ambiguous"), text)
+        XCTAssertFalse(text.contains("no body-location data on this firmware"), text)
+        XCTAssertTrue(text.contains("not the same as the firmware having none"), text)
     }
 
     /// Golden FULL-output lock: pins the exact byte-for-byte report so the Swift and Kotlin twins can't

android/app/src/main/java/com/noop/ble/WhoopBleClient.kt

@@ -1298,7 +1298,7 @@ class WhoopBleClient(
                     sb.append("Δ vs previous capture: first capture — probe again in another position to diff")
                 }
             } else {
-                sb.append("\nNo payload beyond the command byte (bare stub) — no body-location data on this firmware")
+                sb.append("\nNo payload beyond the command byte (bare stub) — this reply carried no body-location data, which is not the same as the firmware having none (see the Verdict above)")
             }
             return sb.toString() to payloadHex
         }

android/app/src/test/java/com/noop/ble/BodyLocationProbeFormatTest.kt

@@ -2,6 +2,7 @@ package com.noop.ble
 
 import org.junit.Assert.assertEquals
 import org.junit.Assert.assertNull
+import org.junit.Assert.assertFalse
 import org.junit.Assert.assertTrue
 import org.junit.Test
 
@@ -61,6 +62,10 @@ class BodyLocationProbeFormatTest {
     @Test fun bareStubIsCalledOut() {
         val (text, payHex) = WhoopBleClient.formatBodyLocationProbe(hexToBytes("aa0700fa24005446758858"), 6, false, null)
         assertTrue(text.contains("bare stub"))
+        // Twin of the Swift assertion: a bare stub is one reply, not a firmware capability.
+        assertTrue(text.contains("ambiguous"))
+        assertFalse(text.contains("no body-location data on this firmware"))
+        assertTrue(text.contains("not the same as the firmware having none"))
         assertNull(payHex)
     }