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).
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.
The no-model fallback is the Phoebus deterministic CLI (sys) running the same
typed actions the assistant emits, exposed as an explicit non-AI (legacy) mode.
Raw emerge/nix/flatpak remain a last resort rather than the intended front-end.
Installing Phoebus now requires a connected model (remote provider or a
user-downloaded local model; none is shipped). The installed system is AI-first
and uses a connected model proactively. It is never required to boot, run or
recover: the deterministic CLI (sys, emerge, nix, flatpak) remains as a
break-glass fallback, and no model ever holds privilege.
The AI assistant stays a defining, always-present subsystem, but Phoebus
ships no model. The user may download a local model or configure a remote
provider; with no model the assistant still explains, plans and applies
deterministic changes and the CLI remains available. Installation requires the
network; the installed system must boot, run and recover offline.
sys install <name>, sys remove <name> and sys search <query> are
deterministic and model-free: Portage resolves a bare name or a full atom.
Adds the remove_package and search_packages typed actions (remove is High risk
and gets the protective snapshot; search is read-only). This is the
old-fashioned fallback so the system stays fully administrable with no LLM.
AI and Nix are now always-present parts of Phoebus (not optional add-ons):
the assistant ships with a local model so it works offline and in recovery,
and Nix is a second package lane shipped and updated through Portage.
Installation needs the network; the installed system must boot, run and
recover without it. The assistant is the preferred front-end, never a gate:
the deterministic CLI (sys, emerge, nix, flatpak) is always available. The
model still never holds privilege. Records ADR 0006 (package lanes).
The appliance ISO firmware-boots, installs (INSTALL_RC=0, NO_SECRET_LEAK) and
the installed disk boots detached as Gentoo-only (Portage, no apt, systemd
running, 0 failed units). Two anomalies are recorded rather than hidden: the
target hostname and a first-boot DHCP timing observation.
Add installer/live/build.sh: overlay the static installer, the OpenCode
manifest and the Debian tools the standard live image lacks (cryptsetup,
btrfs-progs, gdisk, dosfstools, parted, util-linux-extra) onto a Debian-Live
stable base, patch the boot config for a serial console, and preserve the
hybrid BIOS+UEFI boot. The live squashfs is never repacked and libc is never
bundled, so the appliance is unchanged and the target remains Gentoo-only.
Records ADR 0005 and the implementation plan.
Point AGENTS.md, README.md and the docs at the Rust-only toolchain and the
moved VM-BOOT-VERIFICATION.md, and drop the Bash installer from DEVELOPMENT.md.
Delete installer/bin, lib, tui, config, tests/*.sh and README.md now that the
Rust installer is the only proven path (docs/BASH-MIGRATION.md Phase 4). Move
FINDINGS.md and VM-BOOT-VERIFICATION.md to docs/ and delete the Bash-only
TESTING.md. The disposable VM harness under installer/tests/vm/ is retained.
The committed harness now installs with the static Rust binary and boots the
disk detached: systemd PID1, running, 0 failed units, LUKS2 unlock, login and
networking. Also fixes the boot check marker so expect() does not match the
shell's echoed command.
- scripts/backup-timer.sh installs/removes a daily systemd user timer running
scripts/backup-git.sh (enabled locally; DEST should be a synced folder).
- .forgejo/ISSUE_TEMPLATE/*.md and PULL_REQUEST_TEMPLATE.md with a safety
checklist.
- docs/GIT-WORKFLOW.md: branch protection, CI runner, SSH commit signing,
backup timer and recommended git configuration.
Adds scripts/forgejo.sh: 'init' prompts for the token with hidden input,
stores it 0600 at ~/.config/phoebus/forgejo.token, verifies the account and
makes the repository public. Also whoami/repo-info/set-public/list-repos/
create-repo/create-release, using a 0600 temp curl config so the token never
appears in argv, logs or history. Wires make forgejo-init/public/release and
documents the flow in docs/GIT-WORKFLOW.md.
Documents git.phoebus.club:phoebus/phoebus_os (SSH via the port-2222 alias),
push-to-create visibility, publish.sh usage and the post-clone hook setup.
Adds the documentation a new session needs: AGENTS.md (read-first contract), docs/OBJECTIVES.md, ROADMAP.md, STATUS.md, ARCHITECTURE.md, DEVELOPMENT.md, CONTRIBUTING.md, GIT-WORKFLOW.md and CHANGELOG.md.
STATUS.md records an honest implemented/unit-tested/VM-verified matrix and known limitations.