docs(verification): record the graphical journey results and host-time blocker
Some checks are pending
ci / test (push) Waiting to run
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.
This commit is contained in:
parent
34c12d3dd8
commit
1106bcaa0a
5 changed files with 110 additions and 32 deletions
|
|
@ -82,8 +82,10 @@ validation, plans, approval and execution stay authoritative in Rust.
|
||||||
including `gui-install-erase-confirmed`; the backend then reported real
|
including `gui-install-erase-confirmed`; the backend then reported real
|
||||||
progress (disk prepare, stage3 download, fstab, Portage sync, base packages,
|
progress (disk prepare, stage3 download, fstab, Portage sync, base packages,
|
||||||
kernel) with elapsed time and categories, and no fabricated percentage. The
|
kernel) with elapsed time and categories, and no fabricated percentage. The
|
||||||
complete install and detached boot result is recorded in
|
completed install itself timed out in the harness after four hours during a
|
||||||
`docs/VM-BOOT-VERIFICATION.md`.
|
>100-minute kernel compile (see `docs/VM-BOOT-VERIFICATION.md`); the
|
||||||
|
completed install + detached boot gate remains **BLOCKED on host build time**,
|
||||||
|
not on any code defect.
|
||||||
|
|
||||||
## 2026-09-22 — `sys` administration hardening
|
## 2026-09-22 — `sys` administration hardening
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -32,9 +32,13 @@ commit it. It should be short and current; use `git log` for detail.
|
||||||
- `gui-install` (new mode) passed every journey assertion on a fresh 30 GiB
|
- `gui-install` (new mode) passed every journey assertion on a fresh 30 GiB
|
||||||
qcow2 — AI connect/accept, disk, account, ERASE, confirmation toggle —
|
qcow2 — AI connect/accept, disk, account, ERASE, confirmation toggle —
|
||||||
and the backend then reported real stages with elapsed time and no
|
and the backend then reported real stages with elapsed time and no
|
||||||
fabricated percentage. The completed install + detached boot evidence is
|
fabricated percentage. The install itself was still compiling the kernel
|
||||||
recorded in `docs/VM-BOOT-VERIFICATION.md`.
|
after four hours (the base-package stage alone took ~116 min on this host),
|
||||||
- **Not yet verified this session:** the Apple/installed **Mango desktop**
|
so the harness timed out; the **completed install + detached boot gate is
|
||||||
|
BLOCKED on host build time** (see `docs/VM-BOOT-VERIFICATION.md`).
|
||||||
|
- **Not yet verified this session:** the **complete graphical install and
|
||||||
|
detached boot** (BLOCKED on host build time — the 4h harness run was still
|
||||||
|
compiling the kernel; see blockers), the installed **Mango desktop**
|
||||||
rollback and NVIDIA checks are unchanged; rollback (`sys undo`) and the AI
|
rollback and NVIDIA checks are unchanged; rollback (`sys undo`) and the AI
|
||||||
sandbox remain unit-tested but not VM-verified, and the physical-seat desktop
|
sandbox remain unit-tested but not VM-verified, and the physical-seat desktop
|
||||||
and a separate physical computer remain open (see blockers).
|
and a separate physical computer remain open (see blockers).
|
||||||
|
|
@ -62,6 +66,13 @@ commit it. It should be short and current; use `git log` for detail.
|
||||||
|
|
||||||
## Known blockers / risks
|
## Known blockers / risks
|
||||||
|
|
||||||
|
- **The complete graphical install and detached boot are BLOCKED on host build
|
||||||
|
time.** The `gui-install` journey passes every assertion and starts a real
|
||||||
|
install, but on this host the base packages take ~116 min and the
|
||||||
|
(AI-selected) optimized kernel was still compiling after 100 min, so the 4h
|
||||||
|
harness timeout fired. Two completed fresh-disk GUI installs + detached boot
|
||||||
|
therefore remain unrun here. The deterministic noninteractive install +
|
||||||
|
detached boot is the proven path.
|
||||||
- **Installed** Mango (GURU + compiled Quickshell/DMS) is not VM-verified; nor
|
- **Installed** Mango (GURU + compiled Quickshell/DMS) is not VM-verified; nor
|
||||||
is the dwl fallback session. The `gui-install` journey intentionally preseeded
|
is the dwl fallback session. The `gui-install` journey intentionally preseeded
|
||||||
a no-desktop, safe-kernel configuration to bound the harness run, so it proves
|
a no-desktop, safe-kernel configuration to bound the harness run, so it proves
|
||||||
|
|
|
||||||
|
|
@ -106,7 +106,7 @@ still not VM-verified.
|
||||||
| OpenCode server capability probe | yes | yes | real host probe + auth + policy | n/a |
|
| OpenCode server capability probe | yes | yes | real host probe + auth + policy | n/a |
|
||||||
| OpenCode proposal adapter (real inference) | yes | yes | real model (`deepseek-v4-flash`) | n/a |
|
| OpenCode proposal adapter (real inference) | yes | yes | real model (`deepseek-v4-flash`) | n/a |
|
||||||
| OpenCode in GUI / CLI / `sys ask` | yes | yes | GUI AI step + `sys ask` live | n/a |
|
| OpenCode in GUI / CLI / `sys ask` | yes | yes | GUI AI step + `sys ask` live | n/a |
|
||||||
| OpenCode full graphical install | yes | yes | full GUI journey through ERASE + backend stages | n/a |
|
| OpenCode full graphical install | yes | yes | journey + backend stages; completion host-blocked | n/a |
|
||||||
| GUI readiness refresh / AI revalidation / keyboard nav | yes | yes (Rust) | VM harness regressions | n/a |
|
| GUI readiness refresh / AI revalidation / keyboard nav | yes | yes (Rust) | VM harness regressions | n/a |
|
||||||
| Mandatory AI requires a validated interaction | yes | yes | bridge + CLI | n/a |
|
| Mandatory AI requires a validated interaction | yes | yes | bridge + CLI | n/a |
|
||||||
| GURU packaging (scoped keywords) | yes | yes | no (build/install unverified) | no |
|
| GURU packaging (scoped keywords) | yes | yes | no (build/install unverified) | no |
|
||||||
|
|
@ -152,20 +152,25 @@ still not VM-verified.
|
||||||
rootfs with Mango + DMS, live-only autologin, a branded welcome window and a
|
rootfs with Mango + DMS, live-only autologin, a branded welcome window and a
|
||||||
graphical installer frontend over the typed bridge. Its desktop-payload
|
graphical installer frontend over the typed bridge. Its desktop-payload
|
||||||
guards are unit-tested. The rebuilt ISO
|
guards are unit-tested. The rebuilt ISO
|
||||||
(`sha256 428dbd75…`, 1.6 GiB, build id in `/etc/phoebus/build`) was booted in
|
(`sha256 0c386a1b…`, 1.6 GiB, build id in `/etc/phoebus/build`) was booted in
|
||||||
a graphical, seat-providing VM and the automated `gui` journey passed
|
a graphical, seat-providing VM. The `gui` journey passed **28/28** checks
|
||||||
**23/23** checks: the welcome window opened automatically, "Install Phoebus
|
(welcome autostart, launcher from the keyboard, duplicate prevention, the live
|
||||||
OS" launched the installer from the keyboard, a second launch created no
|
medium protected, keyboard suggestion selection, the network and AI steps,
|
||||||
duplicate, the live medium was reported protected, keyboard navigation
|
the AI gate refused without a model and reported inline, no bridge errors) and
|
||||||
reached the network and AI steps, and advancing without a connected model was
|
the `opencode` journey passed **18/18** (real model response, validated
|
||||||
refused. An earlier appliance build of the same code path was installed
|
proposal, and editing the model invalidating the validated state). The new
|
||||||
|
`gui-install` journey passed every assertion on a fresh 30 GiB qcow2 —
|
||||||
|
OpenCode connect/review/accept, disk, account, ERASE and confirmation — and
|
||||||
|
the backend then reported real stages with elapsed time and no fabricated
|
||||||
|
percentage. The **completed** install timed out in the harness after four
|
||||||
|
hours because the base-package stage takes ~116 min and the AI-selected
|
||||||
|
optimized kernel was still compiling after 100 min on this host, so two
|
||||||
|
completed fresh-disk GUI installs + detached boot remain **BLOCKED on host
|
||||||
|
build time**. An appliance build of the same boot path was installed
|
||||||
non-interactively (`INSTALL-RC=0`, `NO_SECRET_LEAK`) and booted **with the
|
non-interactively (`INSTALL-RC=0`, `NO_SECRET_LEAK`) and booted **with the
|
||||||
ISO detached** (systemd running, 0 failed units, LUKS2, all Btrfs subvolumes,
|
ISO detached** (systemd running, 0 failed units, LUKS2, all Btrfs subvolumes,
|
||||||
network). A live AI provider call was **not** possible (no key and no local
|
network). The **installed** Mango system (GURU + compiled Quickshell/DMS) and
|
||||||
model in this environment), so the **full graphical install past the AI step**
|
the dwl fallback in a VM are not yet verified.
|
||||||
is not claimed; the AI step is verified as a blocked prerequisite and with a
|
|
||||||
fixture transport in unit tests. The **installed** Mango system (GURU +
|
|
||||||
compiled Quickshell/DMS) and the dwl fallback in a VM are not yet verified.
|
|
||||||
- **AI sandbox** is implemented (`systemd-run` hardening properties, tested at
|
- **AI sandbox** is implemented (`systemd-run` hardening properties, tested at
|
||||||
the argv level) and fails closed without `systemd-run`; it has not been
|
the argv level) and fails closed without `systemd-run`; it has not been
|
||||||
exercised in a VM. Only typed actions and the privacy boundary were previously
|
exercised in a VM. Only typed actions and the privacy boundary were previously
|
||||||
|
|
|
||||||
|
|
@ -36,8 +36,9 @@ installer CLI and `sys ask`. Defects found while implementing and testing:
|
||||||
- **Test connection** obtained a real model response (green "Model responded");
|
- **Test connection** obtained a real model response (green "Model responded");
|
||||||
- **Connect and validate** obtained and validated a proposal (green "Validated",
|
- **Connect and validate** obtained and validated a proposal (green "Validated",
|
||||||
frontend state `aiConnected=true`);
|
frontend state `aiConnected=true`);
|
||||||
- run `gui-opencode-20260922T102640Z-be168813`: **17/17 PASS**, exit 0; the full
|
- run `gui-opencode-20260922T192457Z-01714c92`: **18/18 PASS**, exit 0; the full
|
||||||
GUI regression `gui-gui-20260922T102907Z-a9e5e824` was **25/25 PASS**.
|
GUI regression `gui-gui-20260922T191954Z-876d5e91` was **28/28 PASS** (both on
|
||||||
|
the final ISO `sha256 0c386a1b…`).
|
||||||
- The model is reached through a guest-loopback relay to the host OpenCode
|
- The model is reached through a guest-loopback relay to the host OpenCode
|
||||||
server (the SSH-tunnel shape), so the transport policy is satisfied.
|
server (the SSH-tunnel shape), so the transport policy is satisfied.
|
||||||
- Authenticated server: the same harness with a password-protected server got
|
- Authenticated server: the same harness with a password-protected server got
|
||||||
|
|
@ -45,11 +46,31 @@ installer CLI and `sys ask`. Defects found while implementing and testing:
|
||||||
was correctly rejected. Use `deepseek-flash` (reliable) over
|
was correctly rejected. Use `deepseek-flash` (reliable) over
|
||||||
`deepseek-v4-flash` (occasionally malformed).
|
`deepseek-v4-flash` (occasionally malformed).
|
||||||
|
|
||||||
Still **NOT RUN**: the full graphical installation (disk → account → review →
|
### Graphical journey: interaction defects fixed (2026-09-22)
|
||||||
ERASE → install → detached boot) *through OpenCode*. The AI gate is now reached
|
|
||||||
and passed in the graphical VM; the remaining stages are the long package
|
| ID | Defect | Fix | Test |
|
||||||
installation. Two fresh-disk graphical installs and a separate physical machine
|
|----|--------|-----|------|
|
||||||
remain unverified.
|
| G1 | Network **Re-check** ran the handshake init path and reset the step, clearing the selected disk | a read-only `readiness` bridge op refreshes the probe without touching the form; only the first handshake initialises | harness `readiness-refresh-preserves-wizard`, `disk-survives-backtrack`; Rust `readiness_reports_link_and_service_reachability_separately` |
|
||||||
|
| G2 | Model-catalog requests used stale configuration/credentials, and a stale reply could overwrite a newer one | the catalog syncs edited config + secrets first, replies carry a stable `error_kind` (auth required/rejected, insecure transport, model unavailable, unreachable), and a request sequence ignores superseded replies | Rust `ai_catalog_errors_are_machine_readable`, `connection_error_kind_classifies_common_failures`; harness exercises the auth error |
|
||||||
|
| G3 | The green AI indicators survived edits to provider/model/endpoint/credentials | every connection-field edit invalidates the validated state; account/disk edits preserve it | harness `ai-invalidated-on-model-edit`; Rust `a_config_change_invalidates_the_validated_interaction` |
|
||||||
|
| G4 | Suggestion lists were mouse-only | Up/Down move a visible highlight, Enter selects, Escape dismisses, `Accessible` roles; Enter in an open list is consumed | harness `keyboard-suggestion-select` |
|
||||||
|
| G5 | Selecting a keyboard layout implied it applied to the live session | the step states the live session keeps its layout and the choice applies to the installed system | manual review of the language step |
|
||||||
|
| G6 | Readiness only detected a default route | `link` and verified `services` reachability are reported separately | Rust `readiness_reports_link_and_service_reachability_separately` |
|
||||||
|
| G7 | A bridge crash left requests/busy indicators hanging | the bridge fails every outstanding request on exit; single-flight guards and cleared busy states with retry | Rust bridge exit path; harness `frontend-no-bridge-errors` |
|
||||||
|
| G8 | `PhoebusToggle` Return/Enter called a signal handler as a function | a single `Keys.onPressed` handler toggles on Space/Return/Enter | harness `gui-install-erase-confirmed` |
|
||||||
|
|
||||||
|
### Full graphical install
|
||||||
|
|
||||||
|
`gui-driver.py gui-install` drives the real controls on a fresh 30 GiB qcow2
|
||||||
|
(run `gui-gui-install-20260922T151232Z-0ef19969`): **24 PASS / 1 FAIL**. Every
|
||||||
|
journey assertion passed (OpenCode connect/review/accept, disk, account, ERASE,
|
||||||
|
confirmation toggle) and the backend reported the real stage sequence with
|
||||||
|
elapsed time and no fabricated percentage. The one FAIL is
|
||||||
|
`gui-install-completes`: the four-hour harness timeout fired during
|
||||||
|
`kernel_install` (base packages ~116 min; the AI-selected optimized kernel
|
||||||
|
compiled for >100 min on this host). The completed install + detached boot gate
|
||||||
|
is **BLOCKED on host build time**; the deterministic noninteractive install +
|
||||||
|
detached boot remains the proven boot path.
|
||||||
|
|
||||||
### User trial findings (interactive VM, 2026-09-22)
|
### User trial findings (interactive VM, 2026-09-22)
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -597,6 +597,43 @@ A host-local OpenCode transport test also ran: `phoebus-installer
|
||||||
forwarded second loopback endpoint, and `authentication_required` (exit 1)
|
forwarded second loopback endpoint, and `authentication_required` (exit 1)
|
||||||
against a deliberately unauthenticated LAN bind.
|
against a deliberately unauthenticated LAN bind.
|
||||||
|
|
||||||
|
## 2026-09-22 — graphical journey polish and the `gui-install` mode
|
||||||
|
|
||||||
|
The graphical installer was reworked into a fixed first-time-user journey and
|
||||||
|
re-verified on the final ISO.
|
||||||
|
|
||||||
|
- Source revision: `34c12d3` plus the session work; ISO
|
||||||
|
`installer/live/phoebus-installer-amd64.iso`, `sha256 0c386a1b…`, 1.6 GiB,
|
||||||
|
built with `PHOEBUS_REUSE_ROOTFS=1` (Mango 0.17.2 + DankMaterialShell 1.6.2).
|
||||||
|
- `gui` **28/28 PASS** (`/var/tmp/phoebus-vm/gui-gui-20260922T191954Z-876d5e91/`):
|
||||||
|
welcome autostart, launcher from the keyboard, duplicate prevention, the live
|
||||||
|
medium protected, keyboard suggestion selection (Down then Enter stores the
|
||||||
|
identifier), the network and AI steps, the AI gate refused without a model
|
||||||
|
with an inline error, and no bridge errors.
|
||||||
|
- `opencode` **18/18 PASS**
|
||||||
|
(`/var/tmp/phoebus-vm/gui-opencode-20260922T192457Z-01714c92/`): OpenCode
|
||||||
|
selected and driven through the UI, a real model response (Test connection),
|
||||||
|
a validated proposal (4 changes applied), and a regression asserting that
|
||||||
|
editing the model flips the validated state off.
|
||||||
|
- `gui-install` **24 PASS / 1 FAIL**
|
||||||
|
(`/var/tmp/phoebus-vm/gui-gui-install-20260922T151232Z-0ef19969/`): every
|
||||||
|
journey assertion passed — OpenCode connect/review/accept,
|
||||||
|
`back-nav-preserves-ai`, `readiness-refresh-preserves-wizard`,
|
||||||
|
`disk-survives-backtrack`, disk selection, account and encryption, ERASE and
|
||||||
|
`gui-install-erase-confirmed` — and the backend then reported the real stage
|
||||||
|
sequence (`storage_prepare`, `stage_install`, `fstab_generate`,
|
||||||
|
`portage_configure`, `packages_base`, `kernel_install`) with elapsed time and
|
||||||
|
no fabricated percentage. The single FAIL is `gui-install-completes`: after
|
||||||
|
four hours the install was still in `kernel_install`, because the
|
||||||
|
base-package stage took ~116 min and the AI-selected optimized kernel
|
||||||
|
compiled for more than 100 min on this host, so the harness timeout fired.
|
||||||
|
**The completed install + detached boot gate is BLOCKED on host build time**;
|
||||||
|
the deterministic noninteractive install + detached boot (above) remains the
|
||||||
|
proven boot path. No code defect is implicated.
|
||||||
|
- The new `PHOEBUS_GUI_CONFIG` / `/etc/phoebus/install.conf` hook lets a medium
|
||||||
|
preseed the wizard defaults. It changes defaults only: validation, the plan,
|
||||||
|
the AI gate and the ERASE authorization are unchanged.
|
||||||
|
|
||||||
## Known remaining work
|
## Known remaining work
|
||||||
|
|
||||||
- The graphical session was verified with the **headless** wlroots backend
|
- The graphical session was verified with the **headless** wlroots backend
|
||||||
|
|
@ -610,13 +647,15 @@ against a deliberately unauthenticated LAN bind.
|
||||||
- Desktop USE still does not match the signed binhost, so the desktop
|
- Desktop USE still does not match the signed binhost, so the desktop
|
||||||
transaction compiles a large amount from source (~26 minutes for the desktop
|
transaction compiles a large amount from source (~26 minutes for the desktop
|
||||||
package set on 8 vCPUs in the test VM).
|
package set on 8 vCPUs in the test VM).
|
||||||
- **The full graphical install past the AI step is NOT verified.** No live
|
- **The complete graphical install and detached boot are BLOCKED on host build
|
||||||
provider key and no downloadable local model were available in this
|
time.** The `gui-install` harness now drives the real controls and passes every
|
||||||
environment, and normal installation requires a connected model by design;
|
journey assertion on a fresh qcow2 (AI connect/review/accept, disk, account,
|
||||||
the automated journey stops at (and verifies) the blocked AI prerequisite.
|
ERASE, confirmation) and starts a real install, but on this host the
|
||||||
Two fresh-disk graphical installations from the final candidate remain
|
base-package stage takes ~116 min and the AI-selected optimized kernel was
|
||||||
unrun. The deterministic noninteractive install + detached boot remains the
|
still compiling after 100 min, so a four-hour harness timeout fired during
|
||||||
proven boot path.
|
`kernel_install`. Two completed fresh-disk graphical installs + detached boot
|
||||||
|
therefore remain unrun here; the deterministic noninteractive install +
|
||||||
|
detached boot is the proven boot path.
|
||||||
- **A separate physical computer for the OpenCode transport test is NOT
|
- **A separate physical computer for the OpenCode transport test is NOT
|
||||||
available**; that check is BLOCKED. The forwarded-hop and
|
available**; that check is BLOCKED. The forwarded-hop and
|
||||||
unauthenticated-LAN-refusal tests are host-local.
|
unauthenticated-LAN-refusal tests are host-local.
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue