fix: resolve travel anchor ID collision for repeat city pairs

Include segment index in travel anchor IDs ("travel:INDEX:from->to")
so Follow Team trips visiting the same city pair multiple times get
unique, independently addressable travel segments. Prevents override
dictionary collisions and incorrect validDayRange lookups.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Trey t
2026-02-11 10:57:53 -06:00
parent 633f7d883f
commit ff6f4b6c2c
12 changed files with 291 additions and 79 deletions

View File

@@ -38,6 +38,7 @@ enum ItemKind: Codable, Hashable {
struct TravelInfo: Codable, Hashable {
let fromCity: String
let toCity: String
var segmentIndex: Int? = nil // Position in trip.travelSegments (nil for legacy records)
var distanceMeters: Double?
var durationSeconds: Double?