Fella v0.1.3

A patch on top of v0.1.2: the Windows /update command now actually
installs the update it downloads.

Fixed

• Windows: /update never applied the download. Since /update landed
  in v0.1.1 it would find the new version, download it, verify it against
  SHA256SUMS, close Fella — and then nothing installed and the app never
  came back. Two things were wrong. The detached hand-off that runs the
  installer was created with no console at all, so powershell.exe
  exited during startup before running a single line — no install, no
  relaunch, no trace. It was also built as a cmd string whose quoting
  arrived mangled, and it waited a fixed two seconds that often wasn't long
  enough for Fella to release the lock on its own binary, so a silent
  installer couldn't overwrite it and simply gave up. The hand-off is now a
  powershell -File script with its own hidden console that waits for the
  lock to actually release, runs the installer to completion, relaunches,
  and writes each step to %TEMP%\fella-update\update.log. Verified end to
  end on a real Windows build (0.1.2-style install → /update → installs
  and relaunches). The download-and-checksum half was always fine, and
  nothing is touched on disk until the checksum passes, so a failed apply
  still can't produce a broken install — the verified installer is left in
  %TEMP%\fella-update\ to run by hand.

Install

macOS / Linux

curl -fsSL https://lilfella.app/install.sh | sh

Windows (PowerShell)

irm https://lilfella.app/install.ps1 | iex

Already on an earlier build? Open Fella and type /update — and on Windows,
this is the release where that finally works.

Or grab the build for your OS directly from this release: .dmg (macOS),
-setup.exe / .msi (Windows), .AppImage / .deb (Linux).

Verify your download

Builds are unsigned. Check against SHA256SUMS, attached to this release:

sha256sum -c SHA256SUMS          # macOS / Linux

Get-FileHash <file> -Algorithm SHA256   # Windows — compare by hand

Known limitations

• /update on macOS and Linux is still best-effort, not yet verified
  against a real install on those platforms — Windows is now tested end to
  end. Nothing is touched on disk until the checksum passes, so a failure
  there means "didn't update", never a broken install — fall back to the
  install command above.
• run_python is not a hostile-code sandbox — see v0.1.0's notes,
  unchanged in this release.
• Unsigned, no signed auto-updater. /update covers the common case;
  code signing and notarisation are still unplanned for now.