docs(sidecar): add bilingual LFS exhaustion runbook

Author: Jacobinwwey

docs/en/sidecar_supply_strategy.md

@@ -207,6 +207,46 @@ Important boundary:
 
 - switch from legacy-allowlist verification toward strict no-LFS enforcement for protected roots
 
+### Operational playbook when monthly LFS bandwidth is exhausted (2026-04-09)
+
+When local checkout/pull fails due to Git LFS bandwidth exhaustion, use this fallback path:
+
+1. Skip LFS smudge for branch switch and sync:
+
+```bash
+GIT_LFS_SKIP_SMUDGE=1 git checkout main
+GIT_LFS_SKIP_SMUDGE=1 git pull --ff-only origin main
+```
+
+2. Verify that no new protected LFS drift was introduced:
+
+```bash
+npm run verify:lfs:policy
+```
+
+3. Verify sidecar supply readiness and current network dependency status:
+
+```bash
+npm run verify:sidecar:supply -- --json
+```
+
+4. Serve docs locally for ops visibility and review:
+
+```bash
+npm run docs:site:serve -- -a 127.0.0.1:8013
+```
+
+5. Keep CI design stable. Do not redesign default release CI for this emergency flow; use the existing mirror-first release workflow and only use `allow_godot_upstream_fallback=false` through `workflow_dispatch` for mirror-only smoke verification.
+
+Execution note validated on 2026-04-09:
+
+- PR #1 was merged to `main` and all triggered `main` workflows completed successfully:
+  - Migration Gates
+  - Mobile E2E Detox Contracts
+  - Fixrisk Operational Readiness
+  - Docs Diataxis Site
+  - Docs GitHub Pages Publish
+
 ### Bottom line
 
 The correct question is not:

docs/zh/sidecar_supply_strategy.md

@@ -207,6 +207,46 @@ npm run verify:sidecar:supply -- --json
 
 - 从“允许历史豁免”的校验，切换到对受保护目录执行严格 no-LFS
 
+### 月度 LFS 带宽超量时的运行手册（2026-04-09）
+
+当本地 checkout/pull 因 Git LFS 带宽超量失败时，按以下应急路径执行：
+
+1. 在切分支与同步阶段跳过 LFS smudge：
+
+```bash
+GIT_LFS_SKIP_SMUDGE=1 git checkout main
+GIT_LFS_SKIP_SMUDGE=1 git pull --ff-only origin main
+```
+
+2. 先确认没有新增受保护 LFS 回流：
+
+```bash
+npm run verify:lfs:policy
+```
+
+3. 再确认 sidecar 供给就绪度与网络依赖现状：
+
+```bash
+npm run verify:sidecar:supply -- --json
+```
+
+4. 启动本地文档站点用于运维可视化与复核：
+
+```bash
+npm run docs:site:serve -- -a 127.0.0.1:8013
+```
+
+5. 保持 CI 设计稳定：这个应急流程不要求重构默认 release CI；继续沿用现有 mirror-first 工作流，仅在 `workflow_dispatch` 下通过 `allow_godot_upstream_fallback=false` 做 mirror-only smoke 校验。
+
+2026-04-09 已验证执行记录：
+
+- PR #1 已合并到 `main`，并且该提交触发的 `main` 工作流全部成功：
+  - Migration Gates
+  - Mobile E2E Detox Contracts
+  - Fixrisk Operational Readiness
+  - Docs Diataxis Site
+  - Docs GitHub Pages Publish
+
 ### 结论
 
 真正该问的问题不是：