v0.6.7: profile pictures on notifications; Windows freeze fixes (from #26)

[karem505]

This is the v0.6.7 release. Notes are in docs/release-notes/v0.6.7.md.

Profile pictures on notifications (suggested in #3)

• bridge.js: takes the icon WhatsApp passes to new Notification() or registration.showNotification(). Only blob:, data: and https: URLs are fetched, without credentials. The image is cropped to a centre square, scaled to 96px and re-encoded as PNG, because Windows toasts can't show WebP. The bridge waits at most 1.5s for it; if the picture can't be loaded in time, the toast goes out without it.

• notify command: takes an optional icon (base64 PNG).

• New notif_icon.rs:

  • decodes the base64 itself, so there's no new crate and the Flatpak sources are unchanged;
  • accepts only a PNG of up to 256 KB;
  • writes it under the app cache dir with a content-hash name and deletes files older than a day.

  It writes only after the lock, the Notifications setting and de-duplication have passed.

• Display: on Windows it's Toast::icon(path, IconCrop::Circular); on Linux the plugin's .icon(path). macOS always shows the app icon.

• Logging: the log only records notif path: icon <scheme> ok|unavailable and "toast shown with picture", never the picture or its URL.

Windows freeze fixes (ported from #26 by @matheuscardosoj)

• Async window-creating commands: add_account, open_account, rename_account, remove_account, open_settings and lock_app are now async. A synchronous command runs inside WebView2's IPC callback, and creating a WebView2 there can deadlock (wry#583).
• Account changes: they're serialized with accounts::lock_mutations(). An added account whose window fails to build is rolled back.
• Autostart off is now a no-op when it's already off. Windows used to report NotFound.

Testing

• On Linux: clippy (-D warnings) and fmt are clean, cargo test passes (106 tests, 4 of them new for icon decode, validation and pruning), and the bridge tests pass, including a new one for picture forwarding, timeouts and refused URL schemes.
• cargo clippy cross-checked for x86_64-pc-windows-msvc and aarch64-apple-darwin. My code adds no new warnings there; the remaining hits are older lints elsewhere on those targets.
• Not run against a logged-in WhatsApp, so it's unverified whether WhatsApp's picture URL can be fetched from the page. If it can't, the log shows icon … unavailable and the toast looks as before.

🤖 Generated with Claude Code

https://claude.ai/code/session_01L8dUghRiNrKrHHR5BNMSSD