Files
ARCADIA-Studio/harness/release-wsl-readiness-20260910.md
T

34 lines
3.6 KiB
Markdown

# Supported WSL2 readiness probe — 2026-09-10
Codex `/root/release_audit`. Root explicitly authorized one isolated supported WSL2 import after the release audit identified the host reboot. No current native Linux release acceptance is claimed.
## Authorization and preflight
Owned distro name `ArcadiaStudio-Release1-20260910`; destination `C:\Users\User\Documents\Git\ARCADIA-Studio\.local\linux-wsl\release1-20260910`. Both absent before action. The preflight required at least 8 GiB host free disk and 3 GiB available RAM; actual values were 9,648,353,280 bytes and 4,208,900 KiB. No compiler, global WSL setting, Windows feature, host restart, QEMU launch, distro unregister or GUI control was authorized or performed. Root retained GUI ownership.
The verified Canonical archive is `.local/linux-wsl/ubuntu-24.04.4-wsl-amd64.wsl`, 391,541,571 bytes, fresh SHA256 `9b2f7730dc68227dd04a9f3e5eab86ad85caf556b8606ad94f1f29ff5c4fd3f5`. This matches the retained HTTPS release checksum; no OpenPGP claim. Current WSL version 2.7.13.0, kernel 6.18.33.2-2 and WSLg 1.0.73.2 were read; Windows reboot time was 2026-09-10 05:07:04.5 -07:00. Earlier `wsl --status` omitted its historical WSL2 virtualization warning, but this was only a hypothesis of readiness.
## Exact action and outcome
```powershell
wsl.exe --import ArcadiaStudio-Release1-20260910 C:\Users\User\Documents\Git\ARCADIA-Studio\.local\linux-wsl\release1-20260910 C:\Users\User\Documents\Git\ARCADIA-Studio\.local\linux-wsl\ubuntu-24.04.4-wsl-amd64.wsl --version 2
```
One attempt completed at **2026-09-10T17:38:44.5529693Z**, elapsed **1.177154 seconds**, exit **-1**. Terminal error:
```text
Wsl/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
```
WSL says virtualization is not enabled and asks for the Virtual Machine Platform component and firmware virtualization. This establishes that actual VM creation remains unavailable. It does not identify whether Windows optional features or the VMware host's nested virtualization is the underlying cause. HypervisorPresent alone did not establish nested VM support. No second attempt or setting change occurred.
The readiness chain stopped before a shell: no `uname`, guest OS inspection, WSLg display/socket check, apt installation, Linux GUI, service, Rust build or test ran. No process was started that requires distro shutdown. The root was immediately informed of the failure.
Raw task-local evidence is under `.local/linux-wsl/readiness-20260910/`: `preflight.json`, `import.log`, `import-status.json`, `post-import-list.txt`, `post-attempt.json`. At 17:39:46 UTC the list still said no distributions were installed and the task install directory was absent; no deletion was needed or performed. Host free disk was 9,647,493,120 bytes and available RAM 4,218,664 KiB.
## Handoff
The preserved source7 ELF/package remains unchanged and unexecuted. Its path, hash, runtime prerequisites, WSLg inference and a candidate launch environment are in `release-readiness-audit-20260910.md`. There is currently **no executable GUI launch command against this distro**, because the distro was not created. Do not present an old cross-build or installed WSLg version as runtime proof.
Next: provide a viable Linux runner or correct the external virtualization prerequisite, then take a fresh bounded readiness decision. The isolated supported import was distinct from the earlier automatically rejected QEMU timer workaround; that workaround remains untouched. Windows authoring, documentation/packaging corrections and release validation can proceed independently. Current-tree Linux runtime/server gates remain open.