deepseek-harness/packages/code-runtime/code-runtime-worker/README.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 packages/code-runtime/code-runtime-worker/README.md
README.md: 44ba6a98169057f24d55f41cf3ca7b9f68bb329c
README.zh.md: e45aa484c0935d5b4b1626f5c4c7c72482cd5b5d
docs: translate remaining READMEs 2026-07-26 05:03:53 +08: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:`
fix(code-runtime): reject a maxWallMs above Node's maximum timer delay `config.maxWallMs` is only checked for positivity, and it is handed to `setTimeout`, which clamps any delay above 2^31-1 ms to 1 ms. A deployment configuring a 25-day wall ceiling therefore gets the opposite of what it asked for: every run times out on the first tick. The runtime now range-checks the field at load against MAX_TIMER_DELAY_MS from dsh-timeout and throws, so the misconfiguration fails loud where it is self-contained instead of silently inverting the budget. `computeMs` needs no matching bound: it is compared against measured event-loop utilization rather than fed to a timer. The test asserts both the rejection and that the boundary value itself loads. 2026-07-27 14:01:15 +08:00			`# pnpm run verify-translation-pairing --write packages/code-runtime/code-runtime-worker/README.md`
refactor: replace overloaded surface terminology 2026-07-24 19:54:25 +08:00			`README.md: 44ba6a98169057f24d55f41cf3ca7b9f68bb329c`
docs(i18n): reproofread updated Chinese documentation 2026-08-09 03:20:17 +08:00			`README.zh.md: e45aa484c0935d5b4b1626f5c4c7c72482cd5b5d`