Add fuzz target for dispute_open with malformed inputs

[greatest0fallt1me]

Description

This is a smart-contract issue for the GrantFox campaign. This is a smart-contract issue for the GrantFox campaign. cargo-fuzz target for dispute_open boundary cases.

Requirements and Context

• Implement per the description
• Add focused tests for the change
• Document any API/visible changes
• Adhere to repo's lint and code style
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/fuzz-dispute-open

2. Implement changes
   • contracts/predictify-hybrid/fuzz/targets/dispute_open.rs (new)
3. Test and commit
   • Run the repo's standard test suite and lint
   • Cover edge cases; include output in the PR

Example commit message

test: fuzz dispute_open

Acceptance Criteria

• Implementation matches the description
• Tests added and passing
• Code review approved
• Docs updated

Guidelines

• Minimum 95% test coverage with cargo test
• require_auth on every state-changing entrypoint
• Overflow-safe math; no unwrap() in production paths
• Clear NatSpec-style /// rustdoc
• Timeframe: 96 hours

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.