- Introduce SystemLock with safe PID-liveness detection via /proc/<pid> to prevent concurrent mutation collisions and reclaim stale locks
- Coordinate paired @ and @var Btrfs snapshots for all high-risk mutations to prevent Portage VDB database drift during rollbacks
- Persist transaction log via tempfile + sync_all + atomic rename to ensure durability against unexpected power loss
- Add SystemAction::SystemStatus and sys status/health query reporting boot assessment counters, reboot state, storage headroom, and package lane readiness
- Unify natural language verbs (update/updates -> CheckUpdates, upgrade -> ApplyUpdates) and dynamic candidate-aware legacy install guidance
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.
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.
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)
- 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.
Implement the shared installation workflow (ADR 0013). sys install, sys ask
install and the explicit backend flags all use one path: identify -> evidence
-> AI investigation -> deterministic validation/effects -> review -> approval
-> execute -> verify -> history.
- phoebus-ai::install: bounded, multi-turn investigation. The model may request
typed read-only evidence (discover_candidates, inspect_candidate,
check_backend, inspect_installation), ask one bounded question about intent,
and must return a structured InstallProposal. Turn/request/size limits and
repeated-request detection bound it; a rejected proposal is revised.
- phoebus-core: add the four read-only investigation actions and strict
validators; add a transaction id; backend/kind wire names now match as_str.
- phoebus-executor::install: resolve_explicit (no model, no fallback),
resolve_deterministic and resolve_with_ai; validate_proposal re-resolves the
candidate against real metadata, rejects fabrication/ambiguity/staleness/
duplicates, maps it to the existing broker action, and binds approval to a
digest; revalidate + verify_installed. chooser gains per-lane friendly-name
resolution and structured evidence.
- transaction::begin/finish record an in-progress transaction before mutation.
- sys: --portage/--flatpak/--nix/--snap/--appimage/--ebuild (mutually
exclusive) bypass the model; an unqualified install consults the model and,
with none, prints the deterministic selection and installs nothing.
- The installer persists /etc/phoebus/install.toml; sys loads it and adds free
space, Wayland, usable lanes, saved preferences and recovery capability to
the bounded facts.
- Docs: ADR 0013, docs/SYS.md install sections and cases 23-31, CHANGELOG,
STATUS, HANDOFF, ROADMAP. New live-VM workflow check script.
Host gates pass: fmt, clippy (no new warnings), workspace tests, make test.
VM: verified the workflow CLI and read-only investigation on the reference
LiveGUI ISO; a full target install journey is running (see HANDOFF).
Replace the fixed category routing (ADR 0006) with a shared, inspectable,
hardware- and preference-aware selection policy over resolved candidates from
Portage (source/binary/vendor), Nix, Flatpak, Snap, AppImage and the Phoebus
overlay. The policy keeps base components under Portage, separates hard
constraints from preferences, honours and persists explicit choices, errors
instead of silently switching lanes, and reuses an already-installed lane.
- phoebus-core::selection: the pure policy (16 tests: base-system, low-memory
vs high-core, sandbox requirement, GPU/arch/storage rejection, explicit
preference, unavailable backend, reproducibility, render).
- phoebus-executor::chooser: resolves real metadata and hardware facts.
- phoebus-executor::{snap,appimage,ebuild}: new lanes. Snap detects daemon and
confinement and installs app-containers/snapd through Portage; AppImage
adopts images with a pinned SHA-256, checks the ELF architecture without
executing, integrates a desktop entry and preserves user data on removal; the
custom ebuild overlay binds approval to the ebuild content digest and builds
through Portage's sandbox.
- Typed actions choose_package / set_package_preference / snap_* / appimage_* /
custom_ebuild_* with strict validators; the assistant prompt and schema are
reconciled (no category routing; custom ebuilds are untrusted).
- Installed sys: the installer locates the trusted static binary, copies it to
/usr/local/bin/sys and proves it runs in the target chroot before the
recovery snapshot, failing closed if absent; the VM harness fetches sys.
- docs/SYS.md: command/action reference and acceptance matrix; ADR 0006 revised.
Host gates pass: fmt, clippy (no new warnings), workspace tests, make test,
release and static sys builds. VM lane journeys remain pending (see HANDOFF).
The installer wrote dracut force_drivers naming nvidia modules during the
first kernel build, before the driver package existed, so the initial
kernel/initramfs build could not resolve them. Only the NVIDIA install
stage installs the driver and regenerates the initramfs.
- dracut_conf() no longer emits the NVIDIA fragment; the modprobe policy
is still written before the kernel.
- write_nvidia_dracut_conf() writes it in the NVIDIA stage, after emerge
and before kernel-install add-all.
- verify_nvidia_modules() proves the driver actually built modules for a
kernel and fails the install otherwise; it returns the resolved version
from var/db/pkg so the record carries the real version, kernel and
module names rather than a 'current' label.
- The update path verifies the rebuilt modules before reporting success;
previous kernels and module trees are left in place.
The verifier accepted one-byte placeholder modules, a caller-supplied
version/flavor, any NVIDIA firmware file and a nouveau blacklist that
happened to exist somewhere. It now establishes what it claims:
- reject placeholder modules and userspace libraries (size floor);
- require every module to be registered in the live kernel's modules.dep;
- normalise the dpkg revision and require the userspace libnvidia-glcore
and firmware directory versions to match the bundled driver;
- infer the module flavor from the on-disk naming and reject a
contradiction;
- require the exact etc/modprobe.d/phoebus-nvidia.conf with nouveau
blacklist and nvidia_drm modeset, not any blacklist;
- keep every filesystem read rooted inside the build root.
Negative tests cover placeholders, version mismatches, a stale
modules.dep, a contradictory flavor and a missing final config.
The live load script previously modprobed the NVIDIA stack for any PCI
vendor 0x10de and the build required etc/modprobe.d/phoebus-nvidia.conf
that nothing created. Replace the vendor-name check with a deterministic
decision computed from the actual display controllers and the bundled
branch's capabilities:
- phoebus-core gains live_nvidia_plan(): supported GPU -> load the
bundled accelerated stack; unsupported GPU -> explicit nouveau
fallback; no GPU -> leave auto-detection; fail-safe -> load nothing.
- phoebus-installer --live-gpu-plan scans sysfs (overridable for tests)
and prints stable key=value lines; probe_nvidia_display_devices() only
considers display-class NVIDIA functions.
- phoebus-nvidia-load consults it, falls back to nouveau on an
unsupported GPU or a failed accelerated load, and never fails the
unit; the service honours phoebus.nvidia=off.
- build.sh now creates the live modprobe policy, replaces Debian's
unconditional nouveau blacklist, and marks the fail-safe entry.
- resolve the NVIDIA branch and kernel-module flavor from PCI device IDs
(Turing+ open modules; Maxwell/Pascal/Volta proprietary, masked below 595;
Fermi/Kepler fall back to nouveau, reported; unknown IDs reported)
- capture pci_id/pci_address in the probe; drive VIDEO_CARDS, package.use,
package.accept_keywords, package.mask, modprobe.d and dracut from the plan,
preserving hybrid Intel/AMD
- add the nvidia_drivers install stage (after the kernel, before boot) that
emerges the driver, regenerates the initramfs, records /etc/phoebus/nvidia and
fails the install on failure; sys update rebuilds modules and the initramfs
- refuse AI changes to x11-drivers/nvidia-drivers
- live ISO: signed non-free components, stable-kernel pin (testing 7.2 breaks
the 550 driver), DKMS build for the exact kernel, gated pre-greetd load,
fail-safe entry, gpu-report, and a --verify-live-nvidia build gate that runs
on cached rootfs builds and fails on any missing component
- docs: ADR 0012, STATUS/CHANGELOG/HANDOFF, live README
- also carries the pending OpenCode model-variant/streaming changes and fixes
the GUI bridge install thread join that could hang
The region and keyboard fields were free-text, so users had to know zone
names and layout names from memory, and the AI model had to be typed.
Add an 'options' bridge op (live timezones/locales/keymaps) and an
'ai_catalog' op (the OpenCode provider/model catalog, or an
OpenAI-compatible /models list), and a searchable PhoebusCombo picker.
Also name provider/model in OpenCode errors instead of an opaque HTTP
code. Record the user-trial findings U1-U5.
Integration tests drive the curl client against a local TCP server
(status preservation, chunked multibyte bodies, oversized bodies,
redirects, abrupt disconnects, authentication). The live tests obtain a
real model response when PHOEBUS_OPENCODE_LIVE_* is set and fail as
BLOCKED when a live run is required but not configured.
OpenCode is an agent server, not an OpenAI endpoint. Add a session/
message client over the established curl transport that implements
ModelTransport, so the strict proposal parser, facts and review are
reused. The probe enforces the loopback/TLS transport policy, pins the
resolved address, supports basic auth, checks HTTP status before parsing,
and reports truthful connection states (ready is reserved for a validated
response). Accept only completed assistant text parts and delete the
transient session on every path. Tests cover endpoint/policy, auth, a
misleading 500, credential non-leakage and the request shape.
OpenCode is an agent application, not an OpenAI-compatible endpoint. Add
a typed probe over /global/health and /config/providers that distinguishes
disconnected, authentication required, incompatible, reachable-no-model and
ready, and never returns provider credentials. Expose it as
phoebus-installer --opencode-probe. Document the four components, host and
tunnelled remote workflows, and the Phoebus assistant boundary (ADR 0011).