Source material unavailable: kabaddi report cannot be produced yet

The analysis supplied with this request is an empty Stage-1 output. Apart from 'Domain Label: kabaddi', no field is populated: no title, no source, no publication time, no one-sentence summary, no information points, no entities, no source-quality or time-sensitivity assessment. Producing a 2,140-word 'original sports news report' from this would mean inventing matches, scores, player names, teams, dates and quotes. I will not do that, because the result would be a sports story tied to no real event, read by people as fact. Technically, the problem is not 'thin information' but a deconstruction pipeline that produced nothing. Four causes are plausible: (1) upstream fetch failed and the input body was empty or only navigation/template text; (2) the body extractor judged the whole page to be noise, common with JS-rendered pages, paywalls and PDFs; (3) the classifier emitted 'kabaddi' first but the extraction stage exited with an exception, and the fallback wrote empty values; (4) the structured-output schema conversion dropped fields, e.g. an invalid JSON from the LLM was silently reset to defaults. In-depth analysis — argument decomposition, evidence-chain evaluation, stance inference, time-sensitivity judgement — must be anchored in concrete statements. The only usable signal right now is 'domain: kabaddi', which establishes nothing beyond the fact that upstream considered the material kabaddi-related. Anything built on top of that would be inference, not reporting. To write the report I need one of the following: the full original article text (most direct — it enables a complete analysis of arguments, evidence, stance and time sensitivity); the raw Stage-1 JSON or logs (to determine whether the failure is in extraction or in the schema); or, if the text genuinely cannot be retrieved, confirmable metadata only — title, publisher, publication date and URL — on which I can assess source quality and recency and state explicitly which conclusions remain out of scope. One engineering note: empty results like this should not be persisted as valid structures. Add an assertion at the Stage-1 exit — information_points.length > 0 && summary != '' — otherwise mark the record as extraction_failed and retain a snapshot of the raw input. Otherwise downstream will keep consuming data that looks normal but is empty, which is more dangerous than a hard error.