[Backend] — Test: `DisputesService.create` allows second dispute after first is resolved

[Olowodarey]

Background

DisputesService.create checks for an existing dispute with
status: DisputeStatus.PENDING. If a previous dispute was resolved (status
changed to RESOLVED or REJECTED), a second dispute can be raised for the
same market. It's unclear if this is intentional. There are no tests for this
scenario.

Goal

Add tests clarifying the intended behavior and guard it.

Requirements

1. Determine the intended behavior by checking business rules: can a market
   receive only one dispute ever, or one active dispute at a time?

   • If one per market ever: change the check to where: { marketId } (no
     status filter).
   • If one active at a time: the current check is correct.

2. Regardless of the decision, add tests in

Acceptance criteria

• Policy is documented and tested.
• No silent second-dispute creation that contradicts the policy.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.
My PR will be submitted in under 10hours.

[anoncon]

@anoncon has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi
I’d like to work on this issue if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away

ℹ️ Repo Maintainers: To accept this application, review their application or assign @anoncon to this issue.

[grantfox-oss]

🦊 GrantFox — @anoncon has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1107)
2. Your PR will be reviewed by the Arena1X maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @anoncon! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @anoncon: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@anoncon's PR #1232 was approved and merged by @Olowodarey.

🏆 @anoncon: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (331 total points). Track your full progress on GrantFox.

👏 Great work, @anoncon! Keep contributing to Arena1X.

[drips-wave]

This issue has been completed by @anoncon as part of the Stellar Wave Program's 6th Wave 🥳

😎 @anoncon: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.