v1.1.6

What's fixed

The pairing QR now shows up everywhere — including Windows.
The QR used to be drawn by Python's qrcode/pillow, but the only thing that installed
them was mesh-start.sh — a bash script using POSIX venv paths. On Windows (install from
source) it could not run, so import qrcode failed and the console silently fell back to
"QR failed". Without a QR the only way to pair was to hand-copy a 140+ character JSON blob
from the PC to the phone. The QR is now generated in the browser: no Python dependency,
works offline and on every platform.
(The prebuilt binaries already bundled qrcode, so they were not affected — this fixes the
"Install from source" path.)

The SQLite handle is now released on shutdown (Windows file lock).
Thanks to @Sajid-ul-Islam for finding and reporting this in #5. An open WAL connection kept
queue.db locked on Windows, blocking temp-dir cleanup. stop() now waits for the in-flight
task to write its result before closing the database — if a task is still running it
deliberately leaves the handle open, because losing a user's answer is worse than a file lock.

---

One-click Hermes companion apps (no Python needed).

• macOS — open hermes-companion-macos.dmg, drag Hermes Companion
  to Applications, then open it from Applications. First launch:
  right-click → Open (unsigned app; one-time Gatekeeper approval).
  To reinstall: quit the running one first (menu-bar icon → Quit).
• Windows — unzip, double-click hermes-companion.exe. If SmartScreen
  appears: More info → Run anyway.
• Linux — unzip, then run hermes-companion.AppImage
  (chmod +x if your browser cleared the executable bit).

The app starts the broker and opens the local browser console automatically;
scan the QR with the Hermes phone app to connect. Runs in the menu bar / tray.