Support HTTPS managed forward-proxy endpoints

## What changed OpenClaw added support for HTTPS managed forward-proxy endpoints. The release introduces the proxy.tls.caFile setting to configure scoped CA trust for TLS connections through those proxies.

The change targets self-hosted deployments that must route traffic through corporate or managed proxies instead of direct internet access.

## Why it matters Self-hosted agents like OpenClaw often run on VPS instances inside restricted networks. Without proper HTTPS proxy handling, certificate validation fails and blocks browser control or external API calls.

This update lowers the barrier for Vibe Builders who operate behind company firewalls or regional proxy requirements. It shifts the bet toward reliable operation in constrained environments rather than assuming open outbound access.

## How to use it Open the YAML configuration file for your OpenClaw instance. Add or update the proxy.tls.caFile key with the full path to your CA certificate bundle.

Restart the agent through the CLI command documented in the install guide. Test a single outbound browser task to confirm the proxy route succeeds without TLS errors.

## Watch for Successful connection logs without certificate warnings will confirm the change works as intended. Mismatched CA paths or expired certificates will break outbound actions first. Expect a follow-up release that adds proxy authentication headers next.