From 178a51d26105f6b526466d2deed979d542a3fd94 Mon Sep 17 00:00:00 2001
From: cnliucheng <brokenway@163.com>
Date: Wed, 12 Aug 2026 09:41:27 +0800
Subject: [PATCH] =?UTF-8?q?docs(memory):=20=E8=AE=B0=E5=BD=95=20GitHub=20?=
 =?UTF-8?q?=E6=8E=A8=E9=80=81=20HTTP/1.1=20=E8=A7=A3=E6=B3=95?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .workbuddy/memory/MEMORY.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.workbuddy/memory/MEMORY.md b/.workbuddy/memory/MEMORY.md
index 2cd1f29..49c385b 100644
--- a/.workbuddy/memory/MEMORY.md
+++ b/.workbuddy/memory/MEMORY.md
@@ -29,3 +29,4 @@
 - 美化按"见效快优先"分批，每轮 `node --check` + grep 残留再交付。
 - **git push 须 `dangerouslyDisableSandbox:true`**（沙箱隔离致 github SSL 超时）；无 SSH，仅 HTTPS remote。
 - **GitHub 链路不稳**：国内环境到 `github.com:443` 常 SSL 重置/HTTP2 framing 失败（非代码问题），`git.soao.net`(soao) 国内远程稳定。策略：soao 为主远程、实时同步；`origin`(GitHub) 失败则延后推或本地代理(`127.0.0.1:7890` 等)临时 `git -C <repo> config http.proxy` 推完 `config --unset` 撤销。代码已 commit 则零丢失风险。
+- **GitHub 推送有效解法（2026-08-12 实测）**：报 `LibreSSL SSL_connect: SSL_ERROR_SYSCALL` 时，若 `curl 直连 https://github.com` 能 200（慢 30s 但通），说明是 git 默认 HTTP/2 framing 问题（curl 默认 HTTP/1.1 所以通）→ 执行 `git -C <repo> config http.version HTTP/1.1` 后再 push 即可成功，推完 `config --unset http.version` 撤销。7890 端口进程可能空转（curl -x 走它返回 000），别依赖该代理。