Add an error boundary around the seller dashboard stats panel to prevent a data error from crashing the full page

[Chucks1093]

Summary

A rendering or data error inside the seller dashboard stats panel currently crashes the entire dashboard page. An error boundary scoped to the stats panel should catch the error and show a fallback while keeping the invoice list section functional.

Scope

• Wrap the stats panel in a React error boundary
• Fallback UI: 'Dashboard stats unavailable — try refreshing'
• Include a retry button that resets the boundary and re-renders the stats panel
• Log the caught error to the existing client-side error logger
• The invoice breakdown list should remain fully interactive during the fallback state

Acceptance Criteria

• Stats panel error does not crash the dashboard page
• Fallback message and retry button shown on error
• Retry button resets boundary and re-renders the stats panel
• Error logged to the client-side logger
• Invoice list remains interactive during fallback

ETA: 12 hours

---

Coordinate on Telegram

[yesi3]

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

Hello Maintainer, I'd like to work on this issue.

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

[mikwansa]

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

Hi, can I work on this issue

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

[eischideraa-unn]

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

Hi Maintainer,
I'd like to take on this issue. I've reviewed the requirements, understand the scope, and can deliver a tested solution that aligns with the project's standards.

Thanks.

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

[Democodes-flash]

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

Hello, I’m Ademola Ayomide, a smart contract developer with experience building. I’d like to take on this issue and deliver a solid solution within 24 hours.

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

[Sam-Rytech]

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

Hi maintainer

I'd like to work on this issue

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Sam-Rytech as part of the Stellar Wave Program's 7th Wave 🥳

Moderator's reason: [Auto-assessed] The PR is open with no maintainer response across any of the four channels. The contributor successfully implemented the seller dashboard and wrapped the stats panel in an ErrorBoundary with the requested fallback UI and retry functionality, fulfilling all acceptance criteria including the specific UI text and component scoping.

😎 @Sam-Rytech: 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.