Race Timing System: Race capture and lifecycle controls

Race capture and lifecycle controls

On Overview → Capture & checkpoints → RFID capture races, select the races allowed for each reader and press Apply capture races. New and upgraded sessions begin with RFID timing paused until configured; observations are still archived for enrollment diagnostics. Select multiple races only when that reader should time overlapping races. Display and result filters do not change capture. Reader scopes persist across application restarts.

Only tags already enrolled in an enabled race may contribute timing crossings. Other-race tags, unknown tags and observations captured while paused remain archived with an exclusion reason. Those excluded reads never become eligible when you change scope or enroll a runner later. Duplicate delivery cannot override the original decision. Existing results from previous versions are preserved during upgrade; review those historical results because race filtering applies to new captures. Camera observations still require manual approval into an enrolled runner's race.

Open Live display, select the race, and use these controls:

• Start selected race records the timing computer's current gun time.
• End selected race stops that race's clock at the recorded end time. Later RFID and approved camera crossing timestamps are excluded. Delayed uploads with timestamps before the end may still update provisional results when the race remains enabled on the reader. Pending racers are not automatically declared DNF; review them. Ending one race does not end others.
• Restart after false start records a new gun time immediately, clears the end state, and excludes all crossings before the new start, including the previous chip start. Racers need a new chip-start crossing. Press at the replacement gun, not while waiting for it. The old start and original observations remain auditable. Retries with the same request ID cannot restart twice; stale requests are rejected. False-start restart is unavailable once the race has finishers; use a reviewed new session for a rerun.

End and restart ask for confirmation naming the selected race. These controls and capture changes require authenticated operator access and CSRF protection. Reader clocks must remain synchronized. Configure capture before starting; starting or restarting a clock does not change which races a reader is allowed to time.

Replay requires explicit --race RACE_KEY; repeat it for overlapping races. Replay does not change the saved reader scope. HTTP reader URLs remain /reads/READER_ID. Race eligibility and exclusion reasons are saved with each archived observation.

Verification for 0.9.0: 34 Python tests passed, including race eligibility, excluded-read immutability, overlapping-reader scopes, prior-schema upgrade, end boundaries, delayed uploads, camera end boundaries, restart persistence/idempotency, and authenticated HTTP controls. All nine embedded JavaScript blocks parsed, and a runtime check confirmed ended race/racer clocks remain frozen. Real reader hardware and rendered browser layout were not available for verification.