Merge pull request #24 from theupriser/docs/iso-todo-2

docs: TODO: tick off what is done, say what is left

CHANGELOG.md

@@ -26,46 +26,6 @@
   * Correctly handle VM environments
   * Correctly quote pacman arguments
 
-## CachyOS with Steamify Live ISO
-CachyOS 26.08 with Steamify built in: install CachyOS and turn the PC into a Steam Machine in one go.
-Its version is the Steamify version on it plus the build date and time (UTC, when the release starts on GitHub; a release on `master` is `v<Steamify version>-<date>-<HHMM>`, e.g. `v2.9.3-2026.09.29-2015`). A new Steamify release starts one (a test build for now); by hand: Run workflow on "ISO 1/2 · Tag and release (GitHub)".
-Releases: GitHub creates the tag and a release with the notes; the ISO itself (over GitHub's 2 GB limit) is built on the Gitea mirror and attached to its release for that tag (git.upriser.nl).
-
-**Features:**
-
-* **ISO:** named after its release tag (`steamify-cachyos-2.9.3-2026.09.29-2030-x86_64.iso`; built by hand, without a tag: `local`), labelled after the Steamify version on it and the build time (`STEAMIFY_2_9_1_20260929_1432`, was CachyOS's `COS_<year><month>`); CachyOS Hello installs it like CachyOS's own
-  release (the ISO's own release, its tag without the v, is in `/etc/steammachine-iso-build` and the boot menu)
-* **Installer (CachyOS - Steamify Installer):**
-  * A Steamify page after the packages page: which Steam Machine parts to set up (rows from
-    `steamify.sh --defaults --list`, the newest Steamify fetched before Calamares starts) and where
-    the PC starts (gaming mode or the desktop)
-  * The Summary lists every chosen item and where the PC starts
-  * The new user's Steam Machine setup runs during the install (`steamify-install`, a Calamares step
-    before cleanup): the first boot is already a Steam Machine
-  * Only what Steamify supports is offered: KDE Plasma, and the boot loaders Limine, systemd-boot and
-    GRUB (not rEFInd)
-* **Live session:** keeps CachyOS's own name; the power-off fix is built for the ISO's kernels, and
-  the login has the Vapor look
-
-**Fixes:**
-
-* **systemd-boot:** the installed system gets its "Linux Boot Manager" EFI boot entry, first in the
-  boot order. cachyos-installer runs `bootctl install` in a chroot, where bootctl leaves the EFI
-  variables alone, so the entry was missing: the PC could only boot through the disk's fallback path
-  (`\EFI\BOOT\BOOTX64.EFI`). Most PCs find it early and boot normally, but firmware that tries the
-  network first waits minutes on every boot (QEMU/OVMF: PXE, HTTP boot and the EFI shell come first),
-  and anything else that writes the fallback file (another OS) takes the boot over.
-  `steamify-install` now registers it with `efibootmgr` from the live system, with the ESP's real
-  disk and partition (bootctl in the chroot writes an entry without a partition, which the firmware
-  can't load); the output is in `/var/log/steamify-bootentry.log`
-* **Installer:** Steamify's install-time logs (`/var/log/steamify-install.log`,
-  `steamify-bootentry.log`) are readable after the first boot: `/var/log` is its own btrfs subvolume
-  (`@log`) that wasn't mounted yet when Steamify ran, so they ended up hidden under it
-* **Installer:** Steamify's setup never asks for a password (its sudo rule is read after CachyOS's
-  `%wheel` rule); Calamares starts with the Boost version it was linked against
-* **Build:** finishes cleanly as root and reports no error after a successful build; the Steamify page's
-  Calamares module is built with the ISO and left out when Calamares' version differs
-
 # 26.07
 **Features:**
 

TODO.md

@@ -1,89 +1,75 @@
 # To do (Steam Machine edition)
 
+Tick items off as they are done; the newest entries are at the top of each list.
+
 ## Open
 
-1. **Steamify installer page** (2026-09-28, working end to end; see
-   `AGENTS.md` for the module/build/testing details and gotchas behind
-   this). `packagechooserq` (custom QML) is built with each ISO by
-   `build-calamares-modules.sh` into `archiso/airootfs/usr/lib/calamares/modules/packagechooserq/`.
-   `netinstall` (checkbox tree) stays as a manually-swappable fallback
-   (`steamify-cachyos-dev/share/sn.sh` + `nisteamify.conf`) for when the
-   module can't load, but isn't wired into `calamares-online.sh`
-   automatically yet.
-   - **Still open**:
-     - A Python job (e.g. `steamifychoice`, before `packages@online`) to
-       normalize either page's choice (packagechooserq's
-       `packagechooser_steamifypage` GS key, or netinstall's
-       packageOperations markers) into one `steamifyChoice` GS key, so
-       `shellprocess_steamify.conf` doesn't need to know which page ran.
-
-2. **Names**: only the installer says Steamify ("CachyOS with Steamify
-   Installer", productName set by calamares-online.sh); the live session,
-   Hello and About this System keep CachyOS's own names (legal clarity). The
-   ISO file stays `steamify-cachyos-<date>.iso`.
-3. **Check the names** after the next build: installer title, Hello and
-   About this System say CachyOS.
-4. ~~Steamify PR for `feat/defaults-options`~~ — done: 2.7.0 (`--options`,
-   `--boot`, `steamify.sh --boot` standalone) and 2.8.0
-   (`--defaults --list`, what the Steamify page's rows come from) are both
-   released. **The ISO builder is up to date with this**: no checkout
-   argument needed, `steamify-prepare.sh` (no args) and `calamares-online.sh`
-   at boot both just fetch the newest release, so the ISO always has 2.8.0+
-   without a rebuild for a Steamify-side change alone. Only pass
-   `steamify-prepare.sh <checkout>` / `vmisobuild.sh --steamify <path>` when
-   testing an *unreleased* Steamify change.
-5. **Build in the test VM** instead of on the Steam Machine
-   (steam-machine-iso skill), and install the result unattended with
-   `scripts/vminstall.sh --iso` (vm-install skill; the Calamares Steamify
-   step then needs `steamify-install` run from the live script).
-6. **Test on the real Steam Machine** from a USB stick (gamescope, LEDs, CEC,
-   power-off) before calling the ISO usable.
+- [ ] **Steamify installer page, one choice key** (2026-09-28; the page works end to end, see `AGENTS.md` for the
+      module/build/testing details). `packagechooserq` (custom QML) is built with each ISO by
+      `build-calamares-modules.sh`. `netinstall` (checkbox tree) stays a manually swappable fallback
+      (`steamify-cachyos-dev/share/sn.sh` + `nisteamify.conf`), not wired into `calamares-online.sh`.
+      Still to do: a Python job (e.g. `steamifychoice`, before `packages@online`) that normalizes either page's choice
+      (`packagechooser_steamifypage` GS key, or netinstall's packageOperations markers) into one `steamifyChoice`
+      GS key, so `shellprocess_steamify.conf` doesn't need to know which page ran.
+- [ ] **Names, the live session**: the installed system's names were checked (2026-09-30: `os-release` and `lsb-release` are
+      CachyOS's, test B3). Still to look at: the installer title, Hello and About this System in the live session (only the
+      installer says Steamify).
+- [ ] **Test on the real Steam Machine** from a USB stick (gamescope, LEDs, CEC, power-off) before calling the ISO usable.
+- [ ] **Retention, first clean-up**: the code is merged (PR #22: at most 10 dev + 10 real releases, the mirror's release with
+      its ISO is deleted first). Watch the first time there are more than 10 releases of a kind; it hasn't run yet.
+- [ ] **Build badge, the other states**: succeeded was seen (`v2.9.6-260930`). Failed, cancelled and a build superseded by a
+      newer one haven't been seen; a crashed runner leaves the badge on "running".
+- [ ] **Check with the CachyOS team** whether the installer branding and the ISO file name are fine with them.
+- [ ] **Drop the Boost 1.91 workaround** in `steamify-prepare.sh` once `cachyos-calamares-next` is rebuilt against the repos' Boost.
 
 ## Done
 
-- **Full ISO install with the Steamify page** (2026-09-28, ISO VM,
-  `--fremont`, Start in: desktop): Summary listed the choices, the
-  install step ran Steamify 2.8.0 with every item OK, `--boot desktop`
-  applied, `exit: 0`; the installed system boots into the desktop.
-- **Steamify Summary** (2026-09-28, ISO VM): an unordered list of the chosen
-  items' names plus "Starts in gaming mode/the desktop"
-  (`patches/packagechooserq-steamify-summary.patch`), with `items.json`
-  written by the launcher (its `$sdir` bug fixed, `0cc7367`).
-- **packagechooserq built with the ISO** (2026-09-28):
-  `build-calamares-modules.sh` builds it in the build container/VM from
-  CachyOS's Calamares source against the current `cachyos-calamares-next`
-  (no prebuilt `.so` in git), with `built-for`; `calamares-online.sh` leaves
-  the Steamify page out when the Calamares it runs differs (the step then
-  installs everything on) instead of risking "Initialization Failed".
-- **Steamify 2.6.0** released (`--defaults`, install-time mode).
-- **Live session** (VM, `--fremont`): Vapor look and layout (Steam Deck
-  wallpaper) at the live login; the power-off module is built for both ISO
-  kernels and loaded at boot, in the VM it returns "No such device" (no
-  AMDI0030 GPIO controller), as designed. Whether it keeps the real Steam
-  Machine off is part of the hardware test.
-- **Regression test 2.6.0 on an existing desktop install** (test VM from
-  ssh-ready, `--fremont`): full first run, re-apply, notifications/CEC/theme
-  off and on again. No errors; user units enabled and running, theme applied
-  and restored live, no first-login autostart with a session.
-- **ISO name**: `steamify-cachyos-<date>-x86_64.iso` (`iso_name` in
-  `archiso/profiledef.sh`); the volume label stays `COS_<yyyymm>`.
-- **VM install from the ISO (2026-09-27, `f42859a`):** a VM install from the ISO (Hello's
-  Install, no manual fixes) ran Steamify's step: every component OK,
-  `exit: 0`, SDDM autologin into gamescope. First desktop login (session switched to plasma in the VM) passed too:
-  Vapor layout, the app opened with everything on. The first-login script
-  runs the newest *release*, so it only works once 2.6.0 is released (in the
-  test it was pointed at the bundle).
-  The VM's text
-  console doesn't show (virgl): read the installed disk with
-  `qemu-nbd -r` + `mount -o ro,rescue=nologreplay,subvol=@` (logs in `@log`).
+### Release pipeline (2026-09-29 and 2026-09-30)
 
-## Later
+- [x] **Daily names like CachyOS**: tag `v<steamify>-<YYMMDD>` (dev: `v<steamify>-dev-<YYMMDD>`), file
+      `steamify-cachyos-<steamify>-[dev-]<YYMMDD>-x86_64.iso`, label `STEAMIFY_<version>_<YYMMDD>`; one ISO per day and
+      kind, the newest build replaces the earlier one.
+- [x] **Always from `master`**: `iso-1-github-tag.yml` takes `kind` (release, dev, auto); steamify-cachyos' `bundle.yml` asks
+      for `release` (a version published from main) or `dev` (an unreleased version on a release branch).
+- [x] **`steamify_ref`**: a release branch builds its dev ISO with its own Steamify (and VERSION) before it is released.
+- [x] **The mirror's build is started by dispatch** after the mirror has the new tag object (a replaced tag starts no run by
+      itself; the dispatch needs the full ref `refs/tags/<tag>`).
+- [x] **Build badge** in the GitHub release: running, then succeeded / failed / cancelled (secret `GH_RELEASE_TOKEN` on the
+      mirror), linked to the public Gitea run.
+- [x] **Generated release notes** and title (`CachyOS <base> with Steamify <version> (<date> UTC)`): base version, Steamify's
+      changelog section, commits since the previous release; the mirror's release uses the same text.
+- [x] **Retention** of at most 10 dev and 10 real releases, deleting the mirror's release with its ISO too (PR #22; first
+      clean-up still to be seen, above).
+- [x] **Old hand-written `CHANGELOG.md` section** (`## CachyOS with Steamify Live ISO`) removed: the release notes are generated.
+- [x] **Same-day replacement of a real release** (2026-09-30): the official build for `v2.9.6-260930` replaced the test build's
+      release on the mirror (ISO asset 42 -> 50, new title and generated notes, badge green with the public run link).
+- [x] **Release notes** leave out the workflow and docs commits (`ci`, `docs`, `…(ci):`) in their list of ISO changes.
+- [x] **The ISO is built on the Gitea mirror's runner** (`iso-2-gitea-build.yml`) and hosted there (over GitHub's 2 GB limit);
+      the VM tests run locally (`scripts/vmtest.sh --install` in steamify-cachyos-dev), not on the runners.
+- [x] **Build in the test VM instead of on the Steam Machine**: superseded by the runner above.
 
-- **Branding**: only the installer carries Steamify's name; check with the
-  CachyOS team whether that and the ISO file name are fine with them.
-- **Release**: a CI job that builds the ISO (privileged container, flags from
-  the steam-machine-iso skill) and hosts it (>2 GB, not a GitHub release asset).
-- **Drop the Boost 1.91 workaround** in `steamify-prepare.sh` once
-  `cachyos-calamares-next` is rebuilt against the repos' Boost.
+### Installer, live session and Steamify (2026-09-27 to 2026-09-29)
 
-Build and test details: the `steam-machine-iso` skill in steamify-cachyos-dev.
+- [x] **Steamify PR `feat/defaults-options`**: 2.7.0 (`--options`, `--boot`) and 2.8.0 (`--defaults --list`) released; the ISO
+      fetches the newest release, nothing to pass for a Steamify-side change alone.
+- [x] **Full ISO install with the Steamify page** (2026-09-28, ISO VM, `--fremont`, Start in: desktop): the Summary listed
+      the choices, the install step ran Steamify 2.8.0 with every item OK, `--boot desktop` applied, `exit: 0`; the
+      installed system boots into the desktop.
+- [x] **Steamify Summary** (2026-09-28): an unordered list of the chosen items' names plus "Starts in gaming mode/the
+      desktop" (`patches/packagechooserq-steamify-summary.patch`), with `items.json` written by the launcher.
+- [x] **packagechooserq built with the ISO** (2026-09-28): `build-calamares-modules.sh` builds it against the current
+      `cachyos-calamares-next` (no prebuilt `.so` in git), with `built-for`; `calamares-online.sh` leaves the Steamify
+      page out when the Calamares it runs differs (the step then installs everything on).
+- [x] **Steamify 2.6.0** released (`--defaults`, install-time mode).
+- [x] **Live session** (VM, `--fremont`): Vapor look and layout (Steam Deck wallpaper) at the live login; the power-off
+      module is built for both ISO kernels and loaded at boot (in the VM it returns "No such device": no AMDI0030 GPIO
+      controller, as designed; whether it keeps the real Steam Machine off is part of the hardware test).
+- [x] **Regression test 2.6.0 on an existing desktop install** (test VM from ssh-ready, `--fremont`): full first run,
+      re-apply, notifications/CEC/theme off and on again; no errors.
+- [x] **ISO name** (first version, since superseded by the daily names above): `steamify-cachyos-<date>-x86_64.iso`.
+- [x] **VM install from the ISO** (2026-09-27, `f42859a`): ran Steamify's step with every component OK, `exit: 0`, SDDM
+      autologin into gamescope; the first desktop login passed too (Vapor layout, the app opened with everything on). The
+      VM's text console doesn't show (virgl): read the installed disk with `qemu-nbd -r` + `mount -o ro,rescue=nologreplay,subvol=@`
+      (logs in `@log`).
+
+Build and test details: the `steam-machine-iso` skill in steamify-cachyos-dev; the release pipeline: `steamify-iso-release`.