Add an App routing test asserting Analytics/Notification chunks stay lazy

[1nonlypiece]

📌 Description

src/App.tsx deliberately lazy-loads Analytics and Notification behind
Suspense while eagerly importing the rest. There is risk that a future static
import re-bundles these heavy chunks (recharts, jsPDF) into the initial bundle.

This issue adds a guard test asserting the lazy boundary holds and the Suspense
fallback renders.

🎯 Requirements and Context

• Render App (or a slimmed routing harness) at /analytics and /notifications
  within a router and assert the Skeleton fallback appears before the route
  resolves.
• Assert the eager routes (/, /vaults, …) render synchronously without a
  fallback flash.
• Add a lightweight static-analysis assertion (or comment-guard test) that
  Analytics/Notification are imported via lazy(() => import(...)) only.

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b test/app-lazy-routes-guard

2. Implement changes

• Add src/__tests__/App.lazyRoutes.test.tsx (mock heavy deps as needed).

3. Test and commit

• Run: npm run test
• Edge cases: navigating to a lazy route then back, unknown path → NotFound.

Example commit message

test: guard lazy Analytics/Notification route boundaries

✅ Guidelines

• Minimum 95% test coverage on the touched lines.
• No regressions in routing or code-splitting.
• Keep the diff small and reviewer-friendly.
• Timeframe: 96 hours.

🏷️ Labels

type-testing · area-frontend · MAYBE REWARDED · GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the contributor Discord to coordinate, ask questions, and get unblocked
  fast: https://discord.gg/xvNAvMJf
• Please introduce yourself in the channel before you start so we can avoid
  duplicate work, pair you with a reviewer, and get your PR merged quickly.
• Maintainers actively triage this channel and aim for fast, clear, respectful
  reviews — reach out any time you're blocked.

[GBOYEE]

Hello! I'd like to take this. I'll write a test that renders the App routing harness and asserts Analytics/Notification stay lazy behind Suspense (not statically imported into the initial chunk). PR in a few hours.

[chisomvictorcv-sketch]

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

Good day I am a full stack developer with over 6 years of experience and I have good practical knowledge on this kindly assign this to me.

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

[drips-wave]

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

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