deepseek-harness/docs/core-data-structures/tools.i18n.yaml

# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
# 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
tools.md: 250e869397f8ecb128d5b644ff7506376d0657c6
tools.zh.md: 96fc9d3eeda0240e195beb11bea088d5606d4757
docs(i18n): core-data-structures and postmortem batch — 22 bilingual pairs core-data-structures 18 篇（core.md 因超长仍在产出、随后补）、 postmortem 3 篇与 RFC 前门 README 配对；流水线 + 二遍校验产出。生成文件 docs/rfc/INDEX.md（gen-rfc-index 产物）列入排除。中文侧页内锚点统一指向英文侧锚名，满足配对门禁的链接目标一致规则。 2026-07-15 23:11:25 -07:00			`# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each`
			`# 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`
fix(tools): bound the shaped-append side channel; total error containment; recorded spill snapshot Responding to ds-review-bot round 2 on #661: - logWork is bounded: past maxParallelSubCalls pending shaped-append tasks the ordered commit lane holds (Promise.race drains one), so a slow spill backend backpressures the run instead of accumulating unbounded pending I/O and retained results. Tasks self-remove on settlement; run settlement still drains every task inside the open turn. New spill test drives three oversized reads against a hung backend at cap 1 and proves the third dispatch cannot start until a save drains. - shapeDispatchLog's catch uses errorMessage() (total), so a thrown value with a throwing toString cannot escape the containment and lose the settle event. - CodeDispatchLog.content documented as the RENDERED result projection (native tool/result vocabulary), not what the program received — the program gets the structured value; doc pair + type-equiv re-synced. - New RECORDED tui-agent snapshot scenario code-mode-dispatch-spill: the real Loader-visible composition (worker runtime + spill-local + policy) drives an oversized bash sub-call end-to-end; replay proves the durable dispatch copy is bounded to preview + locator while the program value stays whole (the outer result carries just the line count). Agent Note updated (both languages). 2026-07-26 18:29:09 +08:00			`tools.md: 250e869397f8ecb128d5b644ff7506376d0657c6`
			`tools.zh.md: 96fc9d3eeda0240e195beb11bea088d5606d4757`