# Pull Request

## Description

Brief description of the changes in this PR.

## 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
- [ ] 🔧 Refactoring (no functional changes)
- [ ] ⚡ Performance improvement
- [ ] 🧪 Test improvements
- [ ] 🔒 Security fix

## Changes Made

- [ ] Change 1
- [ ] Change 2
- [ ] Change 3

## Related Issues

Fixes #(issue_number) Closes #(issue_number) Related to #(issue_number)

## Testing

### Test Environment

- [ ] Local development environment
- [ ] WordPress version: [e.g. 6.4.2]
- [ ] Node.js version: [e.g. 18.17.0]
- [ ] Authentication method tested: [e.g. App Passwords, JWT]

### Tests Performed

- [ ] Unit tests pass (`npm test`)
- [ ] Health check passes (`npm run health`)
- [ ] TypeScript compilation (`npm run build`)
- [ ] Linting passes (`npm run lint`)
- [ ] Manual testing performed

### Test Cases

Describe the test cases you executed:

1. Test case 1
2. Test case 2
3. Test case 3

## Screenshots (if applicable)

Add screenshots to help explain your changes.

## Breaking Changes

If this is a breaking change, describe:

1. What breaks
2. How to migrate existing setups
3. Why this change was necessary

## Documentation

- [ ] Documentation updated (if needed)
- [ ] CLAUDE.md updated (if architecture changes)
- [ ] README updated (if user-facing changes)
- [ ] CHANGELOG.md updated

## Code Quality

- [ ] Code follows the project's style guidelines
- [ ] Self-review of code completed
- [ ] Code is well-commented, particularly complex areas
- [ ] No unnecessary console.log statements
- [ ] Error handling is appropriate
- [ ] Performance considerations addressed

## Security

- [ ] No sensitive information (credentials, tokens, etc.) committed
- [ ] Input validation added where appropriate
- [ ] Authorization checks implemented where needed
- [ ] Dependencies updated to secure versions

## Checklist

- [ ] My code follows the style guidelines of this project
- [ ] 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

## Additional Notes

Add any additional notes, considerations, or context for reviewers.
