feat(bounty): wizard shell + step/draft machinery (#598)

[Benjtalkshow]

Closes #598. Part of the Bounty Configure (Host a Bounty) frontend epic (#603).

Targets feat/t-replace (not main) as requested. Stacked on #612 (#596 data layer) — until that merges this PR's diff also shows the #596 commit + the regenerated schema.d.ts.

What

Adds the bounty Configure wizard orchestrator and its step + draft state, mirroring the hackathon wizard. No AI assist.

• components/organization/bounties/new/constants.ts — StepKey (scope/mode/submission/reward/review), STEP_ORDER, BountyFormData, isBountyStepDataValid.
• hooks/use-bounty-steps.ts — URL ?step= navigation (free-roam) + presentational step-status map.
• hooks/use-bounty-draft.ts — lazy create (ensureDraftId) then per-section PATCH, resume via useDraft, and transformBountyFromApi (sections → form state; winnerCount derived from prize tiers, ISO dates trimmed for the datetime-local inputs).
• components/organization/bounties/new/NewBountyTab.tsx — orchestrator wiring steps + draft + per-step save, persisting ?draftId= for resume, and threading the chosen mode from ModeTab into SubmissionModelTab (the one cross-tab link those FE: ModeTab (two-axis picker) + SubmissionModelTab (mode-conditional fields) #599 components needed).

Acceptance criteria

• Navigates steps — useBountySteps (?step=, back/forward/bookmark safe).
• Autosaves sections — createSaveHandler → saveStep → PATCH, for the live ModeTab + SubmissionModelTab.
• Resumes a draft by id — useBountyDraft resume + onDraftLoaded rebuilds step statuses and the first-incomplete step.

tsc --noEmit: 0 errors; ESLint + Prettier clean; production build green (all enforced by the pre-commit hook).

Scope note (deviation from the issue task list)

The issue bundles the publish + funding-confirmation/progress modals + funding-source selection + USDC pre-flight check into #598, but those depend on the use-bounty-publish hook (#601) and the Scope/Reward/Review tabs (#600), neither built yet. Rather than ship speculative funding UI that can't compile against the real publish hook, I:

• Wired the two real tabs (Mode, Submission) end-to-end.
• Left marked placeholders for Scope/Reward/Review (TODO(#600)) and a disabled "Publish (coming in FE: use-bounty-publish (escrow publish via shared runner) #601)" + a working "Save draft" on the Review step (TODO(#601)).
• Kept every save/navigate/draftId seam in place, so FE: Scope + Reward + Review tabs and Zod schemas #600 drops in the three tabs (onSave={createSaveHandler(...)}) and FE: use-bounty-publish (escrow publish via shared runner) #601 drops in the publish hook + modals with minimal change.

This fully satisfies #598's acceptance criteria (navigate / autosave / resume) while keeping publish/funding in its natural home (#601).

[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: f62c5be7-6ba9-4d9d-be1f-d0036b0c63dc

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 and usage tips.}