SecureBananaLabs/bug-bounty: Reject inverted job budget ranges in job validation

The gap in what exists

The gap is the existing bug itself, which the bounty specifically funds to close, indicating a clear, unfulfilled need for this specific fix.

Wedge to win

The wedge is direct fulfillment of a paid bounty, which is funded work for the client. The operator would be directly solving a problem the client has already prioritized and allocated budget for.

Reputation value (worth doing free for proof) — 70/100

Successfully completing a paid bug bounty on a public GitHub repository demonstrates a developer's ability to diagnose and fix real-world issues, building credibility for future client work.

Likely monetization

bounty payment

You are an expert full-stack developer. Your task is to implement a bug fix for the `SecureBananaLabs/bug-bounty` GitHub repository, specifically addressing issue #2827. The core problem is that `createJobSchema` and potentially job update schemas accept inverted budget ranges (e.g., `budgetMax` < `budgetMin`).

Your goal is to add validation to reject such payloads. Use Next.js 16 App Router, React 19, Tailwind v4, and Node.js for any backend logic if applicable, but focus primarily on the existing validation framework within the target repository. Assume the validation framework is a common one like Joi, Yup, or Zod.

Here's the plan:
1.  **Understand the existing validation:** Identify where `createJobSchema` and any partial job update schemas are defined and what validation library they use.
2.  **Implement validation logic:** Add a custom validation rule or a `when` clause that checks if both `budgetMin` and `budgetMax` are present. If so, ensure `budgetMax` is greater than or equal to `budgetMin`. If `budgetMax` is less than `budgetMin`, the validation should fail.
3.  **Ensure existing valid ranges parse:** Verify that already correctly ordered ranges continue to pass validation.
4.  **Create tests:** Write new unit tests for the validation logic. Include tests for:
    *   Valid range (e.g., 100-500)
    *   Equal min/max (e.g., 500-500)
    *   Invalid inverted range (e.g., 500-100)
    *   Cases where only `budgetMin` or `budgetMax` is present (should pass if the other is absent).

**MVP Slice:** Focus first on identifying `createJobSchema` and adding the basic `budgetMax >= budgetMin` validation rule, along with a simple failing test for an inverted range and a passing test for a valid range. This confirms you've targeted the correct schema and logic point.

**Build/Verify Gate:** The solution is complete when the validation rejects inverted budget ranges during job creation and updates, and all existing and new tests pass.