fix(dev-1705): bump ws to 8.21.0

[spur-vuln-author]

Context

GHSA-96hv-2xvq-fx4p: ws before 8.21.0 is vulnerable (high severity, DoS via unbounded connection buffering). Transitive dependency (not declared in any package.json), resolved via pnpm-lock.yaml. No Dependabot PR exists for this finding, so this PR was constructed directly from the advisory's first_patched_version.

Test evidence

No Dependabot PR existed; constructed from first_patched_version 8.21.0. Added a pnpm.overrides entry and regenerated the lockfile with pnpm install --lockfile-only. Confirmed via lockfile inspection that ws now resolves to 8.22.0 (previously 8.18.1), satisfying >= 8.21.0. Companion-file scan (Dockerfiles, .nvmrc, go.mod, CI workflow YAML, etc. hardcoding 8.18.1) found no hits.

Risk

Low. Lockfile-only transitive dependency bump within the same major version line. GHSA-96hv-2xvq-fx4p / high severity; Tier 1 / 90-day SLA, currently overdue.

---

[spur-vuln-reviewer]

Escalating: Gate 3 (diff equivalence) mechanically FAILed. gate3-check.sh: GATE3 FAIL target=ws manifest=pnpm-lock.yaml pr_version=? required=8.21.0 alerts=80 extra_files=1 state=open. Detail: the helper has no extraction rule for ecosystem=npm manifest basename=pnpm-lock.yaml, so it could not extract the new ws version from the diff, and flagged package.json as a file outside {manifest, lockfile} (which is actually the expected direct-dependency file for an npm/pnpm version bump). This looks like a tooling gap in gate3-check.sh (no pnpm-lock.yaml parser) rather than a real diff deviation, but per the review contract a mechanical Gate 3 FAIL is never re-derived or second-guessed by the reviewer. Required version per max open Dependabot alert(s) 80: 8.21.0. Not merged. A human must review this. This reviewer will not act on this PR again. [[spur-vuln-reviewer: escalated diff-mismatch-constructed]]