404 errors on Custom Header JS/CSS files after redeploy

Our Ahrefs Site Audit is flagging broken JS/CSS on 140+ and 297+ pages respectively. The specific files returning 404 are: https://sellerview.superblog.click/_sbv/1785758440/js/dropdown-chevron-fix.js https://sellerview.superblog.click/_sbv/1785758440/js/utils.js https://sellerview.superblog.click/_sbv/1785878164/css/legacy/index.css We use the Custom Header feature (Settings → Advanced → Header/Footer), and these references likely live inside that custom code block. Questions: Are these platform-generated files, or from our Custom Header code? Does the _sbv/{number}/... build path rotate on redeploy? Is there a stable way to reference custom assets so they don't break on future deploys? Can you check deploy logs to confirm when the build hash last changed? If these are in our Custom Header code, is it safe to remove those 3 lines without breaking dropdown/nav functionality? We'd prefer not to edit the live Custom Header code ourselves until we understand the cause, since it affects all published posts.