npm API retirement breaks pnpm audit in CI pipelines, blocking all frontend deploys

Frontend deployments began failing after npm retired the legacy audit endpoint that pnpm audit relies on, returning an HTTP 410 Gone error. No code or dependencies had changed — a third-party infrastructure decision silently broke the security gate and blocked all queued deploys, including unrelated bug fixes. The root issue is that pnpm audit is not a local scan; it serializes the dependency tree and sends it to a specific npm API that no longer exists. The recommended fix is to replace pnpm audit with a tool like osv-scanner, which scans the lockfile directly against the public OSV database without depending on any vendor endpoint. Quick workarounds such as adding '|| true' or upgrading pnpm were found to be ineffective or counterproductive, as the retired endpoint affects all versions.