Virtual gearing, trainer-speed blend, and cadence decode

Gears are expressed as an offset to the commanded gradient, leaving the
physics on the route's true gradient so shifting changes effort, not speed.
Neutral gear commands exactly the route gradient, so an un-shifted ride is
unchanged.

Cadence is not in FTMS on this trainer but is on its Zwift channel, decoded
against captured frames. The undeclared FTMS trailing bytes were ruled out:
wheel RPM restated at a fixed 73.8x speed.

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

crates/ble/src/lib.rs

@@ -12,6 +12,7 @@
 //! | [`indoor_bike_data`] | `0x2AD2` decoder | no |
 //! | [`control_point`] | `0x2AD9` encoders and response decoding | no |
 //! | [`capabilities`] | `0x2ACC`/`0x2AD5`/`0x2AD6`/`0x2AD8` decoding, and the safety gate | no |
+//! | [`zwift`] | Zwift's proprietary protocol (§2.3.1) | no |
 //! | [`scan`] | discovery | yes |
 //! | [`client`] | the connection actor | yes |
 //!
@@ -47,13 +48,16 @@
 //! (REQUIREMENTS.md §3.2). Per-module attribution notes mark where.
 
 pub mod capabilities;
+pub mod click;
 pub mod client;
 pub mod control_point;
 pub mod error;
 pub mod indoor_bike_data;
 pub mod scan;
 pub mod uuids;
+pub mod zwift;
 
+pub use click::{ClickClient, ClickConfig, ClickEvent};
 pub use capabilities::{
     FitnessMachineFeature, InclinationRange, PowerRange, ResistanceLevelRange, TrainerCapabilities,
     UnsupportedTarget,
@@ -68,3 +72,7 @@ pub use scan::{
     default_adapter, scan, scan_trainers, DiscoveredDevice, ScanKind, TrainerSelector,
 };
 pub use uuids::FITNESS_MACHINE_SERVICE;
+pub use zwift::{
+    Button, ButtonBitmask, ClickButtons, DeviceKind as ZwiftDeviceKind,
+    MessageType as ZwiftMessageType,
+};