Add contract tests between dashboard and integration client

[Lakes41]

Summary

Add contract tests to ensure the dashboard's data models stay compatible with @guildpass/integration-client responses.

Current Behaviour

The dashboard view models and integration client types can drift independently. When live mode is wired in, mismatches may only appear at runtime.

Expected Behaviour

CI should catch breaking changes between integration client response types and dashboard mapping logic.

Suggested Implementation

Create fixture responses for membership lookup, wallet verification, error responses, and missing data. Test that the dashboard mapping layer converts them into the expected member, guild, activity, and verification view models.

Files or Areas Likely Affected

• apps/dashboard/lib/data/
• apps/dashboard/test/fixtures/
• packages/integration-client/src/types.ts
• packages/integration-client/src/client.ts
• apps/dashboard/package.json

Acceptance Criteria

• Fixtures cover successful membership lookup by wallet
• Fixtures cover successful membership lookup by Discord user
• Fixtures cover wallet verification success and failure
• Dashboard mapping tests fail when required response fields drift
• Error responses are mapped into safe dashboard error states
• Contract test commands are documented for contributors

Additional Notes

Assumption: the integration client is the intended live boundary for at least some dashboard data.

[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.

[barry01-hash]

I would love to work on this project.
Please approve

[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.