refactor: rename product brand to Wisper

[hudsonbrendon]

What

Rebrand the user-facing product from OpenWispr to Wisper (domain wisper.chat).

Replaces the brand string across:

• UI components + i18n (all languages)
• User-facing Rust strings (permission prompts, etc.)
• productName, README, landing site, npm package name

The competitor mention "Wispr Flow" is left untouched (word-boundary replace).

Intentionally preserved (don't break existing installs)

• Bundle identifier com.hudsonbrendon.openwispr → keeps macOS TCC (Mic/Accessibility) grants and the per-user data dir.
• GitHub repo / OTA URL → keeps auto-update continuity.
• Rust crate / binary name → internal, no user impact.

Test

• vitest: 201/201 pass.
• cargo check: clean.
• pnpm tauri build → builds Wisper.app; reinstalled and launched, TCC grants carried over.

Follow-ups (separate, heavier)

Renaming the bundle id + GitHub repo and pointing the landing site at wisper.chat break TCC/OTA continuity and are out of scope here.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@hudsonbrendon, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 54 minutes and 3 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0054cf51-a2d3-424a-9239-a711227a0b67

📥 Commits

Reviewing files that changed from the base of the PR and between 69d42f8 and 3212022.

📒 Files selected for processing (14)

• README.md
• package.json
• site/index.html
• src-tauri/src/commands.rs
• src-tauri/src/config.rs
• src-tauri/src/inject.rs
• src-tauri/src/text.rs
• src-tauri/src/uitext.rs
• src-tauri/tauri.conf.json
• src/components/Sidebar.test.tsx
• src/components/Sidebar.tsx
• src/lib/i18n.tsx
• src/routes/Dashboard.test.tsx
• src/routes/Dictionary.test.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rename/wisper

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}