m038andClaude Opus 5
47ec72fa1d
intelligent_gpx mode required BOTH endpoints of a leg to be near the SAME GPX file before treating it as covered. This trip's routes are one contiguous chain recorded a day per file (…-to-X.gpx, X-to-….gpx), so any leg spanning a file boundary — an unblogged intermediate stop — read as uncovered and got a straight connector drawn over an already-GPX-covered path. Each endpoint now only has to be near some file. The trade is that a real gap (flight, train transfer) whose endpoints each sit on their own track also reads as covered and gets no connector; that case is not detectable from proximity alone, and `force_connect: true` on the entry after the gap already handles it. js/map.js is the rebuilt bundle (make build-assets), not a hand-edit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>