Add read-only Windows prerequisite diagnostic #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue/5-windows-first-run"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Related to #5. Partial first-run improvement, not an installer, startup workflow, trust solution, or M0 acceptance.
Adds a Windows PowerShell diagnostic for WSL status/version command availability and Docker Compose. By default it does not contact a Docker engine and exits nonzero to signal incomplete checking; explicitly passing
-CheckEngineopts into probing the currently configured context after a warning that it may be remote. It does not establish WSL2 readiness, Docker Desktop identity/locality, image provenance, browser trust or Foundry readiness. It creates no Foundry resources and changes no trust or policy.Validation: native Windows PowerShell mock and real-probe tests 9/9 passed through process-only encoded test input. An independent reviewer additionally tested the normal
-Fileinvocation from a Windows-local temp copy: default and-CheckEnginemodes behaved as documented. The WSL UNC-Filepath failedAuthorizationManager; no policy was changed. Full suite: 40 passed, 5 skipped (four image-gated Docker runtime and one opt-in live diagnostic). The unchanged TLS Docker runtime suite separately passed 4/4 using previously source-verified imagesha256:1225eacbec52d7ef0e5f039e1b5d2fdf64069c9774cc23aaa4d9379c15f71c32.Independent GLM-5.3 review covered initial commit
836d804and follow-up70ba5c7; findings and remediation are anchored in the PR comment. No new CA, trust import, renewal or security lifecycle code was implemented; native persistent Edge/Chrome trust acceptance requires an authorized disposable Windows account or VM.Independent GLM-5.3 review covered exact original commit
836d804e8e12d6431307dcebe4144d1cdd135b48and the targeted follow-up70ba5c703aabfec02f249b591b7247f67e89c83f. The reviewer verified mitigation of both medium findings: engine probing is explicit opt-in with a warning and no endpoint disclosure; real child-process tests cover exit propagation, missing executable, dual-pipe output and timeout. No new blocking findings; the generic failure message still cannot distinguish every cause.The reviewer also executed the documented
-Filescript from a disposable Windows-local temp copy under native Windows PowerShell 5.1: default skipped the engine and exited 1;-CheckEnginebound correctly and returned 0 on this host. The WSL UNC-Filepath remains denied by AuthorizationManager and no policy was changed. Full suite at HEAD: 40 passed, 5 skipped; native live diagnostic and mock/real-probe tests 9/9 passed separately. This is an independently reviewed partial diagnostic, not a browser trust or installation acceptance claim.