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.
7 lines
451 B
YAML
7 lines
451 B
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: 83c9a398970831e88cb3ef5d71d3f175da97d1f1
|
|
README.zh.md: 8e6c15eccdd83d3b918249920596dcbeee94f2b2
|