# 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 (changes to documentation only)
- [ ] 🔧 Refactoring (code changes that neither fix a bug nor add a feature)
- [ ] ⚡ Performance improvement
- [ ] 🧪 Test improvements
- [ ] 🔒 Security improvement

## Related Issues

<!-- Link to related issues using "Fixes #123", "Closes #123", or "Relates to #123" -->

- Fixes #
- Relates to #

## Changes Made

<!-- Provide a detailed list of changes made -->

-
-
-

## Testing

<!-- Describe the testing you've performed -->

### Test Coverage

- [ ] Tests pass locally (`make test`)
- [ ] All quality checks pass (`make check`)
- [ ] Integration tests pass (`make test-with-zim-data`)
- [ ] New tests added for new functionality
- [ ] Existing tests updated for changed functionality

### Manual Testing

<!-- Describe any manual testing performed -->

- [ ] Tested with real ZIM files
- [ ] Tested error conditions
- [ ] Tested edge cases
- [ ] Verified backward compatibility

## Security Considerations

<!-- Address any security implications -->

- [ ] No new security vulnerabilities introduced
- [ ] Input validation added/updated where needed
- [ ] Path traversal protection maintained
- [ ] Error messages don't leak sensitive information
- [ ] Dependencies are secure and up-to-date

## Performance Impact

<!-- Describe any performance implications -->

- [ ] No performance regression
- [ ] Performance improvements included
- [ ] Memory usage considered
- [ ] Caching behavior verified

## Documentation

<!-- Ensure documentation is updated -->

- [ ] Code is self-documenting with clear variable/function names
- [ ] Docstrings added/updated for new/changed functions
- [ ] README.md updated (if user-facing changes)
- [ ] CHANGELOG.md updated (if notable change)
- [ ] API documentation updated (if API changes)

## Backward Compatibility

<!-- Address compatibility concerns -->

- [ ] No breaking changes
- [ ] Breaking changes documented and justified
- [ ] Migration guide provided (if breaking changes)
- [ ] Deprecation warnings added (if applicable)

## Checklist

<!-- Final verification before submission -->

- [ ] 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

## Screenshots/Examples

<!-- If applicable, add screenshots or code examples -->

```python
# Example usage of new feature
```

## Additional Notes

<!-- Any additional information for reviewers -->

## Reviewer Guidelines

<!-- For reviewers -->

Please review:

1. **Code Quality**: Is the code clean, readable, and well-structured?
2. **Testing**: Are there adequate tests for the changes?
3. **Security**: Are there any security implications?
4. **Performance**: Any performance impact?
5. **Documentation**: Is documentation updated appropriately?
6. **Backward Compatibility**: Are breaking changes justified and documented?

---

Thank you for your contribution! 🎉
