Fix Static Assets 404 After Deployment
Asset 404s usually come from the wrong build base path, files uploaded to the wrong directory, or an Nginx location block matching the request incorrectly.
Quick diagnosis
Compare the page URL, expected asset URL, and any root-level asset request to find where the path changed.
What the result means
If HTML loads but JS or CSS fails, inspect whether the built files exist and whether the browser requests the same path.
Verification method
After each fix, reload in a fresh browser session and inspect rendered text, not only HTTP headers.