Add admin_override_verification audit-trail entry and event with mandatory reason String

[greatest0fallt1me]

Description

admin_override_verification in lib.rs lets an admin override an oracle-verified result, which is among the most trust-sensitive actions in the contract. Each override must require a non-empty justification, append an immutable audit-trail record, and emit an event so off-chain monitors can flag it. This closes a key oracle-manipulation accountability gap.

Requirements and Context

• Require a non-empty reason: String parameter on the override entrypoint in contracts/predictify-hybrid/src/lib.rs.
• Append an AuditRecord via the existing audit_trail module and verify chain integrity.
• Emit a dedicated override event with admin, market id, old/new result, and reason.
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b feature/override-audit-trail

2. Implement changes
   • contracts/predictify-hybrid/src/lib.rs — admin_override_verification
   • contracts/predictify-hybrid/src/audit_trail.rs, contracts/predictify-hybrid/src/events.rs
3. Test and commit
   • cargo test -p predictify-hybrid -- override audit
   • Cover edge cases: empty reason rejected, audit integrity preserved after override
   • Include test output and notes in the PR

Example commit message

feat: require reason and audit trail for verification override

Acceptance Criteria

• Override rejects an empty reason
• An immutable audit record and event are produced per override
• verify_audit_integrity still passes after overrides

Guidelines

• Minimum 95% coverage on touched code, validate auth and audit-trail integrity
• Clear documentation and inline comments
• Timeframe: 96 hours

[Vvictor-commits]

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

please assign this issue to me

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

[drips-wave]

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

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