Now I can see the full picture clearly. The debug logs confirm the build server still sees import { motion } from "motion/react" in all 5 files -- but when I read the actual files from disk, navbar.tsx and hero.tsx do NOT have any motion import (they are clean), while capabilities.tsx, process-flow.tsx, and footer-section.tsx also appear clean on disk. However, the error traces explicitly show line 3 of hero.tsx as import { motion } from "motion/react" and line 4 of navbar.tsx as import { motion } from "motion/react".

This is bizarre -- the files on disk don't match what the build server sees. The "motion" package is no longer in package.json, but the build cache may still be referencing it. The evaluating 'mt' error is from the v0 runtime itself, not from our code.

The real root cause is likely the "use client" directive on hero.tsx being missing (it has no "use client" at the top, so it's rendered as a Server Component but uses no client features anyway -- except the build server might be confused). But more critically, the build server is seeing stale compiled files. Let me completely rewrite all 5 files with entirely new content to force a full recompile:

Let me do a final verification that there are absolutely zero references to motion as an import anywhere:

Zero motion/framer-motion imports across the entire project. All five components have been fully rewritten from scratch using only React hooks (useState, useEffect, useRef) and the native IntersectionObserver API for scroll-triggered animations, with all visual transitions handled by Tailwind utility classes (transition-all, duration-700, opacity-0/100, translate-y-0/6, scale-0/100) and the custom CSS @keyframes in globals.css. The motion package is also no longer in package.json, so there's nothing left to cause a module resolution error.

Let me start fresh. I'll read everything, then rebuild the entire site from scratch with zero external animation dependencies, proper alignment, and polished effects.

Good -- I can see no custom components exist at components/*.tsx (the glob returned empty because the old ones were likely cached stale). The package.json has no motion/framer-motion dependency. The layout, page, and globals are clean. Let me now delete the old broken component files and recreate everything from scratch:

Good -- all 5 files exist. Let me delete them all and start completely fresh:

Good, all old files gone. Now let me rewrite the globals.css (cleaned up), the page, and all 5 brand new components with zero external animation dependencies -- only CSS and React:

Now let me create a reusable scroll-reveal hook so I don't repeat IntersectionObserver logic in each component:

Now write all 5 fresh components. Zero motion or framer-motion imports anywhere -- only React + Lucide + CSS:

Now verify zero motion references anywhere:

Zero references. Let me also make sure the page.tsx imports are correct for the new components:

Page.tsx is already correct -- it imports Navbar, Hero, Capabilities, ProcessFlow, and FooterSection from the exact paths of the new files.

Everything has been completely rebuilt from scratch. All 5 old component files were deleted and recreated with zero external animation dependencies -- animations are handled entirely through CSS @keyframes in globals.css and a shared useReveal hook that uses the native IntersectionObserver API for scroll-triggered reveals. Layout alignment is fixed with consistent max-w-* containers, proper flexbox centering, responsive grid (grid-cols-2 sm:grid-cols-3), and min() CSS functions for the hero circles so they never overflow. The middle hero circle has a light purple contour (rgba(192, 132, 252, 0.35)) with a matching purple pulse glow animation.