Chinesezjc bca73068f6 fix(code-runtime-python): walk the completion value in O(depth), not O(width) ...

`_check_done_value` and `_encode_json_plain` pushed one stack entry per child
(plus a separator marker, and `dict.items()` materialized as a list), so the
bookkeeping scaled with the value's WIDTH rather than its depth. A value the
byte meter admits could then die on the walk's own frames: a flat
`[0] * 2_000_000` serializes to 4.0 MB, but measured peaks were 145.2 MB in the
meter and 114.7 MB in the encoder — 28.7x the serialized size, far past the 12x
the load-time address-space gate reserves.

Each container now pushes ONE cursor frame that pulls its children one at a
time and writes into a shared `io.StringIO`, so the output string is the only
width-proportional allocation and the caller already metered its size. Measured
on the same value: 0.0 MB in the meter and 9.0 MB in the encoder (2.3x), with
identical verdicts.

2026-08-31 14:24:59 +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): walk the completion value in O(depth), not O(width)

2026-08-31 14:24:59 +08:00