Public asset references exist on disk

A missing file under public/ — a hero image, a logo, a web font — renders as a broken image icon, a ghosted logo slot, or a fallback system font in production. None of these fail the build; they degrade the first paint silently. AI tools frequently reference /images/hero.png or /fonts/Inter.woff2 that were never committed to public/, and the failure only surfaces when a designer or customer notices the missing asset days later.

For each unresolved reference, either drop the file into public/ at the expected path or correct the reference to an asset that exists. On a Next.js project the <Image> component from next/image surfaces missing-file errors at build time under output: 'export':

import Image from 'next/image'
<Image src="/images/hero.png" alt="Hero" width={1200} height={630} />

Confirm the file exists at public/images/hero.png.