Streaming accepted a chunked body cut at a chunk boundary as complete,
so the limit now comes from the client that reads the body, picked per
requested size. Script requests keep their own default, maxBodySize
accepts sizes like 10MiB, and files sarin downloads for itself are
capped at 64MiB.
fasthttp allocates the body from the declared Content-Length before
reading it, so a server could exhaust memory by declaring a size it
never sends. The new max response body config bounds every response,
defaults to 10MiB and accepts sizes like 10MiB or 2MB. Scripts get the
same as a maxBodySize option on http().
- --log-level (comma-separated string: info, error): pick which logs are emitted;
the level set is resolved once, up front
- Log responses at the info level: full self-contained JSON to a file or stderr,
a compact "status duration | body" summary in the TUI log box
- Route logs independently of the progress display: the TUI log box when it runs,
stderr when piped, or a file via --log-file/-w (parent dir validated up front)
- Replace --quiet with --progress (bar | none, default bar): progress and logs are
now independent — progress=none still shows the log box; quiet == progress=none
with an empty log level
- Rename the internal "message" concept to "log" (runtimeLog, runtimeLogger, ...)
aykhans