Add view functions get_milestone_status and get_status for off-chain sync in accountability_vault

[1nonlypiece]

Add view functions get_milestone_status and get_status for off-chain sync in accountability_vault

Description

The backend src/services/eventParser.ts and vault sync rely on reconstructing state from events, but only get_vault exists for direct reads in contracts/accountability_vault/src/lib.rs. Add lightweight read-only get_status (returning VaultStatus) and get_milestone_status(index) (returning verified flag + due_date) so the backend can reconcile state cheaply. Cover both in contracts/accountability_vault/src/test.rs.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Add get_status and get_milestone_status to contracts/accountability_vault/src/lib.rs
• Return types friendly to scValToNative used in src/services/eventParser.ts
• Keep functions read-only (no require_auth)
• Add read-path tests in contracts/accountability_vault/src/test.rs

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/contract-view-functions
• Implement changes
  • Modify contracts/accountability_vault/src/lib.rs
  • Add tests in contracts/accountability_vault/src/test.rs
  • Document views in contracts/README.md
  • Add index bounds checks
• Test and commit
  • Run tests, cover edge cases
  • Include test output and notes

Example commit message

feat: add vault status and milestone view functions

Guidelines

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

[deep-bhikadiya]

@deep-bhikadiya has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I’ll add the read-only get_status and get_milestone_status(index) view functions with safe bounds checks, backend-friendly return types, tests for normal and edge cases, and README documentation. Please assign this to me so I can start working on it right away.

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

[drips-wave]

Congratulations, @deep-bhikadiya! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[deep-bhikadiya]

Hi @1nonlypiece , the PR for this issue has been merged successfully. Could you please close this issue? Thanks! 🙌