Add durable persistence for dashboard-managed entities

[Lakes41]

Summary

Introduce a persistence layer for passes, guild settings, members, and activity so dashboard changes can survive refreshes and deployments.

Current Behaviour

The dashboard relies on static mock data. Any future create, edit, or activity ingestion flow would be session-only unless backed by storage.

Expected Behaviour

The dashboard should have a storage abstraction that can support mock in-memory data locally and a durable backend store in live deployments.

Suggested Implementation

Define repository interfaces for passes, guild settings, members, and activity. Add an initial adapter for mock data and a production adapter for a selected backend storage option. Keep storage access server-side.

Files or Areas Likely Affected

• apps/dashboard/lib/data/
• apps/dashboard/lib/repositories/
• apps/dashboard/app/api/
• apps/dashboard/lib/env.ts
• apps/dashboard/app/settings/page.tsx
• README.md

Acceptance Criteria

• Repository interfaces exist for core dashboard entities
• Mock adapter preserves local development behaviour
• Durable adapter is server-only and does not expose credentials
• Pass and settings updates survive page refreshes in durable mode
• Activity events can be appended and queried through the repository layer
• Environment configuration documents the selected storage mode

Additional Notes

Do not hard-code one vendor unless maintainers have already chosen it. If storage choice is undecided, implement the interface and mock adapter first, then document the production adapter contract.

[jaynomyaro]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[khalifa-zoro]

Heyy man, this seems like a well suited issue for my skill set, I'd love to help you fix it and make solid contributions to your project