feat(teachlink): add contract interface semantic versioning

[Tola-byte]

🚀 Pull Request

📋feat(teachlink): add contract interface semantic versioning

Implements contract interface semantic versioning and compatibility enforcement for TeachLinkBridge.
Adds on-chain version metadata (current + minimum_compatible), admin-controlled version updates, compatibility query/assert APIs, tests, and versioning policy documentation.

🔗 Related Issue(s)

• Closes No Versioning System #160

🎯 Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📚 Documentation update
• 🔧 Tooling/Infrastructure
• 🧪 Test improvements
• 🔒 Security fix
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvements

📝 Changes Made

• Added semantic interface version types and status model: ContractSemVer, InterfaceVersionStatus.
• Added interface versioning module with compatibility logic and admin update validation.
• Added new contract entry points:
  • get_interface_version_status
  • get_interface_version
  • get_min_compat_interface_version
  • set_interface_version
  • is_interface_compatible
  • assert_interface_compatible
• Added new bridge errors:
  • IncompatibleInterfaceVersion
  • InvalidInterfaceVersionRange
• Added storage keys:
  • INTERFACE_VERSION
  • MIN_COMPAT_INTERFACE_VERSION
• Added tests for default SemVer behavior, compatibility window checks, and invalid version range rejection.
• Added documentation:
  • docs/versions/CONTRACT_INTERFACE_VERSIONING.md
  • linked from docs/versions/README.md

🧪 Testing

✅ Pre-Merge Checklist (Required)

• 🧪 Unit Tests: I have run cargo test --lib and all tests pass
• 🔨 Debug Build: I have run cargo build and the project builds successfully
• 🎯 WASM Build: I have run cargo build --target wasm32-unknown-unknown --release and WASM builds successfully
• 📝 Code Formatting: I have run cargo fmt --all -- --check and code is properly formatted
• 🔍 Clippy Lints: I have run cargo clippy and there are no new warnings

🧪 Additional Testing (Recommended)

• 📚 Documentation: I have run cargo doc --no-deps and documentation builds without errors
• 🔒 Security Audit: I have run cargo audit and no critical vulnerabilities found
• 🖱️ Manual Testing: I have tested this change manually (if applicable)
• 📊 Performance: I have verified performance impact (if applicable)

📋 Test Results

cargo test -p teachlink-contract test_interface_versioning -- --nocapture

Compilation failed due to pre-existing unrelated errors in:
- contracts/teachlink/src/property_based_tests.rs
- contracts/teachlink/src/notification_tests.rs

Also fixed during this PR work:
- Soroban contract export name length constraint (max 32 chars) by using:
  get_min_compat_interface_version

cargo build --target wasm32-unknown-unknown --release
# Not run in this PR

🔍 Review Checklist

📝 Code Quality

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors

🧪 Testing Requirements

• I have added/updated tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Integration tests have been updated (if applicable)

📚 Documentation

• I have updated the documentation accordingly
• I have updated the CHANGELOG (if applicable)

🔒 Security

• I have not committed any secrets, keys, or sensitive data
• I have considered security implications of my changes
• My changes do not introduce known vulnerabilities

🏗️ Contract-Specific (if applicable)

• Storage changes are backward compatible (or migration plan provided)
• Event emissions are appropriate and documented
• Error handling is comprehensive
• Gas/resource usage has been considered

📸 Screenshots/Recordings

N/A

💥 Breaking Changes

• This PR introduces breaking changes

• What breaks: N/A

• Migration path: N/A

📊 Performance Impact

• CPU/Memory: Negligible (simple comparison checks).
• Gas costs: Minimal additional cost only when calling new version-check methods.
• Network: None.

🔒 Security Considerations

• Risks: Misconfigured compatibility window could reject valid clients.
• Mitigations: Admin update validation enforces sane bounds (min <= current, same major), and explicit compatibility checks are exposed on-chain.

📖 Additional Context

• Links: Branch codex/issue-160-interface-versioning, commit c924cdc
• Discussions: Added explicit SemVer policy for contract interface evolution.
• Examples: Compatibility requires same major and version within [minimum_compatible, current].

🚀 Deployment Notes

• Requires contract redeployment
• Requires data migration
• Requires configuration changes
• No deployment changes needed

📋 Reviewer Checklist

• 📝 Code review completed
• 🧪 Tests verified
• 📚 Documentation reviewed
• 🔒 Security considerations reviewed
• 🏗️ Architecture/design reviewed
• ✅ Approved for merge

---

🤖 CI Status

• 📝 Code Formatting: ✅/❌
• 🔍 Clippy Lints: ✅/❌
• 🧪 Unit Tests: ✅/❌
• 🔨 Debug Build: ✅/❌
• 🎯 WASM Release Build: ✅/❌
• 📚 Documentation: ✅/❌
• 🔒 Security Audit: ✅/⚠️

---

🎯 Ready for Review:

• Yes, all required checks pass and I'm ready for review
• No, I need to fix some issues first

---

Thank you for contributing to TeachLink! 🚀

[drips-wave]

@Tola-byte Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[ISTIFANUS-N]

@Tola-byte resolve conflicts.

[Tola-byte]

@ISTIFANUS-N please merge thanks.

[ISTIFANUS-N]

@Tola-byte resolve conflicts.

[Tola-byte]

bro 2 days ago, now I have to fix conflicts because you merged others in before mine. and I asked earlier.

[ISTIFANUS-N]

bro 2 days ago, now I have to fix conflicts because you merged others in before mine. and I asked earlier.

Chief I believe you saw PRs before yours. And it's only right I merge from the down.
I didn't do anything wrong here.

[Tola-byte]

alright thanks for your attention to this matter.

[Tola-byte]

@ISTIFANUS-N done boss, thanks.