Vault: emit `withdraw`/`withdraw_to` events with documented payload shape

[greatest0fallt1me]

Description

Implement the change described by the title, ensuring it is audit-friendly and fully tested.

Requirements and context

• Must be secure, tested, and documented.
• Keep changes minimal and reviewer-friendly.

Suggested execution

• Fork the repo and create a branch: git checkout -b fix/vault-withdraw-event-shape
• Implement changes in the Callora-Contracts Soroban workspace (contracts/*/src/).
• Run cargo fmt, cargo clippy --all-targets --all-features -- -D warnings, and cargo test from the workspace root.
• For WASM release builds: cargo build --target wasm32-unknown-unknown --release -p callora-vault (adjust -p if the crate name differs).

Deliverables

• Update relevant lib.rs and test.rs.
• Update docs where applicable (README.md, EVENT_SCHEMA.md, SECURITY.md).

Test and commit

• Run tests and ./scripts/coverage.sh (or cargo tarpaulin per tarpaulin.toml).
• Cover edge cases; include summarized test output and brief security notes in the PR description.

Example commit message

chore(contracts): emit `withdraw`/`withdraw_to` events with documented payload shape

Guidelines

• Minimum 95% line coverage for touched crates (workspace policy).
• Clear documentation (Rust /// on public items where applicable; repo markdown as needed).
• Timeframe: 96 hours from assignment unless agreed otherwise.

[GEEKYFOCUS]

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

#246 Vault: emit withdraw/withdraw_to events with documented payload shape
Repo Avatar
CalloraOrg/Callora-Contracts
Description
Implement the change described by the title, ensuring it is audit-friendly and fully tested.

Requirements and context
Must be secure, tested, and documented.
Keep changes minimal and reviewer-friendly.
Suggested execution
Fork the repo and create a branch: git checkout -b fix/vault-withdraw-event-shape
Implement changes in the Callora-Contracts Soroban workspace (contracts/*/src/).
Run cargo fmt, cargo clippy --all-targets --all-features -- -D warnings, and cargo test from the workspace root.
For WASM release builds: cargo build --target wasm32-unknown-unknown --release -p callora-vault (adjust -p if the crate name differs).
Deliverables

Update relevant lib.rs and test.rs.
Update docs where applicable (README.md, EVENT_SCHEMA.md, SECURITY.md).
Test and commit
Run tests and ./scripts/coverage.sh (or cargo tarpaulin per tarpaulin.toml).
Cover edge cases; include summarized test output and brief security notes in the PR description.
Example commit message

chore(contracts): emit withdraw/withdraw_to events with documented payload shape
Guidelines
Minimum 95% line coverage for touched crates (workspace policy).
Clear documentation (Rust /// on public items where applicable; repo markdown as needed).
Timeframe: 96 hours from assignment unless agreed otherwise.

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

[drips-wave]

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

🧑‍💻 @GEEKYFOCUS: 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 @GEEKYFOCUS as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully addressed the issue by implementing the WithdrawEventData struct and updating the event emissions and documentation. The PR has been merged by a maintainer, and although the issue remains open, the work is complete and verified by the merge.

😎 @GEEKYFOCUS: 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.

🧑‍💻 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.