Derive dashboard statistics from typed services

[Lakes41]

Difficulty: Hard

Type: Refactor

Summary

Refactor dashboard overview statistics so they are derived from typed services rather than hard-coded or directly imported mock arrays.

Current Behaviour

The dashboard relies on mock data for passes, guilds, members, and activity. Statistics can drift from source data if each page computes values independently.

Expected Behaviour

Dashboard stats should come from a shared service that computes totals, active counts, recent activity, and trend-ready values consistently.

Suggested Implementation

Add a dashboard metrics service that consumes pass, guild, member, and activity repositories. Use it on the overview page and add tests for edge cases such as empty data, draft passes, inactive members, and failed activity fetches.

Files or Areas Likely Affected

• apps/dashboard/app/dashboard/page.tsx
• apps/dashboard/lib/data/
• apps/dashboard/lib/metrics/
• apps/dashboard/lib/mock-data.ts
• apps/dashboard/test/

Acceptance Criteria

• Dashboard stats are calculated through a shared metrics service
• Draft and inactive records are counted intentionally
• Empty datasets return safe zero values
• Overview page no longer computes core metrics inline
• Tests cover normal, empty, and mixed-status datasets
• Metrics service can later consume live data without changing the page

Additional Notes

Assumption: current mock data remains the source for local development until live storage is introduced.

[YfengJ]

Hi maintainers, I would like to apply for this issue if it is available.

If assigned, I would add a typed dashboard metrics service instead of computing stats ad hoc in the page, preserve the current UI output, define intentional counting for draft/inactive records, return safe zero values for empty datasets, and add focused service tests for empty data, draft passes, inactive members, recent activity, and fetch/error edge cases.

[shadrach68]

I would like to work on this issue because I am a full-stack developer with 5+ years experience. I focus on identifying root causes and delivering clean, efficient, and maintainable solutions, with thorough testing to ensure reliable results.

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.
My PR will be submitted in under 10hours.

[grantfox-oss]

🦊 GrantFox — @shadrach68 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #48)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.