Add Playwright e2e coverage for the bounty creation flow

[Benjtalkshow]

We have Playwright e2e coverage for the bounty application flow in e2e/bounty-application.spec.ts, but the bounty creation flow at /bounty/create has no e2e coverage. This is the highest-value path on the sponsor side and we keep changing the form fields without a regression net.

What to do

Add e2e/bounty-creation.spec.ts covering:

• Navigation to /bounty/create while authenticated (use the same MOCK_SESSION pattern from the existing spec)
• Step 1: fill title, description, organization, GitHub URL, and bounty type
• Step 2: fill reward amount, currency, and deadline (and the milestone or competition fields if the type requires them)
• Step 3: review and click Create
• Assert the user is redirected to /bounty/{newId} after successful creation
• A separate test for the validation path: submitting Step 1 with an empty title should keep the user on Step 1 and show the title error

Mock the CreateBounty GraphQL mutation via page.route('**/api/graphql', ...) following the same setup pattern as bounty-application.spec.ts.

Acceptance criteria

• Happy-path test passes locally and on CI
• Validation test passes locally and on CI
• pnpm exec playwright test e2e/bounty-creation.spec.ts green
• New tests follow the structure and mock conventions in bounty-application.spec.ts

Files

• e2e/bounty-creation.spec.ts (new)

[linear]

BOU-240

[coderabbitai]

🔗 Related PRs

#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#110 - feat: Implement Earnings & Payout Tracking [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!

[Delightech28]

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

I'd like to work on this

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

[drips-wave]

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

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

[Ishant5436]

Fixed in #215 test E2E coverage