FE: Bounty management dashboard shell + overview

[0xdevcollins]

Context

Part of the Bounty Operate to Payout milestone (v1 boundless). The per-bounty organizer management dashboard: the hub for Operate -> Decide -> Payout -> Wrap. The org bounty list already exists (Configure #597); this adds the per-bounty management shell.

Blueprint to mirror

• app/(landing)/organizations/[id]/hackathons/[hackathonId]/page.tsx (overview) + the tabbed management layout (submissions/judging/rewards/settings).

Tasks

• Route app/(landing)/organizations/[id]/bounties/[bountyId]/page.tsx + tabbed management layout: Overview, Applications, Submissions, Payout/Winners, Settings (+ Disputes).
• Overview: status/phase, mode badges, deadlines, prize tiers, intake stats (consume the operate-reads endpoint), escrow event link.
• Mode-aware tab visibility (e.g. Applications tab only for application entry types).

Acceptance criteria

• Organizer opens a published bounty and sees status + stats + navigable management tabs, correct per mode.

Depends on

• Backend operate reads.

[linear]

BOU-283

[coderabbitai]

🔗 Related PRs

#411 - feat: Implement Organization Profile Page ui [merged]
#503 - Feat/improved rewards tab [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!

[juni2003]

Hi, I like to claim #630 (FE: Bounty management dashboard shell + overview). I will implement:
New route: app/(landing)/organizations/[id]/bounties/[bountyId]/page.tsx
BountyOverview + BountyTabs components and client hook use-bounty with a mock fallback
Unit test and a small e2e smoke test. I’ll open a draft PR (feat/bounty-dashboard-630) shortly and mark what’s mocked vs. real API calls. Could you confirm whether the operate-reads endpoint is available, or should I keep mocks for the initial PR? Please assign the issue to me if that’s preferred.

[github-actions]

Closed by #667 (merged into feat/t-replace).