The child reads these byte budgets through int(...), which silently floors a float, so maxLogBytes: 3.5 would truncate at 3 bytes child-side while the host meters and marks at 3.5 — the two sides enforcing different public config. Gate them to integers at load, as the worker backend does; correct the stale comment that claimed the int()-truncated caps needed no gate. Adds a regression test. |
||
|---|---|---|
| .. | ||
| index.ts | ||
| invariant.ts | ||
| protocol.ts | ||