We need to produce JSON with keys: summary, category, article_html. Summary 150-160 chars. Category "howto". article_html must contain full article in HTML. Must follow rules: - Exactly ONE H1 at start with primary keyword. Primary keyword: "best books to read in English for 12 year olds". - H2 for 5-7 main sections. Each section: 2-3 P tags, each 100-150 words. That's a lot: 5-7 sections * 2-3 paragraphs * 100-150 words. Minimum 1500 words. Let's compute: Suppose 6 sections, 2 paragraphs each, 120 words average -> 6*2*120 = 1440 words. That's close but maybe a bit under. If we do 3 paragraphs per section average 120 -> 6*3*120 = 2160 words. That meets 1500. So we need at least 1500 words. We'll produce 6 sections, each with 3 paragraphs of ~120-130 words. That's about 2160 words. Good. - H3 for subsections. We can include subsections within sections. Not required but allowed. - UL/OL lists 5-10 items. Provide book lists etc. - Strong for key terms. - End with 3-5 FAQ questions as H3. - Minimum 1500 words. - Must include specific book recommendations, authors, key takeaways. - No markdown, no code fences. Just JSON with article_html string containing HTML. We need to ensure article_html is valid. We'll produce a string with proper HTML markup. We need to escape quotes? In JSON, we need to escape double quotes inside string. But we can use single quotes for string? JSON requires double quotes for string values. So we need to escape any double quotes inside HTML. Better to use single quotes inside HTML to avoid escaping. But we can use " for quotes inside HTML. We'll use single quotes for attributes like class, but HTML attributes can be single quotes. But to avoid JSON escaping, we should use " instead of double quotes. Let's write HTML with single quotes. Also we need to keep within JSON. For readability, we still need to escape newline? But JSON can contain newline characters inside string, as \n. But for output, we can just output actual newlines? JSON allows newline inside string if properly escaped? In JSON, newline must be escaped as \n. However many systems allow raw newline? Usually JSON string cannot contain literal newline; must be escaped. So we need to escape newlines as \n. But the instruction: "Return ONLY valid JSON (no markdown, no code fences)" So we need to produce JSON. We can produce pretty-printed JSON with newline characters. But each newline inside string values must be escaped. But we can produce JSON with string containing \n. Let's produce a single-line JSON? That might be easier: article_html string with \n escapes. But we can produce JSON with multiline string using \n. Let's produce article_html with \n escapes. Ok. We need 1500+ words. Roughly 2160 words. Let's approximate. We need 6 sections. Let's outline: H2 sections: 1. Classic Picture Books & Graphic Novels 2. Middle-Grade Fantasy & Adventure 3. Mystery & Detective Stories 4. Science Fiction & Future Worlds 5. Historical & Biographical Reads 6. Nonfiction & Informational Titles Within each section, 3 paragraphs. Paragraph lengths ~120 words. Also include UL lists of 5-10 books with author, key takeaways. Also include H3 subsections maybe for each book? Too many. Maybe include H3 for "Why These Books Matter" within each section. Also end with FAQ H3. Make sure we use strong tags for key terms like "best books", "12-year-olds", "reading". Ok. Let's craft. We need to count words. Let's approximate. But we need to produce 1500+ words. We'll do ~2200. Let's start constructing article_html. We need to include meta description etc? Not required in article_html. Ok. Let's write. We'll produce article_html as string with \n. We'll use single quotes for attributes. Eg