# Lappy v0.0.10

Track timing is now functional behind the existing v0.0.9 UI. It supports circuits and point-to-point, interpolated start/finish crossings, consecutive circuit laps, 0–2 splits, sector times/bests, session bests, per-revision PBs and live delta against an actual valid reference trace. The first valid attempt creates the reference; a P2P finish holds until REARM.

GPS faults, gaps, reverse travel, ambiguous/off-course progress and missed gates invalidate attempts. Page and mode changes do not stop timing. Manual date/time never changes elapsed results. Custom route recording, naming, gate review and split placement use real incoming positions. Course/PB/history/reference files have checksums, recoverable backups and separate reference-free summaries. Manual PWR shutdown interrupts the current attempt and flushes Track data before capture close and power release; a failed save holds power for retry.

The UI keeps its layouts, positions, fonts, colors and header factory. Track labels, maps and rows now describe actual data; hardware uses LAPPY where the old unimplemented state used CONCEPT. Synthetic simulator input still uses DEMO. English-only Street, Drag and Settings behavior is preserved; Settings displays the new version.

Validation includes 18 fragmented UBX replays across both types, three split configurations and 5/10/25 Hz, fault/recovery/40-lap tests, native interaction/persistence/shutdown tests, and 92 render states. Both V1 and V2 firmware profiles are built. See VALIDATION.md for final evidence and TRACK_ENGINE.md for policy/limits.

No hardware has arrived or been flashed. No real track pack is bundled. Track limits are eight course revisions, 20 km/2,048 route points, 8,192 reference samples and 32 stored attempts per revision. Incomplete/invalid recon recordings are not resumable saved courses. Independent timing accuracy, task/heap margins, SD fault recovery and actual Dragy compatibility remain hardware acceptance work.