SlotForge Paddock v1.0.1 - Telemetry lap-history integration

SlotForge Paddock v1.0.1

SlotForge Telemetry can now read the race sessions delivered to Paddock by Timing, including individual laps and the configuration each car raced with.

What's new

• One familiar connection: use the existing Dealership address and remembered password. No extra permission toggle or password.
• Complete race evidence: original laps, drivers, lanes, heats, endurance stints, validity/pit flags, standings and adjustments remain linked to the captured configuration.
• Session browsing: filter by car, track, Timing source and date, with bounded pagination.
• Quiet updates: small change notifications through long-polling or optional SSE; clients can download only changed sessions. Private edits do not trigger result notifications.
• Reliable offline refresh: consistent snapshots, corrections, withdrawals and restored databases can be reconciled without duplicating performance records.
• Integration handoff: exact API contract, JSON Schema and artificial fixtures are included for Telemetry developers.

The review aligned the API with Telemetry's completed contract, corrected date-range boundaries and strengthened cleanup when connections close or passwords change. Existing Timing uploads, Dealership sharing, reviewed car submissions and manual performance records remain independent.

Updating

Close the running app before opening the updated version. Your collection and remembered Dealership password remain in place. Database schema 11 and Timing integration v1 are unchanged; no migration is required.

Start Dealership Mode and give Telemetry the displayed address, actual port and existing password. Telemetry provides the analysis UI and offline cache; its client must support this connection. This API exposes delivered Timing sessions, not every historic Timing session or manual Paddock performance entry.

Downloads

• Windows: SlotForge.Paddock.1.0.1.exe — portable app; Node.js is not required.
• Linux: x64 and ARM64 AppImage/deb packages.
• macOS: universal DMG/ZIP for Intel and Apple Silicon.
• Telemetry handoff: SlotForge-Paddock-Telemetry-v1.zip.
• Timing handoff: SlotForge-Paddock-Timing-v1.zip.

Native Linux and macOS jobs attach their downloads after publication. SHA-256 manifests accompany the downloads. Windows is unsigned; macOS is ad-hoc signed and not Apple-notarised. AppImages need executable permission.

Validation

360 automated tests passed, including 18 Telemetry API tests, plus syntax checks. The existing Telemetry client also passed local connection, import, unchanged-refresh, correction, withdrawal and removal-reconciliation checks using a disposable host and cache.

Tests cover authentication, database identity, private-field exclusion, pagination, restored snapshots, notification cancellation and revocation, failed persistence, and compatibility with existing Timing and Dealership functionality. These are automated local tests, not a physical two-computer Wi-Fi acceptance test.

See the review and Telemetry integration handoff.