docs(code-runtime): state the maxWallMs upper bound in the public Config contract

The load-time range check rejects a maxWallMs above Node's maximum
setTimeout delay, but the constraint appeared only in the README design
section. Deployments reading the Config field JSDoc, the generated config
catalog, or the README config summary saw maxWallMs described as a
positive finite wall-clock ceiling, so an out-of-range value looked valid
until plugin load failed.
This commit is contained in:
Chinesezjc
2026-07-27 19:53:57 +08:00
parent fa00b71f18
commit 8f06c561ee
5 changed files with 10 additions and 6 deletions

View File

@@ -16,7 +16,7 @@
maxOldGenerationSizeMb: 512 # worker heap cap (resourceLimits)
```
每个字段都会验证并提供默认值;`maxOutputBytes` 必须是至少 4 字节的安全整数,其余字段必须是有限正数,此外没有其他可调项。
每个字段都会验证并提供默认值;`maxOutputBytes` 必须是至少 4 字节的安全整数,其余字段必须是有限正数,`maxWallMs` 还必须不超过 `2147483647`Node 的 `setTimeout` 最大延迟),此外没有其他可调项。
## 设计