docs: capture JD01 GC post-task lessons

2026-07-01 04:12:24 +00:00
parent 098a60983e
commit e0ac0e45cc
2 changed files with 28 additions and 1 deletions
@@ -118,6 +118,15 @@ Read `docs/reference/gc.md` before these remote cases:

 For JD01, Chrome memory growth should first be treated as an observer lifecycle problem: sentinel/quick-verify terminal paths must stop their observer, and runner TTL/maxSamples/artifact caps must come from YAML. Do not solve it by raw killing Chrome or deleting web-observe directories; use controlled observe stop and GC plan candidates.

+JD01 and other remote hosts may use rebuildable tool caches only through explicit opt-in:
+
+```bash
+bun scripts/cli.ts gc remote JD01 plan --target-use-percent 49 --include-tool-caches --limit 100
+bun scripts/cli.ts gc remote JD01 run --confirm --target-use-percent 49 --include-tool-caches --limit 100
+```
+
+Review the plan first. The remote tool-cache candidate is limited to fixed allowlisted npm/npx/Bun cache directories; do not replace it with ad hoc `rm -rf ~/.npm ~/.bun`, and do not touch `node_modules`, auth/config, k3s/containerd, PVCs, or Docker volumes.
+
 ## Protected Boundaries

 Never use these as generic disk relief:
@@ -143,4 +152,4 @@ docker system df
 du -sh /root/unidesk/.worktree /root/unidesk/.state /tmp /var/log 2>/dev/null || true
 ```

-Summarize the starting and final `df` percentage, major successful cleanup classes, protected failures, and remaining high-risk pressure sources.
+For remote memory/Chrome pressure, also include `free -h`, Chrome/observer process summary, and web-observe state size. Summarize the starting and final `df` percentage, major successful cleanup classes, protected failures, and remaining high-risk pressure sources.