Migrate bounty mutation hooks to GraphQL

[0xdevcollins]

Depends on: #100
Migrate all bounty write operations from REST to GraphQL mutations.

Files to modify

• hooks/use-bounty-mutations.ts

Tasks

• useCreateBounty → use useCreateBountyMutation from generated hooks
• useUpdateBounty → use useUpdateBountyMutation (note: backend expects id inside input, not as a separate arg)
• useDeleteBounty → use useDeleteBountyMutation
• useClaimBounty → this mutation doesn't exist on the backend yet; either:
  • Remove this hook until the backend implements claimBounty, or
  • Use updateBounty with status: 'IN_PROGRESS' as a workaround
• Preserve optimistic update logic (the existing onMutate/onError/onSettled pattern)
• Update query key invalidation to use the new generated query key constants

Acceptance Criteria

• Create, update, and delete bounties all work via GraphQL mutations
• Optimistic updates still function correctly
• Cache invalidation still triggers list refreshes

[linear]

BOU-96

[coderabbitai]

🔗 Related PRs

#30 - feat: Implement React Query hooks for managing bounties [merged]
#34 - feat: Implement API-driven bounty fetching and display with dedicated loading, empty, and error UI components. [merged]
#47 - Add comprehensive GraphQL schema for bounties and projects API [merged]
#55 - feat-Implement Bounty Status Logic & Anti-Squatting [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 150 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 it combines the challenge of solving complex frontend performance problems with the opportunity to deliver a smoother, more reliable user experience, while also sharpening my skills with emerging design and resolution patterns.

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

[7maylord]

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

Hi, i am an experienced backend engineer and i can handle this issue, let me work on it, thanks

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

[Ekene001]

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

Hi, I've gone through the requirements and can have this ready in under 24 hours. I have a lot of experience building complex forms with wallet-connected flows, so I’m familiar with the balance between smooth UX and strict data validation required for event listing.

I’ll tackle this by setting up the form using React Hook Form and Zod to handle the validation for dates, pricing, and sponsor options. I’ll build the UI with Tailwind CSS to ensure it’s fully responsive and includes clean date/time pickers and an image upload field. Finally, I’ll integrate the submission logic with your backend API, ensuring the form respects the user's wallet connection and provides clear success or error feedback once the event is listed.

Please assign this to me!

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