Chain lube tracking and wear modelling now follow a ride when it is moved or updated after import
Fixes
Chain lube distance after moving a ride. When a ride was moved to a different bike, the distance and riding conditions used for the chain's "since last lubed" estimate stayed with the original bike. A chain could show "0 km since last lubed" on a bike that had been ridden every week. Moved rides now count towards the bike they belong to, and existing rides have been corrected.
Ride updates now reach the wear model. Weather that arrived after a ride was imported, and distance or sensor data added when a Strava ride was matched to its device file, were not reflected in the modelling inputs for that ride. Those rides are now refreshed automatically the next time your predictions update.