From 189ab43ec5aa97d040b9c7f69eeaa9bcd4507a85 Mon Sep 17 00:00:00 2001
From: Pigbibi <20649888+Pigbibi@users.noreply.github.com>
Date: Sat, 2 May 2026 04:07:41 +0800
Subject: [PATCH] Revert "docs: document proxy exit verification"

This reverts commit 8ff2dd9ce597623982941e6fa1dcac2d2827ea4e.
---
 README.md | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/README.md b/README.md
index b8b2ab8..f590738 100644
--- a/README.md
+++ b/README.md
@@ -76,14 +76,6 @@ Notes:
 - This repo currently supports **HTTP/HTTPS proxy URLs** for workflow mode.
 - If `SCHWAB_PROXY_URL` is absent, the workflow runs without the home-exit proxy.
 - Only the Schwab automation traffic is proxied. Package installation and GitHub/GCP housekeeping continue to use the runner's default egress.
-- If a VPS or tunnel is used as the public entrypoint, make sure its upstream proxy still exits through the intended home/router WAN address. A reachable proxy endpoint is not enough if the final upstream route falls back to a VPS, VPN, or WireGuard egress IP.
-- A safe connectivity probe is:
-
-  ```bash
-  curl --proxy "$SCHWAB_PROXY_URL" https://api.schwabapi.com/v1/oauth/authorize
-  ```
-
-  A bare authorize request should reach Schwab and return an OAuth/client error, not a tunnel failure. If Schwab's login page reports invalid credentials while the same credentials work manually, verify the proxy's final exit IP before changing secrets.
 - If you want every step to originate from home, a **self-hosted runner in your LAN** is usually simpler and more stable than tunneling a proxy into a GitHub-hosted runner.
 
 ## 📈 Architecture