feat(bounty): full config in settings + open single-claim submit-entry

[Benjtalkshow]

Summary

Two bounty changes.

1. Surface the full configuration in bounty settings

The organizer settings page hid the mode and several fields chosen at creation, which was confusing. This adds a read-only Configuration tab (its own tab, alongside General / Rewards / Timeline / Close-out) showing the bounty mode ("How do contributors enter?" and "How is the work claimed?") plus organizer resources. The off-chain country and GitHub issue URL become editable in the General tab. On-chain values stay read-only.

2. Open single-claim: submit-entry, first entry locks in

For OPEN + SINGLE_CLAIM there is no longer a separate claim step. The detail-page CTA reads Submit entry and goes straight to the entry form, where submitting runs the on-chain apply then submit as one action. The first valid entry locks the bounty to that builder; a second entrant is rejected. The submit gate admits a first entrant while nobody else holds the claim, and the form shows the lock-in and reputation notices.

Notes

• schema.d.ts carries a minimal, hand-applied addition of country, githubIssueUrl and resources to BountyPublicDto (a full codegen regen produced unrelated backend drift, so it was kept out).
• Pairs with the backend PR that exposes those fields and moves the reputation gate to submission time.

Testing

• Settings: open a bounty's settings, confirm the Configuration tab shows mode + resources, and that country / GitHub URL save from General.
• Submit-entry: on an OPEN + SINGLE_CLAIM bounty the CTA is "Submit entry"; submitting claims then submits in one flow. From a second account, submitting fails with "already claimed".

[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: b7a3acf6-4fc1-4eed-84e9-a2f286e15ebf

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.}