ApexTrace 0.1.2 — Release notes

What's Changed

• The local session archive has been migrated from a single JSON file to SQLite. The session list now loads without loading the full telemetry data, and lap data is loaded on demand when a session is opened.

• Each lap's telemetry is stored separately in compressed form. Writes are performed transactionally using the WAL journal mode, reducing the impact of archive growth on startup and saving new sessions.

• On first launch, the existing `player_runs.json` is automatically migrated to `player_runs.sqlite3`. After a successful migration, the original file is preserved alongside it as `player_runs.json.migrated.bak`.

• Fixed session and lap exports in the Windows application. ZIP, CSV, and JSON files are now saved through the system file picker dialog.

• Fixed the fallback download mechanism in browser mode: the download link is added to the document, and the temporary Blob URL is revoked after the download begins.

Compatibility and Data

• ZIP/JSON import and export formats remain unchanged.

• The update does not delete the existing archive. Before installing, it is recommended to finish your current session and close ApexTrace.

• To create a full backup after updating, copy `player_runs.sqlite3` only while the application is closed. The `.migrated.bak` migration backup can be stored separately.

• Automatic rollback to version 0.1.1 is not supported: the older version cannot read the new SQLite archive.