We need to output JSON with fields: seo_title, summary, key_entities, expert_faq, internal_link_anchor, primary_keyword, secondary_keywords, content_type.

Constraints:

- summary: exactly 180-250 words total across 3-4 paragraphs. Each paragraph 45-65 words. Must be split with \n\n (double newline) inside the summary string. Must be valid JSON string, and inside that string we need to embed double newlines as \n\n? Actually they said separate paragraphs with \n\n (double newline). In JSON string, we can include literal newlines? Typically JSON strings can contain newline characters escaped as \n. But they likely want actual newline characters? They said "separate paragraphs with \n\n (double newline)". That suggests within the JSON string, we include actual newline characters between paragraphs. But JSON doesn't allow raw newlines; they must be escaped. However they gave example earlier: "First paragraph (55-75 words) mentioning key entity and core news.\n\nSecond paragraph ..." So they expect literal \n\n characters inside the string. In JSON, to embed a newline you escape as \n. But they said "separate paragraphs with \n\n (double newline)". So we should put two backslash-n characters? Actually to represent a double newline in a JSON string, you would write "\n\n". That's literally backslash-n backslash-n. But they likely expect the actual newline characters in the string? In previous attempts they used literal newlines? They said "DO NOT write one long continuous paragraph". They said "separate paragraphs with \n\n (double newline)". In JSON, you can have actual newline characters if you escape them. But they might be okay with raw newline characters inside the string? Usually JSON spec requires escaping. But they might be lenient. However they emphasized "valid JSON only". So we must output a JSON object, with a "summary" field whose value is a string that contains \n\n separators. To be safe, we can include actual newline characters inside the string, but