# Lappy v0.3.6

Custom Track editing and GPS readiness fixes following the October 27 recordings.

- Track accepts at least five satellites with a valid 3D fix, horizontal accuracy within 5 m and speed accuracy greater than zero and within 1 m/s. Speed bounds, GPS cadence, arrival latency, finite directional crossings and running-attempt continuity remain enforced. Drag is unchanged.
- Poor GPS before Start keeps the course armed and waits for usable updates. Recovery resets crossing continuity, so a crossing hidden inside a bad-data interval cannot start a timer. Poor data after timing begins still invalidates the attempt.
- The armed screen shows the specific GPS blocker, distance before/beyond Start, sideways offset and the finite gate half-width. Invalid attempts offer explicit REARM/DISARM. Gate geometry is never automatically widened or relocated.
- A finished recording opens split selection with zero splits and the recorded direction accepted. Split counts initialise usable positions. Split movement is 50 m per tap with immediate placement; there is no fine-tuning mode.
- Validation distinguishes unset splits, Start/Finish proximity, split ordering and actual gate overlap. Reversal recalculates the final projection, gate distances and split locations; exact unedited endpoints are retained.
- EDIT opens an overview with gate, split, reverse, save and cancel actions. Existing custom courses update their original slot. Unchanged layouts retain revision, PB and reference. Timing-layout changes show a warning before saving a new revision with empty timing records; the previous file generation remains in the normal storage backup. Factory edits create a custom copy.
- ARM, GPS/timing state transitions, validation errors and save requests are recorded for future diagnosis.
- Unconditional recording STOP/CANCEL and partial recovery from v0.3.5 remain available.

Validation includes the original morning failed-recording capture, the later successful 3.224 km recording, the afternoon approach, native LVGL interactions using the private recorded geometry, the full host sanitizer suite and the V2 target build. See the matching hardware report for installation and bench scope. Replays and isolated benches are not a physical road or touch acceptance test.