Temporarily disabled automatic configuration updates

Cloudflare Warp Endpoints are currently blocked in certain regions, (notably Iran and China).
The automatic update process in this workflow replaces not only endpoints, but also critical fields such as private_key, reserved, mtu, and address — which breaks connectivity when regionally restricted.

The workflows are intentionally commented out (disabled) to prevent overwriting the manually working configuration. I will manually set the following parameters until the restrictions are lifted.

• IPv4 range:

162.159.195.1 — 162.159.195.10

• IPv4 range:

162.159.192.5 — 162.159.192.20

• IPv6 range:

2606:4700:d0::a29f:c001 — 2606:4700:d0::a29f:c014

• Custom domain:

wire.nscl.ir

• Ports

500-854-859-864-878-880-890-891-894-903-908-928-934-939-942-943-945-946,955-968-987-988-1002-1010-1014-1018-1070-1074-1180-1387-1701-1843-2371-2408-2506-3138-3476-3581-3854-4177-4198-4233-4500-5279-5956-7103-7152-7156-7281-7559-8319-8742-8854-8886

⚠️ Do NOT re-enable or edit this workflow to auto-replace configs while these regional blocks remain active.

You can still run it manually from actions tab, But if you want to re-enable:

1. Verify that Cloudflare/Warp endpoints are accessible again from affected regions (Iran/China).
2. Uncomment this section to restore the workflow: lines 39, 40 ... and 45 at Spring, WinterGuard and Summer.yml
   .github/workflows/...
3. Test connectivity in staging before pushing to production.