From bfaf97729433d82bac917fccc80a798cf9d5adb6 Mon Sep 17 00:00:00 2001 From: Geoffrey Vancoetsem <10533139+geeooff@users.noreply.github.com> Date: Mon, 16 Nov 2026 17:04:09 +0100 Subject: [PATCH] Record 0.5.0's field checks: every startup path, and the attestation After the release, with the files CI built: the update from the published 0.4.0 through the menu by the package and by the zip, the zip's 0.4 shell calling the new binary through the install-task alias, and a real purge. Lot 19 has only an Office update left to see. Lot 20's first attested release verified with gh attestation verify; an update that waits for the maintainer is still to see. Co-Authored-By: Claude Opus 5.5 --- docs/design/19-startup-list.md | 34 ++++++++++++++++++++++++++++++---- docs/design/20-build-chain.md | 10 ++++++++-- docs/design/README.md | 4 ++-- 3 files changed, 40 insertions(+), 8 deletions(-) diff --git a/docs/design/19-startup-list.md b/docs/design/19-startup-list.md index 0421fd8..e2703c8 100644 --- a/docs/design/19-startup-list.md +++ b/docs/design/19-startup-list.md @@ -1,6 +1,7 @@ # Lot 19 — Starting from Windows' Startup list -**Status: decided 2026-11-16, being built; ships in 0.5.0.** The maintainer +**Status: shipped in 0.5.0, 2026-11-16; every path seen, an Office update +still to see.** The maintainer wants GameModeExecutor in *Settings → Apps → Startup*, with its switch, instead of a logon task that page does not show. The spike adds a second reason: Office's updates end what a logon task started, and spare what the @@ -11,13 +12,13 @@ reason: Office's updates end what a logon task started, and spare what the - [x] `add-to-startup` and `remove-from-startup`, the old names as hidden aliases; the package, the zip's updater and `purge` on them — 2026-11-16 - [x] The user pages, the reference, the changelog — 2026-11-16 - [x] Explorer starts the watcher from a person's terminal and from the package's action — 2026-11-16, below -- [ ] Explorer starts it from the zip's shell, at the 0.5.0 update +- [x] Explorer starts it from the zip's shell, at the 0.5.0 update — 2026-11-16, below - [x] The 0.4 task removed by `add-to-startup`; `uninstall-task` works as an alias — 2026-11-16, below - [x] An upgrade from the published 0.4.0 by the package, a configuration path of the task's kept — 2026-11-16, below -- [ ] An upgrade from the published 0.4.0 by the zip, at the 0.5.0 update +- [x] An update from the published 0.4.0 through the menu, by the package and by the zip — 2026-11-16, below - [x] The switch: off, then a logon; on again — 2026-11-16, below - [x] `remove-from-startup` takes the switch's entry too; `purge` lists the entry and no task — 2026-11-16, below -- [ ] `purge` carried out, at the next full purge +- [x] `purge` carried out — 2026-11-16, below - [ ] The watcher outlives an Office update ## Why @@ -253,6 +254,31 @@ page: `add-to-startup` put the value back. `purge`, answered no, listed *remove the startup entry `GameModeExecutor` and its switch* and no task. +After the release, with the files CI built and attested (`ad7e92dc`): + +- **The package, through the menu.** The published 0.4.0 installed at + 16:52, its task registered. *Check for updates* found 0.5.0 at 16:53:08, + downloaded and verified it, and ran the package: the handover, the task's + configuration read, the value added, the task removed, *Watcher started + through Explorer*, *Updated to 0.5.0* at 16:53:29, the watcher Explorer's + child. +- **The zip, through the menu**, with no package installed. The published + 0.4.0 zip unpacked in a scratch folder and its `install-task` run: the + task registered at 16:57:56. *Check for updates* fetched the 0.5.0 zip; + 0.4.0's shell replaced the files and called the new binary's + `install-task`, which the alias took: the value written for the zip's + copy, the task removed, the watcher started through Explorer, *Updated + to 0.5.0* at 16:58:15. The `.old` files were gone at that start. +- **A real `purge`**, from that zip copy, after the configuration and the + log were copied aside: the watcher stopped; the value and its switch + gone, the recipe's two tasks kept; the configuration, every log file, + the updates folder and both profile folders removed; the executables + deleted once the command had exited. Its console printed no line for the + startup entry, whose removal went to the log it was deleting; worth a + line in a later version. The files were copied back and the published + 0.5.0 package installed at 17:02: *Configuration kept*, the value added, + the watcher Explorer's child. + ## Done when The watcher starts at logon from the `HKCU` `Run` key and shows on the diff --git a/docs/design/20-build-chain.md b/docs/design/20-build-chain.md index e5d97f7..c3127c2 100644 --- a/docs/design/20-build-chain.md +++ b/docs/design/20-build-chain.md @@ -1,8 +1,9 @@ # Lot 20 — The build chain, official and kept current **Status: decided and built 2026-10-17.** Seen the same day: Dependabot's -first PR, two crate patches, merged itself once CI had passed. Still to see: -an update that waits for the maintainer, and the first attested release. Taken while Lot 19's spike waits for an Office +first PR, two crate patches, merged itself once CI had passed. The first +attested release seen 2026-11-16, below. Still to see: an update that waits +for the maintainer. Taken while Lot 19's spike waits for an Office update. Two parts, in this order: Dependabot keeps current whatever the first part settles on. @@ -35,6 +36,11 @@ Read on 2026-10-17: CI uses `actions/checkout@v7`, `actions/upload-artifact@v7` Not a code signature — SmartScreen still warns — but proof the installer was built from the public source, which `SHA256SUMS.txt`, published on the same page as the files, cannot give. + **Seen on 0.5.0, 2026-11-16:** the MSI downloaded from the release + matched `SHA256SUMS.txt`, and `gh attestation verify` passed with one SLSA + provenance v1 statement naming the MSI, the zip and the recipes zip, + signed by `release.yml@refs/tags/v0.5.0` at `ad7e92dc`. A minor of a crate + at 1.0 merged itself on the way, toml 1.1.8 to 1.2.1 (#29). ## 2. Dependabot and automatic merges diff --git a/docs/design/README.md b/docs/design/README.md index d839e04..1c94c22 100644 --- a/docs/design/README.md +++ b/docs/design/README.md @@ -29,8 +29,8 @@ the pages keep the history. | 16 | [What the watcher keeps](16-footprint.md) | done 2026-09-23; memory at rest to measure again against 0.3.0 | | 17 | [A log that turns over each day](17-log-rotation.md) | done 2026-09-26; its last checks seen 2026-10-17 | | 18 | [When the game is gone and nobody is there](18-game-gone-nobody-there.md) | proposed, not decided | -| 19 | [Starting from Windows' Startup list](19-startup-list.md) | being built, for 0.5.0; field checks open | -| 20 | [The build chain, official and kept current](20-build-chain.md) | built 2026-10-17; the first wait and the first attested release to see | +| 19 | [Starting from Windows' Startup list](19-startup-list.md) | shipped in 0.5.0; every path seen; an Office update to see | +| 20 | [The build chain, official and kept current](20-build-chain.md) | built 2026-10-17; attestation seen on 0.5.0; an update that waits still to see | | 21 | [Moving to windows-rs 0.100](21-windows-rs-0100.md) | proposed; waiting for `windows` 0.100 | Logging came before the icon, so the icon was written in the final log