Commit graph

149 commits

Author SHA1 Message Date
fe8de3904b refactor(desktop): unify desktop stack on Mango + DarkMaterial and excise standalone dwl
Some checks are pending
ci / test (push) Waiting to run
- Excised standalone dwl packages: gui-wm/dwl, waybar, wofi, mako, swaybg, swayidle, swaylock
- Removed standalone dwl session and helper assets: PHOEBUS_SESSION_SCRIPT, PHOEBUS_MENU_SCRIPT, PHOEBUS_LOCK_SCRIPT, PHOEBUS_IDLE_SCRIPT, WAYBAR_CONFIG, WAYBAR_STYLE, phoebus-dwl.desktop
- Consolidated DesktopProfile enum to Mango (default) and None (headless), rejecting legacy dwl configurations
- PHOEBUS_MANGO_SESSION_SCRIPT (/usr/local/bin/phoebus-session-mango) fails visibly/diagnostically on error without silent fallback
- Provided /usr/local/bin/phoebus-session as a direct wrapper to phoebus-session-mango
- Live ISO emitted assets reduced from 24 to 17 and verified clean
2026-09-24 15:49:15 -07:00
b5dd264681 feat(gui): verify full graphical install, fix greetd TOML, and automate ISO freshness
Some checks are pending
ci / test (push) Waiting to run
2026-09-24 11:42:16 -07:00
3435d5aed1 docs: record the VM-verified install journey
Some checks are pending
ci / test (push) Waiting to run
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).
2026-09-23 21:42:11 -07:00
dedaa4bc48 fix: defects found by the VM install journey
- 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).
2026-09-23 21:40:42 -07:00
b4729e443d test(install): verify the explicit Portage plan end to end
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.
2026-09-23 20:32:24 -07:00
4934b4c221 test(vm): run the deterministic install with the --no-ai break-glass
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.
2026-09-23 20:31:07 -07:00
f9e39925b4 feat(install): AI-first sys install workflow
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).
2026-09-23 20:30:13 -07:00
8be9bb6444 fix(installer): detect the BLS kernel layout in target verification
Some checks are pending
ci / test (push) Waiting to run
The installed-target check scanned only the top level of /boot and /efi for
vmlinuz/kernel. With layout=bls, kernel-install places the kernel as
<boot>/<machine-id>/<version>/linux, so a correct install would have been
rejected. Scan the tree (bounded, without following symlinks) for linux/vmlinuz/
kernel, and accept a BLS entry that names a kernel.
2026-09-23 18:41:41 -07:00
a6ed363745 test(selection): cover divergent machines and the extended prompt
Some checks are pending
ci / test (push) Waiting to run
- add policy tests for missing hardware information, limited storage choosing
  the smaller candidate, and the same application resolving to Portage binary,
  source or Flatpak depending on the machine, preference and sandbox
  requirement.
- drop the always-on strong-sandbox bonus to a mild +3 so GUI apps are not
  effectively routed to Flatpak by category (ADR 0006 revision intent).
- keep the assistant prompt and a plan-acceptance test in sync with the
  extended action schema (choose_package, set_package_preference, snap_*,
  appimage_acquire, custom_ebuild_prepare).
2026-09-23 18:38:59 -07:00
297f3201ff feat(sys): hardware-aware lane selection and new lanes
Some checks are pending
ci / test (push) Waiting to run
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).
2026-09-23 18:35:26 -07:00
3b1b54ffb9 docs: reconcile NVIDIA, verification and harness status
Some checks are pending
ci / test (push) Waiting to run
Record the reliability pass across STATUS, HANDOFF, CHANGELOG, ADR 0012,
the live README and the boot-verification log: the deterministic live GPU
decision with a real nouveau fallback, the 580 legacy cap and mixed
open/proprietary incompatibility, the compatibility verifier, the
installed lifecycle fix, the repaired GUI harness, the automated but
unrun rollback gate, and the scoped live sudoers. Withdraw the stale
handoff claim that the gui_bridge tests hang (the workspace suite
passes) and record the installed-target missing-sys gap.
2026-09-23 06:28:30 -07:00
4265aefacd fix(live): scope the live privilege policy to the typed brokers
The live user had NOPASSWD: ALL for the graphical broker. Replace it with
an emitted, visudo-validated policy that grants unattended escalation only
to /usr/local/bin/phoebus-installer, /usr/local/bin/sys and the systemctl
power actions; no ALL, no sh -c and no wildcard. The recovery console is
preserved: it logs in with the live-only password and authenticates sudo.
build.sh installs the asset, validates it with visudo and refuses any
unscoped policy. The GUI harness stages its preseed config with the
password-authenticated sudo over a 0600 file instead of bare install, and
the read-only greetd check no longer needs sudo.
2026-09-23 06:22:19 -07:00
c759477c7f test(vm): automate rollback acceptance on a disposable clone
Add a serial-driver rollback mode and guest scripts that exercise the real
rollback path: record the /var/db/pkg fingerprint and a /home marker,
create a recovery point with sys snapshot, install a small package as a
controlled reversible update, run sys undo, power off, boot detached and
compare the restored package state and /home against the pre-rollback
values. Checks kernel modules, the snapshot recovery entry and sys
rollback status. sys is fetched from the host, matching the existing
harness evidence procedure; booting the recovery entry offline remains a
documented manual gate. bash -n guards for every guest script are added
to the no-VM unit tests.
2026-09-23 06:19:17 -07:00
a510efdea2 test(gui): drive the current six-step installer instead of the removed UI
The graphical harness still assumed a step-0 welcome, an ERASE field, a
confirmation checkbox, a full-name field and separate passphrase prompts
that were all removed. Update it to the current product:

- navigate with a state-based _goto_step() instead of counting
  Return/Ctrl+Right from a step that no longer exists;
- drive the real account fields (username, computer name, password,
  confirm) with the default single-password encryption, leaving the
  hidden passphrase fields alone;
- trigger the direct "Install now" action and drop the ERASE/confirm
  assertions, while still exercising duplicate submission;
- report stage, elapsed time and the last state on an install timeout;
- boot with the single-password disk passphrase (user password) and fall
  back to the separate passphrase, instead of always using LUKS_PW;
- remove the dead SESSION_SETTLE knob.
2026-09-23 06:16:30 -07:00
12f264a0e9 fix(nvidia): install the driver before forcing it into the initramfs
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.
2026-09-23 06:13:14 -07:00
33b0b1df77 style: cargo fmt the nvidia changes 2026-09-23 06:10:21 -07:00
5103b57be9 test(nvidia): make the live payload gate prove compatibility
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.
2026-09-23 06:09:54 -07:00
b32683da99 fix(nvidia): cap the legacy branch at 580 and reject mixed open/proprietary hardware
NVIDIA's 580 series is the last to support Maxwell/Pascal/Volta, and
Blackwell requires the open kernel modules. The policy previously masked
>=595, which permits branches that already dropped those architectures,
and assumed the oldest card's branch could serve every newer card.

- Mask >=x11-drivers/nvidia-drivers-581 for the proprietary branch (the
  first series after the last supporting one).
- Compute compatibility across the whole device set: Blackwell plus a
  proprietary-only GPU has no single branch and is reported as an
  explicit incompatibility (nouveau) instead of installing a driver that
  cannot accelerate one card.
- Pascal + Ampere remains proprietary and supported (Ampere accepts
  either flavor).
2026-09-23 06:06:51 -07:00
dc5e27e60a fix(nvidia): deterministic live GPU decision, nouveau fallback and fail-safe
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.
2026-09-23 06:05:27 -07:00
6e5c7d999f feat(installer): overhaul GUI to 6-step flow and resilient UX
Some checks are pending
ci / test (push) Waiting to run
- Streamline installer to direct 6-step flow, eliminating Step 0 duplicate welcome
- Parse friendly layout names from evdev.lst and sort top 30 world layouts first
- Enable dynamic live keymap switching via localectl on layout selection
- Auto-detect timezone and close sibling combos on dropdown expansion
- Remove redundant keyboard test modal from welcome application
- Default-enable single-password disk encryption and accept passwords under 8 chars
- Replace ERASE typing confirmation with direct 'Install now' action
- Enforce Mango desktop, Btrfs filesystem, and Flatpak/Nix invariants against AI mutation
- Add loopback OpenCode/Ollama auto-detection and humanized failure screen with Retry
2026-09-23 05:42:03 -07:00
28536e2c1f feat(gui): responsive low-res layout, display modal and hotkeys
Some checks are pending
ci / test (push) Waiting to run
2026-09-23 04:44:39 -07:00
86c477085c feat(gui): close welcome on launch and enforce installer fullscreen 2026-09-23 03:12:54 -07:00
9eaa844423 feat(gui): live output streaming, OpenCode variants, GURU fix 2026-09-23 02:36:51 -07:00
b4a6b5df80 feat(nvidia): hardware-driven driver policy, installed integration and live payload
Some checks are pending
ci / test (push) Waiting to run
- 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
2026-09-22 21:53:28 -07:00
040181abc2 feat(install): enforce Flatpak non-removable invariant across AI and UI
Some checks are pending
ci / test (push) Waiting to run
2026-09-22 18:52:00 -07:00
10269f3c21 feat(desktop): add reload_config keybindings to Mango default
Some checks are pending
ci / test (push) Waiting to run
2026-09-22 18:25:45 -07:00
3515f1cf12 feat(desktop): streamline installer UX and add DWM keybindings
Some checks are pending
ci / test (push) Waiting to run
- Add canonical DWM / DWL keybindings to MANGO_CONFIG_DEFAULT (Mod+Shift+Return
  terminal, Mod+Return zoom, Mod+j/k focusstack, Mod+Shift+j/k movestack, Mod+h/l
  setmfact, Mod+i/d incnmaster, Mod+Shift+c/q killclient, Mod+t/m/f layouts,
  Mod+Shift+Space float toggle, Mod+Tab view previous, Mod+1..9 tags,
  Mod+Shift+1..9 movetotag, mouse window drag/resize)
- Close Welcome window on installer launch to allow full-screen tiling
- Rewrite PhoebusCombo into a scrollable dropdown with search and vertical scrollbar
- Parse XKB rules (evdev.lst / base.lst) for standard desktop keyboard layouts
- Streamline installer defaults: lock to Mango + DankMaterialShell, Btrfs with
  snapshots, and Nix + Flatpak enabled (removing confusing manual choices)
- Simplify Account step: username only, single password with disk encryption toggle,
  and remove artificial 8-character password length limit
- Direct installation confirmation without typing ERASE or ticking confirmation box
- Fix live progress log details view with a dedicated scrollable log box and 1.5s timer
2026-09-22 18:17:31 -07:00
1106bcaa0a docs(verification): record the graphical journey results and host-time blocker
Some checks are pending
ci / test (push) Waiting to run
Update the changelog, status, handoff, verification register and VM boot
record with the 2026-09-22 graphical journey work: the fixed step sequence,
the interaction-defect fixes (readiness refresh, catalog sync/staleness, AI
revalidation, keyboard suggestion navigation, truthful keyboard-step label,
link vs service readiness, busy/failure handling), the new gui-install
harness mode, and the final-ISO results.

The gui (28/28) and opencode (18/18) journeys pass; gui-install passes every
journey assertion and starts a real install, but the four-hour harness timeout
fired during the kernel build (base packages ~116 min), so two completed
fresh-disk graphical installs + detached boot remain BLOCKED on host build
time, not on a code defect.
2026-09-22 12:30:55 -07:00
34c12d3dd8 feat(installer): rebuild the graphical journey and fix interaction defects
Rework the graphical installer into a fixed first-time-user sequence
(Welcome, Language and keyboard, Internet and readiness, AI connection,
Destination disk, Account and encryption, Review and confirmation,
Installation, Completion) with configuration, validation, plans, approval
and execution still authoritative in Rust.

Fix the audited interaction defects: readiness `Re-check` is a read-only
probe that no longer resets the step or clears the disk; model catalogs are
fetched after syncing the edited settings and credentials and stale replies
are ignored; editing a connection field invalidates the validated state;
suggestion lists support arrow/Enter/Escape with a visible highlight and
accessibility; the keyboard step labels the live-session limitation
truthfully; readiness separates the local link from reachable install
services; and busy states always clear, with the bridge failing outstanding
requests when the backend exits.

Add human-readable language/keyboard names, an explicit AI change review
(Accept/Discard), backend-fact review with edit links, real stage progress
with elapsed time and activity, and clearer failure and completion guidance.

Extend the VM harness with a `gui-install` mode that drives the whole
journey through the visible controls, plus regressions for readiness
refresh, disk survival, keyboard suggestion selection and AI invalidation.
Add Rust tests for readiness, the network probe, error kinds and labels.
2026-09-22 08:17:03 -07:00
4679f935e3 fix(sys): harden the administration broker and complete its command surface
Some checks are pending
ci / test (push) Waiting to run
2026-09-22 07:30:38 -07:00
b4935578ac fix(installer): do not discard the validated AI state on unrelated edits
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.
2026-09-22 04:13:31 -07:00
39c69d59cf feat(gui): pick timezone/locale/keymap and AI model from lists
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.
2026-09-22 03:57:01 -07:00
359f083bc2 test(gui): drive the OpenCode AI step through the real UI
Some checks are pending
ci / test (push) Waiting to run
Add an 'opencode' harness mode with a guest-loopback relay (the tunnel
shape), keyboard selection of the OpenCode chip, UI entry of the server/
provider/model (and a 0600 server password), and assertions on the
frontend's secret-free state (tested, validated, applied). Record the VM
evidence and the remaining not-run full-install gate.
2026-09-22 03:32:07 -07:00
802b843bc9 fix(ai): retry a rejected proposal once with a correction
The shipped DeepSeek models occasionally key a change or rationale wrongly.
Retry once with a corrective turn; the strict parser remains the final
authority and a retry that still fails is still rejected. Add scripted
transport tests for both the proposal and assistant paths.
2026-09-22 03:32:07 -07:00
c16014ade8 feat(gui): select and validate OpenCode from the installer
Add an 'OpenCode agent' choice with server/password/provider/model fields,
a Test connection action, and a secret-free frontend state line the
harness asserts. Require exactly one installer session and assert the
current step and AI state instead of inferring from a screenshot. Add a
live-OpenCode acceptance make target and document the adapter, transport
policy, states and workflows (ADR 0011 updated).
2026-09-22 02:36:36 -07:00
0d65d56eda feat(installer): wire OpenCode into the GUI, CLI and sys ask
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.
2026-09-22 02:36:29 -07:00
5c3674e3c2 test(opencode): real-HTTP and live inference tests
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.
2026-09-22 02:36:28 -07:00
565521564c feat(executor): implement the OpenCode agent-server adapter
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.
2026-09-22 02:36:22 -07:00
33afdaac9a feat(ai): add an OpenCode backend to canonical configuration
Add ai.backend (direct|opencode) plus opencode_server/provider/model
fields, distinct from the direct provider. Require the change-object
shape (action+value) in the proposal prompt: the shipped models keyed
changes by the action name otherwise.
2026-09-22 02:36:22 -07:00
fb4dcc5683 docs: record the 2026-09-22 harness, security and polish session
Some checks are pending
ci / test (push) Waiting to run
Update the changelog, status matrix, handoff and VM boot verification with
the 23/23 graphical journey, the hardened harness, the confirmed fixes and
the remaining blocked/unverified gates (full GUI install past AI, rollback,
installed desktop, physical second-computer OpenCode transport).
2026-09-21 20:01:58 -07:00
613e383082 fix(gui): focus the welcome action and refuse silent mid-install exit
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.
2026-09-21 20:01:58 -07:00
cc23df69de test(vm): enforce harness disk safety and structured results
Validate every writable drive (qcow2, inside PHOEBUS_VM_DISKS, no /dev/*,
block/char devices, raw images, escaping symlinks or outside backing
chains), give each run its own OVMF variable file, QMP socket and state
directory, and use QMP plus argument arrays instead of shell interpolation.
Return nonzero on any failed assertion, timeout, EOF or missing result and
record PASS/FAIL/BLOCKED/SKIPPED/NOT RUN. Add 16 unit tests, a report
generator and a findings register; make test runs the harness suite.
2026-09-21 20:01:50 -07:00
3d43f8c6c8 feat(executor): add an OpenCode server capability probe
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).
2026-09-21 20:01:44 -07:00
0a6725b049 fix(core): refuse symlink escapes in the target root
Reject a symlinked path component while writing beneath TargetRoot
instead of following it, so a planted symlink cannot redirect an
installer write to the host. Cover escaping directories and leaves.
2026-09-21 20:01:38 -07:00
9b5c1155b0 fix(ai): validate provider endpoints and bound the transport
Accept only http(s) endpoints and refuse URLs that could inject curl
config directives. Restrict the transfer to http,https, keep redirects
disabled (so a header cannot follow one to another origin) and bound the
response with max-filesize. Add endpoint and transport regression tests.
2026-09-21 20:01:38 -07:00
d395fd3464 fix(installer): make GUI bridge approvals single-use and bounded
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.
2026-09-21 20:01:38 -07:00
5ae166e827 fix(executor): revalidate the target disk before partitioning
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.
2026-09-21 20:01:32 -07:00
7e9fa9c2a3 feat(installer): graphical welcome and install wizard over a typed bridge
Some checks are pending
ci / test (push) Waiting to run
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).
2026-09-21 13:13:40 -07:00
0f6d503c2e docs(live): document the PHOEBUS_REUSE_ROOTFS build cache
Some checks are pending
ci / test (push) Waiting to run
2026-09-21 06:47:53 -07:00
bbd3d89d6a feat(desktop): make Mango + DankMaterialShell the default and build a live desktop ISO
Some checks are pending
ci / test (push) Waiting to run
- 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.
2026-09-21 06:47:22 -07:00