feat(bounty): wrap flow — results, announcement, archive (#635)

[Benjtalkshow]

What

Implements the FE Wrap step (#635) of the Bounty Operate to Payout milestone: after payout, publish results, announce winners, and close out.

Stacked on #674 (#634 cancel/refund). GitHub can't target a fork branch, so until #674 merges this PR shows its commit too; review the top commit feat(bounty): wrap flow …. It rebases cleanly once #674 lands.

Changes

Data layer

• features/bounties/api/organizer-wrap-client.ts (new) — typed apiClient calls: publishBountyResults, archiveBounty, restoreBounty, plus public reads getBountyResults and getBountyAnnouncement (nullable). Shapes aliased from the generated schema (backend Organization fixes #339).
• features/bounties/api/use-organizer-wrap.ts (new) — useBountyResults, useBountyAnnouncement, usePublishBountyResults, useArchiveBounty, useRestoreBounty. Mutations invalidate the announcement / overview / drafts keys.

Organizer dashboard

• BountyResultsPanel.tsx (new) — a Results tab (visible once completed): winners by tier with payout-tx links, plus a publish-announcement form (or the published message once sent).
• BountySettingsPanel.tsx — added an Archive / Restore card for completed/cancelled bounties (soft close, never a hard delete).
• BountyManagementDashboard.tsx — Results tab wired in.

Public

• BountyResults.tsx (new) + BountyDetail.tsx — a public results block on a completed bounty: announcement message + winners by tier with payout tx.

Acceptance criteria

• Results/winners view on the completed bounty (public + dashboard), consuming the results read.
• Publish a winners announcement (message) -> triggers winner + community notifications.
• Archive / restore a completed or cancelled bounty (never a hard delete).

Known gap (backend follow-up filed)

The operate overview DTO has no archivedAt, so the Settings archive card tracks archived/restored state locally for immediate feedback; it resets to "active" on reload. Reflecting true archive state across reloads needs a backend field — tracked in a boundless-nestjs follow-up issue.

Verification

• tsc --noEmit — 0 errors.
• eslint . — clean.

[vercel]

@Benjtalkshow is attempting to deploy a commit to the Threadflow Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5c71f1b2-d8f5-4813-b24a-d5334e114ae3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}