<!-- The PR title should follow [conventional commits](https://www.conventionalcommits.org/en/). -->
<!-- Mostly, commit prefix should be one of: fix, feat, chore, ci, docs and refactor. Unless it's a special PR. -->
# Type of Change
<!-- Please check 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)
- [ ] Refactoring (no functional changes, code improvements)
- [ ] Performance improvements
- [ ] Tests (adding or modifying tests)
- [ ] Documentation update
- [ ] Build system update
- [ ] Governance (CI, style spec, etc.)

# Why we need this PR
<!-- Describe the purpose of this PR. What problem does it solve? What feature does it add? -->

# Summary of Changes
<!-- List the main changes in this PR -->

# How Has This Been Tested?
<!-- Describe the tests you ran to verify your changes -->

# Checklist
- [ ] All tests pass locally (`cargo test`)
- [ ] Examples compile and run correctly
- [ ] No new warnings introduced
- [ ] Tests (if applicable) are added / updated to prove my change works
- [ ] Docs (if applicable) are updated
- [ ] CHANGELOG.md (if applicable) is updated

# Additional Notes
<!-- Any additional information that reviewers should be aware of -->
<!-- For example: dependencies, performance impact, known limitations, etc. -->
