P0 seat fix: sys-auth/seatd installed and enabled before greetd,
gui-libs/libseat with systemd+builtin+server USE, seat in default user
groups, greeter in video/input/render/seat, and a bounded 3 s seat wait
in phoebus-session-mango (LIBSEAT_BACKEND deliberately unset so every
compiled backend stays available).
P1 fast install: mail-client/thunderbird-bin replaces the source build
in workstation_packages; Thunderbird joins fast_default_deliveries and
SOURCE_CONVERSIONS (source target mail-client/thunderbird, honest
45-90 min estimate), the preference-neutrality guard covers it, and the
first-login welcome names it. All lanes and the mandatory-AI install
requirement are unchanged.
AI robustness: CurlTransport max-time 120 s -> 300 s default,
overrideable via PHOEBUS_AI_TIMEOUT (fail-closed parsing; zero refused)
for both direct and sandboxed sends.
Verified: cargo fmt --check, clippy --workspace --all-targets -- -D
warnings, cargo test --workspace 759/759 (was 757), bash -n on the
session script. Seat-VM reverification, thunderbird VM journeys, and
live CPU-inference proof are NotRun (no VM run this session).
Fixes the %F{ yellow } color bug (Phoebus Gold 214), drops the no-op
site-functions probe, puts fpath before a cached compinit (full audit at
most once per 24h), adds Kitty/application-mode keybindings, replaces
cross-tab SHARE_HISTORY with INC_APPEND_HISTORY, and adds a builtin
vcs_info git branch plus an exit-status prompt arrow. New ZSH_ZPROFILE
bridges /etc/profile (env-update paths, Nix/Flatpak profile.d) into Zsh
login sessions and adds ~/.local/bin to PATH. Seeding stays once-only;
root stays on Bash; /bin/sh untouched.
Verified: cargo fmt --check, clippy --workspace --all-targets -- -D
warnings, cargo test --workspace 757/757, zsh -n on both files plus an
interactive startup smoke test on host zsh 5.9. Installed-session
behavior awaits the disposable VM.
Phoebus stays systemd-boot + BLS (proven baseline, ADR 0002); external GRUB
chainloads EFI/systemd/systemd-bootx64.efi so sys undo BLS rewrites (ADR
0007) keep working and LUKS2/Argon2id is never exposed to GRUB cryptodisk.
The direct-kernel alternative is documented as fragile with the correct
rd.luks.name command line. No installer change.
The gate could pass vacuously: the guest ran unprivileged (every
mutation refused), used a pre-installed break package, restored the
newest snapshot instead of its own, and the driver never asserted the
root marker was gone. Now the driver authenticates sudo with unique
end markers and a verified timestamp, both phases run as root with
explicit --legacy, the break uses app-misc/hello (verified absent,
verified changed), undo targets the recorded snapshot id, and the
driver asserts the break changed the package DB and the root marker
is absent after the detached reboot.
Live image ships gnupg plus the Gentoo release key, fingerprint-checked
at build time against the published release-key fingerprints, so the
fail-closed DIGESTS verification cannot be silently skipped.
Rollback harness: authenticate sudo (unique end markers, verified
timestamp, abort instead of hanging), run both guest phases as root,
use explicit --legacy for snapshot/break/undo, fix the verify SYS path,
emit the real systemd state, and preserve the phase-1 transcript.
The installed boot path is plain unsigned BLS. kernel.uki=true and
kernel.secureboot=true are now rejected by validate_config (which the
CLI, TUI and GUI bridge all share) with errors naming the limitation.
The plan preview reports the real BLS path unconditionally and never
renders the requested flags as active. Golden plan updated; parsing,
validation and rendering regressions added.
The unpinned stage3 path warned and continued when the DIGESTS download
failed, when no SHA-512 entry matched, when gpg or the Gentoo release key
was missing, when the key import failed, and when gpg could not start.
All of these now stop the install before extraction, as do a bad
signature and a hash mismatch. The pinned path requires a valid 64-hex
pin (placeholder refused) before any network use. require_tools covers
gpg/sha256sum/sha512sum and stage_install checks them first.
16 regression tests cover every failure branch (nonzero exit and
cannot-start for hash, probe, import and verify) plus both positive
paths.
Changelog entry for the 2026-09-26 refactor; STATUS corrected to the
current 38-case sys matrix with the new static-binary evidence; VM boot
verification gains the sys-acceptance-refactor run; handoff updated.
Verified with cargo test --workspace (692/692) and the disposable-VM
matrix (guest PASS=38 FAIL=0, driver PASS=41 FAIL=0).
Move the 2763-line typed GUI bridge into focused modules with no UI or
wire-format change: mod.rs keeps the docs and re-exports so
gui_bridge::{Bridge, run_stdio, PROTOCOL_VERSION} paths are unchanged;
protocol.rs holds protocol version 1, the request/secret types, the JSON
progress observer, the disk-change phase, and the newline-delimited JSON
writer; bridge.rs holds the single Bridge owning the installer, request
dispatch, installation support, secret handling, and progress events;
tests.rs holds the regression suite verbatim. Items shared across the
boundary are pub(super) with explicit imports; no glob re-exports and no
service.rs-style leftover file.
cargo fmt clean; cargo clippy --workspace --all-targets -- -D warnings
clean; cargo test --workspace passes (692 passed, 0 failed, identical
to the pre-split baseline).