Chinesezjc bca392e6d1 fix(code-runtime-python): seal the open hold past MAX_PENDING_CHUNKS ...

The review's warning: each held open fragment is a distinct array slot plus
string object header (~30x overhead the byte cap cannot see), and a
budget-sized single-character open flood is honest-child reachable
(print('x', end='', flush=True) in a loop). With maxLogBytes near its ~67 MB
load ceiling that was up to ~2 GB of host auxiliary heap. The hold now seals
into one block past MAX_PENDING_CHUNKS, mirroring the fd-3 reader's blocks and
the stray capture's seal; the merge, truncateLogs, and the finish residual all
read sealed + current fragments, and a within-budget flood regression asserts
the merged entry is byte-identical.

2026-08-31 15:06:05 +08:00

..

boot-write-failure.spec.ts

test(code-runtime-python): cover the boot-ack gate's re-entry guard and run-write failure

2026-08-31 15:00:33 +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): seal the open hold past MAX_PENDING_CHUNKS

2026-08-31 15:06:05 +08:00