Backchannel v0.6.1

Backchannel v0.6.1

A fix release. The v0.6.0 updater could find an update and then refuse to
fetch it without a sign-in, for a build the download portal already hands to
anyone who asks.

Highlights

• Updating no longer asks for an account. Checking for an update worked,
  but pressing Download update opened a window asking you to sign in, and
  there was no account to sign in with, so the update could not be taken from
  inside the app at all. The update download is now anonymous, like every
  other download this project publishes: press the button and it downloads.
  There is no authorization window and no sign-in anywhere on the path.
• Installs on v0.6.0 are fixed without reinstalling. The portal side of
  the old handshake stopped requiring an account at the same time, so a
  v0.6.0 install that checks for updates can fetch v0.6.1 on its own. If you
  already gave up and downloaded a build by hand, nothing is lost; updates
  from here are in-app again.
• An interrupted download says so. A transfer that stops still resumes
  from where it left off, and the panel reports an interrupted download
  rather than blaming an expired authorization it no longer uses.
• Post-call Chat searches meetings by date. The meeting picker matched
  names alone while the session sidebar's find box understood dates, so the
  same query found different sessions depending on which box you typed it
  into. Both now share one implementation: October, oct 8, 8, 10/8 and
  2026-10-08 work in either. Clicking into either box says that searching by
  date works.
• The Privacy First review panel is readable in dark mode. The panel
  listing what stops working and what keeps working kept a light background
  in both themes while the feature names took the dark theme's light text, so
  the names disappeared exactly as you were deciding whether to turn the
  switch on.

Notes for operators

The in-app update routes are now anonymous on the download host:
/api/update/latest/* and /api/update/assets/* both serve without an
account, matching /api/download/releases/*, which was already public.
/api/download/update-grants still answers and still records nothing; it
exists only so installs built before v0.6.1 can complete the handshake they
expect. Recipient accounts no longer govern anything on the download path.

Upgrading

An install on v0.5.3 or later updates itself in place and verifies the new
build's signature before applying it. An install on v0.5.2 or earlier will
not see this release from inside the app: download the bundle from the
release page, quit the old version from the tray, and run the new one.