FE: Bounty detail page (/bounties/[id])

[0xdevcollins]

Context

Part of the Bounty Builder Lifecycle milestone (v1 boundless). The bounty detail page is the hub for the builder: it shows the bounty, the builder's current status, and the mode-aware entry CTA.

Blueprint to mirror

• app/(landing)/hackathons/[slug]/page.tsx (SSR detail)

Tasks

• Route app/(landing)/bounties/[id]/page.tsx (or [slug]): description, acceptance criteria / prize tiers, mode badges, deadlines, organization.
• Eligibility panel: reputationMinimum (open + single claim) or applicationCreditCost (application modes); show the caller's current status via useMyBountyApplication.
• Mode-aware CTA: Claim (open + single claim), Join (open + competition), Apply (application entry types). Disabled/explained when deadline passed or already applied.

Acceptance criteria

• Detail renders correctly per mode; the CTA routes to the right entry flow; the caller's current status is shown.

Depends on

• Bounty data layer.

[linear]

BOU-272

[coderabbitai]

🔗 Related PRs

#430 - Submission page [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!

[Ojas2095]

/claim

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

[Benjtalkshow]

Done in #646 (merged into feat/t-replace). Closing manually since auto-close only fires on merges to the default branch.