/* ============================================================
   ANIMATIONS.CSS — keyframes + scroll reveal utility classes
   Kept deliberately restrained: motion supports the diagnostic
   theme (pulse/scan) rather than decorating every element.
   ============================================================ */

@keyframes pulse-dot {
  0%, 100% { box-shadow: 0 0 0 4px rgba(53,208,127,0.18); }
  50% { box-shadow: 0 0 0 8px rgba(53,208,127,0.06); }
}

@keyframes hud-float {
  0%, 100% { transform: translateY(0); }
  50% { transform: translateY(-8px); }
}

@keyframes scan-line {
  0% { transform: translateY(-100%); }
  100% { transform: translateY(100%); }
}

@keyframes fade-up {
  from { opacity: 0; transform: translateY(24px); }
  to { opacity: 1; transform: translateY(0); }
}

@keyframes fade-in {
  from { opacity: 0; }
  to { opacity: 1; }
}

@keyframes spin-slow {
  from { transform: rotate(0deg); }
  to { transform: rotate(360deg); }
}

/* Scroll-reveal: progressive enhancement.
   Content is visible by default (no JS dependency). JS only adds
   ".js-reveal" once it has successfully attached the IntersectionObserver,
   which is what actually opts an element into the hidden/animate-in state.
   This guarantees the page is never blank if a script fails to run
   (blocked module scripts, sandboxed storage, ad blockers, etc.). */
[data-reveal] {
  opacity: 1;
  transform: none;
}
[data-reveal].js-reveal {
  opacity: 0;
  transform: translateY(28px);
  transition: opacity 0.7s var(--ease-out), transform 0.7s var(--ease-out);
  transition-delay: var(--d, 0ms);
}
[data-reveal].js-reveal.is-visible { opacity: 1; transform: translateY(0); }
[data-reveal="fade"].js-reveal { transform: none; }

@media (prefers-reduced-motion: reduce) {
  [data-reveal] { opacity: 1 !important; transform: none !important; transition: none !important; }
  .diag-hud { animation: none; }
  .diag-hud__dot { animation: none; }
}