Short, imperative summary (e.g., chore: update Copilot guide and PR template)
Fixes issue #
Note: GitHub auto-closes the linked issue on merge when using closing keywords like "Fixes #123" or "Fixed #123".
What does this change do and why?
- Bullet the key changes
- Keep it concise
If UI/visual changes, add before/after or a brief clip.
- Includes a proper closing reference (e.g., Fixes #)
- Lint passes (npm run lint)
- Tests added/updated and pass (npm test)
- Build succeeds (npm run build)
- Docs updated as needed (README/COPILOT.md)
- No breaking changes, or breaking changes documented