{
  "ensure-workspace": {
    "status": "failed",
    "output": "=== Ensure workspace runtime (WSL2 Ubuntu) ===\n=== Ensure WSL2 subsystem is responsive (auto-recovers if wedged) ===\n  $ wsl --status\n    … still running `wsl --status`, 5s elapsed, no response yet…\n    … still running `wsl --status`, 10s elapsed, no response yet…\n    … still running `wsl --status`, 15s elapsed, no response yet…\n    … still running `wsl --status`, 20s elapsed, no response yet…\n    … still running `wsl --status`, 25s elapsed, no response yet…\n    … still running `wsl --status`, 30s elapsed, no response yet…\n    … still running `wsl --status`, 35s elapsed, no response yet…\n    … still running `wsl --status`, 40s elapsed, no response yet…\n    … still running `wsl --status`, 45s elapsed, no response yet…\n  ⚠ `wsl --status` did not respond within 45s (WSL likely wedged)\n  → WSL looks WEDGED, auto-recovery round 1/3 (kill stuck launchers + restart the subsystem):\n  $ taskkill /F /IM wsl.exe   (clearing stuck wsl.exe launchers)\n    | killed 0 stuck wsl.exe process(es)\n  Docker Desktop WSL is running, scoped restart instead:\n  $ wsl --terminate Adom-Workspace\n    … still running `wsl --terminate Adom-Workspace`, 5s elapsed, no response yet…\n    … still running `wsl --terminate Adom-Workspace`, 10s elapsed, no response yet…\n    … still running `wsl --terminate Adom-Workspace`, 15s elapsed, no response yet…\n  ✗ WSL is still wedged after two restarts, not restarting again; handing you manual steps.\n✗ Windows Subsystem for Linux is still wedged after two restarts. Open PowerShell as Administrator, run  wsl --shutdown, then relaunch Hydrogen Desktop and it will resume right where it left off. (Technical detail: WSL2 is wedged at the system level, even the restart command (`wsl --shutdown`/`--terminate`) didn't respond, so only a Windows restart can clear it. (`wsl --status` did not respond within 45s (WSL likely wedged)))",
    "percent": 0.0,
    "attempts": 0,
    "max_attempts": 3
  }
}