fff77a2ed2
mobile-app: Unified React Native + Expo app combining Planner and Journal. OAuth2 PKCE auth, MapLibre maps, versioned REST API with Zod schemas, configurable server URL, offline SQLite, Web Push relay notifications. TanStack Query + Zustand state management. Jest + Maestro testing. 76 tasks across 5 phases. map-core-package: Extract renderer-agnostic map definitions (tiles, color palettes, POI categories, z-index) into @trails-cool/map-core. Pure refactor preparing for MapLibre on mobile. 27 tasks. mobile-activity-recording: GPS recording, live stats, HealthKit/Health Connect export. Separated from mobile-app for independent scheduling. mobile-nearby-sync: BLE route sync between nearby devices for offline group riding. QR waypoint sharing as simpler v1. TXQR noted as future. journal-rest-api spec: Full API contract — endpoints, auth, pagination, errors, discovery, versioning, BRouter proxy. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
16 lines
885 B
Markdown
16 lines
885 B
Markdown
## MODIFIED Requirements
|
|
|
|
### Requirement: Deep link from mobile to Planner
|
|
The system SHALL allow the mobile app to open the Planner web app for full collaborative editing of a route.
|
|
|
|
#### Scenario: Open in Planner from mobile
|
|
- **WHEN** the user taps "Edit in Planner" on a route in the mobile app
|
|
- **THEN** the device browser opens the Planner with the route loaded and a JWT callback URL for saving back to the Journal
|
|
|
|
#### Scenario: Return to mobile after Planner save
|
|
- **WHEN** the user saves a route in the Planner web session that was opened from the mobile app
|
|
- **THEN** the Planner triggers a deep link back to the mobile app, which refreshes the route to show the updated version
|
|
|
|
#### Scenario: Planner session without save
|
|
- **WHEN** the user returns to the mobile app without saving in the Planner
|
|
- **THEN** the mobile app shows the route unchanged (no stale data)
|