# Pull Request ## Description ## Type of Change - [ ] ๐Ÿ“ Documentation update - [ ] ๐Ÿงช Tests only - [ ] ๐Ÿ—๏ธ Scaffolding/stubs - [ ] โœจ New feature - [ ] ๐Ÿ› Bug fix - [ ] โ™ป๏ธ Refactoring - [ ] โš™๏ธ Infrastructure/CI - [ ] ๐Ÿ“ฆ Dependencies update - [ ] ๐Ÿ”’ Security fix - [ ] ๐Ÿ’ฅ Breaking change ## Checklist - [ ] Code follows the project's style guidelines - [ ] 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 ## Auto-Merge Eligibility **Eligible for auto-merge?** - [ ] Yes - This is a docs-only, tests-only, or small AI-generated PR - [ ] No - Requires human review **Reason for auto-merge eligibility:** - [ ] Docs-only (Tier 1) - [ ] Tests-only (Tier 2) - [ ] Scaffolding < 200 lines (Tier 3) - [ ] AI-generated < 500 lines (Tier 4) - [ ] Dependency patch/minor (Tier 5) **If not auto-merge eligible, why?** - [ ] Breaking change - [ ] Security-related - [ ] Infrastructure changes - [ ] Requires discussion - [ ] Large PR (> 500 lines) ## Related Issues Closes # Related to # ## Test Plan ## Screenshots (if applicable) --- **Note**: This PR will be automatically labeled based on files changed. See `GITHUB_AUTOMATION_RULES.md` for details. If this PR meets auto-merge criteria (see `AUTO_MERGE_POLICY.md`), it will be automatically approved and merged after checks pass. For questions about the merge queue system, see `MERGE_QUEUE_PLAN.md`.