Repository navigation
Windows: prove the installed Runtime journey under WSL2 #265
Description
Implement the first Windows proof described in docs/WINDOWS.md, using the existing Runtime and signed-release contracts. Base implementation work on current develop.
Acceptance:
- Install into a dedicated WSL2 environment with stable artifact paths and isolated test data.
- Record source and installed-artifact identities; preserve signature, permission and confinement checks.
- Prove Home launch, passkey sign-in, document save/reopen, stop and restart.
- Prove update, recovery and cross-device People/Chat journeys.
- Record setup friction, resource usage and cleanup; qualify Browser separately.
- Obtain required reviews and installed proof before claiming Windows readiness.
This first proof informs subsequent installer and launcher work. Release scope and isolation dependencies remain governed by Anders’s decisions.
Activity
SashaMIT commentedon Oct 6, 2026
Windows WSL2 is running. The public installer verifies the signed release metadata, then stops because the release provides only aarch64-darwin.
The installed Windows journey requires a signed Linux x86-64 release artifact. Local source testing is continuing.
docs: WSL2 notes state the localhost origin, python3 and the open proof
andersalm commentedon Nov 2, 2026
Windows desktop installer work waits until the macOS and Linux installer (#521) ships. Elacity/elastos-agent-host-spike#1386 runs ElastOS in its own WSL system; elastos-launcher v1.4.0 had a WSL path, which Elacity/elastos-launcher#46 removes. Before Windows ships it needs: WSL turned on without a terminal, passkey sign-in proven on Windows in the default browser where Home opens as on Mac and Linux (Windows Hello inside an app's WebView2 is unproven, see MicrosoftEdge/WebView2Feedback#5663), an installer and uninstaller, and a Windows code-signing certificate, which Elacity does not have today.