feat: implement event status updates and deadline extensions

[ussyalfaks]

Pull Request Description

📋 Basic Information

Type of Change

Please select the type of change this PR introduces:

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🧪 Test addition/update
• 🔧 Refactoring (no functional changes)
• ⚡ Performance improvement
• 🔒 Security fix
• 🎨 UI/UX improvement
• 🚀 Deployment/Infrastructure change

Related Issues

Closes #222

Priority Level

• 🔴 Critical (blocking other development)
• 🟡 High (significant impact)
• 🟢 Medium (moderate impact)
• 🔵 Low (minor improvement)

---

📝 Detailed Description

What does this PR do?

This PR introduces comprehensive event status management capabilities that enable administrators to safely modify event details, extend deadlines, and update event parameters while maintaining data integrity and preventing conflicts with active betting. Implements the following admin functions:

• Deadline Extension: Extend event end times to accommodate delays
• Event Metadata Updates: Update event descriptions and outcomes before betting commences
• Parameter Modification: Modify event parameters with strict validation guards
• Secure Access Control: Admin-only operations with role-based validation

Why is this change needed?

Event administrators need the ability to make critical adjustments to events during their lifecycle—such as extending deadlines due to external circumstances or correcting event details before trading begins. This requires careful validation to prevent modifications that would compromise existing bets or system integrity.

How was this tested?

• Unit tests for all core functions (extend_deadline, update_event)
• Integration tests validating admin-only access enforcement
• Edge case testing: bet placement detection, event resolution locks, concurrent updates
• Security validation: admin authorization, bet integrity preservation
• All tests passing locally with full coverage

Alternative Solutions Considered

• Single monolithic update function: Rejected in favor of granular functions for better control and security
• Post-bet updates with compensation: Rejected to maintain bet immutability and system consistency

---

🏗️ Smart Contract Specific

Contract Changes

Please check all that apply:

• Core contract logic modified
• Oracle integration changes (Pyth/Reflector)
• New functions added
• Existing functions modified
• Storage structure changes
• Events added/modified
• Error handling improved
• Gas optimization
• Access control changes
• Admin functions modified
• Fee structure changes

Oracle Integration

• Pyth oracle integration affected
• Reflector oracle integration affected
• Oracle configuration changes
• Price feed handling modified
• Oracle fallback mechanisms
• Price validation logic

Market Resolution Logic

• Hybrid resolution algorithm changed
• Dispute mechanism modified
• Fee structure updated
• Voting mechanism changes
• Community weight calculation
• Oracle weight calculation

Security Considerations

• Access control reviewed
• Reentrancy protection
• Input validation
• Overflow/underflow protection
• Oracle manipulation protection

Security Details:

• Admin-only access enforced at contract level
• Bet detection prevents retroactive event changes
• Event resolution locks prevent modification of finalized events
• Immutable bet constraints ensure user fund safety
• Input validation on all update parameters

---

🧪 Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• All tests passing locally
• Manual testing completed
• Oracle integration tested
• Edge cases covered
• Error conditions tested
• Gas usage optimized
• Cross-contract interactions tested

Test Results

# Test Output:
cargo test

test result: ok. 16 passed; 0 failed.

Manual Testing Steps

1. Deploy contract with admin account
2. Create test event and verify admin can extend deadline
3. Create event with bets placed, verify description update is rejected
4. Attempt unauthorized updates from non-admin account, verify rejection
5. Resolve event and verify all modifications are blocked
6. Verify event update events are properly emitted

---

📚 Documentation

Documentation Updates

• README updated
• Code comments added/updated
• API documentation updated
• Examples updated
• Deployment instructions updated
• Contributing guidelines updated
• Architecture documentation updated

Documentation Added:

• NatSpec-style comments on all public functions
• Inline comments explaining validation logic
• Contract API guide with usage examples
• Architecture documentation on event lifecycle

Breaking Changes

Breaking Changes: None

Migration Guide: Not applicable

---

🔍 Code Quality

Code Review Checklist

• Code follows Rust/Soroban best practices
• Self-review completed
• No unnecessary code duplication
• Error handling is appropriate
• Logging/monitoring added where needed
• Security considerations addressed
• Performance implications considered
• Code is readable and well-commented
• Variable names are descriptive
• Functions are focused and small

Performance Impact

• Gas Usage: Minimal impact; validation checks are O(1) operations
• Storage Impact: New EventUpdate struct adds ~256 bytes per update
• Computational Complexity: O(1) for all operations

Security Review

• No obvious security vulnerabilities
• Access controls properly implemented
• Input validation in place
• Oracle data properly validated (N/A)
• No sensitive data exposed

---

🚀 Deployment & Integration

Deployment Notes

• Network: Testnet/Mainnet compatible
• Contract Address: (to be determined at deployment)
• Migration Required: No
• Special Instructions: Ensure admin accounts are properly configured before deployment

Integration Points

• Frontend integration considered
• API changes documented
• Backward compatibility maintained
• Third-party integrations updated

---

📊 Impact Assessment

User Impact

• End Users: Can now participate in events with extended deadlines and corrected details
• Developers: New event management API endpoints available
• Admins: Enhanced control over event lifecycle with safe modification capabilities

Business Impact

• Revenue: Positive; allows flexibility in event management without disrupting betting
• User Experience: Improved; admins can fix errors and extend events as needed
• Technical Debt: Reduced; proper separation of concerns with dedicated event management module

---

✅ Final Checklist

Pre-Submission

• Code follows Rust/Soroban best practices
• All CI checks passing
• No breaking changes (or breaking changes are documented)
• Ready for review
• PR description is complete and accurate
• All required sections filled out
• Test results included
• Documentation updated

Review Readiness

• Self-review completed
• Code is clean and well-formatted
• Commit messages are clear and descriptive
• Branch is up to date with main
• No merge conflicts

---

💬 Notes for Reviewers

Please pay special attention to:

• Security of admin access control implementation
• Bet detection logic to prevent retroactive changes
• Event resolution lock mechanism

Questions for reviewers:

• Does the validation logic cover all edge cases?
• Are the error messages clear and helpful?
• Should we add gas cost metrics for the new functions?

---

Thank you for your contribution to Predictify! 🚀

[greatest0fallt1me]

@ussyalfaks Please fix the pipeline