Consolidate the mock data files into lib/mock/ with a factory pattern

[Benjtalkshow]

The mock data layer is spread across several top-level files: lib/mock-bounty.ts, lib/mock-model4.ts, lib/mock-leaderboard.ts, lib/mock-wallet.ts, lib/mock-project.ts, lib/mock-data.ts. They're imported from random places across the codebase with no consistent convention, and there's no single place to flip between data sources.

Move them into lib/mock/ and expose factory functions so we can swap data sources in one place later.

What to do

Create lib/mock/ with subfiles per domain:

• lib/mock/bounties.ts
• lib/mock/leaderboard.ts
• lib/mock/wallet.ts
• lib/mock/projects.ts
• lib/mock/model4.ts

Each file should export factory functions (makeMockBounty(overrides?), makeMockLeaderboardEntry(...), etc.) rather than static arrays where possible, so tests and stories can build fixtures inline.

Add lib/mock/index.ts that re-exports everything.

Find and replace all imports across the codebase. Delete the old top-level files.

Acceptance criteria

• All mock imports come from @/lib/mock/... or @/lib/mock
• No remaining lib/mock-*.ts files at the top level
• pnpm tsc --noEmit and pnpm lint pass
• No behavioral change in the app

Files

• lib/mock-*.ts (delete)
• lib/mock/* (new)
• All importers across app/, components/, hooks/

[linear]

BOU-235

[coderabbitai]

🔗 Related PRs

#10 - implement discover page with bounty and project cards, filtering, and sorting capabilities. [merged]
#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#75 - feat(rating): add RatingStars, RatingModal; integrate maintainer rati… [merged]
#110 - feat: Implement Earnings & Payout Tracking [merged]
#189 - Fixed the - Transition Global State from globalThis to TanStack Query - [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[superstarflayce]

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

I would like to work on this issue because I’m passionate about research, documentation, and contributing to the growth of the Stellar ecosystem.

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

[Shadow-MMN]

@Shadow-MMN has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, please can I work on this issue.

I plan to consolidate the current scattered mock data layer into a centralized lib/mock/ structure with domain-specific files and shared export patterns. Instead of relying on static mock arrays, I will introduce factory functions such as makeMockBounty, makeMockProject, and related builders so fixtures can be generated dynamically for tests, stories, and future data-source switching.

I will also add a single lib/mock/index.ts export layer and refactor all existing imports across the codebase to use the new structure consistently. Once migration is complete, I will remove the old lib/mock-*.ts files entirely.

Before submitting the PR, I will verify there are no remaining legacy imports, ensure there is no behavioral regression in the app, and confirm both pnpm tsc --noEmit and pnpm lint pass successfully.

ETA 24 hours.

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

[drips-wave]

Congratulations, @Shadow-MMN! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @Shadow-MMN: 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 🌊

[Ishant5436]

Fixed in earlier commits