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

The gap in what exists

The gap is the existing bug itself, leading to broken data and client-side issues, which the bounty specifically funds to close.

Wedge to win

The wedge is to directly deliver the requested fix for the specified bounty amount, solving a direct data integrity problem.

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

Successfully completing a paid GitHub bounty, even for a niche project, provides concrete proof of coding ability and attention to detail for potential dev-tool or consulting clients.

Likely monetization

fixed-price bounty

You are an expert software engineer. The task is to fix a bug in a job creation and update schema. The current schema allows `budgetMax` to be less than `budgetMin`, creating invalid job records. You need to implement validation to reject these inverted budget ranges. The solution should be implemented within a GitHub repository, likely in a Node.js/TypeScript environment using a validation library like Joi or Zod if present. 

**Specific Requirements:**
1.  **Locate Schema:** Identify the `createJobSchema` (or similar) responsible for validating new job payloads. If the exact schema isn't immediately obvious, start by searching for keywords like 'job', 'budget', 'schema', 'validation' within the repository.
2.  **Implement Validation:** Add a custom validation rule or constraint to `createJobSchema` to ensure that `budgetMax` is strictly greater than or equal to `budgetMin` when both fields are provided.
3.  **Handle Updates:** Apply the same validation logic to any schema or handler for partial job updates. This validation should only trigger if *both* `budgetMin` and `budgetMax` are present in the update payload.
4.  **Preserve Existing:** Ensure that valid, already-ordered ranges in existing records continue to parse and are not inadvertently affected by the new validation logic (this is implicitly handled by focusing on creation/update validation).
5.  **Testing:** Propose unit tests using a common Node.js testing framework (e.g., Jest) to cover:
    *   Successful creation of jobs with valid budget ranges (`budgetMin <= budgetMax`).
    *   Rejection of job creation with inverted budget ranges (`budgetMax < budgetMin`).
    *   Successful partial update of jobs with valid budget ranges.
    *   Rejection of partial updates with inverted budget ranges when both budget fields are provided.
    *   Successful partial updates when only one budget field is provided (validation should not trigger for inversion).

**Deliverable:** A pull request to a forked repository that addresses the bug and includes relevant tests. Your proposed solution should use a stack compatible with Node.js and modern JavaScript/TypeScript practices.

**Build/Verify Gate:** The validation logic correctly prevents inverted budget ranges, and all new tests pass.