WSL2 + Docker Desktop: k3s namespace timeout on gateway start

[AvgHummus]

Agent Diagnostic

Loaded debug-openshell-cluster skill via Claude (claude.ai) as agent — unable to use native skills because gateway fails to start
Ran openshell gateway start --name nemoclaw — failed with K8s namespace not ready
Ran openshell doctor check — all checks passed (Docker 29.2.1, socket ok)
Monitored kubectl get ns in a second terminal while gateway start ran — openshell namespace appeared at ~90-100 seconds
CLI timed out at ~60 seconds, before namespace appeared
Tried OPENSHELL_BOOTSTRAP_TIMEOUT=300 env var — no effect, timeout is hardcoded
Agent could not resolve — timeout is hardcoded in binary

Description

openshell gateway start always fails on WSL2 + Docker Desktop because k3s takes ~90-100 seconds to create the openshell namespace, but the CLI has a hardcoded ~60 second timeout. Expected behavior: gateway starts successfully.

Reproduction Steps

Windows 11 with WSL2 (Ubuntu) and Docker Desktop
Run openshell gateway start --name nemoclaw
Watch it fail with K8s namespace not ready every time

Environment

OS: Windows 11, WSL2, Ubuntu
Docker: Desktop 29.2.1 (WSL2 backend)
OpenShell: 0.0.12
Hardware: Huawei Laptop, Intel Iris Xe GPU

Logs

K8s namespace not ready
timed out waiting for namespace 'openshell' to exist: Error from server (NotFound): namespaces "openshell" not found

Agent-First Checklist

• I pointed my agent at the repo and had it investigate this issue
• I loaded relevant skills (e.g., debug-openshell-cluster, debug-inference, openshell-cli)
• My agent could not resolve this — the diagnostic above explains why

[johntmyers]

Closing as duplicate of #433 — same root cause (hardcoded namespace wait timeout too short for slower K3s initialization). That issue also captures the downstream PKI breakage. Adding a cross-reference there for WSL2 as an affected environment.