Epic: Bounty completion (Operate -> Decide -> Payout -> Wrap -> Disputes)

[0xdevcollins]

Context

Organizer completion UI in v1 boundless: the per-bounty management surface that takes a published bounty through Operate -> Decide -> Payout -> Wrap -> Disputes. Mirrors the hackathon organizer management pages (submissions / judging / rewards) under /organizations/[id]/bounties/[bountyId]/*. Reuses the shared escrow runner (organizer scope), wallet kit, and funding modals.

Depends on the backend gaps: boundlessfi/boundless-nestjs milestone Bounty Operate to Payout (#337-#340). Payout (select-winners) + cancel already exist on the backend.

Organizer journey by mode (entryType x claimType)

Mode	Decide	Payout
OPEN + SINGLE_CLAIM	review the submission	select_winners (1)
OPEN + COMPETITION	review all submissions at deadline	select_winners (1-3)
APPLICATION_* + SINGLE_CLAIM	select 1 applicant -> they submit -> review	select_winners (1)
APPLICATION_* + COMPETITION	shortlist N -> they submit -> review	select_winners (1-3)

On payout settle the bounty becomes COMPLETED automatically and rewards are pushed on-chain.

Blueprint to mirror

• Overview + tabbed mgmt: app/(landing)/organizations/[id]/hackathons/[hackathonId]/page.tsx + submissions/judging/rewards/settings
• Winners + payout: rewards page (PublishWinnersWizard / AnnouncementStep / PreviewStep), hooks/use-hackathon-publish.ts, features/hackathons/api/use-escrow.ts (useEscrowOpRunner organizer scope), funding modals

Tasks

• FE: Bounty management dashboard shell + overview #630 FE: Bounty management dashboard shell + overview
• FE: Applications review + shortlist/select/decline (Decide) #631 FE: Applications review + shortlist/select/decline (Decide)
• FE: Submissions review (view submitted work for winner selection) #632 FE: Submissions review (view submitted work for winner selection)
• FE: Winner selection + Payout (select-winners signing flow) #633 FE: Winner selection + Payout (select-winners signing flow)
• FE: Cancel / refund flow #634 FE: Cancel / refund flow
• FE: Wrap (results/winners page + announcement + archive) #635 FE: Wrap (results/winners page + announcement + archive)
• FE: Dispute resolution UI #636 FE: Dispute resolution UI
• FE: Nav + codegen + end-to-end verification #637 FE: Nav + codegen + end-to-end verification

Out of scope

Configure (host/publish, shipped); the participant/builder UI (separate milestone). The v2 boundless-platform organizer UI (this lives in v1, alongside Configure).

[linear]

BOU-292

[Rachaelisa]

/attempt #638

Claiming this issue. Looking over the codebase now and will open a PR soon.

[Ojas2095]

/claim

I'd like to take this on! Reviewing the repository right now and will submit a PR shortly.

[coderabbitai]

🔗 Related PRs

#376 - Fix hackathon [merged]
#503 - Feat/improved rewards tab [merged]
#505 - Feat/improved rewards tab [merged]
#576 - fix(rewards): show track winners on the organizer rewards page [merged]
#582 - fix(rewards): match track winners by submissionId, not participantId [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!

[Talentgift24-ux]

I would love to work on this issue

[Rachaelisa]

/claim #638

Count me in on this one. I've started reviewing the repository and the issue requirements — looks straightforward enough. PR coming soon once I've tested the changes.