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.
4.9 KiB
4.9 KiB
Roadmap
Priority order is deliberate. Do not skip a higher item because a later one is more interesting. Status vocabulary: Done, Partial, Next, Later.
| # | Item | Status | Evidence / notes |
|---|---|---|---|
| 1 | Verify the Bash baseline | Done (retired) | tagged v0.1.0-bash-reference; retired with evidence in docs/BASH-MIGRATION.md |
| 2 | Build the Rust architecture | Done | installer-rs/ workspace, 5 crates |
| 3 | Port the deterministic core | Done | phoebus-core (config, plan, policy, validation, models) |
| 4 | Port the destructive backend | Done | phoebus-executor (storage, LUKS2, Btrfs, Portage, boot, users, services) |
| 5 | Rust VM boot parity | Done | Full encrypted UEFI install + boot, zero failed units, 10.7 s |
| 6 | Finish the desktop | Partial | Mango + DankMaterialShell is the default (dwl fallback); greetd login; the live ISO boots the branded welcome + graphical installer and was verified in a graphical VM; installed-desktop verification pending |
| 7 | Finish Flatpak | Partial | flatpak 1.18.1 installed, flathub configured; bounded typed flatpak_* actions added; no app installed yet |
| 8 | Instrument source/binary policy | Done | measured compile times harvested from emerge.log (326 entries); resolved-effect previews added |
| 9 | Background update preparation | Partial | distfile fetch VM-verified; --buildpkgonly skipped while deps need merging (recorded Ready); activation explicit |
| 10 | Snapshots / rollback | Partial | snapshot sets + history VM-verified on Btrfs; coordinated rollback, sys undo, recovery entry, retention and free-space gate implemented + unit-tested; destructive VM acceptance test pending |
| 11 | AI privilege and privacy architecture | Partial | typed actions + enforced privacy boundary + guided proposal review + OS-level sandbox (systemd-run hardening) + approval-bound resolved effects; live call/sandbox not VM-verified |
| 12 | sys operations |
Partial | history, enable/disable, inspect, install, prepare-updates VM-verified; undo, undo status, ask added (unit-tested, VM gate pending) |
| 13 | Kernel optimization policy | Later | conservative fragments only; SAFE/OPTIMIZED/AGGRESSIVE selection exists |
| 14 | ISO / release pipeline | Partial | manifest/verify/assemble tooling; executable evidence-bound gates + publication authorization (ADR 0012); no CI runner has executed a gate |
| 15 | Recovery environment | Later | recovery BLS entry generated; snapshot-based recovery entry written at install; full recovery image not built |
| — | Rust TUI | Partial | ratatui UI with plan/ERASE and AI provider selection; not yet the default on all paths |
| — | Graphical installer (welcome + wizard) | Partial | Quickshell/QML over the typed --gui-bridge; live graphical VM verified, including a detached install+boot; live AI call pending (ADR 0010) |
| — | AI-guided install optimization | Partial | DeepSeek/OpenAI/local providers, evidence-gated typed review, mandatory at install with --no-ai break-glass; fixture-verified, no live call |
| — | Nix as a built-in second lane | Partial | pinned-release bootstrap; nix-daemon active and nix shell nixpkgs#hello VM-verified; on by default |
| — | Git workflow + agent guide | Done | this docs/ set, .githooks/, scripts/ |
Immediate next steps
- Physical-seat desktop: run
phoebus-session/dwl on a real VT (or aseatd-backed session) and verify kitty, wofi,phoebus-menu,phoebus-idle, the polkit agent, logout and reboot interactively (docs/DEVELOPMENT.md). - Mango + DankMaterialShell graphical verification: Mango is now the
default (ADR 0009). Install the
mangoprofile and boot the Mango live ISO in a graphical, seat-providing VM and run the gates indocs/VM-BOOT-VERIFICATION.md. Default promotion was an explicit owner decision; verification is still required to claim stability. - Rollback VM acceptance: deliberately break an update in the disposable
VM, run
sys undo, reboot detached, verify package-state consistency, then boot the recovery entry with no network or model (ADR 0007). - Binary strategy: keep the official signed binhost for packages whose USE
matches and use Flatpak/Nix for other binaries; do not publish a private
Gentoo binhost (ADR 0006). Verify with
emerge -pvand record reuse. - Live AI provider call: exercise
sys askand the installer guided path with a real 0600 key file; the path is currently fixture-verified only, and thesystemd-runsandbox is not yet VM-verified.
Later
- Full recovery environment (network, LUKS, Btrfs, Portage/kernel repair).
- Automated biweekly ISO candidate build with tiered tests and atomic publish.
- AI OS sandbox (systemd sandboxing / namespaces / bubblewrap / Landlock).
- Local model support; richer provider onboarding.
- Optimised kernel profiles with real hardware detection.
- Risk-class update policy (CORE / PROVEN / EDGE) and update preflight.