## Summary

- What changed and why.
- Keep this to 3-6 bullets focused on user-visible or architecture-impacting changes.

## Problem

- What issue or risk this PR addresses.
- Include context needed for reviewers to evaluate correctness quickly.

## Solution

- How the implementation solves the problem.
- Note important design decisions and tradeoffs.

## Testing

- [ ] `yarn -s compile`
- [ ] `cargo check --manifest-path src-tauri/Cargo.toml`
- [ ] Other checks run (list commands)
- [ ] Manual validation completed (list scenarios)

## Impact

- Runtime/platform impact (desktop/mobile/web/CLI), if any.
- Performance, security, migration, or compatibility implications.

## Breaking Changes

- [ ] None
- [ ] Yes (describe clearly, including migration steps)

## Related

- Issue(s):
- Follow-up PR(s)/TODOs: