I can see you’ve provided the structural instructions but the actual article HTML content and language_code are missing from your message.

To proceed, please provide:

1. **The raw article HTML** (the ”P2 output”) that needs to be validated and repaired
2. **The language_code** (e.g., ”sv” for Swedish, ”en” for English, ”de” for German, etc.)

Once you supply those, I will apply your 13-point validation/repair logic:

– Ensure `

` blocks don’t exceed 2 consecutive occurrences without structural breaks (list/table/callout/quote)
– Place a `

` mini-summary after any `

` that has >300 words of prose following it
– Insert at least 2 callout divs (`

`, `n24-note`, or `n24-warning`) appropriately
– Ensure a stats line (`

`) is present after the intro
– Insert a key facts table near the top
– Replace English label tokens (like ”Bottom line:”, ”Frequently Asked Questions”, etc.) with the natural language equivalents for the given `language_code`
– Leave JSON-LD field names in English, but localize any visible user-facing text in the JSON-LD values
– Do not alter factual content, only structure and phrasing for voice/UX markers

Please paste the article HTML and state the language code.