Widen Nintendo BLE discovery + scan diagnostics + in-menu errors (v1.2.2)

[mlstr0m]

Summary

Follow-up on the Reddit field report: permissions are fine, the 30 s search runs clean, but the controller is never matched — and the user saw no error because rumps notifications are invisible in run-from-source.

• Discovery: match manufacturer-data company ID 0x0553 (Nintendo's actual Bluetooth SIG ID, used by other Switch 2 community tools) in addition to 0x057E (Nintendo's USB VID). A controller advertising 0x0553 with no name was previously undetectable.
• Diagnostics: every failed scan round logs the devices it did see (name, RSSI, manufacturer data hex) — the next "not found" report will tell us exactly what the controller advertises.
• Visible errors: the last connection error now shows as a ⚠️ line in the dropdown while idle, so run-from-source users aren't flying blind.

Test plan

• 56 bridge + 50 DSU checks green locally and on CI (new: discovery filter matrix incl. 0x0553-no-name, unrelated-device rejection)
• Diagnostic log line format verified in a real scan
• ⚠️ Whether 0x0553 is what the reporter's controller actually advertises will be confirmed by their next log — the scan dump answers it either way

🤖 Generated with Claude Code