Investigate Windows instability and npm install issues

[beubax]

Context

webcmd currently appears to be unreliable on Windows laptops. Reports so far indicate that the cloak runtime keeps shutting down, and npm package installation has also hit issues.

Goal

Obtain access to a real Windows laptop or equivalent Windows test environment and thoroughly validate the library there, with special attention to the cloak runtime lifecycle and npm package installation path.

Proposed scope

• Set up webcmd from a clean Windows environment.
• Test npm package installation from scratch.
• Run the local daemon + cloak runtime and observe whether/when cloak shuts down.
• Capture logs, process exits, error codes, environment details, and reproduction steps.
• Test common shells/environments where relevant, such as PowerShell, Windows Terminal, and cmd.
• Identify whether failures are caused by packaging, process management, browser/runtime assumptions, path handling, permissions, networking, or environment-specific behavior.
• Add Windows-specific fixes and regression tests where feasible.
• Document Windows setup requirements and known limitations.

Acceptance criteria

• A Windows validation checklist is created and executed.
• npm install issues are reproduced or confirmed fixed on Windows.
• cloak runtime shutdowns are reproduced with logs or ruled out with documented test coverage.
• Root causes are identified for any reproducible Windows failures.
• Fixes or follow-up issues are created for each confirmed defect.
• The repo includes updated Windows setup/troubleshooting documentation if needed.