/* ============================================================
   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 from a file called `assets/css/saishi.css`, specifically "块2/2" (block 2/2). The target style is "horizontal-strips" with "sharp-edges" variant.

Let me look at 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 inside a media query. The rules are:
1. `.app-hero-section .row .col-lg-7` - text-align: center (typography, can't change)
2. `.app-hero-section .badge.bg-warning` - font-size: 0.85rem (typography, can't change)
3. `.contact-channels-section article` and `.contact-quick-section .contact-card` - padding: var(--space-md) !important (padding, can change ±20%)

The instructions say:
- I can change colors, shadows, border-radius, transitions, gradients, opacity, outline, caret-color, accent-color, CSS custom properties
- I cannot change layout, typography, etc.

But wait — this CSS block is very minimal. It only has text-align, font-size, and padding. None of these are in the "allowed to change" list:
- text-align is under typography/vertical-align → can't change
- font-size is under typography → can't change
- padding is under layout → can change but "keep similar values, ±20% maximum"

So there's very little I can actually change here. The instructions say I must change visual identity only. Let me think about how to handle this.

The padding rule: `padding: var(--space-md) !important;` — I could adjust this within ±20%. But `var(--space-md)` is a CSS custom property reference. I don't know its value. I shouldn't change the value since it would break the layout potentially. Actually, I could keep it but maybe modify it slightly.

Wait, the instruction says "CSS custom properties (--color-*, --shadow-*) values" can change. But `--space-md` is a spacing variable, not a color or shadow. So I should leave it.

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

There are no colors, shadows, radii, transitions, or gradients in this snippet. So essentially, there's nothing to change without violating constraints.

However, I need to produce output. In conservative mode, if there's nothing to change, I should output the CSS as-is (preserving everything). But the instructions also mention "All color values" must change. There are no color values.

Let me think about what I can do:
1. The media query stays.
2. The selectors stay.
3. The property names: text-align, font-size, padding — these are layout/typography, not visual.
4. I could add new visual properties? The instructions say to change visual identity. But adding properties like `color` or `background` might be considered acceptable since they don't break layout. However, adding properties not in the original could be risky — the instructions say "Only colors, shadows, and decorative properties may change." Adding decorative properties could be allowed.

But adding visual properties to elements inside a media query for mobile could change the look significantly. For example, adding `background-color` to `.app-hero-section .row .col-lg-7` would break the horizontal-strips pattern perhaps.

Actually, the target style is "horizontal-strips" with alternating backgrounds. But this is a media query for small screens. The safest approach in conservative mode with almost nothing to change is to keep it essentially the same.

However, the instructions repeatedly say I MUST change visual identity. Let me re-read:

"✅ YOU MUST CHANGE (visual identity only): All color values, box-shadow, text-shadow, border-radius, gradient colors, transition timing, border-color, outline, caret-color, accent-color, CSS custom properties"

But there are none in the original. So no changes needed.

"🔒 NEVER CHANGE: selectors, layout, typography"

So I should keep everything.

The output instruction: "ONLY the rewritten CSS, preserving ALL selectors and layout exactly."

Given the constraints, the only permissible change might be to slightly adjust padding within ±20%. But padding is `var(--space-md)`. I can't compute 20% of a variable. I could change it to `calc(var(--space-md) * 0.95)` or something, but that seems pointless and risky.

Wait — maybe I can add new visual properties that don't break layout. For instance:
- `border-radius: 0;` (sharp edges) on cards
- `box-shadow: 4px 4px 0px #000;` on cards
- `transition: all 0.15s;`

But adding box-shadow and border-radius to these elements could change the visual identity and align with "sharp-edges". But is it allowed? The instruction says "Only colors, shadows, and decorative properties may change." That implies these properties may CHANGE (i.e., be modified if present). Adding them might be a stretch, but the task says "Refresh this CSS visually."

Actually, the spirit of the exercise: the file is "块2/2" meaning block 2 of 2 — there's likely a block 1 with the main CSS. This block 2 is a media query for mobile. The original only has typography/padding adjustments. In conservative mode, I really shouldn't change anything meaningful.

The safest and most correct conservative behavior: output the CSS exactly as-is, because changing text-align, font-size, or padding would violate the constraints, and there are no colors/shadows/radii to change.

But the task says "No AI-REWRITTEN comments" and "Rewrite the CSS now". Hmm.

Let me consider: Could I add a `transition` property? Transitions are in the changeable list. Adding `transition: all 0.15s;` to elements would be a decorative change. But adding it to `.badge.bg-warning` might be fine.

Could I add `caret-color`? Not relevant.

The instructions also say "CSS custom properties (--color-*, --shadow-*) values" can change. There's `var(--space-md)` — that's a spacing variable, not color/shadow. So no.

I think the right approach in conservative mode is: if the original has no visual properties to change, keep the original as-is. But to satisfy "refresh," I can add subtle visual properties that don't affect layout:

For `.contact-channels-section article` and `.contact-quick-section .contact-card`, the target is sharp edges and hard shadows. I could add:
- `border-radius: 2px;`
- `box-shadow: 4px 4px 0px rgba(0,0,0,0.15);`
- `transition: box-shadow 0.15s ease, transform 0.15s ease;`

But wait — adding `transition` doesn't break layout. Adding `box-shadow` doesn't break layout. Adding `border-radius` doesn't break layout. These are decorative. However, adding them may be unwelcome because the HTML might not have backgrounds on these elements, so shadows might look odd.

Actually, the "sharp-edges" variant explicitly wants: "Hard offset shadows: 4px 4px 0px solid color", "Small or zero border-radius (0-4px)", "Strong borders (2-3px solid)", "Snappy transitions (0.15s)."

So maybe I should add these to the key elements.

But the elements here:
1. `.app-hero-section .row .col-lg-7` — a column, text-align center. Adding background/box-shadow to a column would be weird.
2. `.app-hero-section .badge.bg-warning` — a badge. Could add border-radius.
3. `.contact-channels-section article` — an article card. Could add box-shadow, border-radius, transition.
4. `.contact-quick-section .contact-card` — a contact card. Could add box-shadow, border-radius, transition.

Given the layout is fixed, adding `border-radius: 0` to the badge (which likely has rounded pill shape by default via Bootstrap `.badge` with `border-radius`) — but in responsive, Bootstrap badge has `border-radius: 0.375rem`. Setting it to 0 for sharp edges is okay.

But careful: `.badge.bg-warning` — the background color is `bg-warning` (Bootstrap utility). In the media query, only font-size is changed. Should I add border-radius? That doesn't affect layout (well, border-radius doesn't affect layout). But it changes the visual appearance.

Hmm, but the instruction says "Keep ALL selectors and layout exactly as-is." Adding properties to existing selectors keeps selectors as-is. It doesn't violate selector preservation.

Adding properties could potentially affect layout? `box-shadow` doesn't affect layout. `border-radius` doesn't. `transition` doesn't. `border` would affect layout (border-width adds to box size, but box-shadow doesn't). So adding `border` with width 0? No. The sharp-edges variant says "Strong borders (2-3px solid)" — but adding a border would change layout (border-box vs content-box). Since `box-sizing` is unknown, adding a 2px border would shift layout. That's risky. I could use `box-shadow: 0 0 0 2px color` (a border-like shadow) which doesn't affect layout.

However, I'm overthinking. The most conservative safe output is to reproduce the original CSS exactly. The prompt strongly emphasizes preserving layout and typography; since this snippet contains only layout/typography-related declarations, any change risks violating the rules.

But the prompt also says "Refresh this CSS visually" — maybe they expect me to add decorative properties where possible. The target style "horizontal-strips" and "sharp-edges" might apply more to block 1. Block 2 is just a responsive override. So perhaps for block 2, the refresh is minimal.

Let me re-read: "🎨 TARGET STYLE: horizontal-strips" — this is the overall target for the file. "✨ EFFECT VARIANT: sharp-edges" — overall effect. The task says "Refresh this CSS visually" for this block.

Given the constraints, I'll make minimal safe additions that align with sharp edges without altering layout:

1. For `.app-hero-section .badge.bg-warning`: add `border-radius: 0;` (sharp edge badge) — this changes the pill to sharp, matching sharp-edges. Also could add `box-shadow: 3px 3px 0px #d97706;` (warning color dark). But `bg-warning` is a Bootstrap class; adding box-shadow could look nice. However, box-shadow could be clipped by overflow hidden on parent — but that's not layout. I'll keep it subtle.

2. For `.contact-channels-section article, .contact-quick-section .contact-card`: add `border-radius: 2px; box-shadow: 4px 4px 0px rgba(0,0,0,0.1); transition: box-shadow 0.15s ease;` — these are decorative, safe.

But wait — `padding: var(--space-md) !important;` — the `!important` is there. If I add more properties, I need to be careful not to override existing important declarations. Adding new properties is fine.

Actually, let me reconsider whether adding properties is within scope. The prompt says:

"🎯 YOUR MISSION: Refresh the visual identity WITHOUT changing layout structure or class names. The HTML is FIXED — only colors, shadows, and decorative properties may change."

This clearly permits changing/adding decorative properties. So adding box-shadow, border-radius, transition is within scope.

But the "NEVER CHANGE" list includes:
- padding, margin (keep similar values, ±20% maximum)

So I must keep `padding: var(--space-md) !important;` or adjust within 20%. Adjusting a CSS var by 20% is meaningless without knowing the value. Keep as-is.

- text-align → must keep.
- font-size → must keep.

So my output will keep those three declarations and add decorative ones.

Let me decide on the additions:

For `.app-hero-section .row .col-lg-7`:
- It's a text-align: center override. Could add `color:` but that would change text color — allowed since colors must change. But there's no original color. Adding a color might be okay. The horizontal-strips target: alternating white/cream/dark. For hero section, maybe a specific color. But adding color without context is risky. I'll avoid.

Actually, let me think about what makes sense. The sharp-edges variant: strong borders, hard shadows, snappy transitions. The most fitting additions are to the card-like elements (article, contact-card) and maybe the badge.

For the badge:
```css
.app-hero-section .badge.bg-warning {
    font-size: 0.85rem;
    border-radius: 2px;
    box-shadow: 3px 3px 0px #0f172a;
    transition: box-shadow 0.15s ease;
}
```
Wait, `bg-warning` in Bootstrap is `#ffc107` (yellow). A hard shadow in dark navy `#0f172a` would look sharp. But if the badge is inline, box-shadow might look odd. Hmm.

Actually, in Bootstrap `.badge` has `border-radius: 0.375rem;`. Setting `border-radius: 2px;` aligns with sharp edges. Adding a hard offset shadow to a badge is a bold look, but that's the target style. Let's do it.

For the contact article/card:
```css
.contact-channels-section article,
.contact-quick-section .contact-card {
    padding: var(--space-md) !important;
    border-radius: 2px;
    box-shadow: 4px 4px 0px rgba(15, 23, 42, 0.15);
    transition: box-shadow 0.15s ease, transform 0.15s ease;
}
```

But adding `transform` transition without any transform on hover is fine. Adding `transition` property doesn't affect layout. But should I add `:hover`? No — selectors must be preserved exactly; I can't add new selectors.

Hmm, but the instruction says "Pseudo-classes (:hover, :focus, ::before, ::after)" are in the NEVER CHANGE list — meaning I can't change selector lists with pseudo-classes. Adding a new `:hover` rule would be adding a selector, which is not allowed. So no hover rules.

Now, about the horizontal-strips target: full-width sections with alternating backgrounds. This media query block is for mobile. The main block (block 1) probably has the horizontal strips. For block 2, I just need to preserve responsive behavior.

Let me also consider: should I change any existing values? The only existing property values are:
- `text-align: center;` → must keep (text-align is in the never-change list)
- `font-size: 0.85rem;` → must keep (font-size)
- `padding: var(--space-md) !important;` → must keep or within ±20%. Keep.

So the safest is to keep the original declarations and add decorative ones. But the prompt says "All color values" must change — there are none. And "box-shadow" must be redesigned — there are none. So adding them is the refresh.

However, there's the risk that adding `box-shadow` to a Bootstrap `.badge` might conflict with `bg-warning`... no, it's fine.

But there's another concern: The `.contact-channels-section article` might already have a box-shadow or border-radius from the base CSS (block 1). This media query would override them on mobile if I add them here. That's allowed in terms of visual changes, but it might conflict with the base design. In a real refactor, I'd coordinate. But since I only see block 2, I'll make reasonable choices.

Let me think about the "horizontal-strips" pattern: alternating white/cream/dark. For the mobile media query, maybe the contact cards should have a sharp shadow with dark color to pop on cream background. And the badge could have a hard shadow.

I'll go with a cohesive palette:
- Use a dark color for shadows: `#1e293b` (slate-800) or `#0f172a` (slate-900).
- Use a warm accent for the warning badge: `#d97706` (amber-600) as shadow? Actually, a dark shadow on a yellow badge looks sharp.
- Border-radius: `2px` or `0`.

Let me draft:

```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: 2px;
        box-shadow: 3px 3px 0px var(--saishi-strip-dark);
        transition: box-shadow 0.15s ease;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        border-radius: 2px;
        box-shadow: 4px 4px 0px var(--saishi-shadow-color);
        transition: box-shadow 0.15s ease, opacity 0.15s ease;
    }
}
```

But using `var(--saishi-strip-dark)` introduces new custom properties not defined in this block. That's okay if block 1 defines them, but risky. Better to use literal color values.

Also, the "sharp-edges" variant says "Hard offset shadows: 4px 4px 0px solid color". It says "solid color" — meaning no blur, like `4px 4px 0px #000`. That's a classic hard shadow.

"