Under the hood
A limit used in stream-json/headless input handling was raised from 50 to 512
What
An internal constant used somewhere in the handling of stream-json input (used in headless, non-interactive modes) was raised from 50 to 512, a tenfold increase.
Why
The finding does not say what this limit governs, so it isn't possible to say concretely what changes for users, but a limit raised by 10x suggests headless stream-json input can now handle substantially more of whatever this constant was capping.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What exactly this constant limits (e.g. queue size, buffered messages, line count) is not established by the evidence.