# To do (Steam Machine edition) ## Open 1. **Test the live session** after the next build (`build-live-modules.sh` runs in the container before buildiso.sh): Vapor look and layout at the live login, `lsmod | grep steamify` in the live session (on the Steam Machine it loads; in the VM with `--fremont` too), and shutting down from the live session on the real Steam Machine stays off. 2. **Steamify PR**: `feat/defaults-mode` (2.6.0, `b948c20`) in steamify-cachyos, pushed, no PR yet (checked 2026-09-27: not on main, newest release v2.5.2). Ready: open it; the user merges (never commit to main). The ISO's first-login step needs 2.6.0 released. 3. **Test on the real Steam Machine** from a USB stick (gamescope, LEDs, CEC, power-off) before calling the ISO usable. ## Done - **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--x86_64.iso` (`iso_name` in `archiso/profiledef.sh`); the volume label stays `COS_`. - **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`). ## Later - **Steamify wizard pages in the installer**, before anything is installed: the same choices as Steamify's menu (conversion, boot into gamescope or desktop, theme, Deck icons, single user, shortcut + non-Steam game, notifications, VRAM booster, HDMI-CEC, Steam Machine support + power-off fix), defaults ticked like a first run. A Calamares page (netinstall-style YAML or a QML module in the `show` sequence) stores the ticked ids in global storage; `steamify-install` passes them to `steamify.sh --backend apply ` (`--boot gamescope|desktop`) instead of `--defaults`. - **Branding**: the live session's os-release says "Steamify, based on CachyOS" (Hello's subtitle); Hello's window title and the boot menu still say CachyOS. Check with the CachyOS team. - **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. Build and test details: the `steam-machine-iso` skill in steamify-cachyos-dev.