Remove Next.js API route proxies

[0xdevcollins]

Depends on: Issues #101, #102, #103, #104
The app/api/bounties/ directory contains Next.js API routes that proxy REST calls. Once all hooks call GraphQL directly, these proxy routes are dead code.

Tasks

• Delete app/api/bounties/ and all subdirectories
• Delete app/api/applications/, app/api/submissions/ if also migrated
• Remove unused REST helpers from lib/api/client.ts and lib/api/bounties.ts
• Remove axios from package.json if no longer used elsewhere
• Run npm run build to verify no broken imports

Acceptance Criteria

• No REST proxy routes remain for bounties
• Bundle size is reduced
• Build passes cleanly

[linear]

BOU-99

[coderabbitai]

🔗 Related PRs

#34 - feat: Implement API-driven bounty fetching and display with dedicated loading, empty, and error UI components. [merged]
#45 - Ekene001/bou 59 setup graphql client code generation [merged]
#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#60 - feat: Implement Model-Specific Claim/Apply/Join Actions [merged]
#88 - feat: Implement bounties detail page [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!

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[BigJohn-dev]

@BigJohn-dev has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

This issue appeals to me because i have a solid experience using Next.js

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

[Abidoyesimze]

@Abidoyesimze has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi I'd like to work on this issue

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

[drips-wave]

Congratulations, @Abidoyesimze! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Abidoyesimze: 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 issued 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 🌊