Standardize loading, error, and empty states across the Guilds and Integrations pages

[Lakes41]

Difficulty: Intermediate
Type: Bug

Background
CONTRIBUTING.md's PR Quality Expectations explicitly require that "any new route or component must handle loading, error, and empty states," implying this is an established project standard. The /guilds and /integrations routes are newer additions (the /integrations route is not yet mentioned in the top-level README's route list, only in CONTRIBUTING.md), and are good candidates for inconsistent state handling relative to older, more mature routes like /dashboard or /passes.

Problem
The /guilds and /integrations pages currently show inconsistent (or missing) handling for the loading, error, and empty-result states compared to other dashboard routes, creating a jarring experience (e.g. a blank page instead of a skeleton, or an unstyled error message).

Expected outcome
Both routes use the same shared loading skeleton, error boundary/message pattern, and empty-state component already established elsewhere in the dashboard (or a newly extracted shared version of it), so the UX is consistent across all routes.

Suggested implementation

• Audit /dashboard, /passes, /members, /activity for their current loading/error/empty patterns.
• Extract a shared <LoadingSkeleton />, <ErrorState />, and <EmptyState /> (or equivalent) into a shared components directory if not already present.
• Apply them consistently to /guilds and /integrations.
• Add basic tests/snapshots asserting each state renders for each of the two routes.

Acceptance criteria

• /guilds and /integrations render a loading skeleton while data is fetching.
• Both routes render a clear, styled error message on fetch failure (simulate via a forced error in mock mode).
• Both routes render a distinct empty state when there are zero guilds/integrations.
• Visual style matches the rest of the dashboard (mobile-first Tailwind, per CONTRIBUTING.md).
• pnpm --filter @guildpass/dashboard test and pnpm lint pass.

Likely affected files/directories
apps/dashboard/app/guilds/, apps/dashboard/app/integrations/, shared UI component directory (e.g. apps/dashboard/components/).

[mishellerv]

Hi! I’d like to work on this issue. I understand that the goal is to make the /guilds and /integrations routes consistent with the rest of the dashboard by properly handling loading, error, and empty states. I’d like to audit the existing patterns, reuse or extract shared UI components where appropriate, apply them to both routes, and add tests covering the different states. If possible, I’d appreciate being assigned this issue. Thank you!

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@mishellerv's PR #318 was approved and merged by @Lakes41.

🏆 @mishellerv: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.

👏 Great work, @mishellerv! Keep contributing to Adamantine-guild.