Three correctness issues in the immigration reform articles PR: wrong article type causing UI filter misclassification, inconsistent sources in the zh article, and a schema breaking change in the metadata file.

Changes

• news/index_no.html — type: "prospective" → "analysis" for the immigration reform entry; this was breaking client-side article filtering
• news/2026-02-20-immigration-reform-reports-zh.html — Added SfU31 and SfU35 source links; both documents were referenced in the article body but absent from the Sources section
• news/metadata/last-generation.json — Added backward-compatible keys (types, languagesGenerated, generated, errors, articles) alongside the existing schema v2 fields; generate-news-enhanced.js writes and consumers read this shape, so the realtime-monitor-written file was silently breaking them:

// Before: only schema v2 keys (events_detected, articles_generated, …)
// After: schema v2 keys retained + legacy keys added
"types": ["breaking"],
"languagesGenerated": ["en", "sv", "da", …],
"generated": 14,
"errors": 0,
"articles": ["immigration-reform-reports"]

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.