phoebus_os/docs/HANDOFF.md
2026-09-22 07:30:38 -07:00

6.4 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: this session (2026-09-22), sys administration hardening.
  • Current focus: Hardened sys into a reliable administration tool. (1) All package/service/Flatpak execution now honours --root through one target_spec/chroot path (offline systemctl --root for enable/disable), and runtime-only service operations are rejected before any command when an alternate root is requested. (2) Every action is validated at the execution boundary (parse_natural now validates its own output); option-like operands are rejected and operands are passed after --. (3) sys ask stops at the first failure, records completed/failed/unattempted actions, and exits nonzero. (4) Ordinary mutating commands are recorded, the generic protective snapshot id is preserved, and recording failures are visible. (5) A genuinely empty package plan is distinguished from unparseable emerge output, which is refused. (6) Added typed start/stop/restart_service and ordinary commands for Flatpak, Nix preparation and snapshots.
  • Last verified (this session):
    • 368 Rust tests green (including 3 new CLI integration tests) + 16 harness tests; cargo fmt --all -- --check and cargo clippy --workspace --all-targets clean (exit 0). Static phoebus-installer/sys build.
    • Unit/integration evidence for all six fixes: preview and execution both chroot to the same alternate root; runtime service ops reject an alternate root without invoking anything; invalid actions are refused by the manual, JSON and AI parsers and at the executor; execute_plan marks later actions unattempted after a failure; unparseable emerge output is refused while a real 0 packages plan is accepted; a material plan change aborts before the mutation.
  • Not yet verified this session: the destructive rollback VM acceptance (sys undo). See the blocker below — rollback stays explicitly unverified. The OpenCode live tests are environment-gated and were skipped (no PHOEBUS_OPENCODE_LIVE_*), and the full graphical install past the AI gate and a separate physical computer remain unverified from the previous session.
  • Public repo: https://git.phoebus.club/phoebus/phoebus_os (remote origin, SSH port 2222).

Next actions (in order)

  1. Complete the graphical install with a real model: download a small local OpenAI-compatible model (or supply a 0600 provider key), then run gui-driver.py gui through disk/account/review/ERASE/install/rebooot twice on fresh qcow2 disks and record the passing journeys. The current automated journey passes to the AI gate only.
  2. Installed Mango desktop: install the default profile in a graphical VM and verify the panel/launcher/terminal/audio/network/lock/idle, the dwl fallback, and the welcome/installer absence on the installed system.
  3. Rollback VM acceptance (BLOCKED this session): deliberately break an update, run sys undo, reboot detached, verify /var/db/pkg matches /, then boot the recovery entry with no network or model (ADR 0007). Needed: (a) free the >=20 GiB make doctor wants for the harness (the root fs has ~12 GiB free); (b) an automated driver for the break-update/undo/recovery sequence — appliance-driver.py only implements install/boot. Until both exist, sys undo stays unverified.
  4. Narrow the live broker privilege: replace the live-only NOPASSWD: ALL rule for the GUI bridge with the smallest practical command-scoped rule once a safe sudoers form is verified (ADR 0011 context).
  5. 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).
  6. Release gates on a CI runner: phoebus-release gates --execute and publish once a runner exists; no gate has executed.

Known blockers / risks

  • No live DeepSeek/OpenAI key and no local model are available; the full GUI install past the AI step and two fresh-disk graphical installs are NOT verified (normal installation requires a connected model). The AI step is verified as a blocked prerequisite and with a fixture transport.
  • Installed Mango (GURU + compiled Quickshell/DMS) is not VM-verified; nor is the dwl fallback session.
  • Rollback (sys undo) is implemented and unit-tested but NOT VM-verified (BLOCKED). Exact blockers: make doctor reports ~13 GiB free versus the

    =20 GiB the harness wants (root fs ~12 GiB free), and the harness has no automated break-update/undo/recovery-boot mode. The AI sandbox is likewise implemented/unit-tested but not VM-verified. NVIDIA is not verified.

  • A separate physical computer for the OpenCode transport test is not available (BLOCKED); a forwarded-hop + unauthenticated-LAN-refusal host-local test was done instead.
  • The GUI bridge reaches Quickshell via Process + /usr/bin/sudo -n; it relies on the live user's passwordless sudo. The live sudoers rule is still NOPASSWD: ALL (live-only); narrowing the broker permission is future work.
  • Harness artifacts live under /var/tmp/phoebus-vm/ (outside git): results.json, screenshot-manifest.json, report.html, screenshots.

Environment notes

  • Dev host: Ubuntu 26.04. QEMU/OVMF/xorriso/rustfmt/clippy/ImageMagick present.
  • Debian-Live base ISO is cached at /home/dominic/debian-live-standard.iso (matches installer/live/base.sha256); the appliance ISO builds without root.
  • Local QML iteration: /tmp/opencode/run-qml.sh <config-dir> runs a config on a nested Mango over the host X11 using the built rootfs libraries, and grim captures it. The sanctioned verification is the disposable VM.
  • VM harnesses: installer/tests/vm/gui-driver.py (graphical live ISO: gui/install/boot), appliance-driver.py, serial-driver.py. DISK must be a disposable qcow2; never point it at /dev/*.
  • Serve the install fixtures from /home/dominic/vmlab/serve with python3 -m http.server 8000 --bind 127.0.0.1 (reachable as 10.0.2.2:8000).

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).