Chinesezjc 146a9d9f61 fix(code-runtime-python): make checkDoneValue over-budget precedence order-independent ...

checkDoneValue returned non-lossless the instant it hit a non-finite/negative-
zero number, before finishing the budget metering. A value that is BOTH over-
budget and non-lossless then classified by member order: `["<huge>", 1e400]`
gave non-lossless while `[1e400, "<huge>"]` gave over-budget — the same value,
two verdicts — which would drive the consumer to emit invalid-output vs
output-limit non-deterministically, contradicting the JSDoc promise that an
over-budget value is rejected as over-budget regardless. Record the number
violation in a flag and let metering finish; return non-lossless only once the
whole value is confirmed within budget. Add a regression test asserting both
member orders classify as over-budget.

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

..

protocol-mirror.e2e.ts

fix(code-runtime-python): close coverage gap and tighten the wire mirror

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

protocol.spec.ts

fix(code-runtime-python): make checkDoneValue over-budget precedence order-independent

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