Add Playwright e2e coverage for the Decline Applicant flow

[Benjtalkshow]

PR #253 and #269 shipped the Decline Applicant flow: useDeclineApplicant hook, Decline button on each application card, confirmation AlertDialog with optional reason field, optimistic cache filter. No e2e spec covers this yet.

What to do

Add e2e/decline-applicant.spec.ts covering:

• Creator opens the bounty detail page and sees the application review dashboard
• Each application card shows a Decline button next to Select
• Clicking Decline opens the confirmation AlertDialog
• Submitting the dialog with no reason succeeds (reason is optional)
• The declined applicant disappears from the dashboard immediately (optimistic)
• If the applicant was in the comparison selection, they are removed from it
• On mutation error (mocked rejection from contract binding), the applicant reappears (rollback)

Reuse MOCK_SESSION and setupMocks from e2e/bounty-application.spec.ts. Stub the dashboard input by mocking the bounty detail query response with an applications array. Inject globalThis.__applicationContracts in the page init script to control mutation outcomes.

Acceptance criteria

• Spec lives at e2e/decline-applicant.spec.ts
• All test cases pass locally and on CI
• pnpm exec playwright test e2e/decline-applicant.spec.ts green

Files

• e2e/decline-applicant.spec.ts (new)

[linear]

BOU-303

[coderabbitai]

🔗 Related PRs

#180 - test(e2e): add Playwright bounty application flow test [merged]
#200 - Feat/bounty selection flow model 2 [merged]
#246 - feat: Add Playwright e2e coverage for bounty creation flow - Add e2e/… [merged]
#248 - chore(e2e): remove bounty-creation spec until create page exists [merged]
#253 - fix: implement decline applicant flow [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!

[zinodict121]

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

Hi maintainer, I will love to work on this issue. Please assign it to me, and i can start working on it immediately

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

[leocagli]

Hi, I'd like to add Playwright e2e coverage for the Decline Applicant flow. I can write tests covering the confirmation dialog, success state, and UI updates after decline. Could you assign me?

[drips-wave]

Congratulations, @zinodict121! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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