/* ═══════════════════════════════════════════════════════════
   brand-fixes.css
   Override. Загружается после всех CSS чайлд-темы (priority 999).

   Назначение:
   1) Починить баг парент-генератора:
      `.wpdevart-comment-respond { color: #HEXpx; }` — невалидное значение.
   2) Нормализовать контраст ссылок формы ответа на комментарий
      (находится внутри светлой main-container, AAA вместо AA-large).
   ═══════════════════════════════════════════════════════════ */

.wpdevart-comment-respond,
.wpdevart-comment-respond p,
.wpdevart-comment-respond li {
    color: #1A1012 !important;
}

.wpdevart-comment-respond a:not(.reply a) {
    color: #6B1F2E !important;
}

.wpdevart-comment-respond a:hover:not(.reply a) {
    color: #2E0D14 !important;
}

/* ─── Home News hero: убираем legacy-фиолет и aurora-оверлей ───
   Источник бага: style.css строки 8833 (purple gradient) и 9138 (aurora).
   Решение: перекрыть overlay бургунди и отключить aurora ::before. */

.home-news__overlay {
    background: linear-gradient(
        115deg,
        rgba(46, 13, 20, 0.88),
        rgba(14, 8, 9, 0.92)
    ) !important;
}

.home-news::before {
    display: none !important;
    background: none !important;
    animation: none !important;
}

.home-news__btn,
.home-news__form button {
    background: var(--primary) !important;
    border-color: var(--primary) !important;
    color: #ffffff !important;
    box-shadow: 0 14px 30px rgba(107, 31, 46, 0.30) !important;
}

.home-news__btn:hover,
.home-news__form button:hover {
    background: var(--primary-600) !important;
    border-color: var(--primary-600) !important;
    box-shadow: 0 18px 44px rgba(107, 31, 46, 0.36) !important;
}

/* FORM FIELD LEGIBILITY — owner report 2026-08-17: fields go dark after data is entered.
 * MEASURED with headless Chrome on the live page: every field computes rgb(255,255,255) on
 * rgb(22,23,15) in BOTH colour schemes and the form carries no data-iz-dark, so neither the
 * dark-form path nor prefers-color-scheme explains it. What paints those boxes is Chrome's own
 * AUTOFILL background, which nothing on this form neutralises: the theme HAS the standard
 * white-inset fix but scoped to .home-contact__field, the HOME page form only, while the car and
 * contact pages render form.dag-form. iz-forms.css deliberately only freezes the transition and
 * leaves the colour to the theme, so this is a real gap and not a duplicate rule. */
form :is(input,textarea,select):-webkit-autofill,
form :is(input,textarea,select):-webkit-autofill:hover,
form :is(input,textarea,select):-webkit-autofill:focus,
form :is(input,textarea,select):-webkit-autofill:active{
  -webkit-box-shadow:0 0 0 1000px #fff inset!important;
          box-shadow:0 0 0 1000px #fff inset!important;
  -webkit-text-fill-color:#16170f!important;
  caret-color:#16170f!important;
}

/* HONEYPOT out of layout. Measured live: dag_hp renders as a VISIBLE 28x46 text input, against the
 * fleet contract that every honeypot is hidden. It does carry tabindex="-1" and autocomplete="off",
 * so tabbing and autofill cannot reach it -- but a stray CLICK still can, and a filled honeypot
 * means the lead is dropped as spam behind an identical /thank-you/ redirect. Moved out of flow
 * rather than display:none, which some bots use as a tell. */
form input[name="dag_hp"], form input[name="hp"], form input[name="iz_hp"],
form input[name="hp_field"], form input[name="website"]{
  position:absolute!important; left:-9999px!important; top:auto!important;
  width:1px!important; height:1px!important; padding:0!important; border:0!important;
  opacity:0!important; pointer-events:none!important;
}

/* CORNER LANGUAGE — owner instruction 2026-08-17. MEASURED over home + /inventory/ + /contact/:
 * this site is ROUNDED, not square — 85 of 110 surfaces (77%) carry a radius. Its language is
 * pill buttons (999px x17), cards at 14/16/18px and fields at 12px. The outliers are therefore the
 * SQUARE ones, the opposite of the sibling 410 root, which is why no blanket rule can serve both.
 * Fixed here: every photo and gallery thumbnail computed 0px while every card around it is rounded
 * (18 images), and the button set was split 999px x17 against 2px x6 and 10px x1.
 * 14px for imagery is the modal card radius on this site, so a photo now matches the card it sits in.
 * The 14/16/18 spread across card families is left alone deliberately: it reads as a size hierarchy,
 * not as drift, and flattening it would be a design decision rather than a consistency fix. */
html body :is(img,picture,figure,.wp-post-image,.attachment-thumbnail,
  .home-featured__media,.cyp-card__media,.home-brands__item img,
  .slick-slide img,.swiper-slide img,.dag-gallery img,.gallery-item img){
  border-radius:14px!important;
}
html body :is(button,.btn,a.btn,.sr-btn,.dag-btn,input[type="submit"],button[type="submit"]){
  border-radius:999px!important;
}