Mobile Raise Dispute CTA still shows "Coming Soon" — bring to parity with desktop sidebar

[Benjtalkshow]

components/bounty-detail/bounty-detail-mobile-cta.tsx:190 renders the Raise Dispute button as a permanently-disabled "Coming Soon" placeholder:

{canRaiseDispute && (
  <Button variant="ghost" className="w-full mt-2 text-gray-400 text-xs h-8" disabled>
    <Gavel className="size-3 mr-2" />
    Raise a Dispute (Coming Soon)
  </Button>
)}

But the flow already shipped in PRs #256 and #268: useRaiseDispute hook, RaiseDisputeDialog component, /api/disputes proxy. The desktop sidebar at components/bounty-detail/bounty-detail-sidebar-cta.tsx:248-262 wires all of this up correctly. Mobile users currently have no way to raise a dispute because of the stale stub.

What to do

Mirror the desktop sidebar pattern in bounty-detail-mobile-cta.tsx:

• Import RaiseDisputeDialog from ./raise-dispute-dialog
• Add a local const [disputeDialogOpen, setDisputeDialogOpen] = useState(false)
• Replace the disabled button with an enabled Button whose onClick calls setDisputeDialogOpen(true)
• Drop the "(Coming Soon)" label, drop the disabled prop, keep the Gavel icon and canRaiseDispute gate
• Render <RaiseDisputeDialog open={disputeDialogOpen} onOpenChange={setDisputeDialogOpen} bountyId={bounty.id} /> near the other mobile dialogs

Acceptance criteria

• No "Coming Soon" string in bounty-detail-mobile-cta.tsx
• Clicking the mobile button opens the same RaiseDisputeDialog the desktop sidebar opens
• On a small viewport, the dispute flow works end to end (open dialog, pick reason, type description, submit, see toast, redirect)
• pnpm tsc --noEmit and pnpm lint pass

Files

• components/bounty-detail/bounty-detail-mobile-cta.tsx
• components/bounty-detail/raise-dispute-dialog.tsx (reference)
• components/bounty-detail/bounty-detail-sidebar-cta.tsx (reference for the pattern)

[linear]

BOU-305

[coderabbitai]

🔗 Related PRs

#201 - Feat/Dispute Resolution Workflow for Bounties [merged]
#241 - Split bounty-detail-sidebar-cta into three focused files [merged]
#251 - Implement Apply for Slot on Multi-Winner Milestone bounties [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!

[forexlord]

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

Hi maintainer, please i would love to work on this, pity please

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

[oscarj007]

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

I have prior experience in solving in solving similar problems
Please permit me to solve it

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

[Oluwasuyi-Timilehin]

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

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.
I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!
ETA: 24 hours

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

[Godfrey-Delight]

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

Hi maintainer
Let me take this one off your plate ASAP

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

[drips-wave]

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

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

[leocagli]

Leo Cagliero here (Starmaker / Open Stellar). In bounty-detail-mobile-cta.tsx:190 the Raise Dispute button is hardcoded as disabled. The fix replaces the placeholder with the same <RaiseDisputeButton> component already used in the desktop sidebar — it receives the same bounty and canRaiseDispute props so the logic is identical, just rendered in the mobile CTA. Can I be assigned?