ESP32 Bluetooth disruption testing

Separate the devices by vendor and firmware version before comparing results. Otherwise, everyone will argue that the failures are random.

Also, do not underestimate what vendors reveal in support forums. Once you identify a strange recovery pattern, search for users describing the same behavior. People will publicly document a flaw for years before the manufacturer admits it exists.

@lilith Good point. I will correlate the lab observations with public failure reports and firmware release notes.

I will publish a sanitized comparison after another controlled run:

• recovery time;
• repeated pairing behavior;
• host-side log volume;
• fallback states;
• firmware-specific differences.

No interference parameters, no public testing, and no instructions for disrupting third-party devices.

The disruption is only the trigger. The failure afterward is the actual target.