## Description

<!-- Provide a clear and concise description of what this PR does -->

### What Changed
<!-- Describe the changes made in this PR -->

### Why
<!-- Explain the motivation and context for these changes -->

### Related Issues
<!-- Link to related issues (e.g., Fixes #123, Relates to #456) -->

---

## Documentation Checklist

**REQUIRED: All PRs must include documentation updates.**

- [ ] **Code changes have corresponding documentation updates**
- [ ] **README updated** (if user-facing changes)
- [ ] **API docs updated** (if endpoints/interfaces changed)
- [ ] **Architecture docs updated** (if design patterns changed)
- [ ] **CHANGELOG updated** (if maintained in this project)
- [ ] **Comments/docstrings added** (for complex or non-obvious logic)
- [ ] **No documentation needed** (explain why below)

**If "No documentation needed" is checked, explain:**
<!-- Why don't these changes require documentation? -->

---

## PR Quality Checklist

- [ ] **PR title follows semantic format** (`feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`)
- [ ] **PR description explains "what" and "why"** (not just "what")
- [ ] **Breaking changes clearly documented** (if applicable)
- [ ] **Screenshots/videos included** (for UI changes)
- [ ] **Tests added/updated** (for code changes)
- [ ] **All tests passing** (`pytest tests/ -v`)
- [ ] **Code quality checks passing** (`ruff check --fix && ruff format && mypy src/`)

---

## Breaking Changes

<!-- If this PR introduces breaking changes, describe them here -->
<!-- Include migration guide if applicable -->

---

## Testing

<!-- Describe how you tested these changes -->

**Test commands run:**
```bash
# Example:
# pytest tests/ -v
# pytest tests/ --cov=src
```

**Manual testing performed:**
<!-- Describe any manual testing done -->

---

## Screenshots/Videos

<!-- For UI changes, include before/after screenshots or demo videos -->

---

## Additional Context

<!-- Any other context, concerns, or notes for reviewers -->

---

## Reviewer Guidance

**Documentation review:**
- [ ] Verify documentation checklist is complete and accurate
- [ ] Check that docs match code changes
- [ ] Ensure docstrings are clear and accurate
- [ ] Verify README/API docs updated if needed

**Code review:**
- [ ] Code follows engineering standards
- [ ] Tests are comprehensive
- [ ] No obvious bugs or security issues
- [ ] Breaking changes are properly documented
