Make a passing CI/release result mean the checks actually ran.
- .forgejo/workflows/ci.yml is fail-closed: it provisions the pinned
toolchain or fails, then runs one 'make ci' (fmt-check, clippy, workspace
tests, VM-harness safety tests, release build, static installer build).
- Pin stable Rust 1.93.1 in installer-rs/rust-toolchain.toml; run cargo gates
with --locked for reproducible dependencies.
- phoebus-release gates now records passed/failed/blocked/skipped/not_run
(only passed is a pass), executes real host gate commands, and imports the
existing VM-harness results.json instead of a competing harness. Gates with
no automation are always blocked.
- Bind gate reports and harness evidence to a candidate name+SHA-256
(--candidate; PHOEBUS_VM_ARTIFACT[_SHA256]); stale or unbound evidence is
failed, never passed.
- publish refuses unless the report is candidate-bound and all-passed, the
manifest verifies the artifact and a detached signature verifies; atomic
publish preserves and restores the previous release on failure.
- vmsafety.Results records the verified artifact digest; 3 new Python tests.
- 20 new Rust regression tests; ADR 0012 and docs updated.
Verified locally: make ci (364 Rust tests, 19 harness tests, release and
static builds) exit 0; static binary is static-pie linked. CI runner, VM and
model gates remain unexecuted here.
A fully-validated OpenCode install was refused at the final step because
selecting a disk or setting the account/LUKS secrets cleared the AI
validation. Bind the validation to a digest of only the AI connection
settings: non-AI config changes preserve it, while an AI provider/model/
endpoint/server or AI-credential change invalidates it. Add regression
tests and password-length placeholder hints.
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.
Select the OpenCode adapter from canonical config in ai_check/ai_test;
add --ai-backend/--opencode-* flags to the installer and sys. Require a
validated interaction (not a provider name) for the mandatory-AI gate in
both the bridge and the CLI, invalidated by config, model or credential
changes. Tests cover the gate, invalidation and the OpenCode backend.
The tiled welcome window was not keyboard-focused, so the primary action
had no focus ring and Return did nothing; request activation and force
focus. Refuse Escape during the destructive phase and say the operation
cannot be cancelled. Show the AI connection guidance beside the controls.
Guard the fixes with live_iso tests.
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).
Consume the approval before destructive work and refuse a second
start_install from a retry, a second frontend or a reconnect. Bound
request lines and secret values; reject deeply nested JSON. Add
regression tests for replay, oversized input and nesting.
probe_disks parsed lsblk human-readable sizes as bytes, so every disk
reported 0 B and the size-based identity check was blind; pass -b.
Re-probe the selected disk immediately before the destructive stage and
refuse if it disappeared, became protected (mounted/read-only/live) or
changed size/model since the review. Add regression tests for each case.
Add a branded live welcome window and a Quickshell/QML installer frontend
over a narrow, fail-closed JSON bridge (phoebus-installer --gui-bridge)
that reuses the same InstallConfig, plan, validation, authorization and
staged executor as the TUI/CLI. Add the Phoebus brand system (emblem,
wordmark, wallpaper, tokens), suppress DMS first-run dialogs on the live
medium, identify the live medium as protected, make the installer
shortcut live-only, and fix the installed boot default so systemd-boot
never selects the recovery entry.
Verified in a disposable graphical VM (welcome/installer journey,
duplicate prevention, keyboard navigation, blocked AI prerequisite) plus
a real non-interactive install and detached boot (INSTALL-RC=0,
NO_SECRET_LEAK, systemd running, 0 failed units, LUKS2, Btrfs, network).
- desktop.profile defaults to mango with Flatpak on; explicit none/minimal/dwl/
full still win. The plan shows the selected session.
- Installed login uses greetd + tuigreet (authentication required, Mango default,
dwl selectable); live autologin is a separate live-only configuration.
- installer/live/build.sh builds a rootless Debian testing rootfs with Mango
(pinned source build), DankMaterialShell (pinned SHA-256 release), Quickshell,
scenefx, Qt Wayland and greetd, then splices it into the base Debian-Live boot
equipment. Live autologin, an Install Phoebus launcher and a serial/VT
recovery console are included and the build fails clearly if a desktop
component is missing. Verified in a graphical seat-providing VM (Mango + DMS +
Quickshell; DMS panel captured).
- Shared desktop assets emitted by phoebus-installer --emit-asset, a graphical
VM driver (live-driver.py), and regression tests for defaults/overrides,
login, live/installed separation and the live ISO guards.
- Docs updated: ADR 0005/0009, STATUS, HANDOFF, CHANGELOG, ROADMAP, DEVELOPMENT
and VM-BOOT-VERIFICATION.
- 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.
Nix is on by default (NIX_ENABLED=no opts out); a desktop VM verified
nix-daemon active and 'nix shell nixpkgs#hello' -> Hello, world!. Create
/nix/var/nix/daemon-socket (the unit's ConditionPathIsReadWrite) and the
.wants links. finalize now runs sync before unmounting so the session script
and exported log are durable across a forced poweroff.
A binary ebuild is impossible (the upstream installer has no DESTDIR and runs
nix-store --load-db against the real root), so bootstrap the pinned,
SHA-256-verified official release with discrete commands in the target chroot
(no curl|sh, no sh -c): store copy, DB load, nixbld users, profile wiring and
nix-daemon units. Gated behind packages.nix (default off) until VM-verified.
Installing Phoebus now requires a connected model: the install gate refuses
with no provider unless the explicit break-glass --no-ai (alias --legacy, or
PHOEBUS_NO_AI=1) is used. Add a 'local' provider kind (Ollama/llama.cpp/
LM Studio) with an optional API key and --ai-endpoint override, so a user can
run a model they downloaded; no model is shipped. Desktop installs now include
xdg-desktop-portal + gtk/wlr backends for Flatpak and Wayland apps.
Deterministic review now rejects encryption=none, filesystem=ext4 and the
aggressive kernel profile, so the LUKS2/Btrfs/stability posture cannot be
traded for convenience. A live provider that returns an invalid proposal is
reported and the installer continues with the proven defaults (the explicit
--ai-proposal-file test path still fails loudly).
Add an OpenAI-compatible provider layer (DeepSeek, OpenAI and a test
transport) that sends only bounded system facts and injects the API key via a
curl config on stdin, never in argv, config or logs. Extend the typed proposal
schema with scoped package.use, build jobs and binary-package preference; every
change now needs a non-empty reason and duplicates are rejected. Wire
--ai/--ai-proposal-file/--ai-facts into the CLI and add provider selection to
the TUI. Deterministic validation and review are unchanged: the model never
reaches the executor and the no-AI path keeps working.
Drop the unused installkernel uki flag (BLS uses uki_generator=none), remove
the empty wireplumber line and the duplicate pipewire entry, and add scoped
package.use plus explicit build jobs to the typed config. The binhost URI is
now derived from the selected profile when unset. No change weakens signature
verification or enables ~amd64.
High-risk sys actions now create their protective snapshot inside
actions::execute and abort if the .snapshots subvolume exists but the snapshot
fails, instead of warning and mutating anyway. Corrupt snapshot history is
surfaced as an error rather than being silently treated as empty.
Remove the Bash test suite and shellcheck from CI, the pre-commit hook, the
Makefile, agent-commit and publish. CI now runs cargo fmt, clippy and test.
parity.rs compared the Rust plan to the Bash installer. The Bash tree is
being retired, so pin the exact Rust plan and destructive preview to golden
files instead (UPDATE_GOLDEN=1 to regenerate).
Initial public import of the proven Bash installer (installer/) and the production Rust workspace (installer-rs/). The reference ISO, build output and local agent transcripts are gitignored.
Verified: installer/tests/run_tests.sh and cargo test --workspace both pass.