## Description

<!-- What does this PR do? Why is it needed? -->

Closes #<!-- issue number -->

## 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
- [ ] Refactor (no functional changes)
- [ ] Dependency update
- [ ] CI/CD changes

## Testing

<!-- How was this tested? What scenarios were covered? -->

- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] Accessibility tested (if UI changes)
- [ ] Tested in staging environment
- [ ] All tests pass locally (`pnpm test`)

**Test coverage:** <!-- e.g., "Added 5 unit tests, 2 integration tests" -->

## Checklist

- [ ] Code follows conventional commit format
- [ ] Self-review completed (read own diff on GitHub)
- [ ] No TypeScript errors (`pnpm typecheck`)
- [ ] No ESLint warnings (`pnpm lint`)
- [ ] Documentation updated (if applicable)
- [ ] Database schema updated (if schema changed)
- [ ] Breaking changes documented below (if applicable)
- [ ] CI checks pass
- [ ] No secrets or credentials in code

## Breaking Changes

<!-- If this is a breaking change, describe:
1. What breaks?
2. How should users migrate?
3. Link to migration guide (if exists)
-->

**None** / <!-- Describe breaking changes here -->

## Screenshots/Logs (if applicable)

<!-- Add screenshots for UI changes, or logs for backend changes -->

## Additional Context

<!-- Any other information reviewers should know -->

## Reviewer Checklist

<!-- For reviewers - don't fill this out yourself -->

- [ ] Code quality meets standards
- [ ] Tests are meaningful and cover edge cases
- [ ] Security considerations addressed
- [ ] Performance impact acceptable
- [ ] Accessibility compliant (if UI)
- [ ] Documentation clear and complete