# Pull Request
## Description
<!-- Provide a brief description of the changes in this PR -->
## Type of Change
<!-- Mark the relevant option with an "x" -->
- [ ] 🐛 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
- [ ] 🔧 Maintenance (dependency updates, CI improvements, etc.)
- [ ] ♻️ Code refactoring (no functional changes)
- [ ] 🧪 Test improvements
## Related Issues
<!-- Link to related issues using keywords like "Fixes #123" or "Relates to #456" -->
- Fixes #
- Relates to #
## Changes Made
<!-- List the main changes made in this PR -->
-
-
-
## Testing
<!-- Describe the tests you ran and how to reproduce them -->
- [ ] All existing tests pass
- [ ] New tests added for new functionality
- [ ] Manual testing performed
- [ ] Integration tests pass
### Test Details
<!-- Provide specific testing details -->
```bash
# Commands used to test
uv run pytest
uv run ruff check .
uv run pyright
```
## Documentation
<!-- Mark relevant options -->
- [ ] Code is self-documenting with clear variable/function names
- [ ] Docstrings added/updated for new functions and classes
- [ ] README updated if needed
- [ ] CHANGELOG updated (if applicable)
## Breaking Changes
<!-- If this is a breaking change, describe what breaks and how to migrate -->
- None
## Performance Impact
<!-- Describe any performance implications -->
- [ ] No performance impact
- [ ] Performance improvement
- [ ] Potential performance regression (explain below)
## Security Considerations
<!-- Any security implications -->
- [ ] No security implications
- [ ] Security improvement
- [ ] Potential security concerns (explain below)
## Deployment Notes
<!-- Any special considerations for deployment -->
- None
## Screenshots/Videos
<!-- If applicable, add screenshots or videos -->
## Checklist
<!-- Mark completed items with an "x" -->
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged and published
## Additional Notes
<!-- Any additional information that reviewers should know -->
---
**For Maintainers:**
- [ ] Labels applied
- [ ] Milestone assigned (if applicable)
- [ ] Breaking changes noted in PR title with `!`
