/* ────────────────────────────────────────────────────────────────────────── RECATOOLS — editorial dynamic-block components (the 5 types) ---------------------------------------------------------------------------- The canonical reader-facing look of fact-grid / verdict / timeline / compare / severity, lifted VERBATIM from resources/views/news/show.blade.php so the TipTap composer is true WYSIWYG — the editor canvas renders each component exactly as the published article does. Tokens (--rt-*) come from public/assets/css/rt-tokens.css — load that FIRST. SINGLE SOURCE OF TRUTH: both the TipTap editor canvas (resources/js/editor/ index.js, which carries the `article-body` class) AND the public reader page (resources/views/news/show.blade.php) consume THIS file — the inline copies were removed from show.blade.php on 2026-06-03 (follow-up to P3-7.1, see docs/editorial-ingestion-design.md §18). SPECIFICITY NOTE — why some selectors carry an `.article-body` / `aside` prefix. On the reader page , so every rule in the page's nested `.rt-theme-v2 { … }` block (incl. the generic prose rules `.article-body th|td|p|aside`) gains +1 class of specificity, landing at (0,2,1). A bare `.news-compare thead th` (0,1,2) would therefore LOSE to the page's `.article-body th`, and `.article-body .news-verdict` (0,2,0) would lose to `.article-body aside`. To preserve the exact reader-page cascade we raise ONLY the selectors that have a competing generic rule to the `.article-body …` tier (and verdict → `aside.news-verdict`). Both contexts nest these under `.article-body`, so the prefix matches in the editor too. This file MUST be linked AFTER the page's inline