Heats and finals started together show ▲/▼ against the start order
(new OBS option, on by default). In practice the best lap is no longer
printed twice as both result and best.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Explains creating a series, running each round from the series page,
points and standings, and a worked winter-series example.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Race Day gets a 1-3 minute warm-up per heat with a green check per
driver when their transponder is seen, countdown announcements
(sv/en), quick transponder fix from the panel, and a start warning
that still allows starting when someone is missing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Announcements can use Piper, a free local neural TTS, instead of the browser's system
voice. No account, no paid service, and it keeps working with no internet at the track.
- npm run tts:install (or Settings -> Audio -> Install) downloads the standalone Piper
release for Linux/Windows/macOS plus Swedish and English voices into piper/ once
- server/tts.js generates each line once, one at a time, and caches it as WAV under
data/tts/; a new line takes ~0.3 s with the standalone build
- src/piper_speech.js plays it and falls back to the browser voice if Piper is missing,
errors, or takes over 2.5 s, so no announcement is lost and timing is never held up
- "Pre-generate phrases and driver names" renders every fixed phrase and name in both
languages before race day
Browser voice stays the default. Generation routes fall under the admin PIN.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Off by default. Once a PIN is set in Settings -> System & backup, every non-GET /api/*
request (plus GET /api/ammc/config) needs a signed 30-day HttpOnly cookie, which also
closes the unauthenticated /api/update/run restart trigger. A 401 opens a PIN dialog
and the pending save is retried after login. Reads stay open because the public overlay
hydrates through GET /api/state. Optional RC_ADMIN_ALLOWED_CIDRS restricts the same
routes by client address.
The PIN hash and signing secret live in data/, outside the app_state blob, so they
never leak through GET /api/state, exports or backups.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The page had grown to ~20 stacked panels on one very long scroll - the same problem
already fixed twice this session for Settings and Event Manager. Grouped into 5 tabs
(Getting started, Create a race, Run a race, Training & results, Video guides) using
the same activeGuideTab-as-module-state approach so the selection survives an in-place
re-render (e.g. a language switch). The always-visible overview cards at the top are
unchanged.
Also investigated a "feels slow" concern raised alongside this: measured the page's
actual render cost in a real browser (median 0.6ms, on par with or faster than Settings/
Timing) and confirmed the periodic tickClock/updateSyncStatus intervals never re-render
an idle Guide page. No performance issue found - the perceived slowness was the page's
length, which this change addresses directly.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Commit all 7 recorded clips to docs/videos/ (alongside the existing docs/screenshots/)
instead of leaving them in the gitignored video-guides/ folder from the earlier
feasibility spike - they're meant to be shipped, discoverable assets now, not scratch
output. scripts/record-video-guides.mjs writes there by default going forward.
Added a "Video Guides" section to README.md/README.sv.md (Getting started + Interface
tour groups) and a matching in-app "Video guides" panel on the Guide page, right after
the overview cards - the most discoverable spot for a brand-new user. Links point at
/docs/videos/<name>.mkv, served by the server's existing /docs static route.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Documents the new race-day Schedule feature (new section + overview
card), staggered-start car call-outs and the per-driver "Done" flag,
the new Settings and Event Manager tab layouts, and the driver
transponder-conflict warning. Also corrects a bullet that had gone
stale: it claimed Open/Free Practice was the only thing that skipped
the start ceremony, which stopped being true once scheduled "Practice"
sessions started getting the full sequence too.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Clubs that reconfigure their track (e.g. running indoors in the same
building) can now add named track layouts under Settings, each with
just a start date/time - layouts are contiguous, so a layout's end is
implicitly the next one's start, with no separate field to keep in
sync. Every session freezes which layout was active when it started,
so the "track record" audio cue and the Results Archive (which now
shows each session's layout) only compare laps run on the same
physical track. With no layouts configured, everything behaves
exactly as before - the feature is fully inert until a club uses it.
Design settled through conversation with the user: global scope (not
per class), start-date-only (no redundant stop date), and no changes
needed to driver/transponder mapping, since that's already fully
independent of track geometry in this app.
Deliberately out of scope for this pass: the mobile/driver training
profile's own cross-session personal-best trend stats still compare
across a driver's whole lap ledger regardless of layout - logged in
ROADMAP.md as a real remaining gap for a later pass.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Two new Training walkthrough steps covering the previous commit's
feature: completed-session history (verified server-side, never
just claimed by the mobile page) and the sessions-metric goal option.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The in-app Guide page hadn't been updated for the guided practice
exercises, their mobile self-service controls, the end-of-practice
summary, or the new Resultatarkiv view - none of it was documented
anywhere a user would find it. Added three new Training walkthrough
steps and a new Resultatarkiv section (overview card + 5-step guide).
While correcting guide text that claimed raw SQLite passing rows are
always retained, found the same gap the results-archive work already
fixed for deleting a single event/session also applies to "Rensa data"
(Settings -> Clear data): the drivers/cars/races/all-competition-data
scopes all reset resultsBySession for every current session, not just
ones tied to the cleared scope, so every session's raw rows became
orphaned at once. clearDataScope now purges those sessions' rows too,
through the same /api/passings/purge endpoint.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
