We need answer only rewritten CSS. Need preserve selectors/layout. Change colors/shadows/radius/transitions/gradients etc. Need fresh palette: centered-stage dark stage #0f0f1a, premium gold or deep purple accent. Airy rhythm large radius 16-28px, pillowy shadows, generous spacing but conservative can't change padding/margins beyond ±20%. Original uses CSS vars with no definitions in this file? We only rewrite this file. We can change color values where literal. We can change var usage? Custom properties values only if defined; none here except usage. We can alter literal colors. Need more distinct. Palette maybe "midnight aubergine + champagne gold". Accent gold #f5c044, primary maybe deep purple #7c3aed? But target centered-stage dark stage #0f0f1a and gold/deep purple accent. Since variables not defined, we can't change --color-primary etc. But can replace with literals? The rules say color values can change, CSS custom properties values. But if we replace var(--color-primary) with literal, does that change layout? No. But maybe should preserve variables? The request says all color values: change. Since variables are used, if variables defined elsewhere maybe changing usages to literals would be visual change. But "preserving selectors and layout exactly". Could replace var(--color-primary) with literal color? That removes custom prop use but selectors same. Is that allowed? It says change CSS custom properties values. If not defined here, could either keep vars or substitute. To make more distinct, we can substitute many color vars with new literal colors. But must be careful not to change layout.

We need output only CSS. Need keep all selectors. Can change border-radius values, shadows, transition timings, filters, opacity.

Let's craft.

Original variables used many. If we substitute all var() color usages with new palette literals, that's significant. But also shadow var(--shadow-sm), --shadow-lg, etc. We can replace with literal shadows. That's allowed. But need preserve fallback? No.

Let's choose palette:
--stage: #0f0f1a (dark)
primary: deep purple #8b5cf6 or #7c3aed
primary-dark: #6d28d9
primary-darker: #3b0764 or #2e1065
accent: gold #f5c044
accent-dark: #d99e1b
danger: #fb7185 (rose)
text: #2d2a3e / #1f1b2e
text-muted: #6b7280 or #7b7691
bg: #fbf9ff (bright)
bg-soft: #f5f1ff or #f6f3fb
bg-muted: #ede8f6
border: #ded7f0
border-soft: #e9e3f7

Need update literal colors:
- .single-post .post-meta i color var primary -> #7c3aed
- post-content color var text -> #2d2a3e
- headings color primary-darker -> #2e1065
- h2 border-bottom 2px solid var border -> #ded7f0
- blockquote border-left 4px solid primary -> #7c3aed; background bg-soft -> #f6f3fb; color text-muted -> #6b7280; border-radius 0 var(--radius-md) ... we can change to 0 20px 20px 0 maybe large radius.
- img border-radius var radius-md -> 18px; shadow var shadow-sm -> 0 8px 24px rgba(80, 63, 150, 0.12), 0 2px 6px rgba(80,63,150,0.08)
- a color primary -> #7c3aed; hover primary-dark -> #6d28d9
- code background bg-muted -> #ede8f6; radius 4px -> 8px; color danger -> #e11d48 or #fb7185
- pre background primary-darker -> #2e1065; color #fff -> #fdfbff; radius radius-md -> 18px
- table borders var border -> #ded7f0
- table th background bg-muted -> #ede8f6
- toc border-left 3px solid primary -> #7c3aed
- toc a hover primary-dark -> #6d28d9
- tags badge bg bg-muted -> #ede8f6; color #475569 -> #5b5470; hover bg primary -> #7c3aed; color #fff -> #fff
- app-hero background var gradient-hero -> maybe linear-gradient(135deg, #1b1233 0%, #3b0764 50%, #7c3aed 100%). color #fff.
- ::before background rgba(0,0,0,0.2) -> rgba(15,15,26,0.45)
- img filter drop-shadow(0 20px 40px rgba(0,0,0,0.3)) -> drop-shadow(0 24px 48px rgba(15,15,26,0.45)) drop-shadow(0 8px 16px rgba(124,58,237,0.25))
- .text-white-50 color rgba(255,255,255,0.65) -> rgba(255,255,255,0.72)
- app-qr-section background bg-soft -> #f6f3fb
- qr-card border 2px solid transparent; hover border-color accent -> #f5c044; box-shadow 0 15px 40px rgba(0,0,0,0.15) -> 0 22px 48px rgba(91, 33, 182, 0.22), 0 6px 16px rgba(245,192,68,0.24)
- app-install-section background bg-soft -> #f6f3fb
- .bg-white transition etc. no color? .bg-white is class but we don't change bg? It's a class name, not selector? Rule .app-install-section .bg-white { transition...}. We could add background-color? That would be changing visual identity maybe okay? But HTML class bg-white likely has background white from bootstrap. We can add background-color: #ffffff? But not necessary. Could add box-shadow? Careful: adding properties allowed? Visual only. We can change box-shadow, radius. But adding background might conflict. We can add border-radius: 24px; box-shadow soft? But original didn't have box-shadow. Adding new property is visual identity, probably okay. But conservative? It says only colors, shadows, decorative properties may change. border-radius allowed. So adding border-radius okay. I'll add border-radius: 24px; box-shadow: 0 10px 30px rgba(80,63,150,0.08); background: #fff maybe.
- app-install-section .bg-white:hover box-shadow var shadow-lg -> 0 28px 60px rgba(80,63,150,0.18), 0 8px 18px rgba(245,192,68,0.15)
- ::before background var gradient-icon -> linear-gradient(180deg, #f5c044, #7c3aed)
- app-showcase-section background bg -> #fbf9ff
- app-showcase img filter drop-shadow(0 15px 30px rgba(0,0,0,0.15)) -> drop-shadow(0 18px 36px rgba(15,15,26,0.18)) drop-shadow(0 6px 12px rgba(124,58,237,0.18))
- .bg-white border-inline-start 3px solid transparent; hover border-inline-start-color primary -> #7c3aed; box-shadow var shadow-md -> 0 16px 40px rgba(80,63,150,0.16), 0 4px 12px rgba(124,58,237,0.12)
- contact-channels bg -> #fbf9ff; article border 1px solid border-soft -> #e9e3f7; hover box-shadow var shadow-lg -> 0 26px 55px rgba(80,63,150,0.16), 0 8px 18px rgba(124,58,237,0.12); border-color primary -> #7c3aed
- contact-quick bg-soft -> #f6f3fb; hover shadow-lg -> similar
- contact-form bg-soft -> #f6f3fb; form-control border 2px solid border -> #ded7f0; focus border primary -> #7c3aed; box-shadow 0 0 0 0.2rem rgba(59,130,246,0.1) -> 0 0 0 0.25rem rgba(124,58,237,0.18), 0 4px 12px rgba(124,58,237,0.12)
- button hover box-shadow var shadow-primary -> 0 14px 28px rgba(124,58,237,0.35), 0 4px 10px rgba(245,192,68,0.25)
- contact-commitments bg-soft -> #f6f3fb; hover shadow-lg -> soft.
- login/signup main:has... input-group-text bg bg-muted -> #ede8f6; border-color border -> #ded7f0; focus border primary -> #7c3aed; background-color #eff6ff -> #f3e8ff or #f5f1ff. form-check-input checked bg/border primary -> #7c3aed.
- button submit hover shadow-primary -> same.
- hero-buttons .btn-warning background accent -> #f5c044; border-color accent -> #f5c044; color primary-darker -> #2e1065; hover accent-dark -> #d99e1b. btn-outline-light hover background rgba(255,255,255,0.15) -> rgba(245,192,68,0.2), color #fff -> #fff.
- scrollbar track bg-muted -> #ede8f6; thumb #94a3b8 -> #a78bfa or #b8a8e8; hover color text-muted -> #6b7280? maybe #7c3aed.
- Firefox scrollbar-color #94a3b8 var(bg-muted) -> #a78bfa #ede8f6
- Print styles: mostly colors, maybe keep black/white? Target dark stage? Print should remain white/black. But we can change print a color to #000 etc. No need. But rule says all color values changed? Print colors can remain black/white. Could change a[href^="http"]::after color #555 -> #444. Not important.
- animations: fadeInUp same, pulse same but can change values? Keep.
- Responsive: no colors except none.

Also border-radius changes: Many places we can add radius to cards? Original does not have radius in many. We can add border-radius to sections? E.g., .qr-card? Original no radius. We can add border-radius: 24px to .qr-card. .app-install-section .bg-white add radius 24. .contact-channels-section article add radius 22. .contact-quick-section .contact-card add radius 22. .contact-commitments-section .bg-white add radius 22. .app-showcase-section .bg-white add radius 22. Forms bg-white? Can't target .bg-white globally? We can only target as original selectors. Adding radius to .bg-white within sections is okay.

Need preserve exact selectors. If we add properties to existing selector blocks, okay. We cannot change selector lists.

We should keep all original declarations, modify values. Need be careful with variable names in output? We can replace var(--color-primary) etc. But if we replace all vars, file no longer references theme variables. That's okay? It might be considered changing CSS custom properties values? Not exactly, but allowed to change color values. However, if some variables control layout? No, only colors/shadows. But if we replace var(--radius-md) with 18px, that's radius. Good. For var(--transition-base) we can replace with cubic-bezier? Transition timing allowed. We can set e.g., 0.35s cubic-bezier(0.22, 1, 0.36, 1). For var(--transition-fast) -> 0.2s ease. var(--transition-slow) -> 0.6s cubic-bezier(0.22,1,0.36,1). But if we replace var(--transition-base), no issue.

For spacing vars like var(--space-sm) etc. We must not change layout beyond ±20%. Could keep as is. But request says only visual. We can keep var(--space-*) untouched. If we replace, risk. So keep spacing vars.

For --radius-md in border-radius, we can replace with 20px. For --radius-sm? none. Could keep var(--radius-md)? But to make distinct, replace with new values. It's allowed.

For --shadow-sm etc., replace with literal shadows.

For --gradient-hero and --gradient-icon, replace with literal gradients.

For --color-* replace with literals.

Need ensure no AI comments. Do not include markdown.

Potential issue: if we replace vars with literals, some selectors may have no var. Fine.

Let's write full CSS.

Need decide transition values. Use a smooth expo-like easing. For all "transition: all var(--transition-base)" -> transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); For fast -> 0.25s ease; slow -> 0.7s cubic-bezier(0.16,1,0.3,1).

Border-radius: For post-content img 18px? Airy rhythm large 16-28. Use 24px for cards, 18px for images, 12px for code, 20px for pre, 22px for qr-card. But blockquote border-radius 0 20px 20px 0. toc? maybe add radius? Original .toc-box only border-left. We can add border-radius: 20px; but that might round left border? Border-inline-start with radius looks weird but okay. Better add border-radius: 0 20px 20px 0? But if it has background? Not sure. We can add border-radius: 20px; But border-inline-start will follow radius? It's okay. Conservative? Visual only.

Maybe add background to toc-box? Not necessary.

Let's produce.

Full CSS:

.single-post { overflow: hidden; }
.single-post .post-meta { font-size: 0.9rem; }
.single-post .post-meta i { color: #7c3aed; }
.post-content { line-height: 1.8; font-size: 1.05rem; color: #2d2a3e; }
.post-content :is(h2, h3, h4) { margin-block: 2rem 1rem; font-weight: 700; color: #2e1065; line-height: 1.4; }
.post-content h2 { font-size: 1.75rem; padding-bottom: var(--space-xs); border-bottom: 2px solid #ded7f0; }
.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 #7c3aed; padding: var(--space-sm) var(--space-md); background: #f6f3fb; border-radius: 0 20px 20px 0; margin-block: var(--space-md); color: #6b7280; font-style: italic; }
.post-content img { max-width: 100%; height: auto; border-radius: 18px; margin-block: var(--space-sm); box-shadow: 0 12px 28px rgba(80, 63, 150, 0.14), 0 4px 10px rgba(80, 63, 150, 0.08); }
.post-content a { color: #7c3aed; text-decoration: underline; transition: color 0.25s ease; }
.post-content a:hover { color: #6d28d9; }
.post-content ul, .post-content ol { padding-inline-start: 1.5rem; }
.post-content code { background: #ede8f6; padding: 2px 6px; border-radius: 8px; font-size: 0.9em; color: #e11d48; }
.post-content pre { background: #2e1065; color: #fdfbff; padding: var(--space-md); border-radius: 20px; overflow-x: auto; margin-block: var(--space-md); box-shadow: 0 16px 32px rgba(46, 16, 101, 0.22); }
.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 #ded7f0; text-align: start; }
.post-content table th { background: #ede8f6; font-weight: 600; }
.toc-box { border-inline-start: 3px solid #7c3aed; border-radius: 0 20px 20px 0; padding: var(--space-sm) var(--space-md); background: #faf8ff; }
Wait original .toc-box had only border-inline-start: 3px solid var(--color-primary); no padding/background. Adding padding changes layout? This is risky because padding affects layout. The rule says padding can change ±20%. Original .toc-box no padding specified here, but may have base padding from elsewhere. Adding padding could increase. Better not add padding. Add border-radius maybe okay. Adding background color is visual. Can add background: #faf8ff; but if no padding, text touches background edges. Could be okay but might look bad. Maybe skip background. Add border-radius: 0 18px 18px 0; Is adding border-radius without padding okay. Fine.

.toc-box ol { padding-inline-start: 1.2rem; }
.toc-box ol li { margin: 0.4rem 0; }
.toc-box ol li a { transition: all 0.25s ease; }
.toc-box ol li a:hover { color: #6d28d9; text-decoration: underline !important; padding-inline-start: 4px; }
.post-tags .badge { background: #ede8f6 !important; color: #5b5470 !important; padding: 6px 12px; font-weight: 500; transition: all 0.25s ease; border-radius: 999px; }
Original no border-radius on badge? Adding radius okay. Use 999px pill.
.post-tags .badge:hover { background: #7c3aed !important; color: #fff !important; transform: translateY(-1px); box-shadow: 0 6px 16px rgba(124, 58, 237, 0.28); }
.post-nav { flex-wrap: wrap; gap: var(--space-sm); }
.post-nav .btn { max-width: 100%; overflow: hidden; text-overflow: ellipsis; }
.app-hero-section { background: linear-gradient(135deg, #0f0f1a 0%, #2e1065 45%, #7c3aed 100%); color: #fff; position: relative; overflow: hidden; }
.app-hero-section::before { content: ''; position: absolute; inset: 0; background: rgba(15, 15, 26, 0.45); 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; text-shadow: 0 4px 24px rgba(245, 192, 68, 0.28), 0 1px 2px rgba(15, 15, 26, 0.5); }
Adding text-shadow allowed.
.app-hero-section img { transition: transform 0.7s cubic-bezier(0.16, 1, 0.3, 1); filter: drop-shadow(0 24px 48px rgba(15, 15, 26, 0.5)) drop-shadow(0 8px 18px rgba(124, 58, 237, 0.35)); }
.app-hero-section img:hover { transform: translateY(-10px); }
.text-white-50 { color: rgba(255, 255, 255, 0.72) !important; }
.app-qr-section { background: #f6f3fb; }
.qr-card { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); border: 2px solid transparent; border-radius: 24px; }
.qr-card:hover { transform: scale(1.03); border-color: #f5c044; box-shadow: 0 24px 50px rgba(91, 33, 182, 0.22), 0 8px 20px rgba(245, 192, 68, 0.28); }
.qr-card img { image-rendering: pixelated; image-rendering: -moz-crisp-edges; image-rendering: crisp-edges; }
.app-install-section { background: #f6f3fb; }
.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 0.4s cubic-bezier(0.16, 1, 0.3, 1); position: relative; overflow: hidden; border-radius: 24px; box-shadow: 0 10px 30px rgba(80, 63, 150, 0.08); background: #ffffff; }
.app-install-section .bg-white:hover { transform: translateY(-5px); box-shadow: 0 30px 60px rgba(80, 63, 150, 0.18), 0 10px 22px rgba(245, 192, 68, 0.16); }
.app-install-section .bg-white::before { content: ''; position: absolute; top: 0; left: 0; width: 4px; height: 100%; background: linear-gradient(180deg, #f5c044 0%, #7c3aed 100%); transform: scaleY(0); transform-origin: top; transition: transform 0.4s cubic-bezier(0.16, 1, 0.3, 1); }
.app-install-section .bg-white:hover::before { transform: scaleY(1); }
.app-showcase-section { background: #fbf9ff; }
.app-showcase-section img { transition: transform 0.7s cubic-bezier(0.16, 1, 0.3, 1); filter: drop-shadow(0 18px 36px rgba(15, 15, 26, 0.2)) drop-shadow(0 6px 14px rgba(124, 58, 237, 0.2)); }
.app-showcase-section img:hover { transform: translateY(-5px) rotate(-1deg); }
.app-showcase-section .bg-white { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); border-inline-start: 3px solid transparent; border-radius: 24px; background: #ffffff; box-shadow: 0 10px 30px rgba(80, 63, 150, 0.08); }
.app-showcase-section .bg-white:hover { border-inline-start-color: #7c3aed; transform: translateX(5px); box-shadow: 0 18px 42px rgba(80, 63, 150, 0.18), 0 6px 16px rgba(124, 58, 237, 0.14); }
.contact-channels-section { background: #fbf9ff; }
.contact-channels-section article { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); border: 1px solid #e9e3f7; border-radius: 24px; background: #ffffff; box-shadow: 0 10px 30px rgba(80, 63, 150, 0.06); }
.contact-channels-section article:hover { transform: translateY(-5px); box-shadow: 0 28px 56px rgba(80, 63, 150, 0.16), 0 8px 20px rgba(124, 58, 237, 0.12); border-color: #7c3aed; }
.contact-channels-section article ul li { transition: padding 0.25s ease; }
.contact-channels-section article ul li:hover { padding-inline-start: 4px; }
.contact-quick-section { background: #f6f3fb; }
.contact-quick-section .contact-card { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); border-radius: 24px; background: #ffffff; box-shadow: 0 10px 30px rgba(80, 63, 150, 0.06); }
.contact-quick-section .contact-card:hover { transform: translateY(-5px); box-shadow: 0 28px 56px rgba(80, 63, 150, 0.16), 0 8px 20px rgba(245, 192, 68, 0.12); }
.contact-quick-section .contact-card i { transition: transform 0.4s cubic-bezier(0.16, 1, 0.3, 1); }
.contact-quick-section .contact-card:hover i { transform: scale(1.1) rotate(-5deg); }
.contact-form-section { background: #f6f3fb; }
.contact-form-section .form-control, .contact-form-section .form-select { border: 2px solid #ded7f0; transition: all 0.25s ease; border-radius: 16px; background: #ffffff; }
.contact-form-section .form-control:focus, .contact-form-section .form-select:focus { border-color: #7c3aed; box-shadow: 0 0 0 0.25rem rgba(124, 58, 237, 0.16), 0 8px 20px rgba(124, 58, 237, 0.12); }
.contact-form-section button[type="submit"] { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); border-radius: 16px; }
.contact-form-section button[type="submit"]:hover { transform: translateY(-2px); box-shadow: 0 16px 32px rgba(124, 58, 237, 0.32), 0 6px 14px rgba(245, 192, 68, 0.24); }
.contact-commitments-section { background: #f6f3fb; }
.contact-commitments-section .bg-white { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); text-align: center; border-radius: 24px; background: #ffffff; box-shadow: 0 10px 30px rgba(80, 63, 150, 0.06); }
.contact-commitments-section .bg-white:hover { transform: translateY(-5px); box-shadow: 0 28px 56px rgba(80, 63, 150, 0.16), 0 8px 20px rgba(245, 192, 68, 0.12); }
.contact-commitments-section .bg-white i { transition: transform 0.4s cubic-bezier(0.16, 1, 0.3, 1); }
.contact-commitments-section .bg-white:hover i { transform: scale(1.15); }
main:has(> .container > .bg-white > form) .input-group-text { background-color: #ede8f6; border-color: #ded7f0; border-inline-end: none; border-radius: 16px 0 0 16px; }
Original had no border-radius. Adding might affect layout? border-radius visual. But if input group has connected inputs, radius on inner might create gaps? Visual only. Could skip radius to avoid weird. But airy rhythm large radius. I'll add border-radius: 16px 0 0 16px; and for form-control border-inline-start: none, maybe border-radius: 0 16px 16px 0; But original rule is main:has(...) .input-group .form-control { border-inline-start: none; } We can add border-radius: 0 16px 16px 0; That's visual. However, input group may have other elements. Better keep simple: add border-radius: 16px; to input-group-text? Actually if only two elements, left and right. Add to both.

main:has(> .container > .bg-white > form) .input-group .form-control { border-inline-start: none; border-radius: 0 16px 16px 0; }
main:has(> .container > .bg-white > form) .input-group:focus-within .input-group-text { border-color: #7c3aed; background-color: #f3e8ff; }
main:has(> .container > .bg-white > form) .input-group:focus-within .form-control { border-color: #7c3aed; }
main:has(> .container > .bg-white > form) .form-check-input:checked { background-color: #7c3aed; border-color: #7c3aed; }
main:has(> .container > .bg-white > form) button[type="submit"] { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); font-weight: 600; border-radius: 16px; }
main:has(> .container > .bg-white > form) button[type="submit"]:hover { transform: translateY(-2px); box-shadow: 0 16px 32px rgba(124, 58, 237, 0.32), 0 6px 14px rgba(245, 192, 68, 0.24); }
.icon-img { max-width: 32px; max-height: 32px; object-fit: contain; }
.icon-emoji { display: inline-block; line-height: 1; }
.hero-buttons .btn { transition: all 0.4s cubic-bezier(0.16, 1, 0.3, 1); border-radius: 16px; }
.hero-buttons .btn:hover { transform: translateY(-3px); box-shadow: 0 20px 40px rgba(15, 15, 26, 0.35), 0 8px 18px rgba(245, 192, 68, 0.2); }
.hero-buttons .btn-warning { background-color: #f5c044; border-color: #f5c044; color: #2e1065; font-weight: 600; }
.hero-buttons .btn-warning:hover { background-color: #d99e1b; border-color: #d99e1b; }
.hero-buttons .btn-outline-light:hover { background-color: rgba(245, 192, 68, 0.2); color: #fff; }
::-webkit-scrollbar { width: 10px; height: 10px; }
::-webkit-scrollbar-track { background: #ede8f6; }
::-webkit-scrollbar-thumb { background: #a78bfa; border-radius: 8px; }
::-webkit-scrollbar-thumb:hover { background: #7c3aed; }
* { scrollbar-width: thin; scrollbar-color: #a78bfa #ede8f6; }
@media print { ... } Need preserve all selectors. Change colors? Print body background #fff color #000, keep. Could change font-size? No. Keep as-is. But rule says colors can change. Keep black/white. Maybe change a[href^="http"]::after color #555 -> #444. Not necessary. I'll keep mostly original but maybe adjust. But we must output. No AI comments.

Print section:
@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: #444; }
    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; }
}
Note original had selector list formatting. I can inline or keep. Fine.

Animations:
@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; }
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; } }
Wait .toc-box padding in media query: original had .toc-box { padding: var(--space-sm) !important; }. If I added padding in base? I decided not. But if I add border-radius only, the media query padding remains. Fine.

But I added border

@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;
        background-color: #f7c948;
        color: #150f2e;
        border-color: rgba(124, 58, 237, 0.35);
        border-radius: 999px;
        text-shadow: 0 1px 0 rgba(255, 255, 255, 0.45);
        box-shadow: 0 10px 24px -10px rgba(247, 201, 72, 0.65), 0 3px 8px -4px rgba(21, 15, 46, 0.35);
        transition: box-shadow 420ms cubic-bezier(0.22, 1, 0.36, 1), background-color 320ms ease-in-out;
    }

    .contact-channels-section article,
    .contact-quick-section .contact-card {
        padding: var(--space-md) !important;
        border-radius: 26px;
        border-color: rgba(124, 58, 237, 0.16);
        background-color: #fdfbff;
        box-shadow: 0 32px 60px -34px rgba(21, 15, 46, 0.42), 0 12px 26px -20px rgba(124, 58, 237, 0.32);
        transition: box-shadow 480ms cubic-bezier(0.22, 1, 0.36, 1), transform 480ms cubic-bezier(0.22, 1, 0.36, 1), background-color 320ms ease-in-out;
    }
}