Commit graph

42 commits

Author SHA1 Message Date
fc36f637b4 test(rollback): add rollback and no-model recovery acceptance harness 2026-09-22 07:56:11 -07:00
1d37fbc1b8 ci(release): fail closed and bind gates to the candidate artifact
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.
2026-09-22 07:34:27 -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
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
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
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
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
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
639cb330fd docs: record the 2026-09-21 appliance baseline (INSTALL-RC=0, detached boot, initial snapshot)
Some checks are pending
ci / test (push) Waiting to run
2026-09-21 04:22:21 -07:00
25f7381b4a feat(desktop): add Mango + DankMaterialShell profile with rollback, assistant and release foundations
Some checks are pending
ci / test (push) Waiting to run
- 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.
2026-09-21 03:46:52 -07:00
b12b2768b4 feat(nix): default Nix on; flush finalize writes before unmount
Some checks are pending
ci / test (push) Waiting to run
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.
2026-09-20 22:35:46 -07:00
fea647ac7d docs: record the rebuilt ISO and the gated Nix bootstrap
Some checks are pending
ci / test (push) Waiting to run
2026-09-20 14:52:18 -07:00
0718bb34e5 feat(nix): gated bootstrap of the pinned Nix release
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.
2026-09-20 14:50:57 -07:00
32a124e3f9 docs: fix handoff numbering
Some checks are pending
ci / test (push) Waiting to run
2026-09-20 14:44:00 -07:00
f8b34635c7 docs: record the mandatory-AI gate, local provider and portals
Note the rebuilt appliance ISO (fec8e312) and the new desktop portals; add
Nix packaging as the top next task since it was deliberately not faked.
2026-09-20 14:43:34 -07:00
d36b2fe5fe docs: one control plane — sys typed actions, not raw Portage
Some checks are pending
ci / test (push) Waiting to run
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.
2026-09-20 14:35:05 -07:00
0c2a6bb9d6 docs: require an AI at install; AI-first system, legacy fallback
Some checks are pending
ci / test (push) Waiting to run
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.
2026-09-20 14:33:19 -07:00
9ae86d5234 docs: ship no model; make the assistant model-optional
Some checks are pending
ci / test (push) Waiting to run
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.
2026-09-20 14:29:59 -07:00
15cc9ec58c feat(sys): add offline Portage install/remove/search commands
Some checks are pending
ci / test (push) Waiting to run
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.
2026-09-20 14:28:35 -07:00
ab7408cdcf docs: make AI and Nix defining, offline-capable subsystems
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).
2026-09-20 14:27:02 -07:00
27795f7998 docs(live): record the Debian-Live appliance install and detached boot
Some checks are pending
ci / test (push) Waiting to run
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.
2026-09-20 13:49:49 -07:00
d6fa7c8dce feat(live): build a Debian-Live installer appliance ISO (no root)
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.
2026-09-20 12:49:31 -07:00
8dbf624046 docs: pin the handoff to this session's verification commit
Some checks are pending
ci / test (push) Waiting to run
2026-09-20 06:59:18 -07:00
b2f5181f7f docs: record the desktop VM session and AI guided-path verification
Add the detached-boot desktop verification (socket wait, polkit agent,
helper reaping) and pin the lockfile for the new phoebus-ai dependency.
2026-09-20 06:59:01 -07:00
b120c1e5e4 docs: record AI guidance, desktop reliability and snapshot verification
Update the status matrix, roadmap, changelog and handoff; add the WS4/WS3 VM
evidence and a concise real-VT desktop test procedure.
2026-09-20 05:03:37 -07:00
4cdce98e7f docs(migration): record Phases 0-4 complete in the session log
Some checks are pending
ci / test (push) Waiting to run
2026-09-20 04:01:03 -07:00
63c76e4a52 docs(migration): pin the Phase 4 evidence commits 2026-09-20 04:00:33 -07:00
fc64793aec docs: update references after retiring the Bash installer
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.
2026-09-20 04:00:19 -07:00
1e5337e7a5 refactor!: retire the Bash installer tree and relocate its docs
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.
2026-09-20 04:00:14 -07:00
fbffa5ca8f docs(migration): map the Bash tests to Rust coverage (Phase 3)
Record the test-to-coverage map, mark Phase 3 verified, and drop the Bash
installer from the contributor docs that are not under docs/.
2026-09-20 03:57:22 -07:00
9bda0496fb docs(migration): pin the Phase 2 evidence commit 2026-09-20 03:55:12 -07:00
54701bd1ef test(vm): record static-binary install and detached boot evidence
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.
2026-09-20 03:54:53 -07:00
f5ea6edf09 chore(docs): add evidence-gated Bash migration plan 2026-09-20 02:57:13 -07:00
bf8230f698 docs(git): hardening docs, backup timer and issue/PR templates
Some checks are pending
ci / test (push) Waiting to run
- 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.
2026-09-20 02:42:50 -07:00
83368f774c feat(git): add session context, host doctor, ADRs and git hygiene
Some checks are pending
ci / test (push) Waiting to run
Adds scripts/context.sh + 'make context' (one-screen session briefing),
scripts/doctor.sh + 'make doctor' (host prerequisites), docs/HANDOFF.md
(rolling cross-session note), docs/adr/ (BLS, desktop profile, keyring, Rust),
.githooks/commit-msg (Conventional Commits), .gitattributes, scripts/backup-git.sh
+ 'make backup', and a Forgejo Actions CI workflow. Updates AGENTS.md reading
order/work loop and DEVELOPMENT.md.
2026-09-20 02:36:32 -07:00
e680084f83 feat(git): add Forgejo API helper and one-command token setup
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.
2026-09-20 02:25:48 -07:00
2e3888feeb docs(git): record the Forgejo remote and clone/setup steps
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.
2026-09-20 02:12:21 -07:00
0e4fe009a8 build: add Makefile with common developer targets
Adds make help/test/check/build/static/hooks/commit/publish wrapping the
documented commands and the git workflow, and links them from DEVELOPMENT.md.
2026-09-20 02:08:36 -07:00
20bfd82079 docs: add objectives, roadmap, status, architecture and agent guide
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.
2026-09-20 02:07:44 -07:00