Manual: add 0-X, and document gate capture now that it is reachable 0-X is the eighth mode, so it joins the modes page with its states, its accuracy and its reset; the target speed joins the settings page and the Setup shortcut that opens it directly. Two things in the manual had also gone out of date rather than merely incomplete: Gate capture is reachable on the device now, and the Tracks page described promoting a circuit without saying how to do it. It now walks the eight points and says what capture refuses - moving, mid-session, or a partial set - because those refusals look like faults until you know they are deliberate. The Setup list named three entries and now has five, two of which are drawn but not connected. Saying so is better than leaving somebody to tap them and wonder. Troubleshooting gains the two 0-X states most likely to be read as faults: a red LOST FIX, which is a run that stopped being measured rather than a slow one, and NO SPEED, which is the receiver declining to measure rather than the fix failing.
Add a user manual, and correct the lap timing row The User Manual page was an empty placeholder. It is now a parent index with seven sub-pages covering every screen and every setting: getting started, navigation, the seven modes, the session screens, settings, tracks and diagnostics. Written for somebody holding the device rather than reading the source, so it leads with the two things that surprise people: only a press-and-hold opens the menu, and no circuit in the supplied pack will time a lap because every one of them is provisional. Both are deliberate, and the manual says why rather than just what. Also corrects a row that had gone stale. The timing engine is no longer waiting on a consumer - fixes reach the timing task and lap events drain back. What is still missing is a circuit whose geometry has been validated, which is a different blocker and now says so.
Created User Manual (markdown)
Receiver configuration persistence confirmed from the flash layer Read back with UBX-CFG-VALGET rather than inferred. Also records why power-cycling the board cannot test this: the firmware configures on every boot, and a power-on boot's log cannot be captured.
GNSS works: 20 Hz accepted fixes on hardware The receiver is configured at boot and delivering accepted fixes. The critical path has moved from hardware to software: nothing consumes the fix queue yet. Also records the two bugs bring-up found, including the UTC sub-second field that made measurement time run backwards and the test that asserted it.
The receiver is connected and talking: one configuration step from a fix The Qwiic cable arrived and the receiver is on the I2C socket. The device talks to it, the board was not damaged, and the receiver already holds a valid fix indoors. It emits NMEA where the firmware parses UBX, so nothing parses yet - that is #16, and it is now the only step between this device and a lap time. Also: the #9 socket hazard is retired but not answered, the boot log's stage lines are documented, and the UART0 open decision is replaced by the one that is actually open.
Write the Hardware page, and link it from Home Covers the parts and why those parts, the shared I2C bus and its deadline, the UART socket conflict between the console and the receiver, how to get diagnostics off the board, what is verified against what is assumed, and the order to bring the receiver up in.
Created Hardware (markdown)
Replace the placeholder Home with project orientation Covers where the project actually is, how to build and flash it, the traps that have each cost real time, why the track provenance gate exists, a document map, and what is blocked on what.
Initial Home page