fix: update QR code rendering in host-papp-react-ui (#171)

Co-authored-by: Sergey Zhuravlev <zhuravlev1337@gmail.com>

Author: Yanaty

CHANGELOG.md

@@ -1,4 +1,4 @@
-()## 0.7.9 (2026-05-11)
+## 0.7.9 (2026-05-15)
 
 ### 🚀 Features
 
@@ -10,6 +10,11 @@
 - **host-api / product-sdk:** `push(...)` now returns an id you can hold onto, and the new `notificationManager.cancel(id)` lets a product cancel a notification it scheduled earlier — handy for "remind me in an hour" style flows where the user changes their mind.
 - **host-api / product-sdk:** if the host can't accept any more scheduled notifications, the product now gets a clear `ScheduleLimitReached` error instead of a generic failure, so it can tell the user what happened.
 
+### 🩹 Fixes
+
+- **host-papp-react-ui:** pairing QR code now renders on `<canvas>` via the lighter `qrcode` dep (replacing `qr-code-styling`), with pixel-snapped modules and circular finder eyes — scans reliably across phone cameras and stays crisp on hi-DPI displays.
+- **host-papp-react-ui:** pairing modal/popover is responsive — shrinks to fit narrow viewports instead of being pinned at 350px.
+
 ### ⚠️ Breaking Changes
 
 - **host-api:** `host_create_transaction` no longer takes a separate `account_id` parameter — the account is now part of the payload as a typed `signer` field.