c7c1c275df
Proposed changes (all with proposal, design, specs, tasks): - app-navigation (9 tasks) — nav bars for both apps - planner-landing-page (7 tasks) — standalone landing page - planner-multiplayer-awareness (13 tasks) — participants, cursors, names - changelog (13 tasks) — public changelog with "what's new" - transactional-emails (15 tasks) — magic link + welcome emails - planner-features (18 tasks) — no-go areas, notes, recovery, rate limits - komoot-import (23 tasks) — Komoot tour import - route-features (37 tasks) — sharing, multi-day, spatial, photos Also adds docs/old-trails-analysis.md with feature analysis from the older trails project. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
16 lines
649 B
Markdown
16 lines
649 B
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Draw no-go areas
|
|
Users SHALL be able to draw polygons on the map that BRouter avoids when computing routes.
|
|
|
|
#### Scenario: Draw polygon
|
|
- **WHEN** a user activates the no-go area tool and draws a polygon on the map
|
|
- **THEN** the polygon is added to the Yjs doc and visible to all participants
|
|
|
|
#### Scenario: Route avoids no-go area
|
|
- **WHEN** a route is computed and a no-go area intersects the direct path
|
|
- **THEN** BRouter routes around the no-go area
|
|
|
|
#### Scenario: Delete no-go area
|
|
- **WHEN** a user deletes a no-go area polygon
|
|
- **THEN** it is removed from the Yjs doc and the route is recomputed
|