/* !important, AND IT IS NOT LAZINESS — the rule below lost every fight it
 * entered, and the fake italic shipped anyway.
 *
 * Eight page-level rules set `font-style: italic` on `em`: .pagehead h1 em,
 * .deepband h2 em, .mega em, .big em, .lede h2 em, .closer h2 em, #cineCopy h1
 * em, .devnotice h2 em, .authtitle em. Every one of them scores 0-2-2 or better
 * against this selector's 0-1-2, and this file is imported BEFORE them, so it
 * loses on specificity and on source order. Measured on /hy/contact: the
 * heading «Եկեք խոսենք։» computed `font-style: italic` — the exact rendering
 * the 2026-09-01 decision rejected, on the first Armenian heading to ship.
 *
 * Raising the selector to `.home3d em` would only tie, and the next page rule
 * would break it again. This is a correctness rule, not a preference: there is
 * no Armenian italic to fall back to, so no page may opt in to one.
 *
 * The founder caught it himself on the live page — "if I am not mistaken we
 * were not slanting emphasised Armenian" — which is exactly right, and is why
 * worker/renderer/hy-type-check.mjs now fails on it.
 */[lang=hy] em,[lang=hy] i{font-style:normal!important;font-weight:600;color:var(--metal,#a8712e)}[lang=hy] .home3d em{color:var(--metal,#a8712e)!important}[lang=hy] .authpage .authsub,[lang=hy] .sellerid dd.todo{font-style:normal!important}[lang=hy] .home3d .deep em,[lang=hy] .home3d .deepband em,[lang=hy] .home3d .deepsec em,[lang=hy] section.deep em{color:var(--metal-lit,#ce9a5a)!important}[lang=hy] .home3d .mega,[lang=hy] .home3d .pagehead h1{line-height:1.18}[lang=hy] .home3d #hero .d1,[lang=hy] .home3d .big,[lang=hy] .home3d .closer h2{line-height:1.22}[lang=hy] .home3d .lede h2{line-height:1.24}[lang=hy] #cineCopy h1{line-height:1.22}[lang=hy] .home3d .deepband h2{line-height:1.26}[lang=hy] .home3d .ft a[data-pending]:after{content:"շուտով"}