## Purpose

<!-- What does this PR change? Summarize in 1–2 sentences. -->

---

## Scope

Select one primary concern:

- [ ] Bug fix (behavior change)
- [ ] Refactor (no behavior change)
- [ ] Documentation update
- [ ] Formatting / code cleanup
- [ ] Dependency / build update
- [ ] New feature

> If this PR includes multiple unrelated concerns, please split it before requesting review.

---

## Description

### Problem
<!-- What issue does this solve? -->

### Solution
<!-- How does this change address the problem? -->

---

## Verification

<!-- How can reviewers verify this change? -->

Steps:
1.
2.
3.

Expected outcome:

---

## Screenshots / Recordings (if applicable)

<!-- Required for UI changes -->

---

## Commit Convention

We recommend using conventional commit prefixes:

- `fix:` – Bug fixes (behavior change)
- `feat:` – New features
- `refactor:` – Code changes without behavior change
- `docs:` – Documentation updates
- `chore:` – Maintenance, tooling, or dependency updates
- `test:` – Test additions or modifications

Clear commit messages make reviews easier and history more meaningful.

---

## Checklist

- [ ] The PR is focused on a single concern
- [ ] Commit messages follow the recommended convention
- [ ] Tests added or updated (if applicable)
- [ ] Documentation updated (if applicable)
- [ ] No unrelated cleanup included
- [ ] All tests pass