kari v0.4.3

kari v0.4.3 — built from 7934376.

TL;DR

• Say when the page cannot reach the app core

What changed

Say when the page cannot reach the app core

The frontend fell back to reading fixture files whenever the Tauri bridge was
missing from the page. That fallback belongs to the browser preview served by
the dev server. Inside a packaged app the same fall back reads a file that is
not there, and on a phone that request answers nobody, so the screen waited
for a board that could never arrive. A packaged page now reports the missing
bridge instead.

The phone log also had no line from the app crate, because the filter enabled
kari_core only. It enables kari as well, and the setup writes one line when
it finishes, so the log shows the order of events on a phone.

Install

Download the .dmg for your Mac: aarch64 for Apple silicon, x64 for Intel.
The app is not signed. After you copy it to Applications, run:

xattr -dr com.apple.quarantine /Applications/kari.app

An installed kari updates itself to this release: it checks on start and every six hours,
writes the new version beside the running one and offers a restart. Settings, Updates has the switch.

A Linux host runs the headless node from kari-node-v0.4.3-x86_64-unknown-linux-gnu.tar.gz,
a Windows host from kari-node-v0.4.3-x86_64-pc-windows-msvc.zip.
Start it with kari-node serve and add it under Settings, Nodes in the app.
A node updates itself only when asked: kari-node update, or serve --auto-update.

An Android phone installs kari-latest.apk. Add this repository to Obtainium: the asset name never
carries the version and the signing key never changes, so an update installs over the previous build.
The phone reaches the nodes over a private network, such as a VPN, and pairs with the code from
Settings, Nodes on the desktop. See TOUR.md.

See the README for requirements and setup.