/* ============================================================
   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 fresh visual identity. The snippet is:

```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;
    }
}
```

Constraints:
- Keep all selectors exactly
- Can change colors, shadows, radius, transitions, gradients
- Can change custom property values (--space-md)
- Cannot change padding/margin beyond ±20% - but wait, this sets `padding: var(--space-md)`. I can change the value of `--space-md` since it's a CSS custom property that is defined elsewhere. Actually the instruction says "CSS custom properties (--color-*, --shadow-*) values" can change. The `--space-md` is a spacing variable. The layout rules say padding/margin keep similar values ±20%. Changing `--space-md` could affect layout elsewhere. Hmm.

Actually, the file only contains this media query. I'm only rewriting this block. I shouldn't change `--space-md` because that's a spacing variable and the instruction says keep padding/margin similar. But I can add new custom properties? No, adding `--color-*` variables inside this media query would be possible but not needed.

The selectors are:
- `.app-hero-section .row .col-lg-7` - has `text-align: center` (layout, can't change)
- `.app-hero-section .badge.bg-warning` - has `font-size: 0.85rem` (typography, can't change)
- `.contact-channels-section article, .contact-quick-section .contact-card` - has `padding: var(--space-md) !important` (padding, can't change)

So actually there are no visual properties to change in this block. But the task insists I must change something visual. Hmm.

Wait - the file fingerprint is given, and the user says "Previous attempt didn't change enough." So I need to add decorative properties that don't alter layout. I can add things like `border-radius`, `box-shadow`, `background`, `color`, `border-color`, `transition`, etc. But I must be careful not to change layout.

For `.app-hero-section .row .col-lg-7` - this is a column with text-align center. Adding `color` would change text color. Adding `background` could change appearance. But this is a hero section column - adding a background might alter visual identity.

For `.app-hero-section .badge.bg-warning` - badge with warning background. I could add `border-radius`, `box-shadow`, `outline`, `border`, `color`. The `bg-warning` class sets background via Bootstrap. I could override with `background-color`? But `bg-warning` is a Bootstrap utility that sets background-color. Adding `background` would override. But careful - is it a visual identity change? Yes, colors can change.

For `.contact-channels-section article, .contact-quick-section .contact-card` - these are cards. I can add `border-radius`, `box-shadow`, `background-color`, `border`, `transition`.

The instruction says "Refresh this CSS visually. Keep ALL selectors and layout exactly as-is. Only change colors, shadows, radius, transitions, gradients." So I should add / modify these decorative properties within the existing selectors.

Also "CSS custom properties (--color-*, --shadow-*) values" - I could redefine `--space-md` but that's a spacing variable, not color/shadow. I shouldn't.

Let me think about the target style: "masonry-flow" with Pinterest-like white cards, soft shadows on light gray bg, accent strips. Effect variant: "tight-rhythm" - compact, small border-radius (2-6px), subtle shadows.

But this is a media query for mobile (max-width: 575.98px). So mobile styles.

Given the selectors:

1. `.app-hero-section .row .col-lg-7` - hero column. I could add a subtle background tint, border-radius, box-shadow? But it's a column inside a row. Adding box-shadow might look odd but it's a decorative change. However, the instruction for layout says don't change width/height/padding/margin. Adding background/border-radius/box-shadow won't change layout.

Actually, adding a background to a col-lg-7 spans the column width - could look like a card. Since it's a hero section, maybe not ideal. But the user wants a visual identity refresh. Hmm.

Alternatively, I could add `color` to the hero column text. But it inherits.

Let me be safe and add visual enhancements:

For `.app-hero-section .row .col-lg-7`:
- Add a subtle radial gradient background? That could change the look significantly. But it's a hero section - probably has its own background. Adding a background might conflict. Better to add `text-shadow`? Or `color`?

Actually the "masonry-flow" style says white cards on light gray. This is mobile responsive section. Maybe the hero section column can remain simple.

Let me interpret the task more practically. The user wants a rewritten CSS that looks different. Since the original CSS only has layout/typography/padding declarations, I need to inject visual properties into these selectors. This is common in such rewrite tasks - they expect you to add decorative properties, not remove existing ones.

Let me craft:

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

    .app-hero-section .badge.bg-warning {
        font-size: 0.85rem;
        background: linear-gradient(135deg, #f6c453, #f0a830);
        border: 1px solid rgba(240, 168, 48, 0.35);
        border-radius: 3px;
        box-shadow: 0 2px 4px rgba(240, 168, 48, 0.25);
        color: #3d2b00;
        transition: transform 0.2s ease, box-shadow 0.2s ease;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        background: #ffffff;
        border: 1px solid #e8e4df;
        border-radius: 4px;
        box-shadow: 0 1px 3px rgba(45, 42, 38, 0.06);
        transition: box-shadow 0.25s ease, border-color 0.25s ease;
    }
}
```

Wait - the badge `bg-warning` is a Bootstrap utility class. Overriding background with a gradient is fine. But adding `transition: transform` implies transform changes, but there's no hover. Fine.

But caution: `.badge.bg-warning` - Bootstrap badge already has border-radius, padding, font-size. I'm adding more. Fine.

However, the "fresh palette" requirement: I used yellow/amber for warning badge. That's similar to Bootstrap warning. Maybe I should use a different accent. Target palette: Pinterest-like white cards, soft shadows on light gray bg, each card may have its own accent strip.

Maybe for the hero column, add nothing or a subtle bottom accent border? `border-bottom: 2px solid...`? But that could affect layout slightly (adds to height, but border doesn't affect layout if box-sizing border-box... actually Bootstrap uses border-box, so border-bottom wouldn't change layout height). Still, border on a col might look odd.

Let me reconsider: The media query is mobile. The `.col-lg-7` hero column centers text. Adding `color` to text is safe.

Actually, I want to be more aggressive with visual identity. Let me define new color variables at the top of the media query? I can define custom properties inside the media query. Since I'm rewriting the file, I can add a `:root` block? But the instruction says preserve all selectors - I can add new ones? It says "Only change colors, shadows, radius, transitions, gradients." Adding a `:root` block with variables is changing the file structurally but it's still CSS. However, the instruction says "preserving ALL selectors" - it doesn't explicitly forbid adding selectors, but conservative mode implies keep HTML fixed. Adding a `:root` or `*` selector wouldn't break HTML. But to be safe, I'll only modify existing selectors.

Let me think about what changes make the most visual impact:

1. Hero column: add a soft gradient background or a subtle bottom accent. Since it's a column that is text-align center, adding a background might make it look like a highlighted band. Pinterest style - maybe not.

2. Badge: red/pink accent? Pinterest brand color is red (#E60023). Warning badge could be a soft coral/peach. But it's a "warning" badge semantically. Bootstrap's warning is yellow. I can shift to a warm peach/orange gradient.

3. Cards: white background, light border, soft shadow, small radius. Add an accent strip via `border-top`? That could mimic "accent strip". Since original has padding var(--space-md), adding border-top would add to element height unless box-sizing border-box (Bootstrap sets it globally, so yes, border-box applies). So border-top won't change layout size beyond the border being inside. Actually in border-box, border is included in width/height, but height is auto - so adding a 3px top border increases rendered height by 3px, which shifts layout slightly. The constraint says width/height/min/max cannot change - but padding/margin can change ±20%. A 3px border isn't padding/margin... it's a border. Border-width is forbidden to change? "border-color and border-style (NOT border-width)" - so I cannot change border-width. But I can add a border that wasn't there? The original had no border. Adding a border adds border-width. That's technically a border-width change from 0 to something. Hmm. The instruction says "border-color and border-style (NOT border-width)" - so I should not change border widths. But adding a border from none means adding a width. To be safe, I'll avoid adding borders with width. I can use `outline` (outline doesn't affect layout). Outline style/color can change, and outline-width is technically not border-width, but it's similar. Better to avoid.

Actually, adding a border might violate the constraint. I'll use box-shadow to simulate borders - `box-shadow: inset 0 0 0 1px rgba(...)`. Inset box-shadow doesn't affect layout. That's a clever way to add a "border" without changing border-width.

For the accent strip, I can use an inset box-shadow: `inset 0 3px 0 #e60023` - that creates a top accent bar inside the card without layout impact. That fits "Each card may have its own accent strip."

Let me design:

Palette (fresh, not default Bootstrap):
- Background light gray: #f5f3f0 (warm gray)
- Card white: #ffffff
- Accent: #e85d4a (coral-red) or Pinterest red #e60023
- Secondary accent: #2a9d8f (teal)
- Text dark: #2b2b2b
- Badge: soft apricot gradient

Since the media query only targets specific elements, I'll apply:

`.app-hero-section .row .col-lg-7`:
- color: #2b2b2b
- Maybe a subtle text-shadow for depth? On mobile centered hero text.
- Could add a background gradient? Hmm. The hero section likely already has a background. Adding a background to the column could look like a card. Given masonry-flow style is about cards, maybe make the hero column look like a card? But it's a text column, not a card.

I think safer: just color and text-shadow. But the user wants "more distinct". Let me add a gradient background to the hero column. Actually the hero column is `col-lg-7` - it's a column inside a row, might contain text. Adding a background could be risky if it already has a background.

Alternatively, I could add a `::before` accent? No, cannot add pseudo-elements because that changes the selector list? Actually the instruction says preserve pseudo-classes, and element types - but adding a `::before` to a selector that didn't have one is adding a new selector. That's not allowed since it must preserve selectors exactly. So no new pseudo-elements.

Let me keep it to: color, text-shadow for the hero column.

`.app-hero-section .badge.bg-warning`:
- Bootstrap badge. Change background to a fresh coral/peach gradient, box-shadow, border-radius (Bootstrap badge already has 0.375rem radius; I can make it smaller per tight-rhythm variant - 3px). Also add color, font-weight already set by Bootstrap. I can add `transition`.

But wait - `font-size: 0.85rem` is the original declaration. I must keep it. Yes.

`.contact-channels-section article, .contact-quick-section .contact-card`:
- These are cards. Add white background, soft shadow, 4px radius, accent strip via inset shadow, transition.

But original CSS uses `padding: var(--space-md) !important;` - I must keep that exact declaration. Yes.

Let me also consider: `background` on `.contact-card` - if the original card already has a background, overriding with white might be a change but that's the intent.

Also, `box-shadow` multi-layer per instruction: "box-shadow (offsets, blur, spread, color — fully redesign with multi-layer effects)". So use multiple shadows.

Let me write:

```css
@media (max-width: 575.98px) {
    .app-hero-section .row .col-lg-7 {
        text-align: center;
        color: #33271e;
        text-shadow: 0 1px 0 rgba(255, 255, 255, 0.7);
    }

    .app-hero-section .badge.bg-warning {
        font-size: 0.85rem;
        background: linear-gradient(135deg, #ffd166, #f4a259);
        border-radius: 3px;
        box-shadow: 0 2px 4px rgba(244, 162, 89, 0.35), 0 0 0 1px rgba(255, 209, 102, 0.4) inset;
        color: #4a2c0a;
        transition: box-shadow 0.25s ease-in-out, transform 0.25s ease-in-out;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        background: #ffffff;
        border-radius: 4px;
        box-shadow: 0 1px 2px rgba(51, 39, 30, 0.04), 0 4px 12px rgba(51, 39, 30, 0.06), inset 0 3px 0 #e76f51;
        transition: box-shadow 0.3s cubic-bezier(0.25, 0.46, 0.45, 0.94), transform 0.3s cubic-bezier(0.25, 0.46, 0.45, 0.94);
    }
}
```

Hmm, but `transition: transform` on cards - if there's no hover, it does nothing. But adding transition is allowed. However, if there's a hover elsewhere that uses transform, this transition would apply. Fine.

Wait - the `inset 0 3px 0 #e76f51` creates a 3px coral strip at the top inside the card. That's the "accent strip". Nice.

But careful: The cards might have overflow hidden? If not, the inset shadow will be clipped at the card's border radius - it's fine.

Should I add `border: 1px solid #e8e4df`? Border-width change concern. Use inset shadow ring instead: `inset 0 0 0 1px rgba(51, 39, 30, 0.06)`. That adds a subtle outline without layout impact. Good.

Let me reconsider the hero column. Adding `color` is safe. But is `text-shadow` a big change? It's a decorative change. Maybe also add a subtle background gradient? I'm hesitant. Actually the target style says "soft shadows on light gray bg" for the overall page. Adding a `background` to the hero column could conflict with the hero section's existing design. But this is a responsive override; maybe the hero section has a dark background, and white text? In that case, setting `color: #33271e` would be wrong. Hmm.

The original CSS doesn't set a color for the hero column, meaning it inherits. Changing it to a dark color might be wrong if the hero has a dark background. This is risky. But the task demands visual changes. Let me think...

The `.badge.bg-warning` suggests Bootstrap. The hero section likely has a light background? Hard to know. Actually, the `bg-warning` badge is a warning badge, often placed in hero sections. On mobile the text is centered.

Risk assessment: If I set `color` to a dark value and the hero has a dark background, the text becomes invisible. That would be a bad rewrite. But conservative mode says only change visual properties - and colors are allowed. The user asked for a fresh palette. I'll assume the hero section is light.

Alternatively, for the hero column I could add just a subtle gradient text? No.

Let me use a custom property for the accent? Not needed.

Actually - I could add a `background` to the hero column. In Pinterest