Kotlin publishes resp_seq and result on a command response; Swift publishes neither #894

Found by the #891 fixture in #893.

Framing.decodeCommandResponseWhoop5 (Kotlin) sets three fields from every COMMAND_RESPONSE:

resp_cmd @10   resp_seq @11   result @12  → FAILURE(0)/SUCCESS(1)/PENDING(2)/UNSUPPORTED(3)

decodeWhoop5CommandResponse (Swift) sets only resp_cmd. resp_seq and result appear nowhere in Packages/WhoopProtocol — not on the 5/MG path and not on the 4.0 one. The three real MG frames in #893 decode result=SUCCESS(1) on Android and produce no result field at all on Apple, from identical bytes.

Why it is worth closing

The result code is the diagnostic for a probe reply — it is the entire evidence column in #891, and UNSUPPORTED(3) is how the MG haptics rejection was identified in #48. Consequences today:

• Every Swift probe re-derives the byte itself rather than reading a parsed field: FeatureFlagProbe.resultLabel, DeviceConfigReadProbe (which calls into it), BodyLocationProbe ("Result code @12"). Three private reimplementations of one two-line decode, and any new probe needs a fourth.
• An Apple strap log does not show the result of a command the app sent; an Android one does. Cross-platform bug reports are not comparable, which is the same failure WHOOP 4.0 (recent firmware): every battery source is dead — opcode 26 silent, opcode 98 answers empty, no BATTERY_LEVEL events, 0x2A19 constant 100 #791 fixed for event names and Name every command the schema names in Android strap logs (#891) #893 for command names.

Whoop4ResponseResultTest.kt records that Kotlin closed the 4.0 half of this deliberately; the Swift side was not part of that change.

Scope

Publish both fields on both families in the Swift interpreter, matching the Kotlin key names and label strings exactly ("SUCCESS(1)", not "SUCCESS"), then assert them on the #893 fixtures so the two suites agree on the same bytes. Worth checking whether adding two entries to the field map disturbs any byte-map consumer or field-count assertion before landing.

Optional follow-on once the field exists: collapse the three probe-local resultLabel helpers onto it.