# Handoff Rolling note between work sessions. **Update this file before you finish**, then commit it. It should be short and current; use `git log` for detail. - **Last updated:** this session (2026-09-24), Focused desktop-stack cleanup: Mango + DarkMaterial established as the sole, canonical desktop experience. Standalone dwl desktop, sessions, helpers, packages, and fallback logic completely excised across the entire codebase. - **Current focus:** 1. **Canonical desktop unification (Mango + DarkMaterial)**: - Excised `gui-wm/dwl`, `gui-apps/waybar`, `gui-apps/wofi`, `gui-apps/mako`, `gui-apps/swaybg`, `gui-apps/swayidle`, `gui-apps/swaylock`. - Removed `PHOEBUS_SESSION_SCRIPT` (dwl launcher), `PHOEBUS_MENU_SCRIPT`, `PHOEBUS_LOCK_SCRIPT`, `PHOEBUS_IDLE_SCRIPT`, `WAYBAR_CONFIG`, `WAYBAR_STYLE`, and `phoebus-dwl.desktop`. - `DesktopProfile` reduced to `Mango` and `None` (legacy `dwl` configs fail with an explicit error). - `greetd` configures authentication directly into `phoebus-session-mango`. - `/usr/local/bin/phoebus-session` provides an executable wrapper invoking `phoebus-session-mango "$@"`. - Session script tests retargeted to `phoebus-session-mango` with stubs. 2. **Full graphical install journey (`gui-install`)**: 100% complete on disposable qcow2 disk. Completed 12 stages (`storage_prepare`, `stage_install`, `fstab_generate`, `portage_configure`, `packages_base`, `kernel_install`, `nvidia_drivers`, `boot_install`, `users_configure`, `services_configure`, `desktop_install`, `finalize`) and emerged 174 desktop packages. 3. **Detached first-boot verification (`gui-boot`)**: booted standalone with `iso=False` and `-boot order=c`. Verified firmware -> systemd-boot -> LUKS2 decrypt -> Btrfs subvolumes (`@`, `@home`, `@var`, `@snapshots`, `@swap`) -> systemd `running` (0 failed units) -> serial login -> `sys` operational. 4. **Greetd greeter fix**: single-line command string in `/etc/greetd/config.toml` resolving TOML basic string multiline error; verified `tuigreet` rendered cleanly on the booted system (`01-boot-desktop.png`). 5. **Live ISO freshness invariant**: `scripts/ensure-live-iso.sh` automatically recompiles static binaries and repacks the live ISO whenever source files are newer than the ISO. - **Last verified (this session):** - `cargo fmt --all -- --check`, `cargo clippy --workspace --all-targets` and `cargo test --workspace` (all crate tests pass). - Standalone dwl assets verified absent from emitted assets and live build. - **Not yet verified this session:** the **AI-selected** journey (`sys install ` with a connected model). It is unit-tested with scripted transports but was not run against a live provider because no authorised provider/credential exists in this environment. - **Public repo:** (remote `origin`, SSH port 2222). ## Next actions (in order) 1. **AI-selected install journey (needs an authorised provider)**: boot the installed disposable disk (`/var/tmp/phoebus-vm/disks/test-disk.qcow2`), serve the built `sys` and a 0600 key file, then: ```sh sudo sys --ai-provider deepseek --ai-api-key-file /run/phoebus/ai.key \ install # and the no-model control in the same run: PHOEBUS_AI_PROVIDER= sudo sys install ``` Confirm the model requests evidence, the resolver confirms the candidate, the plan is presented before approval, and the transaction is recorded. No credential is available here; do not invent one. 2. **Rollback VM acceptance** (`serial-driver.py rollback`) on a cloned disposable image of the installed system. 3. **NVIDIA hardware acceptance (BLOCKED)**: needs an NVIDIA GPU. 4. **Interactive graphical user session** login into Mango / DankMaterialShell under a physical seat or nested Wayland compositor. ## Known blockers / risks - **A full VM install still takes hours** (base stage ~116 min). Use the already installed disposable disk (clone it) for `sys install` journeys rather than a fresh install. - **No NVIDIA GPU** (and no authorised passthrough). - **Snap needs network and AppArmor** for meaningful confinement; the lane detects confinement honestly. - **AppImage provides no sandbox**; do not describe it as one. - **Custom ebuilds remain separately reviewed, untrusted artifacts**; the install workflow never builds one during investigation. - **OpenCode transport** concatenates messages, so multi-turn investigation is best-effort there; the direct providers carry the full conversation. - Harness artifacts live under `/var/tmp/phoebus-vm/` (outside git). ## Environment notes - Dev host: Ubuntu 26.04. QEMU/OVMF/xorriso/rustfmt/clippy/ImageMagick/visudo present. `flatpak` and `snap` clients are present on the host (not proof of the VM lanes). - VM harnesses: `installer/tests/vm/{gui-driver,serial-driver,appliance-driver,live-driver}.py` and `sys-acceptance.sh`. `DISK` must be a disposable qcow2; never `/dev/*`. - Serve fixtures from `/home/dominic/vmlab/serve` with `python3 -m http.server 8000 --bind 127.0.0.1` (reachable as `10.0.2.2:8000`). - The static binaries for the VM: `make static` builds `phoebus-installer` and `sys` under `installer-rs/target/x86_64-unknown-linux-gnu/release/`. ## Definition of a good stopping point - `make test` passes; `docs/STATUS.md` and `docs/CHANGELOG.md` updated; `docs/HANDOFF.md` updated; committed (via `scripts/agent-commit.sh`) and pushed (`scripts/publish.sh`).