a9f8ee61f0
Two import entry points: - Home page: "Import GPX" button next to "Start Planning" - In-session: drag-and-drop GPX onto the map (with confirmation) Parses GPX client-side, extracts waypoints (Douglas-Peucker) and no-go areas from extensions. Non-GPX files show error toast. Also: - Fix spec drift: non-GPX drop now shows error toast (was silent) - Add E2E tests for import button, invalid GPX, and session creation - Archive gpx-import-planner change, sync specs Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
9 lines
478 B
Markdown
9 lines
478 B
Markdown
## MODIFIED Requirements
|
|
|
|
### Requirement: Session initialization
|
|
Sessions can now be initialized from a GPX file upload in addition to URL parameters and the journal handoff.
|
|
|
|
#### Scenario: Session created from GPX upload
|
|
- **WHEN** a session is created via GPX file upload on the home page
|
|
- **THEN** waypoints and no-go areas from the GPX are passed via URL parameters to the session page
|
|
- **AND** the Yjs document is initialized with the extracted data on the client side
|