fix(deps): clear the CLI production audit

[Astro-Han]

Summary

Build CLI release candidate fails on main and on every open PR:

Error: CLI production dependency audit failed: {"info":0,"low":0,"moderate":1,"high":1,"critical":0,"total":2}

Two advisories landed on transitive production dependencies of the CLI — fast-uri (high) and qs (moderate). scripts/release-cli-package.mjs audits production dependencies before it packs, so the gate is doing its job; the lockfile has to move.

packages/cli/THIRD_PARTY_NOTICES.txt moves with it. The notice file records the exact resolved versions, and check:cli-third-party-notices — the next step in the same script — fails with fast-uri@3.1.5: missing from package-lock.json if only the lockfile changes. Regenerated with node scripts/generate-third-party-notices.mjs --target cli.

@xmldom/xmldom (dev) is in the diff because npm audit fix resolves the root lockfile as a whole.

Why the open Dependabot PRs do not cover this

• chore(deps): bump qs from 6.15.3 to 6.16.0 in /packages/eval/harbor/deepseek-harness-toolchain #4586, chore(deps): bump fast-uri from 3.1.5 to 3.1.7 in /packages/eval/harbor/deepseek-harness-toolchain #4587 — same packages, but in packages/eval/harbor/deepseek-harness-toolchain/package-lock.json. That is a different lockfile; the CLI audit reads the root one.
• chore(deps-dev): bump @xmldom/xmldom from 0.8.13 to 0.8.15 #4585 — root lockfile, but @xmldom/xmldom is a dev dependency and the audit runs --omit=dev.

Merging all three leaves the gate red.

Verification

• npm audit --omit=dev — 2 vulnerabilities (1 high, 1 moderate) before, 0 after.
• node scripts/generate-third-party-notices.mjs --target cli --check — OK.
• npm ci clean.
• npm run release:cli:pack -- --allow-dirty gets past both gates above and then stops on cargo deny, which is not installed on this machine. CI has it.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: Claude Code diagnosed the failing gate, applied npm audit fix, regenerated the notice file and drafted this description; the scope and the decision to keep it separate from the e2e work in #4577 were the author's.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes
• No — dependency versions only

[Astro-Han]

Superseded by #4578, which landed the same root-lockfile bumps on main.