HiClaw Installation Issue: Higress Gateway Cannot Start Due to Proxy Configuration

## Environment
- **OS**: Windows 11 Pro 10.0.22621
- **Docker Desktop**: Latest version with WSL2 backend
- **HiClaw Version**: Latest (installed 2026-03-30)
- **Installation Method**: PowerShell script from https://higress.ai/hiclaw/install.ps1

## Problem Description

After successful installation, the Higress Gateway fails to start because it attempts to connect to a non-existent proxy server (`192.168.65.254:9910`), preventing Matrix service and Element Web from functioning.

### Symptoms

1. **Gateway Error Logs**:
```
error wasm convert the wasm config: cannot fetch Wasm module
oci://higress-registry.cn-hangzhou.cr.aliyuncs.com/plugins/basic-auth:2.0.0
proxyconnect tcp: dial tcp 192.168.65.254:9910: connect: connection refused
```

2. **Manager Agent Logs**:
```
[hiclaw] Waiting for Higress Gateway at 127.0.0.1:8080...
[hiclaw] ERROR: Higress Gateway did not become available within 180s
```

3. **Impact**:
- ✅ OpenClaw Console works: http://127.0.0.1:18888/
- ✅ Higress Console works: http://127.0.0.1:18001/
- ❌ Matrix service unavailable (port 8080 not listening)
- ❌ Element Web login fails: http://127.0.0.1:18088/

## Configuration Details

### LLM Configuration
- Provider: OpenAI-compatible (Volcengine Ark)
- Base URL: https://ark.cn-beijing.volces.com/api/coding/v3
- Model: ep-m-20260322180727-2xh9m

### Network Configuration
- Network mode: External access enabled (0.0.0.0)
- Gateway port: 18080
- Higress console: 18001
- Element Web: 18088
- OpenClaw console: 18888

### Installation Directory
- Manager workspace: E:\hiclaw-manager
- Docker volume: hiclaw-data

## Troubleshooting Steps Attempted

### 1. Docker Proxy Configuration
- Set Docker Desktop proxy mode to "system" (disabled manual proxy)
- Removed all proxy settings from `settings-store.json`
- Restarted Docker Desktop multiple times

### 2. WSL Integration
- Disabled WSL distro integration in Docker Desktop settings
- Skipped WSL integration during startup errors

### 3. Environment Variables
- Added to `hiclaw-manager.env`:
```bash
HTTP_PROXY=
HTTPS_PROXY=
http_proxy=
https_proxy=
NO_PROXY=*
no_proxy=*
```

### 4. Network Configuration
- Configured hosts file with HiClaw domains
- Verified Clash proxy bypass rules for `*.aliyuncs.com`
- Confirmed Docker can pull images successfully

### 5. Container Restart
- Restarted `hiclaw-manager` container multiple times
- Checked all service processes are running

## Root Cause Analysis

The Envoy process inside the container inherits proxy configuration from Docker Desktop's WSL2 backend, even after:
- Disabling Docker proxy settings
- Disabling WSL integration
- Setting NO_PROXY environment variables

The proxy address `192.168.65.254:9910` appears to be cached in Docker's WSL2 VM layer.

## Logs

### Gateway Error Log
```
2026-03-30T08:27:49.809905Z error wasm convert the wasm config: 4 errors occurred:
* cannot fetch Wasm module oci://higress-registry.cn-hangzhou.cr.aliyuncs.com/plugins/ai-statistics:2.0.0
proxyconnect tcp: dial tcp 192.168.65.254:9910: connect: connection refused
* cannot fetch Wasm module oci://higress-registry.cn-hangzhou.cr.aliyuncs.com/plugins/ai-proxy:2.0.0
proxyconnect tcp: dial tcp 192.168.65.254:9910: connect: connection refused
* cannot fetch Wasm module oci://higress-registry.cn-hangzhou.cr.aliyuncs.com/plugins/basic-auth:2.0.0
proxyconnect tcp: dial tcp 192.168.65.254:9910: connect: connection refused
* cannot fetch Wasm module oci://higress-registry.cn-hangzhou.cr.aliyuncs.com/plugins/key-auth:2.0.0
proxyconnect tcp: dial tcp 192.168.65.254:9910: connect: connection refused
```

### Manager Agent Log
```
[hiclaw] Waiting for Higress Gateway at 127.0.0.1:8080...
[hiclaw] ERROR: Higress Gateway did not become available within 180s
```

## Questions

1. Is this a known issue with Docker Desktop WSL2 backend?
2. How can we completely disable proxy for the Envoy process inside the container?
3. Are there any workarounds or alternative installation methods for Windows users?
4. Would using Hyper-V backend instead of WSL2 resolve this issue?

## Expected Behavior

Gateway should start successfully and listen on port 8080, allowing Matrix service and Element Web to function properly.

## Additional Context

- Docker can successfully pull images from `higress-registry.cn-hangzhou.cr.aliyuncs.com`
- OpenClaw and Higress consoles work normally
- Only the Gateway's Wasm plugin fetching fails due to proxy issues

Thank you for your help!