Make Journey Mode authored and shareable

[nedcut]

What changed

• adds an authored opening card for the global Relive entry
• ends autoplay on a deliberate completion card with Replay, Share, and Return to map
• preserves exact-item deep links and direct day/photo entry behavior
• uses the native share sheet with clipboard fallback and accessible feedback
• adds Open Graph/Twitter metadata and a generated social image
• expands unit and end-to-end Journey coverage

Why

Journey Mode is the most distinctive public experience in the project. This turns it from a capable media viewer into a beginning-to-end travel story without changing the underlying timeline or URL model.

Configuration

Set NEXT_PUBLIC_SITE_URL in production to the canonical deployed origin so absolute social metadata resolves correctly. Local builds intentionally fall back to http://localhost:3000.

Validation

• npm run lint (0 errors; one pre-existing hook dependency warning)
• npm run typecheck
• npm test (214 tests)
• npm run test:e2e (10 tests)
• git diff --check

Manual smoke test

Open Relive from the global header and begin the story. Confirm a direct ?journey=photo:<id> link bypasses the intro, autoplay finishes on the ending card, Replay restarts the sequence, Share opens the native sheet or reports that the link was copied, and Return to map exits cleanly.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lofoten-map	Ready	Preview, Comment	Jul 11, 2026 8:36pm

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Warning

Review limit reached

@nedcut, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2e92c462-4b0a-4c7e-84fa-54d045a1fb71

📥 Commits

Reviewing files that changed from the base of the PR and between bd21259 and dd1e2ef.

📒 Files selected for processing (13)

• .env.example
• README.md
• app/layout.tsx
• app/opengraph-image.tsx
• app/page.tsx
• components/JourneyPlayback.tsx
• e2e/trip.spec.ts
• lib/journey-video.test.ts
• lib/journey-video.ts
• lib/share.test.ts
• lib/share.ts
• lib/site-url.test.ts
• lib/site-url.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/authored-journey-sharing

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}