Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(i18n): address RFC translation review

Browse Source
This commit is contained in:
Tianyi Cui
2026-07-22 22:29:39 +08:00
parent 0b1857904a
commit 1a39953f69
447 changed files with 1106 additions and 1106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/rfc/rejected/simplification/2026-06-20-drop-durable-step-boundaries.md
View File

@@ -1,9 +1,9 @@
# RFC: Drop durable step boundary events
English | [中文](2026-06-20-drop-durable-step-boundaries.zh.md)
Status: rejected — `step/end` is the durable indication that a model step finished, and keeping the symmetric `step/start` / `step/end` pair makes crash repair, invariants, and transcript inspection clearer than inferring completion from adjacent step-scoped events.
English | [中文](2026-06-20-drop-durable-step-boundaries.zh.md)
## Problem
The session log stores `step/start` and `step/end` events even though every step-scoped event already carries `{ turn, step }`: assistant chunks, assistant messages, tool calls, tool results, usage, and errors. `deriveMessages()` ignores step boundaries, ACP ignores them for UI, and the main consumers are invariants, tests, snapshot goldens, and crash repair.