biking_home - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age
*	Expose ride data as components and make algorithms consume only the slices ↵	Martin Kagamino Lehoux	2026-08-25
\| \| \| \| \| \| \| \| \| \| \|	they read Ride now exposes its columns as component getters (Distances, Elevations, Coords, Timestamps, and the optional Powers, Cadences, HeartRates) with the coords field unexported. difficultyScore, movingTime, Slope and the climb detection internals are pure functions over the specific slices they use, and Climb carries only the component slices it needs instead of a whole Ride.
*	chore(bench): exclude rides with low moving time ratio	Martin Kagamino Lehoux	2026-08-20
\|
*	chore(bench): exclude rides under 10 km	Martin Kagamino Lehoux	2026-08-20
\|
*	chore(bench): exclude short rides	Martin Kagamino Lehoux	2026-08-20
\|
*	fix(ride): use effort metrics for moving time	Martin Kagamino Lehoux	2026-08-20
\|
*	fix(ride): improve moving time against Strava	Martin Kagamino Lehoux	2026-08-20
\|
*	feat(ride): compute moving time from GPX with backtest	Martin Kagamino Lehoux	2026-08-20
	Add ride.MovingTime, a speed-threshold algorithm over track timestamps. Add a -backtest CLI command comparing computed values against Strava's reference across all stored rides, with a percentile distribution summary. Baseline: mean err 3.9%, p50 1.6, p75 4.6, p90 8.4, p95 12.1, p99 44.9.