Release date: 2026-11-21. The current handbook documents 86 flows across eight chapters. v1.3 notes remain the record of the previous release.
The fictional sandbox runs 1–50 lap sessions with exact simulated finish times, final order and a frozen finishing clock. Select a driver, call a stop before the next eligible entry, cancel before entry, and schedule repeat visits. Setup changes restart the local race; live calls preserve it. A pit lane spanning start/finish uses a mapped crossing, rather than a surveyed timing line.
ASP.NET Core owns the shared simulation clock and validates decisions; SignalR sends snapshots to guests. Rooms support up to six driver seats and twelve guests including spectators, exclusive claims, lobby readiness, host controls, reconnect, driver/host handover and guest removal. Invitation URLs contain the room code; private guest credentials stay in tab session storage. Multiplayer guide.
A browser-local team starts with 12,000 fictional credits. Scout generated prospects, sign/release up to six roster drivers, create 210-point custom builds, and select or swap two race seats. Pace/consistency produce a steady synthetic pace offset; pit discipline changes service time. Fees, partial refunds, stat caps, storage failures and stale-tab writes are explicit. Recruiting guide.
Signings fill empty selected team seats and appear in an open sandbox. New unsaved grids use selected signed builds; stored grids and running races wait for explicit sync/selection. Per-slot selection can swap builds while keeping each slot's scheduled pit lap.
Race this circuit fits/simplifies the current replay's approximate outline into an independent fictional venue. New pit lanes try validated connected routes; Monza and Interlagos are covered by geometry and browser checks. The historical replay retains its original clock/data. These are approximate venues with fictional sectors, pit geometry, base pace and distance.
The feature batch passed 78 Vitest checks and 57 Playwright scenarios, plus the authoritative C# room/permission checks and shared browser/server model fixture during room development. The maintained guide has structural/link/version checks in CI. See TESTING for actual coverage and commands.
The header derives its semantic version from the frontend package; /api/status derives it from the API assembly. CI's guide checker compares package, lockfile, API project and handbook metadata. The release uses an annotated v1.4.0 Git tag; publishing a tag is separate from creating a hosted GitHub Release.
Historical caches/bookmarks use PostgreSQL when configured. Recruiting, custom definitions and local preferences remain browser-origin data. Multiplayer rooms remain in one API process's memory even with PostgreSQL: an API restart/redeployment ends rooms. Guest credentials do not provide account recovery. Public hosting, multi-instance room coordination, durable room resume, protected online economies, tyre physics, wages, seasons and vehicle-part upgrades remain future work.