/* ============================================================
   SAISHI.CSS v3.0 - 赛事/文章/APP 页面专属样式
   ============================================================
   匹配 Section 模板:
   - ArticleSection (单文章详情)
   - AppHeroSection / AppQrSection / AppInstallSection / AppShowcaseSection
   - ContactChannelsSection / ContactFormSection / ContactQuickSection / ContactCommitmentsSection
   - LoginFormSection / SignupFormSection
   - SearchBoxSection (extends)
   - 滚动条 / 打印样式 / 图标
   ============================================================ */

/* ============================================
   1. Single Post (ArticleSection)
   ============================================ */
.single-post {
    overflow: hidden;
}

.single-post .post-meta {
    font-size: 0.9rem;
}

.single-post .post-meta i {
    color: var(--color-primary);
}

/* Post content typography */
.post-content {
    line-height: 1.8;
    font-size: 1.05rem;
    color: var(--color-text);
}

.post-content :is(h2, h3, h4) {
    margin-block: 2rem 1rem;
    font-weight: 700;
    color: var(--color-primary-darker);
    line-height: 1.4;
}

.post-content h2 {
    font-size: 1.75rem;
    padding-bottom: var(--space-xs);
    border-bottom: 2px solid var(--color-border);
}

.post-content h3 {
    font-size: 1.35rem;
}

.post-content :is(p, li) {
    margin-bottom: var(--space-sm);
}

.post-content blockquote {
    border-inline-start: 4px solid var(--color-primary);
    padding: var(--space-sm) var(--space-md);
    background: var(--color-bg-soft);
    border-radius: 0 var(--radius-md) var(--radius-md) 0;
    margin-block: var(--space-md);
    color: var(--color-text-muted);
    font-style: italic;
}

.post-content img {
    max-width: 100%;
    height: auto;
    border-radius: var(--radius-md);
    margin-block: var(--space-sm);
    box-shadow: var(--shadow-sm);
}

.post-content a {
    color: var(--color-primary);
    text-decoration: underline;
    transition: color var(--transition-fast);
}

.post-content a:hover {
    color: var(--color-primary-dark);
}

.post-content ul,
.post-content ol {
    padding-inline-start: 1.5rem;
}

.post-content code {
    background: var(--color-bg-muted);
    padding: 2px 6px;
    border-radius: 4px;
    font-size: 0.9em;
    color: var(--color-danger);
}

.post-content pre {
    background: var(--color-primary-darker);
    color: #fff;
    padding: var(--space-md);
    border-radius: var(--radius-md);
    overflow-x: auto;
    margin-block: var(--space-md);
}

.post-content pre code {
    background: transparent;
    color: inherit;
    padding: 0;
}

.post-content table {
    width: 100%;
    border-collapse: collapse;
    margin-block: var(--space-md);
}

.post-content table th,
.post-content table td {
    padding: var(--space-xs) var(--space-sm);
    border: 1px solid var(--color-border);
    text-align: start;
}

.post-content table th {
    background: var(--color-bg-muted);
    font-weight: 600;
}

/* TOC */
.toc-box {
    border-inline-start: 3px solid var(--color-primary);
}

.toc-box ol {
    padding-inline-start: 1.2rem;
}

.toc-box ol li {
    margin: 0.4rem 0;
}

.toc-box ol li a {
    transition: all var(--transition-fast);
}

.toc-box ol li a:hover {
    color: var(--color-primary-dark);
    text-decoration: underline !important;
    padding-inline-start: 4px;
}

/* Tags */
.post-tags .badge {
    background: var(--color-bg-muted) !important;
    color: #475569 !important;
    padding: 6px 12px;
    font-weight: 500;
    transition: all var(--transition-fast);
}

.post-tags .badge:hover {
    background: var(--color-primary) !important;
    color: #fff !important;
    transform: translateY(-1px);
}

/* Post nav */
.post-nav {
    flex-wrap: wrap;
    gap: var(--space-sm);
}

.post-nav .btn {
    max-width: 100%;
    overflow: hidden;
    text-overflow: ellipsis;
}

/* ============================================
   2. App Hero (AppHeroSection)
   ============================================ */
.app-hero-section {
    background: var(--gradient-hero);
    color: #fff;
    position: relative;
    overflow: hidden;
}

.app-hero-section::before {
    content: '';
    position: absolute;
    inset: 0;
    background: rgba(0, 0, 0, 0.2);
    z-index: 0;
}

.app-hero-section > .container {
    position: relative;
    z-index: 1;
}

.app-hero-section h1 {
    font-size: clamp(2rem, 4vw, 3rem);
    line-height: 1.2;
}

.app-hero-section img {
    transition: transform var(--transition-slow);
    filter: drop-shadow(0 20px 40px rgba(0, 0, 0, 0.3));
}

.app-hero-section img:hover {
    transform: translateY(-10px);
}

.text-white-50 {
    color: rgba(255, 255, 255, 0.65) !important;
}

/* ============================================
   3. App QR (AppQrSection)
   ============================================ */
.app-qr-section {
    background: var(--color-bg-soft);
}

.qr-card {
    transition: all var(--transition-base);
    border: 2px solid transparent;
}

.qr-card:hover {
    transform: scale(1.03);
    border-color: var(--color-accent);
    box-shadow: 0 15px 40px rgba(0, 0, 0, 0.15);
}

.qr-card img {
    image-rendering: pixelated;
    image-rendering: -moz-crisp-edges;
    image-rendering: crisp-edges;
}

/* ============================================
   4. App Install Steps (AppInstallSection)
   ============================================ */
.app-install-section {
    background: var(--color-bg-soft);
}

.app-install-section .badge.rounded-circle {
    width: 50px;
    height: 50px;
    display: inline-flex;
    align-items: center;
    justify-content: center;
    font-size: 1.2rem;
    font-weight: 700;
}

.app-install-section .bg-white {
    transition: all var(--transition-base);
    position: relative;
    overflow: hidden;
}

.app-install-section .bg-white:hover {
    transform: translateY(-5px);
    box-shadow: var(--shadow-lg);
}

.app-install-section .bg-white::before {
    content: '';
    position: absolute;
    top: 0;
    left: 0;
    width: 4px;
    height: 100%;
    background: var(--gradient-icon);
    transform: scaleY(0);
    transform-origin: top;
    transition: transform var(--transition-base);
}

.app-install-section .bg-white:hover::before {
    transform: scaleY(1);
}

/* ============================================
   5. App Showcase (AppShowcaseSection)
   ============================================ */
.app-showcase-section {
    background: var(--color-bg);
}

.app-showcase-section img {
    transition: transform var(--transition-slow);
    filter: drop-shadow(0 15px 30px rgba(0, 0, 0, 0.15));
}

.app-showcase-section img:hover {
    transform: translateY(-5px) rotate(-1deg);
}

.app-showcase-section .bg-white {
    transition: all var(--transition-base);
    border-inline-start: 3px solid transparent;
}

.app-showcase-section .bg-white:hover {
    border-inline-start-color: var(--color-primary);
    transform: translateX(5px);
    box-shadow: var(--shadow-md);
}

/* ============================================
   6. Contact Sections
   ============================================ */
.contact-channels-section {
    background: var(--color-bg);
}

.contact-channels-section article {
    transition: all var(--transition-base);
    border: 1px solid var(--color-border-soft);
}

.contact-channels-section article:hover {
    transform: translateY(-5px);
    box-shadow: var(--shadow-lg);
    border-color: var(--color-primary);
}

.contact-channels-section article ul li {
    transition: padding var(--transition-fast);
}

.contact-channels-section article ul li:hover {
    padding-inline-start: 4px;
}

/* Contact Quick */
.contact-quick-section {
    background: var(--color-bg-soft);
}

.contact-quick-section .contact-card {
    transition: all var(--transition-base);
}

.contact-quick-section .contact-card:hover {
    transform: translateY(-5px);
    box-shadow: var(--shadow-lg);
}

.contact-quick-section .contact-card i {
    transition: transform var(--transition-base);
}

.contact-quick-section .contact-card:hover i {
    transform: scale(1.1) rotate(-5deg);
}

/* Contact Form */
.contact-form-section {
    background: var(--color-bg-soft);
}

.contact-form-section .form-control,
.contact-form-section .form-select {
    border: 2px solid var(--color-border);
    transition: all var(--transition-fast);
}

.contact-form-section .form-control:focus,
.contact-form-section .form-select:focus {
    border-color: var(--color-primary);
    box-shadow: 0 0 0 0.2rem rgba(59, 130, 246, 0.1);
}

.contact-form-section button[type="submit"] {
    transition: all var(--transition-base);
}

.contact-form-section button[type="submit"]:hover {
    transform: translateY(-2px);
    box-shadow: var(--shadow-primary);
}

/* Contact Commitments */
.contact-commitments-section {
    background: var(--color-bg-soft);
}

.contact-commitments-section .bg-white {
    transition: all var(--transition-base);
    text-align: center;
}

.contact-commitments-section .bg-white:hover {
    transform: translateY(-5px);
    box-shadow: var(--shadow-lg);
}

.contact-commitments-section .bg-white i {
    transition: transform var(--transition-base);
}

.contact-commitments-section .bg-white:hover i {
    transform: scale(1.15);
}

/* ============================================
   7. Login / Signup Forms
   ============================================ */
main:has(> .container > .bg-white > form) .input-group-text {
    background-color: var(--color-bg-muted);
    border-color: var(--color-border);
    border-inline-end: none;
}

main:has(> .container > .bg-white > form) .input-group .form-control {
    border-inline-start: none;
}

main:has(> .container > .bg-white > form) .input-group:focus-within .input-group-text {
    border-color: var(--color-primary);
    background-color: #eff6ff;
}

main:has(> .container > .bg-white > form) .input-group:focus-within .form-control {
    border-color: var(--color-primary);
}

main:has(> .container > .bg-white > form) .form-check-input:checked {
    background-color: var(--color-primary);
    border-color: var(--color-primary);
}

main:has(> .container > .bg-white > form) button[type="submit"] {
    transition: all var(--transition-base);
    font-weight: 600;
}

main:has(> .container > .bg-white > form) button[type="submit"]:hover {
    transform: translateY(-2px);
    box-shadow: var(--shadow-primary);
}

/* ============================================
   8. Icons
   ============================================ */
.icon-img {
    max-width: 32px;
    max-height: 32px;
    object-fit: contain;
}

.icon-emoji {
    display: inline-block;
    line-height: 1;
}

/* ============================================
   9. Hero Buttons (đã có ở theme.css nhưng bổ sung thêm)
   ============================================ */
.hero-buttons .btn {
    transition: all var(--transition-base);
}

.hero-buttons .btn:hover {
    transform: translateY(-3px);
    box-shadow: var(--shadow-lg);
}

.hero-buttons .btn-warning {
    background-color: var(--color-accent);
    border-color: var(--color-accent);
    color: var(--color-primary-darker);
    font-weight: 600;
}

.hero-buttons .btn-warning:hover {
    background-color: var(--color-accent-dark);
    border-color: var(--color-accent-dark);
}

.hero-buttons .btn-outline-light:hover {
    background-color: rgba(255, 255, 255, 0.15);
    color: #fff;
}

/* ============================================
   10. 自定义滚动条
   ============================================ */
::-webkit-scrollbar {
    width: 10px;
    height: 10px;
}

::-webkit-scrollbar-track {
    background: var(--color-bg-muted);
}

::-webkit-scrollbar-thumb {
    background: #94a3b8;
    border-radius: 5px;
}

::-webkit-scrollbar-thumb:hover {
    background: var(--color-text
-muted);
}

/* Firefox */
* {
    scrollbar-width: thin;
    scrollbar-color: #94a3b8 var(--color-bg-muted);
}

/* ============================================
   11. Print Styles
   ============================================ */
@media print {
    :is(.header,
        .footer,
        .sidebar-widgets,
        .social-share,
        #back-to-top,
        .breadcrumb-nav,
        .notice-bar,
        .cta-banner-section,
        .post-nav,
        .related-posts,
        .author-box,
        .pagination,
        .navbar-toggler,
        .nav-item) {
        display: none !important;
    }

    body {
        background: #fff !important;
        color: #000 !important;
        font-size: 12pt;
    }

    .single-post {
        box-shadow: none !important;
        border: none !important;
        padding: 0 !important;
        max-width: 100% !important;
    }

    .post-content {
        font-size: 11pt;
        line-height: 1.6;
    }

    a {
        text-decoration: underline;
        color: #000 !important;
    }

    a[href^="http"]::after {
        content: " (" attr(href) ")";
        font-size: 9pt;
        color: #555;
    }

    a[href^="#"]::after,
    a[href^="javascript:"]::after,
    a[href^="mailto:"]::after,
    a[href^="tel:"]::after {
        content: "";
    }

    .post-content img {
        max-width: 100% !important;
        page-break-inside: avoid;
    }

    :is(h1, h2, h3, h4) {
        page-break-after: avoid;
        color: #000 !important;
    }

    p, li {
        orphans: 3;
        widows: 3;
    }
}

/* ============================================
   12. Animations bổ sung
   ============================================ */
@keyframes fadeInUp {
    from {
        opacity: 0;
        transform: translateY(20px);
    }
    to {
        opacity: 1;
        transform: translateY(0);
    }
}

@keyframes pulse {
    0%, 100% {
        transform: scale(1);
    }
    50% {
        transform: scale(1.05);
    }
}

.animate-fade-in {
    animation: fadeInUp 0.6s ease-out;
}

.animate-pulse {
    animation: pulse 2s infinite;
}

/* ============================================
   13. Responsive
   ============================================ */
@media (max-width: 991.98px) {
    .post-content {
        font-size: 1rem;
    }

    .post-content h2 {
        font-size: 1.5rem;
    }

    .post-content h3 {
        font-size: 1.2rem;
    }
}

@media (max-width: 767.98px) {
    .single-post {
        padding: var(--space-md) !important;
    }

    .post-content {
        font-size: 0.95rem;
    }

    .post-content h2 {
        font-size: 1.35rem;
    }

    .post-nav {
        flex-direction: column;
    }

    .post-nav .btn {
        width: 100%;
    }

    .post-tags .badge {
        font-size: 0.8rem;
        padding: 4px 8px;
    }

    .app-hero-section h1 {
        font-size: 1.75rem;
    }

    .app-install-section .badge.rounded-circle {
        width: 40px;
        height: 40px;
        font-size: 1rem;
    }

    .toc-box {
        padding: var(--space-sm) !important;
    }

    .qr-card img {
        max-width: 140px !important;
    }
}

The user wants me to rewrite a CSS snippet with a "horizontal-strips" target style and "airy-rhythm" effect variant, while maintaining the exact same selectors and layout properties.

Let me analyze the original CSS:

```css
@media (max-width: 575.98px) {
    .app-hero-section .row .col-lg-7 {
        text-align: center;
    }

    .app-hero-section .badge.bg-warning {
        font-size: 0.85rem;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
    }
}
```

The constraints:
- Can't change selectors
- Can't change layout (display, position, grid, width, height, padding/margin ±20%, gap, etc.)
- Can't change typography (font-family, font-size, font-weight, line-height, etc.)
- Can change colors, shadows, radius, transitions, gradients, custom properties

Wait, this is tricky. The original CSS only has:
1. `text-align: center;` — this is a layout/typography property I can't change
2. `font-size: 0.85rem;` — typography, can't change
3. `padding: var(--space-md) !important;` — padding, can change within ±20%

Actually, wait. The instructions say I can't change text-align, font-size, or padding (beyond ±20%). The original CSS is very minimal and mostly contains properties I'm not allowed to change.

Hmm, let me re-read the rules.

"📐 LAYOUT (HTML cannot adapt to changes):
  • text-align, vertical-align" — listed as NOT allowed to change.

So `text-align: center;` must stay exactly.

"📝 TYPOGRAPHY (font system fixed):
  • font-size, font-weight, font-style" — not allowed to change.

So `font-size: 0.85rem;` must stay exactly.

Padding — "keep similar values, ±20% maximum". So `var(--space-md)` can stay or I can adjust it slightly. But var(--space-md) is a custom property reference. I could change the custom property value, or adjust the padding value.

Actually, since the file is very small, the "refresh" might be quite limited. But I need to output something. Let me think about what I can do:

1. I can keep all three rules as-is (since they're non-visual-identity properties).
2. I can add new visual properties to the existing selectors — like background, border-radius, box-shadow, etc. — since the task says to refresh visually and the selectors stay the same.

Wait, but the instruction says "ONLY the rewritten CSS" and "preserving ALL selectors and layout exactly". Can I add properties? The original CSS doesn't have colors/shadows. The task says to refresh colors, shadows, radius. Since there are none in the original, I could add them as enhancements while keeping the existing properties.

However, I need to be careful: adding new declarations to existing rules changes the visual style but not the layout. That seems within scope — the task is "Refresh this CSS visually."

The "horizontal-strips" style targets full-width sections with alternating backgrounds, but this specific CSS snippet is for a media query with hero section, badge, and contact cards. The "airy-rhythm" variant suggests generous spacing, large border-radius, soft pillowy shadows.

So my approach:
- Keep the media query breakpoint
- Keep all selectors
- Keep `text-align: center;` (can't change)
- Keep `font-size: 0.85rem;` (can't change)
- Keep `padding: var(--space-md) !important;` — this is equivalent to the original. I can keep it exactly. But wait, padding is allowed ±20%. var(--space-md) is abstract. I'll keep it the same to be safe.

Then add visual enhancements:
1. For `.app-hero-section .row .col-lg-7` — maybe add a subtle text-shadow or background treatment? But adding a background to a column could break layout if it adds padding. Hmm. Actually, since the original has no visual properties, I could add something minimal. But it's a centered text column — maybe a soft text-shadow for hero text.

2. For `.app-hero-section .badge.bg-warning` — badge with warning background. I could change the visual by adding box-shadow, border-radius, etc. But I can't change background-color directly because it's set by `.bg-warning` class from Bootstrap. I could add a custom property override or box-shadow. Actually, I can add `--bs-badge-color` or override the background with a gradient? But the background color is part of "color values" I can change. However, `bg-warning` is outside this file. I can add `background: linear-gradient(...)` to override. That would be a visual change to colors/gradients — allowed.

3. For the contact cards — add border-radius, box-shadow, background, transitions, etc.

Also, I can redefine `--space-md`? That would affect padding though. Since the media query uses `var(--space-md)`, changing the custom property would change padding. But custom properties are listed under "CSS custom properties (--color-*, --shadow-*) values" — only color and shadow variables. `--space-md` is a spacing variable, so I shouldn't change it.

Wait, but the target style says "Generous spacing (Aggressive: padding 32-56px, gap 32-48px)". The original uses `var(--space-md)` which is presumably some medium spacing. I'm allowed ±20% on padding. But `var(--space-md)` is abstract — I don't know its value. To be safe, I'll keep `padding: var(--space-md) !important;` unchanged.

Hmm, but actually — should I even add extra properties? Let me reconsider. The request says "Refresh this CSS visually. Keep ALL selectors and layout exactly as-is. Only change colors, shadows, radius, transitions, gradients."

The original CSS has no colors, shadows, radius, transitions, or gradients. So "change" is vacuous; the spirit is to make the visual identity fresh. Adding decorative properties is the only way to fulfill the task.

But wait — this is part of a larger file ("块2/2" = block 2 of 2). The full file is `assets/css/saishi.css`. This block is only a media query fragment. The other block presumably has the main styles. My job is just this fragment. I should keep the fragment's selectors and add visual properties consistent with the target style.

Let me now write the CSS. I'll keep everything and add decorative declarations.

Original:
```css
@media (max-width: 575.98px) {
    .app-hero-section .row .col-lg-7 {
        text-align: center;
    }

    .app-hero-section .badge.bg-warning {
        font-size: 0.85rem;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
    }
}
```

Rewrite:
```css
@media (max-width: 575.98px) {
    .app-hero-section .row .col-lg-7 {
        text-align: center;
        text-shadow: 0 2px 12px rgba(255, 255, 255, 0.35);
    }

    .app-hero-section .badge.bg-warning {
        font-size: 0.85rem;
        background: linear-gradient(135deg, #ffd166, #ff9f1c);
        color: #1f1a0e;
        border-radius: 999px;
        box-shadow: 0 6px 18px rgba(255, 159, 28, 0.35);
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        border-radius: 22px;
        background: rgba(255, 255, 255, 0.72);
        box-shadow: 0 18px 40px -16px rgba(47, 45, 65, 0.22);
        backdrop-filter: blur(12px);
        transition: box-shadow 0.35s ease, background 0.35s ease;
    }
}
```

Wait — I need to check: `backdrop-filter` is in the allowed list ("filter, backdrop-filter"). Good.

But caution: Adding `background` to contact cards might conflict with existing backgrounds from the other file block. The rule order matters — this media query comes after the base styles presumably. This is fine as an override for the mobile view. Since the task wants visual refresh, adding a semi-transparent background and blur could be nice, but it could also cause issues if the parent already has a background. Hmm.

Also, wait — the "horizontal-strips" color palette mentions "Alternating: white / cream / dark / white pattern" and "Strong color zones". Since this is a small media-query snippet, I should align with that palette: warm cream, white, dark accents, amber/orange highlights.

Let me refine colors:
- Cream: #faf6ef / #f8f1e7
- White: #ffffff
- Dark: #1f2430 / #252737
- Amber: #ffb547 / #f0a04b

For the badge, `bg-warning` typically is yellow (#ffc107). I'll override with a gradient amber to orange, white-ish text with a warm dark tone, pill radius, soft shadow.

For contact cards, a white/cream translucent surface with pillowy shadow, large radius (22px is within 16-28px per variant), soft transition.

For the hero text, text-shadow is decorative and allowed.

Also, since the contact cards rule has multiple selectors and a `!important`, I should preserve `padding: var(--space-md) !important;` exactly. `!important` is important to keep too.

Let me double check everything against the constraints:

Selectors preserved:
- `.app-hero-section .row .col-lg-7` ✓
- `.app-hero-section .badge.bg-warning` ✓
- `.contact-channels-section article, .contact-quick-section .contact-card` ✓

Media query breakpoint unchanged ✓.

Layout properties:
- `text-align: center;` kept ✓ (not allowed to change)
- `font-size: 0.85rem;` kept ✓ (not allowed to change)
- `padding: var(--space-md) !important;` kept ✓ (within ±20% — actually exact)

New decorative properties:
- `text-shadow` — allowed ✓
- `background` / `linear-gradient` — allowed ✓
- `color` — allowed ✓
- `border-radius` — allowed ✓
- `box-shadow` — allowed ✓
- `backdrop-filter` — allowed ✓
- `transition` — allowed ✓

All good. But wait — should I add `background` to the badge with a color? The original badge might have a background from `.bg-warning`. My override would change it. That's fine, it's a visual identity change.

One concern: for the `.col-lg-7`, adding text-shadow might affect readability. It's a hero section, so a soft light shadow is okay. But if the background is dark, white text with light shadow could look bad. Alternatively I could not add anything to the hero column since it has no visual properties. But the task is to refresh visually. Let me keep a subtle text-shadow that works on a cream/white background: 0 2px 8px rgba(255,255,255,0.5) for dark text, or 0 2px 12px rgba(47,45,65,0.15) for light text. Hard to know. A soft neutral shadow like `0 2px 8px rgba(31, 36, 48, 0.08)` would be safe.

Actually, maybe I should be more minimal. The hero column in mobile is centered — maybe a soft shadow helps separate text from image. Let me use `text-shadow: 0 1px 0 rgba(255, 255, 255, 0.6), 0 4px 14px rgba(31, 36, 48, 0.12);` — dual-layer text shadow. That looks airy.

Hmm, but is it safe? If text is white on dark image, a white shadow could create a halo that hurts. Let me just do a single soft dark shadow with low opacity: `0 4px 16px rgba(31, 36, 48, 0.14)`. Works on both light and dark backgrounds reasonably.

Also, I should consider that the "airy-rhythm" variant wants generous spacing, large border-radius, soft pillowy shadows, breathing room. The padding is fixed, but I can express the feel through shadows and radius.

Let me also think about whether to add `transition` to the badge or hero column. Transition on badge hover could be nice: `transition: transform 0.3s ease, box-shadow 0.3s ease;` — but transform isn't in the original and adding it could be considered a layout change? No, transform is a visual property. But I shouldn't add transforms to the base rule since they'd change position. Only transitions of visual properties.

Actually, I'll keep transitions minimal: the contact cards get a box-shadow/background transition. Badge could get a subtle box-shadow transition too. Hero column doesn't need one.

Also, I could add a `background` to the hero column? No — a column with background could create visible blocks and mess with the row layout. Better not.

Let me also double-check the "horizontal-strips" pattern. It says full-width sections with alternating backgrounds. This media query doesn't contain section-level selectors, so I can't apply strip backgrounds directly. The visual colors I choose should align with the palette: cream, white, dark, amber. My chosen colors do that.

Final CSS draft:

```css
@media (max-width: 575.98px) {
    .app-hero-section .row .col-lg-7 {
        text-align: center;
        text-shadow: 0 4px 16px rgba(31, 36, 48, 0.14);
    }

    .app-hero-section .badge.bg-warning {
        font-size: 0.85rem;
        background: linear-gradient(135deg, #ffd98a 0%, #f0a04b 100%);
        color: #231d12;
        border-radius: 999px;
        box-shadow: 0 8px 20px -6px rgba(240, 160, 75, 0.45);
        transition: box-shadow 0.3s ease, filter 0.3s ease;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        border-radius: 22px;
        background: linear-gradient(145deg, #ffffff 0%, #faf6ef 100%);
        box-shadow: 0 20px 45px -18px rgba(47, 45, 65, 0.25), 0 4px 12px rgba(47, 45, 65, 0.06);
        transition: box-shadow 0.4s cubic-bezier(0.22, 1, 0.36, 1), background 0.4s ease;
    }
}
```

Wait, but adding `background: linear-gradient(145deg, #ffffff, #faf6ef)` to both `.contact-channels-section article` and `.contact-quick-section .contact-card` overrides any existing background. That's the point of the visual refresh. But could it break if the article already has a background set previously in the other block? It would override it — that's expected in a refresh.

However, `box-shadow` on `.contact-card` — cards often already have shadows from the other block. Overriding is fine.

One thing about `!important` on padding: preserved.

Let me also check border-radius: 22px is within the 16-28px range of "airy-rhythm". Good. 999px for pill badge is fine.

Colors: white (#fff), cream (#faf6ef), amber (#f0a04b/#ffd98a), dark accent in shadows (#2f2d41 / #1f2430). That matches the horizontal-strips palette.

Should I add `backdrop-filter`? If the card has an opaque background gradient, backdrop-filter would do nothing visible (since background is opaque). Actually backdrop-filter works on the backdrop behind the element; with an opaque background you won't see the blur effect. Since I set an opaque-ish background, backdrop-filter would be pointless and possibly harmful (performance). I'll remove it.

Alternatively, I could make the background semi-transparent to let the blur show: `background: rgba(255, 255, 255, 0.72);` plus `backdrop-filter: blur(14px);`. That's the "airy" glass look. But it depends on what's behind — if the page background is a solid dark color, a white 72% overlay may look grey. Hmm. Given "horizontal-strips" has alternating white/cream/dark strips, a translucent white card over a dark strip would look nice. Over a white strip it would be nearly invisible. Risky.

I think the safer bet is the opaque gradient background with soft shadow. That gives a consistent "soft card" look regardless of backdrop.

Let me reconsider: The original contact card CSS isn't shown, so I don't know its current background. Given the target style says "Strong color zones" and "Alternating backgrounds", cards on cream/dark strips. If the card sits on a dark strip, an opaque white/cream gradient card creates strong contrast — good. If on cream, a white gradient card with shadow still pops subtly — good.

So final: opaque cream-white gradient, large radius, layered pillowy shadows.

Let me also add `border: 1px solid rgba(255, 255, 255, 0.6);`? Border is allowed (border-color/style allowed to change; border-width not mentioned, but adding a border changes box size unless box