Make the BLE layer say what it actually received

Chasing a paddle that shifted on one platform and not the other cost
several rebuilds, and most of that was spent unable to tell two very
different situations apart: a pod that was sending nothing, and a pod
whose frames we were receiving and quietly discarding. The logs looked
identical because every decoder in this path fails by dropping.

`click.rs` now logs every notification with its length and bytes before
anything tries to interpret it, and the unhandled-frame line in
`controller.rs` carries the payload rather than just the type byte —
which is the least useful part of a frame you could not parse, since it
is usually the framing that is wrong and not the content.

The default log filter gains `bikecontrol_ble=debug`. It was `info`,
which silenced the entire crate that owns every BLE conversation —
subscribe failures included. Survivable on desktop where RUST_LOG can
override it; not on Android, which has no environment to set and is
exactly where the subscribe was failing.

Adds `probe listen`, which decodes nothing on purpose: the GATT tree with
descriptors (the CCCD value is where a subscribe goes wrong, and
`inspect` stops short of it), then a subscribe to every notifying
characteristic across all services, reporting each as ok or FAILED. Each
notification prints characteristic, length and raw bytes, and the summary
names the characteristics that stayed silent — the difference between a
quiet device and listening in the wrong place.

That last part is what settled this one: it recorded 304 button frames
from a pod the app was reporting as dead.

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

src-tauri/src/lib.rs

@@ -28,7 +28,12 @@ use crate::state::AppState;
 /// Set up `tracing` for whatever this platform calls "somewhere I can read it".
 fn init_tracing() {
     let filter = tracing_subscriber::EnvFilter::try_from_default_env()
-        .unwrap_or_else(|_| "info,bikecontrol_app_lib=debug".into());
+        // `bikecontrol_ble` belongs here as much as the shell does: it owns every
+        // BLE conversation, so leaving it at `info` silences exactly the frames
+        // NFR-8 says must be loggable — subscribe failures, bad button frames,
+        // the lot. That is survivable on desktop, where RUST_LOG can override
+        // it, and not on Android, where there is no environment to set.
+        .unwrap_or_else(|_| "info,bikecontrol_app_lib=debug,bikecontrol_ble=debug".into());
 
     // Android has no stdout: the default writer would drop every line. See
     // `android::Logcat`.