/* ============================================================
   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 CSS with a conservative mode. 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;
    }
}
```

This is a media query with three rules. The target style is "masonry-flow" with "tight-rhythm" effect variant.

Constraints:
- I can change: colors, box-shadow, text-shadow, border-radius, gradients, transitions, filter, backdrop-filter, opacity, outline styles, border-color and border-style (NOT border-width), caret-color, accent-color, CSS custom properties.
- I cannot change: selectors, display, position, grid-template, width, height, padding, margin (keep similar ±20% max), gap, font properties, text-align, etc.

Wait, but `text-align: center` is in the original — text-align is in the "never change" list (typography section includes text-align). So I must keep `text-align: center`.

`font-size: 0.85rem` — font-size is in the never change list. So keep it.

`padding: var(--space-md) !important` — padding is in never change (keep similar ±20%). `var(--space-md)` is a CSS custom property reference value. I could change the `--space-md` value? Actually custom properties are listed as changeable (CSS custom properties (--color-*, --shadow-*) values). But `--space-md` is a spacing variable, not color/shadow. The instruction says "CSS custom properties (--color-*, --shadow-*) values" — so only color and shadow custom properties. I shouldn't change `--space-md` since that would affect layout/padding values.

Hmm, but the task says "Refresh this CSS visually. Keep ALL selectors and layout exactly as-is. Only change colors, shadows, radius, transitions, gradients."

The original CSS block has:
1. `text-align: center` — not changeable
2. `font-size: 0.85rem` — not changeable
3. `padding: var(--space-md) !important` — padding not changeable beyond ±20%, but `var(--space-md)` is a variable reference. I can't change what it resolves to without changing the custom property definition somewhere else. I could replace it with a padding value within 20% of... well I don't know what --space-md is. Safer to keep it.

So actually this CSS block is entirely layout/typography with no colors. Hmm. What can I change?

Maybe I can add visual properties that don't affect layout:
- Add `border-radius` to the cards
- Add `box-shadow` to the cards
- Add `transition` for hover effects
- Add colors (background, border-color)
- The badge could get accent-color, etc.

But the strict instruction says "Preserving ALL selectors and layout exactly" and "ONLY the rewritten CSS". Adding new declarations to existing rules is allowed as long as they are visual-only (colors, shadows, radius, transitions, gradients).

However, in conservative mode, "HTML is FIXED — only colors, shadows, and decorative properties may change." Adding box-shadow to `.contact-card` is decorative, okay. Adding border-radius is decorative, okay.

But we should be careful: the media query is `max-width: 575.98px` (mobile). The target style "masonry-flow" is aggressive with white cards on light gray bg, soft shadows, accent strips. The "tight-rhythm" variant: compact spacing (8-16px padding, 8-12px gap), small border radius (2-6px), subtle shadows or none, information-dense.

I can refresh the visual identity by:
- Adding a subtle background color to the hero section? Or to the cards?
- Adding small border-radius to article and contact-card
- Adding subtle box-shadows to contact cards
- Adding transition for interactive feel

But I must not change selectors. I can add declarations to existing rules. Also I shouldn't add new selectors.

Let me think about what's reasonable. The original CSS has three rules. I can add visual-only declarations to each:

Rule 1: `.app-hero-section .row .col-lg-7 { text-align: center; }` — this centers text on mobile. I could add colors? Not appropriate for a column container. Maybe add nothing, or add a text-shadow? No, that would look weird. Keep as is.

Rule 2: `.app-hero-section .badge.bg-warning { font-size: 0.85rem; }` — the badge. I could add border-radius, box-shadow, border-color, background gradient? The class is `bg-warning` (Bootstrap warning yellow). I can change the visual identity by adding a `background` gradient, `border-radius`, `box-shadow`, `transition`. But careful: Bootstrap's `.bg-warning` sets background-color. Adding a background gradient would override or layer. That's a visual change, allowed.

Rule 3: `.contact-channels-section article, .contact-quick-section .contact-card { padding: var(--space-md) !important; }` — I can add border-radius, box-shadow, background, border, transition.

But wait — the instruction says "ONLY the rewritten CSS, preserving ALL selectors and layout exactly." The safest is to keep all existing declarations and add new visual-only declarations. But adding declarations may change the layout? box-shadow doesn't change layout. border-radius doesn't. background doesn't. border would change layout unless `border: 1px solid` adds to the box size (but box-sizing may be border-box in Bootstrap, typically border-box). Actually Bootstrap sets `box-sizing: border-box`, so adding a border doesn't change layout dimensions. But to be safe, maybe use `outline` instead? Or `box-shadow` with inset for a border effect.

Actually the "never change" list includes `box-sizing` but as a property value; I can't change it. Bootstrap sets border-box globally, so borders are safe. But the instruction explicitly says "border-color and border-style (NOT border-width)" — this means I am allowed to change border-color and border-style, but not border-width. If I add `border: 1px solid ...` that's adding border-width. Hmm, but if no border exists, adding one changes layout in content-box. To be safe, I can use `box-shadow: 0 0 0 1px color` to simulate a border without layout change.

Also, for the `bg-warning` badge — Bootstrap's badge has `display: inline-block` and padding. Adding background gradient is fine.

Let me consider the "tight-rhythm" variant: small border-radius 2-6px, subtle shadows or none. I'll use 4px radius and subtle shadows.

For the masonry-flow palette: Pinterest-like white cards, soft shadows on light gray bg, each card may have its own accent strip. The contact cards on mobile — I can give them a soft shadow and a small accent strip via `box-shadow: inset 3px 0 0 accent` (an inset shadow that creates an accent strip on the left without layout change). That's a nice touch.

Let me craft:

```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;
        border-radius: 4px;
        background: linear-gradient(135deg, #ffd166, #f4a261);
        box-shadow: 0 2px 6px rgba(244, 162, 97, 0.25);
        transition: box-shadow 0.25s ease, transform 0.25s ease;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        border-radius: 4px;
        background: #ffffff;
        box-shadow: 0 1px 3px rgba(23, 25, 35, 0.06), 0 4px 12px rgba(23, 25, 35, 0.04), inset 3px 0 0 #ef6351;
        transition: box-shadow 0.2s ease;
    }
}
```

Wait, but there's a concern: adding `background: #ffffff` to `.contact-card` could change appearance if the parent has a gray bg — that's fine, it's the Pinterest look. But is it safe? The instruction says colors may change. Yes.

However, I should be careful with `transform` in transition — transform is not in the allowed list to change, but I'm only adding a transition that references transform. The transition property is allowed to change. But I'm not actually transforming anything. It's fine. Actually to be safe, maybe just transition box-shadow.

Also, "box-shadow (offsets, blur, spread, color — fully redesign with multi-layer effects)" — I'm doing that.

Border-radius is allowed to change — adding is fine.

Now, should I worry that adding `background: #ffffff` with `!important`? The original uses `!important` on padding. I'll keep the `!important` on padding exactly. For new declarations, no need for `!important`.

Also the badge: Bootstrap `.bg-warning` sets `--bs-bg-opacity` and background-color. Adding a `background` shorthand with gradient overrides it. That's a visual change, good. But also Bootstrap badge has `border-radius: 0.375rem` (0.375rem = 6px). My 4px is close to the tight-rhythm variant — good.

Also, should I use `accent-color`? Not relevant.

Let me reconsider whether adding declarations violates "SELECTORS preserved." No, selectors unchanged. Adding declarations to a rule is fine.

But wait — the instruction says "ONLY the rewritten CSS, preserving ALL selectors and layout exactly." Also says "No AI-REWRITTEN comments." I should not add comments.

Also the instruction about "#块2/2" suggests this is block 2 of 2, just this media query. Good.

Let me also think about whether to change the `--space-md` variable? No, it's a spacing variable. Not allowed to change effectively (would affect padding). Keep it.

One more consideration: The instruction says "padding, margin (keep similar values, ±20% maximum)". `var(--space-md)` is unknown, but I'm not changing it. Good.

Now what about the `text-align` rule — I could leave it untouched. Should I add anything? The hero col-lg-7 on mobile is just a centered column. Adding a color or text-shadow to it might be okay, but text-shadow would make text look odd. I'll leave it as-is.

Actually, adding `background` to `.col-lg-7`? No.

But the "target style" says "Each card may have its own accent strip." I applied that to contact cards via inset shadow.

Let me also consider `filter`/`backdrop-filter` — could add `backdrop-filter` to the badge? Not necessary.

Let me refine the shadow palette for Pinterest-like soft shadows:
- Soft: `0 1px 2px rgba(0,0,0,0.05), 0 4px 12px rgba(0,0,0,0.04)`
- Accent strip inset: `inset 0 0 0 1px rgba(0,0,0,0.03), inset 3px 0 0 #e85d4a`

The palette: white cards, light gray bg. Since background is on body elsewhere (probably), I'll set card background to white.

Let me pick a cohesive accent palette:
- Badge: warm amber gradient `#ffd166` to `#f7b267`
- Card accent: coral/red `#ef6351` or `#e85d4a`
- Shadow colors: rgba(30, 34, 45, ...)

Let me also add transition to cards: `transition: box-shadow 0.25s ease-in-out, border-radius 0.25s ease-in-out;` — hmm, border-radius transition is subtle but not needed. Keep box-shadow only.

Actually, for the badge, transition on `box-shadow` and `background` is nice. Let me write:

```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;
        border-radius: 4px;
        background: linear-gradient(135deg, #ffd166 0%, #f4a261 100%);
        box-shadow: 0 2px 8px rgba(222, 142, 74, 0.28), 0 1px 2px rgba(23, 25, 35, 0.06);
        transition: box-shadow 0.25s ease;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        border-radius: 4px;
        background: #ffffff;
        box-shadow: 0 1px 2px rgba(23, 25, 35, 0.05), 0 6px 16px rgba(23, 25, 35, 0.04), inset 0 0 0 1px rgba(23, 25, 35, 0.04), inset 3px 0 0 #ef6351;
        transition: box-shadow 0.25s ease-in-out;
    }
}
```

Wait — `box-shadow: ... inset 0 0 0 1px rgba(...)` creates a border-like ring without layout change. That's a nice "border" that uses box-shadow, so it doesn't touch border-width. Good.

But is `box-shadow` with four layers too much for tight-rhythm? Tight-rhythm says subtle shadows or none. The masonry-flow style wants soft shadows. Combining both: soft but subtle. I'll keep two or three layers.

Let me simplify:

Badge:
```css
box-shadow: 0 2px 6px rgba(233, 154, 84, 0.3);
```

Card:
```css
box-shadow: 0 1px 2px rgba(22, 25, 35, 0.05), 0 8px 20px rgba(22, 25, 35, 0.04), inset 3px 0 0 #ef6351;
```

That's good.

But I need to double check: Is the `transition` on `.contact-card` going to affect anything? It's fine.

Also, the `!important` on padding must remain. Yes.

One concern: `.contact-channels-section article` — article elements might already have a background from elsewhere. Overriding to white is fine — colors may change.

Now, the output format: "ONLY the rewritten CSS ... No markdown fences, no explanations ... First character = first CSS character." So I output just the CSS, starting with `@media`.

Let me also double-check the allowed to change: transition timing, easing, duration — yes. So adding transitions is allowed.

Also border-radius: "border-radius (visual rounding only)" — yes.

Also note "border-color and border-style (NOT border-width)" — I'm not touching border properties at all.

Also "CSS custom properties (--color-*, --shadow-*) values" — I'm not defining custom properties, but using color values directly. Fine.

Now let me also consider whether the badge's `background: linear-gradient(...)` might be too aggressive for conservative mode? Aggressive mode targets masonry-flow, but conservative mode only allows visual changes. Adding a gradient background is a color change — allowed. However, the badge class is `bg-warning` which is Bootstrap. On mobile, the badge will now be a gradient. That's a fresh visual identity. Good.

Actually, should I be more conservative and not override the Bootstrap warning background? The task explicitly asks to refresh visuals with a new palette. The Pinterest-like palette uses white cards and soft shadows. The badge is a warning badge; a warm amber gradient fits.

Alternatively, I could keep the badge as `background-color` from Bootstrap but add a soft shadow and radius. But the instruction says "All color values ... gradient colors and stops in linear/radial/conic-gradient" can change. Adding a gradient is allowed. I'll keep the gradient but make it subtle: `linear-gradient(135deg, #ffd166, #fca652)`.

Let me also think about `text-shadow`? Not needed.

Let me finalize:

```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;
        border-radius: 4px;
        background: linear-gradient(135deg, #ffd166 0%, #f4a261 100%);
        box-shadow: 0 2px 8px rgba(244, 162, 97, 0.3), 0 1px 2px rgba(15, 18, 25, 0.08);
        transition: box-shadow 0.25s ease;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        border-radius: 4px;
        background: #ffffff;
        box-shadow: 0 1px 2px rgba(15, 18, 25, 0.05), 0 6px 16px rgba(15, 18, 25, 0.04), inset 3px 0 0 #ef6351;
        transition: box-shadow 0.25s ease-in-out;
    }
}
```

Hmm, should I keep