Race Timing System: Separate race controls and team results

Separate race controls and team results

Use Race controls (/controls) for Start, End and Stop & Reset. Live results (/display) contains only viewing options, race clock, individual/team results, pagination and fullscreen. The earlier Restart button is removed. Stop & Reset records a stopped false-start attempt, returns the clock to zero and leaves the race Ready until you press Start at the next gun. The original observations/start remain in audit history; they cannot count in the new attempt. Reset retries are idempotent and state survives application restart. Recorded finishers prevent destructive reset; use a reviewed new timing session for a rerun.

Sports Hub team results: connect your Hub API account and import the race from Racers & bibs, then select the race on Race Controls and press Refresh Hub team results. This reads /api/commercial/v1/cross_country_entries?cross_country_race_id=ID plus /api/commercial/v1/teams; the key needs cross_country_entries:read, teams:read and access to the linked race. Results are grouped by Hub team ID, named from the Hub catalog, and totaled from the first five finished entries' recorded points (or recorded overall place where points are absent). Equal totals share rank because this read API does not expose an official aggregate/tie resolution. This is a provisional aggregation of Hub records, not an official aggregate standings endpoint.

On Live Results choose Results → Teams. A pulled Hub snapshot takes priority over locally derived team results. The page shows its update date/time and marks snapshots older than one minute as needing refresh. Refresh from Race Controls when Hub results change; no background service or automatic billed API polling is added. Failed or wrong-race refreshes preserve the last successful snapshot. Empty Hub results show an empty view. Reconnect your API key after restarting the receiver; saved snapshots remain available without the key. Local RFID capture does not automatically upload finishes to Hub; continue using the existing results export/upload workflow.

For local teams, Racers & bibs has an optional Team field and tag CSVs accept optional team_name. Team membership is separate from tags, so multiple tags never duplicate racers in team scoring. When no Hub snapshot exists, the Teams view shows local team finisher counts; optionally enable cross-country team scoring on Race Controls. Local scoring uses gun-time order, first five scorers, up to seven displacing runners, and excludes incomplete teams and unattached runners from team-scoring places. Equal scores compare sixth-place runners, then first-four totals when neither has a sixth. Identical scoring-field finish times withhold team scores for finish-order review instead of awarding places by bib. Individual places remain separate. All displays remain provisional.

Local scoring reference: https://www.uiltexas.org/cross-country/manual/cross-country-regular-season . Confirm the meet's applicable rules before enabling this scoring mode for other race formats.

Verification: 37 Python tests passed, including Stop & Reset/Start persistence, authentication/CSRF, read-only live page, team scoring and race-specific Hub snapshot caching/error recovery. Eleven embedded scripts parsed; simulated UI checks exercised team pagination with no local entries, ended clocks and Stop & Reset returning controls to Ready. Live authenticated Hub access, hardware and rendered browser layout were not available for verification.