trails/openspec/specs/journal-route-detail/spec.md at 2b48e2a8e17250cef95bd6db59c4d9fddb881c8e

Ullrich Schäfer 0cf87b72ab

Fix medium-severity spec drift across 17 specs

- authentication-methods: document completeAuth mode param ("redirect"|"json");
  clarify add-passkey nudge (no dismiss mechanism, disappears on passkey add)
- journal-auth: session maxAge is 30 days; terms allow-list uses /legal/ prefix
  matching (broader than fixed list of paths)
- session-notes: mark awareness isolation and UndoManager isolation as not yet
  implemented (shared instances in current code)
- activity-feed: add fan-out scenario for visibility change to public
- explore: note that ?perPage is not yet implemented (hardcoded page size)
- multi-day-routes: add per-day GPX track split scenario (splitByDays option);
  document overnight vs isDayBreak naming gap
- osm-poi-overlays: debounce is 800ms + 2000ms min interval (not 500ms);
  retry is not automatic (fires on next viewport change)
- brouter-integration: rate limit corrected to 300/hour; add segment-cache
  requirement (client caches per-pair segments)
- wahoo-route-push: OAuth state shape uses camelCase (returnTo, pushAfter
  object) not snake_case with push_after boolean
- komoot-import: document noop adapter / ConnectedServiceManager bypass;
  note four Komoot-specific routes that bypass the generic OAuth framework
- background-jobs: exponential backoff not wired (retryLimit only); add SIGINT
- connected-services: add revoked status; name ConnectionNotActiveError
- infrastructure: add INTEGRATION_SECRET and SENTRY_DSN to env var lists;
  split secret decryption scenario by workflow (cd-apps vs cd-infra)
- secret-management: correct CD decryption — cd-apps only decrypts app.env;
  cd-infra decrypts both
- transactional-emails: welcome email is async (pg-boss job); magic-link email
  includes 6-digit numeric code
- journal-route-detail: websites are https: links (not mailto:); opening_hours
  is also displayed
- local-dev-environment: add mobile app (Expo) dev commands

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-24 11:11:31 +02:00

1.3 KiB

Raw Blame History

Purpose

The Journal route detail page displays a saved route with its metadata, map, elevation, day breakdown, and waypoint POI details.

Requirements

Requirement: POI metadata on route detail waypoints

The Journal route detail page SHALL display POI metadata (phone, address, website, opening hours) for waypoints that have associated OpenStreetMap POI data.

Scenario: POI metadata displayed on waypoints

WHEN a route detail page is loaded and a waypoint has POI metadata from the Planner
THEN the waypoint displays the POI name, icon, and category alongside its coordinates

Scenario: Phone, address, website, and opening hours shown

WHEN a waypoint has POI metadata including phone, address, website, or opening hours
THEN those details are shown in the waypoint detail section with appropriate links (tel: for phone, https: for website; opening hours displayed as text)

Note: mailto: links for websites are not rendered — all website values are treated as https: links. The opening_hours OSM tag is also displayed when present.

Scenario: Waypoints without POI data display normally

WHEN a waypoint on the route detail page has no associated POI metadata
THEN the waypoint displays as before with coordinates and name only, with no empty POI sections shown

1.3 KiB Raw Blame History