Updates and releases
From the studio
Connected, the studio asks the daemon once whether a newer release exists. If so, the status bar reads Runner running 0.2.0 · 0.3.0 available and the warning center gets an entry. Click the runner: the panel shows what changed and one button, Update to 0.3.0 and restart.
The daemon downloads the release for its platform, checks the sha256 against the release's checksums, swaps its own binary and starts again on the same address and token. The page waits for the new version and reports Updated to 0.3.0; the connection is the same. Runs are untouched.
An update is refused while a job runs; wait for it or cancel it. Check for updates asks again at any time. Restart runner starts the daemon again without updating.
From a terminal
sigscape-daemon update
The same check and swap, printed. sigscape-daemon --version shows what is installed.
A daemon too old for the studio
The studio names the oldest daemon it can drive. An older one reads Runner outdated in the footer, its Run buttons stay off, and because it predates self-update you install the current release with the installer and start it again.
How a release is made
A release is a tag on the daemon's repository: git tag v0.3.0 && git push origin v0.3.0. The repository's workflow builds the binary for Linux (x86_64, arm64), macOS (Apple silicon, Intel) and Windows, publishes one archive per platform with checksums.txt, and writes the notes from the commits. Every running daemon sees it at its next check; the installer serves it from then on.