Asset and codegen imports resolve

A missing asset or codegen output fails the bundler the moment it tries to inline the file, so import logo from './logo.svg' with no logo.svg on disk hard-stops the build. AI tools commonly write import statements for images, stylesheets, and Prisma/GraphQL-Codegen outputs that were never created — the codegen case is especially subtle because the file exists locally after npm run dev but the CI step skips the generator and fails. Either way the deploy breaks.

For each flagged asset, either create the file at the expected location or remove the import if it was hallucinated. For codegen outputs, wire the generator into the install and build lifecycle in package.json so CI produces the same files your dev machine does:

{
  "scripts": {
    "postinstall": "prisma generate",
    "build": "prisma generate && next build"
  }
}