kari v0.15.0

kari v0.15.0 — built from 90b7588.

kari keeps its own hook entries current. You click "Install hooks" once. From
then on, every start compares the entries in settings.json with the events
this version registers, and writes them again when a release adds one. Away
mode and the autopilot gate no longer wait for a second click after an
upgrade.

TL;DR

• Keep the hook entries current at every start (#49)

What changed

Keep the hook entries current at every start (#49)

A release can add an event to the set kari registers in settings.json. 0.11
added PermissionRequest for Away mode, and the autopilot gate added Bash to
the PreToolUse matcher. A user who installed the hooks before that kept the
old set, so the feature was off and only a line in the node log said so.

kari owns its entries now. At start the server compares the event, the
matcher, the timeout and the command line with what this version installs. If
one differs, it writes the entries again, with a backup first and every other
hook untouched. A user who never installed the hooks gets nothing, and the
write is idempotent, so the next start writes nothing.

entries_current replaces held_event_installed and gate_installed, which asked
the same question for one event each.

The hooks_install example refuses to run without CLAUDE_CONFIG_DIR: it writes
settings.json and removes the relay script, so it must never touch a real
install.

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

On Windows, run kari_0.15.0_x64-setup.exe. It installs for the current user,
because kari reads the Claude Code state of whoever is logged in. That installer is
not signed either, so SmartScreen asks once: More info, then Run anyway.

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.

Every host runs the headless node, so that its sessions stay on the board while no window is open.
A Mac takes kari-node-v0.15.0-aarch64-apple-darwin (or the x86_64 one),
a Linux host kari-node-v0.15.0-x86_64-unknown-linux-gnu.tar.gz,
a Windows host kari-node-v0.15.0-x86_64-pc-windows-msvc.zip.
Run kari-node service install to keep it running at login. One engine runs on a host at a time:
open the app and the node steps down, quit the app and it takes the host back.
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.