(function () { try { if (sessionStorage.getItem('introPlayed:v1') === '1') return; } catch (e) {} if (window.matchMedia && window.matchMedia('(prefers-reduced-motion: reduce)').matches) return; var d = document.documentElement; d.classList.add('intro-active'); // Resolve the theme ourselves instead of reading // d.classList.contains('dark') — next-themes' own // theme-setting script (rendered inside , // i.e. AFTER this script in document order) hasn't run // yet at this point, so that class is never present here // and this always picked the light avatar/background // regardless of the visitor's actual theme. Mirrors // next-themes' own algorithm exactly (storageKey="theme", // defaultTheme="dark") so the two never disagree. var stored = null; try { stored = localStorage.getItem('theme'); } catch (e) {} var isDark = stored ? stored === 'dark' : true; var src = isDark ? '/avatar-dark.jpg' : '/avatar-light.jpg'; var shell = document.createElement('div'); shell.id = 'intro-shell'; // This shell owns the entire loading-hold visual by // itself — its ring/breathe/dot CSS animations run // continuously and are NEVER recreated by React (see // components/IntroLoader.tsx). React only reads this // element's live rect once, at the exact moment flight // begins, then removes it and mounts a flying clone in // its place — a single one-time hand-off rather than a // continuous animation being swapped out from under // itself, which is what used to cause visible stutter. shell.innerHTML = '

' + '

' + '

' + '

' + '

'; document.body.appendChild(shell); })();

Contact Me