openclaw message read --json silently truncates stdout at ~64KB, breaking JSON parse on large Discord reads

Reading Discord history through the OpenClaw CLI with openclaw message read --json --limit N produces unparseable output once the payload grows large. With --limit above roughly 30 on a busy channel, the JSON is cut off mid-object and any downstream parse fails with a JSONDecodeError at approximately char 65405 — i.e. right at a 64KB boundary. There is no error, no non-zero exit, and no warning: the command appears to succeed and simply emits a truncated document, so the failure looks like malformed API data rather than a stdout limit.