Source Material Missing: Cricket Report Generation Blocked

The requested cricket news report cannot be provided because the Stage-1 output contained no actual source material. The Stage-1 result was an unfilled template: title, source, article type, core viewpoints, information points, entities and time sensitivity were all blank or marked N/A. The only valid signal was the domain label 'cricket_world', which indicates that the domain classifier ran but says nothing about any specific match, series or player. Writing a report from this would require inventing events, names, statistics and quotes, which is incompatible with factual reporting. Technically, this most likely reflects an upstream extraction failure: a paywall, a JavaScript-rendered page or anti-scraping blocking returned an empty body, and the pipeline silently filled in defaults. A second possibility is truncation or serialization loss in the Stage-1 output, where only the schema skeleton was returned. A third is that the input itself was an empty document. The correct next step is diagnosis rather than writing: check the raw input size, the length of the extracted body field, and the finish_reason in the Stage-1 call log. A finish_reason of 'length' would directly indicate truncation. A minimum-validity assertion should also be added to Stage-1 so that empty information points raise an error instead of passing an empty template downstream. Any one of the following will allow the real cricket report to be produced immediately: a rerun Stage-1 output, the original article text, or confirmation of whether other articles in the same batch processed normally.