Add submission mutation hooks (new)

[0xdevcollins]

Depends on: #100

The backend has three submission-related mutations (submitToBounty, reviewSubmission, markSubmissionPaid) that have no corresponding frontend hooks yet.

Tasks

• Create hooks/use-submission-mutations.ts with:
  • useSubmitToBounty() — calls submitToBounty mutation
  • useReviewSubmission() — calls reviewSubmission mutation
  • useMarkSubmissionPaid() — calls markSubmissionPaid mutation
• Each hook should invalidate the relevant bounty detail query on success
• Add submission query key factory to lib/query/query-keys.ts
• Wire the hooks into existing or new UI (bounty detail page's submission section)

Acceptance Criteria

• Users can submit PRs to bounties via GraphQL
• Org members can review and mark submissions as paid
• Bounty detail cache refreshes after submission actions

[linear]

BOU-97

[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]
#40 - feat: add user profile mutation hook with Better Auth integration [merged]
#60 - feat: Implement Model-Specific Claim/Apply/Join Actions [merged]
#90 - feat:implement sponsor review dashboard. [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

[Ekene001]

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

Hello, can I handle this?

I've gone through the requirements and can have this ready in under 24 hours. I have experience implementing GraphQL mutation patterns and cache invalidation strategies, so I’m familiar with ensuring UI states stay perfectly synced after contract-related actions.

I’ll tackle this by creating the use-submission-mutations.ts file and implementing the three hooks for submitting, reviewing, and marking payments. I'll use TypeScript to define the mutation logic and integrate the query key factory to ensure that the bounty detail cache automatically refreshes on success. Finally, I’ll wire these hooks into the bounty detail page so the submission flow is fully functional and provides immediate visual feedback to both users and org members.

Please assign this to me.

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

[Shadow-MMN]

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

Hi , please can I work on this issue .

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

[legend4tech]

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

Hi, I’m Legend4Tech, a full-stack developer and a former fellow at OnlyDust. I came across this issue and I’m really interested in working on it. I have experience across both frontend and backend development, and I enjoy digging into problems, understanding the context, and delivering clean, well-structured solutions.

I’d be happy to contribute and collaborate with the maintainers to get this resolved. Please let me know if you’d like me to proceed or if there are any specific guidelines I should follow.

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

[drips-wave]

Congratulations, @Shadow-MMN! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 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 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 🌊