Add structured log for each page navigation event recording the route and time since last navigation

[Chucks1093]

Summary

There is no client-side log tracking navigation between routes, making it difficult to reconstruct user journeys when debugging production issues. A debug-level log on each route change should record the destination route and the elapsed time since the previous navigation.

Scope

• Listen to route change events in the router and emit a debug-level log on each transition with fields: from_route, to_route, time_since_last_nav_ms
• time_since_last_nav_ms is the wall-clock time between the previous navigation completion and the current one
• Log emitted after the route change completes, not when it begins
• from_route is null on the first navigation (page load)

Acceptance Criteria

• Log emitted after each route change with all three fields
• from_route is null on first navigation
• time_since_last_nav_ms reflects time since last completed navigation
• Log not emitted in the test environment

ETA: 12 hours

---

Coordinate on Telegram

[MoscowDev]

@MoscowDev has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd be happy to take this issue on. I have experience building production-ready applications and collaborating effectively through GitHub workflows, including implementing features, resolving bugs, and submitting well-documented pull requests.

I'll carefully review the existing implementation, identify the root cause, and deliver a robust, maintainable solution that aligns with the project's architecture and coding standards. Before submitting my PR, I'll thoroughly test the changes to ensure reliability and avoid regressions.

My goal is to contribute high-quality, clean, and maintainable code while communicating clearly throughout the process and delivering a dependable solution in a timely manner.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MoscowDev to this issue.

[yangqingqu]

@yangqingqu has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer, I would love to work on this issue. Kindly assign to me, thanks.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @yangqingqu to this issue.

[GABRIELOFGOD]

@GABRIELOFGOD has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I can work on this please assign to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GABRIELOFGOD to this issue.

[drips-wave]

Congratulations, @GABRIELOFGOD! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @GABRIELOFGOD: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@GABRIELOFGOD's PR #609 was approved and merged by @Chucks1093.

🏆 @GABRIELOFGOD: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (48 total points). Track your full progress on GrantFox.

👏 Great work, @GABRIELOFGOD! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @GABRIELOFGOD as part of the Stellar Wave Program's 7th Wave 🥳

😎 @GABRIELOFGOD: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.