Add 8 proposed changes and old trails analysis

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>

openspec/changes/route-features/specs/activity-feed/spec.md

@@ -0,0 +1,12 @@
+## MODIFIED Requirements
+
+### Requirement: Activity visibility
+Activities SHALL have visibility levels controlling who can see them.
+
+#### Scenario: Private activity
+- **WHEN** an activity's visibility is "private"
+- **THEN** only the owner can view it
+
+#### Scenario: Public activity
+- **WHEN** an activity's visibility is "public"
+- **THEN** anyone can view it on the owner's profile

openspec/changes/route-features/specs/activity-photos/spec.md

@@ -0,0 +1,16 @@
+## ADDED Requirements
+
+### Requirement: Photo attachments on activities
+Users SHALL be able to upload photos to their activities.
+
+#### Scenario: Upload photo
+- **WHEN** a user adds a photo to an activity
+- **THEN** the photo is uploaded to S3 storage and linked to the activity
+
+#### Scenario: View photos
+- **WHEN** a user views an activity with photos
+- **THEN** the photos are displayed in a gallery on the activity page
+
+#### Scenario: Delete photo
+- **WHEN** a user deletes a photo from their activity
+- **THEN** the photo is removed from storage and unlinked

openspec/changes/route-features/specs/multi-day-routes/spec.md

@@ -0,0 +1,16 @@
+## ADDED Requirements
+
+### Requirement: Day-break waypoints
+Waypoints in the Planner SHALL support a day-break marker that splits the route into stages.
+
+#### Scenario: Mark day break
+- **WHEN** a user marks a waypoint as a day break in the Planner
+- **THEN** the route is visually split into days at that point
+
+#### Scenario: Per-day statistics
+- **WHEN** a route has day-break markers
+- **THEN** the sidebar shows distance and elevation per day/stage
+
+#### Scenario: GPX export with day segments
+- **WHEN** a multi-day route is exported as GPX
+- **THEN** each day is a separate track segment in the GPX file

openspec/changes/route-features/specs/route-management/spec.md

@@ -0,0 +1,12 @@
+## MODIFIED Requirements
+
+### Requirement: Route metadata
+Routes SHALL track visibility, contributors, and support forking.
+
+#### Scenario: Visibility on route creation
+- **WHEN** a user creates a route
+- **THEN** the route defaults to "private" visibility
+
+#### Scenario: Contributor recorded on version
+- **WHEN** a Planner session saves a new route version via callback
+- **THEN** the version records the contributor who made the edit

openspec/changes/route-features/specs/route-sharing/spec.md

@@ -0,0 +1,30 @@
+## ADDED Requirements
+
+### Requirement: Route visibility levels
+Routes SHALL have a visibility setting controlling who can see them.
+
+#### Scenario: Private route
+- **WHEN** a route's visibility is "private"
+- **THEN** only the owner can view it
+
+#### Scenario: Public route
+- **WHEN** a route's visibility is "public"
+- **THEN** anyone can view it and export its GPX
+
+### Requirement: Share routes with specific users
+Route owners SHALL be able to share routes with specific users at view or edit permission levels.
+
+#### Scenario: Share with view access
+- **WHEN** owner shares a route with another user as "view"
+- **THEN** that user can see the route and export GPX but cannot edit
+
+#### Scenario: Share with edit access
+- **WHEN** owner shares a route with another user as "edit"
+- **THEN** that user can start Planner sessions and create new versions
+
+### Requirement: Fork routes
+Users SHALL be able to fork (copy) public routes to their own collection.
+
+#### Scenario: Fork a public route
+- **WHEN** a user clicks "Fork" on a public route
+- **THEN** a copy is created in their collection with the original credited

openspec/changes/route-features/specs/spatial-search/spec.md

@@ -0,0 +1,12 @@
+## ADDED Requirements
+
+### Requirement: Map-based route discovery
+Users SHALL be able to discover public routes by browsing a map.
+
+#### Scenario: Browse routes on map
+- **WHEN** a user visits the route explore page and pans/zooms the map
+- **THEN** public routes within the visible area are shown as polylines on the map
+
+#### Scenario: Route preview
+- **WHEN** a user clicks a route on the explore map
+- **THEN** a popup or sidebar shows the route name, distance, elevation, and a link to the detail page