Add event emission for Escrow (ReleaseEvent)

[soomtochukwu]

Description

The implementation of 'Add event emission for Escrow (ReleaseEvent)' is a cornerstone of the Lance protocol's decentralization and reliability strategy.
This task directly impacts the core user journey by ensuring that the platform remains trustless and efficient at scale.
By completing this, we enable a more robust interaction between the client and freelancer layers of our marketplace.
Technical considerations for this task include strict adherence to security best practices and high-performance throughput.
This feature has been prioritized as part of our milestone to reach a production-ready beta for the Stellar ecosystem.

Requirements

1. Adhere to the architectural standards defined in the project's root documentation and style guides.
2. All data inputs must be sanitized and validated to prevent common Web3 attack vectors like reentrancy or overflows.
3. Ensure compatibility with the current versions of Soroban Rust SDK (for contracts) or Stellar SDK (for JS/TS).
4. Logic must be optimized to minimize on-chain footprint and backend latency, maintaining a highly responsive system.
5. Documentation for any new public functions or components must be provided in the /docs folder or internal wiki.

Acceptance Criteria

1. The feature must pass all existing and new unit tests with a coverage target of at least 90% for core logic.
2. Successful integration with the Backend API and Smart Contract storage must be verified in a Testnet environment.
3. The implementation must include comprehensive logging for all state-changing operations to assist in debugging.
4. Error states must be handled gracefully, providing clear and actionable feedback via standard Soroban error codes.
5. Peer review by at least one senior engineer is required to ensure long-term maintainability and code quality.

[Gozirimdev]

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

Hey Maintainer , I am a software developer and I will love to work on this issue

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

[drips-wave]

Congratulations, @Gozirimdev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Gozirimdev as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The PR has been open for over 6 days without any maintainer objections. It directly addresses the issue by implementing the requested ReleaseEvent in the escrow contract, providing corresponding unit tests and documentation as required by the acceptance criteria.

😎 @Gozirimdev: You earned 150 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.