From b9ca80e801ba12f3d062192edb909e434f8971c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=9B=B7=E7=94=B5=E8=8A=BD=E8=A1=A3?= Date: Sun, 13 Sep 2026 13:36:58 -0400 Subject: [PATCH] docs(agents): record the 0.1.15 upstream sync window and its known limitations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sync record now ends at upstream `3794978` (2026-09-09, ≈v1.0.24). Lists the two limitations the sync left: the Windows frame writer still prints through std's stderr lock, and the bwrap builder re-stats /data. Claude-Session: https://claude.ai/code/session_01RUqV8HVGXcAETyYbZ2tPQ4 --- AGENTS.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 8df0265..a63a950 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -17,11 +17,19 @@ import) or any `KIMI_*` env var. Upstream sync record (update on every sync): fork baseline is upstream snapshot `8adf901` (2026-07-16, ≈v0.2.102); bug fixes evaluated and selectively ported through upstream `77cd7eb` (2026-08-25, ≈v1.0.10) in -the 0.1.13 cycle. Upstream is daily "Synced from monorepo" snapshots — +the 0.1.13 cycle and through `3794978` (2026-09-09, ≈v1.0.24) in the +0.1.15 cycle. Upstream is daily "Synced from monorepo" snapshots — the commit BODIES carry per-change bullet lists, and `crates/codegen/xai-grok-shell/changelogs/` maps releases to dates; start any future sync from those two, not from raw diffs. +Known limitations left by the 0.1.15 sync (fix before relying on them): +the Windows frame writer writes through `std::io::stderr`, so a console +that stops reading still blocks exit-path prints behind std's stderr lock +(unix silences fd 2 after a timed-out writer join); the bwrap command +builder re-checks `Path::exists("/data")` and can omit the devbox bind on +a stat error that the profile classification treated as present. + ## Hard constraints - **Zero egress**: only `auth.kimi.com`, `api.kimi.com`, `api.moonshot.cn`,