Chronos Server now ships as a Docker image only, so the Windows setup no
longer offers it and the separate Uploader setup goes: one setup installs,
updates, adds and removes Chronos Desktop and Chronos Uploader in place.
- Install log format 2 records each component's files, shortcuts, version
and SHA-256; format 1 logs (1.0) are still read. A file of a removed
program that changed since setup installed it is kept, never deleted.
- A Chronos Server 1.0 for Windows installed by 1.0 is retained as "no
longer offered": its files and service are untouched until the user
unticks it or explicit /COMPONENTS leave it out; then it is removed with
its service. A format 1 log keeps every file the payload does not know.
- The separate 1.0 Chronos Uploader product is replaced: the Uploader is
preselected, its sign-in entry moves to the new copy (Task Manager state
kept), its shortcut is handed over and the old product is uninstalled.
An all-users copy under a per-user install stays and is said so.
- The setup window shows the dry-run plan (Changes: adds, removes,
replaces) before Update; with every program unticked the primary action
becomes Uninstall. /COMPONENTS=Desktop names the desktop app.
- pack-installer refuses Server (--legacy packs a 1.0 one for the CI test);
release.yml publishes only Chronos-Setup-<v>.exe and the portable zip;
the installer test covers add/remove in place, the Uploader replacement
and the retained Server.
Refs #64
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>