## π Pull Request Summary
### Type of Change
<!-- Please select the type of change this PR introduces -->
- [ ] π 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)
- [ ] π§ Configuration/tooling update (changes to build process, CI/CD, etc.)
- [ ] β»οΈ Code refactoring (no functional changes, no API changes)
- [ ] π¨ Style/formatting changes (code formatting, missing semicolons, etc.)
- [ ] β‘ Performance improvement
- [ ] π§ͺ Test improvements
- [ ] π Security enhancement
### Description
<!-- Provide a clear and concise description of what this PR does -->
### Related Issues
<!-- Link to related issues using keywords like "Fixes #123" or "Closes #456" -->
- Fixes #
- Related to #
### Changes Made
<!-- List the main changes made in this PR -->
-
-
-
### Testing
<!-- Describe how you tested your changes -->
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] Tested in documentation-only mode
- [ ] Tested in full mode (with SFCC credentials)
- [ ] All existing tests pass
### Test Coverage
<!-- Describe what testing was done -->
### Breaking Changes
<!-- If this is a breaking change, describe what breaks and how to migrate -->
### Documentation
<!-- Check all that apply -->
- [ ] README.md updated (if user-facing changes)
- [ ] copilot-instructions.md updated (if architectural changes)
- [ ] API documentation updated
- [ ] Agent skills updated (ai-instructions/skills)
- [ ] Code comments added/updated
- [ ] No documentation changes needed
### Performance Impact
<!-- Describe any performance implications -->
- [ ] No performance impact
- [ ] Performance improvement
- [ ] Minor performance impact (acceptable)
- [ ] Significant performance impact (needs discussion)
### Security Considerations
<!-- Describe any security implications -->
- [ ] No security impact
- [ ] Security improvement
- [ ] Reviewed for security implications
- [ ] No new external dependencies
- [ ] New dependencies reviewed for security
### Checklist
<!-- Ensure all items are checked before requesting review -->
- [ ] Code follows the project's style guidelines
- [ ] Self-review of the code has been performed
- [ ] Code is well-commented, particularly in hard-to-understand areas
- [ ] Changes generate no new warnings or errors
- [ ] Any dependent changes have been merged and published
- [ ] Version numbers updated (if applicable)
- [ ] Changelog updated (if applicable)
### Reviewer Notes
<!-- Any specific areas you'd like reviewers to focus on -->
### Screenshots/Examples
<!-- If applicable, add screenshots or code examples -->
---
### For Maintainers
<!-- This section is for maintainers to fill out during review -->
#### Review Checklist
- [ ] Code quality and style
- [ ] Test coverage adequate
- [ ] Documentation updated appropriately
- [ ] Security implications reviewed
- [ ] Performance impact acceptable
- [ ] Breaking changes properly documented
- [ ] Version bump needed
- [ ] Release notes needed