Clarify and test cancel_bid versus withdraw_bid semantics

[Baskarayelu]

Description

Document and test differences between cancel and withdraw paths, status transitions, and events.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Align with existing Soroban contract patterns in quicklendx-contracts

Suggested execution

• Fork the repo and create a branch
• git checkout -b feature/cancel-vs-withdraw-bid
• Implement changes
• Write contract: src/bid.rs, src/lib.rs
• Write comprehensive tests: src/test_bid.rs
• Add documentation: docs/contracts/bidding.md
• Include NatSpec-style comments (Rust doc comments on public items)
• Validate security assumptions

Test and commit

• Run tests
• Cover edge cases
• Include test output and security notes

Example commit message

feat: document cancel_bid versus withdraw_bid

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[EmmyKay0026]

@EmmyKay0026 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi there, I’m interested in taking this on! Clearly distinguishing between cancel_bid and withdraw_bid is vital for both security and user clarity, especially when handling locked collateral and state transitions in a lending protocol.

I’ll focus on ensuring the state machine for bids is bulletproof—verifying that cancel is only available in pre-acceptance states while "withdraw" correctly handles post-expiry or rejected scenarios. I'll also aim for that 95% test coverage mark by targeting edge cases like partial fills and unauthorized access. Should I implement specific custom events for each path to make off-chain tracking easier for the frontend?

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

[drips-wave]

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

🧑‍💻 @EmmyKay0026: 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 🌊