Chinesezjc 8f06c561ee 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.

2026-07-27 19:53:57 +08:00

..

bootstrap.ts

fix(code-runtime): capture worker error intrinsic

2026-07-23 03:51:15 +08:00

index.ts

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

2026-07-27 19:53:57 +08:00

invariant.ts

fix(invariants): assert runtime relationships, not API shapes

2026-07-20 19:34:19 +08:00

output-json.ts

fix(code-runtime): harden captured JSON boundary

2026-07-23 03:32:24 +08:00

protocol.ts

fix(code-mode): generalize failures and bound diagnostics

2026-07-23 01:32:17 +08:00

worker-json.ts

fix(code-runtime): harden captured JSON boundary

2026-07-23 03:32:24 +08:00

worker.ts

Merge remote-tracking branch 'origin/master' into codex/trim-ai-prose

2026-07-14 00:40:36 +08:00