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

docs: state the plan-mode flush as a step boundary

Browse Source 
ds-review-bot round 2: set() during an open multi-step turn applies at
the next request derivation in that same turn, so 'next turn boundary'
misstated the public timing contract (and propagated into the generated
catalogs). set()'s JSDoc, the module JSDoc, the pending-intent field
comment, and the subsystem page (both languages) now say step boundary;
catalogs regenerated; plan pair re-recorded.
This commit is contained in:
Tianyi Cui
2026-07-28 12:04:21 +08:00
parent bd62b6c032
commit 3e1c7351be
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/subsystems/plan.i18n.yaml
View File

@@ -2,5 +2,5 @@
# side as of the last confirmed-consistent state. Both languages carry equal authority;
# after editing either side, bring the other along and re-record with:
# pnpm run verify-translation-pairing --write docs/subsystems/plan.md
plan.md: eb88047573536cd15be587b1419271bfbd93e9f1
plan.zh.md: 5a838a045d63f2cabad80cad8af12df5da7e87f3
plan.md: c8bb6c9b6a0bcfd20ed6eadece4552d49f3c757c
plan.zh.md: c8acedaef0724581227b57afbf81418a7e538aed