Extend the Bounty type with optional UI fields to remove ad-hoc casts

[Benjtalkshow]

The UI reads several fields from bounty that aren't on the codegen BountyFieldsFragment: claimCount, maxParticipants, maxSlots, totalSlotsOccupied, milestones, contributorProgress, submissions, applications. Components and hooks work around this with inline casts like (bounty as { submissions?: Array<{ ... }> | null }) scattered everywhere. The casts drift in shape from one file to the next, and TypeScript can't help when one of them is wrong.

What to do

Define each of these as optional fields on the Bounty interface in types/bounty.ts. Most of them are already there; the gap is consistency. Specifically:

• submissions?: BountySubmission[] | null
• applications?: BountyApplication[] | null (add BountyApplication if missing)
• claimCount?: number | null
• maxParticipants?: number | null
• maxSlots?: number | null
• totalSlotsOccupied?: number | null
• milestones?: Milestone[] | null
• contributorProgress?: ContributorProgress[] | null

Where useBountyDetail already returns BountyFieldsFragment & Partial<Bounty>, that covers most call sites. The remaining ad-hoc casts in bounty-detail-client.tsx, bounty-detail-sidebar-cta.tsx, model4-maintainer-dashboard.tsx, and use-competition-join-state.ts should be removed in favor of the typed shape.

Acceptance criteria

• No (bounty as { ... }) casts remaining in the bounty detail tree
• pnpm tsc --noEmit and pnpm lint pass
• No behavioral change

Files

• types/bounty.ts
• components/bounty-detail/bounty-detail-client.tsx
• components/bounty-detail/bounty-detail-sidebar-cta.tsx
• components/bounty-detail/model4-maintainer-dashboard.tsx
• hooks/use-competition-join-state.ts

[linear]

BOU-236

[coderabbitai]

🔗 Related PRs

#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#56 - feat: Implementation of bounty participation & submission backend logic [merged]
#87 - feat:implement user dashboard-my claims [merged]
#178 - Feat/competition bounty flow [merged]
#186 - Implement Multi-Winner Milestone Bounty Flow (Issue #173) [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!

[oxravenz]

Submitted fix via PR: #221

[1sraeliteX]

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

I would like to work on this issue because i can handle it effectively and on time

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

[drips-wave]

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

🧑‍💻 @1sraeliteX: 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