Chinesezjc fca41b78ea fix(code-runtime-python): bound the load-time budget to the frame parser cap ...

The review found the 64 MiB parse cap contradicted the load-time budget bound:
maxLogBytes/maxValueBytes could be configured up to ceiling - envelope (~256 MiB),
but the receive path silently dropped any frame past the 64 MiB parser cap, so an
honest child's budget-internal done frame under such a config would be discarded
and the run stranded to the wall clock. The load bound is now parse-cap -
envelope, so a configured budget always fits through the parser; the boundary
test moves to 64 MiB - 64. The >64 MiB model-constructed binding-argument drop
is registered as an accepted residual in the README (en + zh).

2026-08-31 14:51:20 +08:00

..

boot-write-failure.spec.ts

fix(code-runtime-python): seal stray fragments, flush by serialized cost, charge lone surrogates fully

2026-08-31 14:22:37 +08:00

protocol-mirror.e2e.ts

docs(code-runtime-python): name the roster aliases by subset direction, align metering prose

2026-08-07 15:37:19 +08:00

protocol.spec.ts

docs(code-runtime-python): trim metering prose and cover encodeJsonPlain depth

2026-08-07 13:27:54 +08:00

residual-detach.spec.ts

docs(code-runtime-python): sync README with the shipped backend

2026-08-31 14:20:00 +08:00

runtime.spec.ts

fix(code-runtime-python): bound the load-time budget to the frame parser cap

2026-08-31 14:51:20 +08:00