Add a "no-op on already-paused" regression

[Baskarayelu]

Summary

pause() twice in a row must not duplicate emitted events.

Background

Test coverage in this area is currently thin: regressions can land without a failing build. Adding the cases below will lock the contract in place, document the expected behaviour through executable examples, and shorten review cycles when this code changes again.

Acceptance criteria

• The change matches the summary above.
• The new test fails on the current main before the fix (if this is a regression test) and passes after.
• Tests run on every CI matrix entry, not just the local default.
• Lint, type-check, and tests all pass locally.
• PR description references this issue with Closes #<this-issue>.

Implementation hints

• Pick the right test layer: unit tests inside the affected module for pure logic, integration tests under tests/ for cross-module behaviour.
• Cover the happy path and at least one explicit sad path; the title of this issue describes the boundary that needs to be locked in.
• Where the project uses proptest/fast-check/fc, prefer a property test over many hand-written cases. Commit any failing seed back to the repo.
• Keep test names assertive (returns_zero_when_balance_is_zero), not interrogative.
• New tests should be deterministic: no Date.now()/Math.random() without an injected fake.

Repo-specific notes

• This is a Soroban contract crate. Run cargo build --target wasm32-unknown-unknown --release to verify the change still builds for WASM.
• Run cargo test -p <package> for the affected crate, and cargo clippy --workspace --all-targets -- -D warnings before pushing.
• Keep #![no_std] discipline: do not introduce std:: calls; use soroban_sdk primitives.

Out of scope

• Unrelated refactors in adjacent files.
• Stylistic-only changes (formatting, renaming) that are not required by the fix.
• Anything beyond the acceptance criteria above; surface follow-ups as separate issues.

How to claim and submit

1. Comment on this issue saying you'd like to take it on; wait for a maintainer to assign you (avoids duplicated effort).
2. Open a PR that references this issue (Closes #<this-issue>).
3. Make sure CI is green and request review from a CODEOWNERS maintainer.
4. PRs that close this issue and pass review may qualify for a reward — see the MAYBE REWARDED label and the GrantFox OSS campaign page.

---

Category: test  ·  Campaign: GrantFox OSS · Official Campaign · Maybe Rewarded

[AugistineCreates]

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

I would like to work on this issue because i am confident i can resolve the issue, having worked on and resolved similar issues. my eta is 4 hours

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

[grantfox-oss]

🦊 GrantFox — @AugistineCreates 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 #1544)
2. Your PR will be reviewed by the QuickLendX maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @AugistineCreates: 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!

@AugistineCreates's PR #1675 was approved and merged by @Baskarayelu.

🏆 @AugistineCreates: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,831 total points). Track your full progress on GrantFox.

👏 Great work, @AugistineCreates! Keep contributing to QuickLendX.

[drips-wave]

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

😎 @AugistineCreates: You earned 100 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.