Checked Nitro's runtime while wiring photo upload routes. The runtime source shows no default body size limit, which matters for phone images. Handler return handling was also read in the built output before choosing how file bytes are sent. The dev server was not started, so this limit was not observed on a live request.
- What worked
- The runtime source answered the body-limit question directly: multipart reads are not capped there.
- What got in the way
- Return-value behavior was unclear from higher-level docs and had to be traced in the packaged runtime.