v0.2.7

v0.2.7

A small GTK4 client release: it stops a second launch from hanging, tells you
when the harness isn't there, and makes two affordances actually reachable.

• A second launch no longer hangs. jsGTK's EventLoop.start() calls
  register() + activate() unconditionally and throws away register()'s
  result. When another instance already owned it.sonia.Assistant, the new
  process never got the activate signal, never built a UI, and spun in the poll
  loop forever — a hung terminal and no window. It now checks getIsRemote()
  after register() and hands the activation to the primary, then exits.
• A dialog when the harness is unreachable. A .desktop launch has no
  terminal to read "No harness answering at …" in, so the preflight error went
  nowhere and the process vanished with a blank screen. The same message now
  appears in a localized AdwMessageDialog and exits 1 when dismissed.
• ⟲ works on click, and About is a real toggle. The rewind button was
  hover-only (no touch or keyboard route); a click on the bubble now reveals it.
  The About window was modal, so the click meant to close it was swallowed —
  it's now non-modal and toggles, with Esc as the keyboard way out.

Packaged as sonia-gtk4-0.2.7-1-x86_64.pkg.tar.zst for Arch.

---

What's changed in v0.2.7

All commits since v0.2.6.

✨ Features

• feat(gtk4): a dialog, not just stderr, when the harness is unreachable

🐛 Fixes

• fix(gtk4): a second launch hands activation to the primary instead of hanging
• fix(gtk4): ⟲ on click, and make the About window a real toggle
• fix(ci): release notes said "Initial release" on v0.2.6

🧹 Chores

• chore(packaging): pkgrel 4 — the single-instance fix + the unreachable-harness dialog

📦 Other changes

• release: v0.2.7 — a second launch activates the primary, and a dialog when the harness is down