Add Playwright e2e coverage for the Raise Dispute flow

[Benjtalkshow]

PR #256 and #268 shipped the Raise Dispute flow: useRaiseDispute hook, RaiseDisputeDialog component, /api/disputes REST proxy, and the trigger button on the bounty sidebar. No e2e spec covers this yet, so any regression in the dialog flow will slip through CI.

What to do

Add e2e/raise-dispute.spec.ts covering:

• Eligible user (creator or participant on a bounty in IN_PROGRESS or UNDER_REVIEW) sees an active Raise Dispute button
• Clicking it opens the AlertDialog with reason Select and description Textarea
• Submitting with empty reason or empty description keeps the dialog open and shows inline validation
• Submitting valid input closes the dialog, shows a success toast, and redirects to /dispute/{newDisputeId}
• On API failure (mocked 500), the dialog stays open and shows an error toast

Mock the POST /api/disputes route via page.route('**/api/disputes', ...). Follow the conventions in e2e/bounty-application.spec.ts for session setup and mock GraphQL responses.

Acceptance criteria

• Spec lives at e2e/raise-dispute.spec.ts
• All five test cases pass locally and on CI
• pnpm exec playwright test e2e/raise-dispute.spec.ts green
• Reuses the MOCK_SESSION and setupMocks pattern from bounty-application.spec.ts

Files

• e2e/raise-dispute.spec.ts (new)

[linear]

BOU-302

[Glittersup]

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

I’m interested in handling this issue. I’ve built and tested web3 applications across contracts, backend services, and frontend flows.

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

[coderabbitai]

🔗 Related PRs

#180 - test(e2e): add Playwright bounty application flow test [merged]
#201 - Feat/Dispute Resolution Workflow for Bounties [merged]
#246 - feat: Add Playwright e2e coverage for bounty creation flow - Add e2e/… [merged]
#256 - feat: implement raise dispute flow with redirect to dispute review page [merged]
#268 - fix(disputes): restore useRaiseDispute hook lost in merge [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

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

[DevSolex]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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