Split bounty-detail-sidebar-cta.tsx into SidebarCTA and MobileCTA files

[Benjtalkshow]

components/bounty-detail/bounty-detail-sidebar-cta.tsx is around 680 lines and exports both SidebarCTA and MobileCTA from the same file. The two components duplicate state and event handlers (cancel dialog, dispute dialog, application dialog, copy logic) and any change to the apply or dispute flow has to be made in both places. The file is hard to read and a constant merge-conflict surface. We've already had merges drop handleApply from SidebarCTA and break the build.

What to do

Split into three files:

• components/bounty-detail/bounty-detail-sidebar-cta.tsx exports SidebarCTA
• components/bounty-detail/bounty-detail-mobile-cta.tsx exports MobileCTA
• components/bounty-detail/use-bounty-cta-state.ts exports a shared hook returning everything both components need: walletAddress, hasJoined, isPastDeadline, handleJoin, handleApply, cancel dialog state, copy state, canRaiseDispute, etc.

Update bounty-detail-client.tsx to import MobileCTA from the new file. No behavioral change.

Acceptance criteria

• Both components render exactly as before
• No duplicated state or event handlers between the two files
• Each file is under 300 lines
• The shared hook owns all the data both components consume

Files

• components/bounty-detail/bounty-detail-sidebar-cta.tsx
• components/bounty-detail/bounty-detail-mobile-cta.tsx (new)
• components/bounty-detail/use-bounty-cta-state.ts (new)
• components/bounty-detail/bounty-detail-client.tsx

[linear]

BOU-234

[coderabbitai]

🔗 Related PRs

#17 - feat: Built BountyCard component with shadcn composition [merged]
#112 - Refactor bounty logic and data structures to align with backend schema [merged]
#165 - refactor: modularize BountiesPage and fix status filter bug (#127) [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!

[Biokes]

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

Hi maintainer,
I will like to work on this issue.

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

[18060910075zx-coder]

Submitted PR: #224

It splits SidebarCTA/MobileCTA and moves shared state into use-bounty-cta-state.ts as requested.

[drips-wave]

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

🧑‍💻 @Biokes: 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 earlier commits