## Description
<!-- Provide a clear and concise description of your changes -->
## Related Issue
<!-- Link to the issue this PR addresses -->
Closes #
Fixes #
Related to #
## 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
- [ ] Code refactoring (no functional changes)
- [ ] Performance improvement
- [ ] Test updates
- [ ] Build/CI changes
- [ ] Security fix
## Changes Made
<!-- List the specific changes made in this PR -->
-
-
-
## Testing
<!-- Describe the testing you've performed -->
### Test Coverage
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] All existing tests pass
### Test Details
```bash
# Commands used for testing
npm test
npm run lint
npm run typecheck
```
**Test results**:
## Breaking Changes
<!-- If this is a breaking change, describe the impact and migration path -->
**Does this PR introduce breaking changes?** No / Yes
If yes:
- **What breaks**:
- **Migration guide**:
- **Deprecation notice needed**: Yes / No
## Documentation
<!-- Have you updated the documentation? -->
- [ ] README.md updated (if needed)
- [ ] API documentation updated (if needed)
- [ ] Code comments added/updated
- [ ] CHANGELOG.md updated
- [ ] Migration guide added (if breaking change)
## Security Considerations
<!-- Answer these security questions -->
- [ ] No new dependencies added
- [ ] New dependencies have been audited for vulnerabilities
- [ ] No secrets or credentials in code
- [ ] Input validation added where needed
- [ ] No new security warnings from linters/scanners
## Performance Impact
<!-- Describe any performance implications -->
- [ ] No significant performance impact
- [ ] Performance improvement (describe below)
- [ ] Performance regression (describe below and justify)
**Details**:
## Screenshots
<!-- If applicable, add screenshots to demonstrate the changes -->
## Checklist
<!-- Ensure all items are completed before requesting review -->
### Code Quality
- [ ] Code follows the project's style guidelines
- [ ] Self-review of code completed
- [ ] Code is commented, particularly in hard-to-understand areas
- [ ] No console.log or debug statements left in production code
- [ ] TypeScript types are properly defined (no `any` unless justified)
### Testing
- [ ] All new and existing tests pass locally
- [ ] Test coverage maintained or improved
- [ ] Edge cases considered and tested
### Documentation
- [ ] Documentation has been updated where needed
- [ ] Changes are described in the PR description
- [ ] Commit messages follow conventional commits format
### Review
- [ ] PR is ready for review
- [ ] PR is small and focused (if not, explain why)
- [ ] Reviewers assigned
- [ ] Labels added
## Additional Notes
<!-- Any additional information for reviewers -->
## Reviewer Checklist
<!-- For reviewers to complete -->
- [ ] Code review completed
- [ ] Tests reviewed and adequate
- [ ] Documentation reviewed
- [ ] Security implications considered
- [ ] Performance implications considered
- [ ] Breaking changes noted and acceptable
---
<!-- Thank you for your contribution! -->
