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).
Move the 4218-line shared service layer into focused modules with no
behavior change: mod.rs keeps the plan types, render, and shared helpers
with explicit re-exports so every phoebus_installer::service::* path,
the serialized plan format, approval digests, replay protection, and
privileged validation behavior are unchanged; plan.rs holds PlanStore
and the planning APIs; validation.rs holds seals, digests, and the
privileged validation boundary; execution.rs holds validated elevated
execution; tests.rs holds the regression suite verbatim. Sibling-private
helpers (constrain_action, plan_integrity, reviewed_steps,
validate_effect_bindings, ServiceConfirm) are pub(super) with explicit
imports; no glob re-exports.
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; plan_golden and adversarial digest tests
unchanged).
Box the CommandFailure payload so ExecError shrinks 128 -> 96 bytes and
Result<T, ExecError> passes result_large_err without per-site boxing.
Preserve the display text, redacted stdout/stderr capture, and the stderr
tail used for update failures; update the constructor and every match
site. Add regression tests for the error text, captured output, and the
96-byte size bound.
Resolve the remaining Clippy warnings without blanket allows: a type
alias for the snap-entry tuple in actions.rs, a CommandRecord params
struct for Logger::command in log.rs, and DiskPhase variant renames in
gui_bridge.rs. cargo clippy --workspace --all-targets -- -D warnings is
clean; cargo test --workspace passes (692 tests).
Unifies AI-first administration across the CLI (sys) and desktop GUI
(phoebus-assistant) through a shared service layer, fixes installed
desktop QML asset provisioning, adds Polkit elevation, and introduces
contextual conversation continuity.
- Extract phoebus_installer::service shared by CLI and desktop assistant bridge:
- Reviewable plan staging (PreparedPlan) with SHA-256 cryptographic digests,
15-minute TTL expiration, and replay prevention (PlanStore).
- Pre-mutation system state revalidation binding execution strictly to the reviewed plan.
- Honest recommendations displaying genuine provenance and unmeasured compile times.
- Two-phase transaction logging (begin before mutation, finish with verification).
- Provision installed desktop assets and Polkit policy in phoebus-executor::desktop:
- Added gui-apps/quickshell to canonical Mango desktop packages.
- Embed 13 QML and policy files into target root under /usr/share/phoebus/assistant/.
- Installed Polkit policy (club.phoebus.sys.policy) allowing unprivileged users to
authenticate mutating plans via pkexec without blanket passwordless sudo.
- Eliminate startup freeze and polling in phoebus-assistant:
- Multi-source update queries moved to on-demand tab switching.
- Handshake timer reduced to one-shot 100ms with fast deterministic check.
- Add phoebus_installer::conversation:
- Bounded 10-turn history with credential redaction.
- Contextual follow-up resolution for comparisons, backend switching, and confirmation.
- Implement unified cross-source removal (plan_removal) preserving user data by default.
- Verified: all 486 workspace tests pass, release and crt-static builds succeed,
and 23/23 VM acceptance cases pass (PASS=23 FAIL=0).
- Default natural-language and conversational routing for sys install, sys please install, and sys ask through shared AI workflow
- Constrain AI candidate evaluation when source flags are supplied without bypassing the model
- Enforce explicit --legacy flag for deterministic administration; legacy install without a source flag refuses execution and offers choices
- Audit --action and --action-file entry points to require --legacy or --broker
- Provide truthful guidance on absent or failing AI models without silent mutation or unverified fallback
- Implement package correctness safeguards: Nix attribute evaluation probe, Portage binary check with source compile abort guard, cross-source installed application tracking, and data preservation on removal
- Provide Quickshell desktop assistant (phoebus-assistant) backed by stdio JSON-RPC bridge (sys --assistant-bridge) and desktop integration
- Implement unified multi-source update checking across all package lanes
- Implement quiet proactive assistance monitor with alert deduplication and snoozing
- Expand acceptance suite in installer/tests/vm/sys-acceptance.sh to 22 cases (22/22 PASS)
Record the disposable-VM evidence for the AI-first install workflow: the
deterministic install, the explicit --portage install/remove journey with a
protective snapshot and durable history, the no-model offer, the read-only
investigation actions, and the 19/19 acceptance matrix. Note the AI-selected
journey as the remaining gate (needs a connected provider).
- chooser: keep the plain Portage install atom and record the version
separately. emerge rejects a bare versioned atom (app-misc/hello-2.12.3), so
resolve/split now produce app-misc/hello + version 2.12.3.
- effects: parse emerge --unmerge --pretend output (it does not use the
[ebuild] form), so sys remove has a concrete plan instead of being refused as
unestablished.
- action: reject unknown fields on internally tagged unit variants
(deny_unknown_fields does not cover them), closing a fail-closed gap.
- transaction: fsync the log so a completed outcome survives power loss and is
not later read as an interrupted operation.
- serial-driver: import re at module level (do_boot used it unqualified).
Add an executor test: resolve an explicit --portage plan, confirm verification
fails before the merge and succeeds once the VDB entry exists, so success is
never claimed from a zero exit alone.
The install harness drives the deterministic backend, which must pass the
documented --no-ai break-glass to satisfy the mandatory-AI install gate. The
previous invocation omitted it and the installer correctly refused.