Implement the maintainer dashboard actions for Multi-Winner Milestone bounties

[Benjtalkshow]

The Model 4 maintainer dashboard at components/bounty-detail/model4-maintainer-dashboard.tsx lists each contributor with action buttons for Release Payment, Advance, Remove, View Submissions, and Message. Every action runs a shared handleAction stub that logs and resets after a fake delay. The button labels still carry the [Coming soon] suffix.

We need each action to actually do something visible. The dashboard should reflect contributor state changes so the maintainer can manage participants end to end.

What to do

Split the single handleAction into named handlers and back each with a mutation in hooks/use-bounty-application.ts:

• Release Payment records the payout for the contributor's current milestone and updates the per-bounty escrow status
• Advance moves the contributor to the next milestone in contributorProgress
• Remove deletes the contributor from contributorProgress and decrements totalSlotsOccupied
• View Submissions opens a side panel or modal listing the contributor's submitted work
• Message opens a basic message dialog that records the message against the bounty

Drop the [Coming soon] suffix from each button label once wired. Keep the tooltip wording short.

Acceptance criteria

• Release Payment visibly updates the escrow status panel on the bounty detail
• Advance moves the contributor to the next milestone, visible in the funnel and in the dashboard's current milestone column
• Remove drops the contributor from the funnel and the dashboard, and the slot count updates
• View Submissions opens a panel with a list (empty state acceptable if no submissions exist)
• Message opens a dialog and records the text against the bounty
• All actions show a loading spinner on the triggering button and a success toast on completion

Files

• components/bounty-detail/model4-maintainer-dashboard.tsx
• hooks/use-bounty-application.ts
• components/bounty-detail/bounty-detail-client.tsx

[linear]

BOU-230

[coderabbitai]

🔗 Related PRs

#60 - feat: Implement Model-Specific Claim/Apply/Join Actions [merged]
#90 - feat:implement sponsor review dashboard. [merged]
#111 - Feat: implementation logic for single claim model [merged]
#117 - feat: add frontend hooks for submission mutations [merged]
#200 - Feat/bounty selection flow model 2 [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!

[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.

[sirakinb]

Opened a PR for this issue: #238

It replaces the shared [Coming soon] action stub with named mutations and visible dashboard state updates for Release Payment, Advance, Remove, View Submissions, Message, and View All Applications. Verified with:

• npm run lint
• npx tsc --noEmit
• npm run build

[Ishant5436]

Fixed in earlier commits

[Ishant5436]

Settlement Information:

• Solana: 2WktXRjaQ4GKhj6FJhUSndTBLVjxrk43TQwyywehneDA

[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.

[kingjosmel]

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

I am a Full-Stack Developer, and I will wire up the Model 4 maintainer dashboard to transition it from static stubs into a fully functional, state-driven participant management command center.

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