Implement the Decline applicant flow on the application review dashboard

[Benjtalkshow]

The application review dashboard at components/bounty/application-review-dashboard.tsx lets a creator Select an applicant or compare two side by side. The Decline button was removed in an earlier PR because it had no handler. We still need a way to formally decline applicants so they receive a notification and the application leaves the review queue.

What to do

Add a useDeclineApplicant mutation in hooks/use-bounty-application.ts accepting bountyId and applicantAddress. Optimistically remove the applicant from the dashboard's applications list and roll back on error.

In application-review-dashboard.tsx:

• Add a Decline button next to Select on each application card, using the same red-outline styling as the previous version
• Open a confirmation AlertDialog with a small textarea for an optional reason
• Submit through the new mutation
• Show a success toast and remove the card from the list on success

The applicant should see a "Declined" notification on their side via the existing notification system once that wiring is in place (out of scope for this issue).

Acceptance criteria

• Each application card shows a Decline button next to Select
• Clicking opens a confirmation AlertDialog with an optional reason field
• Confirming removes the application from the list with an optimistic update
• Reason text is recorded against the application in the cache
• Comparison mode handles the case where one of the two selected applicants is declined (drop them out of comparison)

Files

• components/bounty/application-review-dashboard.tsx
• hooks/use-bounty-application.ts

[linear]

BOU-233

[coderabbitai]

🔗 Related PRs

#111 - Feat: implementation logic for single claim model [merged]
#170 - Feature: Bounty Cancellation and Refund Flow [merged]
#180 - test(e2e): add Playwright bounty application flow test [merged]
#200 - Feat/bounty selection flow model 2 [merged]
#201 - Feat/Dispute Resolution Workflow for Bounties [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!

[harmondconsultant-png]

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

Can you kindly assign this to me?

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

[Yash-Karakoti]

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

gm gm, i really wanna work on this , I’ll implement the useDeclineApplicant mutation to handle the backend logic with optimistic updates. On the dashboard, I’ll add a red-outlined Decline button to each card that triggers an AlertDialog with an optional reason field. i'll ensure the local cache updates immediately upon success and that any applicants currently in comparison mode are automatically removed if declined.

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

[iyop666]

Opened a focused PR for this: #237

[whisper011]

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

Gm! I'd like to work on this.

I've gone through the issue and understand what needs to be done. I'll keep the fix scoped, clean, and tested — and communicate clearly if anything comes up along the way.

Ready to start immediately. Feel free to assign it!

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

[frank0277]

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

Hi maintainer, I’d like to work on this issue.

I’ve reviewed the requirements and I’m confident I can submit a focused PR that stays within the issue scope. I’ll make sure to:

• keep the changes minimal and relevant
• avoid touching unrelated files
• run the required build/test checks before opening the PR
• include a clear summary, validation steps, and Closes #ISSUE_NUMBER in the PR bo

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

[Ishant5436]

Fixed in earlier commits