Ride the drivetrain, command the load in watts

Speed now comes from the drivetrain and the load from the road, which is
the way round a bike actually works.

Speed is cadence x development, filtered lightly. Power, not cadence,
decides whether the rider is driving it: on a direct-drive trainer the
flywheel keeps the cranks turning after they stop, so cadence alone reads
a healthy 80 rpm for someone doing nothing. Below 15 W the speed runs
down to whatever the gradient sustains on no power - zero uphill, a real
freewheeling speed on a descent. Stopping on a 3.5% climb used to settle
at 22 km/h and stay there, because the model wanted to decelerate and a
blend toward the flywheel speed outvoted it; that blend is gone.

The D100 sends no cadence over FTMS - it is a rebadged Magene T110 with
cadence disabled in firmware (qdomyos-zwift#3282) - so it is inferred
from wheel speed, which one sprocket and no freewheel make exact. Its
Zwift channel does carry cadence, and is now greeted with RideOn and
subscribed on every notifying characteristic, so a measured value is used
where one arrives.

The load is commanded as power, not gradient. The trainer declares
50-600 W in 1 W steps against 0-6% inclination in 0.1% steps refusing
negatives, and whether it acts on 0x11 at all is still unconfirmed. Its
power target is a ceiling rather than a setpoint, which is very nearly
what a road is: exceed it and the surplus becomes speed. Gravity travels
on the same channel as watts, so nothing is lost by leaving 0x11 alone.
LoadChannel keeps the gradient path selectable and tested.

Virtual shifting reaches the trainer for the first time. The physics
load model was written but never called, and a paddle press both shifted
a gear in Rust and nudged the gradient in the webview - the shift
silently, the tilt visibly, so the paddles looked like a gradient trim.

Also: a fixed 12 W drivetrain loss, held as a power because that is how
it presents; crank length, so a gear can be reported as the force it puts
under the foot; gear and pedal force on the ride screen; a drag-race
profile for testing gearing on the flat.

Two readout bugs fixed on the way. The rolling windows were trimmed by
timestamp but fed on a fixed timer, so every second spent on the ride
screen before starting pushed samples at t=0 that could never expire -
speed read a fraction of the truth for the first 45 s. And the headline
speed was a 45 s mean, which took most of a minute to show a gear change.

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

README.md

@@ -22,10 +22,10 @@ The app drives the hardware end to end: it scans over BlueZ, connects, acquires
 control, feeds Indoor Bike Data into the ride engine, and writes control targets back at
 4 Hz. Recording to FIT is the remaining gap.
 
-The synthetic rider is still available for GUI work with no hardware on the desk —
-`BIKECONTROL_MOCK=1`, or `BIKECONTROL_DEMO=1` which also loads the sample route and starts
-riding. Both need the `mock-ride` feature, which is on by default;
-`--no-default-features` produces a binary that can only ever show real trainer data.
+There is no synthetic rider and no ride-without-a-trainer mode. The ride screen is gated on
+an FTMS trainer that has accepted the control point, and with no trainer attached the ride
+reads zero — a session that could be finished without any of it having happened is worse
+than no session at all.
 
 ---
 
@@ -50,12 +50,6 @@ cd ..
 ./target/debug/bikecontrol-app
 ```
 
-Open straight onto a running ride with the sample GPX loaded:
-
-```bash
-BIKECONTROL_DEMO=1 ./target/debug/bikecontrol-app
-```
-
 ### Development mode (hot reload)
 
 ```bash
@@ -249,5 +243,5 @@ ui              Svelte 5 + uPlot — renders snapshots, issues intents
 `crates/core/src/types.rs` is the shared contract between all of them. Change it
 deliberately.
 
-The app selects its data source by Cargo feature: `mock-ride` (default) drives a synthetic
-rider; `real-session` wraps the real ride engine and needs a live telemetry source.
+The app has one data source: `src-tauri/src/session_backend.rs`, which wraps the real ride
+engine and is fed by live FTMS telemetry. Nothing fabricates rider data.