## Summary

Brief description of what this PR does.

Closes #(issue number)

## Changes

- [ ] Feature A
- [ ] Fix B
- [ ] Refactor C

## Type of Change

- [ ] 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
- [ ] Performance improvement
- [ ] Refactoring (no functional changes)

## Testing

- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manual testing performed

Describe the tests you ran:

## Checklist

- [ ] Code compiles without warnings on GCC and Clang
- [ ] Tests pass (`ctest --output-on-failure`, `pytest`)
- [ ] Benchmarks run if performance-related
- [ ] CHANGELOG updated for user-facing changes
- [ ] Documentation updated (README, headers, guides)
- [ ] PR title follows conventional commit style (`feat:`, `fix:`, `docs:`, etc.)

## Additional Notes

Any other notes for reviewers:

- Design decisions
- Trade-offs
- Migration steps (if breaking change)
