ble-name-whitespace: iOS strips the device name too, delete the entry

BluetoothNameFilter.matches on iOS now trims surrounding whitespace before
both criteria, as Android does, so both platforms conform to rule
ble-name-regex. Remove the entry, its marker on the BLE page and the rule's
reference to it, and record the stripping in the rule's iOS state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: Staacks

docs/file-format/bluetooth-low-energy.md

@@ -80,8 +80,6 @@ The apps use the regular expression engine of their platform (`java.util.regex`
 
 Both forms see the name with leading and trailing whitespace removed, as some devices pad their names: the phyphox:m advertises `phyphox:m 131` followed by a line break, and `nameRegex="phyphox:m( \d+)?"` matches it without having to allow for that. Whitespace inside the name is part of it.
 
-{{inconsistency:ble-name-whitespace}}
-
 ### BLE as input
 
 If data should be read from a BLE device and displayed in phyphox, the device should be defined within the input block of the phyphox file.

inconsistencies.yml

@@ -93,40 +93,3 @@
     length and different values on the two platforms; a power-of-two input
     gives identical results on both. This holds for fft and for its inverse
     ifft alike; dft and idft have no such restriction.
-
-- id: ble-name-whitespace
-  title: Whitespace around Bluetooth device names
-  area: file-format
-  status: decided
-  since: "1.21"
-  canonical: >-
-    The name and nameRegex criteria of a bluetooth element see the device name
-    with leading and trailing whitespace (spaces, tabs, line breaks) stripped;
-    nameRegex then has to match that whole stripped name (rule ble-name-regex).
-    Whitespace inside the name is part of it.
-  affects:
-    android: >-
-      Conforms on the development branch since 2026-10-14: BluetoothNameFilter.matches
-      strips the name, and every match site goes through it. Before, the scan dialog
-      trimmed the name and the other two sites (shipped experiments for a scanned
-      device in ExperimentListActivity.openBluetoothExperiments, the paired-device
-      shortcut in Bluetooth.kt) did not, so a phyphox:m was listed as supported but
-      offered an empty experiment list.
-    ios: >-
-      Matches the name as reported (BluetoothNameFilter.swift). The pattern is
-      compiled as ^(?:...)$, and ICU's $ also matches before a final line
-      terminator, so a single trailing newline - the phyphox:m case - is tolerated
-      by accident; leading whitespace or a trailing space or tab is not.
-  verified: >-
-    Symptom observed on hardware 2026-10-14: a phyphox:m was listed as
-    supported in the Android scan dialog but offered no shipped experiments
-    (development branch), while iOS offered them. The trailing newline was seen
-    in a BlueZ scan of a phyphox:m on 2026-08-27; that the Android stack
-    reports the name the same way is inferred from the symptom. Not yet
-    re-checked on a device after the Android fix.
-  summary: >-
-    Some devices pad their advertised names, the phyphox:m with a trailing
-    newline. Android strips surrounding whitespace before matching; iOS does
-    not, and only tolerates a single trailing newline by a quirk of its
-    regular expression engine. A device with other padding would match its
-    experiments on Android only.

spec/rules.yml

@@ -483,7 +483,6 @@ rules:
       previously connected device rather than a shortened advertised one;
       an author who sees a device under a shortened name should match that.
     applies_to: "bluetooth@nameRegex in the input and the output block"
-    inconsistency: ble-name-whitespace
     state:
       android: >-
         Conforms as of the development branch (24a3e752, 2026-10-05; the
@@ -499,15 +498,16 @@ rules:
         from the shipped files. Test BluetoothNameFilterTest carries the
         ble-name-regex-match tag.
       ios: >-
-        Conforms as of the development branch (a8e25dbb, 2026-10-05):
+        Conforms as of the development branch (a8e25dbb, 2026-10-05; the
+        whitespace stripping, decided 2026-10-14, in
+        BluetoothNameFilter.matches, which every match site goes through):
         BluetoothNameFilter (Experiments/BluetoothNameFilter.swift)
         compiles the pattern once at parse time with NSRegularExpression
         as ^(?:...)$, so alternatives backtrack to the whole name like
         Java's matches(); it replaces the name string on the descriptors,
         in BluetoothScan and in ExperimentManager's shipped-experiment
         lookup. A pattern that does not compile is an ElementHandlerError.
         Test BluetoothNameFilterTests carries the ble-name-regex-match tag.
-        Does not strip whitespace yet (ble-name-whitespace).
       editor: >-
         Conforms as of main (8fa26a2, 2026-10-05): both bluetooth blocks
         carry a "device name (regular expression)" field