## Description
**Brief description of changes**
Provide a clear and concise description of what this PR does.
**Related Issue(s)**
- Fixes #issue_number
- Closes #issue_number
- Related to #issue_number
## Type of Change
Please delete options that are not relevant.
- [ ] 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
- [ ] Code refactoring (no functional changes)
- [ ] Test improvements
- [ ] CI/CD improvements
- [ ] Dependency updates
## Changes Made
**Detailed description of changes:**
- Change 1: Description
- Change 2: Description
- Change 3: Description
**Files modified:**
- `file1.py`: Description of changes
- `file2.py`: Description of changes
- `README.md`: Updated documentation
## Testing
**Test Coverage:**
- [ ] Tests pass locally
- [ ] New tests added for new functionality
- [ ] Existing tests updated for changes
- [ ] Manual testing completed
- [ ] Integration tests pass
- [ ] Performance tests pass (if applicable)
**Testing Details:**
```bash
# Commands used for testing
pytest test_server.py -v
python server.py --test
```
**Test Results:**
```
# Paste test output here
```
**Manual Testing Scenarios:**
1. Scenario 1: Description and result
2. Scenario 2: Description and result
3. Scenario 3: Description and result
## Code Quality
**Code Quality Checks:**
- [ ] Code follows the project's style guidelines
- [ ] Self-review of code completed
- [ ] Code is commented, particularly in hard-to-understand areas
- [ ] No debugging code or console.log statements left
- [ ] Error handling is appropriate
- [ ] Performance considerations addressed
**Linting and Formatting:**
- [ ] Black formatting applied
- [ ] Flake8 linting passed
- [ ] MyPy type checking passed
- [ ] Import sorting (isort) applied
## Documentation
**Documentation Updates:**
- [ ] README updated (if needed)
- [ ] API documentation updated (if needed)
- [ ] Code comments added/updated
- [ ] Examples updated (if needed)
- [ ] CHANGELOG updated
**Documentation Changes:**
- Updated README section: ...
- Added new examples: ...
- Updated API docs: ...
## Breaking Changes
**Are there any breaking changes?**
- [ ] Yes (describe below)
- [ ] No
**If yes, describe the breaking changes:**
- Breaking change 1: Description and migration path
- Breaking change 2: Description and migration path
**Migration Guide:**
```python
# Before
old_code_example()
# After
new_code_example()
```
## Performance Impact
**Performance Considerations:**
- [ ] No performance impact
- [ ] Performance improvement
- [ ] Minor performance impact
- [ ] Significant performance impact (explain below)
**Performance Details:**
- Benchmark results: ...
- Memory usage: ...
- Execution time: ...
## Security Considerations
**Security Impact:**
- [ ] No security impact
- [ ] Security improvement
- [ ] Potential security considerations (explain below)
**Security Details:**
- Input validation: ...
- Authentication/Authorization: ...
- Data handling: ...
## Dependencies
**Dependency Changes:**
- [ ] No dependency changes
- [ ] Added new dependencies
- [ ] Updated existing dependencies
- [ ] Removed dependencies
**New Dependencies:**
- `package-name==version`: Reason for adding
**Updated Dependencies:**
- `package-name`: `old-version` → `new-version`: Reason for update
## Deployment
**Deployment Considerations:**
- [ ] No special deployment requirements
- [ ] Configuration changes required
- [ ] Database migrations required
- [ ] Environment variable changes
- [ ] Special deployment steps (describe below)
**Deployment Steps:**
1. Step 1: Description
2. Step 2: Description
3. Step 3: Description
## Checklist
**Before submitting this PR, please make sure:**
- [ ] I have read the [CONTRIBUTING](CONTRIBUTING.md) guidelines
- [ ] I have performed a self-review of my own 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
- [ ] I have checked my code and corrected any misspellings
- [ ] I have updated the CHANGELOG.md file
**Code Review:**
- [ ] I have requested review from appropriate team members
- [ ] I have addressed all review comments
- [ ] I have resolved all merge conflicts
## Screenshots/Examples
**Before:**
```
# Example of old behavior
```
**After:**
```
# Example of new behavior
```
**Screenshots:**
<!-- Add screenshots if applicable -->
## Additional Notes
**Additional context:**
Add any other context about the pull request here.
**Future Work:**
- Future improvement 1
- Future improvement 2
**Known Issues:**
- Known issue 1 (will be addressed in future PR)
- Known issue 2 (acceptable limitation)
## Reviewer Notes
**Areas of Focus:**
Please pay special attention to:
- Area 1: Specific concern or complexity
- Area 2: New functionality that needs careful review
- Area 3: Performance-critical code
**Questions for Reviewers:**
1. Question 1 about implementation approach
2. Question 2 about design decisions
3. Question 3 about testing strategy
