phoebus_os/docs/HANDOFF.md
Phoebus bbd3d89d6a
Some checks are pending
ci / test (push) Waiting to run
feat(desktop): make Mango + DankMaterialShell the default and build a live desktop ISO
- desktop.profile defaults to mango with Flatpak on; explicit none/minimal/dwl/
  full still win. The plan shows the selected session.
- Installed login uses greetd + tuigreet (authentication required, Mango default,
  dwl selectable); live autologin is a separate live-only configuration.
- installer/live/build.sh builds a rootless Debian testing rootfs with Mango
  (pinned source build), DankMaterialShell (pinned SHA-256 release), Quickshell,
  scenefx, Qt Wayland and greetd, then splices it into the base Debian-Live boot
  equipment. Live autologin, an Install Phoebus launcher and a serial/VT
  recovery console are included and the build fails clearly if a desktop
  component is missing. Verified in a graphical seat-providing VM (Mango + DMS +
  Quickshell; DMS panel captured).
- Shared desktop assets emitted by phoebus-installer --emit-asset, a graphical
  VM driver (live-driver.py), and regression tests for defaults/overrides,
  login, live/installed separation and the live ISO guards.
- Docs updated: ADR 0005/0009, STATUS, HANDOFF, CHANGELOG, ROADMAP, DEVELOPMENT
  and VM-BOOT-VERIFICATION.
2026-09-21 06:47:22 -07:00

3.9 KiB

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: commit 639cb33 + this session (2026-09-21)
  • Current focus: Mango + DankMaterialShell as the default desktop. The installed default is desktop.profile = "mango" with greetd authenticated login (Mango default, dwl fallback), and installer/live/build.sh now builds a Mango live desktop ISO from a rootless Debian testing rootfs plus pinned Mango/DMS releases. Graphical VM verification of the installed desktop and the built ISO is the remaining evidence gap.
  • Last verified: static Rust binary install + detached boot and the 2026-09-21 appliance baseline (INSTALL-RC=0, NO_SECRET_LEAK, coordinated initial snapshot + recovery entry) in docs/VM-BOOT-VERIFICATION.md; unit/functional tests for the Mango default, explicit overrides, greetd login, live/installed separation, session entries, pinned release checksums and the live ISO guards; and the built Mango live ISO booted in a graphical seat-providing VM (Mango + DMS + Quickshell running, DMS panel/welcome captured by screendump).
  • Public repo: https://git.phoebus.club/phoebus/phoebus_os (remote origin, SSH port 2222).

Next actions (in order)

  1. Mango graphical verification (default, so highest priority): install the default profile and boot the built live ISO in a graphical, seat-providing VM; verify the panel/launcher/terminal/Install-Phoebus entry, audio/network, lock/idle, logout/reboot and the dwl fallback, plus authenticated login on the installed system (docs/VM-BOOT-VERIFICATION.md).
  2. Rollback VM acceptance: deliberately break an update in the disposable VM, run sys undo, reboot detached, verify package-state consistency (/var/db/pkg matches /), then boot the snapshot recovery entry with no network or model (ADR 0007).
  3. Live AI provider call: exercise sys ask with a real 0600 key file and confirm the systemd-run sandbox properties apply; the path is fixture-verified only.
  4. Physical-seat desktop: run phoebus-session on a real VT/seat and check phoebus-menu, phoebus-lock, phoebus-idle, kitty, XWayland, the polkit agent, logout/reap and reboot (docs/DEVELOPMENT.md).
  5. Matching signed binhost / binary strategy: keep the official binhost for matching USE and Flatpak/Nix elsewhere; do not publish a private binhost (ADR 0006). Verify with emerge -pv.
  6. Release gates on a CI runner: run phoebus-release gates --execute and phoebus-release publish once a runner exists; no gate has executed.

Known blockers / risks

  • No live DeepSeek/OpenAI call has been made (no key in this environment).
  • No Forgejo Actions runner is known to exist; .forgejo/workflows/ci.yml only runs once one is registered.
  • Desktop graphical login / physical seat has not been exercised; the serial VM has no logind seat.
  • NVIDIA is not verified on hardware.
  • Rollback and the AI sandbox are implemented and unit-tested but not VM-verified.

Environment notes

  • Dev host: Ubuntu 26.04. QEMU/OVMF/xorriso/rustfmt/clippy installed.
  • Debian-Live base ISO is cached at /home/dominic/debian-live-standard.iso (matches installer/live/base.sha256); the appliance ISO builds without root.
  • The appliance harness is installer/tests/vm/appliance-driver.py + appliance-guest.sh + appliance-test.conf.example; serve the stage3, config and 0600 secret files over python3 -m http.server 8000.
  • The VM harness disks are disposable qcow2 files on / (not /tmp, which is a small tmpfs); never point DISK at /dev/*.
  • The VM harness honours CHECKS_TIMEOUT / INSTALL_TIMEOUT for long runs.

Definition of a good stopping point

  • make test passes; docs/STATUS.md and docs/CHANGELOG.md updated; docs/HANDOFF.md updated; committed and pushed (scripts/agent-commit.sh + scripts/publish.sh).