From 2544688fde706a755536ef1a85ebe55f329a120e Mon Sep 17 00:00:00 2001 From: Joseph Spiker Date: Tue, 6 Oct 2026 03:35:18 -0400 Subject: [PATCH] docs: correct Activity Tracker, Routes & Paths in the beta README Evidence: spikersoft-ios@main RouteSyncService.swift:4 pulls missing routes; spikersoft-android@main RouteSyncWorker.kt:35 does not. Co-authored-by: Cursor --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 97b78c6..aee8ba2 100644 --- a/README.md +++ b/README.md @@ -884,7 +884,7 @@ All three clients share the same map stack: **six raster base maps** (`osm-stand - **Ghost racing**: race a prior attempt with live gap computation and spoken auto-announcements (off / every minute / every km), optionally triggered by the volume buttons. - **Return-to-start**: detects a dwell back at the start point and fires a chime + spoken prompt + actionable notification — deliberately **never auto-stops** (it feeds on raw fixes, because the sampling gate starves while stationary). - **Listen-while-recording**: a companion sheet offers resume-a-book / pick-a-book / device music; audio cues duck the narration. -- **Two-way sync**: uploads pending recordings, flushes delete tombstones, then *pulls down* routes the device lacks — so a reinstall doesn't show an empty history. +- **Two-way sync**: iOS (`RouteSyncService`) uploads pending recordings, flushes delete tombstones, then pulls down routes the device lacks, so a reinstall does not show an empty history. Android uploads and flushes tombstones, then refreshes trail-share status only for routes already on the device. ### Routes, analysis, trimming