Add integration test for 404 page rendering on unknown routes

[Chucks1093]

Summary

The NotFoundPage component is registered for all unmatched routes but has no test confirming it actually renders when a user navigates to a path that does not exist.

Scope

• Navigate to a non-existent path in the test renderer
• Assert the NotFoundPage content is rendered
• Assert the page title or heading contains a 404 or not found message

Acceptance Criteria

• Unknown route renders NotFoundPage
• Page contains a recognizable not-found message

ETA: 12 hours

---

Coordinate on Telegram

[Benedict315]

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

Hello please assign

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

[Talentgift24-ux]

@Talentgift24-ux has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would love tto work on this issue

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

[drips-wave]

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

🧑‍💻 @Benedict315: 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 🌊