phoebus_os/docs/HANDOFF.md
Phoebus 25f7381b4a
Some checks are pending
ci / test (push) Waiting to run
feat(desktop): add Mango + DankMaterialShell profile with rollback, assistant and release foundations
- Mango + DankMaterialShell desktop option (desktop.profile = "mango") through
  the GURU overlay with scoped ~amd64 keywords, a sealed session entry point and
  a dwl fallback session (ADR 0009).
- Coherent rollback/recovery: coordinated @ + @var snapshots, fstab and BLS
  root-subvolume rewriting, matching-kernel selection, snapshot recovery entry,
  retention/space gates and sys undo (ADR 0007).
- Installed assistant (sys ask) with an OS-level systemd sandbox boundary and
  fail-closed typed plans; resolved package effects bound to approval.
- Nix build isolation enforced (sandbox, no fallback) plus lifecycle/cleanup.
- Desktop helpers (menu/lock/idle), transaction log, release gates with atomic
  publish and signing helpers, and a Debian-Live appliance VM harness.
2026-09-21 03:46:52 -07:00

67 lines
3.4 KiB
Markdown

# 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 `b12b276` + this session (2026-09-21)
- **Current focus:** coherent rollback/recovery, the installed AI assistant with
an OS-level sandbox, Nix build isolation, resolved package effects, desktop
completeness, and release gates. A new **Mango + DankMaterialShell** desktop
profile (`desktop.profile = "mango"`, ADR 0009) is implemented and selectable
with a dwl fallback; it is **not yet graphical-VM verified** and is not the
default.
- **Last verified:** static Rust binary install + detached boot
(`docs/VM-BOOT-VERIFICATION.md`); in this session additionally: a fresh
Debian-Live appliance install on a disposable qcow2 (recorded in
`docs/VM-BOOT-VERIFICATION.md` when it completes), plus unit/functional tests
for rollback, effects, transactions, the assistant schema, the sandbox argv,
and the desktop helpers.
- **Public repo:** <https://git.phoebus.club/phoebus/phoebus_os>
(remote `origin`, SSH port 2222).
## Next actions (in order)
1. **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).
2. **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.
3. **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`).
4. **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`.
5. **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`).