Act as a senior front-end engineer. Images, fonts or downloads load on my machine, but on the live site some of them 404 or show as broken. Built with {{tech_stack}}. One example: {{error_message}} Gather evidence first: - In the network tab, filter by images, fonts and other: copy each failing file's exact requested URL and status - Compare it with where the file actually sits in the build output folder after a production build - Check the host's deploy log or file browser to see whether the file was uploaded at all Likely causes for this symptom: 1. File name case: Logo.PNG on disk, logo.png in code. Works on Mac and Windows, fails on the Linux server 2. Files referenced by a string path the bundler never sees, so they're not copied. Put them in the public folder, or import them so the bundler handles them 3. Public folder paths written wrong: including the word public in the URL, or a relative path that breaks on nested routes (images/a.png instead of /images/a.png) 4. A subfolder or base path deploy that asset URLs don't account for 5. Files ignored by git, stored with Git LFS, or over the host's size limit 6. Images from a storage bucket: a private bucket, expired signed URLs, the wrong project URL in production, or a domain missing from the image optimizer's allowed list 7. Fonts loaded from another domain and blocked by CORS Confirm which cause applies, fix it at the source, and rename files to lowercase with hyphens. Add checks that would have caught it: a build step or test that crawls the built pages and fails on any asset returning 404, plus a case-sensitive import lint rule. Explain it in plain words.