5.3 KiB
5.3 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-24), End-to-end graphical installation
and detached first-boot verification: full 6-step graphical wizard completed
(all 12 stages, 174 packages), detached first-boot verified (systemd running,
LUKS2 unlock,
sysoperational,tuigreetactive), greetd TOML syntax fix, and live ISO freshness automation. - Current focus:
- 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. - Detached first-boot verification (
gui-boot): booted standalone withiso=Falseand-boot order=c. Verified firmware -> systemd-boot -> LUKS2 decrypt -> Btrfs subvolumes (@,@home,@var,@snapshots,@swap) -> systemdrunning(0 failed units) -> serial login ->sysoperational. - Greetd greeter fix: single-line command string in
/etc/greetd/config.tomlresolving TOML basic string multiline error; verifiedtuigreetrendered cleanly on the booted system (01-boot-desktop.png). - Live ISO freshness invariant:
scripts/ensure-live-iso.shautomatically recompiles static binaries and repacks the live ISO whenever source files are newer than the ISO. - Fast installation kernel profile: default kernel profile set to
KernelProfile::Safe(sys-kernel/gentoo-kernel-bin), preventing 100+ min kernel compilation from source during installation.
- Full graphical install journey (
- Last verified (this session):
cargo fmt --all -- --check,cargo clippy --workspace --all-targetsandcargo test --workspace(508 tests pass across all crates).- Live ISO repack:
installer/live/phoebus-installer-amd64.isofresh and verified. - Full graphical installation:
gui-gui-install-20260924T144711Z-feab515b(gui-install-completesPASS,07-gi-07-complete.pngcaptured). - Standalone detached first boot:
gui-boot-20260924T183545Z-4b5de282(6/6 PASS, systemd running,sysbinary operational,tuigreetactive).
- Not yet verified this session: the AI-selected journey
(
sys install <app>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: https://git.phoebus.club/phoebus/phoebus_os
(remote
origin, SSH port 2222).
Next actions (in order)
- AI-selected install journey (needs an authorised provider): boot the
installed disposable disk (
/var/tmp/phoebus-vm/disks/test-disk.qcow2), serve the builtsysand a 0600 key file, then:
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.sudo sys --ai-provider deepseek --ai-api-key-file /run/phoebus/ai.key \ install <application> # and the no-model control in the same run: PHOEBUS_AI_PROVIDER= sudo sys install <application> - Rollback VM acceptance (
serial-driver.py rollback) on a cloned disposable image of the installed system. - NVIDIA hardware acceptance (BLOCKED): needs an NVIDIA GPU.
- 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 installjourneys 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.
flatpakandsnapclients are present on the host (not proof of the VM lanes). - VM harnesses:
installer/tests/vm/{gui-driver,serial-driver,appliance-driver,live-driver}.pyandsys-acceptance.sh.DISKmust be a disposable qcow2; never/dev/*. - Serve fixtures from
/home/dominic/vmlab/servewithpython3 -m http.server 8000 --bind 127.0.0.1(reachable as10.0.2.2:8000). - The static binaries for the VM:
make staticbuildsphoebus-installerandsysunderinstaller-rs/target/x86_64-unknown-linux-gnu/release/.
Definition of a good stopping point
make testpasses;docs/STATUS.mdanddocs/CHANGELOG.mdupdated;docs/HANDOFF.mdupdated; committed (viascripts/agent-commit.sh) and pushed (scripts/publish.sh).