[All Platform][Playbook] LKG v0.0.109 fails documented Windows Express onboarding (Ollama unreachable); fix already in v0.0.119

## Description

The current LKG (last-known-good) tag resolved by the unpinned NemoClaw installer is v0.0.109, several releases behind the latest tag. v0.0.109 has known Ollama connectivity and messaging-channel problems that leave users unable to use the product after following the documented installation flow. NemoClaw should update the LKG tag to the latest release.

Confirmed repro: following the documented Windows Express onboarding flow without pinning a specific tag installs v0.0.109. The installer downloads and installs Ollama on the Windows host, but Ollama never becomes reachable through `host.docker.internal`, and onboarding times out and exits 1 after roughly 574 seconds. No OpenClaw sandbox is created. Messaging-channel functionality is also known to be broken on v0.0.109.

Pinning the same flow to v0.0.119 explicitly (`NEMOCLAW_INSTALL_TAG=v0.0.119`) completes successfully on the same class of host: onboarding reaches Ready and the sandbox is healthy. The relevant Ollama-reachability fix (PR #10470) is confirmed an ancestor of the v0.0.119 tag.

Release-blocker assessment: the documented onboarding flow does not instruct a user to pin a specific tag, so anyone following the default/documented path resolves to the stale LKG and hits this failure with no workaround available within the documented steps. The result is a complete inability to produce a working OpenClaw sandbox, and the pass/fail split (LKG fails consistently; a pinned v0.0.119 run succeeds cleanly) confirms this is not a single-host fluke. The LKG being stale is a platform-agnostic problem — every platform's unpinned installer resolves the same tag — and other reports (#10836, #11160) independently hit different failures caused by the same stale v0.0.109 LKG on different platforms.

Platform scope: The stale-LKG root cause is platform-agnostic (every platform's unpinned installer resolves the same tag). The Ollama-reachability repro in this report was directly reproduced on a Windows 11 WSL2 GB300 Station configuration (staging environment).
Regression: No — v0.0.109 predates the PR #10470 fix; this is not a regression, the LKG tag simply has not advanced past a pre-fix release.

## Environment

```text
Device: GB300 Station
OS: Windows 11 Enterprise Insider Preview, WSL2 Ubuntu 24.04.4 LTS
Architecture: aarch64
Node.js: v22.23.2
npm: 10.9.8
Docker: 29.7.2
OpenShell CLI: 0.0.101
NemoClaw: v0.0.109 (LKG, unpinned installer)
OpenClaw: N/A (onboarding did not complete)
GPU: NVIDIA GB300, Driver 615.53, CUDA 13.2
```

## Steps to Reproduce

1. On a Windows 11 WSL2 GB300 Station host, in Ubuntu 24.04 under WSL2, verify prerequisites:
```bash
docker info --format '{{.ServerVersion}}'
nvidia-smi
```
2. Run the documented Windows Express installation flow without pinning a tag:
```bash
export NEMOCLAW_PROVIDER=install-windows-ollama
export NEMOCLAW_AGENT=openclaw
export NEMOCLAW_NON_INTERACTIVE=1
export NEMOCLAW_NON_INTERACTIVE_SUDO_MODE=prompt
export NEMOCLAW_YES=1
export NEMOCLAW_POLICY_MODE=suggested
export NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1
curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
```
3. Wait for the Windows Express installation and onboarding to complete.
4. After onboarding fails, run the diagnostic commands the installer itself prints:
```bash
powershell.exe -Command "Get-Process ollama* -ErrorAction SilentlyContinue"
powershell.exe -Command "Get-NetTCPConnection -LocalPort 11434 -State Listen -ErrorAction SilentlyContinue"
docker run --rm curlimages/curl:8.10.1 -sf --connect-timeout 2 --max-time 5 http://host.docker.internal:11434/api/tags
```
5. For comparison, on the same class of host, repeat step 2 but pin the tag explicitly:
```bash
curl -fsSL https://www.nvidia.com/nemoclaw.sh | NEMOCLAW_INSTALL_TAG=v0.0.119 bash
```

## Expected Result

NemoClaw should update its LKG tag to the latest release. The documented, unpinned installation flow should reach the same working result as explicitly pinning to the latest tag — onboarding should complete and produce a Ready, healthy OpenClaw sandbox either way.

## Actual Result

Unpinned flow (resolves to v0.0.109, the current LKG):
```text
PowerShell launch via verified ollama.exe failed: Ollama did not become reachable
PowerShell launch via refreshed Windows PATH failed: Ollama did not become reachable
Timed out waiting for Ollama to start on the Windows host.
Onboarding did not finish.
[ERROR] Onboarding did not complete successfully.
```
(approximately 574 seconds elapsed before exit code 1; no OpenClaw sandbox created)

Pinned to v0.0.119, same class of host:
- Preflight detected the Docker Desktop credential helper was unavailable.
- Bridge and DNS probes were reported inconclusive with: `A specified logon session does not exist. It may already have been terminated.`
- NemoClaw printed: `Docker Desktop credential helper is unavailable in this WSL session; using an isolated credential-free config for the local-inference probe image.`
- The managed sandbox image pull used the same isolated credential-free configuration.
- Sandbox creation completed successfully.
- OpenClaw setup and policy application completed.
- Installer exited 0.
- Sandbox reached Ready and Docker health is healthy.

## Logs

```text
PowerShell launch via verified ollama.exe failed: Ollama did not become reachable
PowerShell launch via refreshed Windows PATH failed: Ollama did not become reachable
Timed out waiting for Ollama to start on the Windows host.
Onboarding did not finish.
[ERROR] Onboarding did not complete successfully.
```

Start at the unpinned NemoClaw installer entry point and trace how NEMOCLAW_INSTALL_TAG selects the LKG value. Update the LKG from v0.0.109 to the working release identified in the issue, then run the documented Windows Express flow without a pinned tag and confirm onboarding reaches Ready with a healthy sandbox.

Written by the indexing model from the issue text.