Your invoice-extraction service intermittently hands unparseable JSON to downstream consumers. You pull traces for the failing requests: every one ends with `stop_reason: "max_tokens"` and the JSON body is cut off mid-array, while successful requests end with `stop_reason: "end_turn"`. What is the correct diagnosis?