FE: Submissions review (view submitted work for winner selection)

[0xdevcollins]

Context

Part of the Bounty Operate to Payout milestone (v1 boundless, Decide). The organizer reviews submitted work to choose winners. This is the surface that feeds winner selection.

Blueprint to mirror

• Hackathon organizer submissions review / detail sheet.

Tasks

• Submissions tab: list submissions (consume the organizer submissions-review endpoint) with applicant, contentUri link (PR/repo/writeup/demo), anchor status, submitted-at.
• Submission detail view; respect submissionVisibility (competition HIDDEN_UNTIL_DEADLINE: gate review until deadline).
• Mark/track which submissions the organizer intends to award (pre-select per prize tier), feeding the Payout step.

Acceptance criteria

• Organizer can open and review each submission's work and stage winners for payout.

Depends on

• Backend organizer submissions-review endpoint.

[linear]

BOU-285

[coderabbitai]

🔗 Related PRs

#430 - Submission page [merged]
#555 - feat(hackathons): add "hidden until results" submission visibility mode [merged]
#576 - fix(rewards): show track winners on the organizer rewards page [merged]
#582 - fix(rewards): match track winners by submissionId, not participantId [merged]
#586 - fix(submissions): unbreak submission detail page + publish hackathon recap [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!

[github-actions]

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